Hour audit: 2026-09-15T10
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-15T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T10:00:00.000024420+00:00 · last event 2026-09-15T10:59:59.999968548+00:00
VOLUME 110,593,833 rows · 1,182,574,987 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 110,077,908 · h: 109,806,279 · e: 109,800,284 · f: 109,773,678 · c: 105,214,733 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 389,678 (0.35%) · h: 10,179,446 (9.20%) · e: 716,421 (0.65%) · f: 282,479 (0.26%) · c: 99,025,809 (89.54%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 110,593,833 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 281948d330399bc8bef96bf162963b9affd0e192290508a158818d7b8d0807f8
the corpus checksum ledger names this file with the same digest
joined 110,596,404 to merged 110,593,833, minus 2,571 (minus 0.0023%)
boundary drops 2,571 · 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-15T12:01:38Z 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,588,610 121,017,574 0-40 ac65314e5c70d104c580dea71fe24bbe47971cdbb1cce9c4d9b8c5c4fed105d2 book 828,911 65,660,702 41-44 18cd5e05a502e8c829dec875bf33f3e3fb7691b421cf6b4cbb4d167f5586610e last_trade_price 53,965 3,084,436 45-45 094fa1e200189794d1fd32206c57b420ce8e3e8692ec086fa4eed1740f4287cb market_resolved 827 132,978 46-46 36c914ff3a3f771069c6b49e52e646998ee69492a033abfce0912e442129b1c0 new_market 3,038 292,861 47-47 1f8724cd4f645468a9708c8fcc418877919b734395bbc903407ae1e5038afccd price_change 99,114,898 990,992,421 48-426 54b7231112e06928ec50e3511cffb1c793d1a978571d6cf6a32425f5b40180f0 tick_size_change 3,584 131,394 427-427 17b6a31d59d02e2bac828ffb511e85798b7056524285894249d670724101c7e3 EVENT MIX count share price_change 99,114,898 89.62% best_bid_ask 10,588,610 9.57% book 828,911 0.75% last_trade_price 53,965 0.05% tick_size_change 3,584 <0.01% new_market 3,038 <0.01% market_resolved 827 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,588,744 10,588,610 134 1,075 FULL book 829,286 828,911 375 169,340 FULL last_trade_price 53,965 53,965 0 77 FULL market_resolved 827 827 0 16 FULL new_market 3,038 3,038 0 16 FULL price_change 99,116,960 99,114,898 2,062 418 FULL tick_size_change 3,584 3,584 0 43 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,093,438 9,523,733 5ms 14ms 149ms 4.8s 0 transport_latency_assumed best_bid_ask e 10,584,283 64,829 37ms 49ms 303ms 15.9s 0 transport_latency_assumed best_bid_ask f 10,584,162 25,163 45ms 61ms 316ms 13.9s 0 transport_latency_assumed best_bid_ask g 10,575,068 2,877 81ms 110ms 634ms 40.3s 0 transport_latency_assumed best_bid_ask h 10,584,088 972,008 18ms 28ms 255ms 47.4s 0 transport_latency_assumed book c 459,164 442,650 2.8min 1.2d 33.8d 108.5d 0 book_staleness book e 119,847 5,194 39ms 653ms 2.0h 90.0d 0 book_staleness book f 119,259 4,642 48ms 575ms 1.6h 108.5d 0 book_staleness book g 665,976 360,622 4.2min 1.7d 34.7d 108.5d 0 book_staleness book h 118,232 15,803 22ms 153ms 28.0min 89.9d 0 book_staleness last_trade_price c 51,176 47,708 11ms 56ms 275ms 5.0s 0 transport_latency_assumed last_trade_price e 53,779 449 49ms 284ms 2.2s 16.0s 0 transport_latency_assumed last_trade_price f 53,752 206 59ms 283ms 2.6s 14.1s 0 transport_latency_assumed last_trade_price g 53,268 29 100ms 553ms 7.4s 40.4s 0 transport_latency_assumed last_trade_price h 53,718 5,573 25ms 101ms 538ms 26.8s 0 transport_latency_assumed market_resolved c 770 745 5ms 23ms 4.5min 4.5min 0 transport_latency_assumed market_resolved e 786 6 37ms 116ms 428ms 59.9s 0 transport_latency_assumed market_resolved f 786 4 46ms 137ms 504ms 692ms 0 transport_latency_assumed market_resolved g 786 not meas. 82ms 251ms 654ms 1.1s 0 transport_latency_assumed market_resolved h 786 72 18ms 60ms 180ms 1.0min 0 transport_latency_assumed new_market c 1,926 1,075 136ms 2.7min 4.9min 24.6min 0 transport_latency_assumed new_market e 1,871 363 213ms 22.7s 41.7s 1.1min 0 transport_latency_assumed new_market f 1,871 387 196ms 20.8s 29.8s 57.9s 0 transport_latency_assumed new_market g 1,871 302 316ms 22.4s 46.4s 1.4min 0 transport_latency_assumed new_market h 1,871 911 156ms 20.2s 35.3s 1.2min 0 transport_latency_assumed price_change c 94,604,847 89,006,597 5ms 16ms 167ms 4.9s 0 transport_latency_assumed price_change e 99,036,134 645,576 37ms 65ms 582ms 16.1s 0 transport_latency_assumed price_change f 99,010,264 252,077 45ms 76ms 551ms 14.3s 0 transport_latency_assumed price_change g 98,777,355 25,848 83ms 145ms 1.5s 40.4s 0 transport_latency_assumed price_change h 99,044,000 9,184,800 18ms 34ms 326ms 47.9s 0 transport_latency_assumed tick_size_change c 3,412 3,301 5ms 9ms 49ms 433ms 0 transport_latency_assumed tick_size_change e 3,584 4 37ms 44ms 119ms 562ms 0 transport_latency_assumed tick_size_change f 3,584 not meas. 45ms 50ms 124ms 206ms 0 transport_latency_assumed tick_size_change g 3,584 not meas. 78ms 97ms 224ms 454ms 0 transport_latency_assumed tick_size_change h 3,584 279 18ms 31ms 65ms 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-15/10/2026-09-15T10.parquet sha256sum 2026-09-15T10.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.