Hour audit: 2026-09-12T23
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-12T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T23:00:00.000059863+00:00 · last event 2026-09-12T23:59:59.999981445+00:00
VOLUME 129,610,975 rows · 1,386,253,150 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 127,460,440 · h: 127,455,289 · g: 122,579,441 · f: 122,389,868 · c: 103,472,093 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,849,763 (1.43%) · h: 27,299,792 (21.06%) · g: 156,320 (0.12%) · f: 634,410 (0.49%) · c: 99,670,690 (76.90%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 7505359d529795ab76759488d2a0a29e8b8fe3222ab0a2617f619690c2da2c6e
the corpus checksum ledger names this file with the same digest
joined 129,619,348 to merged 129,610,975, minus 8,373 (minus 0.0065%)
boundary drops 8,373 · 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-13T01:37:31Z as cefgh
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,905,412 143,177,664 0-49 314afd6e357e48472200ef80aca785b242c5b1ed96badc880ee78cb68a9e0b23 book 2,247,592 96,359,877 50-58 b47b6d9c12662acbaa3f64316f8c2b937ab749f8032baa15d79d49d3f5389a26 last_trade_price 49,567 2,857,430 59-59 9ba01962a316139381b37dd8d2658e874b0edfc3c8848f112cf468a28fbc4efb market_resolved 8,619 726,851 60-60 f32dacf1e1368570277119aeb30500ca9bb9f4fdb93260128de9ffc76ed1c91b new_market 3,275 261,709 61-61 d8c030259ae5088a6288682e221010fbbd1bb7e5a662a7f98b6563eae3f32a8b price_change 114,388,238 1,141,089,758 62-498 f3d2a21aada92ba1c9b3f49ddba426daf035531b30c33cecf2236087707a5928 tick_size_change 8,272 304,822 499-499 0e084a796ca01b889ab17d95d3419718ff27fb430fa0721d1854f12d9b092104 EVENT MIX count share price_change 114,388,238 88.26% best_bid_ask 12,905,412 9.96% book 2,247,592 1.73% last_trade_price 49,567 0.04% market_resolved 8,619 <0.01% tick_size_change 8,272 <0.01% new_market 3,275 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,905,696 12,905,412 284 5,205 FULL book 2,253,207 2,247,592 5,615 188,871 FULL last_trade_price 49,568 49,567 1 590 FULL market_resolved 8,656 8,619 37 1,552 FULL new_market 3,291 3,275 16 292 FULL price_change 114,390,658 114,388,238 2,420 4,169 FULL tick_size_change 8,272 8,272 0 589 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,353,157 9,995,942 5ms 9ms 152ms 3.8s 0 transport_latency_assumed best_bid_ask e 12,903,783 178,358 39ms 45ms 201ms 3.4s 0 transport_latency_assumed best_bid_ask f 12,353,026 44,936 45ms 53ms 227ms 4.7s 0 transport_latency_assumed best_bid_ask g 12,383,500 4,829 78ms 94ms 428ms 32.7s 0 transport_latency_assumed best_bid_ask h 12,904,331 2,681,347 18ms 25ms 265ms 53.2s 0 transport_latency_assumed book c 1,999,404 1,966,686 29.3min 1.2d 34.3d 106.1d 0 book_staleness book e 127,462 12,749 42ms 17.4min 5.5d 106.0d 0 book_staleness book f 508,005 140,995 6.3min 1.1d 31.2d 106.0d 0 book_staleness book g 521,710 98,633 6.5min 1.1d 31.2d 106.0d 0 book_staleness book h 117,107 28,529 21ms 13.9s 1.2d 87.6d 0 book_staleness last_trade_price c 38,288 36,472 10ms 42ms 267ms 4.9s 0 transport_latency_assumed last_trade_price e 49,474 823 45ms 97ms 454ms 5.0s 0 transport_latency_assumed last_trade_price f 47,471 223 51ms 104ms 509ms 5.0s 0 transport_latency_assumed last_trade_price g 47,319 28 90ms 200ms 1.6s 33.1s 0 transport_latency_assumed last_trade_price h 49,495 12,021 23ms 60ms 376ms 22.7s 0 transport_latency_assumed market_resolved c 7,786 7,698 9.7min 27.3min 34.5min 35.3min 0 transport_latency_assumed market_resolved e 3,186 36 42ms 120ms 346ms 25.6s 0 transport_latency_assumed market_resolved f 3,179 152 49ms 164ms 5.4min 5.7min 0 transport_latency_assumed market_resolved g 3,149 3 89ms 245ms 5.5min 5.8min 0 transport_latency_assumed market_resolved h 3,186 730 31ms 58ms 135ms 34.0s 0 transport_latency_assumed new_market c 2,529 2,030 4.4min 24.5min 1.6h 2.9h 0 transport_latency_assumed new_market e 1,285 269 227ms 23.6s 1.4min 45.5min 0 transport_latency_assumed new_market f 1,285 298 231ms 29.8s 1.4min 2.5h 0 transport_latency_assumed new_market g 1,285 121 303ms 25.8s 1.3min 1.6h 0 transport_latency_assumed new_market h 1,285 557 181ms 20.5s 1.2min 2.4h 0 transport_latency_assumed price_change c 91,064,357 87,655,784 5ms 10ms 179ms 3.9s 0 transport_latency_assumed price_change e 114,366,978 1,657,425 39ms 47ms 243ms 3.6s 0 transport_latency_assumed price_change f 109,469,134 447,794 45ms 55ms 267ms 4.8s 0 transport_latency_assumed price_change g 109,614,534 52,702 78ms 100ms 500ms 33.6s 0 transport_latency_assumed price_change h 114,371,613 24,574,533 18ms 28ms 284ms 53.4s 0 transport_latency_assumed tick_size_change c 6,572 6,078 5ms 18ms 272ms 365ms 0 transport_latency_assumed tick_size_change e 8,272 103 39ms 48ms 337ms 606ms 0 transport_latency_assumed tick_size_change f 7,768 12 45ms 61ms 373ms 582ms 0 transport_latency_assumed tick_size_change g 7,944 4 78ms 102ms 577ms 1.0s 0 transport_latency_assumed tick_size_change h 8,272 2,075 18ms 26ms 282ms 4.3s 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-12/23/2026-09-12T23.parquet sha256sum 2026-09-12T23.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.