Hour audit: 2026-09-30T20
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-30T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-30T20:00:00.000004168+00:00 · last event 2026-09-30T20:59:59.999982718+00:00
VOLUME 109,189,434 rows · 1,223,602,049 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 108,504,536 · h: 108,471,115 · m: 108,469,760 · i: 108,461,795 · g: 103,069,208 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 12,638,801 (11.58%) · h: 4,492,135 (4.11%) · m: 82,767,014 (75.80%) · i: 8,671,174 (7.94%) · g: 620,310 (0.57%) (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 109,189,434 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 dd98eec6bb235535ca558be501b0eb02ffa95e41d8a81b671c1094feb0a9b113
the corpus checksum ledger names this file with the same digest
joined 109,195,509 to merged 109,189,434, minus 6,075 (minus 0.0056%)
boundary drops 6,075 · 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-30T23:58:26Z 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,011,483 123,469,122 0-38 9c09c4cdc699ba60f8c44e11a31717327c028dd82a4d1dda630617f3008bd0d4 book 1,077,083 77,916,634 39-43 0c8b31a4a57d3a56087b8e292a1b027fbd25203ec73df8d8d9550bc1382b78a1 last_trade_price 59,726 3,523,898 44-44 5f239056a4919496ab2edb77a8c5ea9ae44a7e31141296f4177b72245d21ce00 market_resolved 1,818 261,108 45-45 8462bff5e8d652367fc33366f8f714f5bfc61b9ac1c88ec8f2461c53b36f06c5 new_market 3,056 345,506 46-46 117e3d6110ef761bddbcfb85fa379260e6391c4b0ce61c80ba35cbcdf6b77c18 price_change 98,032,752 1,016,709,221 47-420 f16c596a9e645a5d3d331d1bf0a68c09c016b4c19b2353a7a8452ed37bb889be tick_size_change 3,516 130,770 421-421 e88f3fa0f94d7414b48992d63bd9e8624e4a8b3594c2f0f3165639a79f08409b EVENT MIX count share price_change 98,032,752 89.78% best_bid_ask 10,011,483 9.17% book 1,077,083 0.99% last_trade_price 59,726 0.05% tick_size_change 3,516 <0.01% new_market 3,056 <0.01% market_resolved 1,818 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,012,211 10,011,483 728 2,783 FULL book 1,077,098 1,077,083 15 9,462 FULL last_trade_price 59,730 59,726 4 136 FULL market_resolved 1,818 1,818 0 4 FULL new_market 3,056 3,056 0 0 FULL price_change 98,038,080 98,032,752 5,328 2,129 FULL tick_size_change 3,516 3,516 0 35 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,460,404 13,117 79ms 137ms 700ms 25.1s 0 transport_latency_assumed best_bid_ask h 9,996,666 359,097 19ms 66ms 602ms 1.8min 0 transport_latency_assumed best_bid_ask i 9,996,557 693,017 19ms 72ms 329ms 38.6s 0 transport_latency_assumed best_bid_ask k 9,998,656 1,118,122 14ms 52ms 336ms 54.5s 0 transport_latency_assumed best_bid_ask m 9,998,206 7,828,130 5ms 39ms 234ms 4.8s 0 transport_latency_assumed book g 902,759 444,747 33.8min 2.9d 39.3d 123.9d 0 book_staleness book h 597,385 122,699 13.4min 2.4d 39.3d 123.9d 0 book_staleness book i 596,404 133,696 13.1min 2.4d 39.3d 123.9d 0 book_staleness book k 598,660 149,901 12.8min 2.4d 39.3d 123.9d 0 book_staleness book m 598,621 226,040 12.2min 2.4d 39.3d 123.9d 0 book_staleness last_trade_price g 56,259 193 88ms 374ms 10.9s 24.6s 0 transport_latency_assumed last_trade_price h 59,588 2,659 20ms 100ms 763ms 1.6min 0 transport_latency_assumed last_trade_price i 59,652 5,879 23ms 120ms 1.1s 3.7s 0 transport_latency_assumed last_trade_price k 59,625 8,294 15ms 63ms 366ms 17.9s 0 transport_latency_assumed last_trade_price m 59,564 42,701 7ms 63ms 331ms 3.6s 0 transport_latency_assumed market_resolved g 1,629 53 84ms 30.9s 3.1min 5.1min 0 transport_latency_assumed market_resolved h 1,633 41 20ms 29.2s 52.9s 53.9s 0 transport_latency_assumed market_resolved i 1,633 74 21ms 24.7s 47.7s 57.7s 0 transport_latency_assumed market_resolved k 1,633 216 16ms 298ms 52.1s 55.9s 0 transport_latency_assumed market_resolved m 1,633 1,434 6ms 23.7s 54.3s 55.6s 0 transport_latency_assumed new_market g 2,216 232 12.4s 30.0s 1.0min 1.8min 0 transport_latency_assumed new_market h 2,216 545 14.0s 32.4s 1.0min 1.4min 0 transport_latency_assumed new_market i 2,216 644 12.8s 26.8s 56.9s 1.7min 0 transport_latency_assumed new_market k 2,216 471 13.3s 30.1s 57.9s 1.6min 0 transport_latency_assumed new_market m 2,216 1,164 11.6s 26.2s 57.8s 1.5min 0 transport_latency_assumed price_change g 92,642,565 161,968 80ms 192ms 3.2s 25.5s 0 transport_latency_assumed price_change h 97,810,111 4,006,987 19ms 74ms 803ms 1.8min 0 transport_latency_assumed price_change i 97,801,817 7,837,615 19ms 80ms 543ms 49.5s 0 transport_latency_assumed price_change k 97,840,230 11,361,389 14ms 58ms 420ms 56.0s 0 transport_latency_assumed price_change m 97,806,004 74,664,793 6ms 47ms 308ms 4.9s 0 transport_latency_assumed tick_size_change g 3,376 not meas. 79ms 107ms 502ms 834ms 0 transport_latency_assumed tick_size_change h 3,516 107 18ms 58ms 193ms 1.1s 0 transport_latency_assumed tick_size_change i 3,516 249 18ms 70ms 153ms 245ms 0 transport_latency_assumed tick_size_change k 3,516 408 13ms 47ms 166ms 324ms 0 transport_latency_assumed tick_size_change m 3,516 2,752 5ms 31ms 113ms 254ms 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/20/2026-09-30T20.parquet sha256sum 2026-09-30T20.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.