Hour audit: 2026-10-03T08
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-03T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T08:00:00.000044955+00:00 · last event 2026-10-03T08:59:59.999950144+00:00
VOLUME 101,857,091 rows · 1,040,295,920 bytes (992.10 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured g: 101,666,947 · k: 101,570,287 · m: 101,565,303 · i: 101,560,481 · h: 101,552,992 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 246,735 (0.24%) · k: 3,077,315 (3.02%) · m: 97,699,537 (95.92%) · i: 270,062 (0.27%) · h: 563,442 (0.55%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 101,857,091 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f7b870f15d9d9b5c170d98c311188c75f95458a04ea2776bb290c749008f14e5
the corpus checksum ledger names this file with the same digest
joined 101,859,342 to merged 101,857,091, minus 2,251 (minus 0.0022%)
boundary drops 2,251 · 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-03T10:43:22Z 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,304,855 107,836,854 0-35 bf99c80d26ea82165cdf79bf5fa08299dd548c03f11948c4af82ba9db2077c98 book 320,872 31,276,301 36-37 771830b1e1e411b79be1e25550e33980f1414455f395df1822f84ef8f5e00cdd last_trade_price 43,247 2,513,675 38-38 77a7b907be7aa831ad51057d77f9500d2b6e6e57d58f9ce444c1e67ed07c86b8 market_resolved 728 113,606 39-39 164529fa1b514b8e61bc87b90484a56f8ca0f9ba69b9df5a0d220c9d9290c5e8 new_market 363 39,678 40-40 7dd4b6e9c1a1b5f5c8c3454318069f087e1173cd14935efb59a377f0299ca948 price_change 92,184,462 897,259,107 41-392 7c99fc69b12f61cb5eb5924816bbf053f34717863a7d6b248f8865842908383e tick_size_change 2,564 92,060 393-393 1143edc98bdf295bcfc726f35e7d6c532ef6690f6901e39a7497b0c0cbe11f5d EVENT MIX count share price_change 92,184,462 90.50% best_bid_ask 9,304,855 9.14% book 320,872 0.32% last_trade_price 43,247 0.04% tick_size_change 2,564 <0.01% market_resolved 728 <0.01% new_market 363 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,305,056 9,304,855 201 65 FULL book 320,880 320,872 8 99,689 FULL last_trade_price 43,247 43,247 0 0 FULL market_resolved 728 728 0 1 FULL new_market 363 363 0 0 FULL price_change 92,186,504 92,184,462 2,042 243 FULL tick_size_change 2,564 2,564 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,301,769 644 77ms 93ms 227ms 16.4s 0 transport_latency_assumed best_bid_ask h 9,303,041 43,337 17ms 22ms 72ms 7.1s 0 transport_latency_assumed best_bid_ask i 9,304,392 16,937 21ms 25ms 68ms 4.2s 0 transport_latency_assumed best_bid_ask k 9,304,411 274,097 12ms 18ms 58ms 9.0s 0 transport_latency_assumed best_bid_ask m 9,304,335 8,969,840 4ms 8ms 42ms 2.2s 0 transport_latency_assumed book g 315,086 228,000 4.5min 1.3d 41.8d 126.4d 0 book_staleness book h 88,936 3,104 20ms 42ms 1.0h 107.9d 0 book_staleness book i 87,648 1,216 22ms 45ms 1.8s 126.4d 0 book_staleness book k 88,127 4,028 15ms 29ms 3.4min 107.8d 0 book_staleness book m 88,787 84,524 6ms 14ms 28.8min 2.7d 0 book_staleness last_trade_price g 43,168 36 79ms 195ms 2.1s 16.4s 0 transport_latency_assumed last_trade_price h 43,084 372 18ms 28ms 236ms 3.0s 0 transport_latency_assumed last_trade_price i 43,192 197 22ms 36ms 309ms 3.8s 0 transport_latency_assumed last_trade_price k 43,178 1,696 13ms 23ms 226ms 1.2s 0 transport_latency_assumed last_trade_price m 43,150 40,946 5ms 11ms 123ms 1.2s 0 transport_latency_assumed market_resolved g 705 not meas. 81ms 27.1s 47.7s 47.7s 0 transport_latency_assumed market_resolved h 706 1 19ms 28.0s 54.5s 54.6s 0 transport_latency_assumed market_resolved i 706 not meas. 22ms 27.0s 48.3s 48.3s 0 transport_latency_assumed market_resolved k 706 29 14ms 29.0s 41.9s 56.9s 0 transport_latency_assumed market_resolved m 706 698 5ms 23.2s 44.5s 44.6s 0 transport_latency_assumed new_market g 255 19 99ms 703ms 1.4min 1.6min 0 transport_latency_assumed new_market h 255 67 40ms 315ms 13.2s 1.5min 0 transport_latency_assumed new_market i 255 26 34ms 30.1s 32.2s 1.7min 0 transport_latency_assumed new_market k 255 48 45ms 30.6s 1.5min 1.6min 0 transport_latency_assumed new_market m 255 203 25ms 30.4s 1.4min 1.6min 0 transport_latency_assumed price_change g 92,003,400 18,036 77ms 97ms 612ms 16.5s 0 transport_latency_assumed price_change h 92,114,406 516,554 18ms 23ms 171ms 9.0s 0 transport_latency_assumed price_change i 92,121,724 251,682 21ms 27ms 240ms 4.2s 0 transport_latency_assumed price_change k 92,131,046 2,797,374 12ms 20ms 120ms 9.0s 0 transport_latency_assumed price_change m 92,125,506 88,600,816 4ms 9ms 72ms 2.5s 0 transport_latency_assumed tick_size_change g 2,564 not meas. 77ms 92ms 157ms 3.4s 0 transport_latency_assumed tick_size_change h 2,564 7 18ms 23ms 38ms 129ms 0 transport_latency_assumed tick_size_change i 2,564 4 21ms 27ms 54ms 154ms 0 transport_latency_assumed tick_size_change k 2,564 43 13ms 20ms 39ms 80ms 0 transport_latency_assumed tick_size_change m 2,564 2,510 4ms 8ms 22ms 146ms 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-03/08/2026-10-03T08.parquet sha256sum 2026-10-03T08.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.