Hour audit: 2026-09-10T08
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-10T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T08:00:00.000040427+00:00 · last event 2026-09-10T08:59:59.999800476+00:00
VOLUME 91,008,146 rows · 909,827,247 bytes (867.68 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 90,822,129 · c: 90,814,698 · e: 90,789,070 · f: 90,787,459 · g: 90,720,464 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 2,973,254 (3.27%) · c: 87,601,861 (96.26%) · e: 278,434 (0.31%) · f: 138,717 (0.15%) · g: 15,880 (0.02%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 91,008,146 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 891c3ad8a8223c8b575797f5bee09183d17aa43a43be55928b2b81fb74b7ac3b
the corpus checksum ledger names this file with the same digest
joined 91,011,892 to merged 91,008,146, minus 3,746 (minus 0.0041%)
boundary drops 3,746 · 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-10T09:54:18Z 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,080,694 99,495,405 0-34 6acc1f606d05e54cbc3adc722959926c57fd1a890ce61efa788f264a000e4b76 book 364,505 38,075,509 35-36 4439846502bcb61d0f20ef960bea81e1d92a946f44a29af4929de4e28186c6fe last_trade_price 52,286 2,968,389 37-37 7d17a00e9cd2f1bca4fa1f240943cab481f67ce3367550a6ddc0d1c384814423 market_resolved 644 104,988 38-38 9b8a995358a8ef8b49d66e7a148d77b0e17a062d3ad75a9e2b3ebd3ee2ab5a22 new_market 461 57,720 39-39 c81df8edf5b58cd19518a2010432cc654f51941cbda1a9ed66c83302d3a5624c price_change 81,507,640 768,015,461 40-350 d8c032f332127e94620954ab5b4b54b4c5ef056c140dc94927f27b21e8110fa2 tick_size_change 1,916 70,901 351-351 4ec04c0513937e588341d26fa4230dfdc1990563e87ff2a322503accb2e43493 EVENT MIX count share price_change 81,507,640 89.56% best_bid_ask 9,080,694 9.98% book 364,505 0.40% last_trade_price 52,286 0.06% tick_size_change 1,916 <0.01% market_resolved 644 <0.01% new_market 461 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,080,904 9,080,694 210 111 FULL book 364,965 364,505 460 109,636 FULL last_trade_price 52,286 52,286 0 0 FULL market_resolved 644 644 0 3 FULL new_market 461 461 0 0 FULL price_change 81,510,716 81,507,640 3,076 56 FULL tick_size_change 1,916 1,916 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,080,238 8,775,334 5ms 9ms 71ms 3.4s 0 transport_latency_assumed best_bid_ask e 9,078,549 20,235 39ms 44ms 121ms 4.6s 0 transport_latency_assumed best_bid_ask f 9,078,754 6,909 45ms 50ms 131ms 9.4s 0 transport_latency_assumed best_bid_ask g 9,078,665 811 76ms 95ms 236ms 10.9s 0 transport_latency_assumed best_bid_ask h 9,079,020 277,405 17ms 21ms 91ms 6.9s 0 transport_latency_assumed book c 179,843 162,019 11ms 5.4h 18.8d 103.4d 0 book_staleness book e 174,086 56,870 57ms 5.0h 17.6d 103.4d 0 book_staleness book f 168,409 51,128 56ms 4.2h 15.6d 103.4d 0 book_staleness book g 115,414 5,891 82ms 257ms 13.4h 84.9d 0 book_staleness book h 207,850 88,597 161ms 8.1h 18.8d 103.4d 0 book_staleness last_trade_price c 52,247 49,519 10ms 45ms 216ms 5.0s 0 transport_latency_assumed last_trade_price e 52,189 309 46ms 139ms 2.1s 5.0s 0 transport_latency_assumed last_trade_price f 52,193 210 52ms 133ms 1.4s 5.0s 0 transport_latency_assumed last_trade_price g 52,199 43 90ms 191ms 536ms 5.1s 0 transport_latency_assumed last_trade_price h 52,195 2,205 23ms 80ms 472ms 5.0s 0 transport_latency_assumed market_resolved c 617 594 5ms 10ms 66ms 213ms 0 transport_latency_assumed market_resolved e 617 27 40ms 197ms 56.6s 1.0min 0 transport_latency_assumed market_resolved f 616 not meas. 47ms 207ms 56.6s 1.0min 0 transport_latency_assumed market_resolved g 617 not meas. 84ms 260ms 537ms 834ms 0 transport_latency_assumed market_resolved h 615 23 18ms 88ms 57.0s 1.1min 0 transport_latency_assumed new_market c 375 247 41ms 289ms 14.2s 1.1min 0 transport_latency_assumed new_market e 375 37 85ms 346ms 21.3s 1.0min 0 transport_latency_assumed new_market f 375 52 83ms 409ms 31.5s 1.1min 0 transport_latency_assumed new_market g 375 13 111ms 540ms 32.5s 1.7min 0 transport_latency_assumed new_market h 375 112 48ms 249ms 23.9s 1.0min 0 transport_latency_assumed price_change c 81,499,462 78,612,248 5ms 10ms 81ms 3.4s 0 transport_latency_assumed price_change e 81,481,338 200,956 39ms 45ms 179ms 5.7s 0 transport_latency_assumed price_change f 81,485,196 80,418 45ms 52ms 177ms 10.2s 0 transport_latency_assumed price_change g 81,471,278 9,122 76ms 100ms 273ms 11.7s 0 transport_latency_assumed price_change h 81,480,158 2,604,896 17ms 23ms 120ms 6.9s 0 transport_latency_assumed tick_size_change c 1,916 1,900 4ms 7ms 20ms 68ms 0 transport_latency_assumed tick_size_change e 1,916 not meas. 38ms 48ms 112ms 161ms 0 transport_latency_assumed tick_size_change f 1,916 not meas. 45ms 49ms 122ms 461ms 0 transport_latency_assumed tick_size_change g 1,916 not meas. 76ms 93ms 218ms 431ms 0 transport_latency_assumed tick_size_change h 1,916 16 18ms 28ms 59ms 158ms 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-10/08/2026-09-10T08.parquet sha256sum 2026-09-10T08.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.