Hour audit: 2026-09-30T23
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-30T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T23:00:00.000001971+00:00 · last event 2026-09-30T23:59:59.999958235+00:00
VOLUME 106,021,863 rows · 1,154,253,612 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 105,439,719 · h: 105,434,640 · m: 105,392,553 · i: 105,299,497 · g: 105,250,530 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 10,927,868 (10.31%) · h: 3,263,802 (3.08%) · m: 89,217,592 (84.15%) · i: 2,384,887 (2.25%) · g: 227,714 (0.21%) (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 106,021,863 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2a8c45e82d6cab9e4df2a0e055911ac378dbf0a572c204b642d90409a8f0ff40
the corpus checksum ledger names this file with the same digest
joined 106,028,386 to merged 106,021,863, minus 6,523 (minus 0.0062%)
boundary drops 6,523 · 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-10-01T02:07:38Z as ghikm
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,004,359 117,602,382 0-38 7aa7ca0a5b7b0759828c20ca07e6d1458d9060580f542d4bf9cf5a930fd1e1dd book 974,067 74,785,209 39-42 1edf0f6d6c8615a4ed1070a9e614de4591277af9490dbe84df25bb73e7c59029 last_trade_price 51,734 2,954,532 43-43 c40ee202b9908c90b6ae025406107f61752c3a8b0e78f32963c2cbdddb03bc8d market_resolved 806 124,178 44-44 1b10174ace7c59810f74c5e4ce11101d8dd0ed6d0021bca03d972573c9c9ce9d new_market 1,193 113,295 45-45 488ffa4927915086878ba0bb9d52840991e7cbf473df70cc33fd924aa5bfa3fc price_change 94,987,800 957,391,183 46-408 d9935615fe3cd026d8bd5cbca3a2e675b342986d22f17cbbcd3d80352e0356c3 tick_size_change 1,904 71,101 409-409 173330ce3a2910931e48bb0fcf5872e8a506a671726faf0c3ffcfd3d3f0774fc EVENT MIX count share price_change 94,987,800 89.59% best_bid_ask 10,004,359 9.44% book 974,067 0.92% last_trade_price 51,734 0.05% tick_size_change 1,904 <0.01% new_market 1,193 <0.01% market_resolved 806 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,004,616 10,004,359 257 122 FULL book 975,351 974,067 1,284 216,193 FULL last_trade_price 51,736 51,734 2 2 FULL market_resolved 806 806 0 0 FULL new_market 1,193 1,193 0 0 FULL price_change 94,992,780 94,987,800 4,980 118 FULL tick_size_change 1,904 1,904 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,997,808 3,450 80ms 102ms 464ms 30.7s 0 transport_latency_assumed best_bid_ask h 10,001,624 217,598 19ms 41ms 308ms 54.8s 0 transport_latency_assumed best_bid_ask i 10,002,856 212,129 20ms 50ms 202ms 9.5s 0 transport_latency_assumed best_bid_ask k 10,001,980 846,043 13ms 32ms 197ms 56.7s 0 transport_latency_assumed best_bid_ask m 10,003,229 8,725,139 4ms 19ms 161ms 6.1s 0 transport_latency_assumed book g 407,992 185,595 11.8min 2.3d 39.4d 124.1d 0 book_staleness book h 445,562 215,865 14.3min 2.4d 39.4d 124.1d 0 book_staleness book i 297,320 108,024 2.1min 1.9d 39.4d 124.1d 0 book_staleness book k 447,112 234,311 14.6min 2.4d 39.4d 124.1d 0 book_staleness book m 367,452 230,272 7.7min 2.3d 39.4d 124.1d 0 book_staleness last_trade_price g 50,474 37 91ms 484ms 7.2s 30.5s 0 transport_latency_assumed last_trade_price h 51,680 3,183 19ms 85ms 765ms 45.8s 0 transport_latency_assumed last_trade_price i 51,697 1,341 24ms 117ms 769ms 4.6s 0 transport_latency_assumed last_trade_price k 51,701 9,499 15ms 63ms 381ms 35.6s 0 transport_latency_assumed last_trade_price m 51,688 37,674 7ms 57ms 399ms 1.6s 0 transport_latency_assumed market_resolved g 762 not meas. 83ms 237ms 49.7s 57.1s 0 transport_latency_assumed market_resolved h 762 22 21ms 75ms 49.7s 56.4s 0 transport_latency_assumed market_resolved i 762 24 24ms 97ms 54.8s 54.8s 0 transport_latency_assumed market_resolved k 762 132 16ms 44ms 48.8s 48.8s 0 transport_latency_assumed market_resolved m 762 628 6ms 174ms 52.5s 52.5s 0 transport_latency_assumed new_market g 714 118 218ms 15.9s 36.6s 1.7min 0 transport_latency_assumed new_market h 714 214 196ms 15.7s 44.2s 1.9min 0 transport_latency_assumed new_market i 714 158 148ms 14.4s 38.2s 1.7min 0 transport_latency_assumed new_market k 714 186 197ms 13.5s 25.3s 1.7min 0 transport_latency_assumed new_market m 714 517 68ms 15.1s 43.2s 1.6min 0 transport_latency_assumed price_change g 94,790,876 38,514 81ms 119ms 1.2s 31.0s 0 transport_latency_assumed price_change h 94,932,394 2,826,870 19ms 44ms 391ms 58.8s 0 transport_latency_assumed price_change i 94,944,244 2,063,184 20ms 55ms 300ms 9.5s 0 transport_latency_assumed price_change k 94,935,546 9,837,526 14ms 36ms 216ms 56.7s 0 transport_latency_assumed price_change m 94,966,804 80,221,706 5ms 24ms 187ms 8.2s 0 transport_latency_assumed tick_size_change g 1,904 not meas. 80ms 97ms 446ms 1.1s 0 transport_latency_assumed tick_size_change h 1,904 50 19ms 40ms 195ms 540ms 0 transport_latency_assumed tick_size_change i 1,904 27 19ms 48ms 139ms 1.5s 0 transport_latency_assumed tick_size_change k 1,904 171 13ms 30ms 183ms 952ms 0 transport_latency_assumed tick_size_change m 1,904 1,656 5ms 18ms 56ms 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-30/23/2026-09-30T23.parquet sha256sum 2026-09-30T23.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.