Hour audit: 2026-09-16T22
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-16T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T22:00:00.000213287+00:00 · last event 2026-09-16T22:59:59.999895395+00:00
VOLUME 113,188,105 rows · 1,156,869,964 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 112,721,597 · e: 112,719,537 · c: 112,715,625 · h: 112,708,182 · g: 112,701,320 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 233,353 (0.21%) · e: 407,035 (0.36%) · c: 108,910,673 (96.22%) · h: 3,480,341 (3.07%) · g: 156,703 (0.14%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 113,188,105 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f629c6e4ae5637f5fe698f2eca42725c5265a70009e4c8c5ef506e6a34284a03
the corpus checksum ledger names this file with the same digest
joined 113,190,986 to merged 113,188,105, minus 2,881 (minus 0.0025%)
boundary drops 2,881 · 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-16T23:59: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 13,160,046 147,111,624 0-50 2f9a8067c2e26bf35146119f4aefcc78192fb11828a571cec2c0bde881d0e837 book 642,157 55,113,045 51-53 df3ec4b03f7af677e2069bf36c0df600c7e5c6dabfb7bc43ffbfd1cce634c134 last_trade_price 40,742 2,428,455 54-54 0314190e4ac00fd5bcff6612640d246a47cd13a43ca90974258f841f43bced6d market_resolved 1,797 286,179 55-55 21c6106516f15ae99fbb03ca1b88408c96198352415955485b540f5f657dd472 new_market 1,887 187,830 56-56 764cb2aad36d911302b44bc5c7ba21a74ed88d4e8d85187e1b54f25a42b7932d price_change 99,338,384 950,341,838 57-435 64f1f19159709420a0a6aeeed93a68d4897e7e2fa7ca641f48b4439f9cfb0107 tick_size_change 3,092 112,706 436-436 82063cfb72f5b9f75d2c028335087e476301b7da19a770674efa9397156fd62e EVENT MIX count share price_change 99,338,384 87.76% best_bid_ask 13,160,046 11.63% book 642,157 0.57% last_trade_price 40,742 0.04% tick_size_change 3,092 <0.01% new_market 1,887 <0.01% market_resolved 1,797 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,160,315 13,160,046 269 197 FULL book 642,841 642,157 684 156,309 FULL last_trade_price 40,742 40,742 0 3 FULL market_resolved 1,797 1,797 0 0 FULL new_market 1,887 1,887 0 0 FULL price_change 99,340,312 99,338,384 1,928 59 FULL tick_size_change 3,092 3,092 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,158,565 12,735,151 5ms 8ms 100ms 7.1s 0 transport_latency_assumed best_bid_ask e 13,156,674 34,659 38ms 46ms 189ms 8.4s 0 transport_latency_assumed best_bid_ask f 13,156,652 14,535 45ms 54ms 212ms 17.7s 0 transport_latency_assumed best_bid_ask g 13,155,287 2,625 80ms 97ms 345ms 7.3s 0 transport_latency_assumed best_bid_ask h 13,156,678 373,076 18ms 23ms 154ms 39.8s 0 transport_latency_assumed book c 186,639 163,313 7.1s 31.8min 25.4d 110.0d 0 book_staleness book e 227,709 117,718 32.3s 50.5min 25.4d 110.0d 0 book_staleness book f 219,801 109,450 28.7s 59.8min 25.4d 110.0d 0 book_staleness book g 250,660 136,692 50.2s 2.1h 25.4d 110.0d 0 book_staleness book h 226,737 114,984 33.3s 1.4h 25.4d 110.0d 0 book_staleness last_trade_price c 40,690 39,121 10ms 43ms 222ms 5.0s 0 transport_latency_assumed last_trade_price e 40,693 146 48ms 147ms 1.3s 5.0s 0 transport_latency_assumed last_trade_price f 40,685 61 56ms 165ms 1.1s 5.0s 0 transport_latency_assumed last_trade_price g 40,622 14 93ms 239ms 2.2s 7.0s 0 transport_latency_assumed last_trade_price h 40,588 1,400 23ms 73ms 431ms 26.0s 0 transport_latency_assumed market_resolved c 1,770 1,732 5ms 10ms 290ms 880ms 0 transport_latency_assumed market_resolved e 1,770 1 112ms 204ms 55.5s 58.2s 0 transport_latency_assumed market_resolved f 1,770 not meas. 119ms 212ms 961ms 59.1s 0 transport_latency_assumed market_resolved g 1,770 not meas. 205ms 366ms 1.4s 1.0min 0 transport_latency_assumed market_resolved h 1,770 64 39ms 80ms 54.5s 57.2s 0 transport_latency_assumed new_market c 1,195 784 91ms 26.3s 47.1s 5.1min 0 transport_latency_assumed new_market e 1,195 203 203ms 25.6s 47.4s 3.7min 0 transport_latency_assumed new_market f 1,195 217 190ms 23.4s 49.9s 2.2min 0 transport_latency_assumed new_market g 1,195 126 275ms 27.3s 54.0s 1.1min 0 transport_latency_assumed new_market h 1,195 557 138ms 20.4s 54.1s 13.8min 0 transport_latency_assumed price_change c 99,323,678 95,967,510 5ms 9ms 106ms 7.4s 0 transport_latency_assumed price_change e 99,288,408 254,308 39ms 50ms 294ms 8.8s 0 transport_latency_assumed price_change f 99,298,402 109,090 45ms 60ms 319ms 20.1s 0 transport_latency_assumed price_change g 99,248,694 17,246 81ms 103ms 488ms 8.1s 0 transport_latency_assumed price_change h 99,278,122 2,990,230 18ms 25ms 200ms 40.2s 0 transport_latency_assumed tick_size_change c 3,088 3,062 5ms 7ms 17ms 220ms 0 transport_latency_assumed tick_size_change e 3,088 not meas. 38ms 43ms 116ms 314ms 0 transport_latency_assumed tick_size_change f 3,092 not meas. 45ms 49ms 85ms 248ms 0 transport_latency_assumed tick_size_change g 3,092 not meas. 79ms 95ms 223ms 593ms 0 transport_latency_assumed tick_size_change h 3,092 30 18ms 26ms 128ms 586ms 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-16/22/2026-09-16T22.parquet sha256sum 2026-09-16T22.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.