Hour audit: 2026-09-30T07
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-30T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T07:00:00.003122492+00:00 · last event 2026-09-30T07:59:59.999829876+00:00
VOLUME 103,289,056 rows · 1,101,230,138 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 102,877,506 · i: 102,848,184 · m: 102,794,757 · h: 102,736,842 · g: 102,637,373 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 3,965,663 (3.84%) · i: 665,657 (0.64%) · m: 97,403,692 (94.30%) · h: 1,143,623 (1.11%) · g: 110,421 (0.11%) (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 103,289,056 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1e553ec766ebbd92382d6195651c7b6d84a323ea62f67bca29af05bc8400dbbc
the corpus checksum ledger names this file with the same digest
joined 103,290,936 to merged 103,289,056, minus 1,880 (minus 0.0018%)
boundary drops 1,880 · 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-30T16:50:18Z 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 9,805,945 114,190,566 0-37 673f0a215f7906a1b5926d9a907486952c20154d5030a1baaf369e6046ca82b5 book 614,272 58,472,928 38-40 e7fff761b481a774b5dd78f643058fe6398b85e91f0b175999f9d786610d63f3 last_trade_price 53,635 3,048,480 41-41 48334c8afb48acfe4fa68b602688c7a02ffb9378d469bbac7e66ca51c6d0851d market_resolved 632 102,611 42-42 1e7db9fdb4b4ac4b62de268e8e570ced3809c870552fb097e37c49dcdbe4364a new_market 1,412 142,559 43-43 ea5e2d1a80882f9091ef9357d82e93cb9dc79d7d3edf99aee6dd71e91801bc69 price_change 92,810,432 923,990,787 44-398 39eefd66847e46c00e9a8bbad1a8416c391cfb251bbb1103be3845a74983ee7e tick_size_change 2,728 100,310 399-399 8e4bdf6b5acb6adf0cd83adf5f03a7d2c89681c603e86c8ad1fab1bd2f6f4baf EVENT MIX count share price_change 92,810,432 89.86% best_bid_ask 9,805,945 9.49% book 614,272 0.59% last_trade_price 53,635 0.05% tick_size_change 2,728 <0.01% new_market 1,412 <0.01% market_resolved 632 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,806,151 9,805,945 206 191 FULL book 614,308 614,272 36 194,890 FULL last_trade_price 53,635 53,635 0 0 FULL market_resolved 632 632 0 0 FULL new_market 1,412 1,412 0 0 FULL price_change 92,812,070 92,810,432 1,638 91 FULL tick_size_change 2,728 2,728 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,797,455 1,774 78ms 105ms 527ms 26.6s 0 transport_latency_assumed best_bid_ask h 9,797,588 93,870 18ms 28ms 255ms 1.1min 0 transport_latency_assumed best_bid_ask i 9,803,458 41,978 23ms 32ms 165ms 29.7s 0 transport_latency_assumed best_bid_ask k 9,803,174 368,882 13ms 25ms 198ms 26.5s 0 transport_latency_assumed best_bid_ask m 9,798,366 9,299,441 4ms 10ms 110ms 10.6s 0 transport_latency_assumed book g 228,441 93,353 15.6s 1.3d 38.7d 123.4d 0 book_staleness book h 262,546 97,171 42.3s 1.4d 38.7d 123.4d 0 book_staleness book i 219,549 65,196 1.7s 1.2d 36.7d 123.4d 0 book_staleness book k 280,955 114,762 1.2min 1.5d 38.7d 123.4d 0 book_staleness book m 311,654 243,790 2.3min 1.7d 38.7d 123.4d 0 book_staleness last_trade_price g 51,441 11 86ms 800ms 16.0s 26.7s 0 transport_latency_assumed last_trade_price h 53,185 646 20ms 85ms 820ms 11.2s 0 transport_latency_assumed last_trade_price i 53,450 865 25ms 57ms 398ms 2.7s 0 transport_latency_assumed last_trade_price k 53,336 2,186 15ms 53ms 400ms 25.9s 0 transport_latency_assumed last_trade_price m 53,194 49,927 5ms 15ms 184ms 10.0s 0 transport_latency_assumed market_resolved g 610 not meas. 86ms 16.9s 56.2s 56.9s 0 transport_latency_assumed market_resolved h 610 6 21ms 16.4s 56.4s 56.5s 0 transport_latency_assumed market_resolved i 610 23 25ms 135ms 57.0s 57.3s 0 transport_latency_assumed market_resolved k 610 25 16ms 15.4s 56.3s 56.4s 0 transport_latency_assumed market_resolved m 610 578 5ms 13.0s 53.0s 53.1s 0 transport_latency_assumed new_market g 937 109 314ms 19.4s 1.1min 1.7min 0 transport_latency_assumed new_market h 937 214 163ms 21.5s 1.1min 1.7min 0 transport_latency_assumed new_market i 937 207 147ms 14.9s 57.3s 1.5min 0 transport_latency_assumed new_market k 937 227 193ms 15.8s 53.7s 1.7min 0 transport_latency_assumed new_market m 937 655 78ms 15.8s 1.0min 1.4min 0 transport_latency_assumed price_change g 92,555,761 15,174 78ms 144ms 1.3s 26.7s 0 transport_latency_assumed price_change h 92,619,248 951,692 18ms 34ms 354ms 1.1min 0 transport_latency_assumed price_change i 92,767,452 557,384 23ms 36ms 206ms 37.4s 0 transport_latency_assumed price_change k 92,735,766 3,479,526 13ms 28ms 252ms 27.8s 0 transport_latency_assumed price_change m 92,627,268 87,806,656 4ms 11ms 142ms 10.6s 0 transport_latency_assumed tick_size_change g 2,728 not meas. 77ms 93ms 627ms 1.3s 0 transport_latency_assumed tick_size_change h 2,728 24 18ms 37ms 513ms 6.2s 0 transport_latency_assumed tick_size_change i 2,728 4 23ms 31ms 98ms 5.8s 0 transport_latency_assumed tick_size_change k 2,728 55 13ms 21ms 152ms 6.3s 0 transport_latency_assumed tick_size_change m 2,728 2,645 4ms 9ms 44ms 3.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-30/07/2026-09-30T07.parquet sha256sum 2026-09-30T07.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.