Hour audit: 2026-10-04T03
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-04T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T03:00:00.000068816+00:00 · last event 2026-10-04T03:59:59.998596036+00:00
VOLUME 111,547,937 rows · 1,201,014,740 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 110,899,489 · m: 110,876,996 · h: 110,866,509 · k: 106,081,812 · g: 105,484,048 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 257,214 (0.23%) · m: 105,582,570 (94.65%) · h: 1,010,689 (0.91%) · k: 4,525,469 (4.06%) · g: 171,995 (0.15%) (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 111,547,937 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 bc609183bb22c5d86498cb0ef68d770474a2e50538186f7a5134d80eb4848596
the corpus checksum ledger names this file with the same digest
joined 111,552,227 to merged 111,547,937, minus 4,290 (minus 0.0038%)
boundary drops 4,290 · 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-04T05:55:08Z 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 10,141,347 115,493,485 0-38 f7327b2dcec187a9f6570a6ff5ede0e08a1e60873271f64a3458ff545fb8267e book 722,385 65,329,124 39-41 6a38713c91553177694812fb3eb925c37d3cbbfe7d1a0ee34711f158df736731 last_trade_price 45,513 2,627,247 42-42 e530372a8c9f50bb691492b3e4028f48bb81f55ed4bb1708d875691b5f11dfd2 market_resolved 3,870 525,003 43-43 6c068f79cc11a58bcedb1269e67521ff9df2b33a752dfae0b7a4433af2bf4e15 new_market 290 34,425 44-44 4e0facdb8fb5bfcbdca5247dce5cc2381ebd577a8c7d70e332ad2f7e48cd236d price_change 100,629,524 1,015,551,678 45-428 add2e06869c337acdb015e12bb34d4c526eae3d54204da7307f943aab44af392 tick_size_change 5,008 183,342 429-429 c746a1876f6c793001d95a4e1afa8e21d18e9fcd23c0b042576226cb8b5055ad EVENT MIX count share price_change 100,629,524 90.21% best_bid_ask 10,141,347 9.09% book 722,385 0.65% last_trade_price 45,513 0.04% tick_size_change 5,008 <0.01% market_resolved 3,870 <0.01% new_market 290 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,141,644 10,141,347 297 1,237 FULL book 724,149 722,385 1,764 225,375 FULL last_trade_price 45,516 45,513 3 144 FULL market_resolved 3,870 3,870 0 51 FULL new_market 292 290 2 8 FULL price_change 100,631,748 100,629,524 2,224 945 FULL tick_size_change 5,008 5,008 0 171 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,613,051 142 78ms 93ms 187ms 5.7s 0 transport_latency_assumed best_bid_ask h 10,140,483 86,865 17ms 23ms 65ms 39.5s 0 transport_latency_assumed best_bid_ask i 10,140,242 19,526 22ms 27ms 60ms 5.9s 0 transport_latency_assumed best_bid_ask k 9,669,542 368,652 13ms 21ms 55ms 1.0s 0 transport_latency_assumed best_bid_ask m 10,140,507 9,666,162 4ms 10ms 40ms 1.2s 0 transport_latency_assumed book g 546,504 168,949 28.7min 2.1d 42.6d 127.2d 0 book_staleness book h 92,100 1,715 21ms 36ms 657ms 108.7d 0 book_staleness book i 93,233 1,375 24ms 43ms 2.3h 108.7d 0 book_staleness book k 547,484 463,148 38.8min 2.1d 42.5d 127.2d 0 book_staleness book m 97,968 87,198 6ms 38ms 1.3d 127.2d 0 book_staleness last_trade_price g 41,233 7 81ms 157ms 462ms 1.8s 0 transport_latency_assumed last_trade_price h 45,456 607 19ms 30ms 191ms 4.1s 0 transport_latency_assumed last_trade_price i 45,404 227 23ms 35ms 182ms 1.7s 0 transport_latency_assumed last_trade_price k 43,452 2,504 14ms 25ms 128ms 1.4s 0 transport_latency_assumed last_trade_price m 45,397 42,168 6ms 14ms 111ms 1.7s 0 transport_latency_assumed market_resolved g 3,175 120 81ms 23.6s 5.3min 5.7min 0 transport_latency_assumed market_resolved h 3,186 32 20ms 151ms 50.7s 56.4s 0 transport_latency_assumed market_resolved i 3,186 64 24ms 69ms 53.0s 54.6s 0 transport_latency_assumed market_resolved k 3,327 571 15ms 53.6s 8.7min 10.8min 0 transport_latency_assumed market_resolved m 3,186 3,083 6ms 14.7s 49.1s 56.3s 0 transport_latency_assumed new_market g 214 13 100ms 540ms 13.4s 1.4min 0 transport_latency_assumed new_market h 214 32 42ms 9.2s 1.3min 1.5min 0 transport_latency_assumed new_market i 214 34 48ms 7.9s 28.0s 1.6min 0 transport_latency_assumed new_market k 224 48 55ms 11.9s 6.4min 7.1min 0 transport_latency_assumed new_market m 214 163 23ms 10.7s 1.4min 1.7min 0 transport_latency_assumed price_change g 95,275,147 2,764 78ms 95ms 286ms 6.0s 0 transport_latency_assumed price_change h 100,580,062 921,414 18ms 24ms 79ms 39.6s 0 transport_latency_assumed price_change i 100,612,202 235,986 22ms 28ms 81ms 6.4s 0 transport_latency_assumed price_change k 95,813,175 3,690,352 13ms 22ms 64ms 1.1s 0 transport_latency_assumed price_change m 100,584,716 95,779,008 5ms 10ms 43ms 1.8s 0 transport_latency_assumed tick_size_change g 4,724 not meas. 78ms 92ms 215ms 3.2s 0 transport_latency_assumed tick_size_change h 5,008 24 18ms 23ms 56ms 125ms 0 transport_latency_assumed tick_size_change i 5,008 2 22ms 27ms 54ms 215ms 0 transport_latency_assumed tick_size_change k 4,608 194 13ms 21ms 44ms 99ms 0 transport_latency_assumed tick_size_change m 5,008 4,788 5ms 9ms 29ms 209ms 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-04/03/2026-10-04T03.parquet sha256sum 2026-10-04T03.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.