Hour audit: 2026-09-24T23
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-24T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T23:00:00.000017545+00:00 · last event 2026-09-24T23:59:59.999995489+00:00
VOLUME 116,866,141 rows · 1,227,616,132 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 116,430,932 · k: 116,417,506 · h: 116,415,519 · g: 116,382,692 · c: 111,586,534 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,220,887 (1.04%) · k: 9,905,138 (8.48%) · h: 1,227,542 (1.05%) · g: 6,796 (0.01%) · c: 104,505,778 (89.42%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 116,866,141 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2a117be35ee8de903b51ffd28c949f3cf303c6090f7c36b702e51877101bd369
the corpus checksum ledger names this file with the same digest
joined 116,878,252 to merged 116,866,141, minus 12,111 (minus 0.0104%)
boundary drops 12,111 · 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-25T01:54:33Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,428,156 152,533,178 0-51 176ec40d9c5e5f42a9b2f1557b789dd174a3c3d7f61722996d856053555fd7ba book 515,309 50,545,229 52-53 a0feea15dbcd82355cb87f79f2aad25d247201d20430117ccfc31f1e98edf2e9 last_trade_price 46,432 2,657,373 54-54 4d5efb685857cf1a1488c728254abe12cb76fdec39f4a186ac40e4ccd0201452 market_resolved 604 94,175 55-55 8f7e0f690d1d00a5b038a34e31f78f4e229c45d0b36aca0b6dd02e1b09986021 new_market 840 85,770 56-56 091e680204f96d8d01286bf673e78968b8655dd70c4e866beb1ada90695d942b price_change 102,872,852 1,020,297,370 57-449 7dd46c1910baccb21e637395ba6e95a4e6e3ca6a0bdf3da954a60d6d43b584eb tick_size_change 1,948 72,398 450-450 2f511da0b4cac00849ca23ba7468266a6754811c043bdc6d5a1f621331582ef6 EVENT MIX count share price_change 102,872,852 88.03% best_bid_ask 13,428,156 11.49% book 515,309 0.44% last_trade_price 46,432 0.04% tick_size_change 1,948 <0.01% new_market 840 <0.01% market_resolved 604 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,428,425 13,428,156 269 756 FULL book 524,991 515,309 9,682 203,591 FULL last_trade_price 46,432 46,432 0 56 FULL market_resolved 604 604 0 7 FULL new_market 840 840 0 1 FULL price_change 102,875,012 102,872,852 2,160 516 FULL tick_size_change 1,948 1,948 0 10 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,814,893 12,048,577 4ms 9ms 81ms 4.4s 0 transport_latency_assumed best_bid_ask g 13,426,226 365 82ms 101ms 266ms 13.7s 0 transport_latency_assumed best_bid_ask h 13,427,106 125,469 18ms 27ms 108ms 43.1s 0 transport_latency_assumed best_bid_ask i 13,427,082 131,895 19ms 24ms 84ms 4.5s 0 transport_latency_assumed best_bid_ask k 13,426,825 1,121,850 12ms 18ms 80ms 11.1s 0 transport_latency_assumed book c 508,473 486,456 6.2min 3.3d 33.4d 118.0d 0 book_staleness book g 96,537 1,804 87ms 312ms 34.5min 99.5d 0 book_staleness book h 96,116 3,024 22ms 75ms 28.9min 99.5d 0 book_staleness book i 99,705 5,600 21ms 180ms 2.9d 99.6d 0 book_staleness book k 111,258 18,425 16ms 5.1min 15.6d 99.6d 0 book_staleness last_trade_price c 44,781 40,514 5ms 23ms 238ms 1.6s 0 transport_latency_assumed last_trade_price g 46,283 5 86ms 247ms 1.7s 13.7s 0 transport_latency_assumed last_trade_price h 46,298 967 19ms 53ms 285ms 6.3s 0 transport_latency_assumed last_trade_price i 46,339 719 21ms 61ms 417ms 2.2s 0 transport_latency_assumed last_trade_price k 46,179 4,227 13ms 35ms 242ms 11.2s 0 transport_latency_assumed market_resolved c 579 524 5ms 21ms 4.8min 6.4min 0 transport_latency_assumed market_resolved g 582 27 85ms 306ms 45.9s 51.8s 0 transport_latency_assumed market_resolved h 582 16 19ms 76ms 46.8s 51.1s 0 transport_latency_assumed market_resolved i 582 3 20ms 102ms 52.0s 55.5s 0 transport_latency_assumed market_resolved k 582 34 13ms 57ms 52.7s 56.8s 0 transport_latency_assumed new_market c 543 308 59ms 16.9s 6.6min 6.6min 0 transport_latency_assumed new_market g 534 61 158ms 15.6s 54.5s 1.6min 0 transport_latency_assumed new_market h 535 151 102ms 10.7s 53.0s 1.7min 0 transport_latency_assumed new_market i 534 156 89ms 16.5s 57.1s 1.2min 0 transport_latency_assumed new_market k 534 164 79ms 15.1s 47.2s 58.9s 0 transport_latency_assumed price_change c 98,215,357 91,927,611 5ms 11ms 91ms 4.5s 0 transport_latency_assumed price_change g 102,810,582 4,534 82ms 105ms 356ms 13.7s 0 transport_latency_assumed price_change h 102,842,934 1,097,910 18ms 30ms 134ms 45.7s 0 transport_latency_assumed price_change i 102,854,742 1,082,510 19ms 26ms 114ms 4.5s 0 transport_latency_assumed price_change k 102,830,180 8,760,287 12ms 19ms 95ms 11.2s 0 transport_latency_assumed tick_size_change c 1,908 1,788 4ms 8ms 46ms 90ms 0 transport_latency_assumed tick_size_change g 1,948 not meas. 82ms 98ms 235ms 482ms 0 transport_latency_assumed tick_size_change h 1,948 5 18ms 22ms 52ms 351ms 0 transport_latency_assumed tick_size_change i 1,948 4 19ms 23ms 52ms 78ms 0 transport_latency_assumed tick_size_change k 1,948 151 12ms 16ms 30ms 110ms 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-24/23/2026-09-24T23.parquet sha256sum 2026-09-24T23.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.