Hour audit: 2026-09-14T07
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-14T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T07:00:00.000814283+00:00 · last event 2026-09-14T07:59:59.999942540+00:00
VOLUME 103,010,194 rows · 1,046,086,348 bytes (997.63 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 102,287,124 · e: 102,271,602 · g: 102,270,887 · h: 102,244,931 · c: 92,568,238 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 137,120 (0.13%) · e: 341,008 (0.33%) · g: 34,043 (0.03%) · h: 13,562,486 (13.17%) · c: 88,935,537 (86.34%) (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 103,010,194 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 91ec47b214406c03e9769ccbc9f120fb72d4e67f58855edf67bbe3a400076d88
the corpus checksum ledger names this file with the same digest
joined 103,012,920 to merged 103,010,194, minus 2,726 (minus 0.0026%)
boundary drops 2,726 · 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-14T08:56:33Z 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 11,448,396 122,794,637 0-43 4ef835e4f8016ecff045cb0763a0b8ccca4b09289ee75dc6e4601010df1805b8 book 789,149 58,892,666 44-47 e3c6c6b6af3abc3caeb551c1bb90bb39220522848e882672bdab75421cf47d16 last_trade_price 43,753 2,529,304 48-48 6204f7b3209a2db5ce80d740f2098d0da155dd763d2035a5c81ffd6083197c55 market_resolved 507 71,940 49-49 849f2f088f640f67ecf8f473771e9ec0afd158baf69f646d073dd905cf471191 new_market 615 62,026 50-50 d30b849af85960801124226bfa83074ac150ee1da7a9a4143ab9ba6f56f59265 price_change 90,725,998 860,494,551 51-397 ba1fbc6b1b774149e46067a278ec66ced05b755f00751b4df25c2861f4a7ec68 tick_size_change 1,776 64,862 398-398 4e8bff06fd8d8d8bcb0062313db6372c1b76123a607ad4f58fb3ede663d30350 EVENT MIX count share price_change 90,725,998 88.07% best_bid_ask 11,448,396 11.11% book 789,149 0.77% last_trade_price 43,753 0.04% tick_size_change 1,776 <0.01% new_market 615 <0.01% market_resolved 507 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,448,668 11,448,396 272 787 FULL book 789,163 789,149 14 163,582 FULL last_trade_price 43,753 43,753 0 173 FULL market_resolved 507 507 0 0 FULL new_market 615 615 0 36 FULL price_change 90,728,438 90,725,998 2,440 784 FULL tick_size_change 1,776 1,776 0 29 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,303,426 9,925,781 5ms 10ms 71ms 3.7s 0 transport_latency_assumed best_bid_ask e 11,447,005 33,133 43ms 46ms 111ms 2.9s 0 transport_latency_assumed best_bid_ask f 11,446,124 12,411 47ms 51ms 123ms 12.5s 0 transport_latency_assumed best_bid_ask g 11,442,653 885 81ms 96ms 227ms 12.7s 0 transport_latency_assumed best_bid_ask h 11,444,330 1,476,186 18ms 22ms 77ms 16.1s 0 transport_latency_assumed book c 749,660 737,593 21.6min 2.6d 36.6d 107.4d 0 book_staleness book e 92,482 1,463 45ms 108ms 1.2h 88.9d 0 book_staleness book f 106,635 5,948 49ms 3.5min 6.9d 107.4d 0 book_staleness book g 139,699 22,352 101ms 9.4h 22.6d 107.4d 0 book_staleness book h 118,394 21,793 22ms 2.6h 8.7d 88.9d 0 book_staleness last_trade_price c 39,435 37,502 10ms 42ms 178ms 4.7s 0 transport_latency_assumed last_trade_price e 43,648 208 49ms 104ms 722ms 4.8s 0 transport_latency_assumed last_trade_price f 43,668 100 53ms 118ms 1.2s 11.2s 0 transport_latency_assumed last_trade_price g 43,596 23 92ms 209ms 1.5s 4.9s 0 transport_latency_assumed last_trade_price h 43,648 5,920 23ms 58ms 209ms 5.8s 0 transport_latency_assumed market_resolved c 441 420 5ms 3.0min 5.8min 6.0min 0 transport_latency_assumed market_resolved e 441 3 45ms 172ms 52.0s 1.0min 0 transport_latency_assumed market_resolved f 441 1 49ms 182ms 52.0s 1.0min 0 transport_latency_assumed market_resolved g 441 4 88ms 254ms 1.4s 1.0min 0 transport_latency_assumed market_resolved h 441 79 19ms 64ms 51.9s 1.0min 0 transport_latency_assumed new_market c 371 238 73ms 20.3s 3.7min 3.8min 0 transport_latency_assumed new_market e 400 57 167ms 13.0s 22.1s 1.3min 0 transport_latency_assumed new_market f 400 46 163ms 17.3s 22.4s 1.2min 0 transport_latency_assumed new_market g 400 75 305ms 23.4s 53.0s 1.1min 0 transport_latency_assumed new_market h 400 199 127ms 19.7s 24.2s 59.7s 0 transport_latency_assumed price_change c 81,473,245 78,232,355 5ms 11ms 80ms 5.6s 0 transport_latency_assumed price_change e 90,685,850 306,144 43ms 48ms 153ms 3.6s 0 transport_latency_assumed price_change f 90,688,080 118,614 47ms 54ms 179ms 12.9s 0 transport_latency_assumed price_change g 90,642,322 10,704 81ms 100ms 308ms 14.3s 0 transport_latency_assumed price_change h 90,635,942 12,058,181 18ms 24ms 95ms 17.6s 0 transport_latency_assumed tick_size_change c 1,660 1,648 5ms 8ms 25ms 68ms 0 transport_latency_assumed tick_size_change e 1,776 not meas. 42ms 46ms 114ms 193ms 0 transport_latency_assumed tick_size_change f 1,776 not meas. 47ms 51ms 76ms 983ms 0 transport_latency_assumed tick_size_change g 1,776 not meas. 81ms 94ms 116ms 332ms 0 transport_latency_assumed tick_size_change h 1,776 128 18ms 20ms 55ms 79ms 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-14/07/2026-09-14T07.parquet sha256sum 2026-09-14T07.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.