Hour audit: 2026-09-08T07
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-08T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T07:00:00.000051554+00:00 · last event 2026-09-08T07:59:59.999989277+00:00
VOLUME 93,046,184 rows · 955,605,709 bytes (911.34 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 92,605,355 · h: 92,601,634 · c: 92,599,725 · f: 92,599,247 · g: 92,347,586 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 374,809 (0.40%) · h: 2,810,715 (3.02%) · c: 89,598,533 (96.29%) · f: 247,152 (0.27%) · g: 14,975 (0.02%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 93,046,184 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2562c0a66fd8183df8873906cc3903f33a2c91469b387e4e737dc1cd962e5b8c
the corpus checksum ledger names this file with the same digest
joined 93,049,463 to merged 93,046,184, minus 3,279 (minus 0.0035%)
boundary drops 3,279 · 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-08T08:54:48Z 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 9,082,012 98,089,397 0-34 3d8f209d75cac87e927da5e17ee1e6f4d3b01b0340b78d54d23e3cd6450af862 book 763,933 65,698,706 35-37 96d0fb78aee240b32e7e513f65f99378d252039ae416b079cda311e498780a98 last_trade_price 56,668 3,170,573 38-38 3f6ccf5ffa0d06a51c2ae10df14723f6a79771aaaa0e5b03d74d2ba265372701 market_resolved 520 86,647 39-39 670402e3468048880f970dc12a17fc40e7cfd59b00687bca4498610b5610449b new_market 657 74,704 40-40 b3cb557759a048953dee096637b8f8fec3edf3a2af9ebf76671132776ae06c6a price_change 83,140,674 787,360,638 41-358 e69a5508b163204d55bde0ad45205098fcdf841dbdc87f4774d1ebb446fd3d05 tick_size_change 1,720 62,420 359-359 151cab5210a1ee231feeb20c9e1af7ef230ea993fec9a965e9486090324485c8 EVENT MIX count share price_change 83,140,674 89.35% best_bid_ask 9,082,012 9.76% book 763,933 0.82% last_trade_price 56,668 0.06% tick_size_change 1,720 <0.01% new_market 657 <0.01% market_resolved 520 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,082,162 9,082,012 150 115 FULL book 763,941 763,933 8 173,728 FULL last_trade_price 56,669 56,668 1 1 FULL market_resolved 520 520 0 0 FULL new_market 657 657 0 0 FULL price_change 83,143,794 83,140,674 3,120 258 FULL tick_size_change 1,720 1,720 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,080,762 8,806,752 4ms 8ms 67ms 5.3s 0 transport_latency_assumed best_bid_ask e 9,078,971 18,499 37ms 41ms 117ms 2.4s 0 transport_latency_assumed best_bid_ask f 9,078,704 4,814 47ms 51ms 132ms 2.5s 0 transport_latency_assumed best_bid_ask g 9,080,164 729 79ms 99ms 268ms 10.5s 0 transport_latency_assumed best_bid_ask h 9,080,393 251,218 16ms 19ms 83ms 42.1s 0 transport_latency_assumed book c 344,199 252,153 1.8min 13.8h 26.7d 101.4d 0 book_staleness book e 394,485 175,731 3.3min 15.9h 27.5d 101.4d 0 book_staleness book f 407,128 187,755 3.7min 16.5h 27.5d 101.4d 0 book_staleness book g 127,108 7,263 86ms 437ms 19.9h 82.9d 0 book_staleness book h 349,186 141,031 2.0min 13.2h 26.7d 101.4d 0 book_staleness last_trade_price c 56,628 54,371 9ms 36ms 194ms 5.0s 0 transport_latency_assumed last_trade_price e 56,557 172 43ms 93ms 527ms 5.0s 0 transport_latency_assumed last_trade_price f 56,561 106 53ms 98ms 387ms 5.0s 0 transport_latency_assumed last_trade_price g 56,609 13 91ms 168ms 651ms 8.1s 0 transport_latency_assumed last_trade_price h 56,622 2,006 20ms 53ms 287ms 7.0s 0 transport_latency_assumed market_resolved c 520 490 5ms 11ms 49.6s 1.3min 0 transport_latency_assumed market_resolved e 520 8 38ms 187ms 46.3s 1.3min 0 transport_latency_assumed market_resolved f 520 not meas. 48ms 200ms 46.3s 1.3min 0 transport_latency_assumed market_resolved g 520 not meas. 83ms 342ms 52.9s 1.4min 0 transport_latency_assumed market_resolved h 520 22 16ms 84ms 59.4s 1.5min 0 transport_latency_assumed new_market c 487 211 88ms 641ms 26.3s 1.1min 0 transport_latency_assumed new_market e 487 123 157ms 384ms 31.8s 1.1min 0 transport_latency_assumed new_market f 487 43 180ms 13.2s 21.2s 1.0min 0 transport_latency_assumed new_market g 487 60 311ms 17.9s 29.7s 1.2min 0 transport_latency_assumed new_market h 487 220 120ms 19.3s 53.4s 1.3min 0 transport_latency_assumed price_change c 83,115,409 80,482,866 5ms 9ms 74ms 5.5s 0 transport_latency_assumed price_change e 83,072,615 180,276 37ms 42ms 167ms 3.7s 0 transport_latency_assumed price_change f 83,054,127 54,434 47ms 53ms 168ms 4.8s 0 transport_latency_assumed price_change g 83,080,978 6,910 80ms 100ms 340ms 11.5s 0 transport_latency_assumed price_change h 83,112,706 2,416,188 16ms 20ms 103ms 42.1s 0 transport_latency_assumed tick_size_change c 1,720 1,690 5ms 7ms 20ms 39ms 0 transport_latency_assumed tick_size_change e 1,720 not meas. 37ms 40ms 54ms 104ms 0 transport_latency_assumed tick_size_change f 1,720 not meas. 47ms 50ms 112ms 134ms 0 transport_latency_assumed tick_size_change g 1,720 not meas. 79ms 93ms 115ms 223ms 0 transport_latency_assumed tick_size_change h 1,720 30 16ms 18ms 65ms 75ms 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/07/2026-09-08T07.parquet sha256sum 2026-09-08T07.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.