Hour audit: 2026-09-29T08
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-29T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T08:00:00.000069694+00:00 · last event 2026-09-29T08:59:59.999985659+00:00
VOLUME 103,179,430 rows · 1,100,811,192 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 102,692,619 · g: 102,530,377 · h: 101,739,724 · i: 100,268,575 · c: 100,198,477 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 5,366,557 (5.20%) · g: 35,800 (0.03%) · h: 1,028,552 (1.00%) · i: 4,151,786 (4.02%) · c: 92,596,735 (89.74%) (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 103,179,430 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 43c36af24b1928890eba1d9d2b7da4d309c181b17bad54b7d8695ec7dba482e3
the corpus checksum ledger names this file with the same digest
joined 103,180,984 to merged 103,179,430, minus 1,554 (minus 0.0015%)
boundary drops 1,554 · 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-29T11:15:31Z 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 10,690,976 122,487,712 0-40 8e2f04d6cab6f3f8e9b9733b362c311a688e71872cbd0c67d5ba29d631976258 book 452,834 39,249,459 41-42 245b59c8c2838be265de65d778ee607e4cc49914212985b5141a58f99b276d14 last_trade_price 45,294 2,631,579 43-43 ae81c4d485b991153dda5ce44775cbf97f85f09b40ec0c7dd8883580c0008eec market_resolved 667 111,074 44-44 dea9a90c942baa596427b68258c5ce21ac404d8c4daf4d8b2b0f10590ae794b7 new_market 1,179 115,586 45-45 f0b9d9c94c04b9493732d791ec13e8f465c9bbc80f5139dfb23440b95158805f price_change 91,984,920 934,910,237 46-396 c45069f8965fd5910589280d38e2854eff490e096981ff9e028a77b28ef7bfa2 tick_size_change 3,560 130,987 397-397 9d77e53e3164df7ae6f0dde10a3be4f778f7356d32cb750bbbf5fb36639b223a EVENT MIX count share price_change 91,984,920 89.15% best_bid_ask 10,690,976 10.36% book 452,834 0.44% last_trade_price 45,294 0.04% tick_size_change 3,560 <0.01% new_market 1,179 <0.01% market_resolved 667 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,691,160 10,690,976 184 2,106 FULL book 452,872 452,834 38 129,190 FULL last_trade_price 45,294 45,294 0 130 FULL market_resolved 671 667 4 40 FULL new_market 1,179 1,179 0 0 FULL price_change 91,986,248 91,984,920 1,328 3,505 FULL tick_size_change 3,560 3,560 0 39 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,418,294 9,678,672 5ms 10ms 101ms 14.9s 0 transport_latency_assumed best_bid_ask g 10,685,561 802 78ms 99ms 392ms 19.0s 0 transport_latency_assumed best_bid_ask h 10,646,652 89,168 18ms 25ms 162ms 1.0min 0 transport_latency_assumed best_bid_ask i 10,434,073 387,536 20ms 27ms 101ms 11.0s 0 transport_latency_assumed best_bid_ask k 10,689,511 534,798 12ms 21ms 107ms 21.3s 0 transport_latency_assumed book c 395,447 377,657 39.1min 2.0d 37.8d 122.4d 0 book_staleness book g 122,832 26,642 94ms 8.0h 21.9d 103.9d 0 book_staleness book h 108,906 22,036 22ms 46.2s 1.0d 122.4d 0 book_staleness book i 92,378 7,742 22ms 69ms 7.7h 103.9d 0 book_staleness book k 110,401 18,757 17ms 1.3h 16.8d 103.9d 0 book_staleness last_trade_price c 43,280 39,548 6ms 16ms 197ms 3.5s 0 transport_latency_assumed last_trade_price g 44,478 14 82ms 347ms 6.4s 18.7s 0 transport_latency_assumed last_trade_price h 43,468 537 19ms 42ms 437ms 24.3s 0 transport_latency_assumed last_trade_price i 44,347 2,720 21ms 44ms 358ms 2.1s 0 transport_latency_assumed last_trade_price k 45,151 2,475 14ms 38ms 278ms 7.0s 0 transport_latency_assumed market_resolved c 645 554 5ms 30ms 38.4s 1.9min 0 transport_latency_assumed market_resolved g 656 17 81ms 238ms 14.7s 15.8s 0 transport_latency_assumed market_resolved h 649 10 19ms 58ms 17.8s 20.5s 0 transport_latency_assumed market_resolved i 640 55 21ms 80ms 13.6s 2.2min 0 transport_latency_assumed market_resolved k 660 31 14ms 54ms 27.0s 1.5min 0 transport_latency_assumed new_market c 735 330 143ms 20.3s 26.5s 1.7min 0 transport_latency_assumed new_market g 735 77 364ms 24.1s 44.0s 1.3min 0 transport_latency_assumed new_market h 735 225 192ms 21.8s 56.9s 1.8min 0 transport_latency_assumed new_market i 735 251 132ms 15.3s 32.9s 1.5min 0 transport_latency_assumed new_market k 735 296 186ms 21.7s 56.0s 1.9min 0 transport_latency_assumed price_change c 89,336,612 82,496,685 5ms 12ms 118ms 21.6s 0 transport_latency_assumed price_change g 91,672,555 8,248 79ms 124ms 1.6s 19.0s 0 transport_latency_assumed price_change h 90,935,754 916,570 18ms 30ms 217ms 1.1min 0 transport_latency_assumed price_change i 89,692,914 3,753,358 20ms 29ms 187ms 11.0s 0 transport_latency_assumed price_change k 91,842,601 4,810,059 12ms 25ms 137ms 21.3s 0 transport_latency_assumed tick_size_change c 3,464 3,289 5ms 9ms 96ms 175ms 0 transport_latency_assumed tick_size_change g 3,560 not meas. 77ms 92ms 143ms 389ms 0 transport_latency_assumed tick_size_change h 3,560 6 18ms 24ms 57ms 165ms 0 transport_latency_assumed tick_size_change i 3,488 124 19ms 27ms 48ms 84ms 0 transport_latency_assumed tick_size_change k 3,560 141 12ms 17ms 56ms 87ms 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-29/08/2026-09-29T08.parquet sha256sum 2026-09-29T08.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.