Hour audit: 2026-09-09T01
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-09T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T01:00:00.001475616+00:00 · last event 2026-09-09T01:59:59.999991697+00:00
VOLUME 104,747,362 rows · 1,048,761,579 bytes (1000.18 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 104,618,070 · f: 104,604,063 · h: 104,537,958 · g: 104,534,901 · e: 104,471,906 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 100,692,735 (96.13%) · f: 175,523 (0.17%) · h: 3,475,897 (3.32%) · g: 44,432 (0.04%) · e: 358,775 (0.34%) (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 104,747,362 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f53db2ad06f74438684f882b37353edbf7b0dd9504ff42fb396964696271600f
the corpus checksum ledger names this file with the same digest
joined 104,750,258 to merged 104,747,362, minus 2,896 (minus 0.0028%)
boundary drops 2,896 · 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-09T02:57:35Z 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,943,145 119,799,822 0-41 2956535dff67c683858b6f65086281aef09f0e6d4f87b34c33e94d33f2e4e866 book 187,328 17,877,787 42-42 69fde3cac5c7b8e645c4b40f2e812e1929039fa2f1fa90c8021c5c2de8de2482 last_trade_price 63,346 3,439,380 43-43 09d47723acbaa0d60d797414f13ac0795f00e652251d8e5d5779cbb705c9bbd6 market_resolved 2,248 366,916 44-44 e09d214693d54425e4fd59b05ee7e6a3429ba0feecde5bda77e2eb28c67c93b2 new_market 2,159 212,327 45-45 6abeda7a16cb11d1671f0add9e2c391cf82e037929e18777466889300f459c5d price_change 93,545,568 905,743,810 46-402 1f03c01362f09b8d53224df00047734b4091e36ed642eb2acd65d625e29194f8 tick_size_change 3,568 130,021 403-403 e733829d87243a42a17f1779033be550346f1a8df823fa6d6212ae77a016672b EVENT MIX count share price_change 93,545,568 89.31% best_bid_ask 10,943,145 10.45% book 187,328 0.18% last_trade_price 63,346 0.06% tick_size_change 3,568 <0.01% market_resolved 2,248 <0.01% new_market 2,159 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,943,471 10,943,145 326 426 FULL book 187,377 187,328 49 23,151 FULL last_trade_price 63,347 63,346 1 0 FULL market_resolved 2,248 2,248 0 1 FULL new_market 2,159 2,159 0 6 FULL price_change 93,548,088 93,545,568 2,520 441 FULL tick_size_change 3,568 3,568 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,941,818 10,550,627 4ms 9ms 100ms 3.5s 0 transport_latency_assumed best_bid_ask e 10,939,955 35,913 43ms 50ms 158ms 8.9s 0 transport_latency_assumed best_bid_ask f 10,940,237 16,396 46ms 56ms 176ms 7.2s 0 transport_latency_assumed best_bid_ask g 10,938,188 2,158 84ms 102ms 326ms 21.8s 0 transport_latency_assumed best_bid_ask h 10,940,891 338,051 18ms 24ms 158ms 30.3s 0 transport_latency_assumed book c 146,100 137,452 6ms 191ms 22.8h 83.7d 0 book_staleness book e 142,062 9,188 46ms 274ms 9.4h 102.1d 0 book_staleness book f 138,999 5,790 48ms 169ms 5.1h 83.6d 0 book_staleness book g 145,308 11,461 90ms 1.9s 21.4h 84.1d 0 book_staleness book h 150,164 23,437 21ms 11.4s 1.2d 83.6d 0 book_staleness last_trade_price c 63,202 59,909 9ms 39ms 210ms 5.0s 0 transport_latency_assumed last_trade_price e 63,152 225 49ms 103ms 1.8s 8.9s 0 transport_latency_assumed last_trade_price f 63,242 204 52ms 110ms 859ms 7.2s 0 transport_latency_assumed last_trade_price g 63,018 45 95ms 206ms 2.7s 23.0s 0 transport_latency_assumed last_trade_price h 63,029 2,963 23ms 56ms 389ms 8.8s 0 transport_latency_assumed market_resolved c 2,245 2,185 4ms 8ms 189ms 560ms 0 transport_latency_assumed market_resolved e 2,245 4 45ms 124ms 399ms 1.0min 0 transport_latency_assumed market_resolved f 2,245 4 48ms 134ms 381ms 1.0min 0 transport_latency_assumed market_resolved g 2,245 not meas. 90ms 252ms 683ms 1.2s 0 transport_latency_assumed market_resolved h 2,244 55 19ms 45ms 214ms 1.0min 0 transport_latency_assumed new_market c 1,370 893 73ms 27.1s 1.3min 1.4min 0 transport_latency_assumed new_market e 1,375 308 129ms 25.5s 1.1min 1.4min 0 transport_latency_assumed new_market f 1,370 257 148ms 27.3s 1.3min 3.7min 0 transport_latency_assumed new_market g 1,376 164 232ms 28.1s 1.1min 1.4min 0 transport_latency_assumed new_market h 1,370 537 125ms 30.4s 1.3min 3.8min 0 transport_latency_assumed price_change c 93,459,767 89,938,151 5ms 10ms 108ms 5.0s 0 transport_latency_assumed price_change e 93,319,549 313,137 43ms 53ms 201ms 8.9s 0 transport_latency_assumed price_change f 93,454,402 152,872 46ms 60ms 219ms 7.2s 0 transport_latency_assumed price_change g 93,381,198 30,604 85ms 107ms 414ms 21.9s 0 transport_latency_assumed price_change h 93,376,692 3,110,804 18ms 26ms 168ms 36.7s 0 transport_latency_assumed tick_size_change c 3,568 3,518 4ms 7ms 29ms 242ms 0 transport_latency_assumed tick_size_change e 3,568 not meas. 43ms 49ms 118ms 147ms 0 transport_latency_assumed tick_size_change f 3,568 not meas. 46ms 52ms 121ms 174ms 0 transport_latency_assumed tick_size_change g 3,568 not meas. 83ms 97ms 202ms 615ms 0 transport_latency_assumed tick_size_change h 3,568 50 18ms 22ms 47ms 78ms 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/01/2026-09-09T01.parquet sha256sum 2026-09-09T01.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.