Hour audit: 2026-10-02T20
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-10-02T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T20:00:00.000240639+00:00 · last event 2026-10-02T20:59:59.998972055+00:00
VOLUME 106,350,280 rows · 1,204,906,935 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 105,274,732 · h: 105,250,090 · m: 105,231,259 · k: 99,652,272 · g: 99,006,188 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,503,047 (1.41%) · h: 2,818,117 (2.65%) · m: 95,667,943 (89.96%) · k: 5,870,951 (5.52%) · g: 490,222 (0.46%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 f0bbede0a1ebbe4747cac0e12340aab67cd7d40225fedffe70bf2b7884782ea9
the corpus checksum ledger names this file with the same digest
joined 106,362,592 to merged 106,350,280, minus 12,312 (minus 0.0116%)
boundary drops 12,312 · 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-02T22:45:46Z 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,777,740 118,575,570 0-37 7e9baa4d51f6d841130a1f4624cb8efdfd0d31b5a4a5427e229339efaa5f787d book 1,854,243 101,484,405 38-45 ea78628d85003baa5388d56bf4a9dde4fe4ffdf6782006d65bd0cff70423b61d last_trade_price 61,192 3,539,604 46-46 682fb6d21c90efaf6612c4c48f4156194fecc7caeba2e8eb009b6002e5a40dad market_resolved 2,369 343,816 47-47 f726df9944462ba617532911b25289de4ee626dd4b7205b3939ba241d979542f new_market 3,698 351,677 48-48 9ca841998be0057a50f1f2444c74b8e434af5a3d1f511f2b954fc11d62f66f8c price_change 94,645,842 979,203,347 49-410 d25d41b544a697c39a6703a0b0e20d205447de812d5ddc0bdc6ea4fa1e470a03 tick_size_change 5,196 191,304 411-411 25c9d5ceede0a6f5e77a61d2c297e184fcdc67a70ea4715a8e436527d7ff801c EVENT MIX count share price_change 94,645,842 88.99% best_bid_ask 9,777,740 9.19% book 1,854,243 1.74% last_trade_price 61,192 0.06% tick_size_change 5,196 <0.01% new_market 3,698 <0.01% market_resolved 2,369 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,778,377 9,777,740 637 2,977 FULL book 1,854,355 1,854,243 112 1,086 FULL last_trade_price 61,193 61,192 1 195 FULL market_resolved 2,369 2,369 0 1 FULL new_market 3,698 3,698 0 0 FULL price_change 94,657,404 94,645,842 11,562 1,888 FULL tick_size_change 5,196 5,196 0 66 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,221,512 2,665 81ms 121ms 814ms 29.2s 0 transport_latency_assumed best_bid_ask h 9,770,451 217,558 19ms 38ms 579ms 1.2min 0 transport_latency_assumed best_bid_ask i 9,770,728 99,572 25ms 42ms 341ms 46.3s 0 transport_latency_assumed best_bid_ask k 9,246,702 488,326 14ms 28ms 301ms 1.1min 0 transport_latency_assumed best_bid_ask m 9,771,399 8,969,619 5ms 17ms 224ms 11.2s 0 transport_latency_assumed book g 1,032,353 443,830 27.9min 1.1d 41.3d 125.9d 0 book_staleness book h 898,385 327,623 18.7min 1.0d 41.3d 125.9d 0 book_staleness book i 885,708 316,552 18.4min 23.5h 41.3d 125.9d 0 book_staleness book k 1,008,141 348,619 25.3min 1.1d 41.3d 125.9d 0 book_staleness book m 870,879 417,619 17.6min 1.0d 41.3d 125.9d 0 book_staleness last_trade_price g 56,808 46 95ms 1.4s 14.0s 29.3s 0 transport_latency_assumed last_trade_price h 60,924 1,358 21ms 155ms 1.1s 55.1s 0 transport_latency_assumed last_trade_price i 60,962 568 29ms 222ms 2.2s 5.5s 0 transport_latency_assumed last_trade_price k 58,005 3,920 15ms 63ms 438ms 36.9s 0 transport_latency_assumed last_trade_price m 60,919 55,300 6ms 28ms 286ms 2.0s 0 transport_latency_assumed market_resolved g 2,264 184 85ms 44.9s 7.2min 7.3min 0 transport_latency_assumed market_resolved h 2,113 72 20ms 141ms 44.8s 59.9s 0 transport_latency_assumed market_resolved i 2,113 105 27ms 10.3s 50.2s 57.7s 0 transport_latency_assumed market_resolved k 2,214 144 15ms 38.6s 6.7min 7.4min 0 transport_latency_assumed market_resolved m 2,113 1,864 6ms 9.8s 50.3s 55.0s 0 transport_latency_assumed new_market g 2,308 304 468ms 4.7min 6.2min 6.6min 0 transport_latency_assumed new_market h 2,189 659 303ms 38.9s 4.1min 4.3min 0 transport_latency_assumed new_market i 2,189 612 251ms 37.4s 4.1min 4.3min 0 transport_latency_assumed new_market k 2,348 807 318ms 4.8min 6.5min 6.6min 0 transport_latency_assumed new_market m 2,189 1,316 107ms 33.4s 3.6min 4.2min 0 transport_latency_assumed price_change g 88,685,983 43,192 82ms 204ms 3.8s 29.8s 0 transport_latency_assumed price_change h 94,510,836 2,270,656 19ms 52ms 789ms 1.3min 0 transport_latency_assumed price_change i 94,547,848 1,085,496 26ms 58ms 652ms 46.7s 0 transport_latency_assumed price_change k 89,329,930 5,028,720 14ms 34ms 376ms 1.1min 0 transport_latency_assumed price_change m 94,518,568 86,217,778 5ms 20ms 262ms 11.2s 0 transport_latency_assumed tick_size_change g 4,960 1 81ms 115ms 301ms 469ms 0 transport_latency_assumed tick_size_change h 5,192 191 19ms 48ms 281ms 1.2s 0 transport_latency_assumed tick_size_change i 5,184 142 25ms 52ms 258ms 1.0s 0 transport_latency_assumed tick_size_change k 4,932 415 14ms 32ms 150ms 331ms 0 transport_latency_assumed tick_size_change m 5,192 4,447 5ms 53ms 330ms 840ms 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-10-02/20/2026-10-02T20.parquet sha256sum 2026-10-02T20.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.