Hour audit: 2026-09-17T13
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-17T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T13:00:00.000081740+00:00 · last event 2026-09-17T13:59:59.999708572+00:00
VOLUME 121,664,511 rows · 1,302,745,450 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 120,310,978 · g: 119,776,392 · e: 119,636,727 · f: 115,858,334 · c: 112,365,353 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 13,409,304 (11.02%) · g: 213,822 (0.18%) · e: 544,319 (0.45%) · f: 787,627 (0.65%) · c: 106,709,439 (87.71%) (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 121,664,511 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e2cb9eefb771a849ca1338b2774727e85ceb5ddaf4a341df1c405ad9e575895b
the corpus checksum ledger names this file with the same digest
joined 121,669,791 to merged 121,664,511, minus 5,280 (minus 0.0043%)
boundary drops 5,280 · 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-17T15:00:50Z 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 12,555,178 143,314,250 0-47 f14b78d8bf37044e27ca57bc45148738299c86b5812b176ec5938a277e6286d1 book 1,525,828 89,241,662 48-53 5f935fc170b564ef46762c0fbc42452e117aed746fedb55625c2c999ed3d20ee last_trade_price 60,457 3,457,522 54-54 680cfab9e4c6b4fd7f0a17dc557d7be0ac6d8d0cf237fb85a2f48fad21219779 market_resolved 717 114,527 55-55 0f06c0856217b9597ef7a6305d7bf6fe6867578cc097860d44b027a7ef3a3c82 new_market 813 82,781 56-56 bd16aaaef41916a31e52761cad6a5497d567a8b591e2279bafae393459ffd70f price_change 107,517,866 1,065,017,519 57-467 9e390ed1cf22e8cd317528a6351486f35bb36cb4880512839b23a57fff062752 tick_size_change 3,652 134,076 468-468 808386bdb724380fb0ce50ecb169ed20290d0176c88285c5882f0d42e01cdec6 EVENT MIX count share price_change 107,517,866 88.37% best_bid_ask 12,555,178 10.32% book 1,525,828 1.25% last_trade_price 60,457 0.05% tick_size_change 3,652 <0.01% new_market 813 <0.01% market_resolved 717 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,555,422 12,555,178 244 849 FULL book 1,528,806 1,525,828 2,978 168,059 FULL last_trade_price 60,457 60,457 0 134 FULL market_resolved 717 717 0 31 FULL new_market 813 813 0 0 FULL price_change 107,519,924 107,517,866 2,058 94 FULL tick_size_change 3,652 3,652 0 84 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,616,566 11,096,159 6ms 12ms 75ms 3.9s 0 transport_latency_assumed best_bid_ask e 12,530,527 49,908 43ms 51ms 174ms 14.0s 0 transport_latency_assumed best_bid_ask f 11,990,541 14,130 47ms 59ms 198ms 13.8s 0 transport_latency_assumed best_bid_ask g 12,532,640 1,509 78ms 97ms 301ms 26.3s 0 transport_latency_assumed best_bid_ask h 12,551,126 1,393,472 19ms 28ms 99ms 7.9s 0 transport_latency_assumed book c 935,789 587,953 3.4min 2.1d 36.8d 110.7d 0 book_staleness book e 193,488 40,849 120ms 20.4min 24.0d 110.6d 0 book_staleness book f 934,219 622,043 3.3min 1.9d 36.8d 110.6d 0 book_staleness book g 338,570 183,827 37.6s 1.0h 26.0d 110.6d 0 book_staleness book h 258,478 91,156 2.5s 30.1min 26.0d 110.6d 0 book_staleness last_trade_price c 56,578 53,632 12ms 47ms 216ms 5.0s 0 transport_latency_assumed last_trade_price e 58,449 320 55ms 405ms 5.2s 14.0s 0 transport_latency_assumed last_trade_price f 57,911 213 63ms 540ms 6.8s 11.8s 0 transport_latency_assumed last_trade_price g 58,494 21 98ms 1.3s 15.4s 26.3s 0 transport_latency_assumed last_trade_price h 60,103 6,271 25ms 85ms 474ms 5.8s 0 transport_latency_assumed market_resolved c 686 653 6ms 18ms 5.2min 5.4min 0 transport_latency_assumed market_resolved e 700 2 115ms 281ms 579ms 959ms 0 transport_latency_assumed market_resolved f 689 15 117ms 210ms 4.6min 4.6min 0 transport_latency_assumed market_resolved g 699 1 194ms 351ms 727ms 1.0s 0 transport_latency_assumed market_resolved h 700 46 37ms 85ms 191ms 547ms 0 transport_latency_assumed new_market c 542 327 93ms 23.7s 5.2min 5.2min 0 transport_latency_assumed new_market e 525 102 160ms 474ms 24.9s 1.3min 0 transport_latency_assumed new_market f 525 66 213ms 19.9s 4.7min 4.7min 0 transport_latency_assumed new_market g 525 100 270ms 19.7s 24.3s 56.2s 0 transport_latency_assumed new_market h 525 218 100ms 17.3s 26.4s 1.6min 0 transport_latency_assumed price_change c 99,751,708 94,967,386 6ms 14ms 88ms 4.3s 0 transport_latency_assumed price_change e 106,849,386 453,130 43ms 62ms 1.2s 14.0s 0 transport_latency_assumed price_change f 102,871,017 151,160 48ms 72ms 1.2s 13.8s 0 transport_latency_assumed price_change g 106,841,816 28,364 78ms 115ms 3.0s 26.3s 0 transport_latency_assumed price_change h 107,436,394 11,917,826 19ms 32ms 166ms 8.2s 0 transport_latency_assumed tick_size_change c 3,484 3,329 6ms 13ms 52ms 100ms 0 transport_latency_assumed tick_size_change e 3,652 8 43ms 56ms 123ms 248ms 0 transport_latency_assumed tick_size_change f 3,432 not meas. 47ms 59ms 121ms 249ms 0 transport_latency_assumed tick_size_change g 3,648 not meas. 78ms 96ms 179ms 882ms 0 transport_latency_assumed tick_size_change h 3,652 315 19ms 28ms 62ms 286ms 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-17/13/2026-09-17T13.parquet sha256sum 2026-09-17T13.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.