Hour audit: 2026-09-29T14
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-29T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T14:00:00.000003008+00:00 · last event 2026-09-29T14:59:59.999990108+00:00
VOLUME 116,713,066 rows · 1,353,130,886 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 115,270,716 · h: 115,196,469 · i: 113,498,971 · g: 112,563,732 · c: 100,339,245 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 21,986,971 (18.84%) · h: 4,591,088 (3.93%) · i: 3,806,330 (3.26%) · g: 71,717 (0.06%) · c: 86,256,960 (73.91%) (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,713,066 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1482ff7a72bb905f65d43d151fc309b3258aba49b0a69ab8dc53c482f04f6b62
the corpus checksum ledger names this file with the same digest
joined 116,723,147 to merged 116,713,066, minus 10,081 (minus 0.0086%)
boundary drops 10,081 · 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-29T17:19:50Z 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,509,518 131,990,403 0-40 572b6d4675441014907f9dd105a4f221c4d2c06fe437c44b7dd228038c41cc99 book 1,538,946 81,876,334 41-46 9671c36cb4d06598ec88ad7b78dd5b7f005d0e7e54372867ac0a6e4e88215ca6 last_trade_price 67,889 3,918,360 47-47 d2e6a493eae3450b66f22d7756af607b2c93aabb85446c4cf5aca693d2df49bb market_resolved 1,319 159,531 48-48 64d45f9ba939f91bf4b82f923daea77103f32855a1c07811c2a74626778ceeaf new_market 3,280 310,191 49-49 79e8b1e11ee900547739aa0ccce35b4f2c18d6ec9685351dedb8896d44dcd8e5 price_change 104,588,926 1,133,428,775 50-448 72b9aa543b33ecb76fca835ce7ce1a710a71bf3f39c6a0fe9da753203a4df762 tick_size_change 3,188 118,767 449-449 f0aa09914582bd0f6f578a20f6d11a579bb8dd2dd7e41558e26b76a876bb1c7a EVENT MIX count share price_change 104,588,926 89.61% best_bid_ask 10,509,518 9.00% book 1,538,946 1.32% last_trade_price 67,889 0.06% new_market 3,280 <0.01% tick_size_change 3,188 <0.01% market_resolved 1,319 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,510,411 10,509,518 893 2,094 FULL book 1,541,846 1,538,946 2,900 223,453 FULL last_trade_price 67,891 67,889 2 287 FULL market_resolved 1,319 1,319 0 37 FULL new_market 3,280 3,280 0 0 FULL price_change 104,595,212 104,588,926 6,286 2,416 FULL tick_size_change 3,188 3,188 0 100 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,116,685 7,874,022 6ms 29ms 241ms 5.9s 0 transport_latency_assumed best_bid_ask g 10,458,716 3,854 79ms 167ms 3.4s 53.2s 0 transport_latency_assumed best_bid_ask h 10,506,409 401,038 20ms 55ms 780ms 2.4min 0 transport_latency_assumed best_bid_ask i 10,345,621 337,458 22ms 48ms 366ms 1.1min 0 transport_latency_assumed best_bid_ask k 10,508,074 1,893,146 15ms 38ms 296ms 1.3min 0 transport_latency_assumed book c 1,492,819 1,452,411 2.0h 2.4d 41.5d 122.7d 0 book_staleness book g 154,695 22,505 151ms 1.5h 19.1d 122.7d 0 book_staleness book h 175,697 20,799 38ms 4.8h 20.3d 104.2d 0 book_staleness book i 144,816 9,655 27ms 1.1s 22.7h 104.1d 0 book_staleness book k 150,880 33,576 20ms 712ms 2.1d 104.2d 0 book_staleness last_trade_price c 57,296 49,176 8ms 37ms 289ms 5.9s 0 transport_latency_assumed last_trade_price g 60,072 45 98ms 4.5s 16.9s 53.3s 0 transport_latency_assumed last_trade_price h 67,524 2,478 22ms 157ms 1.4s 1.5min 0 transport_latency_assumed last_trade_price i 66,849 2,040 24ms 312ms 2.3s 21.7s 0 transport_latency_assumed last_trade_price k 67,615 14,150 16ms 55ms 343ms 13.4s 0 transport_latency_assumed market_resolved c 1,087 931 8ms 6.5min 8.6min 9.1min 0 transport_latency_assumed market_resolved g 959 4 80ms 728ms 55.0s 1.6min 0 transport_latency_assumed market_resolved h 961 182 23ms 30.2s 55.2s 1.5min 0 transport_latency_assumed market_resolved i 943 45 23ms 171ms 59.0s 2.3min 0 transport_latency_assumed market_resolved k 961 157 16ms 28.1s 52.2s 52.3s 0 transport_latency_assumed new_market c 2,042 1,482 119ms 367ms 6.1min 7.9min 0 transport_latency_assumed new_market g 1,981 239 557ms 1.7min 2.0min 2.1min 0 transport_latency_assumed new_market h 1,981 452 428ms 1.7min 2.0min 2.2min 0 transport_latency_assumed new_market i 1,981 344 329ms 1.7min 2.0min 2.2min 0 transport_latency_assumed new_market k 1,981 763 320ms 1.7min 2.0min 2.2min 0 transport_latency_assumed price_change c 89,666,484 76,876,385 7ms 32ms 290ms 6.2s 0 transport_latency_assumed price_change g 101,884,125 45,070 80ms 402ms 12.7s 56.1s 0 transport_latency_assumed price_change h 104,440,709 4,166,077 21ms 73ms 1.1s 2.4min 0 transport_latency_assumed price_change i 102,935,625 3,456,739 22ms 71ms 828ms 1.3min 0 transport_latency_assumed price_change k 104,538,017 20,044,655 15ms 43ms 344ms 1.3min 0 transport_latency_assumed tick_size_change c 2,832 2,553 6ms 15ms 97ms 421ms 0 transport_latency_assumed tick_size_change g 3,184 not meas. 78ms 110ms 579ms 1.8s 0 transport_latency_assumed tick_size_change h 3,188 62 20ms 41ms 347ms 30.5s 0 transport_latency_assumed tick_size_change i 3,136 49 22ms 41ms 132ms 339ms 0 transport_latency_assumed tick_size_change k 3,188 524 14ms 22ms 72ms 275ms 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/14/2026-09-29T14.parquet sha256sum 2026-09-29T14.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.