Hour audit: 2026-09-29T01
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-29T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T01:00:00.000000719+00:00 · last event 2026-09-29T01:59:59.999761064+00:00
VOLUME 107,311,662 rows · 1,123,099,477 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 107,216,614 · k: 107,212,957 · c: 107,199,938 · i: 107,184,321 · g: 106,923,794 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,337,615 (2.18%) · k: 7,456,908 (6.95%) · c: 96,520,987 (89.94%) · i: 964,931 (0.90%) · g: 31,221 (0.03%) (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 107,311,662 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 75e2c979b632633eaea8a0dea9fdd13c1ca4fac200dbe96732d4d070d9f2eb85
the corpus checksum ledger names this file with the same digest
joined 107,314,037 to merged 107,311,662, minus 2,375 (minus 0.0022%)
boundary drops 2,375 · 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-29T04:08:19Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,145,347 127,165,535 0-42 d4c4072815181982f102eae0c3badfc32b20d498995cbf63a190d0cb2b60eb08 book 194,189 18,062,713 43-43 42f03882c74dc041d947a680a69ad586db1554d4bbccad503a46d4b89a984c09 last_trade_price 74,560 4,001,634 44-44 5a37ca20843f80ebdbd39799cdc43a3ce84365c30b62afed347170fe1be635a0 market_resolved 616 97,859 45-45 2d5e2e5331215f8999a6ae6d56786c41c56353dddd948fdf190ba673bb66063e new_market 1,445 147,145 46-46 bdabe321b282c954032a434edc6e64958f7e16a14440ddcd666215f88cf85905 price_change 95,892,481 972,290,527 47-412 076a49595c67f3e908c85f5a776ad5b3a61a0644c5447b4b7ec74b6588002597 tick_size_change 3,024 112,406 413-413 82f30c389b6d80d478b9a78f49d3d3be96bbe593f34f413eb9f11d17bd1f69e6 EVENT MIX count share price_change 95,892,481 89.36% best_bid_ask 11,145,347 10.39% book 194,189 0.18% last_trade_price 74,560 0.07% tick_size_change 3,024 <0.01% new_market 1,445 <0.01% market_resolved 616 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,145,606 11,145,347 259 140 FULL book 194,193 194,189 4 17,012 FULL last_trade_price 74,560 74,560 0 0 FULL market_resolved 616 616 0 0 FULL new_market 1,445 1,445 0 0 FULL price_change 95,894,593 95,892,481 2,112 149 FULL tick_size_change 3,024 3,024 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,143,838 10,151,155 4ms 15ms 133ms 5.2s 0 transport_latency_assumed best_bid_ask g 11,132,892 2,419 82ms 107ms 514ms 23.9s 0 transport_latency_assumed best_bid_ask h 11,143,556 221,043 18ms 28ms 175ms 37.4s 0 transport_latency_assumed best_bid_ask i 11,143,357 93,432 24ms 35ms 146ms 6.0s 0 transport_latency_assumed best_bid_ask k 11,144,348 677,298 13ms 25ms 165ms 56.5s 0 transport_latency_assumed book c 160,786 141,380 7ms 88ms 1.5d 103.6d 0 book_staleness book g 149,273 6,919 104ms 5.4s 15.0h 120.5d 0 book_staleness book h 167,356 19,796 22ms 2.9s 1.9d 122.1d 0 book_staleness book i 156,058 6,057 26ms 113ms 14.1h 103.6d 0 book_staleness book k 158,189 20,037 16ms 71ms 20.3h 103.6d 0 book_staleness last_trade_price c 74,153 65,308 6ms 24ms 249ms 2.4s 0 transport_latency_assumed last_trade_price g 70,148 10 104ms 3.5s 15.2s 23.9s 0 transport_latency_assumed last_trade_price h 74,320 1,726 20ms 46ms 269ms 9.4s 0 transport_latency_assumed last_trade_price i 74,091 690 25ms 71ms 340ms 3.6s 0 transport_latency_assumed last_trade_price k 74,429 6,826 15ms 36ms 210ms 5.1s 0 transport_latency_assumed market_resolved c 598 566 5ms 11ms 115ms 41.7s 0 transport_latency_assumed market_resolved g 598 not meas. 83ms 220ms 577ms 50.6s 0 transport_latency_assumed market_resolved h 598 5 19ms 48ms 203ms 40.1s 0 transport_latency_assumed market_resolved i 598 19 29ms 76ms 49.7s 55.4s 0 transport_latency_assumed market_resolved k 598 26 14ms 32ms 82ms 45.5s 0 transport_latency_assumed new_market c 957 472 118ms 46.0s 2.7min 2.9min 0 transport_latency_assumed new_market g 957 103 301ms 33.2s 1.6min 2.3min 0 transport_latency_assumed new_market h 957 418 153ms 43.5s 2.8min 2.9min 0 transport_latency_assumed new_market i 957 255 142ms 34.9s 1.9min 2.7min 0 transport_latency_assumed new_market k 957 197 208ms 41.6s 2.4min 2.7min 0 transport_latency_assumed price_change c 95,816,582 86,159,590 5ms 19ms 151ms 5.5s 0 transport_latency_assumed price_change g 95,566,902 21,766 83ms 139ms 3.0s 23.9s 0 transport_latency_assumed price_change h 95,826,803 2,094,525 19ms 33ms 221ms 37.4s 0 transport_latency_assumed price_change i 95,806,236 864,398 25ms 42ms 220ms 6.5s 0 transport_latency_assumed price_change k 95,831,412 6,752,202 14ms 28ms 175ms 1.0min 0 transport_latency_assumed tick_size_change c 3,024 2,516 5ms 45ms 479ms 1.6s 0 transport_latency_assumed tick_size_change g 3,024 4 83ms 227ms 859ms 1.2s 0 transport_latency_assumed tick_size_change h 3,024 102 19ms 51ms 532ms 3.0s 0 transport_latency_assumed tick_size_change i 3,024 80 26ms 54ms 568ms 2.4s 0 transport_latency_assumed tick_size_change k 3,024 322 14ms 41ms 731ms 56.7s 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-29/01/2026-09-29T01.parquet sha256sum 2026-09-29T01.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.