Hour audit: 2026-09-10T03
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-10T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T03:00:00.000024926+00:00 · last event 2026-09-10T03:59:59.999995581+00:00
VOLUME 112,272,359 rows · 1,169,962,528 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 111,486,742 · f: 111,260,675 · h: 111,205,580 · e: 111,197,934 · c: 102,509,961 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 170,203 (0.15%) · f: 253,633 (0.23%) · h: 12,002,119 (10.69%) · e: 909,079 (0.81%) · c: 98,937,325 (88.12%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 112,272,359 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9f95ce0c2c0dc6c134d13c49a199a80bf0f3d51ac69910d889f80992f0db70fc
the corpus checksum ledger names this file with the same digest
joined 112,273,719 to merged 112,272,359, minus 1,360 (minus 0.0012%)
boundary drops 1,360 · 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-10T05:03:00Z 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,323,034 104,908,401 0-35 683f91e9403737bca445cee598574e8b75b79c7b0d90fa429401e68439abb43f book 1,149,865 76,574,748 36-40 e466967cd81d7a26c7b182c99d803fb5515f112b0971f215abad2c894c1681c9 last_trade_price 50,477 2,847,422 41-41 96a0b42baf0338ef17498ac84d6d2a27abaf29ca2edc05d77112fe31b39cc501 market_resolved 1,799 266,580 42-42 112db36c1c456158a1051b1ab71ca7a801b54397359f09b5895d6a41c7349c4e new_market 936 103,523 43-43 6d02b203ae808306a0a7292ad82c69081bc0c727fbc6e08f0e64a900dd1dfeda price_change 101,742,416 983,845,391 44-432 77d66dd54b783381ea15e9c3fe9efe75a5c684fa4f630c3421bc041a919c4474 tick_size_change 3,832 135,417 433-433 b60c36a7b851d741717d77ded8f04c1675363776025611a9ef5619aca22e4f2d EVENT MIX count share price_change 101,742,416 90.62% best_bid_ask 9,323,034 8.30% book 1,149,865 1.02% last_trade_price 50,477 0.04% tick_size_change 3,832 <0.01% market_resolved 1,799 <0.01% new_market 936 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,323,134 9,323,034 100 1,413 FULL book 1,149,893 1,149,865 28 193,906 FULL last_trade_price 50,477 50,477 0 205 FULL market_resolved 1,799 1,799 0 60 FULL new_market 936 936 0 0 FULL price_change 101,743,648 101,742,416 1,232 894 FULL tick_size_change 3,832 3,832 0 101 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,474,775 8,195,199 4ms 9ms 85ms 2.3s 0 transport_latency_assumed best_bid_ask e 9,321,656 75,619 39ms 46ms 144ms 3.0s 0 transport_latency_assumed best_bid_ask f 9,321,102 18,796 46ms 55ms 164ms 4.5s 0 transport_latency_assumed best_bid_ask g 9,317,463 1,225 84ms 123ms 354ms 20.9s 0 transport_latency_assumed best_bid_ask h 9,322,008 1,032,195 18ms 26ms 124ms 27.7s 0 transport_latency_assumed book c 956,089 910,233 9.6min 19.0h 31.6d 103.2d 0 book_staleness book e 154,001 21,706 46ms 3.0h 10.5d 84.7d 0 book_staleness book f 169,159 27,029 65ms 5.5h 15.4d 103.2d 0 book_staleness book g 452,125 155,161 4.4min 18.2h 28.4d 103.2d 0 book_staleness book h 146,221 35,736 24ms 1.6h 7.4d 103.2d 0 book_staleness last_trade_price c 46,192 43,775 10ms 46ms 215ms 5.0s 0 transport_latency_assumed last_trade_price e 50,431 610 47ms 112ms 994ms 5.0s 0 transport_latency_assumed last_trade_price f 50,295 195 54ms 129ms 1.0s 5.0s 0 transport_latency_assumed last_trade_price g 50,271 64 94ms 211ms 4.2s 19.8s 0 transport_latency_assumed last_trade_price h 50,404 5,833 23ms 73ms 360ms 7.2s 0 transport_latency_assumed market_resolved c 1,614 1,562 4ms 24ms 4.8min 4.8min 0 transport_latency_assumed market_resolved e 1,674 25 43ms 134ms 56.0s 1.0min 0 transport_latency_assumed market_resolved f 1,674 5 49ms 138ms 56.0s 1.0min 0 transport_latency_assumed market_resolved g 1,674 34 91ms 254ms 44.4s 55.9s 0 transport_latency_assumed market_resolved h 1,674 173 22ms 61ms 56.0s 1.9min 0 transport_latency_assumed new_market c 687 433 62ms 12.0s 6.9min 21.9min 0 transport_latency_assumed new_market e 679 140 130ms 12.4s 1.2min 41.0min 0 transport_latency_assumed new_market f 679 113 127ms 2.4s 1.4min 47.7min 0 transport_latency_assumed new_market g 679 45 246ms 17.9s 1.2min 20.9min 0 transport_latency_assumed new_market h 679 205 98ms 385ms 1.9min 20.9min 0 transport_latency_assumed price_change c 93,027,176 89,782,827 5ms 10ms 93ms 4.3s 0 transport_latency_assumed price_change e 101,665,661 810,951 40ms 48ms 178ms 4.2s 0 transport_latency_assumed price_change f 101,713,934 207,495 47ms 58ms 204ms 4.5s 0 transport_latency_assumed price_change g 101,660,698 13,674 85ms 127ms 442ms 21.1s 0 transport_latency_assumed price_change h 101,680,762 10,927,469 18ms 28ms 135ms 32.1s 0 transport_latency_assumed tick_size_change c 3,428 3,296 4ms 9ms 65ms 431ms 0 transport_latency_assumed tick_size_change e 3,832 28 40ms 68ms 380ms 457ms 0 transport_latency_assumed tick_size_change f 3,832 not meas. 46ms 51ms 94ms 636ms 0 transport_latency_assumed tick_size_change g 3,832 not meas. 79ms 93ms 142ms 663ms 0 transport_latency_assumed tick_size_change h 3,832 508 18ms 24ms 63ms 2.0s 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/03/2026-09-10T03.parquet sha256sum 2026-09-10T03.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.