Hour audit: 2026-09-20T16
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-20T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-20T16:00:00.000023552+00:00 · last event 2026-09-20T16:59:59.999985052+00:00
VOLUME 137,918,520 rows · 1,541,106,240 bytes (1.44 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 135,451,524 · e: 135,206,805 · g: 129,730,574 · f: 115,578,419 · c: 106,326,778 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 32,789,841 (23.77%) · e: 3,867,934 (2.80%) · g: 264,086 (0.19%) · f: 1,081,175 (0.78%) · c: 99,915,484 (72.45%) (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 137,918,520 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 390f46685342e5e68eeb7c5abf4184667c89c34a41411da78700e81258fcfa49
the corpus checksum ledger names this file with the same digest
joined 137,926,914 to merged 137,918,520, minus 8,394 (minus 0.0061%)
boundary drops 8,394 · 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-20T18:40:28Z 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,237,007 157,149,048 0-50 cbeab3463d25c7d882b39e3923a2672e9b445c4d9624c993a46cdd2386917209 book 2,567,255 109,853,646 51-60 1e9f2557839ba728b4a122def3444df17be40a61de34ef9706d1a07e05a15a98 last_trade_price 83,939 4,899,057 61-61 63ef5726ba80b946f790157482796ae34e1830f1e30ee21622148563a3d646bc market_resolved 4,339 519,823 62-62 cbc18b98e4c11273e5a1b7234862eee006c88a1b83faff92024dcd5e6398029c new_market 3,480 324,277 63-63 114137bac5b7cb68415acb745d523d28cf180d6c717635aafdccf94abc990cd8 price_change 122,012,052 1,266,420,862 64-529 c4216c6e73a9e293701bd4f4ea20b751dad1d3e09e36d05033c2b00ed974175d tick_size_change 10,448 372,868 530-530 ddc006eb19ad3951e440b98f73d2b75083a0c009cfce64089e68d5fdac58a7ec EVENT MIX count share price_change 122,012,052 88.47% best_bid_ask 13,237,007 9.60% book 2,567,255 1.86% last_trade_price 83,939 0.06% tick_size_change 10,448 <0.01% market_resolved 4,339 <0.01% new_market 3,480 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,237,255 13,237,007 248 3,699 FULL book 2,571,665 2,567,255 4,410 164,826 FULL last_trade_price 83,939 83,939 0 815 FULL market_resolved 4,339 4,339 0 356 FULL new_market 3,480 3,480 0 141 FULL price_change 122,015,788 122,012,052 3,736 1,358 FULL tick_size_change 10,448 10,448 0 588 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,273,966 9,681,221 6ms 18ms 156ms 3.4s 0 transport_latency_assumed best_bid_ask e 13,230,774 383,127 42ms 66ms 342ms 26.6s 0 transport_latency_assumed best_bid_ask f 11,165,110 62,178 47ms 73ms 345ms 27.4s 0 transport_latency_assumed best_bid_ask g 12,681,361 6,980 81ms 137ms 842ms 36.3s 0 transport_latency_assumed best_bid_ask h 13,234,805 3,103,501 19ms 46ms 277ms 1.1min 0 transport_latency_assumed book c 2,168,110 1,985,220 5.2min 2.0d 43.0d 113.8d 0 book_staleness book e 175,702 9,887 47ms 2.6s 23.9min 95.2d 0 book_staleness book f 1,525,082 364,861 4.3min 2.0d 42.7d 113.8d 0 book_staleness book g 516,208 163,133 1.0min 1.1d 36.1d 113.7d 0 book_staleness book h 174,960 44,154 25ms 115ms 4.7min 95.3d 0 book_staleness last_trade_price c 62,910 59,084 7ms 26ms 224ms 2.6s 0 transport_latency_assumed last_trade_price e 82,834 2,378 48ms 728ms 11.7s 26.5s 0 transport_latency_assumed last_trade_price f 70,425 482 53ms 632ms 9.5s 27.4s 0 transport_latency_assumed last_trade_price g 76,375 88 90ms 825ms 13.3s 36.4s 0 transport_latency_assumed last_trade_price h 83,771 21,907 21ms 73ms 495ms 46.5s 0 transport_latency_assumed market_resolved c 3,355 3,142 7ms 6.8min 12.8min 14.7min 0 transport_latency_assumed market_resolved e 3,120 115 46ms 200ms 50.2s 1.0min 0 transport_latency_assumed market_resolved f 3,638 391 108ms 8.1min 15.7min 16.0min 0 transport_latency_assumed market_resolved g 3,112 71 90ms 372ms 2.9min 4.4min 0 transport_latency_assumed market_resolved h 3,120 620 30ms 89ms 50.4s 1.1min 0 transport_latency_assumed new_market c 2,049 1,529 65ms 1.5min 2.3h 12.7h 0 transport_latency_assumed new_market e 2,038 379 180ms 39.5s 2.1min 2.8h 0 transport_latency_assumed new_market f 2,233 494 184ms 2.3min 2.9h 12.7h 0 transport_latency_assumed new_market g 2,036 320 308ms 35.5s 1.9min 2.8min 0 transport_latency_assumed new_market h 2,038 758 130ms 45.6s 2.1min 4.1h 0 transport_latency_assumed price_change c 93,808,020 88,177,357 6ms 20ms 181ms 3.6s 0 transport_latency_assumed price_change e 121,701,889 3,471,916 42ms 93ms 2.7s 26.6s 0 transport_latency_assumed price_change f 102,802,455 652,722 47ms 98ms 1.9s 27.5s 0 transport_latency_assumed price_change g 116,441,174 93,494 82ms 198ms 4.6s 36.3s 0 transport_latency_assumed price_change h 121,942,382 29,616,563 19ms 51ms 338ms 1.1min 0 transport_latency_assumed tick_size_change c 8,368 7,931 5ms 14ms 125ms 302ms 0 transport_latency_assumed tick_size_change e 10,448 132 42ms 59ms 238ms 667ms 0 transport_latency_assumed tick_size_change f 9,476 47 46ms 59ms 216ms 667ms 0 transport_latency_assumed tick_size_change g 10,308 not meas. 80ms 112ms 443ms 16.8s 0 transport_latency_assumed tick_size_change h 10,448 2,338 19ms 31ms 142ms 13.6s 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-20/16/2026-09-20T16.parquet sha256sum 2026-09-20T16.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.