Hour audit: 2026-09-29T09
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-29T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T09:00:00.000084419+00:00 · last event 2026-09-29T09:59:59.999781238+00:00
VOLUME 102,834,946 rows · 1,087,358,545 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 102,601,579 · c: 102,566,668 · i: 102,486,348 · h: 102,302,241 · g: 102,062,862 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 7,676,266 (7.46%) · c: 92,623,824 (90.07%) · i: 429,520 (0.42%) · h: 2,048,142 (1.99%) · g: 57,194 (0.06%) (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 102,834,946 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6e5cfdcd85aa8c9d4ad8797f02472bc898574442aea7517df57565971c723a34
the corpus checksum ledger names this file with the same digest
joined 102,836,959 to merged 102,834,946, minus 2,013 (minus 0.0020%)
boundary drops 2,013 · 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-29T12:12:30Z 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,118,602 126,625,270 0-42 2c24d7371b96c5644143a35f7526c3f8cdbb2b69e72077680aa848782d174502 book 258,322 25,376,569 43-43 4f43b94bfa02df54ece582596a2c2427528df3361e1167ad99d36f118888fcdc last_trade_price 49,458 2,837,471 44-44 47af11b4e695dca97fe91f712bdec63dbe20d1aea58611442f53f77d04cf3906 market_resolved 586 96,103 45-45 4a3d82ce18d184c2c3c89d99b6b49273a5339964bcf9caacd4b518eb0e557dac new_market 434 50,031 46-46 9946d8f6890026bd97f969dd696e97f4a4dff5d2e605fccf067fbabb77d030da price_change 91,404,296 931,084,880 47-395 d348a51192be3eb59d13d51261d1512b7a20d25e647586cb2b2b32e3d19c6206 tick_size_change 3,248 116,865 396-396 a0482ed9f2b4eb2564e23b23fb6abbbeb07ecc9c32cffb7cb32fb22d235a211f EVENT MIX count share price_change 91,404,296 88.88% best_bid_ask 11,118,602 10.81% book 258,322 0.25% last_trade_price 49,458 0.05% tick_size_change 3,248 <0.01% market_resolved 586 <0.01% new_market 434 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,118,815 11,118,602 213 125 FULL book 258,408 258,322 86 65,616 FULL last_trade_price 49,462 49,458 4 2 FULL market_resolved 586 586 0 0 FULL new_market 434 434 0 0 FULL price_change 91,406,006 91,404,296 1,710 328 FULL tick_size_change 3,248 3,248 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,109,020 10,131,200 5ms 15ms 96ms 6.8s 0 transport_latency_assumed best_bid_ask g 11,104,116 728 78ms 98ms 334ms 20.1s 0 transport_latency_assumed best_bid_ask h 11,105,211 195,733 18ms 26ms 117ms 23.2s 0 transport_latency_assumed best_bid_ask i 11,107,011 31,167 30ms 37ms 110ms 5.5s 0 transport_latency_assumed best_bid_ask k 11,116,329 759,774 13ms 22ms 84ms 10.4s 0 transport_latency_assumed book c 130,899 117,211 9ms 6.1h 21.9d 104.0d 0 book_staleness book g 142,399 41,963 176ms 12.4h 22.0d 122.5d 0 book_staleness book h 136,780 37,248 27ms 7.5h 22.0d 104.0d 0 book_staleness book i 128,553 27,437 35ms 5.9h 21.9d 120.9d 0 book_staleness book k 128,157 34,463 19ms 4.7h 21.9d 104.0d 0 book_staleness last_trade_price c 49,269 43,601 6ms 29ms 222ms 3.9s 0 transport_latency_assumed last_trade_price g 48,132 3 86ms 1.2s 8.4s 19.0s 0 transport_latency_assumed last_trade_price h 48,324 1,184 19ms 68ms 467ms 4.6s 0 transport_latency_assumed last_trade_price i 49,104 339 32ms 88ms 401ms 5.3s 0 transport_latency_assumed last_trade_price k 49,287 4,331 15ms 46ms 274ms 5.3s 0 transport_latency_assumed market_resolved c 569 495 5ms 36ms 36.2s 40.1s 0 transport_latency_assumed market_resolved g 569 not meas. 81ms 623ms 53.2s 54.5s 0 transport_latency_assumed market_resolved h 569 5 19ms 369ms 55.1s 56.6s 0 transport_latency_assumed market_resolved i 569 66 31ms 20.1s 54.2s 54.2s 0 transport_latency_assumed market_resolved k 569 20 15ms 62ms 36.0s 39.2s 0 transport_latency_assumed new_market c 325 123 65ms 7.8s 37.6s 1.5min 0 transport_latency_assumed new_market g 325 32 226ms 9.0s 1.4min 1.6min 0 transport_latency_assumed new_market h 325 124 60ms 471ms 20.8s 1.2min 0 transport_latency_assumed new_market i 325 33 90ms 560ms 37.5s 1.7min 0 transport_latency_assumed new_market k 325 122 69ms 18.5s 37.2s 1.5min 0 transport_latency_assumed price_change c 91,273,338 82,328,172 5ms 18ms 131ms 7.0s 0 transport_latency_assumed price_change g 90,764,073 14,468 78ms 132ms 3.0s 20.1s 0 transport_latency_assumed price_change h 91,007,784 1,813,810 18ms 33ms 229ms 24.0s 0 transport_latency_assumed price_change i 91,197,538 370,470 30ms 45ms 216ms 5.8s 0 transport_latency_assumed price_change k 91,303,664 6,877,376 13ms 26ms 126ms 10.6s 0 transport_latency_assumed tick_size_change c 3,248 3,022 5ms 12ms 65ms 246ms 0 transport_latency_assumed tick_size_change g 3,248 not meas. 78ms 94ms 180ms 3.0s 0 transport_latency_assumed tick_size_change h 3,248 38 18ms 28ms 73ms 123ms 0 transport_latency_assumed tick_size_change i 3,248 8 30ms 41ms 89ms 220ms 0 transport_latency_assumed tick_size_change k 3,248 180 13ms 20ms 61ms 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-29/09/2026-09-29T09.parquet sha256sum 2026-09-29T09.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.