Hour audit: 2026-09-14T01
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-14T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T01:00:00.000049494+00:00 · last event 2026-09-14T01:59:59.999790886+00:00
VOLUME 116,075,680 rows · 1,195,094,103 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 115,466,478 · h: 115,261,587 · f: 111,399,650 · g: 111,197,835 · c: 110,873,816 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 489,126 (0.42%) · h: 9,008,118 (7.76%) · f: 256,605 (0.22%) · g: 47,622 (0.04%) · c: 106,274,209 (91.56%) (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,075,680 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d19aa8a15d1803a075fb152192414c4e6f13ec704e0f678420dd165e2bd67024
the corpus checksum ledger names this file with the same digest
joined 116,081,046 to merged 116,075,680, minus 5,366 (minus 0.0046%)
boundary drops 5,366 · 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-14T02:59:20Z 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,303,243 130,773,020 0-46 33542609de75bddeaa04a4c3f4d5be463163145ceb8701636afb98458196a16c book 581,017 55,029,989 47-49 c207a13cde6f74f2b16181003d924805bb08be60e2a38c10a6d9f30e42518c85 last_trade_price 47,737 2,677,766 50-50 7ad6eb3b87b11a6f7bb963b67ab28257b444542ff956a6f67e19951463b5f06f market_resolved 1,170 170,331 51-51 17bc97b27b870641a0014af446d629815d97647c829ac8f045307598f700e5e2 new_market 621 64,147 52-52 f5af2b5dfa874cd9f7ca7e663c5c925a7fb2e8bb639496500d76f2f09d401fee price_change 103,139,220 1,004,959,562 53-446 1040738790881fdf294aef51d71096fae4aa129ad9a29abbc1218c0624eab3a0 tick_size_change 2,672 98,226 447-447 ebc669b5ac5c54d70133a0007c7c978c1fed0baf121f2551fc439b1716c3d238 EVENT MIX count share price_change 103,139,220 88.86% best_bid_ask 12,303,243 10.60% book 581,017 0.50% last_trade_price 47,737 0.04% tick_size_change 2,672 <0.01% market_resolved 1,170 <0.01% new_market 621 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,303,553 12,303,243 310 650 FULL book 581,023 581,017 6 165,480 FULL last_trade_price 47,737 47,737 0 119 FULL market_resolved 1,170 1,170 0 18 FULL new_market 621 621 0 0 FULL price_change 103,144,270 103,139,220 5,050 581 FULL tick_size_change 2,672 2,672 0 60 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,783,560 11,335,077 4ms 9ms 73ms 18.2s 0 transport_latency_assumed best_bid_ask e 12,301,470 44,792 39ms 45ms 117ms 5.8s 0 transport_latency_assumed best_bid_ask f 11,834,857 13,105 47ms 55ms 139ms 18.0s 0 transport_latency_assumed best_bid_ask g 11,813,857 950 83ms 109ms 257ms 9.5s 0 transport_latency_assumed best_bid_ask h 12,292,723 909,319 17ms 25ms 90ms 27.1s 0 transport_latency_assumed book c 435,203 423,418 6.7min 1.4d 33.3d 107.1d 0 book_staleness book e 102,702 3,547 41ms 122ms 5.5h 88.6d 0 book_staleness book f 433,330 101,650 7.0min 1.4d 33.3d 107.1d 0 book_staleness book g 454,279 32,829 8.3min 1.5d 33.3d 107.1d 0 book_staleness book h 108,289 19,573 20ms 221ms 1.1h 21.0h 0 book_staleness last_trade_price c 45,558 42,807 10ms 49ms 232ms 5.0s 0 transport_latency_assumed last_trade_price e 47,507 387 46ms 112ms 814ms 5.9s 0 transport_latency_assumed last_trade_price f 45,980 144 54ms 107ms 498ms 5.0s 0 transport_latency_assumed last_trade_price g 45,860 70 93ms 188ms 551ms 9.6s 0 transport_latency_assumed last_trade_price h 46,778 4,329 23ms 64ms 283ms 5.9s 0 transport_latency_assumed market_resolved c 1,046 1,005 5ms 200ms 4.4min 4.9min 0 transport_latency_assumed market_resolved e 1,047 5 41ms 118ms 285ms 768ms 0 transport_latency_assumed market_resolved f 1,045 13 48ms 130ms 5.4min 5.4min 0 transport_latency_assumed market_resolved g 1,029 not meas. 87ms 242ms 1.2s 59.8s 0 transport_latency_assumed market_resolved h 1,047 147 17ms 47ms 31.6s 1.0min 0 transport_latency_assumed new_market c 400 293 54ms 16.6s 10.9min 2.7h 0 transport_latency_assumed new_market e 400 52 157ms 15.7s 11.8min 1.8h 0 transport_latency_assumed new_market f 403 61 151ms 14.2s 1.2h 4.3h 0 transport_latency_assumed new_market g 400 51 198ms 2.0s 36.3min 2.4h 0 transport_latency_assumed new_market h 400 164 66ms 15.8s 11.1min 4.5h 0 transport_latency_assumed price_change c 98,605,477 94,469,077 5ms 11ms 84ms 18.7s 0 transport_latency_assumed price_change e 103,010,680 440,332 40ms 48ms 156ms 5.9s 0 transport_latency_assumed price_change f 99,081,503 141,632 47ms 59ms 172ms 18.2s 0 transport_latency_assumed price_change g 98,879,878 13,722 84ms 117ms 304ms 9.6s 0 transport_latency_assumed price_change h 102,809,678 8,074,457 17ms 28ms 104ms 31.4s 0 transport_latency_assumed tick_size_change c 2,572 2,532 4ms 6ms 23ms 74ms 0 transport_latency_assumed tick_size_change e 2,672 11 39ms 42ms 103ms 291ms 0 transport_latency_assumed tick_size_change f 2,532 not meas. 46ms 50ms 90ms 169ms 0 transport_latency_assumed tick_size_change g 2,532 not meas. 80ms 94ms 148ms 349ms 0 transport_latency_assumed tick_size_change h 2,672 129 17ms 21ms 57ms 181ms 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/01/2026-09-14T01.parquet sha256sum 2026-09-14T01.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.