Hour audit: 2026-09-23T14
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-23T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T14:00:00.000011027+00:00 · last event 2026-09-23T14:59:59.999967532+00:00
VOLUME 147,291,699 rows · 1,671,956,547 bytes (1.56 GiB) · 7 products, all holding rows
WITNESSES cfghik — 6 machines contributed rows
captured h: 143,623,560 · i: 126,149,137 · g: 124,918,409 · f: 109,978,502 · k: 109,958,071 · c: 107,464,237 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 22,229,748 (15.09%) · i: 6,560,382 (4.45%) · g: 330,719 (0.22%) · f: 1,455,627 (0.99%) · k: 21,158,510 (14.37%) · c: 95,556,713 (64.88%) (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 147,291,699 rows exactly, so those pairs supplied none
6 expected, all 6 contributed
INTEGRITY sha256 843d861f5d2244879136626185932cede9106582cb4d3afa15e2e5c0c7e8b9bb
the corpus checksum ledger names this file with the same digest
joined 147,316,194 to merged 147,291,699, minus 24,495 (minus 0.0166%)
boundary drops 24,495 · 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-23T20:06:02Z 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 13,839,374 166,514,454 0-52 1185cf966caa7558107bb915d7fbb03902336305d4771afea882aa2cfeaee154 book 3,915,292 143,392,809 53-67 6ce7a006334953f0e50cdf90fbe1aa40d2d5e56e0a1ef5d8e4c6b35d9d9c2da8 last_trade_price 74,236 4,231,215 68-68 f26aa7b19dae39f91750bbd2c821b05ebeea0dc4c7f7c0e0523eb2d3c1f56e53 market_resolved 2,608 216,165 69-69 8133f2321d700714601279f822e53c5c4f0732db56137804bc406955174033e8 new_market 1,707 123,029 70-70 a05579e4fdce56310c2b86198bf912a7aba4e7f581ce605aeaeaa3ea4b7d88bf price_change 129,455,006 1,355,675,539 71-564 3376dd4bdda64598b2c9f2c86430ea00e79a52b0b437ddc3d53a1b2a36d2fd4f tick_size_change 3,476 129,640 565-565 d68a0142d4d54655793addbf6424e4972567a7adf30733f5884d81cf91333fa7 EVENT MIX count share price_change 129,455,006 87.89% best_bid_ask 13,839,374 9.40% book 3,915,292 2.66% last_trade_price 74,236 0.05% tick_size_change 3,476 <0.01% market_resolved 2,608 <0.01% new_market 1,707 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,839,598 13,839,374 224 6,724 FULL book 3,937,497 3,915,292 22,205 102,137 FULL last_trade_price 74,236 74,236 0 1,094 FULL market_resolved 2,618 2,608 10 397 FULL new_market 1,721 1,707 14 89 FULL price_change 129,457,048 129,455,006 2,042 3,342 FULL tick_size_change 3,476 3,476 0 402 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,155,628 9,224,293 6ms 15ms 117ms 2.3s 0 transport_latency_assumed best_bid_ask f 10,427,564 71,604 50ms 68ms 253ms 14.3s 0 transport_latency_assumed best_bid_ask g 12,081,538 11,267 80ms 109ms 475ms 30.6s 0 transport_latency_assumed best_bid_ask h 13,836,049 2,070,590 19ms 43ms 138ms 47.0s 0 transport_latency_assumed best_bid_ask i 12,078,260 601,464 21ms 31ms 120ms 3.1s 0 transport_latency_assumed best_bid_ask k 10,427,472 1,860,156 13ms 21ms 89ms 1.6s 0 transport_latency_assumed book c 2,553,969 930,920 11.8min 4.0d 42.8d 116.7d 0 book_staleness book f 2,346,351 650,761 11.6min 4.0d 42.8d 116.7d 0 book_staleness book g 1,316,859 177,916 9.5min 4.0d 42.0d 116.7d 0 book_staleness book h 351,455 101,204 19.3s 1.7d 32.0d 116.7d 0 book_staleness book i 1,303,631 157,160 10.0min 3.9d 42.0d 116.7d 0 book_staleness book k 2,501,729 1,897,331 11.8min 4.0d 42.8d 116.7d 0 book_staleness last_trade_price c 55,074 49,032 7ms 22ms 182ms 1.4s 0 transport_latency_assumed last_trade_price f 53,144 467 58ms 939ms 8.4s 14.2s 0 transport_latency_assumed last_trade_price g 59,337 66 94ms 2.8s 14.6s 30.7s 0 transport_latency_assumed last_trade_price h 74,017 12,217 21ms 71ms 357ms 7.1s 0 transport_latency_assumed last_trade_price i 64,277 2,924 23ms 98ms 752ms 3.0s 0 transport_latency_assumed last_trade_price k 54,863 9,530 14ms 32ms 156ms 1.4s 0 transport_latency_assumed market_resolved c 1,362 752 56.4s 13.0min 18.4min 22.0min 0 transport_latency_assumed market_resolved f 1,305 235 18.6s 12.0min 18.8min 18.8min 0 transport_latency_assumed market_resolved g 1,107 36 95ms 6.9min 10.8min 10.9min 0 transport_latency_assumed market_resolved h 979 321 22ms 19.9s 55.4s 55.4s 0 transport_latency_assumed market_resolved i 1,131 229 34ms 7.5min 11.6min 15.8min 0 transport_latency_assumed market_resolved k 2,066 1,035 9.3min 27.8min 36.2min 36.8min 0 transport_latency_assumed new_market c 766 349 96ms 7.1min 13.5min 13.5min 0 transport_latency_assumed new_market f 796 138 217ms 8.6min 13.1min 14.0min 0 transport_latency_assumed new_market g 670 70 280ms 40.1s 8.5min 8.6min 0 transport_latency_assumed new_market h 632 143 112ms 16.7s 48.9s 1.5min 0 transport_latency_assumed new_market i 717 180 103ms 5.0min 8.5min 8.6min 0 transport_latency_assumed new_market k 1,354 827 5.2min 23.0min 32.1min 33.1min 0 transport_latency_assumed price_change c 94,694,966 85,349,102 6ms 18ms 162ms 3.8s 0 transport_latency_assumed price_change f 97,146,750 732,406 51ms 90ms 1.7s 14.4s 0 transport_latency_assumed price_change g 111,455,882 141,364 81ms 160ms 4.8s 30.7s 0 transport_latency_assumed price_change h 129,356,952 20,044,735 20ms 49ms 228ms 47.6s 0 transport_latency_assumed price_change i 112,698,181 5,798,344 21ms 39ms 253ms 3.7s 0 transport_latency_assumed price_change k 96,967,831 17,389,055 13ms 24ms 135ms 2.0s 0 transport_latency_assumed tick_size_change c 2,472 2,265 5ms 13ms 107ms 148ms 0 transport_latency_assumed tick_size_change f 2,592 16 50ms 63ms 219ms 918ms 0 transport_latency_assumed tick_size_change g 3,016 not meas. 79ms 97ms 412ms 11.4s 0 transport_latency_assumed tick_size_change h 3,476 538 19ms 40ms 237ms 293ms 0 transport_latency_assumed tick_size_change i 2,940 81 20ms 26ms 73ms 126ms 0 transport_latency_assumed tick_size_change k 2,756 576 13ms 17ms 53ms 263ms 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/14/2026-09-23T14.parquet sha256sum 2026-09-23T14.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.