Hour audit: 2026-09-12T09
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-12T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T09:00:00.000020885+00:00 · last event 2026-09-12T09:59:59.999976934+00:00
VOLUME 120,553,506 rows · 1,280,996,043 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 115,748,123 · f: 115,709,918 · e: 115,705,751 · g: 115,543,899 · c: 59,387,073 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 59,469,521 (49.33%) · f: 377,178 (0.31%) · e: 3,346,561 (2.78%) · g: 31,130 (0.03%) · c: 57,329,116 (47.55%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 120,553,506 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 29e083d46ff63b590f4178dc6a548d9659f4c8d833c21e08f438b06427e4e73b
the corpus checksum ledger names this file with the same digest
joined 120,569,440 to merged 120,553,506, minus 15,934 (minus 0.0132%)
boundary drops 15,934 · 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-12T11:36:11Z 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 10,772,286 120,049,929 0-41 666880a777bdde13db04698ac5a30b8f9088b7042fb427e7e362a340323768c1 book 5,091,499 141,796,118 42-61 2b9bd804568b421ee10cd83f776830faf1f8fad9de2496ab74e2d8dba4b3abcd last_trade_price 59,368 3,451,577 62-62 8fbb05e54114c255bf6252069a772679f61ef96e00e0b69e67ae1cb9882020b5 market_resolved 4,772 124,733 63-63 cecb08862576455c0d0d83f1cef6be9e6bfe3a509e830e55084fa98ed2ae20f3 new_market 4,349 106,750 64-64 5fedb381bc8f28561019a5d94e5d7beda632abc06b11f9da3e145e1f83ae0e34 price_change 104,618,168 1,013,979,096 65-464 74fe832f0778b032829588ed84271a6126061208fd69ec89da6964d60377757f tick_size_change 3,064 112,676 465-465 744f0947937f8f4db9f487ee70a048ce9f918cdfed3cee94a93e5832055e1101 EVENT MIX count share price_change 104,618,168 86.78% best_bid_ask 10,772,286 8.94% book 5,091,499 4.22% last_trade_price 59,368 0.05% market_resolved 4,772 <0.01% new_market 4,349 <0.01% tick_size_change 3,064 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,772,458 10,772,286 172 16,425 FULL book 5,105,595 5,091,499 14,096 203,050 FULL last_trade_price 59,368 59,368 0 1,359 FULL market_resolved 4,772 4,772 0 217 FULL new_market 4,349 4,349 0 206 FULL price_change 104,619,834 104,618,168 1,666 10,805 FULL tick_size_change 3,064 3,064 0 420 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 5,149,569 4,969,030 5ms 12ms 50ms 1.1s 0 transport_latency_assumed best_bid_ask e 10,770,035 305,889 40ms 45ms 110ms 3.2s 0 transport_latency_assumed best_bid_ask f 10,768,716 27,681 48ms 53ms 141ms 3.5s 0 transport_latency_assumed best_bid_ask g 10,768,444 1,835 84ms 102ms 262ms 11.0s 0 transport_latency_assumed best_bid_ask h 10,770,514 5,467,851 18ms 26ms 83ms 19.2s 0 transport_latency_assumed book c 4,933,668 4,858,492 27.3min 15.9h 31.6d 105.5d 0 book_staleness book e 286,845 55,538 18.5s 8.6h 20.8d 105.5d 0 book_staleness book f 296,060 51,933 27.1s 8.9h 20.8d 105.5d 0 book_staleness book g 148,220 8,601 94ms 7.5min 3.0d 87.0d 0 book_staleness book h 316,348 116,935 39.6s 9.7h 20.8d 105.5d 0 book_staleness last_trade_price c 27,674 25,889 11ms 46ms 219ms 4.9s 0 transport_latency_assumed last_trade_price e 59,204 2,267 47ms 131ms 1.3s 5.0s 0 transport_latency_assumed last_trade_price f 58,881 532 54ms 136ms 886ms 5.0s 0 transport_latency_assumed last_trade_price g 59,032 91 98ms 224ms 838ms 10.9s 0 transport_latency_assumed last_trade_price h 59,248 30,589 24ms 73ms 289ms 5.2s 0 transport_latency_assumed market_resolved c 4,626 4,617 33.7min 1.1h 1.4h 1.5h 0 transport_latency_assumed market_resolved e 428 6 42ms 122ms 356ms 599ms 0 transport_latency_assumed market_resolved f 428 3 49ms 130ms 305ms 459ms 0 transport_latency_assumed market_resolved g 428 not meas. 91ms 249ms 711ms 894ms 0 transport_latency_assumed market_resolved h 428 146 19ms 58ms 120ms 142ms 0 transport_latency_assumed new_market c 4,318 4,112 28.4min 1.0h 1.3h 1.4h 0 transport_latency_assumed new_market e 339 55 119ms 11.7s 18.8s 1.0min 0 transport_latency_assumed new_market f 339 23 119ms 12.4s 22.1s 1.2min 0 transport_latency_assumed new_market g 339 35 160ms 12.1s 21.9s 1.0min 0 transport_latency_assumed new_market h 339 124 79ms 15.4s 21.6s 1.0min 0 transport_latency_assumed price_change c 49,265,830 47,465,668 5ms 12ms 57ms 1.5s 0 transport_latency_assumed price_change e 104,585,836 2,982,730 41ms 45ms 140ms 3.2s 0 transport_latency_assumed price_change f 104,582,430 297,002 48ms 55ms 176ms 3.7s 0 transport_latency_assumed price_change g 104,564,376 20,568 85ms 105ms 314ms 13.4s 0 transport_latency_assumed price_change h 104,598,182 53,852,200 18ms 28ms 93ms 21.6s 0 transport_latency_assumed tick_size_change c 1,388 1,308 5ms 14ms 69ms 175ms 0 transport_latency_assumed tick_size_change e 3,064 76 40ms 45ms 89ms 196ms 0 transport_latency_assumed tick_size_change f 3,064 4 48ms 53ms 107ms 1.6s 0 transport_latency_assumed tick_size_change g 3,060 not meas. 84ms 99ms 138ms 258ms 0 transport_latency_assumed tick_size_change h 3,064 1,676 18ms 27ms 79ms 236ms 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-12/09/2026-09-12T09.parquet sha256sum 2026-09-12T09.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.