Hour audit: 2026-10-03T18
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-03T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T18:00:00.001450399+00:00 · last event 2026-10-03T18:59:59.999989067+00:00
VOLUME 142,471,617 rows · 1,646,854,991 bytes (1.53 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 139,992,856 · m: 139,972,040 · i: 127,501,576 · g: 120,729,537 · k: 114,810,130 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,783,190 (1.95%) · m: 129,481,844 (90.88%) · i: 1,249,267 (0.88%) · g: 1,448,342 (1.02%) · k: 7,508,974 (5.27%) (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 142,471,617 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0f043c1dfbe89a704686ed3df3a436a25a80246b44d17bed763dc5bc29e26fe3
the corpus checksum ledger names this file with the same digest
joined 142,521,864 to merged 142,471,617, minus 50,247 (minus 0.0353%)
boundary drops 50,247 · 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-03T20:54:20Z 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 12,533,886 152,290,677 0-47 d4f1b6d4a7eeb006b94d4c914ded2af1406b873ba09cfb329280bc7fa741f42d book 2,552,740 112,879,810 48-57 0ce89117366d62391e5f2350d5385a4c8f29d3408944b48d7d2a995c9cdde21c last_trade_price 59,937 3,540,620 58-58 7b82da52fe4d96977141881168789dea40b83fdf7113229e658c03ed70b66afa market_resolved 9,906 938,586 59-59 23baa55c2072b68abae000ba8cfe2a9a4d728623222fd14061628f4c37044227 new_market 2,266 205,041 60-60 1164896b28e18d9803401681d6ec5b84fc21691b00839ef74303ee4b1e004a0a price_change 127,304,294 1,375,064,727 61-546 d2603fbd080be96484edba4451e0a3ce759b644cc2171aae8b0d28caa3092668 tick_size_change 8,588 317,107 547-547 2127042967eb2d0fe965a50794cf990fd5b9d4925d75490eb9961f7b39693a14 EVENT MIX count share price_change 127,304,294 89.35% best_bid_ask 12,533,886 8.80% book 2,552,740 1.79% last_trade_price 59,937 0.04% market_resolved 9,906 <0.01% tick_size_change 8,588 <0.01% new_market 2,266 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,537,332 12,533,886 3,446 5,340 FULL book 2,554,176 2,552,740 1,436 236,876 FULL last_trade_price 59,948 59,937 11 658 FULL market_resolved 9,908 9,906 2 889 FULL new_market 2,682 2,266 416 704 FULL price_change 127,349,230 127,304,294 44,936 4,210 FULL tick_size_change 8,588 8,588 0 450 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,695,638 903 81ms 107ms 422ms 23.2s 0 transport_latency_assumed best_bid_ask h 12,534,366 240,152 19ms 31ms 197ms 52.5s 0 transport_latency_assumed best_bid_ask i 11,357,719 87,546 21ms 33ms 135ms 6.3s 0 transport_latency_assumed best_bid_ask k 10,131,651 576,671 14ms 27ms 126ms 16.8s 0 transport_latency_assumed best_bid_ask m 12,532,905 11,628,614 5ms 14ms 86ms 4.8s 0 transport_latency_assumed book g 1,568,026 1,433,711 27.4min 1.7d 42.2d 126.8d 0 book_staleness book h 122,638 4,372 24ms 70ms 3.4s 64.4d 0 book_staleness book i 1,106,891 129,228 23.1min 1.7d 42.2d 126.8d 0 book_staleness book k 2,052,419 876,535 34.8min 1.8d 42.2d 126.9d 0 book_staleness book m 124,294 108,894 8ms 37ms 1.5h 57.3d 0 book_staleness last_trade_price g 48,625 22 89ms 317ms 8.7s 23.1s 0 transport_latency_assumed last_trade_price h 59,853 1,876 20ms 51ms 547ms 9.0s 0 transport_latency_assumed last_trade_price i 52,347 843 24ms 53ms 497ms 4.0s 0 transport_latency_assumed last_trade_price k 46,727 3,999 15ms 34ms 276ms 9.0s 0 transport_latency_assumed last_trade_price m 59,819 53,197 7ms 23ms 231ms 1.7s 0 transport_latency_assumed market_resolved g 6,717 2,540 136ms 12.6min 19.5min 20.2min 0 transport_latency_assumed market_resolved h 4,745 134 20ms 113ms 52.7s 56.7s 0 transport_latency_assumed market_resolved i 6,193 899 28ms 10.3min 19.1min 21.6min 0 transport_latency_assumed market_resolved k 5,870 1,868 20ms 8.0min 16.4min 16.9min 0 transport_latency_assumed market_resolved m 4,744 4,465 6ms 17.9s 50.2s 56.2s 0 transport_latency_assumed new_market g 1,078 226 309ms 2.9min 14.0min 16.1min 0 transport_latency_assumed new_market h 986 168 126ms 34.1s 3.3min 3.9min 0 transport_latency_assumed new_market i 2,110 584 3.6min 9.0min 14.2min 15.5min 0 transport_latency_assumed new_market k 1,497 593 252ms 5.8min 8.3min 10.2min 0 transport_latency_assumed new_market m 986 695 45ms 10.6s 3.0min 3.7min 0 transport_latency_assumed price_change g 108,401,485 10,940 81ms 126ms 893ms 23.2s 0 transport_latency_assumed price_change h 127,261,680 2,536,374 19ms 34ms 277ms 53.4s 0 transport_latency_assumed price_change i 114,968,588 1,030,088 22ms 36ms 203ms 6.3s 0 transport_latency_assumed price_change k 102,564,770 6,048,817 14ms 29ms 161ms 17.3s 0 transport_latency_assumed price_change m 127,240,704 117,678,075 5ms 16ms 101ms 5.4s 0 transport_latency_assumed tick_size_change g 7,968 not meas. 80ms 118ms 1.0s 2.2s 0 transport_latency_assumed tick_size_change h 8,588 114 19ms 32ms 332ms 6.9s 0 transport_latency_assumed tick_size_change i 7,728 79 21ms 35ms 286ms 699ms 0 transport_latency_assumed tick_size_change k 7,196 491 14ms 27ms 195ms 2.2s 0 transport_latency_assumed tick_size_change m 8,588 7,904 5ms 15ms 153ms 280ms 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/18/2026-10-03T18.parquet sha256sum 2026-10-03T18.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.