Hour audit: 2026-09-12T04
back to the files for this hour · how the archive is audited
Every number on this page is a stored measurement read from this hour's own records: its
manifest.json, its witness
statistics sidecar, and the corpus attestation. Nothing here is computed from the served
bytes at the time you load the page, so no line below claims the bytes are correct. The
digest and the one command that checks them are printed instead.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-12T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T04:00:00.000006398+00:00 · last event 2026-09-12T04:59:59.999879285+00:00
VOLUME 106,393,194 rows · 1,108,667,198 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 104,990,481 · g: 104,988,913 · f: 104,988,625 · h: 104,937,171 · c: 88,976,972 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 2,370,257 (2.23%) · g: 73,873 (0.07%) · f: 526,311 (0.49%) · h: 18,532,359 (17.42%) · c: 84,890,394 (79.79%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 cb3af358844a481789911fd84b180fe7026911d300bd4aaff41cc82c955888b4
the corpus checksum ledger names this file with the same digest
joined 106,406,776 to merged 106,393,194, minus 13,582 (minus 0.0128%)
boundary drops 13,582 · guard cache
SIDECARS none: this hour's manifest has no v31 key. The v3.1 sidecars are optional, and hours before them have none
MARKETS not measured (the per-hour market census runs on the capture host and its output is not published per hour)
HISTORY merged 2026-09-12T06:34:41Z as cefgh
layout union-event-sorted-v1
re-merges not measured (the merge ledger records the merge that produced this file, not the history of attempts)
supersessions not measured (supersession is recorded per corpus in the storage registry, not in the hour manifest)
CHECKS 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
PASS the checksum ledger names this file
PASS the hour is whole
PASS a boundary guard ran
UPSTREAM our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.The words in this report
Each line in the CHECKS block states what was found, not what was
hoped for: a check that passes is named for the thing that is true, and a check that does
not is renamed to the thing that is wrong. So FINDING never sits beside a
sentence asserting the opposite of the one below it.
The report above is fixed-width text, so nothing in it can be clicked. The same terms are linked here instead. Its verdict is a statement about minutes and nothing else. The row it reports comes from this hour's own manifest and its witness-statistics sidecar, and the completeness line comes from the corpus attestation. The gap between the joined and merged counts is deduplication, not loss, and the boundary drops are the duplicates discarded at the seam with the hour before. Where the history line names a supersession, this hour was rebuilt to a better state after it was first published. The precision is the timestamp resolution these files carry.
Detail
The same records, per product. A product holding no rows renders its zero rather than
being dropped: dropped and empty are indistinguishable to a reader, and only one of them is
a defect. A cell reading not meas. is one nothing published, which is a third
thing again and never a zero.
The class column is the merger's own verdict for that product, and it is
keyed to CONTRIBUTION rather than presence. FULL means every machine expected to
be capturing this hour delivered rows for that product; PARTIAL means some did
and some did not; SINGLE-BY-DESIGN means only one machine was ever expected, and
SINGLE-BY-DEFECT means several were and one delivered. So PARTIAL
here is a statement about the fleet, not about the product being damaged or truncated: the
rows that are present are whole.
PRODUCT rows bytes row groups sha256 best_bid_ask 10,074,730 111,922,422 0-38 ff1bea8c30af8296665084a8bef966e4ee6e286c78b1c95b883c21bac23914e1 book 1,507,900 83,138,748 39-44 dc620cce1689b37b9cb8b57c120cd17f9feca06f7bf3ef00873eaeb6bea9025a last_trade_price 45,207 2,611,068 45-45 000fe48c19280b963a5ebff80ef900a6f21fd555bbd955e9d8dfb1a39fbb39e5 market_resolved 1,371 178,979 46-46 cb7778151d88adaa0027b88468ec849ea1b4e18d446ae51d6d8f6152375efdde new_market 2,146 203,408 47-47 aeec6dcb420e67b9a0a17297f1b29940912cd12554a1e509b5a82c8dde073ee9 price_change 94,759,000 909,294,732 48-409 880fe0409eadde487ab5c2c6ee0ee2a049f4174c3ac35134ef7808bf5b2e35f6 tick_size_change 2,840 104,482 410-410 4d0cc689e697785d7fec7a2f1fb70797c1bb3310c8147c88e32ca2192333710f EVENT MIX count share price_change 94,759,000 89.06% best_bid_ask 10,074,730 9.47% book 1,507,900 1.42% last_trade_price 45,207 0.04% tick_size_change 2,840 <0.01% new_market 2,146 <0.01% market_resolved 1,371 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,075,745 10,074,730 1,015 2,532 FULL book 1,511,548 1,507,900 3,648 205,702 FULL last_trade_price 45,208 45,207 1 311 FULL market_resolved 1,371 1,371 0 63 FULL new_market 2,156 2,146 10 128 FULL price_change 94,767,908 94,759,000 8,908 1,738 FULL tick_size_change 2,840 2,840 0 50 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,509,469 8,129,155 5ms 10ms 277ms 25.7s 0 transport_latency_assumed best_bid_ask e 10,073,106 213,944 39ms 43ms 214ms 10.8s 0 transport_latency_assumed best_bid_ask f 10,073,278 45,741 45ms 51ms 245ms 18.0s 0 transport_latency_assumed best_bid_ask g 10,072,090 4,958 85ms 106ms 498ms 11.2s 0 transport_latency_assumed best_bid_ask h 10,073,808 1,680,932 18ms 26ms 381ms 30.1s 0 transport_latency_assumed book c 1,437,355 1,418,978 19.3min 10.6h 31.4d 105.3d 0 book_staleness book e 148,241 18,883 44ms 3.1h 9.4d 105.3d 0 book_staleness book f 138,127 12,430 50ms 1.9h 6.6d 87.2d 0 book_staleness book g 164,554 23,207 161ms 3.6h 18.4d 105.3d 0 book_staleness book h 145,686 34,402 27ms 2.4h 6.7d 105.3d 0 book_staleness last_trade_price c 35,934 34,024 10ms 43ms 392ms 17.1s 0 transport_latency_assumed last_trade_price e 45,099 1,178 45ms 101ms 519ms 4.4s 0 transport_latency_assumed last_trade_price f 45,143 259 52ms 111ms 655ms 12.8s 0 transport_latency_assumed last_trade_price g 45,049 31 97ms 216ms 1.4s 8.9s 0 transport_latency_assumed last_trade_price h 45,128 9,715 23ms 65ms 557ms 30.1s 0 transport_latency_assumed market_resolved c 1,218 1,196 5ms 6.0min 10.6min 11.2min 0 transport_latency_assumed market_resolved e 1,090 10 41ms 142ms 348ms 514ms 0 transport_latency_assumed market_resolved f 1,090 11 47ms 131ms 346ms 506ms 0 transport_latency_assumed market_resolved g 1,091 1 92ms 257ms 585ms 2.4min 0 transport_latency_assumed market_resolved h 1,090 153 19ms 65ms 137ms 2.5s 0 transport_latency_assumed new_market c 1,302 723 273ms 59.7s 6.3min 26.1min 0 transport_latency_assumed new_market e 1,321 400 231ms 21.3s 36.0s 1.2min 0 transport_latency_assumed new_market f 1,321 394 191ms 20.4s 32.7s 1.2min 0 transport_latency_assumed new_market g 1,311 124 380ms 21.4s 32.4s 3.5min 0 transport_latency_assumed new_market h 1,321 505 204ms 21.8s 32.5s 39.5s 0 transport_latency_assumed price_change c 78,989,054 75,303,804 5ms 10ms 298ms 28.4s 0 transport_latency_assumed price_change e 94,718,784 2,135,804 39ms 45ms 285ms 11.2s 0 transport_latency_assumed price_change f 94,726,826 467,452 46ms 53ms 317ms 18.6s 0 transport_latency_assumed price_change g 94,701,978 45,548 85ms 114ms 606ms 13.4s 0 transport_latency_assumed price_change h 94,667,298 16,806,392 18ms 30ms 400ms 30.1s 0 transport_latency_assumed tick_size_change c 2,640 2,514 5ms 9ms 720ms 1.6s 0 transport_latency_assumed tick_size_change e 2,840 38 39ms 44ms 180ms 538ms 0 transport_latency_assumed tick_size_change f 2,840 24 45ms 50ms 227ms 547ms 0 transport_latency_assumed tick_size_change g 2,840 4 84ms 101ms 618ms 1.7s 0 transport_latency_assumed tick_size_change h 2,840 260 18ms 24ms 1.7s 6.9s 0 transport_latency_assumed
Captured and supplied are different numbers
Captured is how many rows each machine's own feed carried. Redundant capture means these OVERLAP, heavily and on purpose, so they do not partition the file and their sum is larger than it. Two machines each capturing nearly every event is the archive working, not double counting.
Supplied is how many rows of the merged file actually came from that machine. This one does partition: it sums to the file's row count exactly. But it is decided by the merge's tie-break, so a machine can capture almost everything and supply almost nothing. Read alone, either number tells a false story about the fleet, which is why both are printed and neither is called "the witness share".
What the skew columns mean
Arrival skew is the receipt timestamp minus the venue timestamp, in milliseconds. For six of the seven products the sidecar interprets it as transport latency, and marks that interpretation assumed: it rests on the venue timestamp being emit time, which we cannot verify from outside.
book is not latency and must not be read as latency. Its
venue timestamp is the last time the book changed, so the sidecar interprets it as book
staleness and warns in its own note that large values mean a quiet book rather than slow
transport. Its maximum runs to weeks for that reason. This is why the table above gives a
row per product per machine and never one figure for the hour: percentiles do not average,
and these seven do not measure the same quantity.
Check it yourself
The digest above is a claim. This is how you refuse to take our word for it:
curl -O https://archive.pendulumflow.com/v3/2026-09-12/04/2026-09-12T04.parquet sha256sum 2026-09-12T04.parquet # compare with the sha256 line in the report above
A range digest certifies bytes. That those bytes are the product the manifest names comes from the manifest, which is why both are published and both are checkable.