Hour audit: 2026-09-19T12
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-19T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T12:00:00.000267313+00:00 · last event 2026-09-19T12:59:59.999957668+00:00
VOLUME 133,428,106 rows · 1,503,192,901 bytes (1.40 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 130,759,871 · e: 130,468,174 · g: 125,496,450 · f: 115,210,551 · c: 102,718,452 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 30,092,554 (22.55%) · e: 4,723,996 (3.54%) · g: 199,323 (0.15%) · f: 962,321 (0.72%) · c: 97,449,912 (73.04%) (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 133,428,106 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 87aae399d6aac06c6bb55cf786ae30b4ad95f9df0c1fd51c261824ffab715545
the corpus checksum ledger names this file with the same digest
joined 133,430,121 to merged 133,428,106, minus 2,015 (minus 0.0015%)
boundary drops 2,015 · 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-19T14:03:02Z 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,616,624 160,302,416 0-51 0114efac659931a1248b6206d1f2049da25531bce997f074d2a70e02c6b177d2 book 2,692,415 120,445,043 52-62 d6bfe6da6269b1df47c0c9eebedd0a56db26d16d6eaa121a7d97b7bd42738429 last_trade_price 67,891 3,985,733 63-63 bd20b60ba74bcf7311d537629ad5351db20dcdcd836b4e748adc1f64fb03e089 market_resolved 1,582 204,684 64-64 44442057073253026f2cef739a79325e02c1aa2f6abdc68767453c053161f3a9 new_market 1,084 101,739 65-65 b17a6b93d783a21c5ca140facb681d5acfe9b971e94bf5fff15ef2f8b02d40d9 price_change 117,040,634 1,216,348,734 66-512 9d1149d8b4b7f680ad0214768b653440f03f310dcb89debe2ea4759c0ec44944 tick_size_change 7,876 288,276 513-513 0994a8fb5b2cc08b2569f32d442126136d7510f829cc8399fa446ac5db46ec11 EVENT MIX count share price_change 117,040,634 87.72% best_bid_ask 13,616,624 10.21% book 2,692,415 2.02% last_trade_price 67,891 0.05% tick_size_change 7,876 <0.01% market_resolved 1,582 <0.01% new_market 1,084 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,616,802 13,616,624 178 7,289 FULL book 2,692,669 2,692,415 254 204,236 FULL last_trade_price 67,892 67,891 1 998 FULL market_resolved 1,582 1,582 0 85 FULL new_market 1,084 1,084 0 0 FULL price_change 117,042,216 117,040,634 1,582 6,040 FULL tick_size_change 7,876 7,876 0 525 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,444,641 9,927,788 5ms 13ms 121ms 5.1s 0 transport_latency_assumed best_bid_ask e 13,600,451 501,686 41ms 51ms 190ms 11.8s 0 transport_latency_assumed best_bid_ask f 11,786,915 52,247 48ms 58ms 188ms 3.8s 0 transport_latency_assumed best_bid_ask g 13,004,578 7,250 78ms 95ms 292ms 12.8s 0 transport_latency_assumed best_bid_ask h 13,611,681 3,127,653 18ms 46ms 156ms 19.9s 0 transport_latency_assumed book c 2,237,956 2,181,404 5.0min 20.3h 38.5d 112.6d 0 book_staleness book e 153,174 19,470 44ms 1.5s 25.7min 94.1d 0 book_staleness book f 1,402,933 355,574 4.3min 20.2h 37.7d 112.6d 0 book_staleness book g 590,008 98,847 2.0min 13.8h 28.0d 112.6d 0 book_staleness book h 147,349 37,120 23ms 123ms 18.9min 94.0d 0 book_staleness last_trade_price c 51,064 47,965 11ms 50ms 401ms 5.0s 0 transport_latency_assumed last_trade_price e 66,414 2,820 49ms 164ms 2.1s 11.7s 0 transport_latency_assumed last_trade_price f 58,768 675 57ms 182ms 1.5s 5.2s 0 transport_latency_assumed last_trade_price g 64,801 278 90ms 254ms 2.9s 7.8s 0 transport_latency_assumed last_trade_price h 67,314 16,153 26ms 90ms 600ms 8.3s 0 transport_latency_assumed market_resolved c 1,315 1,264 6ms 8.9min 15.4min 17.7min 0 transport_latency_assumed market_resolved e 1,233 51 43ms 196ms 15.8s 1.2min 0 transport_latency_assumed market_resolved f 1,310 128 53ms 3.3min 9.9min 10.9min 0 transport_latency_assumed market_resolved g 1,198 3 83ms 251ms 992ms 5.8min 0 transport_latency_assumed market_resolved h 1,233 136 20ms 77ms 216ms 55.6s 0 transport_latency_assumed new_market c 750 483 140ms 6.4min 10.2min 12.4min 0 transport_latency_assumed new_market e 644 95 193ms 19.1s 34.6s 1.1min 0 transport_latency_assumed new_market f 696 173 243ms 5.6min 36.2min 37.0min 0 transport_latency_assumed new_market g 644 75 297ms 18.1s 32.4s 2.0min 0 transport_latency_assumed new_market h 644 258 124ms 16.3s 36.7s 2.3min 0 transport_latency_assumed price_change c 89,976,526 85,285,030 5ms 15ms 145ms 5.3s 0 transport_latency_assumed price_change e 116,638,382 4,199,713 41ms 58ms 389ms 11.8s 0 transport_latency_assumed price_change f 101,953,153 553,518 48ms 65ms 311ms 6.8s 0 transport_latency_assumed price_change g 111,827,429 92,870 78ms 104ms 487ms 15.2s 0 transport_latency_assumed price_change h 116,923,774 26,909,503 18ms 50ms 219ms 20.0s 0 transport_latency_assumed tick_size_change c 6,200 5,978 5ms 11ms 47ms 237ms 0 transport_latency_assumed tick_size_change e 7,876 161 41ms 49ms 126ms 295ms 0 transport_latency_assumed tick_size_change f 6,776 6 48ms 59ms 122ms 264ms 0 transport_latency_assumed tick_size_change g 7,792 not meas. 78ms 91ms 191ms 352ms 0 transport_latency_assumed tick_size_change h 7,876 1,731 18ms 41ms 89ms 4.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-19/12/2026-09-19T12.parquet sha256sum 2026-09-19T12.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.