Hour audit: 2026-09-14T05
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-14T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T05:00:00.000041433+00:00 · last event 2026-09-14T05:59:59.999830884+00:00
VOLUME 95,892,733 rows · 921,064,750 bytes (878.40 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 95,769,397 · e: 95,746,972 · c: 95,655,328 · g: 95,636,643 · h: 95,601,410 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 103,754 (0.11%) · e: 247,337 (0.26%) · c: 93,461,764 (97.46%) · g: 51,504 (0.05%) · h: 2,028,374 (2.12%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 95,892,733 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 51cfdcf51e5b29f71a7a0c16b888d99a6c250bbb89bd018b74442331f3fc82db
the corpus checksum ledger names this file with the same digest
joined 95,894,694 to merged 95,892,733, minus 1,961 (minus 0.0020%)
boundary drops 1,961 · 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-14T06:55:18Z 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 11,126,080 115,880,937 0-42 18bfdd25eaf87330bdff6eadd3bf7dfa3dbe55d39ec9264f11bc6926ab21589c book 213,504 22,984,479 43-43 22802adae95d23178a062434c54a8df2247bb64f5e60292d435d62aeacf63fc5 last_trade_price 40,326 2,287,200 44-44 8c8d888f6e29458820cce5164d985e463393c5f27a2a226a59e75db6594ffb2b market_resolved 850 131,714 45-45 ef3238b52187aa344ecf9a7555666db2583f7b599379a2c3cd53aaea4171f2c5 new_market 485 55,986 46-46 6d8a839f845085ad802a77edff45185e5451f54448d1e8c6bfab1fac7b5349f1 price_change 84,509,892 778,572,140 47-369 d43c53692d569dffffa07a7f4fee092a206261540ae9d97a55346b6c62585055 tick_size_change 1,596 58,251 370-370 0ed5ddb478d63c862b447d230dca03514978b44ea7cab45d14dfb1ff2bb9643c EVENT MIX count share price_change 84,509,892 88.13% best_bid_ask 11,126,080 11.60% book 213,504 0.22% last_trade_price 40,326 0.04% tick_size_change 1,596 <0.01% market_resolved 850 <0.01% new_market 485 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,126,280 11,126,080 200 155 FULL book 213,530 213,504 26 58,233 FULL last_trade_price 40,327 40,326 1 0 FULL market_resolved 850 850 0 0 FULL new_market 485 485 0 0 FULL price_change 84,511,626 84,509,892 1,734 207 FULL tick_size_change 1,596 1,596 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,125,740 10,901,527 4ms 7ms 44ms 6.0s 0 transport_latency_assumed best_bid_ask e 11,124,329 10,993 41ms 45ms 90ms 2.6s 0 transport_latency_assumed best_bid_ask f 11,124,100 5,063 46ms 50ms 99ms 2.4s 0 transport_latency_assumed best_bid_ask g 11,122,249 375 81ms 95ms 202ms 13.8s 0 transport_latency_assumed best_bid_ask h 11,124,766 208,122 17ms 20ms 63ms 6.8s 0 transport_latency_assumed book c 109,546 102,254 6ms 2.9h 8.6d 88.8d 0 book_staleness book e 104,173 17,370 44ms 1.1h 7.9d 107.3d 0 book_staleness book f 117,303 30,503 50ms 5.6h 14.3d 107.3d 0 book_staleness book g 134,917 47,479 96ms 9.3h 22.6d 107.3d 0 book_staleness book h 96,889 15,898 21ms 1.9min 4.9d 88.8d 0 book_staleness last_trade_price c 40,304 38,786 9ms 39ms 165ms 5.0s 0 transport_latency_assumed last_trade_price e 40,224 102 48ms 93ms 241ms 5.0s 0 transport_latency_assumed last_trade_price f 40,214 44 52ms 99ms 290ms 5.0s 0 transport_latency_assumed last_trade_price g 40,189 10 93ms 170ms 457ms 13.8s 0 transport_latency_assumed last_trade_price h 40,153 1,384 22ms 53ms 188ms 5.0s 0 transport_latency_assumed market_resolved c 814 779 5ms 11ms 59.3s 1.0min 0 transport_latency_assumed market_resolved e 814 1 44ms 191ms 58.1s 59.8s 0 transport_latency_assumed market_resolved f 814 1 48ms 196ms 57.5s 59.8s 0 transport_latency_assumed market_resolved g 814 not meas. 88ms 250ms 59.1s 1.1min 0 transport_latency_assumed market_resolved h 814 69 19ms 74ms 57.5s 59.6s 0 transport_latency_assumed new_market c 370 264 57ms 16.7s 23.5s 1.8min 0 transport_latency_assumed new_market e 370 41 126ms 17.4s 24.1s 57.7s 0 transport_latency_assumed new_market f 370 33 129ms 19.2s 34.5s 1.2min 0 transport_latency_assumed new_market g 370 10 225ms 14.5s 22.6s 55.8s 0 transport_latency_assumed new_market h 370 137 64ms 16.0s 23.2s 1.0min 0 transport_latency_assumed price_change c 84,376,958 82,416,586 4ms 7ms 55ms 6.0s 0 transport_latency_assumed price_change e 84,475,466 218,830 41ms 45ms 121ms 2.6s 0 transport_latency_assumed price_change f 84,485,000 68,110 47ms 51ms 130ms 2.4s 0 transport_latency_assumed price_change g 84,336,508 3,630 81ms 99ms 251ms 13.8s 0 transport_latency_assumed price_change h 84,336,822 1,802,736 18ms 21ms 77ms 6.9s 0 transport_latency_assumed tick_size_change c 1,596 1,568 4ms 8ms 50ms 68ms 0 transport_latency_assumed tick_size_change e 1,596 not meas. 41ms 46ms 75ms 103ms 0 transport_latency_assumed tick_size_change f 1,596 not meas. 47ms 51ms 97ms 164ms 0 transport_latency_assumed tick_size_change g 1,596 not meas. 82ms 109ms 281ms 321ms 0 transport_latency_assumed tick_size_change h 1,596 28 18ms 23ms 73ms 652ms 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-14/05/2026-09-14T05.parquet sha256sum 2026-09-14T05.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.