Hour audit: 2026-09-16T14
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-16T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T14:00:00.001043916+00:00 · last event 2026-09-16T14:59:59.999679732+00:00
VOLUME 116,354,307 rows · 1,252,260,382 bytes (1.17 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 115,855,226 · c: 115,819,884 · e: 115,681,877 · f: 115,676,351 · g: 115,267,589 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 5,677,306 (4.88%) · c: 109,532,731 (94.14%) · e: 686,471 (0.59%) · f: 352,586 (0.30%) · g: 105,213 (0.09%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 116,354,307 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 423314b6cd6fbc0b5c1e0a56b481ac33c3677b7cf45b950c5b4254f00dfb9568
the corpus checksum ledger names this file with the same digest
joined 116,358,349 to merged 116,354,307, minus 4,042 (minus 0.0035%)
boundary drops 4,042 · 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-16T16:00:25Z 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,177,217 141,550,005 0-46 6c5017667e580fe722e6bf4bbee01cfb082395eccd851428df7e98407660ebf0 book 662,138 59,297,785 47-49 086b1ce0ddd82cb6a7137fc9bd026d20f1b55e889417c089dc565c42e0afb570 last_trade_price 58,703 3,403,426 50-50 c6bee8c8849cff3e80abc9b9e7a0fe3f94ff51af0223f99c3cb9c43641cdb253 market_resolved 780 122,605 51-51 dde26f884d0b07c8ab343aa4ec4c2f6f7546abc59e6f456f93588e89661d5361 new_market 2,103 203,038 52-52 b302288ee0e98dae198bb73fe634f9227029f0800ad5b48454e2b95421b1372d price_change 103,449,274 1,046,212,291 53-447 e2d63b861be14a81181e970b47c83f798352c15fbd91ecc36accdf4e00d53ac6 tick_size_change 4,092 147,414 448-448 65a8f6ecd2b02ac90108e91998588a5f18020b6fd0ebc48cb4d76285913e0dca EVENT MIX count share price_change 103,449,274 88.91% best_bid_ask 12,177,217 10.47% book 662,138 0.57% last_trade_price 58,703 0.05% tick_size_change 4,092 <0.01% new_market 2,103 <0.01% market_resolved 780 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,177,513 12,177,217 296 295 FULL book 663,155 662,138 1,017 152,326 FULL last_trade_price 58,704 58,703 1 1 FULL market_resolved 780 780 0 0 FULL new_market 2,103 2,103 0 0 FULL price_change 103,452,002 103,449,274 2,728 116 FULL tick_size_change 4,092 4,092 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,175,069 11,546,024 5ms 14ms 122ms 6.4s 0 transport_latency_assumed best_bid_ask e 12,170,215 53,139 38ms 52ms 261ms 19.7s 0 transport_latency_assumed best_bid_ask f 12,170,542 20,647 45ms 61ms 295ms 21.1s 0 transport_latency_assumed best_bid_ask g 12,161,146 2,754 76ms 101ms 521ms 26.8s 0 transport_latency_assumed best_bid_ask h 12,169,937 554,653 18ms 36ms 212ms 1.5min 0 transport_latency_assumed book c 183,024 163,297 11ms 17.0min 16.9d 108.1d 0 book_staleness book e 281,814 133,995 16.0s 33.1min 25.0d 109.7d 0 book_staleness book f 275,557 128,735 12.9s 32.6min 25.0d 109.7d 0 book_staleness book g 192,026 56,834 337ms 21.7min 25.0d 109.7d 0 book_staleness book h 328,881 179,277 37.8s 48.5min 25.0d 109.7d 0 book_staleness last_trade_price c 58,438 55,288 11ms 51ms 252ms 5.0s 0 transport_latency_assumed last_trade_price e 57,617 237 58ms 561ms 6.0s 19.8s 0 transport_latency_assumed last_trade_price f 57,716 133 66ms 749ms 9.2s 21.1s 0 transport_latency_assumed last_trade_price g 56,421 73 99ms 1.2s 11.5s 27.0s 0 transport_latency_assumed last_trade_price h 58,383 2,972 26ms 117ms 652ms 50.6s 0 transport_latency_assumed market_resolved c 756 690 6ms 25ms 58.4s 58.4s 0 transport_latency_assumed market_resolved e 756 29 40ms 199ms 54.3s 54.4s 0 transport_latency_assumed market_resolved f 756 not meas. 46ms 202ms 54.4s 54.4s 0 transport_latency_assumed market_resolved g 756 24 78ms 231ms 659ms 2.1s 0 transport_latency_assumed market_resolved h 756 37 20ms 83ms 54.7s 54.8s 0 transport_latency_assumed new_market c 1,287 770 115ms 23.5s 50.4s 1.6min 0 transport_latency_assumed new_market e 1,287 245 216ms 22.1s 45.4s 1.4min 0 transport_latency_assumed new_market f 1,287 433 170ms 21.9s 44.3s 1.5min 0 transport_latency_assumed new_market g 1,287 174 327ms 24.6s 48.5s 58.2s 0 transport_latency_assumed new_market h 1,287 481 153ms 23.3s 46.0s 58.9s 0 transport_latency_assumed price_change c 103,397,218 97,762,772 6ms 17ms 154ms 6.4s 0 transport_latency_assumed price_change e 103,166,096 498,808 39ms 72ms 1.1s 20.1s 0 transport_latency_assumed price_change f 103,166,401 202,638 45ms 83ms 1.5s 21.1s 0 transport_latency_assumed price_change g 102,851,861 45,354 77ms 143ms 3.1s 28.1s 0 transport_latency_assumed price_change h 103,291,890 4,939,702 19ms 43ms 311ms 1.6min 0 transport_latency_assumed tick_size_change c 4,092 3,890 6ms 18ms 57ms 110ms 0 transport_latency_assumed tick_size_change e 4,092 18 39ms 50ms 137ms 4.8s 0 transport_latency_assumed tick_size_change f 4,092 not meas. 45ms 71ms 158ms 307ms 0 transport_latency_assumed tick_size_change g 4,092 not meas. 77ms 100ms 231ms 11.9s 0 transport_latency_assumed tick_size_change h 4,092 184 19ms 44ms 135ms 1.9s 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/14/2026-09-16T14.parquet sha256sum 2026-09-16T14.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.