Hour audit: 2026-09-23T13
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-23T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T13:00:00.000189828+00:00 · last event 2026-09-23T13:59:59.999932048+00:00
VOLUME 142,797,534 rows · 1,614,496,877 bytes (1.50 GiB) · 7 products, all holding rows
WITNESSES cfghik — 6 machines contributed rows
captured h: 139,781,105 · i: 133,702,792 · g: 122,329,211 · f: 117,359,442 · c: 116,164,551 · k: 109,106,573 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 13,587,220 (9.52%) · i: 6,425,682 (4.50%) · g: 408,179 (0.29%) · f: 781,245 (0.55%) · c: 103,758,821 (72.66%) · k: 17,836,387 (12.49%) (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 142,797,534 rows exactly, so those pairs supplied none
6 expected, all 6 contributed
INTEGRITY sha256 946347e926526b25bc0a4806e65c084286c9dee0b7130a114aba4e04fd21ccfd
the corpus checksum ledger names this file with the same digest
joined 142,799,727 to merged 142,797,534, minus 2,193 (minus 0.0015%)
boundary drops 2,193 · 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-23T18:32:15Z as cfghik
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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 14,298,216 170,038,143 0-54 3538a5ff7eba3a2bf82df8555610aec0e6092cb328ba49baf9e0d004eb4232d1 book 3,221,854 126,311,121 55-67 eadf4fa74f79f94599e17fbb3259ef4c7c5660a0b69e9a849a16e72ba8dd57df last_trade_price 66,128 3,778,222 68-68 a02980e0ea155f0d00a566a373f025c6d3746d31011252a917f4c9285620ff7f market_resolved 1,456 153,453 69-69 f769217c6840d6e302ecf3fe70c73014635bdefd9eb7286f9099e708fdb63d90 new_market 1,968 169,126 70-70 b79619154e4792eb75a04045b373b72ddaa32b3e111514b21a6f2b7b028d54c2 price_change 125,204,148 1,312,284,434 71-548 80b2d18d5fa1df2d9c05b0c933acb4d620ec0fe80193ee66c80b52a9e51119cf tick_size_change 3,764 137,529 549-549 dab825cee80b68d2dcd8f13b3a406602b9e5f170b9ee8a74d60bd4916508b350 EVENT MIX count share price_change 125,204,148 87.68% best_bid_ask 14,298,216 10.01% book 3,221,854 2.26% last_trade_price 66,128 0.05% tick_size_change 3,764 <0.01% new_market 1,968 <0.01% market_resolved 1,456 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,298,450 14,298,216 234 6,711 FULL book 3,221,960 3,221,854 106 88,152 FULL last_trade_price 66,129 66,128 1 986 FULL market_resolved 1,456 1,456 0 198 FULL new_market 1,968 1,968 0 4 FULL price_change 125,206,000 125,204,148 1,852 4,088 FULL tick_size_change 3,764 3,764 0 378 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,757,785 10,664,277 5ms 16ms 137ms 3.0s 0 transport_latency_assumed best_bid_ask f 11,877,040 10,422 50ms 69ms 276ms 9.5s 0 transport_latency_assumed best_bid_ask g 12,455,965 1,157 79ms 111ms 519ms 29.1s 0 transport_latency_assumed best_bid_ask h 14,293,182 1,368,363 19ms 38ms 195ms 17.2s 0 transport_latency_assumed best_bid_ask i 13,634,911 646,982 21ms 33ms 131ms 6.3s 0 transport_latency_assumed best_bid_ask k 10,922,289 1,607,015 13ms 22ms 110ms 6.0s 0 transport_latency_assumed book c 1,580,504 467,459 9.5min 4.0d 42.0d 116.7d 0 book_staleness book f 1,671,699 653,719 9.5min 4.0d 42.8d 116.6d 0 book_staleness book g 1,289,049 391,751 8.1min 4.0d 42.0d 116.6d 0 book_staleness book h 353,347 74,777 36.5s 1.7d 32.0d 116.7d 0 book_staleness book i 523,401 40,444 3.8min 1.9d 32.0d 116.6d 0 book_staleness book k 2,306,012 1,593,704 9.7min 4.0d 42.8d 116.7d 0 book_staleness last_trade_price c 54,582 48,042 7ms 28ms 248ms 3.0s 0 transport_latency_assumed last_trade_price f 53,085 123 54ms 377ms 4.8s 9.6s 0 transport_latency_assumed last_trade_price g 55,938 32 92ms 1.2s 16.6s 29.1s 0 transport_latency_assumed last_trade_price h 65,945 6,841 21ms 86ms 551ms 7.8s 0 transport_latency_assumed last_trade_price i 63,091 2,788 25ms 120ms 539ms 2.7s 0 transport_latency_assumed last_trade_price k 50,627 8,302 14ms 41ms 248ms 1.3s 0 transport_latency_assumed market_resolved c 799 622 7ms 32.9s 5.3min 8.8min 0 transport_latency_assumed market_resolved f 1,080 253 71ms 7.5min 14.7min 14.7min 0 transport_latency_assumed market_resolved g 868 68 83ms 3.8min 5.6min 5.9min 0 transport_latency_assumed market_resolved h 916 186 19ms 14.1s 22.0s 24.6s 0 transport_latency_assumed market_resolved i 903 31 23ms 20.6s 2.8min 3.8min 0 transport_latency_assumed market_resolved k 1,035 296 25ms 8.8min 10.8min 10.9min 0 transport_latency_assumed new_market c 1,144 495 180ms 4.5min 4.9min 5.3min 0 transport_latency_assumed new_market f 1,170 280 272ms 4.7min 11.3min 11.4min 0 transport_latency_assumed new_market g 1,051 81 316ms 13.7s 49.7s 4.8min 0 transport_latency_assumed new_market h 1,045 284 151ms 17.5s 24.8s 1.5min 0 transport_latency_assumed new_market i 1,045 278 134ms 12.5s 26.4s 5.0min 0 transport_latency_assumed new_market k 1,171 550 117ms 1.3min 10.5min 11.5min 0 transport_latency_assumed price_change c 102,766,521 92,575,113 6ms 19ms 162ms 4.3s 0 transport_latency_assumed price_change f 103,752,152 116,448 51ms 86ms 689ms 9.6s 0 transport_latency_assumed price_change g 108,522,904 15,090 80ms 152ms 2.7s 34.8s 0 transport_latency_assumed price_change h 125,062,906 12,136,515 19ms 43ms 272ms 21.3s 0 transport_latency_assumed price_change i 119,475,801 5,735,040 22ms 40ms 211ms 6.6s 0 transport_latency_assumed price_change k 95,822,327 14,625,942 13ms 26ms 145ms 8.2s 0 transport_latency_assumed tick_size_change c 3,216 2,813 6ms 25ms 96ms 225ms 0 transport_latency_assumed tick_size_change f 3,216 not meas. 51ms 69ms 273ms 1.6s 0 transport_latency_assumed tick_size_change g 3,436 not meas. 80ms 113ms 436ms 1.6s 0 transport_latency_assumed tick_size_change h 3,764 254 19ms 45ms 323ms 515ms 0 transport_latency_assumed tick_size_change i 3,640 119 22ms 45ms 105ms 286ms 0 transport_latency_assumed tick_size_change k 3,112 578 13ms 20ms 52ms 149ms 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-23/13/2026-09-23T13.parquet sha256sum 2026-09-23T13.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.