Hour audit: 2026-09-09T23
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-09T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T23:00:00.003000875+00:00 · last event 2026-09-09T23:59:59.999947673+00:00
VOLUME 103,053,007 rows · 1,060,934,768 bytes (1011.79 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 102,541,448 · h: 102,532,228 · e: 102,521,874 · g: 102,498,364 · c: 98,640,511 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 164,237 (0.16%) · h: 7,429,641 (7.21%) · e: 518,315 (0.50%) · g: 44,586 (0.04%) · c: 94,896,228 (92.08%) (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 103,053,007 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a8374fbd29802d4675ecf7f2ffc2809eed0c29d4d70a8c2d9cc8dacc8a1e8e69
the corpus checksum ledger names this file with the same digest
joined 103,056,424 to merged 103,053,007, minus 3,417 (minus 0.0033%)
boundary drops 3,417 · 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-10T00:59:59Z 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 8,081,202 92,509,205 0-30 65d3b6952d64f8eb9a58cefdd76d925f4d2455ffb769a396449a9b752dd064cb book 531,108 55,798,922 31-33 29e5f42aa2172a028c99619fc04970335027cd41e349699a3e9c24f35813d267 last_trade_price 52,320 3,025,108 34-34 33a8453a9c959ccaf3686d7bfe8d4adcd251d3e7cb1be4a47b99a544c435bcf2 market_resolved 1,236 185,902 35-35 85878a478667a82e2e9d4e9b7daf087146d04dc2a4b3ca6a60e31833ad12c71b new_market 1,045 119,270 36-36 e2f6e3c947b75653690ff8b582ca6ef01cd1df1e4bc272ca533f4462760f79b8 price_change 94,382,724 907,994,919 37-397 d69ff43b107d1f050076bc17106bdccb32df26e70bc73b6426f47c12bd7f6508 tick_size_change 3,372 123,460 398-398 f6de11c10c698272bb37808cfb24a35b30620279b8861c58a44209cb5c38e7c7 EVENT MIX count share price_change 94,382,724 91.59% best_bid_ask 8,081,202 7.84% book 531,108 0.52% last_trade_price 52,320 0.05% tick_size_change 3,372 <0.01% market_resolved 1,236 <0.01% new_market 1,045 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,081,400 8,081,202 198 610 FULL book 531,158 531,108 50 197,638 FULL last_trade_price 52,321 52,320 1 87 FULL market_resolved 1,236 1,236 0 0 FULL new_market 1,045 1,045 0 0 FULL price_change 94,385,892 94,382,724 3,168 600 FULL tick_size_change 3,372 3,372 0 26 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,737,636 7,449,435 5ms 10ms 106ms 7.6s 0 transport_latency_assumed best_bid_ask e 8,079,430 36,619 39ms 47ms 171ms 5.2s 0 transport_latency_assumed best_bid_ask f 8,079,020 10,121 46ms 56ms 191ms 5.0s 0 transport_latency_assumed best_bid_ask g 8,078,146 2,001 81ms 96ms 264ms 11.8s 0 transport_latency_assumed best_bid_ask h 8,080,323 583,026 18ms 23ms 125ms 39.3s 0 transport_latency_assumed book c 511,223 496,656 5.2min 16.2h 28.3d 103.0d 0 book_staleness book e 117,141 5,575 42ms 498ms 14.4h 103.0d 0 book_staleness book f 117,083 5,142 49ms 692ms 14.5h 84.5d 0 book_staleness book g 124,470 9,704 91ms 54.1s 2.0d 103.1d 0 book_staleness book h 114,895 14,031 21ms 97ms 8.3h 84.5d 0 book_staleness last_trade_price c 50,469 48,069 10ms 42ms 221ms 5.3s 0 transport_latency_assumed last_trade_price e 52,269 323 47ms 142ms 1.4s 5.3s 0 transport_latency_assumed last_trade_price f 52,246 108 56ms 174ms 1.5s 5.0s 0 transport_latency_assumed last_trade_price g 52,149 100 95ms 181ms 602ms 9.9s 0 transport_latency_assumed last_trade_price h 52,259 3,720 23ms 66ms 335ms 6.7s 0 transport_latency_assumed market_resolved c 1,150 1,135 5ms 15ms 4.8min 4.8min 0 transport_latency_assumed market_resolved e 1,150 not meas. 40ms 118ms 273ms 46.1s 0 transport_latency_assumed market_resolved f 1,150 not meas. 47ms 126ms 287ms 625ms 0 transport_latency_assumed market_resolved g 1,150 not meas. 87ms 218ms 398ms 796ms 0 transport_latency_assumed market_resolved h 1,150 101 18ms 45ms 107ms 45.9s 0 transport_latency_assumed new_market c 756 498 60ms 22.2s 1.2min 14.5min 0 transport_latency_assumed new_market e 754 166 132ms 12.7s 42.4s 29.4min 0 transport_latency_assumed new_market f 754 74 174ms 11.7s 46.5s 13.0min 0 transport_latency_assumed new_market g 754 65 220ms 676ms 47.1s 5.0min 0 transport_latency_assumed new_market h 754 242 104ms 13.7s 44.2s 5.4min 0 transport_latency_assumed price_change c 90,336,009 86,897,290 5ms 10ms 130ms 7.8s 0 transport_latency_assumed price_change e 94,267,758 475,604 40ms 51ms 250ms 5.3s 0 transport_latency_assumed price_change f 94,287,823 148,780 47ms 62ms 298ms 5.0s 0 transport_latency_assumed price_change g 94,238,323 32,716 81ms 98ms 329ms 13.3s 0 transport_latency_assumed price_change h 94,279,475 6,828,334 18ms 25ms 166ms 43.7s 0 transport_latency_assumed tick_size_change c 3,268 3,145 5ms 10ms 52ms 320ms 0 transport_latency_assumed tick_size_change e 3,372 28 39ms 49ms 129ms 433ms 0 transport_latency_assumed tick_size_change f 3,372 12 46ms 55ms 127ms 259ms 0 transport_latency_assumed tick_size_change g 3,372 not meas. 81ms 97ms 191ms 309ms 0 transport_latency_assumed tick_size_change h 3,372 187 18ms 27ms 82ms 159ms 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/23/2026-09-09T23.parquet sha256sum 2026-09-09T23.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.