Hour audit: 2026-09-29T04
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-29T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T04:00:00.000011434+00:00 · last event 2026-09-29T04:59:59.999444961+00:00
VOLUME 94,102,500 rows · 1,000,056,307 bytes (953.73 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 93,926,742 · k: 93,864,176 · i: 93,744,205 · c: 93,710,044 · g: 93,568,246 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,830,453 (1.95%) · k: 4,079,530 (4.34%) · i: 4,760,059 (5.06%) · c: 83,340,744 (88.56%) · g: 91,714 (0.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 94,102,500 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 78004d8c06ba9d3e202fcf9db69e02b5a40d95d5c026f5ed5adcbaa9e9a3c023
the corpus checksum ledger names this file with the same digest
joined 94,104,184 to merged 94,102,500, minus 1,684 (minus 0.0018%)
boundary drops 1,684 · 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-29T07:07:51Z 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,316,974 117,926,241 0-39 b0907b0bdd0247705856c254816a3db8570027f403d5d4a25e600605a5b789b4 book 288,338 26,968,965 40-41 51440fd8300133bc37d9d03d30934ef5a83a51ff3ccd40ae079c13b0666399ca last_trade_price 41,215 2,452,969 42-42 f151b527f62f47132bbff66a516f07baaf7d07a0007686b1ae6e182fff3c3f55 market_resolved 652 107,867 43-43 70ade395a82fe92fcf5c16a3d44fc71002a3dedb0a8c00ad42c9362abe706c4d new_market 3,375 332,709 44-44 a10a9f4f6d22b6f9a0467221348676ea08f0e5c5cc1c780b90d3943ad02d2dc5 price_change 83,449,390 851,096,615 45-363 af4e97afcf72fcbb3bd944a0800cee07717ce5189583bf73c64e2d44bd1d7aa8 tick_size_change 2,556 93,435 364-364 6cc2e199a61d057b8e713c90357aa8b152245b321e7c36f992cf5969483f25d6 EVENT MIX count share price_change 83,449,390 88.68% best_bid_ask 10,316,974 10.96% book 288,338 0.31% last_trade_price 41,215 0.04% new_market 3,375 <0.01% tick_size_change 2,556 <0.01% market_resolved 652 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,317,176 10,316,974 202 138 FULL book 288,394 288,338 56 79,744 FULL last_trade_price 41,215 41,215 0 8 FULL market_resolved 652 652 0 2 FULL new_market 3,375 3,375 0 0 FULL price_change 83,450,816 83,449,390 1,426 316 FULL tick_size_change 2,556 2,556 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,298,519 9,282,605 5ms 13ms 349ms 30.7s 0 transport_latency_assumed best_bid_ask g 10,310,712 5,967 78ms 114ms 798ms 28.9s 0 transport_latency_assumed best_bid_ask h 10,312,644 161,079 18ms 27ms 702ms 1.6min 0 transport_latency_assumed best_bid_ask i 10,305,842 478,272 18ms 25ms 309ms 51.8s 0 transport_latency_assumed best_bid_ask k 10,315,162 389,051 13ms 23ms 429ms 44.8s 0 transport_latency_assumed book c 113,860 95,680 8ms 5.1h 21.7d 122.3d 0 book_staleness book g 110,938 24,464 97ms 4.9h 20.4d 122.3d 0 book_staleness book h 200,898 110,786 43.2s 1.2d 37.6d 122.3d 0 book_staleness book i 95,031 13,081 21ms 3.4s 2.0d 103.8d 0 book_staleness book k 130,933 44,327 25ms 13.3h 23.6d 122.3d 0 book_staleness last_trade_price c 41,043 35,622 6ms 29ms 540ms 7.8s 0 transport_latency_assumed last_trade_price g 40,515 73 84ms 437ms 9.7s 28.7s 0 transport_latency_assumed last_trade_price h 41,047 916 19ms 47ms 869ms 42.7s 0 transport_latency_assumed last_trade_price i 41,166 2,261 19ms 53ms 651ms 7.8s 0 transport_latency_assumed last_trade_price k 41,128 2,343 14ms 38ms 588ms 27.4s 0 transport_latency_assumed market_resolved c 651 538 5ms 131ms 39.8s 40.8s 0 transport_latency_assumed market_resolved g 652 1 83ms 448ms 55.4s 56.9s 0 transport_latency_assumed market_resolved h 652 11 19ms 122ms 40.4s 52.9s 0 transport_latency_assumed market_resolved i 651 68 20ms 113ms 31.8s 33.1s 0 transport_latency_assumed market_resolved k 652 34 15ms 123ms 45.2s 46.1s 0 transport_latency_assumed new_market c 2,101 879 176ms 18.5s 2.2min 3.1min 0 transport_latency_assumed new_market g 2,101 329 410ms 21.9s 2.1min 3.1min 0 transport_latency_assumed new_market h 2,101 749 230ms 43.7s 2.2min 3.1min 0 transport_latency_assumed new_market i 2,101 714 190ms 22.0s 2.1min 3.1min 0 transport_latency_assumed new_market k 2,101 704 229ms 20.7s 2.2min 3.2min 0 transport_latency_assumed price_change c 83,251,318 73,923,420 5ms 18ms 406ms 32.8s 0 transport_latency_assumed price_change g 83,100,772 60,880 78ms 169ms 3.0s 28.9s 0 transport_latency_assumed price_change h 83,366,844 1,556,824 18ms 34ms 783ms 1.6min 0 transport_latency_assumed price_change i 83,296,862 4,265,416 18ms 32ms 420ms 51.9s 0 transport_latency_assumed price_change k 83,371,644 3,642,850 13ms 28ms 468ms 44.9s 0 transport_latency_assumed tick_size_change c 2,552 2,000 6ms 50ms 358ms 2.1s 0 transport_latency_assumed tick_size_change g 2,556 not meas. 81ms 219ms 674ms 1.4s 0 transport_latency_assumed tick_size_change h 2,556 88 18ms 60ms 561ms 6.0s 0 transport_latency_assumed tick_size_change i 2,552 247 19ms 54ms 293ms 5.6s 0 transport_latency_assumed tick_size_change k 2,556 221 14ms 53ms 320ms 5.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/04/2026-09-29T04.parquet sha256sum 2026-09-29T04.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.