Hour audit: 2026-09-16T15
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-16T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T15:00:00.000004965+00:00 · last event 2026-09-16T15:59:59.999763857+00:00
VOLUME 121,794,178 rows · 1,314,822,772 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 120,983,543 · h: 120,973,966 · f: 116,865,523 · c: 116,189,267 · g: 116,086,670 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,357,597 (1.11%) · h: 10,216,192 (8.39%) · f: 623,644 (0.51%) · c: 109,398,545 (89.82%) · g: 198,200 (0.16%) (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 121,794,178 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 869c752dd1c94174a5457e17fa63b5e422190730d2df7e3bd740b2b96d2cea05
the corpus checksum ledger names this file with the same digest
joined 121,798,139 to merged 121,794,178, minus 3,961 (minus 0.0033%)
boundary drops 3,961 · 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-16T17:01:08Z 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,247,106 143,943,758 0-46 57c986d2854f54d5fb7024284d69204b1d370ba5140c6870897439da5a92fe99 book 866,380 69,466,966 47-50 ff85626f3c05d948d87cfd2426911049ddce893a5b1c79acef91179baae69125 last_trade_price 58,371 3,392,066 51-51 e60d4bfbfe23e8d956a62cdc7fc345fed415ea73d01816d21d6f1b6fffc8e99a market_resolved 832 122,946 52-52 3737699fe5c9f246c71dfeb8071a2219c431ef2f32fd89a6dd101072d8988c7c new_market 2,701 277,315 53-53 909f7eaeb78d556422edf011f0cb90ca34cd0b489c52193981d6518293ccc41c price_change 108,615,228 1,096,102,809 54-468 a10f1184a2786b5cf796b64864f15a6d4d4368ff2964aaba54e5d7d3c7e8d24b tick_size_change 3,560 130,748 469-469 2cbc339277a8a5b649500e423fa7abfd0c76fb86f99d7f144dc456176256badd EVENT MIX count share price_change 108,615,228 89.18% best_bid_ask 12,247,106 10.06% book 866,380 0.71% last_trade_price 58,371 0.05% tick_size_change 3,560 <0.01% new_market 2,701 <0.01% market_resolved 832 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,247,262 12,247,106 156 917 FULL book 868,468 866,380 2,088 170,474 FULL last_trade_price 58,372 58,371 1 224 FULL market_resolved 832 832 0 21 FULL new_market 2,701 2,701 0 0 FULL price_change 108,616,944 108,615,228 1,716 153 FULL tick_size_change 3,560 3,560 0 67 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,697,220 11,026,355 6ms 16ms 166ms 4.7s 0 transport_latency_assumed best_bid_ask e 12,244,179 141,100 40ms 57ms 295ms 15.0s 0 transport_latency_assumed best_bid_ask f 11,794,944 45,925 44ms 64ms 316ms 10.9s 0 transport_latency_assumed best_bid_ask g 11,761,024 2,786 79ms 113ms 695ms 23.1s 0 transport_latency_assumed best_bid_ask h 12,242,439 1,030,940 20ms 37ms 272ms 50.9s 0 transport_latency_assumed book c 499,666 457,502 1.5min 15.8h 34.8d 109.7d 0 book_staleness book e 159,141 26,264 62ms 7.6min 9.2d 109.7d 0 book_staleness book f 503,011 161,221 2.2min 13.8h 34.8d 109.7d 0 book_staleness book g 499,329 168,823 1.8min 14.2h 34.9d 109.7d 0 book_staleness book h 182,940 52,570 43ms 14.4min 13.9d 109.7d 0 book_staleness last_trade_price c 55,077 51,703 11ms 57ms 297ms 5.0s 0 transport_latency_assumed last_trade_price e 58,200 727 59ms 479ms 5.4s 15.0s 0 transport_latency_assumed last_trade_price f 56,215 341 64ms 487ms 5.5s 11.0s 0 transport_latency_assumed last_trade_price g 54,196 24 103ms 1.4s 15.3s 23.1s 0 transport_latency_assumed last_trade_price h 57,766 5,576 28ms 116ms 781ms 29.3s 0 transport_latency_assumed market_resolved c 748 712 6ms 30ms 2.4min 4.2min 0 transport_latency_assumed market_resolved e 756 7 42ms 249ms 632ms 1.0s 0 transport_latency_assumed market_resolved f 756 52 46ms 467ms 4.4min 4.9min 0 transport_latency_assumed market_resolved g 755 13 86ms 561ms 5.2min 5.2min 0 transport_latency_assumed market_resolved h 756 48 21ms 89ms 313ms 3.6s 0 transport_latency_assumed new_market c 1,799 1,004 121ms 4.5min 4.6min 4.7min 0 transport_latency_assumed new_market e 1,799 483 235ms 4.5min 4.6min 4.7min 0 transport_latency_assumed new_market f 1,799 238 222ms 4.5min 4.6min 4.7min 0 transport_latency_assumed new_market g 1,799 170 326ms 4.4min 4.6min 4.7min 0 transport_latency_assumed new_market h 1,799 806 143ms 4.5min 4.6min 4.6min 0 transport_latency_assumed price_change c 103,931,273 97,858,064 6ms 18ms 172ms 4.9s 0 transport_latency_assumed price_change e 108,515,908 1,188,992 41ms 75ms 1.0s 15.0s 0 transport_latency_assumed price_change f 104,505,334 415,860 44ms 83ms 1.2s 10.9s 0 transport_latency_assumed price_change g 103,766,103 26,384 80ms 157ms 4.2s 23.1s 0 transport_latency_assumed price_change h 108,484,706 9,125,928 20ms 43ms 355ms 50.9s 0 transport_latency_assumed tick_size_change c 3,484 3,205 6ms 36ms 251ms 838ms 0 transport_latency_assumed tick_size_change e 3,560 24 41ms 92ms 457ms 725ms 0 transport_latency_assumed tick_size_change f 3,464 7 44ms 73ms 478ms 747ms 0 transport_latency_assumed tick_size_change g 3,464 not meas. 80ms 215ms 871ms 2.7s 0 transport_latency_assumed tick_size_change h 3,560 324 20ms 43ms 407ms 6.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-16/15/2026-09-16T15.parquet sha256sum 2026-09-16T15.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.