Hour audit: 2026-09-11T04
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-11T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T04:00:00.002981663+00:00 · last event 2026-09-11T04:59:59.999784263+00:00
VOLUME 106,582,632 rows · 1,101,936,363 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 106,189,163 · h: 105,864,879 · g: 105,839,787 · e: 105,811,033 · c: 102,108,869 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 592,130 (0.56%) · h: 8,421,060 (7.90%) · g: 65,809 (0.06%) · e: 908,351 (0.85%) · c: 96,595,282 (90.63%) (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 106,582,632 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5f520344afff9c5a8ea76dfe37535403a69f6f49d4d4710dd5c0ccc15c1c3b0f
the corpus checksum ledger names this file with the same digest
joined 106,585,282 to merged 106,582,632, minus 2,650 (minus 0.0025%)
boundary drops 2,650 · 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-11T06:35:05Z 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,336,298 114,349,344 0-39 4c47e5a80b3d38c1472b5c3665881b190b6cc35a3fde46d349696744e0e7dfb9 book 783,727 66,509,685 40-42 589383ac58dc9a624bd24bb2d2d842a05e5cbcbde11ea6aee776fa751478fec1 last_trade_price 45,322 2,559,466 43-43 a4f172b87b5a1344cf12aea980707edd2b8d85a2f99f3ebbc4f478bf3dee1d0d market_resolved 837 130,277 44-44 1fc032c91a6c7f1486e834c117a9dd830a9199345947727b7cdaf48831d39186 new_market 2,954 309,999 45-45 64540b561139bc13d71e7b7ec903975f29b6648cb6a0eb6a979dffde1c4f4a75 price_change 95,411,134 916,777,360 46-409 2cd77f738615dc3335df592f87dc082482ee099a37164bd8e97a94359c1dc23d tick_size_change 2,360 87,392 410-410 a24584f09c44e529243cc23dd2374c40e91eaf5a03521e246a18838c6b7a174f EVENT MIX count share price_change 95,411,134 89.52% best_bid_ask 10,336,298 9.70% book 783,727 0.74% last_trade_price 45,322 0.04% new_market 2,954 <0.01% tick_size_change 2,360 <0.01% market_resolved 837 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,336,509 10,336,298 211 431 FULL book 783,737 783,727 10 201,543 FULL last_trade_price 45,323 45,322 1 49 FULL market_resolved 837 837 0 1 FULL new_market 2,954 2,954 0 0 FULL price_change 95,413,562 95,411,134 2,428 228 FULL tick_size_change 2,360 2,360 0 4 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,932,796 9,408,131 5ms 11ms 263ms 7.5s 0 transport_latency_assumed best_bid_ask e 10,333,231 91,927 39ms 48ms 268ms 9.4s 0 transport_latency_assumed best_bid_ask f 10,331,480 33,599 45ms 58ms 298ms 4.8s 0 transport_latency_assumed best_bid_ask g 10,332,899 5,359 76ms 122ms 549ms 20.3s 0 transport_latency_assumed best_bid_ask h 10,335,625 797,282 16ms 30ms 520ms 24.9s 0 transport_latency_assumed book c 509,717 499,631 6.8min 22.2h 29.1d 104.2d 0 book_staleness book e 115,868 10,468 44ms 6.7min 3.7d 104.3d 0 book_staleness book f 455,275 246,049 4.1min 20.6h 26.5d 104.3d 0 book_staleness book g 135,407 17,248 107ms 1.3h 5.6d 104.3d 0 book_staleness book h 102,129 10,331 20ms 237ms 7.1h 85.7d 0 book_staleness last_trade_price c 43,917 41,094 10ms 49ms 358ms 5.0s 0 transport_latency_assumed last_trade_price e 45,116 441 48ms 166ms 2.8s 9.2s 0 transport_latency_assumed last_trade_price f 45,204 176 55ms 167ms 1.4s 5.0s 0 transport_latency_assumed last_trade_price g 44,881 33 93ms 342ms 7.7s 20.3s 0 transport_latency_assumed last_trade_price h 45,253 3,578 22ms 79ms 584ms 9.8s 0 transport_latency_assumed market_resolved c 800 750 5ms 35ms 5.4min 5.4min 0 transport_latency_assumed market_resolved e 800 13 42ms 205ms 58.4s 1.0min 0 transport_latency_assumed market_resolved f 800 not meas. 49ms 247ms 521ms 1.0min 0 transport_latency_assumed market_resolved g 800 not meas. 90ms 386ms 883ms 1.8s 0 transport_latency_assumed market_resolved h 800 74 20ms 104ms 1.0min 1.0min 0 transport_latency_assumed new_market c 2,046 1,086 116ms 19.1s 1.3min 14.6min 0 transport_latency_assumed new_market e 2,046 552 181ms 19.6s 1.3min 1.8min 0 transport_latency_assumed new_market f 2,046 294 219ms 20.7s 1.3min 1.9min 0 transport_latency_assumed new_market g 2,046 263 292ms 19.9s 1.3min 2.0min 0 transport_latency_assumed new_market h 2,046 759 164ms 20.7s 1.3min 2.0min 0 transport_latency_assumed price_change c 91,617,249 86,642,423 5ms 13ms 277ms 8.2s 0 transport_latency_assumed price_change e 95,311,612 804,914 40ms 54ms 415ms 9.4s 0 transport_latency_assumed price_change f 95,351,998 312,012 45ms 65ms 399ms 4.8s 0 transport_latency_assumed price_change g 95,321,394 42,906 77ms 144ms 767ms 20.3s 0 transport_latency_assumed price_change h 95,376,666 7,608,879 17ms 34ms 515ms 24.9s 0 transport_latency_assumed tick_size_change c 2,344 2,167 5ms 19ms 352ms 1.0s 0 transport_latency_assumed tick_size_change e 2,360 36 40ms 50ms 324ms 643ms 0 transport_latency_assumed tick_size_change f 2,360 not meas. 45ms 83ms 355ms 1.0s 0 transport_latency_assumed tick_size_change g 2,360 not meas. 79ms 120ms 906ms 1.3s 0 transport_latency_assumed tick_size_change h 2,360 157 17ms 25ms 604ms 7.4s 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-11/04/2026-09-11T04.parquet sha256sum 2026-09-11T04.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.