Hour audit: 2026-09-22T18
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-22T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T18:00:00.000049644+00:00 · last event 2026-09-22T18:59:59.999973276+00:00
VOLUME 122,049,143 rows · 1,365,861,596 bytes (1.27 GiB) · 7 products, all holding rows
WITNESSES cefhik — 6 machines contributed rows
captured h: 120,482,755 · i: 119,669,025 · e: 119,630,814 · k: 116,516,517 · f: 116,342,097 · c: 109,633,948 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,268,419 (3.50%) · i: 1,636,185 (1.34%) · e: 140,722 (0.12%) · k: 19,750,773 (16.18%) · f: 231,770 (0.19%) · c: 96,021,274 (78.67%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 122,049,143 rows exactly, so those pairs supplied none
6 expected, all 6 contributed
INTEGRITY sha256 d39b9bddbdbeadda4457b485cf09d67a5df11212d872bd57d347612261c4e7ff
the corpus checksum ledger names this file with the same digest
joined 122,051,469 to merged 122,049,143, minus 2,326 (minus 0.0019%)
boundary drops 2,326 · 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-22T21:31:46Z as cefhik
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 12,293,240 146,626,524 0-46 f9dc8c1439535f5541ed456ea6a164a58ca312f8e3e459fd391bc3a64090fe84 book 1,322,550 78,668,401 47-52 6c49ec0ca93b72ebf69100b1d1b1feb140345d25a62b368aca80f4345524c3f9 last_trade_price 63,236 3,644,791 53-53 591634fe5dd69007fe83e89a415a5c7dcb5c8094c13fdc982d4a35d98a1a7385 market_resolved 821 113,496 54-54 3a130ac102d62f29d1a16ec7ccd19829ddf83ff7e8652cb43b087a7edd8488d8 new_market 3,434 344,382 55-55 daa70518c796106f52051b8967ccc494461794355164761d9837ba62fc2733de price_change 108,361,966 1,134,929,790 56-469 4443fd92cf007d4ce6dc04f892c0800d0d9fe5a44afbf3c6140a0e4244398d9a tick_size_change 3,896 143,313 470-470 a0260d5eba50cbed21b00d8215705815240f7d83dda1578c6409c4ad4cf2d908 EVENT MIX count share price_change 108,361,966 88.79% best_bid_ask 12,293,240 10.07% book 1,322,550 1.08% last_trade_price 63,236 0.05% tick_size_change 3,896 <0.01% new_market 3,434 <0.01% market_resolved 821 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,293,376 12,293,240 136 2,147 FULL book 1,323,372 1,322,550 822 178,599 FULL last_trade_price 63,236 63,236 0 271 FULL market_resolved 821 821 0 9 FULL new_market 3,434 3,434 0 0 FULL price_change 108,363,334 108,361,966 1,368 1,068 FULL tick_size_change 3,896 3,896 0 97 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,088,422 9,783,918 6ms 22ms 241ms 9.0s 0 transport_latency_assumed best_bid_ask e 12,252,478 9,856 45ms 74ms 575ms 24.0s 0 transport_latency_assumed best_bid_ask f 11,830,993 6,722 49ms 77ms 424ms 27.0s 0 transport_latency_assumed best_bid_ask h 12,278,538 407,647 18ms 35ms 348ms 50.4s 0 transport_latency_assumed best_bid_ask i 12,237,036 158,003 23ms 47ms 385ms 22.2s 0 transport_latency_assumed best_bid_ask k 11,820,386 1,927,094 13ms 26ms 232ms 56.7s 0 transport_latency_assumed book c 927,416 786,440 7.7min 3.2d 42.0d 115.8d 0 book_staleness book e 144,552 18,064 60ms 1.2min 4.1d 115.8d 0 book_staleness book f 540,078 150,205 5.9min 2.2d 38.2d 115.8d 0 book_staleness book h 143,766 19,048 23ms 3.6s 5.6d 97.3d 0 book_staleness book i 408,853 179,340 1.7min 23.9h 36.5d 115.8d 0 book_staleness book k 538,359 169,453 3.1min 2.0d 38.3d 115.8d 0 book_staleness last_trade_price c 57,119 49,444 7ms 39ms 351ms 2.5s 0 transport_latency_assumed last_trade_price e 59,792 133 51ms 830ms 9.2s 23.9s 0 transport_latency_assumed last_trade_price f 59,674 102 57ms 781ms 5.7s 27.0s 0 transport_latency_assumed last_trade_price h 62,059 2,338 19ms 93ms 793ms 42.1s 0 transport_latency_assumed last_trade_price i 59,228 557 25ms 528ms 2.9s 22.2s 0 transport_latency_assumed last_trade_price k 59,756 10,662 14ms 54ms 387ms 7.7s 0 transport_latency_assumed market_resolved c 700 560 7ms 42.6s 6.0min 6.3min 0 transport_latency_assumed market_resolved e 693 not meas. 47ms 11.3s 56.5s 1.0min 0 transport_latency_assumed market_resolved f 706 80 52ms 39.5s 5.3min 5.3min 0 transport_latency_assumed market_resolved h 693 42 20ms 300ms 58.4s 58.5s 0 transport_latency_assumed market_resolved i 693 19 25ms 780ms 57.6s 1.9min 0 transport_latency_assumed market_resolved k 693 120 17ms 50.7s 4.0min 4.4min 0 transport_latency_assumed new_market c 2,153 772 143ms 18.3s 29.4s 5.1min 0 transport_latency_assumed new_market e 2,153 259 218ms 15.8s 26.8s 1.9min 0 transport_latency_assumed new_market f 2,155 223 240ms 18.7s 28.8s 5.0min 0 transport_latency_assumed new_market h 2,153 614 170ms 15.5s 25.2s 1.5min 0 transport_latency_assumed new_market i 2,153 732 148ms 17.6s 28.1s 1.6min 0 transport_latency_assumed new_market k 2,153 834 141ms 14.2s 24.3s 1.8min 0 transport_latency_assumed price_change c 97,554,494 85,396,784 6ms 27ms 255ms 9.2s 0 transport_latency_assumed price_change e 107,167,250 112,410 46ms 118ms 2.9s 24.1s 0 transport_latency_assumed price_change f 103,904,683 74,438 49ms 113ms 1.6s 27.1s 0 transport_latency_assumed price_change h 107,991,650 3,838,658 18ms 43ms 411ms 51.5s 0 transport_latency_assumed price_change i 106,957,170 1,297,506 23ms 74ms 1.3s 22.2s 0 transport_latency_assumed price_change k 104,091,378 17,642,170 13ms 31ms 253ms 57.8s 0 transport_latency_assumed tick_size_change c 3,644 3,356 6ms 12ms 61ms 392ms 0 transport_latency_assumed tick_size_change e 3,896 not meas. 45ms 90ms 372ms 903ms 0 transport_latency_assumed tick_size_change f 3,808 not meas. 48ms 61ms 225ms 1.2s 0 transport_latency_assumed tick_size_change h 3,896 72 18ms 30ms 618ms 5.2s 0 transport_latency_assumed tick_size_change i 3,892 28 23ms 47ms 241ms 574ms 0 transport_latency_assumed tick_size_change k 3,792 440 13ms 19ms 119ms 569ms 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-22/18/2026-09-22T18.parquet sha256sum 2026-09-22T18.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.