Hour audit: 2026-09-17T21
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-17T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T21:00:00.000050900+00:00 · last event 2026-09-17T21:59:59.999728018+00:00
VOLUME 111,770,531 rows · 1,171,205,682 bytes (1.09 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 111,135,627 · h: 110,552,773 · f: 110,205,658 · g: 109,398,169 · c: 106,438,214 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,504,912 (1.35%) · h: 8,167,295 (7.31%) · f: 400,700 (0.36%) · g: 78,003 (0.07%) · c: 101,619,621 (90.92%) (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 111,770,531 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 75b60161308405f3c0c886261731c1c7b23c870f4be504f09835da665b97c90c
the corpus checksum ledger names this file with the same digest
joined 111,773,007 to merged 111,770,531, minus 2,476 (minus 0.0022%)
boundary drops 2,476 · 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-17T23:36:39Z 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,804,466 123,277,582 0-41 318b2d584180ebc1d92bb816d897660da7b47095fff8c3b7563c5b172075f547 book 603,078 58,229,988 42-44 59720a96b64e9a35695850eb2199f580b7fda62dd0b82cd1f4846affd308504b last_trade_price 48,176 2,782,248 45-45 aa54a02bcc8d30bbcc61cf0bda43c8dbd10f7ab7bab1f40b3e83b56bbf8d5d1f market_resolved 1,032 156,796 46-46 8f252378beadc7b64f965d4b2da03e4e517e300d7bb6fea669b521281db19d2c new_market 3,053 308,480 47-47 3599adc1b9e6a0246624f15218da8d93250d33baa9dfc8f4324f3e789cd333e9 price_change 100,307,798 985,069,258 48-430 2f9b8198d07f453d5109b7411fccbf4e060c4366d52c7b5ada9699ce6b5ba198 tick_size_change 2,928 107,410 431-431 0db42210722fb199e7fb7166325ce364bb6265155ade298174a5e14c619264ee EVENT MIX count share price_change 100,307,798 89.74% best_bid_ask 10,804,466 9.67% book 603,078 0.54% last_trade_price 48,176 0.04% new_market 3,053 <0.01% tick_size_change 2,928 <0.01% market_resolved 1,032 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,804,714 10,804,466 248 3,118 FULL book 603,290 603,078 212 186,277 FULL last_trade_price 48,176 48,176 0 204 FULL market_resolved 1,032 1,032 0 43 FULL new_market 3,053 3,053 0 0 FULL price_change 100,309,814 100,307,798 2,016 4,434 FULL tick_size_change 2,928 2,928 0 57 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,327,588 9,885,302 5ms 10ms 137ms 3.5s 0 transport_latency_assumed best_bid_ask e 10,798,408 139,038 40ms 49ms 245ms 16.7s 0 transport_latency_assumed best_bid_ask f 10,707,077 32,040 47ms 58ms 273ms 12.4s 0 transport_latency_assumed best_bid_ask g 10,671,580 3,678 80ms 105ms 507ms 38.6s 0 transport_latency_assumed best_bid_ask h 10,744,509 744,408 17ms 33ms 277ms 45.1s 0 transport_latency_assumed book c 508,411 491,523 2.3min 4.5h 36.1d 111.0d 0 book_staleness book e 138,527 32,378 50ms 9.1min 12.3d 111.0d 0 book_staleness book f 127,063 20,972 54ms 4.1min 10.5d 111.0d 0 book_staleness book g 133,176 28,545 114ms 8.9min 11.9d 110.9d 0 book_staleness book h 124,163 29,660 23ms 2.5min 10.4d 111.0d 0 book_staleness last_trade_price c 44,091 41,681 10ms 51ms 276ms 5.0s 0 transport_latency_assumed last_trade_price e 47,492 786 50ms 257ms 5.0s 16.8s 0 transport_latency_assumed last_trade_price f 47,269 374 59ms 251ms 3.6s 12.4s 0 transport_latency_assumed last_trade_price g 45,826 104 101ms 605ms 19.8s 38.8s 0 transport_latency_assumed last_trade_price h 47,785 5,231 24ms 100ms 775ms 8.1s 0 transport_latency_assumed market_resolved c 948 919 5ms 12ms 236ms 5.7min 0 transport_latency_assumed market_resolved e 969 59 43ms 285ms 54.2s 55.0s 0 transport_latency_assumed market_resolved f 963 8 49ms 224ms 6.3s 2.4min 0 transport_latency_assumed market_resolved g 964 3 85ms 349ms 1.1s 2.4min 0 transport_latency_assumed market_resolved h 963 43 19ms 129ms 56.1s 1.3min 0 transport_latency_assumed new_market c 1,998 1,222 75ms 13.8s 40.0s 1.2min 0 transport_latency_assumed new_market e 1,998 449 167ms 21.7s 53.6s 1.1min 0 transport_latency_assumed new_market f 1,998 278 155ms 23.6s 55.2s 1.2min 0 transport_latency_assumed new_market g 1,998 263 300ms 30.9s 1.0min 1.4min 0 transport_latency_assumed new_market h 1,998 841 127ms 24.8s 53.4s 1.2min 0 transport_latency_assumed price_change c 95,552,410 91,196,254 5ms 12ms 155ms 4.5s 0 transport_latency_assumed price_change e 100,145,305 1,332,186 40ms 58ms 451ms 16.7s 0 transport_latency_assumed price_change f 99,318,380 347,028 48ms 68ms 464ms 12.5s 0 transport_latency_assumed price_change g 98,541,733 45,410 81ms 129ms 1.2s 38.8s 0 transport_latency_assumed price_change h 99,630,439 7,386,920 18ms 37ms 324ms 45.2s 0 transport_latency_assumed tick_size_change c 2,768 2,720 5ms 8ms 36ms 183ms 0 transport_latency_assumed tick_size_change e 2,928 16 40ms 45ms 210ms 694ms 0 transport_latency_assumed tick_size_change f 2,908 not meas. 47ms 53ms 132ms 545ms 0 transport_latency_assumed tick_size_change g 2,892 not meas. 79ms 95ms 287ms 394ms 0 transport_latency_assumed tick_size_change h 2,916 192 17ms 31ms 208ms 5.1s 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-17/21/2026-09-17T21.parquet sha256sum 2026-09-17T21.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.