Hour audit: 2026-09-29T02
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-29T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T02:00:00.001220481+00:00 · last event 2026-09-29T02:59:59.999939951+00:00
VOLUME 104,740,025 rows · 1,135,853,727 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 104,510,256 · h: 104,494,230 · c: 104,468,609 · i: 104,465,112 · g: 102,934,400 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 9,010,673 (8.60%) · h: 5,121,036 (4.89%) · c: 87,549,025 (83.59%) · i: 2,914,665 (2.78%) · g: 144,626 (0.14%) (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 104,740,025 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f17be9b25ab71fd9238e6326be3e77d1e0fa791fe5d9244ac0c50ffde3f1cdb9
the corpus checksum ledger names this file with the same digest
joined 104,741,737 to merged 104,740,025, minus 1,712 (minus 0.0016%)
boundary drops 1,712 · 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-29T05:12:08Z 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,841,676 128,836,218 0-41 fdad8927f3702d58e5a08a36a43e7e4589bb5ac28e495ae4189333e6c4dac5f6 book 285,370 26,390,630 42-43 7b97ff91af16c3222d180c0729033290112618d2a6df5ad9f0b3d0b45e1ff3c1 last_trade_price 44,790 2,631,383 44-44 a3cc10d13d0deba4bc8ae379dcf93597c595ed78b3f9a970c09f80fcb824d51b market_resolved 513 83,367 45-45 d030055faab1ff4f74f34f5ffe5460f4eef5e973e72bcd1e1c78bcd6e93179d7 new_market 8,226 948,437 46-46 26b0e9a6c4ab9e2c68a344adf05ebd8ff2b42d4278a8cf40106dae1edccbdfdb price_change 93,556,034 975,642,160 47-403 a8e4c517584b4902c061e294a4043003a8b875406550113f7ccb0cee50e3e4d5 tick_size_change 3,416 126,756 404-404 0d7ffe171a2f41fd3544fa6ff0e2a8bc10cd3214636595cb7acd9638285dbc39 EVENT MIX count share price_change 93,556,034 89.32% best_bid_ask 10,841,676 10.35% book 285,370 0.27% last_trade_price 44,790 0.04% new_market 8,226 <0.01% tick_size_change 3,416 <0.01% market_resolved 513 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,841,879 10,841,676 203 268 FULL book 285,386 285,370 16 66,214 FULL last_trade_price 44,791 44,790 1 1 FULL market_resolved 513 513 0 0 FULL new_market 8,226 8,226 0 0 FULL price_change 93,557,526 93,556,034 1,492 228 FULL tick_size_change 3,416 3,416 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,838,982 9,199,127 5ms 45ms 390ms 10.9s 0 transport_latency_assumed best_bid_ask g 10,809,039 10,510 81ms 238ms 1.5s 47.8s 0 transport_latency_assumed best_bid_ask h 10,836,832 505,395 18ms 56ms 1.3s 1.5min 0 transport_latency_assumed best_bid_ask i 10,838,598 297,592 22ms 52ms 381ms 49.5s 0 transport_latency_assumed best_bid_ask k 10,838,254 829,052 13ms 57ms 506ms 2.1min 0 transport_latency_assumed book c 136,613 108,391 15ms 5.9h 21.7d 103.7d 0 book_staleness book g 128,063 32,932 305ms 5.9h 21.7d 103.6d 0 book_staleness book h 180,778 81,577 799ms 16.0h 29.4d 122.2d 0 book_staleness book i 108,652 10,038 32ms 3.1s 1.3d 103.7d 0 book_staleness book k 146,186 52,432 39ms 10.5h 23.5d 122.2d 0 book_staleness last_trade_price c 44,626 36,588 6ms 75ms 503ms 4.4s 0 transport_latency_assumed last_trade_price g 41,331 81 101ms 2.2s 20.3s 48.1s 0 transport_latency_assumed last_trade_price h 44,548 2,047 20ms 134ms 1.5s 43.0s 0 transport_latency_assumed last_trade_price i 44,654 1,258 25ms 155ms 848ms 8.1s 0 transport_latency_assumed last_trade_price k 44,689 4,816 15ms 93ms 585ms 2.0min 0 transport_latency_assumed market_resolved c 506 399 5ms 199ms 49.1s 50.3s 0 transport_latency_assumed market_resolved g 506 6 97ms 554ms 56.8s 57.5s 0 transport_latency_assumed market_resolved h 506 35 23ms 335ms 47.6s 49.4s 0 transport_latency_assumed market_resolved i 506 47 31ms 227ms 36.7s 38.4s 0 transport_latency_assumed market_resolved k 506 26 21ms 286ms 54.1s 56.3s 0 transport_latency_assumed new_market c 6,244 2,256 134ms 28.4s 1.5min 3.5min 0 transport_latency_assumed new_market g 6,244 513 277ms 35.6s 1.8min 13.3min 0 transport_latency_assumed new_market h 6,244 2,227 145ms 23.5s 1.7min 3.5min 0 transport_latency_assumed new_market i 6,244 1,716 141ms 29.0s 1.9min 3.4min 0 transport_latency_assumed new_market k 6,244 1,514 193ms 17.2s 1.8min 3.3min 0 transport_latency_assumed price_change c 93,438,222 78,199,246 5ms 52ms 414ms 10.9s 0 transport_latency_assumed price_change g 91,945,801 100,584 83ms 373ms 10.6s 48.4s 0 transport_latency_assumed price_change h 93,421,906 4,529,638 19ms 72ms 1.4s 1.8min 0 transport_latency_assumed price_change i 93,463,042 2,603,962 22ms 68ms 481ms 49.8s 0 transport_latency_assumed price_change k 93,470,961 8,122,604 14ms 64ms 519ms 2.1min 0 transport_latency_assumed tick_size_change c 3,416 3,018 5ms 26ms 332ms 619ms 0 transport_latency_assumed tick_size_change g 3,416 not meas. 82ms 225ms 993ms 5.8s 0 transport_latency_assumed tick_size_change h 3,416 117 19ms 46ms 942ms 4.4s 0 transport_latency_assumed tick_size_change i 3,416 52 23ms 59ms 273ms 575ms 0 transport_latency_assumed tick_size_change k 3,416 229 14ms 35ms 522ms 3.4s 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/02/2026-09-29T02.parquet sha256sum 2026-09-29T02.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.