Hour audit: 2026-10-02T14
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-02T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T14:00:00.000025279+00:00 · last event 2026-10-02T14:59:59.999710435+00:00
VOLUME 127,134,785 rows · 1,461,504,603 bytes (1.36 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 126,304,396 · m: 126,289,786 · i: 126,077,883 · h: 126,074,698 · g: 118,641,393 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 11,327,394 (8.91%) · m: 109,190,854 (85.89%) · i: 2,018,852 (1.59%) · h: 3,901,870 (3.07%) · g: 695,815 (0.55%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 19ed2188962171eb869ebecd0f88905bfba77c86a8909eaaa6e116c61066a0c5
the corpus checksum ledger names this file with the same digest
joined 127,141,616 to merged 127,134,785, minus 6,831 (minus 0.0054%)
boundary drops 6,831 · 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-02T16:49:07Z 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,492,925 130,361,438 0-40 0b4611b3d895c34c2d420b07eb1830b2ade273a29d3154ef9d77cb438ca55017 book 1,319,431 93,072,415 41-46 2a0bc70e2d365fa5a4b6633f03d41077414da69b012a2b7118d47fdec998ab5b last_trade_price 65,961 3,770,582 47-47 e28d24049b932102abd4b99d91d753a0250fb7211e30738090b4d90fc49bb3b2 market_resolved 690 109,192 48-48 dc1e319077609622fa0f113d191bed83c8b7b5b13138f8adc9f397c138ec72e0 new_market 1,222 116,597 49-49 5ea99b91d0f2ea431ed71bd8a040014d3dfbf6ac842cb655724e8cb96a7d8e54 price_change 115,251,448 1,232,508,590 50-489 b122f5f1710bf75cab89aed58e3e9cc520771dcf2d7ad838602fe85cc46b9ee3 tick_size_change 3,108 115,240 490-490 823afabce0a62f30176355b9f7af7531024b64931dad4bbb1262dd24de3ff5a4 EVENT MIX count share price_change 115,251,448 90.65% best_bid_ask 10,492,925 8.25% book 1,319,431 1.04% last_trade_price 65,961 0.05% tick_size_change 3,108 <0.01% new_market 1,222 <0.01% market_resolved 690 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,493,238 10,492,925 313 620 FULL book 1,320,581 1,319,431 1,150 182,175 FULL last_trade_price 65,961 65,961 0 89 FULL market_resolved 690 690 0 5 FULL new_market 1,222 1,222 0 2 FULL price_change 115,256,816 115,251,448 5,368 659 FULL tick_size_change 3,108 3,108 0 62 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,938,526 905 80ms 138ms 1.1s 35.6s 0 transport_latency_assumed best_bid_ask h 10,482,020 299,959 19ms 44ms 402ms 50.4s 0 transport_latency_assumed best_bid_ask i 10,490,478 141,360 23ms 44ms 253ms 8.8s 0 transport_latency_assumed best_bid_ask k 10,490,315 910,735 15ms 37ms 216ms 9.2s 0 transport_latency_assumed best_bid_ask m 10,491,365 9,139,966 6ms 24ms 199ms 4.9s 0 transport_latency_assumed book g 875,604 680,190 33.6min 1.3d 41.0d 125.7d 0 book_staleness book h 549,713 155,835 12.4min 17.4h 41.0d 125.7d 0 book_staleness book i 330,040 62,902 52.3s 13.9h 41.0d 125.7d 0 book_staleness book k 536,172 155,169 10.9min 16.4h 41.0d 125.7d 0 book_staleness book m 544,793 265,335 12.0min 16.5h 41.0d 125.7d 0 book_staleness last_trade_price g 56,897 13 94ms 2.9s 17.7s 35.5s 0 transport_latency_assumed last_trade_price h 65,526 1,727 22ms 283ms 3.2s 12.5s 0 transport_latency_assumed last_trade_price i 65,674 1,304 31ms 224ms 1.7s 7.3s 0 transport_latency_assumed last_trade_price k 65,916 6,048 17ms 75ms 418ms 1.8s 0 transport_latency_assumed last_trade_price m 65,927 56,869 7ms 36ms 563ms 3.0s 0 transport_latency_assumed market_resolved g 664 16 85ms 36.6s 3.6min 4.2min 0 transport_latency_assumed market_resolved h 669 12 21ms 39.8s 43.4s 50.8s 0 transport_latency_assumed market_resolved i 669 3 32ms 34.5s 37.6s 57.8s 0 transport_latency_assumed market_resolved k 669 48 17ms 38.4s 42.2s 50.9s 0 transport_latency_assumed market_resolved m 669 611 6ms 27.6s 39.2s 52.0s 0 transport_latency_assumed new_market g 726 81 294ms 18.1s 48.3s 1.6min 0 transport_latency_assumed new_market h 726 241 201ms 21.1s 1.1min 1.3min 0 transport_latency_assumed new_market i 728 213 122ms 17.3s 50.4s 149.9d 0 transport_latency_assumed new_market k 726 131 136ms 19.6s 49.6s 1.6min 0 transport_latency_assumed new_market m 726 556 35ms 18.6s 53.6s 1.7min 0 transport_latency_assumed price_change g 107,766,116 14,606 82ms 262ms 11.7s 35.6s 0 transport_latency_assumed price_change h 114,972,936 3,444,004 20ms 66ms 1.4s 50.5s 0 transport_latency_assumed price_change i 115,187,186 1,812,982 24ms 58ms 679ms 9.7s 0 transport_latency_assumed price_change k 115,207,490 10,255,044 15ms 47ms 291ms 9.9s 0 transport_latency_assumed price_change m 115,183,198 99,724,812 6ms 28ms 260ms 5.0s 0 transport_latency_assumed tick_size_change g 2,860 4 81ms 269ms 806ms 9.4s 0 transport_latency_assumed tick_size_change h 3,108 92 20ms 76ms 734ms 4.0s 0 transport_latency_assumed tick_size_change i 3,108 88 25ms 58ms 343ms 808ms 0 transport_latency_assumed tick_size_change k 3,108 219 16ms 83ms 416ms 909ms 0 transport_latency_assumed tick_size_change m 3,108 2,705 6ms 33ms 217ms 315ms 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/14/2026-10-02T14.parquet sha256sum 2026-10-02T14.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.