Hour audit: 2026-09-23T12
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-23T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T12:00:00.000006507+00:00 · last event 2026-09-23T12:59:59.998964591+00:00
VOLUME 128,837,676 rows · 1,425,280,108 bytes (1.33 GiB) · 7 products, all holding rows
WITNESSES cfghik — 6 machines contributed rows
captured h: 126,829,966 · i: 121,643,435 · f: 120,923,091 · g: 120,494,268 · c: 113,825,158 · k: 112,829,325 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,341,623 (5.70%) · i: 2,294,737 (1.78%) · f: 227,363 (0.18%) · g: 69,299 (0.05%) · c: 102,093,051 (79.24%) · k: 16,811,603 (13.05%) (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 128,837,676 rows exactly, so those pairs supplied none
6 expected, all 6 contributed
INTEGRITY sha256 68167daa10f3bb54abaff79163ea6931c30211c5735d186ce1e4373b341cd667
the corpus checksum ledger names this file with the same digest
joined 128,839,796 to merged 128,837,676, minus 2,120 (minus 0.0016%)
boundary drops 2,120 · 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-23T16:05:03Z as cfghik
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 13,185,542 156,357,599 0-50 862fd80cbdbbc0a395147d54294d8e8082f9ef20df1cc1f13a561a69e289f4c3 book 1,897,087 93,568,663 51-58 27d0afd1c48adc980e74e7f5c3c057ccc81542075e8a26c55b07b84edad95076 last_trade_price 58,302 3,341,613 59-59 3ababc9c8dd4e0ba2869fe076f3743320bdcca82fcd7bc05b435cd68dd89948b market_resolved 1,370 151,325 60-60 10b54c1bde5b96b91379aeebaff1aecbdc831c2f7809cf9cb9f712c284df1383 new_market 1,765 165,778 61-61 6772df5543b664780711e508d61cdd4756e1f73112d634ba6da74c413670876e price_change 113,689,722 1,170,085,982 62-495 a4d89eb1ce7f5f8e1e2a5fc038fb67eb323bb86d5af8fe561a3ff194363b02a0 tick_size_change 3,888 141,457 496-496 f816036c3cde251503fcf8ec4751ce3ac6db38dd65dcae70e14d82c4b9f3f82f EVENT MIX count share price_change 113,689,722 88.24% best_bid_ask 13,185,542 10.23% book 1,897,087 1.47% last_trade_price 58,302 0.05% tick_size_change 3,888 <0.01% new_market 1,765 <0.01% market_resolved 1,370 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,185,768 13,185,542 226 2,506 FULL book 1,897,195 1,897,087 108 191,179 FULL last_trade_price 58,304 58,302 2 461 FULL market_resolved 1,370 1,370 0 39 FULL new_market 1,765 1,765 0 4 FULL price_change 113,691,506 113,689,722 1,784 502 FULL tick_size_change 3,888 3,888 0 167 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,716,962 10,648,403 6ms 15ms 161ms 10.8s 0 transport_latency_assumed best_bid_ask f 12,536,442 5,571 50ms 66ms 294ms 15.9s 0 transport_latency_assumed best_bid_ask g 12,518,278 1,212 79ms 109ms 641ms 34.8s 0 transport_latency_assumed best_bid_ask h 13,182,232 725,542 18ms 32ms 219ms 30.4s 0 transport_latency_assumed best_bid_ask i 12,639,790 211,554 22ms 33ms 141ms 7.9s 0 transport_latency_assumed best_bid_ask k 11,564,008 1,593,260 12ms 20ms 105ms 7.9s 0 transport_latency_assumed book c 980,066 471,082 8.9min 3.9d 41.7d 116.6d 0 book_staleness book f 539,401 154,289 5.3min 2.7d 38.3d 116.6d 0 book_staleness book g 541,427 56,979 5.5min 2.7d 38.8d 116.6d 0 book_staleness book h 122,963 10,653 23ms 173ms 2.3h 98.0d 0 book_staleness book i 521,470 134,297 4.0min 2.5d 37.7d 116.6d 0 book_staleness book k 1,296,620 1,069,787 10.6min 3.9d 42.5d 116.6d 0 book_staleness last_trade_price c 51,388 45,856 7ms 26ms 234ms 1.4s 0 transport_latency_assumed last_trade_price f 54,777 59 54ms 444ms 8.0s 15.9s 0 transport_latency_assumed last_trade_price g 53,273 2 93ms 1.4s 10.8s 34.0s 0 transport_latency_assumed last_trade_price h 57,961 3,666 20ms 87ms 534ms 15.1s 0 transport_latency_assumed last_trade_price i 55,018 1,004 26ms 162ms 991ms 4.2s 0 transport_latency_assumed last_trade_price k 50,606 7,715 14ms 43ms 229ms 1.1s 0 transport_latency_assumed market_resolved c 941 791 6ms 3.2min 5.9min 6.7min 0 transport_latency_assumed market_resolved f 882 5 51ms 543ms 4.9min 5.9min 0 transport_latency_assumed market_resolved g 918 51 81ms 18.5s 5.9min 5.9min 0 transport_latency_assumed market_resolved h 902 75 19ms 9.5s 58.4s 1.0min 0 transport_latency_assumed market_resolved i 890 29 23ms 17.3s 4.9min 4.9min 0 transport_latency_assumed market_resolved k 1,197 419 19ms 10.0min 14.6min 15.7min 0 transport_latency_assumed new_market c 1,042 407 133ms 19.0s 29.1s 4.3min 0 transport_latency_assumed new_market f 1,042 129 230ms 17.8s 28.1s 1.3min 0 transport_latency_assumed new_market g 1,042 97 360ms 20.3s 33.7s 4.4min 0 transport_latency_assumed new_market h 1,042 275 186ms 20.3s 29.3s 1.5min 0 transport_latency_assumed new_market i 1,038 230 161ms 18.1s 31.0s 1.6min 0 transport_latency_assumed new_market k 1,141 627 127ms 3.6min 11.0min 11.0min 0 transport_latency_assumed price_change c 101,071,091 90,923,233 6ms 19ms 191ms 12.1s 0 transport_latency_assumed price_change f 107,786,731 67,310 50ms 87ms 1.2s 16.0s 0 transport_latency_assumed price_change g 107,375,562 10,958 80ms 169ms 4.1s 34.8s 0 transport_latency_assumed price_change h 113,460,978 6,601,277 19ms 40ms 314ms 50.1s 0 transport_latency_assumed price_change i 108,421,501 1,947,572 23ms 43ms 280ms 7.9s 0 transport_latency_assumed price_change k 99,912,285 14,139,372 13ms 25ms 152ms 8.1s 0 transport_latency_assumed tick_size_change c 3,668 3,279 6ms 17ms 123ms 299ms 0 transport_latency_assumed tick_size_change f 3,816 not meas. 50ms 71ms 197ms 415ms 0 transport_latency_assumed tick_size_change g 3,768 not meas. 79ms 129ms 509ms 1.3s 0 transport_latency_assumed tick_size_change h 3,888 135 19ms 38ms 166ms 858ms 0 transport_latency_assumed tick_size_change i 3,728 51 22ms 38ms 104ms 261ms 0 transport_latency_assumed tick_size_change k 3,468 423 13ms 21ms 55ms 104ms 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-23/12/2026-09-23T12.parquet sha256sum 2026-09-23T12.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.