Hour audit: 2026-09-24T06
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-09-24T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T06:00:00.000206+00:00 · last event 2026-09-24T06:59:59.999875303+00:00
VOLUME 120,578,471 rows · 1,279,564,299 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 120,040,196 · k: 119,808,189 · h: 119,734,392 · c: 114,706,470 · g: 114,626,464 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,576,030 (1.31%) · k: 11,387,997 (9.44%) · h: 2,530,761 (2.10%) · c: 104,948,164 (87.04%) · g: 135,519 (0.11%) (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 120,578,471 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6e77da73cb9acb59f43584d015d5c237b0c506ebbad482cb3836f0ddbbc30962
the corpus checksum ledger names this file with the same digest
joined 120,580,502 to merged 120,578,471, minus 2,031 (minus 0.0017%)
boundary drops 2,031 · 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-09-24T09:43:09Z as cghik
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 13,353,696 152,199,762 0-50 f856ac07c26f91520b7bcc5afc2ba85669ef4643c67ff608540c661c6adad4ea book 896,493 67,590,833 51-54 e604460ac4863491e30ca6366939f620b6320c155e5fabfe1565c2831a01bbd8 last_trade_price 54,344 3,065,493 55-55 80a426e7e6c5417d9d528343b07bc1fc3e91d73b121fae6b67f9703cec1f4c13 market_resolved 640 96,286 56-56 b598612a82c11c58a46c2966f6a031e5e09b1ca47b0ad93341a950d19472d506 new_market 2,128 211,863 57-57 ab478dd04cf9139799fa81ade7a87e3b26ed1418a585c2a878ee25446e1600cd price_change 106,269,382 1,054,963,558 58-463 0204c8eba56075d8e01c3c1688859578a0981d7510d3af5f6642b3e378bc2700 tick_size_change 1,788 64,722 464-464 ab187d443ad7cd7ff26a856e0471ee488b5f66e41f344792d5fb440ec8ee1e0f EVENT MIX count share price_change 106,269,382 88.13% best_bid_ask 13,353,696 11.07% book 896,493 0.74% last_trade_price 54,344 0.05% new_market 2,128 <0.01% tick_size_change 1,788 <0.01% market_resolved 640 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,353,966 13,353,696 270 796 FULL book 896,513 896,493 20 192,802 FULL last_trade_price 54,344 54,344 0 86 FULL market_resolved 641 640 1 1 FULL new_market 2,128 2,128 0 51 FULL price_change 106,271,122 106,269,382 1,740 364 FULL tick_size_change 1,788 1,788 0 11 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,782,653 11,813,146 5ms 12ms 102ms 5.8s 0 transport_latency_assumed best_bid_ask g 12,790,642 1,137 79ms 104ms 406ms 31.7s 0 transport_latency_assumed best_bid_ask h 13,350,799 240,115 18ms 34ms 202ms 36.1s 0 transport_latency_assumed best_bid_ask i 13,349,385 140,161 21ms 30ms 127ms 4.0s 0 transport_latency_assumed best_bid_ask k 13,351,696 1,159,137 12ms 21ms 118ms 9.0s 0 transport_latency_assumed book c 554,986 519,197 6.6min 3.4d 38.5d 117.3d 0 book_staleness book g 537,092 124,776 6.5min 2.8d 36.3d 117.3d 0 book_staleness book h 132,422 15,692 23ms 4.0min 14.9d 98.8d 0 book_staleness book i 422,102 197,983 2.7min 2.4d 32.7d 117.4d 0 book_staleness book k 159,495 38,845 19ms 33.8min 18.7d 115.7d 0 book_staleness last_trade_price c 51,965 46,150 5ms 24ms 205ms 2.4s 0 transport_latency_assumed last_trade_price g 50,716 4 89ms 431ms 7.6s 32.2s 0 transport_latency_assumed last_trade_price h 54,179 1,472 19ms 55ms 278ms 9.7s 0 transport_latency_assumed last_trade_price i 54,248 542 23ms 93ms 476ms 3.9s 0 transport_latency_assumed last_trade_price k 54,264 6,176 13ms 34ms 196ms 1.6s 0 transport_latency_assumed market_resolved c 585 508 5ms 13.9s 3.9min 5.0min 0 transport_latency_assumed market_resolved g 585 8 91ms 22.0s 4.8min 4.8min 0 transport_latency_assumed market_resolved h 584 12 25ms 148ms 44.3s 51.4s 0 transport_latency_assumed market_resolved i 584 42 24ms 173ms 44.3s 51.4s 0 transport_latency_assumed market_resolved k 585 70 14ms 69ms 30.9s 57.1s 0 transport_latency_assumed new_market c 1,351 628 78ms 4.1min 4.7min 4.9min 0 transport_latency_assumed new_market g 1,352 246 272ms 4.4min 5.2min 5.9min 0 transport_latency_assumed new_market h 1,377 524 117ms 24.4s 2.0min 3.0min 0 transport_latency_assumed new_market i 1,377 367 115ms 26.5s 1.9min 2.9min 0 transport_latency_assumed new_market k 1,377 363 134ms 29.2s 2.0min 3.0min 0 transport_latency_assumed price_change c 101,313,170 92,566,907 5ms 16ms 120ms 5.8s 0 transport_latency_assumed price_change g 101,244,333 9,348 80ms 131ms 1.1s 33.2s 0 transport_latency_assumed price_change h 106,193,243 2,272,926 18ms 39ms 231ms 36.7s 0 transport_latency_assumed price_change i 106,210,712 1,236,928 21ms 38ms 178ms 4.2s 0 transport_latency_assumed price_change k 106,238,984 10,183,273 13ms 24ms 140ms 9.3s 0 transport_latency_assumed tick_size_change c 1,760 1,628 5ms 10ms 109ms 168ms 0 transport_latency_assumed tick_size_change g 1,744 not meas. 79ms 98ms 320ms 603ms 0 transport_latency_assumed tick_size_change h 1,788 20 18ms 26ms 88ms 270ms 0 transport_latency_assumed tick_size_change i 1,788 7 21ms 27ms 84ms 307ms 0 transport_latency_assumed tick_size_change k 1,788 133 12ms 18ms 86ms 182ms 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-09-24/06/2026-09-24T06.parquet sha256sum 2026-09-24T06.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.