Hour audit: 2026-09-22T06
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-22T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T06:00:00.000693567+00:00 · last event 2026-09-22T06:59:59.999875324+00:00
VOLUME 100,950,241 rows · 1,050,909,279 bytes (1002.23 MiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured c: 100,481,188 · h: 100,381,049 · f: 100,244,201 · e: 99,889,504 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 94,319,184 (93.43%) · h: 5,460,250 (5.41%) · f: 425,067 (0.42%) · e: 745,740 (0.74%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 100,950,241 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 a068956a308f1a8d2a4fc2a78ab36fb209e181fb2a35576304d2666a84cc5f11
the corpus checksum ledger names this file with the same digest
joined 100,957,021 to merged 100,950,241, minus 6,780 (minus 0.0067%)
boundary drops 6,780 · 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-22T07:53:15Z as cefh
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,198,512 105,562,640 0-35 fb119ad851a234c2a064b6f04e71c36b3fcbca13d7e70bc15ca6c470663da749 book 714,963 58,176,286 36-38 07e8d5678424b9914d6a02a7ce8082691247f8e4ac188da8a87e7eca1402c3fd last_trade_price 49,143 2,777,601 39-39 837fb6b2c6e35c260fdedd233829154e0e3d73b1f2f69dbf3096df8871ff6dc5 market_resolved 611 97,278 40-40 0d3484b171fcae1ebce2a1b2b1d6f1080b05b3694b4b3fb08b55810820482b3b new_market 3,470 347,045 41-41 3e193a7a47e93123422ad0f94433ca900000113efff65c3e5d4b39f5403dffff price_change 90,981,126 882,708,461 42-389 57676f3df09533fc7326affea7246aea86bc05ce898b0498b8112cd3fde482ac tick_size_change 2,416 87,630 390-390 02f0e6f9e5e14929bc6e6802422607300a0e04060764412536717d4058e0c548 EVENT MIX count share price_change 90,981,126 90.12% best_bid_ask 9,198,512 9.11% book 714,963 0.71% last_trade_price 49,143 0.05% new_market 3,470 <0.01% tick_size_change 2,416 <0.01% market_resolved 611 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,198,644 9,198,512 132 272 FULL book 719,707 714,963 4,744 151,362 FULL last_trade_price 49,143 49,143 0 1 FULL market_resolved 611 611 0 0 FULL new_market 3,470 3,470 0 0 FULL price_change 90,983,030 90,981,126 1,904 75 FULL tick_size_change 2,416 2,416 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,196,306 8,669,422 5ms 16ms 222ms 5.6s 0 transport_latency_assumed best_bid_ask e 9,178,485 52,287 41ms 58ms 338ms 28.5s 0 transport_latency_assumed best_bid_ask f 9,191,982 24,561 47ms 67ms 363ms 28.3s 0 transport_latency_assumed best_bid_ask h 9,190,842 452,242 19ms 33ms 317ms 1.0min 0 transport_latency_assumed book c 288,609 227,848 1.1min 23.9h 30.7d 115.3d 0 book_staleness book e 328,175 167,187 1.8min 1.4d 38.7d 115.4d 0 book_staleness book f 295,071 138,087 1.2min 1.2d 30.7d 115.3d 0 book_staleness book h 366,613 181,841 2.3min 1.5d 37.7d 115.4d 0 book_staleness last_trade_price c 48,968 45,593 6ms 27ms 320ms 3.7s 0 transport_latency_assumed last_trade_price e 47,412 307 43ms 170ms 5.3s 28.5s 0 transport_latency_assumed last_trade_price f 48,096 154 49ms 179ms 5.8s 28.2s 0 transport_latency_assumed last_trade_price h 48,586 3,089 20ms 57ms 498ms 11.6s 0 transport_latency_assumed market_resolved c 601 522 5ms 215ms 49.5s 50.5s 0 transport_latency_assumed market_resolved e 601 31 43ms 599ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 601 not meas. 49ms 405ms 43.4s 57.4s 0 transport_latency_assumed market_resolved h 601 58 20ms 346ms 1.0min 1.0min 0 transport_latency_assumed new_market c 2,251 1,179 177ms 2.6min 3.2min 3.4min 0 transport_latency_assumed new_market e 2,251 705 249ms 2.7min 3.3min 3.4min 0 transport_latency_assumed new_market f 2,251 640 222ms 2.0min 3.2min 3.3min 0 transport_latency_assumed new_market h 2,251 946 167ms 1.4min 3.2min 3.3min 0 transport_latency_assumed price_change c 90,942,041 85,372,262 5ms 19ms 250ms 5.6s 0 transport_latency_assumed price_change e 90,330,164 525,219 41ms 75ms 627ms 28.6s 0 transport_latency_assumed price_change f 90,703,784 261,623 47ms 84ms 727ms 28.3s 0 transport_latency_assumed price_change h 90,769,740 4,822,022 19ms 38ms 368ms 1.0min 0 transport_latency_assumed tick_size_change c 2,412 2,358 5ms 9ms 68ms 421ms 0 transport_latency_assumed tick_size_change e 2,416 4 41ms 47ms 118ms 418ms 0 transport_latency_assumed tick_size_change f 2,416 2 47ms 54ms 129ms 525ms 0 transport_latency_assumed tick_size_change h 2,416 52 19ms 25ms 75ms 880ms 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-22/06/2026-09-22T06.parquet sha256sum 2026-09-22T06.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.