Hour audit: 2026-10-03T12
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-03T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T12:00:00.001410779+00:00 · last event 2026-10-03T12:59:59.999946168+00:00
VOLUME 111,320,639 rows · 1,165,925,767 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 111,230,014 · m: 111,196,421 · k: 111,196,047 · i: 111,187,612 · g: 111,141,429 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,248,102 (1.12%) · m: 104,728,287 (94.08%) · k: 4,639,026 (4.17%) · i: 654,696 (0.59%) · g: 50,528 (0.05%) (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 111,320,639 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 520b95edd04485e08dae9630ec0df74a2f78502614287f89a8b60dea0d8237cf
the corpus checksum ledger names this file with the same digest
joined 111,322,517 to merged 111,320,639, minus 1,878 (minus 0.0017%)
boundary drops 1,878 · 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-03T14:46:51Z 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,985,350 120,898,691 0-38 9e065d609fe2aa8bcafcca774ca9cd90de04a3dfa6f3111102ad73d20fec5aee book 135,482 14,799,726 39-39 78421fee34ea32312b6b95c5e995e8623ac7372101b4b4e0682991130187944b last_trade_price 51,964 3,038,927 40-40 8f660d68718700906bd0e481dbe6b0de042aadd5e8160abe9187586532732cd3 market_resolved 703 113,027 41-41 602750be171fa7964e3e01672c6e08bf2faef2e2607b2cbcf593e0de37662f6f new_market 2,208 206,686 42-42 73073f9dc425f191a6e90e765b9b32fb52ed4feb7e936926f25e0697c2eebde1 price_change 101,141,400 1,025,467,991 43-428 01bb4d3691db91d6d6a43e6e1f226024aca81874bf889edafb25d2f04f816bcf tick_size_change 3,532 130,116 429-429 1b1db9df7289370c1365eb91b64974c1be24976e41b6a1380e7ef7513bf60c3b EVENT MIX count share price_change 101,141,400 90.86% best_bid_ask 9,985,350 8.97% book 135,482 0.12% last_trade_price 51,964 0.05% tick_size_change 3,532 <0.01% new_market 2,208 <0.01% market_resolved 703 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,985,494 9,985,350 144 192 FULL book 135,482 135,482 0 12,371 FULL last_trade_price 51,964 51,964 0 0 FULL market_resolved 703 703 0 0 FULL new_market 2,208 2,208 0 0 FULL price_change 101,143,134 101,141,400 1,734 321 FULL tick_size_change 3,532 3,532 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,981,622 1,562 79ms 101ms 547ms 31.9s 0 transport_latency_assumed best_bid_ask h 9,983,956 108,781 18ms 27ms 352ms 51.9s 0 transport_latency_assumed best_bid_ask i 9,983,699 54,786 21ms 28ms 191ms 14.5s 0 transport_latency_assumed best_bid_ask k 9,983,627 411,453 13ms 24ms 289ms 58.2s 0 transport_latency_assumed best_bid_ask m 9,983,873 9,408,768 4ms 11ms 104ms 5.3s 0 transport_latency_assumed book g 120,210 13,891 90ms 36.3s 5.9d 126.6d 0 book_staleness book h 112,105 7,624 23ms 236ms 16.0h 108.1d 0 book_staleness book i 108,214 4,189 24ms 98ms 45.2min 108.0d 0 book_staleness book k 110,192 9,877 18ms 91ms 9.1h 108.1d 0 book_staleness book m 109,034 99,901 7ms 33ms 1.5h 31.0d 0 book_staleness last_trade_price g 51,749 16 85ms 301ms 2.7s 20.1s 0 transport_latency_assumed last_trade_price h 51,855 796 20ms 54ms 652ms 44.4s 0 transport_latency_assumed last_trade_price i 51,711 474 23ms 57ms 667ms 5.0s 0 transport_latency_assumed last_trade_price k 51,766 3,146 15ms 36ms 409ms 50.8s 0 transport_latency_assumed last_trade_price m 51,788 47,532 6ms 17ms 201ms 2.4s 0 transport_latency_assumed market_resolved g 691 not meas. 80ms 216ms 3.5s 25.1s 0 transport_latency_assumed market_resolved h 691 2 19ms 48ms 26.6s 55.3s 0 transport_latency_assumed market_resolved i 691 19 22ms 70ms 55.9s 56.0s 0 transport_latency_assumed market_resolved k 691 30 14ms 31ms 3.4s 22.5s 0 transport_latency_assumed market_resolved m 691 652 5ms 11ms 9.4s 56.6s 0 transport_latency_assumed new_market g 1,325 159 299ms 27.0s 1.8min 2.4min 0 transport_latency_assumed new_market h 1,325 251 176ms 28.3s 2.1min 2.5min 0 transport_latency_assumed new_market i 1,325 571 139ms 37.6s 2.2min 2.5min 0 transport_latency_assumed new_market k 1,325 357 209ms 34.2s 1.9min 2.5min 0 transport_latency_assumed new_market m 1,325 870 76ms 36.2s 2.0min 2.5min 0 transport_latency_assumed price_change g 100,982,300 34,900 79ms 123ms 1.2s 31.9s 0 transport_latency_assumed price_change h 101,076,550 1,130,562 18ms 30ms 464ms 54.3s 0 transport_latency_assumed price_change i 101,038,440 594,641 21ms 32ms 294ms 17.2s 0 transport_latency_assumed price_change k 101,044,914 4,213,883 13ms 26ms 305ms 59.7s 0 transport_latency_assumed price_change m 101,046,178 95,167,414 5ms 12ms 108ms 5.4s 0 transport_latency_assumed tick_size_change g 3,532 not meas. 78ms 94ms 215ms 859ms 0 transport_latency_assumed tick_size_change h 3,532 86 18ms 25ms 142ms 2.4s 0 transport_latency_assumed tick_size_change i 3,532 16 21ms 29ms 89ms 727ms 0 transport_latency_assumed tick_size_change k 3,532 280 13ms 23ms 106ms 13.4s 0 transport_latency_assumed tick_size_change m 3,532 3,150 5ms 16ms 355ms 455ms 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/12/2026-10-03T12.parquet sha256sum 2026-10-03T12.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.