Hour audit: 2026-09-15T23
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-15T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T23:00:00.000933563+00:00 · last event 2026-09-15T23:59:59.999721404+00:00
VOLUME 116,936,714 rows · 1,208,070,452 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 116,437,022 · h: 116,392,399 · e: 116,381,182 · f: 116,372,447 · g: 112,267,394 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 111,842,667 (95.64%) · h: 4,149,121 (3.55%) · e: 317,028 (0.27%) · f: 142,754 (0.12%) · g: 485,144 (0.41%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 116,936,714 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 016f61b35efe56fb8ff4ee0452788cc21e0f5a21e9cfdce8c4ba0c6f73548b8f
the corpus checksum ledger names this file with the same digest
joined 116,938,978 to merged 116,936,714, minus 2,264 (minus 0.0019%)
boundary drops 2,264 · 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-16T01:36:56Z 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,792,528 143,541,154 0-48 9f8e0274d2157d138a585490006949660ad9e0622f4f3df3a165e23dbb547839 book 577,767 53,449,459 49-51 331693040a33a4222af82591b1fdec633825d3da0e80802f5d65f6f21964c381 last_trade_price 44,677 2,556,149 52-52 ca8045ce92cad85801955d91c396955f03a372b511a2e4c3d3df022153692183 market_resolved 1,066 161,851 53-53 632aa36eb48b976348144d3705fe8eaca94da3daf01ac610370209e4fdb43959 new_market 1,540 158,844 54-54 6bd93ee09b701a479414bc2ce98371d9f9c4cac8bb0da5da2e206a082567a345 price_change 103,516,148 1,006,764,005 55-449 798f1ee8d96aee683b9b285053879ec982858177e8d70824ac54c097875738d0 tick_size_change 2,988 108,990 450-450 3e88aaa9d0511b38397f409c444ee058cd70d283f4bd821e6bcea0a17c4d220e EVENT MIX count share price_change 103,516,148 88.52% best_bid_ask 12,792,528 10.94% book 577,767 0.49% last_trade_price 44,677 0.04% tick_size_change 2,988 <0.01% new_market 1,540 <0.01% market_resolved 1,066 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,792,680 12,792,528 152 425 FULL book 578,283 577,767 516 175,282 FULL last_trade_price 44,677 44,677 0 45 FULL market_resolved 1,066 1,066 0 0 FULL new_market 1,540 1,540 0 0 FULL price_change 103,517,744 103,516,148 1,596 246 FULL tick_size_change 2,988 2,988 0 17 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,792,118 12,317,330 5ms 9ms 82ms 4.4s 0 transport_latency_assumed best_bid_ask e 12,790,160 32,865 39ms 47ms 189ms 8.0s 0 transport_latency_assumed best_bid_ask f 12,790,071 13,182 45ms 57ms 192ms 17.4s 0 transport_latency_assumed best_bid_ask g 12,302,354 1,408 81ms 100ms 342ms 20.9s 0 transport_latency_assumed best_bid_ask h 12,790,669 427,743 17ms 26ms 115ms 47.5s 0 transport_latency_assumed book c 95,923 89,942 7ms 34ms 4.2min 90.5d 0 book_staleness book e 97,790 4,239 41ms 428ms 24.1min 90.5d 0 book_staleness book f 99,264 4,861 48ms 741ms 38.3min 90.5d 0 book_staleness book g 560,482 469,908 2.9min 22.8h 35.2d 109.0d 0 book_staleness book h 98,164 8,817 21ms 135ms 19.4min 90.4d 0 book_staleness last_trade_price c 44,610 42,437 10ms 50ms 231ms 5.0s 0 transport_latency_assumed last_trade_price e 44,403 173 49ms 213ms 1.5s 8.1s 0 transport_latency_assumed last_trade_price f 44,319 115 56ms 208ms 4.9s 17.4s 0 transport_latency_assumed last_trade_price g 41,944 10 95ms 268ms 2.5s 20.9s 0 transport_latency_assumed last_trade_price h 44,439 1,942 23ms 85ms 394ms 8.9s 0 transport_latency_assumed market_resolved c 1,001 958 5ms 8ms 54.8s 1.0min 0 transport_latency_assumed market_resolved e 1,001 1 39ms 189ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 1,001 not meas. 45ms 196ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 1,001 19 86ms 259ms 3.3min 4.3min 0 transport_latency_assumed market_resolved h 1,001 88 18ms 108ms 1.0min 1.0min 0 transport_latency_assumed new_market c 1,000 708 67ms 25.6s 47.8s 9.2min 0 transport_latency_assumed new_market e 1,000 166 199ms 22.2s 49.6s 6.0min 0 transport_latency_assumed new_market f 1,000 112 178ms 21.6s 50.8s 4.0min 0 transport_latency_assumed new_market g 1,010 135 270ms 38.6s 4.5min 18.4min 0 transport_latency_assumed new_market h 1,000 419 96ms 27.6s 50.9s 4.4min 0 transport_latency_assumed price_change c 103,499,382 99,388,354 5ms 11ms 93ms 4.6s 0 transport_latency_assumed price_change e 103,443,840 279,584 39ms 57ms 333ms 8.0s 0 transport_latency_assumed price_change f 103,433,804 124,484 45ms 66ms 325ms 17.4s 0 transport_latency_assumed price_change g 99,357,683 13,664 82ms 111ms 482ms 21.2s 0 transport_latency_assumed price_change h 103,454,138 3,710,062 18ms 30ms 146ms 47.7s 0 transport_latency_assumed tick_size_change c 2,988 2,938 5ms 7ms 31ms 175ms 0 transport_latency_assumed tick_size_change e 2,988 not meas. 39ms 44ms 120ms 322ms 0 transport_latency_assumed tick_size_change f 2,988 not meas. 44ms 51ms 120ms 247ms 0 transport_latency_assumed tick_size_change g 2,920 not meas. 82ms 97ms 232ms 638ms 0 transport_latency_assumed tick_size_change h 2,988 50 18ms 25ms 67ms 226ms 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/23/2026-09-15T23.parquet sha256sum 2026-09-15T23.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.