Hour audit: 2026-09-08T14
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-08T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T14:00:00.000864210+00:00 · last event 2026-09-08T14:59:59.999958165+00:00
VOLUME 105,715,784 rows · 1,134,518,671 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 104,910,997 · e: 104,753,706 · f: 104,706,462 · g: 104,213,927 · c: 96,639,688 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 13,458,149 (12.73%) · e: 1,163,687 (1.10%) · f: 669,532 (0.63%) · g: 88,858 (0.08%) · c: 90,335,558 (85.45%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 105,715,784 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5d08797467512133e7f4ce7d23f7683cf71772fb6751aeea78d45e991c08e8a9
the corpus checksum ledger names this file with the same digest
joined 105,718,512 to merged 105,715,784, minus 2,728 (minus 0.0026%)
boundary drops 2,728 · 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-08T15:57:56Z 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,153,582 115,218,702 0-38 9d9f5175016160cf4ac192bfd911774f5a3c311dbd48ea4e6ce6ccf863ec8ca7 book 1,024,398 75,128,835 39-42 7f35e160ce0bc19339e0b1ea15023d6035945a66002dddb13dbfbf0bd2408170 last_trade_price 77,090 4,280,194 43-43 bd95fde1cfae03d5377e046ff483581d608bb0ef952a663f14e45a87e0060ef4 market_resolved 1,096 169,194 44-44 8183e1c1632554bd9f9967fc937aa1e4617cdb4d23891165e765bbd73d0a6589 new_market 3,084 283,249 45-45 b0241ebb4807101c3edff7580330cfcc136e39f33bbf384dbf36b43d0dcba306 price_change 94,453,426 938,120,354 46-406 cb9ba70d6f63cc0fdfa283b8b1448f4a1741aba60a6a058400d0e8d961dfa035 tick_size_change 3,108 114,274 407-407 ce7a59fda77d24d9db3a6077fe49d1c066062e0259515e9e106c4f70f884bf04 EVENT MIX count share price_change 94,453,426 89.35% best_bid_ask 10,153,582 9.60% book 1,024,398 0.97% last_trade_price 77,090 0.07% tick_size_change 3,108 <0.01% new_market 3,084 <0.01% market_resolved 1,096 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,153,869 10,153,582 287 988 FULL book 1,024,820 1,024,398 422 177,697 FULL last_trade_price 77,091 77,090 1 165 FULL market_resolved 1,096 1,096 0 16 FULL new_market 3,084 3,084 0 99 FULL price_change 94,455,444 94,453,426 2,018 1,204 FULL tick_size_change 3,108 3,108 0 41 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,245,604 8,700,194 6ms 15ms 180ms 10.1s 0 transport_latency_assumed best_bid_ask e 10,148,974 100,763 41ms 57ms 333ms 23.0s 0 transport_latency_assumed best_bid_ask f 10,147,439 51,802 46ms 66ms 382ms 25.7s 0 transport_latency_assumed best_bid_ask g 10,127,447 4,437 84ms 118ms 670ms 43.1s 0 transport_latency_assumed best_bid_ask h 10,152,248 1,296,386 18ms 32ms 323ms 51.3s 0 transport_latency_assumed book c 910,845 830,274 7.9min 22.4h 30.7d 101.7d 0 book_staleness book e 230,648 48,232 57ms 4.4h 8.9d 101.7d 0 book_staleness book f 219,485 42,238 57ms 3.4h 6.6d 101.7d 0 book_staleness book g 184,521 20,872 94ms 4.2min 1.1d 83.2d 0 book_staleness book h 258,753 82,782 47ms 7.9h 17.0d 101.7d 0 book_staleness last_trade_price c 70,302 66,039 11ms 47ms 260ms 5.0s 0 transport_latency_assumed last_trade_price e 76,524 950 48ms 198ms 3.7s 22.8s 0 transport_latency_assumed last_trade_price f 76,370 463 54ms 199ms 2.9s 25.8s 0 transport_latency_assumed last_trade_price g 74,413 145 96ms 296ms 9.0s 42.2s 0 transport_latency_assumed last_trade_price h 76,994 9,493 24ms 101ms 568ms 43.2s 0 transport_latency_assumed market_resolved c 979 947 6ms 1.9min 4.5min 5.6min 0 transport_latency_assumed market_resolved e 993 7 42ms 190ms 777ms 59.8s 0 transport_latency_assumed market_resolved f 993 7 47ms 195ms 697ms 59.8s 0 transport_latency_assumed market_resolved g 993 not meas. 86ms 278ms 1.7s 14.7s 0 transport_latency_assumed market_resolved h 993 135 18ms 91ms 470ms 59.5s 0 transport_latency_assumed new_market c 1,690 1,119 119ms 1.2min 5.4min 1.6h 0 transport_latency_assumed new_market e 1,785 339 236ms 1.0min 2.5min 2.6min 0 transport_latency_assumed new_market f 1,785 476 250ms 59.3s 2.4min 2.5min 0 transport_latency_assumed new_market g 1,785 270 376ms 52.1s 2.6min 2.6min 0 transport_latency_assumed new_market h 1,785 880 174ms 1.0min 2.4min 2.5min 0 transport_latency_assumed price_change c 86,407,324 80,734,262 6ms 20ms 232ms 10.1s 0 transport_latency_assumed price_change e 94,291,674 1,013,356 41ms 81ms 510ms 23.0s 0 transport_latency_assumed price_change f 94,257,282 574,534 47ms 90ms 570ms 25.8s 0 transport_latency_assumed price_change g 93,821,660 63,130 85ms 160ms 996ms 43.1s 0 transport_latency_assumed price_change h 94,417,116 12,068,144 18ms 43ms 353ms 52.6s 0 transport_latency_assumed tick_size_change c 2,944 2,723 6ms 19ms 182ms 339ms 0 transport_latency_assumed tick_size_change e 3,108 40 41ms 56ms 472ms 599ms 0 transport_latency_assumed tick_size_change f 3,108 12 46ms 69ms 328ms 561ms 0 transport_latency_assumed tick_size_change g 3,108 4 84ms 125ms 640ms 27.4s 0 transport_latency_assumed tick_size_change h 3,108 329 18ms 35ms 308ms 1.0s 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-08/14/2026-09-08T14.parquet sha256sum 2026-09-08T14.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.