Hour audit: 2026-09-12T06
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-12T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T06:00:00.000078729+00:00 · last event 2026-09-12T06:59:59.999996735+00:00
VOLUME 107,518,134 rows · 1,121,706,772 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 105,457,195 · g: 105,190,946 · f: 105,174,636 · h: 105,141,855 · c: 83,560,944 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,136,915 (1.06%) · g: 28,831 (0.03%) · f: 201,263 (0.19%) · h: 25,202,724 (23.44%) · c: 80,948,401 (75.29%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 107,518,134 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6b9a97443e7c1bceabecb479342f4bb530cf962c03d463aebb82ac721d4f55ee
the corpus checksum ledger names this file with the same digest
joined 107,522,627 to merged 107,518,134, minus 4,493 (minus 0.0042%)
boundary drops 4,493 · 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-12T08:34:37Z 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,572,780 115,564,647 0-40 7b4861f9606de657cc13f3086e341a6faedeede57f78d841cf800162bb118422 book 2,438,002 108,217,315 41-50 7cdffefd30ac434dc4ff8214f4d99378a530c5c545213365d44a23d2c7d45237 last_trade_price 47,053 2,709,407 51-51 77e42fe96550cd88fc0ea1549522895928e1fd9d51b4f9fa387d12ed756a2a2e market_resolved 1,547 135,864 52-52 1f75aa587bb57615cfea505bab2ccd7c91b24f9546b7bebe63d04fc99baee055 new_market 665 56,280 53-53 4174c0c6238f3bdad733249985207c1eb4fa2015c5b56117e0acf2123051c110 price_change 94,456,863 893,749,797 54-414 6b4d1b01777c792ce4e359131125d11de729551dea586db263cddd0f588cdfbc tick_size_change 1,224 46,095 415-415 54412630022c00b3816e66ea95e660367c15c94c752dea2333e2f2e1a77a9626 EVENT MIX count share price_change 94,456,863 87.85% best_bid_ask 10,572,780 9.83% book 2,438,002 2.27% last_trade_price 47,053 0.04% market_resolved 1,547 <0.01% tick_size_change 1,224 <0.01% new_market 665 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,573,107 10,572,780 327 3,885 FULL book 2,439,070 2,438,002 1,068 205,008 FULL last_trade_price 47,057 47,053 4 440 FULL market_resolved 1,547 1,547 0 12 FULL new_market 665 665 0 0 FULL price_change 94,459,957 94,456,863 3,094 4,985 FULL tick_size_change 1,224 1,224 0 92 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,254,732 7,993,367 5ms 9ms 70ms 2.9s 0 transport_latency_assumed best_bid_ask e 10,560,030 91,974 41ms 44ms 87ms 2.0s 0 transport_latency_assumed best_bid_ask f 10,570,819 17,030 46ms 50ms 102ms 2.5s 0 transport_latency_assumed best_bid_ask g 10,569,659 616 84ms 106ms 253ms 13.9s 0 transport_latency_assumed best_bid_ask h 10,571,871 2,469,793 17ms 21ms 70ms 6.7s 0 transport_latency_assumed book c 2,225,073 2,191,383 11.5min 12.6h 31.5d 105.4d 0 book_staleness book e 550,114 168,154 6.2min 13.1h 27.7d 105.3d 0 book_staleness book f 137,218 14,440 49ms 57.4min 6.7d 105.4d 0 book_staleness book g 159,429 22,753 121ms 3.7h 17.5d 105.3d 0 book_staleness book h 134,275 41,272 22ms 47.7min 6.1d 105.4d 0 book_staleness last_trade_price c 33,910 32,455 10ms 40ms 217ms 4.8s 0 transport_latency_assumed last_trade_price e 46,952 678 46ms 97ms 376ms 4.9s 0 transport_latency_assumed last_trade_price f 46,912 190 52ms 102ms 289ms 5.0s 0 transport_latency_assumed last_trade_price g 46,957 10 97ms 211ms 791ms 5.0s 0 transport_latency_assumed last_trade_price h 47,010 13,720 22ms 56ms 220ms 4.9s 0 transport_latency_assumed market_resolved c 1,343 1,336 4.2min 12.9min 15.7min 15.9min 0 transport_latency_assumed market_resolved e 786 11 43ms 123ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 786 40 49ms 139ms 58.5s 1.0min 0 transport_latency_assumed market_resolved g 786 not meas. 96ms 264ms 59.2s 59.2s 0 transport_latency_assumed market_resolved h 786 160 19ms 62ms 58.2s 1.0min 0 transport_latency_assumed new_market c 525 378 166ms 12.0min 12.1min 12.2min 0 transport_latency_assumed new_market e 350 60 87ms 12.7s 29.4s 1.4min 0 transport_latency_assumed new_market f 350 51 100ms 12.7s 22.9s 1.3min 0 transport_latency_assumed new_market g 350 32 150ms 13.6s 25.2s 27.2s 0 transport_latency_assumed new_market h 350 144 61ms 16.9s 43.4s 1.6min 0 transport_latency_assumed price_change c 73,044,505 70,728,650 5ms 9ms 75ms 4.3s 0 transport_latency_assumed price_change e 94,297,739 875,974 41ms 45ms 115ms 4.3s 0 transport_latency_assumed price_change f 94,417,327 169,510 47ms 50ms 125ms 4.3s 0 transport_latency_assumed price_change g 94,412,541 5,420 84ms 111ms 295ms 13.9s 0 transport_latency_assumed price_change h 94,386,339 22,677,309 17ms 22ms 80ms 6.9s 0 transport_latency_assumed tick_size_change c 856 832 5ms 10ms 38ms 128ms 0 transport_latency_assumed tick_size_change e 1,224 64 41ms 45ms 94ms 166ms 0 transport_latency_assumed tick_size_change f 1,224 2 47ms 52ms 98ms 207ms 0 transport_latency_assumed tick_size_change g 1,224 not meas. 83ms 105ms 262ms 422ms 0 transport_latency_assumed tick_size_change h 1,224 326 17ms 37ms 141ms 267ms 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/06/2026-09-12T06.parquet sha256sum 2026-09-12T06.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.