Hour audit: 2026-09-10T02
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-10T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T02:00:00.000002973+00:00 · last event 2026-09-10T02:59:59.999993532+00:00
VOLUME 116,983,546 rows · 1,215,315,249 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 116,549,469 · g: 116,540,705 · h: 116,504,865 · e: 116,488,894 · c: 112,039,843 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 222,684 (0.19%) · g: 27,000 (0.02%) · h: 8,100,244 (6.92%) · e: 893,590 (0.76%) · c: 107,740,028 (92.10%) (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 116,983,546 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 653f2adc7358f96b8dbeb357804fdac2bc548a257e5cabc0f2a3b8ac122b2fc8
the corpus checksum ledger names this file with the same digest
joined 116,986,396 to merged 116,983,546, minus 2,850 (minus 0.0024%)
boundary drops 2,850 · 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-10T04:37:19Z 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,617,362 118,223,190 0-40 18abc747341377f181dcaa016c798506735aef573480395fa207d71266db8aee book 532,320 56,736,798 41-43 5131064168ff340b6ff05c68233d4bd5d905b3523b83137403e8483b3e3a9a57 last_trade_price 56,968 3,271,965 44-44 a10444c034e1f37decb4cde0cc3baae22dbcc098b61614299ad28922772fc8ab market_resolved 3,184 490,997 45-45 840c41235be2e8242b60627f41d785f560fcd8dd629ded30366a86510374a2c8 new_market 618 74,867 46-46 5bea909d38f2fc401446bc902ff1bc48e8a4311d863171633b3dbbb8736722d5 price_change 105,768,346 1,035,010,522 47-450 4c27c6330a40da2abe8def1685c30c4077649d8f0117d82bb9b14d524096e021 tick_size_change 4,748 173,840 451-451 ca3cea8dfc995774d7bb9c42760da8cf9d6f09f48755f96cea40dc20a5768064 EVENT MIX count share price_change 105,768,346 90.41% best_bid_ask 10,617,362 9.08% book 532,320 0.46% last_trade_price 56,968 0.05% tick_size_change 4,748 <0.01% market_resolved 3,184 <0.01% new_market 618 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,617,671 10,617,362 309 420 FULL book 532,328 532,320 8 195,963 FULL last_trade_price 56,969 56,968 1 69 FULL market_resolved 3,184 3,184 0 0 FULL new_market 618 618 0 0 FULL price_change 105,770,878 105,768,346 2,532 242 FULL tick_size_change 4,748 4,748 0 63 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,140,681 9,778,373 5ms 10ms 83ms 2.7s 0 transport_latency_assumed best_bid_ask e 10,616,270 79,666 41ms 48ms 133ms 3.2s 0 transport_latency_assumed best_bid_ask f 10,616,291 17,139 47ms 57ms 162ms 2.5s 0 transport_latency_assumed best_bid_ask g 10,615,273 1,099 81ms 97ms 251ms 13.4s 0 transport_latency_assumed best_bid_ask h 10,616,512 741,085 17ms 31ms 113ms 41.1s 0 transport_latency_assumed book c 516,410 505,801 6.1min 17.4h 28.3d 103.2d 0 book_staleness book e 119,517 2,485 43ms 95ms 2.4s 84.6d 0 book_staleness book f 119,037 950 49ms 108ms 1.1s 84.5d 0 book_staleness book g 138,823 13,331 88ms 3.6min 2.6d 103.2d 0 book_staleness book h 119,193 9,753 20ms 60ms 1.8s 39.2d 0 book_staleness last_trade_price c 54,653 51,738 10ms 44ms 212ms 5.0s 0 transport_latency_assumed last_trade_price e 56,917 496 47ms 102ms 444ms 5.0s 0 transport_latency_assumed last_trade_price f 56,924 189 53ms 116ms 496ms 5.0s 0 transport_latency_assumed last_trade_price g 56,838 12 92ms 182ms 706ms 5.1s 0 transport_latency_assumed last_trade_price h 56,875 4,533 23ms 69ms 267ms 39.1s 0 transport_latency_assumed market_resolved c 3,073 3,015 5ms 11ms 4.3min 5.3min 0 transport_latency_assumed market_resolved e 3,073 7 89ms 155ms 350ms 647ms 0 transport_latency_assumed market_resolved f 3,073 4 90ms 143ms 353ms 627ms 0 transport_latency_assumed market_resolved g 3,073 1 127ms 254ms 563ms 1.1s 0 transport_latency_assumed market_resolved h 3,073 157 33ms 64ms 137ms 542ms 0 transport_latency_assumed new_market c 484 293 55ms 421ms 34.3s 7.8min 0 transport_latency_assumed new_market e 484 84 110ms 375ms 54.0s 21.1min 0 transport_latency_assumed new_market f 484 45 97ms 394ms 34.4s 3.0min 0 transport_latency_assumed new_market g 484 47 226ms 13.3s 54.8s 18.3min 0 transport_latency_assumed new_market h 484 149 82ms 349ms 34.9s 37.7s 0 transport_latency_assumed price_change c 101,320,046 97,396,404 5ms 11ms 99ms 2.7s 0 transport_latency_assumed price_change e 105,687,885 810,848 41ms 50ms 168ms 3.2s 0 transport_latency_assumed price_change f 105,748,912 204,357 47ms 60ms 201ms 5.1s 0 transport_latency_assumed price_change g 105,721,466 12,510 81ms 101ms 314ms 13.4s 0 transport_latency_assumed price_change h 105,703,980 7,344,227 17ms 33ms 134ms 41.3s 0 transport_latency_assumed tick_size_change c 4,496 4,404 5ms 7ms 28ms 187ms 0 transport_latency_assumed tick_size_change e 4,748 4 41ms 45ms 107ms 312ms 0 transport_latency_assumed tick_size_change f 4,748 not meas. 47ms 51ms 85ms 129ms 0 transport_latency_assumed tick_size_change g 4,748 not meas. 81ms 93ms 135ms 4.7s 0 transport_latency_assumed tick_size_change h 4,748 340 17ms 24ms 71ms 184ms 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/02/2026-09-10T02.parquet sha256sum 2026-09-10T02.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.