Hour audit: 2026-09-24T07
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-24T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-24T07:00:00.000155502+00:00 · last event 2026-09-24T07:59:59.999968274+00:00
VOLUME 108,014,167 rows · 1,119,295,148 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 107,670,766 · k: 107,438,576 · h: 107,390,786 · g: 107,322,703 · c: 102,863,257 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 987,234 (0.91%) · k: 9,672,296 (8.95%) · h: 1,012,705 (0.94%) · g: 36,855 (0.03%) · c: 96,305,077 (89.16%) (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 108,014,167 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6904d531397fa2043df5bd02105da398d72275b0331f52cb2d6607c974f12816
the corpus checksum ledger names this file with the same digest
joined 108,017,273 to merged 108,014,167, minus 3,106 (minus 0.0029%)
boundary drops 3,106 · 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-24T10:08:29Z 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 11,606,780 131,971,326 0-44 29d4fe8fb6eac0c3a82cfd2b2555118d54e8a87d0e6df5594b0df3056e150ffa book 663,083 56,974,388 45-47 eb21f0c7b6fb80e8f1d9975fe10bdfb6b5bccea08b5dc1fe53a48e24dbd239c1 last_trade_price 47,233 2,677,880 48-48 93d4c90ca9c6327ed4664dd40706a59759225d6f3c7bfaa8097a5ff6c6c83da9 market_resolved 569 86,869 49-49 a5cdc8d7d7d932bee57bf461ac1f0357eb4d168e6618d30123d08b1593ad32ef new_market 1,172 125,411 50-50 151428b95e9f1302295db4013fa2b41d0a44085cf0302343e929b88ac0cfc45f price_change 95,693,354 926,152,734 51-416 37ffec98e7a3e1c3ed08e66309b64301a5afaaafa6370520bfd9a17abd1e823a tick_size_change 1,976 72,815 417-417 b614f6f1497ec3547318b42a5917c69cbc0dc048c9cd7136dcb6c41579a1ab51 EVENT MIX count share price_change 95,693,354 88.59% best_bid_ask 11,606,780 10.75% book 663,083 0.61% last_trade_price 47,233 0.04% tick_size_change 1,976 <0.01% new_market 1,172 <0.01% market_resolved 569 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,607,022 11,606,780 242 489 FULL book 664,209 663,083 1,126 194,236 FULL last_trade_price 47,233 47,233 0 90 FULL market_resolved 569 569 0 7 FULL new_market 1,172 1,172 0 3 FULL price_change 95,695,092 95,693,354 1,738 476 FULL tick_size_change 1,976 1,976 0 20 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,025,226 10,371,751 4ms 9ms 100ms 6.2s 0 transport_latency_assumed best_bid_ask g 11,603,462 539 78ms 97ms 345ms 28.1s 0 transport_latency_assumed best_bid_ask h 11,605,706 98,826 18ms 41ms 148ms 23.0s 0 transport_latency_assumed best_bid_ask i 11,604,737 84,775 21ms 27ms 105ms 7.8s 0 transport_latency_assumed best_bid_ask k 11,606,096 1,050,889 12ms 17ms 86ms 8.6s 0 transport_latency_assumed book c 535,360 431,172 5.3min 3.4d 39.7d 117.4d 0 book_staleness book g 133,514 32,050 95ms 30.5min 18.7d 117.4d 0 book_staleness book h 101,382 6,019 22ms 142ms 1.4d 98.9d 0 book_staleness book i 340,338 176,104 2.3min 2.5d 32.7d 117.4d 0 book_staleness book k 105,699 17,738 15ms 1.6s 3.5d 98.9d 0 book_staleness last_trade_price c 44,704 40,977 5ms 16ms 175ms 3.5s 0 transport_latency_assumed last_trade_price g 46,643 4 84ms 244ms 6.8s 28.3s 0 transport_latency_assumed last_trade_price h 47,077 577 19ms 61ms 350ms 7.5s 0 transport_latency_assumed last_trade_price i 47,215 327 23ms 70ms 508ms 7.2s 0 transport_latency_assumed last_trade_price k 47,188 5,348 13ms 24ms 148ms 6.9s 0 transport_latency_assumed market_resolved c 520 425 5ms 38.5s 3.6min 5.2min 0 transport_latency_assumed market_resolved g 527 not meas. 88ms 37.0s 51.1s 57.7s 0 transport_latency_assumed market_resolved h 527 5 26ms 30.2s 44.3s 55.9s 0 transport_latency_assumed market_resolved i 527 102 26ms 30.1s 57.3s 57.8s 0 transport_latency_assumed market_resolved k 527 37 14ms 32.1s 44.2s 47.1s 0 transport_latency_assumed new_market c 814 367 91ms 13.1s 2.2min 5.8min 0 transport_latency_assumed new_market g 817 86 258ms 13.6s 1.8min 2.3min 0 transport_latency_assumed new_market h 817 292 124ms 15.8s 1.8min 2.2min 0 transport_latency_assumed new_market i 817 192 115ms 10.7s 1.5min 2.3min 0 transport_latency_assumed new_market k 817 235 108ms 556ms 1.9min 2.2min 0 transport_latency_assumed price_change c 91,254,737 85,458,546 4ms 10ms 111ms 8.5s 0 transport_latency_assumed price_change g 95,535,764 4,176 79ms 104ms 554ms 28.8s 0 transport_latency_assumed price_change h 95,633,301 906,982 18ms 44ms 171ms 23.6s 0 transport_latency_assumed price_change i 95,675,156 725,734 21ms 30ms 144ms 8.0s 0 transport_latency_assumed price_change k 95,676,273 8,597,916 12ms 18ms 98ms 8.6s 0 transport_latency_assumed tick_size_change c 1,896 1,839 4ms 8ms 21ms 35ms 0 transport_latency_assumed tick_size_change g 1,976 not meas. 78ms 96ms 246ms 591ms 0 transport_latency_assumed tick_size_change h 1,976 4 18ms 39ms 84ms 250ms 0 transport_latency_assumed tick_size_change i 1,976 not meas. 21ms 28ms 61ms 96ms 0 transport_latency_assumed tick_size_change k 1,976 133 12ms 16ms 44ms 204ms 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/07/2026-09-24T07.parquet sha256sum 2026-09-24T07.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.