Hour audit: 2026-10-01T10
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-01T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T10:00:00.000115205+00:00 · last event 2026-10-01T10:59:59.999723017+00:00
VOLUME 110,675,156 rows · 1,222,510,144 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 110,002,709 · i: 109,991,409 · h: 108,370,665 · m: 106,823,089 · g: 105,955,250 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 9,742,393 (8.80%) · i: 18,752,480 (16.94%) · h: 31,541,064 (28.50%) · m: 45,870,146 (41.45%) · g: 4,769,073 (4.31%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 508a1b91cbc238efabd8d4383cfa76e9fcb1e95829d2df646a1c5fc61c70d4f5
the corpus checksum ledger names this file with the same digest
joined 110,683,788 to merged 110,675,156, minus 8,632 (minus 0.0078%)
boundary drops 8,632 · 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-01T13:07:51Z 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,561,763 122,166,908 0-36 c7e7e5a9d123750f21dfbee0a794c90a5eea610ed2d15d52177bd749a0430a06 book 316,290 31,481,254 37-38 1ae58c81db90abebef021b1f45794285a1493ce6c38cf84e521d618627ca4793 last_trade_price 48,879 2,925,587 39-39 e62f114ad625433669a23060bdb8d3b83bafe59679a8168abdc2ec726bc2bd1d market_resolved 791 117,160 40-40 1fccf7f30ea20ca98cfc888b88ed0285bd889d88ef8c996e268d3af5a11e85f5 new_market 1,283 125,909 41-41 38a4c096becd1c14f5271b98d93e565267b073a80820a4e438e188a67786274a price_change 100,742,946 1,064,309,592 42-426 fbbfb716d94cb12ad8242c7d451305c884a2cfe63db0e9f7c59102478226f0b9 tick_size_change 3,204 119,508 427-427 458b2f69f3eda2bb21bf9923f72acf883e302bfc417881c5aa32cbeb3f3041ae EVENT MIX count share price_change 100,742,946 91.03% best_bid_ask 9,561,763 8.64% book 316,290 0.29% last_trade_price 48,879 0.04% tick_size_change 3,204 <0.01% new_market 1,283 <0.01% market_resolved 791 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,562,454 9,561,763 691 229 FULL book 317,684 316,290 1,394 92,733 FULL last_trade_price 48,879 48,879 0 14 FULL market_resolved 792 791 1 69 FULL new_market 1,283 1,283 0 16 FULL price_change 100,749,492 100,742,946 6,546 16,122 FULL tick_size_change 3,204 3,204 0 18 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,547,946 421,639 165ms 447ms 1.0s 15.1s 0 transport_latency_assumed best_bid_ask h 9,549,092 2,531,987 87ms 349ms 869ms 54.3s 0 transport_latency_assumed best_bid_ask i 9,552,890 1,709,480 110ms 379ms 900ms 14.3s 0 transport_latency_assumed best_bid_ask k 9,528,653 808,954 145ms 424ms 967ms 9.3s 0 transport_latency_assumed best_bid_ask m 9,541,147 4,089,703 80ms 338ms 866ms 10.5s 0 transport_latency_assumed book g 141,964 38,826 334ms 9.9h 24.0d 124.5d 0 book_staleness book h 125,122 48,775 152ms 3.0h 22.6d 106.0d 0 book_staleness book i 131,903 38,662 236ms 5.2h 24.0d 106.0d 0 book_staleness book k 204,877 111,607 4.9s 1.4d 39.8d 124.5d 0 book_staleness book m 132,188 78,420 146ms 6.0h 5.4d 105.9d 0 book_staleness last_trade_price g 48,224 891 195ms 598ms 1.4s 12.7s 0 transport_latency_assumed last_trade_price h 48,498 13,677 74ms 452ms 1.3s 30.0s 0 transport_latency_assumed last_trade_price i 48,495 5,499 142ms 527ms 1.7s 14.3s 0 transport_latency_assumed last_trade_price k 48,329 3,705 166ms 560ms 1.4s 9.2s 0 transport_latency_assumed last_trade_price m 48,485 25,107 61ms 402ms 1.3s 10.4s 0 transport_latency_assumed market_resolved g 647 43 227ms 32.2s 54.4s 2.5min 0 transport_latency_assumed market_resolved h 647 174 122ms 26.7s 58.3s 58.3s 0 transport_latency_assumed market_resolved i 647 125 187ms 38.5s 49.7s 2.3min 0 transport_latency_assumed market_resolved k 712 167 184ms 42.9s 8.7min 8.7min 0 transport_latency_assumed market_resolved m 647 282 130ms 37.8s 49.6s 52.1s 0 transport_latency_assumed new_market g 814 189 687ms 30.5s 1.3min 1.7min 0 transport_latency_assumed new_market h 814 288 173ms 23.9s 35.0s 1.6min 0 transport_latency_assumed new_market i 814 185 181ms 23.2s 34.8s 1.7min 0 transport_latency_assumed new_market k 830 141 397ms 25.2s 6.9min 6.9min 0 transport_latency_assumed new_market m 814 480 66ms 22.5s 35.7s 1.3min 0 transport_latency_assumed price_change g 96,212,475 4,307,316 177ms 498ms 1.3s 15.1s 0 transport_latency_assumed price_change h 98,643,288 28,945,112 87ms 375ms 1.0s 55.3s 0 transport_latency_assumed price_change i 100,253,456 16,998,078 121ms 416ms 1.1s 14.4s 0 transport_latency_assumed price_change k 100,216,152 8,817,582 150ms 459ms 1.2s 9.3s 0 transport_latency_assumed price_change m 97,096,604 41,674,858 83ms 363ms 1.1s 10.5s 0 transport_latency_assumed tick_size_change g 3,180 169 231ms 570ms 1.2s 7.5s 0 transport_latency_assumed tick_size_change h 3,204 1,051 93ms 445ms 873ms 1.1s 0 transport_latency_assumed tick_size_change i 3,204 451 179ms 538ms 969ms 1.6s 0 transport_latency_assumed tick_size_change k 3,156 237 208ms 511ms 1.1s 1.3s 0 transport_latency_assumed tick_size_change m 3,204 1,296 108ms 446ms 881ms 5.3s 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-01/10/2026-10-01T10.parquet sha256sum 2026-10-01T10.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.