Hour audit: 2026-09-20T10
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-20T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-20T10:00:00.000027221+00:00 · last event 2026-09-20T10:59:59.999549583+00:00
VOLUME 107,051,414 rows · 1,103,875,348 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 106,983,969 · h: 106,964,079 · f: 106,943,330 · e: 106,935,403 · g: 106,782,634 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 101,621,344 (94.93%) · h: 4,626,520 (4.32%) · f: 253,935 (0.24%) · e: 503,371 (0.47%) · g: 46,244 (0.04%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 66c9e69990bc28798063de9e11eb2ed40fc94f441856564b89f0d08b8dcf973e
the corpus checksum ledger names this file with the same digest
joined 107,054,039 to merged 107,051,414, minus 2,625 (minus 0.0025%)
boundary drops 2,625 · 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-20T12:35: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 11,092,636 126,944,284 0-42 e4c4c40322f127e95943d358b4664d3fd9a2c0bbf4e6efa44e28d907802e6f6d book 150,124 16,226,975 43-43 43d7e56bce26a44343d00e4d0abcec031cc80096d6cd62d23a8d80508308dbc7 last_trade_price 54,393 3,194,476 44-44 826078232f104a2518287516dd9e1174e53c9498388c21822f37e96dffb510dd market_resolved 1,124 174,293 45-45 e2bb614d3ac00a712b0198cc5a4719b19303a785fc9cef3fcb29d2443fefe2ec new_market 2,899 283,505 46-46 c4315ece1a4a34ec744088929569af6ea2df93caf29c1d908cea5debd0f4dcdd price_change 95,745,454 955,662,922 47-412 1e40c3f72f6a15c40326ff8e8c0434342d4a0aa6032e13aac49a54377a719f99 tick_size_change 4,784 168,131 413-413 5d87c2593832f4930bc9cdb61d6fe3aa2cc91bf1cbec47867c5c8a3207f59e2a EVENT MIX count share price_change 95,745,454 89.44% best_bid_ask 11,092,636 10.36% book 150,124 0.14% last_trade_price 54,393 0.05% tick_size_change 4,784 <0.01% new_market 2,899 <0.01% market_resolved 1,124 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,092,823 11,092,636 187 562 FULL book 150,124 150,124 0 14,453 FULL last_trade_price 54,393 54,393 0 0 FULL market_resolved 1,124 1,124 0 0 FULL new_market 2,899 2,899 0 0 FULL price_change 95,747,892 95,745,454 2,438 267 FULL tick_size_change 4,784 4,784 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,090,216 10,563,960 5ms 12ms 169ms 6.6s 0 transport_latency_assumed best_bid_ask e 11,088,669 47,284 40ms 51ms 274ms 15.6s 0 transport_latency_assumed best_bid_ask f 11,087,942 22,695 46ms 59ms 298ms 11.2s 0 transport_latency_assumed best_bid_ask g 11,085,306 2,732 77ms 101ms 565ms 28.6s 0 transport_latency_assumed best_bid_ask h 11,089,281 455,965 18ms 30ms 284ms 59.0s 0 transport_latency_assumed book c 122,359 113,164 7ms 690ms 1.8d 95.0d 0 book_staleness book e 120,185 8,933 43ms 758ms 20.7h 94.9d 0 book_staleness book f 119,177 7,683 50ms 635ms 15.1h 95.0d 0 book_staleness book g 121,517 10,718 85ms 4.2s 1.8d 95.0d 0 book_staleness book h 115,398 9,626 23ms 127ms 18.1min 94.9d 0 book_staleness last_trade_price c 54,140 50,722 6ms 25ms 256ms 1.6s 0 transport_latency_assumed last_trade_price e 54,175 358 42ms 173ms 1.4s 15.7s 0 transport_latency_assumed last_trade_price f 54,061 234 49ms 188ms 1.7s 11.2s 0 transport_latency_assumed last_trade_price g 53,465 73 82ms 295ms 8.1s 28.8s 0 transport_latency_assumed last_trade_price h 54,240 3,006 20ms 60ms 438ms 56.8s 0 transport_latency_assumed market_resolved c 1,088 1,042 5ms 26ms 54.2s 56.8s 0 transport_latency_assumed market_resolved e 1,088 4 42ms 209ms 54.4s 57.0s 0 transport_latency_assumed market_resolved f 1,088 36 48ms 201ms 633ms 5.8s 0 transport_latency_assumed market_resolved g 1,088 1 81ms 342ms 996ms 1.3min 0 transport_latency_assumed market_resolved h 1,088 41 20ms 99ms 55.8s 58.5s 0 transport_latency_assumed new_market c 1,860 1,120 99ms 29.0s 54.1s 2.8h 0 transport_latency_assumed new_market e 1,860 284 205ms 29.3s 53.0s 1.3min 0 transport_latency_assumed new_market f 1,860 331 213ms 28.7s 53.5s 3.3h 0 transport_latency_assumed new_market g 1,860 376 294ms 28.4s 52.8s 4.7h 0 transport_latency_assumed new_market h 1,860 788 156ms 28.2s 54.8s 36.4min 0 transport_latency_assumed price_change c 95,709,522 90,886,716 5ms 14ms 186ms 7.0s 0 transport_latency_assumed price_change e 95,664,642 446,500 41ms 63ms 430ms 15.7s 0 transport_latency_assumed price_change f 95,674,418 222,944 47ms 72ms 461ms 11.2s 0 transport_latency_assumed price_change g 95,514,614 32,340 78ms 130ms 1.1s 28.8s 0 transport_latency_assumed price_change h 95,697,428 4,156,954 19ms 35ms 314ms 59.1s 0 transport_latency_assumed tick_size_change c 4,784 4,620 5ms 10ms 133ms 264ms 0 transport_latency_assumed tick_size_change e 4,784 8 40ms 46ms 248ms 574ms 0 transport_latency_assumed tick_size_change f 4,784 12 46ms 54ms 244ms 472ms 0 transport_latency_assumed tick_size_change g 4,784 4 77ms 91ms 423ms 983ms 0 transport_latency_assumed tick_size_change h 4,784 140 18ms 26ms 252ms 2.5s 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-20/10/2026-09-20T10.parquet sha256sum 2026-09-20T10.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.