Hour audit: 2026-10-03T06
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-10-03T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T06:00:00.000075705+00:00 · last event 2026-10-03T06:59:59.999954424+00:00
VOLUME 92,461,075 rows · 949,247,346 bytes (905.27 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 92,395,610 · h: 92,364,471 · i: 92,359,051 · m: 92,354,845 · g: 92,340,510 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 2,686,941 (2.91%) · h: 583,223 (0.63%) · i: 346,840 (0.38%) · m: 88,816,523 (96.06%) · g: 27,548 (0.03%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 92,461,075 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ec43df7ec78e59209b39c502430f6a83cdaead0746987cf31b3ae5c1e4149b36
the corpus checksum ledger names this file with the same digest
joined 92,463,037 to merged 92,461,075, minus 1,962 (minus 0.0021%)
boundary drops 1,962 · 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-10-03T08:41:16Z as ghikm
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 9,532,910 110,084,391 0-36 0fb959069a6099f701b149a210bbbea0298638aacd2e6d1656921575c5a2cc7f book 148,299 14,263,409 37-37 faf49590ba9d09e8d0bbeb86e446850183718ed6f2bc5ff338c6e21009a082d0 last_trade_price 56,639 3,125,155 38-38 a137734d30725286cc30e8632cec2b0417697796cb3f24919856155a0d919f42 market_resolved 1,189 177,551 39-39 6b2e5ba399a8e4e44b61b354543be4754c71ff94eb0d8251a3339ab83a997b0b new_market 472 50,591 40-40 2aafdd08dac7f8a7e4b30d988346415995cc046017f0692e7f3fa68ccb5826ae price_change 82,719,466 820,410,544 41-356 246beed8feae2de8a81252bcdd257dcdbcb97fb5fd57662b001914e4202c5d2a tick_size_change 2,100 77,916 357-357 8558889bfc3c2565de1e37cafb4c2eb597747ac93087ecb109505a4837b0e956 EVENT MIX count share price_change 82,719,466 89.46% best_bid_ask 9,532,910 10.31% book 148,299 0.16% last_trade_price 56,639 0.06% tick_size_change 2,100 <0.01% market_resolved 1,189 <0.01% new_market 472 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,533,120 9,532,910 210 72 FULL book 148,299 148,299 0 14,841 FULL last_trade_price 56,639 56,639 0 0 FULL market_resolved 1,189 1,189 0 0 FULL new_market 472 472 0 0 FULL price_change 82,721,218 82,719,466 1,752 276 FULL tick_size_change 2,100 2,100 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,531,159 288 76ms 93ms 242ms 12.0s 0 transport_latency_assumed best_bid_ask h 9,531,363 51,494 17ms 22ms 81ms 44.7s 0 transport_latency_assumed best_bid_ask i 9,531,942 28,518 19ms 24ms 65ms 7.9s 0 transport_latency_assumed best_bid_ask k 9,532,178 264,058 13ms 18ms 60ms 17.5s 0 transport_latency_assumed best_bid_ask m 9,531,937 9,188,552 4ms 8ms 43ms 5.5s 0 transport_latency_assumed book g 137,227 23,830 87ms 25.1min 16.7d 107.8d 0 book_staleness book h 117,108 5,276 20ms 45ms 5.4h 107.7d 0 book_staleness book i 115,646 2,858 21ms 52ms 25.2min 107.7d 0 book_staleness book k 115,866 6,711 15ms 31ms 42.6min 107.7d 0 book_staleness book m 116,160 109,624 6ms 15ms 24.1min 2.4d 0 book_staleness last_trade_price g 56,464 1 80ms 364ms 6.7s 12.0s 0 transport_latency_assumed last_trade_price h 56,356 628 18ms 29ms 209ms 7.8s 0 transport_latency_assumed last_trade_price i 56,491 305 20ms 36ms 264ms 1.6s 0 transport_latency_assumed last_trade_price k 56,498 2,452 14ms 24ms 167ms 4.2s 0 transport_latency_assumed last_trade_price m 56,514 53,253 5ms 12ms 129ms 1.7s 0 transport_latency_assumed market_resolved g 1,109 83 80ms 28.6s 52.4s 52.5s 0 transport_latency_assumed market_resolved h 1,109 9 19ms 31.8s 45.9s 55.3s 0 transport_latency_assumed market_resolved i 1,109 7 20ms 27.1s 57.1s 57.2s 0 transport_latency_assumed market_resolved k 1,109 75 14ms 33.9s 48.0s 48.0s 0 transport_latency_assumed market_resolved m 1,109 1,015 5ms 22.8s 52.9s 53.0s 0 transport_latency_assumed new_market g 333 58 246ms 31.7s 1.2min 1.4min 0 transport_latency_assumed new_market h 333 44 116ms 14.7s 33.4s 1.5min 0 transport_latency_assumed new_market i 333 76 56ms 16.7s 1.3min 1.8min 0 transport_latency_assumed new_market k 333 51 63ms 491ms 13.0s 1.8min 0 transport_latency_assumed new_market m 333 243 33ms 286ms 17.9s 1.5min 0 transport_latency_assumed price_change g 82,612,118 3,288 77ms 97ms 767ms 12.0s 0 transport_latency_assumed price_change h 82,656,102 525,772 17ms 23ms 134ms 50.2s 0 transport_latency_assumed price_change i 82,651,430 315,076 19ms 25ms 142ms 8.6s 0 transport_latency_assumed price_change k 82,687,526 2,413,582 13ms 20ms 84ms 21.8s 0 transport_latency_assumed price_change m 82,646,692 79,461,748 4ms 9ms 51ms 7.3s 0 transport_latency_assumed tick_size_change g 2,100 not meas. 76ms 89ms 101ms 196ms 0 transport_latency_assumed tick_size_change h 2,100 not meas. 17ms 21ms 28ms 45ms 0 transport_latency_assumed tick_size_change i 2,100 not meas. 19ms 22ms 33ms 47ms 0 transport_latency_assumed tick_size_change k 2,100 12 12ms 16ms 24ms 45ms 0 transport_latency_assumed tick_size_change m 2,100 2,088 4ms 7ms 10ms 26ms 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-10-03/06/2026-10-03T06.parquet sha256sum 2026-10-03T06.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.