Hour audit: 2026-09-29T05
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-29T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-29T05:00:00.000196989+00:00 · last event 2026-09-29T05:59:59.999544616+00:00
VOLUME 93,425,074 rows · 972,223,662 bytes (927.18 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 93,291,081 · k: 93,232,327 · g: 93,149,945 · i: 91,679,207 · c: 90,208,132 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 1,551,799 (1.66%) · k: 6,899,532 (7.39%) · g: 45,567 (0.05%) · i: 695,532 (0.74%) · c: 84,232,644 (90.16%) (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 93,425,074 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 172db8a95d099fa09e3c253bc4161ed555c0ec920bf58e4441798f43c7f2912c
the corpus checksum ledger names this file with the same digest
joined 93,427,402 to merged 93,425,074, minus 2,328 (minus 0.0025%)
boundary drops 2,328 · 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-29T08:06:54Z 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,192,500 113,980,621 0-38 e4b27e15bc82cbefc9b551f32e47bc9f364615064d0243f570eaae0aabad8adb book 197,249 20,052,656 39-39 bed485d4fd348142b7c5bfe1eaed1f7de1d5af16baf28b0708b0e36ee18f4770 last_trade_price 47,332 2,694,124 40-40 63cccf5f9c3292b127aefda16204746d05972ba13178e805fe469cd7d6f93732 market_resolved 1,869 287,295 41-41 27251b8c9860ae909b6fb7610e4361e0968a8782308c9b5f57b0752451904718 new_market 830 88,171 42-42 0a29e28d6e3005dc601d5698492c7a0794724c2ff3ab2d7b5298d1deabffa9b2 price_change 82,980,834 833,895,027 43-359 66cb81c48a7751e47fb0e7ef7c08a6d13be04aaf81f9f537d5e64fbaa2d134a6 tick_size_change 4,460 160,265 360-360 f1c442194a4ec234682660d89d84c546f211ce9971398407fc65f680e0ffe6da EVENT MIX count share price_change 82,980,834 88.82% best_bid_ask 10,192,500 10.91% book 197,249 0.21% last_trade_price 47,332 0.05% tick_size_change 4,460 <0.01% market_resolved 1,869 <0.01% new_market 830 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,192,708 10,192,500 208 2,567 FULL book 197,333 197,249 84 44,064 FULL last_trade_price 47,334 47,332 2 135 FULL market_resolved 1,869 1,869 0 50 FULL new_market 830 830 0 0 FULL price_change 82,982,868 82,980,834 2,034 4,739 FULL tick_size_change 4,460 4,460 0 48 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,917,908 9,333,223 5ms 10ms 74ms 3.8s 0 transport_latency_assumed best_bid_ask g 10,189,238 801 77ms 95ms 301ms 19.2s 0 transport_latency_assumed best_bid_ask h 10,191,079 137,797 18ms 24ms 114ms 1.6min 0 transport_latency_assumed best_bid_ask i 10,023,994 60,074 21ms 27ms 96ms 5.3s 0 transport_latency_assumed best_bid_ask k 10,190,786 660,605 12ms 20ms 87ms 24.3s 0 transport_latency_assumed book c 124,639 115,520 7ms 6.5h 21.8d 122.3d 0 book_staleness book g 131,781 35,383 93ms 6.9h 21.8d 122.3d 0 book_staleness book h 113,487 18,250 22ms 1.1h 16.6d 103.8d 0 book_staleness book i 98,052 4,075 23ms 71ms 10.9h 103.6d 0 book_staleness book k 114,575 24,021 16ms 1.1h 16.6d 120.7d 0 book_staleness last_trade_price c 46,255 42,630 6ms 16ms 134ms 1.3s 0 transport_latency_assumed last_trade_price g 46,957 5 80ms 274ms 4.4s 19.3s 0 transport_latency_assumed last_trade_price h 47,154 797 19ms 42ms 293ms 12.1s 0 transport_latency_assumed last_trade_price i 46,792 439 23ms 46ms 233ms 3.7s 0 transport_latency_assumed last_trade_price k 47,141 3,461 14ms 33ms 211ms 7.7s 0 transport_latency_assumed market_resolved c 1,765 1,630 5ms 13ms 53.7s 2.3min 0 transport_latency_assumed market_resolved g 1,794 29 79ms 215ms 33.0s 53.2s 0 transport_latency_assumed market_resolved h 1,794 18 20ms 57ms 47.4s 52.4s 0 transport_latency_assumed market_resolved i 1,772 97 23ms 70ms 50.5s 2.4min 0 transport_latency_assumed market_resolved k 1,794 95 15ms 33ms 50.6s 53.9s 0 transport_latency_assumed new_market c 565 275 84ms 14.4s 33.6s 1.4min 0 transport_latency_assumed new_market g 565 47 264ms 14.4s 30.9s 1.7min 0 transport_latency_assumed new_market h 565 197 116ms 16.2s 31.1s 1.6min 0 transport_latency_assumed new_market i 565 161 99ms 12.6s 36.4s 1.3min 0 transport_latency_assumed new_market k 565 150 103ms 12.7s 23.2s 30.8s 0 transport_latency_assumed price_change c 80,112,664 74,735,326 5ms 12ms 89ms 18.4s 0 transport_latency_assumed price_change g 82,775,150 9,302 78ms 114ms 873ms 19.4s 0 transport_latency_assumed price_change h 82,932,542 1,394,632 18ms 29ms 161ms 1.6min 0 transport_latency_assumed price_change i 81,503,644 630,638 22ms 32ms 147ms 8.7s 0 transport_latency_assumed price_change k 82,873,006 6,210,936 13ms 23ms 112ms 28.4s 0 transport_latency_assumed tick_size_change c 4,336 4,040 5ms 12ms 77ms 240ms 0 transport_latency_assumed tick_size_change g 4,460 not meas. 78ms 140ms 444ms 4.4s 0 transport_latency_assumed tick_size_change h 4,460 108 18ms 31ms 132ms 2.0s 0 transport_latency_assumed tick_size_change i 4,388 48 22ms 37ms 276ms 1.0s 0 transport_latency_assumed tick_size_change k 4,460 264 13ms 26ms 145ms 433ms 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/05/2026-09-29T05.parquet sha256sum 2026-09-29T05.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.