Hour audit: 2026-09-18T21
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-18T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T21:00:00.000422846+00:00 · last event 2026-09-18T21:59:59.999982785+00:00
VOLUME 100,049,865 rows · 1,074,909,538 bytes (1.00 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 99,479,003 · e: 99,434,918 · f: 99,402,384 · h: 99,186,479 · g: 98,985,118 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 94,563,189 (94.52%) · e: 741,204 (0.74%) · f: 504,203 (0.50%) · h: 4,150,924 (4.15%) · g: 90,345 (0.09%) (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 100,049,865 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e8d07107007ef58be785942cddbeda05a330a60bb4cc5292f2979c60fb6269aa
the corpus checksum ledger names this file with the same digest
joined 100,053,489 to merged 100,049,865, minus 3,624 (minus 0.0036%)
boundary drops 3,624 · 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-19T01:34:43Z 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,331,166 146,307,131 0-50 de8b9fa7ff477cf05c8544240b7d8dd432e0e583c94448674a06adf4a842c6cb book 909,957 68,151,733 51-54 4a1a090f5e3c182be924ed597f05d554800a7f4c20d81a3319ae119c7a35ff02 last_trade_price 47,779 2,758,134 55-55 09d4165c30da73f6960e43cdf7398be31b32430c6225b34bf006e51b722b31cb market_resolved 2,171 353,503 56-56 8a9d07a66fac49787c286e544859080f0ebe7d9797f086b000e460a46d212138 new_market 1,866 194,133 57-57 e4c1be4ca78c73a3055fe1b6e9a9a612d3c8d523a5c6259079916668c66fe433 price_change 85,754,354 855,909,801 58-385 ca63e9b0db5aa712ea2a84a2ef18376c486ab94948232d78d17478f44c7dd10a tick_size_change 2,572 94,532 386-386 e1f73d8bfa958af45c7f18b7479498eb32e32fd6bdfa0e3984314b2e1ad77842 EVENT MIX count share price_change 85,754,354 85.71% best_bid_ask 13,331,166 13.32% book 909,957 0.91% last_trade_price 47,779 0.05% tick_size_change 2,572 <0.01% market_resolved 2,171 <0.01% new_market 1,866 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,331,469 13,331,166 303 242 FULL book 910,675 909,957 718 198,949 FULL last_trade_price 47,780 47,779 1 0 FULL market_resolved 2,171 2,171 0 7 FULL new_market 1,866 1,866 0 0 FULL price_change 85,756,956 85,754,354 2,602 430 FULL tick_size_change 2,572 2,572 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,328,822 12,721,512 5ms 11ms 141ms 6.5s 0 transport_latency_assumed best_bid_ask e 13,326,201 63,337 41ms 50ms 214ms 6.3s 0 transport_latency_assumed best_bid_ask f 13,326,101 35,149 46ms 56ms 231ms 10.5s 0 transport_latency_assumed best_bid_ask g 13,326,502 3,339 79ms 101ms 439ms 55.7s 0 transport_latency_assumed best_bid_ask h 13,324,972 507,829 17ms 29ms 198ms 39.3s 0 transport_latency_assumed book c 384,713 259,818 5.4min 6.2h 27.3d 112.0d 0 book_staleness book e 461,657 246,278 8.0min 6.2h 27.3d 112.0d 0 book_staleness book f 439,488 219,860 7.4min 6.2h 27.3d 112.0d 0 book_staleness book g 244,766 62,803 55.0s 6.1h 27.3d 112.0d 0 book_staleness book h 356,982 121,198 4.6min 6.2h 27.3d 112.0d 0 book_staleness last_trade_price c 47,520 45,064 10ms 50ms 273ms 4.9s 0 transport_latency_assumed last_trade_price e 47,449 311 58ms 488ms 3.3s 6.3s 0 transport_latency_assumed last_trade_price f 47,472 239 62ms 444ms 6.1s 10.5s 0 transport_latency_assumed last_trade_price g 47,275 30 101ms 1.0s 11.4s 20.2s 0 transport_latency_assumed last_trade_price h 47,254 2,135 24ms 118ms 654ms 5.6s 0 transport_latency_assumed market_resolved c 2,156 2,066 5ms 15ms 370ms 56.0s 0 transport_latency_assumed market_resolved e 2,153 14 59ms 267ms 676ms 55.1s 0 transport_latency_assumed market_resolved f 2,153 9 62ms 278ms 579ms 1.0min 0 transport_latency_assumed market_resolved g 2,153 12 97ms 440ms 907ms 2.0s 0 transport_latency_assumed market_resolved h 2,153 70 29ms 103ms 1.0s 55.6s 0 transport_latency_assumed new_market c 1,236 716 86ms 24.5s 1.5min 8.8min 0 transport_latency_assumed new_market e 1,236 239 143ms 25.3s 1.5min 2.1min 0 transport_latency_assumed new_market f 1,236 172 180ms 25.3s 1.4min 2.1min 0 transport_latency_assumed new_market g 1,236 187 272ms 25.6s 1.5min 13.1min 0 transport_latency_assumed new_market h 1,236 552 125ms 23.9s 1.3min 2.0min 0 transport_latency_assumed price_change c 85,711,984 81,531,582 5ms 13ms 166ms 7.1s 0 transport_latency_assumed price_change e 85,593,654 431,005 42ms 70ms 898ms 7.6s 0 transport_latency_assumed price_change f 85,583,366 248,762 47ms 76ms 924ms 10.6s 0 transport_latency_assumed price_change g 85,360,614 23,974 80ms 154ms 3.1s 57.2s 0 transport_latency_assumed price_change h 85,451,310 3,519,031 18ms 37ms 296ms 41.6s 0 transport_latency_assumed tick_size_change c 2,572 2,431 5ms 15ms 192ms 380ms 0 transport_latency_assumed tick_size_change e 2,568 20 41ms 53ms 269ms 585ms 0 transport_latency_assumed tick_size_change f 2,568 12 47ms 70ms 209ms 411ms 0 transport_latency_assumed tick_size_change g 2,572 not meas. 79ms 98ms 675ms 1.9s 0 transport_latency_assumed tick_size_change h 2,572 109 18ms 34ms 203ms 3.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-18/21/2026-09-18T21.parquet sha256sum 2026-09-18T21.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.