Hour audit: 2026-10-02T10
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-02T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T10:00:00.000170472+00:00 · last event 2026-10-02T10:59:59.999945633+00:00
VOLUME 113,316,235 rows · 1,194,715,060 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 113,209,718 · h: 113,192,902 · k: 113,177,106 · m: 113,172,413 · g: 112,802,366 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 377,964 (0.33%) · h: 1,122,131 (0.99%) · k: 6,181,915 (5.46%) · m: 105,547,370 (93.14%) · g: 86,855 (0.08%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 113,316,235 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a80fc464b0dcd0f73f4f01cbdb868f8d4b11b4feab86732ef8205f0fcd989802
the corpus checksum ledger names this file with the same digest
joined 113,317,817 to merged 113,316,235, minus 1,582 (minus 0.0014%)
boundary drops 1,582 · 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-02T12:45:31Z 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,683,376 127,525,386 0-40 b8ed782c9726aea8958555e32e83c0adc139e6ebc253debbd307502699080b41 book 198,292 21,358,676 41-41 0aaee77e953e0f0f5e732b14463be017e9200848a6f386754e570c544b5da536 last_trade_price 51,385 2,945,313 42-42 7b21c81e04b17b87f9b2e31b6075279b6bedb231e186cfcb47338a8eea142020 market_resolved 699 104,835 43-43 e001b244c1374a31c1b6279400816bc8b603f4f6a3e25b51e29e87a40c0e12ea new_market 1,569 150,626 44-44 64033ee457b34bbb267498084c92b1f6623209e87b6ba8dbc2bc765b3cbe62fe price_change 102,376,434 1,041,173,932 45-435 26f44c0c931d49ab885448133c3a10af90eb01c94d4bf1484cb1eef6719b19a5 tick_size_change 4,480 165,327 436-436 22ab3639cbcf3597c052205fd13f726135a07083263ab9c17e51be9f383f2fc9 EVENT MIX count share price_change 102,376,434 90.35% best_bid_ask 10,683,376 9.43% book 198,292 0.17% last_trade_price 51,385 0.05% tick_size_change 4,480 <0.01% new_market 1,569 <0.01% market_resolved 699 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,683,544 10,683,376 168 170 FULL book 198,296 198,292 4 40,682 FULL last_trade_price 51,385 51,385 0 1 FULL market_resolved 699 699 0 0 FULL new_market 1,569 1,569 0 0 FULL price_change 102,377,844 102,376,434 1,410 160 FULL tick_size_change 4,480 4,480 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,677,306 850 77ms 113ms 652ms 34.2s 0 transport_latency_assumed best_bid_ask h 10,681,004 97,920 19ms 33ms 299ms 1.5min 0 transport_latency_assumed best_bid_ask i 10,682,090 31,956 23ms 42ms 232ms 33.2s 0 transport_latency_assumed best_bid_ask k 10,682,066 526,399 12ms 24ms 231ms 1.2min 0 transport_latency_assumed best_bid_ask m 10,682,920 10,026,251 5ms 10ms 125ms 7.0s 0 transport_latency_assumed book g 179,835 76,840 1.0s 9.2h 29.7d 125.5d 0 book_staleness book h 108,261 5,357 24ms 196ms 9.7h 107.0d 0 book_staleness book i 109,072 5,260 36ms 211ms 9.8h 107.0d 0 book_staleness book k 110,324 12,623 15ms 128ms 9.8h 107.0d 0 book_staleness book m 108,138 98,212 7ms 36ms 4.6h 107.0d 0 book_staleness last_trade_price g 50,460 8 90ms 1.6s 15.9s 34.2s 0 transport_latency_assumed last_trade_price h 51,356 674 21ms 70ms 993ms 54.8s 0 transport_latency_assumed last_trade_price i 51,373 255 31ms 82ms 683ms 3.9s 0 transport_latency_assumed last_trade_price k 51,365 3,306 13ms 62ms 428ms 10.2s 0 transport_latency_assumed last_trade_price m 51,372 47,142 6ms 14ms 204ms 2.1s 0 transport_latency_assumed market_resolved g 662 not meas. 80ms 324ms 49.2s 49.2s 0 transport_latency_assumed market_resolved h 662 8 20ms 62ms 41.6s 41.6s 0 transport_latency_assumed market_resolved i 662 1 26ms 87ms 35.2s 56.9s 0 transport_latency_assumed market_resolved k 662 56 14ms 66ms 52.1s 52.1s 0 transport_latency_assumed market_resolved m 662 634 5ms 17.4s 54.3s 54.6s 0 transport_latency_assumed new_market g 977 131 323ms 23.3s 41.0s 1.5min 0 transport_latency_assumed new_market h 977 235 185ms 31.5s 39.5s 1.6min 0 transport_latency_assumed new_market i 977 284 222ms 20.7s 40.5s 1.6min 0 transport_latency_assumed new_market k 977 230 275ms 31.9s 39.3s 1.7min 0 transport_latency_assumed new_market m 977 689 45ms 33.6s 39.4s 1.6min 0 transport_latency_assumed price_change g 101,888,646 9,026 78ms 201ms 6.4s 34.2s 0 transport_latency_assumed price_change h 102,346,162 1,017,884 19ms 35ms 533ms 2.4min 0 transport_latency_assumed price_change i 102,361,064 340,204 23ms 45ms 430ms 33.2s 0 transport_latency_assumed price_change k 102,327,232 5,639,092 12ms 27ms 303ms 1.2min 0 transport_latency_assumed price_change m 102,323,864 95,370,228 5ms 11ms 153ms 7.0s 0 transport_latency_assumed tick_size_change g 4,480 not meas. 77ms 122ms 1.3s 2.6s 0 transport_latency_assumed tick_size_change h 4,480 53 19ms 38ms 767ms 34.5s 0 transport_latency_assumed tick_size_change i 4,480 4 24ms 45ms 461ms 10.2s 0 transport_latency_assumed tick_size_change k 4,480 209 13ms 36ms 392ms 7.7s 0 transport_latency_assumed tick_size_change m 4,480 4,214 5ms 12ms 204ms 329ms 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-02/10/2026-10-02T10.parquet sha256sum 2026-10-02T10.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.