Hour audit: 2026-09-09T06
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-09T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T06:00:00.000053401+00:00 · last event 2026-09-09T06:59:59.999786446+00:00
VOLUME 93,782,417 rows · 914,375,517 bytes (872.02 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 93,643,475 · e: 93,620,518 · c: 93,605,701 · g: 93,583,683 · h: 93,515,216 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 131,289 (0.14%) · e: 290,670 (0.31%) · c: 90,193,257 (96.17%) · g: 49,375 (0.05%) · h: 3,117,826 (3.32%) (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 93,782,417 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c2744ff1a817c306b76c3c3d4c267268ee3164bd2cf870363558203afc5ee22b
the corpus checksum ledger names this file with the same digest
joined 93,785,915 to merged 93,782,417, minus 3,498 (minus 0.0037%)
boundary drops 3,498 · 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-09T07:54:53Z 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,071,290 97,963,217 0-34 d84621fbe7b0cccd2a6cffc7031bcbc2910b978cace1f3872451f68186793ddd book 164,229 17,260,583 35-35 929d3504835a39095e4859c5433cc4eb49e0e40b461a302a2bc9fa68388f792f last_trade_price 49,227 2,795,651 36-36 d5606948297633b92adc6a9f5127639d431d8e176fba578c1d515167cccfc87b market_resolved 626 98,235 37-37 941f7f6f6509159bd2211b5e0081b0aaea2a6d68fa872bdcad20f4182357a293 new_market 809 90,699 38-38 2b7217e8b3bf25ab3d069520892afd492419a73f0c6ae230cf8dae0da7aaee7c price_change 84,494,276 795,023,716 39-361 a61b285f4e7a265025c5599cdd24925f52345fc84cedad9a2eba93f3809d28be tick_size_change 1,960 72,390 362-362 e77cf712cbd8c1352bd818b5f9f4c646a81024dbc72f6e9c0d5100c13713f006 EVENT MIX count share price_change 84,494,276 90.10% best_bid_ask 9,071,290 9.67% book 164,229 0.18% last_trade_price 49,227 0.05% tick_size_change 1,960 <0.01% new_market 809 <0.01% market_resolved 626 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,071,474 9,071,290 184 138 FULL book 164,361 164,229 132 28,720 FULL last_trade_price 49,227 49,227 0 1 FULL market_resolved 626 626 0 0 FULL new_market 809 809 0 0 FULL price_change 84,497,458 84,494,276 3,182 456 FULL tick_size_change 1,960 1,960 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,070,878 8,775,551 5ms 8ms 70ms 6.7s 0 transport_latency_assumed best_bid_ask e 9,069,618 18,921 36ms 41ms 124ms 3.7s 0 transport_latency_assumed best_bid_ask f 9,069,336 6,856 45ms 50ms 137ms 2.6s 0 transport_latency_assumed best_bid_ask g 9,068,800 829 83ms 96ms 267ms 18.1s 0 transport_latency_assumed best_bid_ask h 9,070,134 269,133 14ms 23ms 93ms 15.2s 0 transport_latency_assumed book c 104,592 99,196 6ms 22ms 2.9h 83.8d 0 book_staleness book e 119,420 17,822 38ms 4.7min 1.8d 84.3d 0 book_staleness book f 127,951 26,080 49ms 25.8min 3.5d 102.3d 0 book_staleness book g 114,560 12,590 88ms 26.2s 1.5d 100.8d 0 book_staleness book h 105,586 8,541 18ms 64ms 4.2h 83.8d 0 book_staleness last_trade_price c 49,175 47,114 9ms 37ms 174ms 5.0s 0 transport_latency_assumed last_trade_price e 49,209 141 42ms 97ms 674ms 5.0s 0 transport_latency_assumed last_trade_price f 49,148 41 52ms 104ms 570ms 5.0s 0 transport_latency_assumed last_trade_price g 49,096 4 92ms 193ms 1.6s 18.3s 0 transport_latency_assumed last_trade_price h 49,039 1,927 20ms 55ms 242ms 5.1s 0 transport_latency_assumed market_resolved c 615 596 5ms 9ms 58.3s 58.5s 0 transport_latency_assumed market_resolved e 615 9 38ms 191ms 55.0s 55.1s 0 transport_latency_assumed market_resolved f 615 not meas. 47ms 207ms 55.1s 55.1s 0 transport_latency_assumed market_resolved g 615 11 87ms 372ms 774ms 1.2s 0 transport_latency_assumed market_resolved h 615 10 17ms 81ms 55.2s 55.3s 0 transport_latency_assumed new_market c 599 332 69ms 11.3s 32.6s 1.1min 0 transport_latency_assumed new_market e 599 113 117ms 10.9s 32.3s 1.4min 0 transport_latency_assumed new_market f 599 80 137ms 483ms 32.0s 1.1min 0 transport_latency_assumed new_market g 599 30 245ms 733ms 31.0s 1.1min 0 transport_latency_assumed new_market h 599 254 79ms 13.9s 31.9s 33.9s 0 transport_latency_assumed price_change c 84,377,882 81,268,528 5ms 9ms 96ms 7.5s 0 transport_latency_assumed price_change e 84,379,097 253,664 36ms 43ms 190ms 4.6s 0 transport_latency_assumed price_change f 84,393,866 98,232 46ms 54ms 204ms 4.9s 0 transport_latency_assumed price_change g 84,348,053 35,911 83ms 102ms 369ms 18.3s 0 transport_latency_assumed price_change h 84,287,283 2,837,941 14ms 24ms 136ms 16.8s 0 transport_latency_assumed tick_size_change c 1,960 1,940 5ms 7ms 15ms 31ms 0 transport_latency_assumed tick_size_change e 1,960 not meas. 36ms 41ms 107ms 265ms 0 transport_latency_assumed tick_size_change f 1,960 not meas. 45ms 49ms 126ms 205ms 0 transport_latency_assumed tick_size_change g 1,960 not meas. 81ms 98ms 351ms 794ms 0 transport_latency_assumed tick_size_change h 1,960 20 14ms 24ms 106ms 304ms 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-09/06/2026-09-09T06.parquet sha256sum 2026-09-09T06.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.