Hour audit: 2026-09-15T22
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-15T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T22:00:00.000075521+00:00 · last event 2026-09-15T22:59:59.999914783+00:00
VOLUME 115,876,878 rows · 1,209,148,288 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 115,148,299 · h: 115,140,935 · e: 115,110,085 · f: 115,094,130 · c: 110,838,589 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 318,675 (0.28%) · h: 8,858,378 (7.64%) · e: 502,115 (0.43%) · f: 236,845 (0.20%) · c: 105,960,865 (91.44%) (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 115,876,878 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f636425b5f194976a8d4a81beb959f02b38e8be4802d4f9a97fcadf3f94fd0fb
the corpus checksum ledger names this file with the same digest
joined 115,878,831 to merged 115,876,878, minus 1,953 (minus 0.0017%)
boundary drops 1,953 · 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-15T23:59:37Z 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,568,384 144,003,269 0-47 1ab020738b712af7d6f86583df43ef10d8392c857101972e3163ace15bd2d12d book 784,592 63,353,186 48-50 11e1aac8705f0df13e49d77d0764cc7fafc1e51f05bdd8008f0e738c568f7c29 last_trade_price 47,070 2,707,575 51-51 805d9253f6a2c0c91c9424a297b02b3d083e0acfda30ac8d2f685d9c19bc18b9 market_resolved 2,652 408,930 52-52 e9baaf5c521be7932abe51b6736300a3e8861a420f1c0d01528d937d4454103f new_market 1,652 168,994 53-53 476fc06d23b0c8b7b8214bf1bfaf50872bced7f6f258314c000a36cef79e98c0 price_change 102,469,740 997,088,187 54-444 0e97f71f695c8ed0c7251c201555496238f879aaf100c5c4948553cbc4c61404 tick_size_change 2,788 102,509 445-445 b8a6767aa03316e0523d78055319ef00131f2b6a0a8e76fb593d2615d1b78ad7 EVENT MIX count share price_change 102,469,740 88.43% best_bid_ask 12,568,384 10.85% book 784,592 0.68% last_trade_price 47,070 0.04% tick_size_change 2,788 <0.01% market_resolved 2,652 <0.01% new_market 1,652 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,568,530 12,568,384 146 440 FULL book 784,726 784,592 134 177,191 FULL last_trade_price 47,073 47,070 3 62 FULL market_resolved 2,652 2,652 0 17 FULL new_market 1,652 1,652 0 0 FULL price_change 102,471,410 102,469,740 1,670 127 FULL tick_size_change 2,788 2,788 0 29 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,048,322 11,552,746 5ms 11ms 102ms 3.3s 0 transport_latency_assumed best_bid_ask e 12,565,631 49,051 39ms 50ms 221ms 13.7s 0 transport_latency_assumed best_bid_ask f 12,565,621 20,967 44ms 59ms 220ms 14.2s 0 transport_latency_assumed best_bid_ask g 12,558,051 2,169 81ms 105ms 428ms 45.0s 0 transport_latency_assumed best_bid_ask h 12,566,538 943,451 18ms 29ms 158ms 46.3s 0 transport_latency_assumed book c 480,453 417,541 2.2min 17.9h 35.1d 109.0d 0 book_staleness book e 130,423 24,524 58ms 10.8min 10.3d 109.0d 0 book_staleness book f 130,548 24,588 63ms 11.4min 10.3d 109.0d 0 book_staleness book g 466,718 296,224 2.2min 14.6h 34.3d 109.0d 0 book_staleness book h 115,804 21,715 23ms 1.7min 6.6d 109.0d 0 book_staleness last_trade_price c 44,521 42,061 10ms 50ms 243ms 4.9s 0 transport_latency_assumed last_trade_price e 46,745 230 55ms 451ms 5.0s 13.7s 0 transport_latency_assumed last_trade_price f 46,693 246 61ms 315ms 3.8s 14.0s 0 transport_latency_assumed last_trade_price g 45,711 35 102ms 777ms 9.4s 45.0s 0 transport_latency_assumed last_trade_price h 46,861 4,498 24ms 102ms 525ms 23.5s 0 transport_latency_assumed market_resolved c 2,623 2,563 5ms 14ms 5.7min 6.0min 0 transport_latency_assumed market_resolved e 2,575 2 107ms 191ms 545ms 48.7s 0 transport_latency_assumed market_resolved f 2,575 1 114ms 198ms 546ms 48.7s 0 transport_latency_assumed market_resolved g 2,574 not meas. 207ms 356ms 799ms 1.7s 0 transport_latency_assumed market_resolved h 2,575 86 37ms 78ms 413ms 1.3min 0 transport_latency_assumed new_market c 1,086 784 81ms 21.8s 1.0min 2.8min 0 transport_latency_assumed new_market e 1,081 172 205ms 19.5s 50.0s 1.1min 0 transport_latency_assumed new_market f 1,081 195 184ms 20.5s 49.9s 1.0min 0 transport_latency_assumed new_market g 1,081 79 284ms 22.1s 49.2s 1.7min 0 transport_latency_assumed new_market h 1,081 422 128ms 21.4s 53.2s 1.0min 0 transport_latency_assumed price_change c 98,258,912 93,942,578 5ms 13ms 118ms 3.4s 0 transport_latency_assumed price_change e 102,360,842 428,128 39ms 65ms 660ms 15.1s 0 transport_latency_assumed price_change f 102,344,824 190,848 45ms 73ms 563ms 14.2s 0 transport_latency_assumed price_change g 102,071,376 20,168 82ms 134ms 1.7s 47.0s 0 transport_latency_assumed price_change h 102,405,288 7,888,018 18ms 35ms 227ms 47.1s 0 transport_latency_assumed tick_size_change c 2,672 2,592 5ms 9ms 44ms 345ms 0 transport_latency_assumed tick_size_change e 2,788 8 39ms 44ms 117ms 219ms 0 transport_latency_assumed tick_size_change f 2,788 not meas. 44ms 50ms 116ms 390ms 0 transport_latency_assumed tick_size_change g 2,788 not meas. 81ms 96ms 187ms 503ms 0 transport_latency_assumed tick_size_change h 2,788 188 18ms 24ms 67ms 400ms 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-15/22/2026-09-15T22.parquet sha256sum 2026-09-15T22.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.