Hour audit: 2026-09-09T20
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-09T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T20:00:00.001061188+00:00 · last event 2026-09-09T20:59:59.999988368+00:00
VOLUME 120,869,997 rows · 1,337,621,436 bytes (1.25 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 118,429,370 · h: 118,423,479 · f: 113,653,259 · g: 113,326,339 · c: 90,160,958 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 4,175,426 (3.45%) · h: 31,033,368 (25.67%) · f: 1,438,672 (1.19%) · g: 195,144 (0.16%) · c: 84,027,387 (69.52%) (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 120,869,997 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0c82fd6eba57ce164ec4efe8683ea32a5becafe5ea1e2ae43c19d0bbb87573d8
the corpus checksum ledger names this file with the same digest
joined 120,876,813 to merged 120,869,997, minus 6,816 (minus 0.0056%)
boundary drops 6,816 · 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-09T22:37:03Z 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,831,428 126,188,148 0-41 62bd29ddf2500974094534b62f1a6e6339f82069207260d5082c6d4dd9736439 book 2,617,444 105,645,100 42-51 bccff0e6ea0e3fa6e2e6e71e9944b140e51d019955f545d72e55790dc9afa799 last_trade_price 64,101 3,646,259 52-52 c1b01c1d8edd180b7f4537db407ec13c8b2821008e151d94b5eb3ece2d370087 market_resolved 1,426 179,283 53-53 f5148bef6d75019150ef029f15e417600dfefe65a6dc39bda8f174db996bf633 new_market 8,926 834,407 54-54 5685eb4dffe5c74ca119b747323a6b253f3926beaaeea27b51dd063b888c2f5c price_change 107,341,972 1,099,580,327 55-464 4758a8e921117ff23d4553108df77c50917d996acf77408f2a244e5af30d9ed7 tick_size_change 4,700 172,513 465-465 aaf132d26b02f4efc9768bb499b921a23df895a485f818313d9dad8704f8f0be EVENT MIX count share price_change 107,341,972 88.81% best_bid_ask 10,831,428 8.96% book 2,617,444 2.17% last_trade_price 64,101 0.05% new_market 8,926 <0.01% tick_size_change 4,700 <0.01% market_resolved 1,426 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,831,699 10,831,428 271 6,543 FULL book 2,620,845 2,617,444 3,401 190,042 FULL last_trade_price 64,103 64,101 2 510 FULL market_resolved 1,426 1,426 0 104 FULL new_market 8,926 8,926 0 43 FULL price_change 107,345,114 107,341,972 3,142 6,068 FULL tick_size_change 4,700 4,700 0 392 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,017,430 7,466,842 6ms 23ms 327ms 40.2s 0 transport_latency_assumed best_bid_ask e 10,827,916 397,687 41ms 104ms 502ms 29.9s 0 transport_latency_assumed best_bid_ask f 10,346,887 117,978 47ms 110ms 512ms 23.9s 0 transport_latency_assumed best_bid_ask g 10,334,251 11,021 88ms 284ms 1.3s 38.7s 0 transport_latency_assumed best_bid_ask h 10,829,113 2,837,900 18ms 66ms 1.1s 1.0min 0 transport_latency_assumed book c 2,415,532 2,284,285 20.3min 20.5h 32.1d 102.9d 0 book_staleness book e 237,788 44,043 577ms 6.3h 15.1d 102.9d 0 book_staleness book f 591,706 154,841 4.9min 14.8h 28.1d 102.9d 0 book_staleness book g 551,895 71,451 4.3min 14.3h 28.0d 102.9d 0 book_staleness book h 205,773 62,824 64ms 3.0h 7.9d 102.9d 0 book_staleness last_trade_price c 45,830 42,847 11ms 65ms 421ms 4.9s 0 transport_latency_assumed last_trade_price e 63,821 1,866 72ms 643ms 9.8s 29.8s 0 transport_latency_assumed last_trade_price f 61,337 872 77ms 575ms 6.4s 23.9s 0 transport_latency_assumed last_trade_price g 60,150 149 129ms 1.4s 16.6s 38.7s 0 transport_latency_assumed last_trade_price h 63,922 18,367 29ms 190ms 1.8s 54.6s 0 transport_latency_assumed market_resolved c 1,125 1,036 7ms 6.7min 16.9min 17.0min 0 transport_latency_assumed market_resolved e 1,079 30 42ms 350ms 59.2s 59.6s 0 transport_latency_assumed market_resolved f 1,065 46 48ms 282ms 5.1min 5.1min 0 transport_latency_assumed market_resolved g 1,074 11 94ms 608ms 5.5min 5.5min 0 transport_latency_assumed market_resolved h 1,079 303 19ms 236ms 57.4s 57.8s 0 transport_latency_assumed new_market c 6,189 4,108 176ms 6.2min 10.2min 19.6min 0 transport_latency_assumed new_market e 5,080 943 233ms 2.3min 4.1min 4.8min 0 transport_latency_assumed new_market f 5,183 1,245 253ms 4.0min 39.6min 40.0min 0 transport_latency_assumed new_market g 5,187 1,050 376ms 3.9min 4.7min 4.9min 0 transport_latency_assumed new_market h 5,080 1,580 198ms 2.1min 4.1min 4.7min 0 transport_latency_assumed price_change c 79,671,720 74,225,261 6ms 25ms 333ms 40.2s 0 transport_latency_assumed price_change e 107,288,986 3,730,750 41ms 133ms 858ms 29.9s 0 transport_latency_assumed price_change f 102,642,505 1,163,650 47ms 135ms 781ms 23.9s 0 transport_latency_assumed price_change g 102,369,230 111,462 89ms 344ms 3.3s 38.7s 0 transport_latency_assumed price_change h 107,313,812 28,110,849 18ms 71ms 1.1s 1.3min 0 transport_latency_assumed tick_size_change c 3,132 3,008 5ms 10ms 462ms 1.2s 0 transport_latency_assumed tick_size_change e 4,700 107 40ms 58ms 418ms 938ms 0 transport_latency_assumed tick_size_change f 4,576 40 46ms 64ms 372ms 741ms 0 transport_latency_assumed tick_size_change g 4,552 not meas. 81ms 143ms 785ms 1.4s 0 transport_latency_assumed tick_size_change h 4,700 1,545 18ms 32ms 663ms 22.8s 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/20/2026-09-09T20.parquet sha256sum 2026-09-09T20.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.