Hour audit: 2026-09-11T11
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-11T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T11:00:00.000019080+00:00 · last event 2026-09-11T11:59:59.999931277+00:00
VOLUME 108,140,823 rows · 1,161,449,695 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 106,471,632 · e: 106,460,918 · h: 106,449,068 · g: 106,303,065 · c: 89,217,583 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 340,314 (0.31%) · e: 1,034,772 (0.96%) · h: 21,497,738 (19.88%) · g: 38,753 (0.04%) · c: 85,229,246 (78.81%) (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 108,140,823 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d7da2912b4d531a866b3c66a37ed51923ab7ae8287e70cbc8e0e564484f1faf2
the corpus checksum ledger names this file with the same digest
joined 108,144,220 to merged 108,140,823, minus 3,397 (minus 0.0031%)
boundary drops 3,397 · 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-11T12:59:50Z 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 9,303,790 107,130,894 0-35 8698e24b2d53e680a5f9d805e4bdbac5eb6e81c6bb3953649298647100998cf3 book 1,920,301 96,307,003 36-43 20d363930434f70ed0f8e9c19bb6802cf1df744bac0212fdd751e833b237a1f7 last_trade_price 54,212 3,100,802 44-44 954fac81f7341f8b4e9b144623f009a85ca61b81e742d06dfa713ac27a14297b market_resolved 691 98,902 45-45 ca2762e8c8adcd00e1c23467e741024c454622db90d6339b6576e1723020240e new_market 599 57,588 46-46 bea0c7b8916028830ddb6def73130af502c883a938e205fba1d1a747ef2e1fe7 price_change 96,858,594 953,423,137 47-416 2289b49d7644f6873a1b0e56337491015c9ed40853d09b73d5275c3b283abf9a tick_size_change 2,636 97,210 417-417 154bbfc57009fd28bd4a0f684c522f3d87544e0061784813422881e369b2274a EVENT MIX count share price_change 96,858,594 89.57% best_bid_ask 9,303,790 8.60% book 1,920,301 1.78% last_trade_price 54,212 0.05% tick_size_change 2,636 <0.01% market_resolved 691 <0.01% new_market 599 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,303,998 9,303,790 208 3,086 FULL book 1,921,036 1,920,301 735 202,463 FULL last_trade_price 54,212 54,212 0 378 FULL market_resolved 691 691 0 36 FULL new_market 599 599 0 3 FULL price_change 96,861,048 96,858,594 2,454 1,955 FULL tick_size_change 2,636 2,636 0 108 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,668,718 7,350,952 5ms 12ms 96ms 3.9s 0 transport_latency_assumed best_bid_ask e 9,301,446 77,192 40ms 46ms 150ms 4.3s 0 transport_latency_assumed best_bid_ask f 9,301,836 18,601 46ms 54ms 166ms 2.9s 0 transport_latency_assumed best_bid_ask g 9,301,896 1,943 77ms 96ms 286ms 11.1s 0 transport_latency_assumed best_bid_ask h 9,302,396 1,855,102 18ms 25ms 109ms 15.4s 0 transport_latency_assumed book c 1,761,999 1,674,863 18.3min 1.2d 30.7d 104.6d 0 book_staleness book e 278,118 72,175 37.2s 15.5h 19.9d 104.6d 0 book_staleness book f 283,821 72,510 42.9s 15.7h 19.9d 104.6d 0 book_staleness book g 126,519 9,517 84ms 23.9s 1.5d 86.0d 0 book_staleness book h 253,391 91,236 16.4s 14.1h 19.9d 104.6d 0 book_staleness last_trade_price c 44,225 41,908 11ms 43ms 214ms 4.9s 0 transport_latency_assumed last_trade_price e 54,088 629 48ms 129ms 1.2s 5.0s 0 transport_latency_assumed last_trade_price f 54,163 202 54ms 140ms 768ms 5.0s 0 transport_latency_assumed last_trade_price g 54,062 44 93ms 269ms 2.1s 11.2s 0 transport_latency_assumed last_trade_price h 54,143 11,429 24ms 67ms 304ms 7.5s 0 transport_latency_assumed market_resolved c 602 580 6ms 4.9min 9.1min 11.7min 0 transport_latency_assumed market_resolved e 599 2 42ms 187ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 599 11 47ms 177ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 599 not meas. 79ms 295ms 716ms 1.3s 0 transport_latency_assumed market_resolved h 599 98 19ms 61ms 1.0min 1.1min 0 transport_latency_assumed new_market c 425 291 127ms 4.2min 8.6min 1.1h 0 transport_latency_assumed new_market e 357 67 129ms 12.6s 20.6s 1.3min 0 transport_latency_assumed new_market f 357 48 136ms 4.4s 53.2s 1.2min 0 transport_latency_assumed new_market g 357 37 274ms 15.7s 53.9s 1.3min 0 transport_latency_assumed new_market h 357 156 76ms 12.2s 40.0s 1.4min 0 transport_latency_assumed price_change c 79,739,410 76,158,528 5ms 13ms 139ms 4.3s 0 transport_latency_assumed price_change e 96,823,674 884,706 41ms 50ms 238ms 4.3s 0 transport_latency_assumed price_change f 96,828,220 248,942 46ms 59ms 246ms 2.9s 0 transport_latency_assumed price_change g 96,816,996 27,212 77ms 109ms 423ms 11.2s 0 transport_latency_assumed price_change h 96,835,546 19,539,206 18ms 28ms 158ms 15.4s 0 transport_latency_assumed tick_size_change c 2,204 2,124 5ms 11ms 38ms 75ms 0 transport_latency_assumed tick_size_change e 2,636 1 41ms 47ms 109ms 171ms 0 transport_latency_assumed tick_size_change f 2,636 not meas. 46ms 50ms 185ms 313ms 0 transport_latency_assumed tick_size_change g 2,636 not meas. 77ms 91ms 168ms 836ms 0 transport_latency_assumed tick_size_change h 2,636 511 18ms 23ms 37ms 80ms 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/11/2026-09-11T11.parquet sha256sum 2026-09-11T11.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.