Hour audit: 2026-09-30T04
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-30T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T04:00:00.000098274+00:00 · last event 2026-09-30T04:59:59.999955345+00:00
VOLUME 104,538,448 rows · 1,116,815,587 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 102,480,038 · h: 102,410,805 · m: 102,400,190 · i: 102,230,200 · g: 102,201,299 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 2,651,403 (2.54%) · h: 993,095 (0.95%) · m: 98,144,378 (93.88%) · i: 2,554,644 (2.44%) · g: 194,928 (0.19%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 2e4e293e47f602233a5b4507f81f7860fbb6fae0bd075110d5fba49ffce61588
the corpus checksum ledger names this file with the same digest
joined 104,541,493 to merged 104,538,448, minus 3,045 (minus 0.0029%)
boundary drops 3,045 · 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-30T15:32:43Z 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,745,075 111,705,714 0-37 b6442f3beebb4de3ed251299cf3f4304065eaf2f82ae3d699027e824cf422224 book 2,251,505 91,866,356 38-46 ad052c79db74a126f6d0fa0976a81c2429283c0967c9d44688eb19b3a0640d47 last_trade_price 45,190 2,573,227 47-47 a4073a4eddc69fa9e67f10ca7ebeeea826556224a99b14dc096222a6bcdef860 market_resolved 828 135,008 48-48 c9ac1b5e420f86b17100455011bc933be9c6b7c9d011dc1f3c6dacbdac9074d6 new_market 3,018 286,100 49-49 d91647c4f88933d1c8053ac95e3b11db1b8275351460f2377b3ba0f1c78b72fd price_change 92,487,940 908,873,619 50-402 ea3f7bab6646e1a34ad73eaf8ba1ed900716f1327958ad8c2ca03b2fa8ce14e1 tick_size_change 4,892 181,725 403-403 3d0708e89322b14c2a4c5707d46ed16cab3908790ac7e02991ee344e71cb2df1 EVENT MIX count share price_change 92,487,940 88.47% best_bid_ask 9,745,075 9.32% book 2,251,505 2.15% last_trade_price 45,190 0.04% tick_size_change 4,892 <0.01% new_market 3,018 <0.01% market_resolved 828 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,745,261 9,745,075 186 361 FULL book 2,252,409 2,251,505 904 226,254 FULL last_trade_price 45,191 45,190 1 31 FULL market_resolved 828 828 0 0 FULL new_market 3,018 3,018 0 0 FULL price_change 92,489,894 92,487,940 1,954 194 FULL tick_size_change 4,892 4,892 0 19 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,735,705 2,928 79ms 121ms 915ms 38.5s 0 transport_latency_assumed best_bid_ask h 9,739,983 81,557 18ms 29ms 852ms 1.4min 0 transport_latency_assumed best_bid_ask i 9,556,172 61,854 21ms 36ms 371ms 25.0s 0 transport_latency_assumed best_bid_ask k 9,741,466 229,195 13ms 26ms 470ms 1.1min 0 transport_latency_assumed best_bid_ask m 9,741,203 9,369,541 4ms 9ms 196ms 20.8s 0 transport_latency_assumed book g 349,096 160,237 11.1min 1.8d 38.6d 123.3d 0 book_staleness book h 228,227 60,229 43.7s 1.4d 38.6d 123.3d 0 book_staleness book i 2,054,259 1,806,305 2.3h 3.0d 42.5d 123.3d 0 book_staleness book k 271,766 82,154 2.6min 1.6d 38.6d 123.3d 0 book_staleness book m 204,668 142,580 16.0s 1.2d 38.6d 123.3d 0 book_staleness last_trade_price g 44,227 32 83ms 333ms 7.1s 30.3s 0 transport_latency_assumed last_trade_price h 44,844 533 19ms 66ms 1.3s 33.7s 0 transport_latency_assumed last_trade_price i 44,092 480 23ms 73ms 771ms 7.7s 0 transport_latency_assumed last_trade_price k 44,969 1,404 14ms 48ms 627ms 53.4s 0 transport_latency_assumed last_trade_price m 45,041 42,741 5ms 12ms 378ms 3.4s 0 transport_latency_assumed market_resolved g 801 34 80ms 353ms 17.9s 1.3min 0 transport_latency_assumed market_resolved h 801 9 18ms 67ms 28.5s 28.6s 0 transport_latency_assumed market_resolved i 801 27 21ms 124ms 50.1s 50.1s 0 transport_latency_assumed market_resolved k 801 10 14ms 54ms 22.4s 1.4min 0 transport_latency_assumed market_resolved m 801 748 5ms 11ms 25.6s 56.8s 0 transport_latency_assumed new_market g 1,850 279 453ms 19.4s 40.1s 1.6min 0 transport_latency_assumed new_market h 1,850 501 275ms 23.4s 35.9s 1.6min 0 transport_latency_assumed new_market i 1,850 492 272ms 21.2s 55.0s 1.4min 0 transport_latency_assumed new_market k 1,850 438 322ms 19.6s 49.2s 1.6min 0 transport_latency_assumed new_market m 1,850 1,308 162ms 19.5s 59.7s 1.7min 0 transport_latency_assumed price_change g 92,064,736 31,414 79ms 162ms 1.9s 39.7s 0 transport_latency_assumed price_change h 92,390,208 850,223 18ms 36ms 927ms 1.5min 0 transport_latency_assumed price_change i 90,568,154 685,430 21ms 40ms 453ms 27.4s 0 transport_latency_assumed price_change k 92,414,294 2,338,024 13ms 31ms 489ms 1.1min 0 transport_latency_assumed price_change m 92,401,783 88,582,849 4ms 10ms 220ms 21.6s 0 transport_latency_assumed tick_size_change g 4,884 4 80ms 362ms 1.1s 1.6s 0 transport_latency_assumed tick_size_change h 4,892 43 18ms 94ms 4.0s 11.5s 0 transport_latency_assumed tick_size_change i 4,872 56 21ms 68ms 1.1s 3.1s 0 transport_latency_assumed tick_size_change k 4,892 178 13ms 113ms 1.1s 3.8s 0 transport_latency_assumed tick_size_change m 4,844 4,611 4ms 11ms 381ms 559ms 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-30/04/2026-09-30T04.parquet sha256sum 2026-09-30T04.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.