Hour audit: 2026-09-29T11
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-29T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T11:00:00.000375287+00:00 · last event 2026-09-29T11:59:59.999968833+00:00
VOLUME 105,734,326 rows · 1,193,339,132 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 105,271,837 · c: 105,267,083 · h: 105,259,505 · i: 104,884,117 · g: 104,700,189 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 7,228,088 (6.84%) · c: 87,230,056 (82.50%) · h: 2,131,852 (2.02%) · i: 9,067,496 (8.58%) · g: 76,834 (0.07%) (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 105,734,326 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4d7bc3c3964ff4e03f5f98c3e57538a384a2321c7a7b036edc11819df7203182
the corpus checksum ledger names this file with the same digest
joined 105,736,248 to merged 105,734,326, minus 1,922 (minus 0.0018%)
boundary drops 1,922 · 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-29T13:52: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,593,992 127,571,721 0-40 097cba719ffe2996ee7002f51fd7de325c91fbd290f912d4ec880cd0de0aeb9f book 507,492 48,625,681 41-42 7abc14ad685349be163f63d3ee174f78d876f663f22d00475e32ac6fe74248c6 last_trade_price 55,692 3,185,168 43-43 3625a90e680ffa35365201b5dcf1efee3cde3561c688c6abae133e3ca04c74ce market_resolved 861 134,457 44-44 7edb87947b80e27759406a582834372eaf1df3bbb220217e5466b2a938a156d5 new_market 1,047 112,113 45-45 75ead3e6d3d2858f996bb0d2d394c4675c55db3f532286896b10fd6c83ce69b6 price_change 94,571,854 1,012,381,139 46-406 2a79ddcfedae1362c8854c741470df983239ee03874409702d7babe597115251 tick_size_change 3,388 124,389 407-407 8c8939a7a621baa53d8b2fc7f1f9cc09aeedf44da8ec8f11ae3c51bceda26b06 EVENT MIX count share price_change 94,571,854 89.44% best_bid_ask 10,593,992 10.02% book 507,492 0.48% last_trade_price 55,692 0.05% tick_size_change 3,388 <0.01% new_market 1,047 <0.01% market_resolved 861 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,594,172 10,593,992 180 95 FULL book 507,502 507,492 10 165,711 FULL last_trade_price 55,692 55,692 0 3 FULL market_resolved 861 861 0 0 FULL new_market 1,047 1,047 0 0 FULL price_change 94,573,586 94,571,854 1,732 330 FULL tick_size_change 3,388 3,388 0 9 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,592,373 8,849,415 5ms 21ms 212ms 13.1s 0 transport_latency_assumed best_bid_ask g 10,581,040 1,582 78ms 114ms 558ms 32.5s 0 transport_latency_assumed best_bid_ask h 10,591,886 175,877 18ms 30ms 220ms 51.1s 0 transport_latency_assumed best_bid_ask i 10,559,294 911,651 18ms 31ms 245ms 21.6s 0 transport_latency_assumed best_bid_ask k 10,592,254 655,467 13ms 26ms 193ms 54.3s 0 transport_latency_assumed book c 129,587 104,414 8ms 3.4min 6.7d 104.1d 0 book_staleness book g 181,430 56,363 444ms 19.6h 29.8d 122.6d 0 book_staleness book h 150,972 32,654 26ms 7.8h 22.0d 122.6d 0 book_staleness book i 417,395 280,341 11.2min 2.1d 37.9d 122.6d 0 book_staleness book k 145,489 33,720 20ms 5.9h 22.0d 104.1d 0 book_staleness last_trade_price c 55,366 45,893 7ms 33ms 325ms 5.2s 0 transport_latency_assumed last_trade_price g 54,004 18 89ms 1.4s 11.6s 32.5s 0 transport_latency_assumed last_trade_price h 55,328 1,480 19ms 60ms 411ms 24.1s 0 transport_latency_assumed last_trade_price i 54,313 3,481 20ms 168ms 1.3s 10.9s 0 transport_latency_assumed last_trade_price k 55,513 4,820 14ms 43ms 283ms 9.4s 0 transport_latency_assumed market_resolved c 828 652 6ms 20.0s 55.9s 58.3s 0 transport_latency_assumed market_resolved g 828 not meas. 82ms 19.8s 56.2s 56.3s 0 transport_latency_assumed market_resolved h 828 6 19ms 13.7s 50.1s 54.9s 0 transport_latency_assumed market_resolved i 828 151 20ms 10.3s 46.1s 51.6s 0 transport_latency_assumed market_resolved k 828 52 14ms 308ms 55.3s 55.5s 0 transport_latency_assumed new_market c 709 252 148ms 17.9s 30.7s 1.8min 0 transport_latency_assumed new_market g 709 75 364ms 20.7s 29.7s 1.7min 0 transport_latency_assumed new_market h 709 202 180ms 25.2s 1.0min 1.4min 0 transport_latency_assumed new_market i 709 269 134ms 22.8s 1.0min 1.6min 0 transport_latency_assumed new_market k 709 249 130ms 14.4s 55.6s 1.8min 0 transport_latency_assumed price_change c 94,484,836 78,226,762 6ms 25ms 230ms 13.1s 0 transport_latency_assumed price_change g 93,878,790 18,796 78ms 181ms 3.8s 32.7s 0 transport_latency_assumed price_change h 94,456,398 1,921,538 18ms 36ms 274ms 51.8s 0 transport_latency_assumed price_change i 93,848,218 7,871,288 18ms 45ms 533ms 21.9s 0 transport_latency_assumed price_change k 94,473,656 6,533,470 13ms 30ms 215ms 54.5s 0 transport_latency_assumed tick_size_change c 3,384 2,668 6ms 37ms 240ms 4.6s 0 transport_latency_assumed tick_size_change g 3,388 not meas. 78ms 134ms 802ms 9.5s 0 transport_latency_assumed tick_size_change h 3,384 95 19ms 51ms 306ms 4.3s 0 transport_latency_assumed tick_size_change i 3,360 315 19ms 47ms 266ms 889ms 0 transport_latency_assumed tick_size_change k 3,388 310 13ms 33ms 464ms 562ms 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/11/2026-09-29T11.parquet sha256sum 2026-09-29T11.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.