Hour audit: 2026-09-08T12
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-08T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T12:00:00.000040171+00:00 · last event 2026-09-08T12:59:59.999983293+00:00
VOLUME 98,056,482 rows · 1,047,585,099 bytes (999.06 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 97,417,361 · e: 97,343,960 · f: 97,340,176 · g: 97,023,638 · c: 93,741,421 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 8,232,597 (8.40%) · e: 638,244 (0.65%) · f: 343,188 (0.35%) · g: 37,905 (0.04%) · c: 88,804,548 (90.56%) (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 98,056,482 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 dfedb9148fc3044b8241e98cc12341dd1d9de4e6404ab962ea400f2c23166573
the corpus checksum ledger names this file with the same digest
joined 98,059,093 to merged 98,056,482, minus 2,611 (minus 0.0027%)
boundary drops 2,611 · 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-08T13:56:06Z 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 9,133,173 102,440,659 0-34 88f994da2aacb13f8bb898ef92705d43cb3b2578aec210c11060ecd138d015b8 book 1,053,399 77,568,606 35-39 2a5f14dde0dabc6ef440ff4442a414fa4375eef1ef570258fc54578d6929c4f1 last_trade_price 62,881 3,601,546 40-40 a61a65dea37dd6b5f9b6125c5680e6b35248f959aa006a0c35558d3ab5e45707 market_resolved 1,023 159,243 41-41 872d62b5be26fd34498fff9d8bbe85c9340eb3932f9bf83de6c471e8403d9375 new_market 2,482 249,725 42-42 e6d44b19c1ffbdad07a02242958a070ea211952925442c55957cea000c01950e price_change 87,799,824 862,311,035 43-377 418fd798fcfdbf3ef077b92829c7d56bea8c5720eae9cdd6544f33f9ed547da7 tick_size_change 3,700 136,094 378-378 53af9a205f0c3e9a6f315658b5fdc66c7919366f8da1b5c1d7c1e290d35a2876 EVENT MIX count share price_change 87,799,824 89.54% best_bid_ask 9,133,173 9.31% book 1,053,399 1.07% last_trade_price 62,881 0.06% tick_size_change 3,700 <0.01% new_market 2,482 <0.01% market_resolved 1,023 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,133,332 9,133,173 159 698 FULL book 1,053,407 1,053,399 8 175,867 FULL last_trade_price 62,881 62,881 0 71 FULL market_resolved 1,023 1,023 0 60 FULL new_market 2,482 2,482 0 7 FULL price_change 87,802,268 87,799,824 2,444 410 FULL tick_size_change 3,700 3,700 0 38 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,727,824 8,279,696 5ms 12ms 156ms 5.8s 0 transport_latency_assumed best_bid_ask e 9,126,768 45,067 39ms 47ms 235ms 8.1s 0 transport_latency_assumed best_bid_ask f 9,127,470 19,487 47ms 58ms 245ms 6.3s 0 transport_latency_assumed best_bid_ask g 9,127,119 1,996 83ms 105ms 487ms 9.9s 0 transport_latency_assumed best_bid_ask h 9,128,799 786,927 17ms 25ms 258ms 19.4s 0 transport_latency_assumed book c 672,572 634,820 8.7min 20.3h 27.9d 101.6d 0 book_staleness book e 429,187 129,049 2.5min 15.0h 26.7d 101.6d 0 book_staleness book f 423,110 121,495 2.3min 15.1h 26.7d 101.6d 0 book_staleness book g 141,901 7,139 88ms 1.8s 16.1h 83.1d 0 book_staleness book h 474,933 160,896 3.6min 16.2h 26.9d 101.6d 0 book_staleness last_trade_price c 60,513 57,071 11ms 47ms 264ms 5.0s 0 transport_latency_assumed last_trade_price e 62,523 651 45ms 149ms 3.7s 8.2s 0 transport_latency_assumed last_trade_price f 62,646 273 53ms 145ms 1.6s 6.4s 0 transport_latency_assumed last_trade_price g 62,570 76 94ms 241ms 3.6s 9.7s 0 transport_latency_assumed last_trade_price h 62,701 4,810 23ms 129ms 812ms 5.3s 0 transport_latency_assumed market_resolved c 924 885 5ms 21ms 4.6min 4.6min 0 transport_latency_assumed market_resolved e 984 9 40ms 189ms 495ms 621ms 0 transport_latency_assumed market_resolved f 984 5 48ms 213ms 505ms 820ms 0 transport_latency_assumed market_resolved g 984 not meas. 85ms 355ms 894ms 1.6s 0 transport_latency_assumed market_resolved h 984 124 17ms 94ms 188ms 1.2s 0 transport_latency_assumed new_market c 1,599 949 97ms 22.9s 3.9min 4.9min 0 transport_latency_assumed new_market e 1,606 306 167ms 18.1s 56.3s 1.4min 0 transport_latency_assumed new_market f 1,606 239 201ms 21.9s 59.8s 1.4min 0 transport_latency_assumed new_market g 1,606 134 299ms 19.8s 57.1s 1.3min 0 transport_latency_assumed new_market h 1,606 854 132ms 20.5s 1.1min 1.8min 0 transport_latency_assumed price_change c 84,274,437 79,827,765 5ms 13ms 169ms 5.9s 0 transport_latency_assumed price_change e 87,719,196 463,150 39ms 57ms 406ms 8.2s 0 transport_latency_assumed price_change f 87,720,660 201,678 47ms 66ms 359ms 6.4s 0 transport_latency_assumed price_change g 87,685,758 28,560 84ms 128ms 738ms 10.1s 0 transport_latency_assumed price_change h 87,744,638 7,278,671 17ms 30ms 310ms 19.4s 0 transport_latency_assumed tick_size_change c 3,552 3,362 5ms 11ms 244ms 670ms 0 transport_latency_assumed tick_size_change e 3,696 12 39ms 54ms 272ms 2.2s 0 transport_latency_assumed tick_size_change f 3,700 11 47ms 71ms 189ms 2.1s 0 transport_latency_assumed tick_size_change g 3,700 not meas. 83ms 105ms 485ms 4.9s 0 transport_latency_assumed tick_size_change h 3,700 315 17ms 27ms 86ms 1.2s 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-08/12/2026-09-08T12.parquet sha256sum 2026-09-08T12.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.