Hour audit: 2026-09-14T15
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-14T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T15:00:00.000978591+00:00 · last event 2026-09-14T15:59:59.999932203+00:00
VOLUME 116,736,304 rows · 1,284,257,438 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 113,638,744 · e: 113,551,852 · f: 113,549,588 · g: 113,091,366 · c: 76,038,791 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 41,983,630 (35.96%) · e: 2,638,193 (2.26%) · f: 1,003,788 (0.86%) · g: 106,862 (0.09%) · c: 71,003,831 (60.82%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 e115903eeda44c57c2195cd47e301f9db96cbceef712d578d4d1f2376b2e7a68
the corpus checksum ledger names this file with the same digest
joined 116,753,286 to merged 116,736,304, minus 16,982 (minus 0.0145%)
boundary drops 16,982 · 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-14T16:58:51Z 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 11,303,322 132,040,215 0-43 ef61d6012a8355cd4d81e90597b812ee69e7d132dfd60d9844ddee2838c2e8ed book 3,166,520 106,331,635 44-56 2ee889681b78eba2c05eb0aa59a024449ae5554657908d3704932b2293bdeba3 last_trade_price 62,817 3,689,199 57-57 39b03a5c703e6753fe0a8600b6f41c499fb8c6599e255f5d905631fbbac1c55a market_resolved 1,896 144,684 58-58 9d9a3192088d1b5bc66a04b4f9074cc13dde1287ea92bbc63d4ad40989241e0c new_market 10,367 707,518 59-59 9bf78128ccc54a3f027bfee9230f9a9037ff27dfb945a056feb3c96ad8be472e price_change 102,185,474 1,039,799,009 60-449 50abfe82af103fad6a2892b125ef8563149264dcd059b5da89a77a6392d94dbd tick_size_change 5,908 214,628 450-450 ec16a29ef60ba118a2b8bb9265bf6ec6cd9f1960dc09d0ed29fc0fa84c793d73 EVENT MIX count share price_change 102,185,474 87.54% best_bid_ask 11,303,322 9.68% book 3,166,520 2.71% last_trade_price 62,817 0.05% new_market 10,367 <0.01% tick_size_change 5,908 <0.01% market_resolved 1,896 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,304,632 11,303,322 1,310 7,973 FULL book 3,166,601 3,166,520 81 162,967 FULL last_trade_price 62,830 62,817 13 961 FULL market_resolved 1,896 1,896 0 42 FULL new_market 10,367 10,367 0 79 FULL price_change 102,201,052 102,185,474 15,578 4,290 FULL tick_size_change 5,908 5,908 0 484 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,253,957 6,757,754 6ms 19ms 203ms 3.6s 0 transport_latency_assumed best_bid_ask e 11,298,736 269,028 42ms 76ms 394ms 20.6s 0 transport_latency_assumed best_bid_ask f 11,298,698 98,424 49ms 88ms 423ms 23.9s 0 transport_latency_assumed best_bid_ask g 11,291,036 8,673 84ms 193ms 980ms 41.4s 0 transport_latency_assumed best_bid_ask h 11,301,036 4,169,443 19ms 41ms 452ms 47.2s 0 transport_latency_assumed book c 3,105,724 3,088,833 21.7min 2.9d 37.1d 107.7d 0 book_staleness book e 139,043 6,560 50ms 2.7s 1.4h 89.1d 0 book_staleness book f 140,679 5,254 59ms 2.6s 1.9h 89.2d 0 book_staleness book g 164,474 14,985 201ms 30.7min 7.2d 107.7d 0 book_staleness book h 138,339 50,888 25ms 212ms 2.2min 89.1d 0 book_staleness last_trade_price c 39,744 36,897 12ms 58ms 276ms 4.5s 0 transport_latency_assumed last_trade_price e 62,356 1,193 72ms 1.0s 11.8s 20.6s 0 transport_latency_assumed last_trade_price f 62,339 697 78ms 735ms 10.2s 24.2s 0 transport_latency_assumed last_trade_price g 60,278 114 126ms 2.6s 16.9s 41.4s 0 transport_latency_assumed last_trade_price h 62,623 23,916 26ms 106ms 718ms 31.4s 0 transport_latency_assumed market_resolved c 1,565 1,529 7.2min 16.4min 19.7min 19.8min 0 transport_latency_assumed market_resolved e 825 23 43ms 272ms 511ms 782ms 0 transport_latency_assumed market_resolved f 825 9 50ms 275ms 510ms 861ms 0 transport_latency_assumed market_resolved g 825 1 88ms 423ms 971ms 2.5s 0 transport_latency_assumed market_resolved h 825 334 20ms 104ms 488ms 1.4s 0 transport_latency_assumed new_market c 8,837 6,703 4.8min 11.9min 16.8min 22.7h 0 transport_latency_assumed new_market e 4,128 753 218ms 1.7min 4.4min 22.5h 0 transport_latency_assumed new_market f 4,135 893 209ms 2.1min 4.4min 1.5h 0 transport_latency_assumed new_market g 4,135 590 339ms 2.0min 4.5min 22.5h 0 transport_latency_assumed new_market h 4,135 1,428 143ms 1.6min 4.4min 1.5h 0 transport_latency_assumed price_change c 65,624,992 61,108,354 6ms 21ms 212ms 4.5s 0 transport_latency_assumed price_change e 102,040,856 2,360,536 42ms 117ms 2.5s 20.6s 0 transport_latency_assumed price_change f 102,037,004 898,472 49ms 128ms 1.6s 24.1s 0 transport_latency_assumed price_change g 101,564,710 82,490 84ms 294ms 6.7s 41.4s 0 transport_latency_assumed price_change h 102,125,878 37,735,622 19ms 47ms 476ms 47.5s 0 transport_latency_assumed tick_size_change c 3,972 3,761 6ms 14ms 149ms 373ms 0 transport_latency_assumed tick_size_change e 5,908 100 42ms 78ms 492ms 1.1s 0 transport_latency_assumed tick_size_change f 5,908 39 48ms 87ms 489ms 648ms 0 transport_latency_assumed tick_size_change g 5,908 9 82ms 191ms 736ms 11.6s 0 transport_latency_assumed tick_size_change h 5,908 1,999 19ms 38ms 347ms 1.7s 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-14/15/2026-09-14T15.parquet sha256sum 2026-09-14T15.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.