Hour audit: 2026-09-29T17
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-29T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T17:00:00.000006197+00:00 · last event 2026-09-29T17:59:59.999741531+00:00
VOLUME 115,047,978 rows · 1,321,961,808 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 113,516,832 · h: 112,998,822 · i: 112,861,281 · g: 110,844,632 · c: 99,451,689 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 22,782,236 (19.80%) · h: 3,215,209 (2.79%) · i: 2,594,285 (2.25%) · g: 54,977 (0.05%) · c: 86,401,271 (75.10%) (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 115,047,978 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ba51bfbc400b6980b45c9f7e83a66225ba36033b97cf2aa06a8583137246cfc2
the corpus checksum ledger names this file with the same digest
joined 115,050,307 to merged 115,047,978, minus 2,329 (minus 0.0020%)
boundary drops 2,329 · 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-29T20:11:58Z 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,907,823 135,700,018 0-41 d1f921e2e445d0b8465df8295ed58ac9e3c913e4764917db572e2ead3cb6615d book 1,604,036 82,955,422 42-48 7c6ee7bc61f8ec64ac62137330f51fb1ba5d40c66d8f00f0e092a9d870f61979 last_trade_price 70,165 4,020,265 49-49 7fb6084fcf59ce8e162b0b70b27f1db3e773c6f8e68f7d84e3abc11f2bffdee0 market_resolved 2,325 214,758 50-50 f238463a205dc482a4186622cf9c4c7e9fd6a944259bdf5c1446d0db8ffef737 new_market 1,889 170,715 51-51 6695ae3d0f35106094e69162a38ce3949092d2a0381de241d84e430dfb54a9ea price_change 102,458,128 1,097,456,126 52-442 83d52d2c8275ea27ae7c6b527a38515135f997ad7da388c46979c6e15fb80288 tick_size_change 3,612 133,186 443-443 20ced9ca81ec173367caa4e9fbc2831bc5cbf24e2e6352e7b15cb0bab5ba6878 EVENT MIX count share price_change 102,458,128 89.06% best_bid_ask 10,907,823 9.48% book 1,604,036 1.39% last_trade_price 70,165 0.06% tick_size_change 3,612 <0.01% market_resolved 2,325 <0.01% new_market 1,889 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,908,073 10,907,823 250 1,307 FULL book 1,604,088 1,604,036 52 228,810 FULL last_trade_price 70,166 70,165 1 269 FULL market_resolved 2,325 2,325 0 43 FULL new_market 1,919 1,889 30 95 FULL price_change 102,460,124 102,458,128 1,996 1,245 FULL tick_size_change 3,612 3,612 0 126 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,446,867 8,200,771 6ms 27ms 253ms 23.0s 0 transport_latency_assumed best_bid_ask g 10,831,514 2,415 79ms 149ms 1.8s 36.4s 0 transport_latency_assumed best_bid_ask h 10,883,760 316,450 21ms 60ms 670ms 1.7min 0 transport_latency_assumed best_bid_ask i 10,880,008 248,991 21ms 44ms 390ms 56.9s 0 transport_latency_assumed best_bid_ask k 10,905,743 2,139,196 13ms 31ms 215ms 57.7s 0 transport_latency_assumed book c 1,546,058 1,520,466 1.4h 2.5d 38.2d 122.8d 0 book_staleness book g 153,201 19,544 108ms 14.0min 13.8d 104.3d 0 book_staleness book h 190,155 22,944 45ms 5.5h 22.3d 122.8d 0 book_staleness book i 157,982 12,505 26ms 9.8s 1.3d 122.8d 0 book_staleness book k 152,591 28,577 18ms 190ms 1.8d 104.3d 0 book_staleness last_trade_price c 61,823 53,961 7ms 33ms 266ms 4.7s 0 transport_latency_assumed last_trade_price g 63,665 48 95ms 2.5s 16.5s 36.3s 0 transport_latency_assumed last_trade_price h 69,065 1,671 24ms 193ms 1.4s 59.3s 0 transport_latency_assumed last_trade_price i 68,827 1,353 23ms 236ms 1.8s 10.2s 0 transport_latency_assumed last_trade_price k 69,855 13,132 15ms 52ms 295ms 3.9s 0 transport_latency_assumed market_resolved c 2,112 1,922 51.4s 13.3min 27.3min 30.9min 0 transport_latency_assumed market_resolved g 1,221 1 83ms 3.5s 43.9s 54.3s 0 transport_latency_assumed market_resolved h 1,224 17 24ms 903ms 41.5s 52.4s 0 transport_latency_assumed market_resolved i 1,224 22 22ms 306ms 38.5s 47.4s 0 transport_latency_assumed market_resolved k 1,224 363 15ms 344ms 37.5s 47.6s 0 transport_latency_assumed new_market c 1,338 807 357ms 14.3min 26.9min 26.9min 0 transport_latency_assumed new_market g 983 119 354ms 25.1s 1.8min 2.7min 0 transport_latency_assumed new_market h 983 159 225ms 27.8s 1.9min 2.4min 0 transport_latency_assumed new_market i 979 381 123ms 26.8s 2.2min 2.7min 0 transport_latency_assumed new_market k 983 423 132ms 26.4s 1.5min 2.3min 0 transport_latency_assumed price_change c 88,390,367 76,620,578 6ms 29ms 256ms 29.1s 0 transport_latency_assumed price_change g 99,790,452 32,850 80ms 292ms 10.2s 36.4s 0 transport_latency_assumed price_change h 101,850,023 2,873,878 22ms 86ms 887ms 1.7min 0 transport_latency_assumed price_change i 101,748,649 2,330,986 21ms 67ms 1.2s 57.1s 0 transport_latency_assumed price_change k 102,382,824 20,599,836 14ms 36ms 232ms 59.6s 0 transport_latency_assumed tick_size_change c 3,124 2,766 6ms 16ms 102ms 353ms 0 transport_latency_assumed tick_size_change g 3,596 not meas. 79ms 116ms 654ms 8.2s 0 transport_latency_assumed tick_size_change h 3,612 90 22ms 43ms 282ms 8.9s 0 transport_latency_assumed tick_size_change i 3,612 47 21ms 45ms 149ms 1.2s 0 transport_latency_assumed tick_size_change k 3,612 709 13ms 24ms 139ms 1.0s 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/17/2026-09-29T17.parquet sha256sum 2026-09-29T17.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.