Hour audit: 2026-10-03T03
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-03T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T03:00:00.000040161+00:00 · last event 2026-10-03T03:59:59.999942832+00:00
VOLUME 94,454,879 rows · 956,012,375 bytes (911.72 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 94,400,741 · h: 94,388,646 · i: 94,380,471 · m: 94,367,512 · g: 94,315,547 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 2,025,132 (2.14%) · h: 487,771 (0.52%) · i: 277,491 (0.29%) · m: 91,656,383 (97.04%) · g: 8,102 (0.01%) (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 94,454,879 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 58c9fef724eb1f0278ac546efada9cacfd263afe32734dd295ceebc41c9c7725
the corpus checksum ledger names this file with the same digest
joined 94,456,536 to merged 94,454,879, minus 1,657 (minus 0.0018%)
boundary drops 1,657 · 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-03T05:41:59Z 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,022,012 101,566,701 0-34 6d4bc3531217671e4d84189fd043f48ea076c2243b84ae0746b584fd26d466d0 book 107,056 11,336,719 35-35 db5476816f3292812db178030117115ab8cba3aac75d7672e10a242a70ed8edd last_trade_price 37,949 2,205,263 36-36 3fbb77e5c7286606cd4a5d4867af05c43d34cbf085dfe7b9c3299ee508d25222 market_resolved 1,756 277,068 37-37 ed0cdcc3fada1b85343072528a93207056134b931512e6d78516631e575300ce new_market 312 36,155 38-38 8b622c75c897be5a6032814a3fd5ed1998c9fe8bbdac0a4ad7b74fed652a0e46 price_change 85,283,370 839,419,968 39-364 27e3dc6a46d71adfc97040b5de9ae82613d794732963d5f2cefe5e89db23de4f tick_size_change 2,424 89,107 365-365 dfab5c52377cc9aff4b5547efc2c11df4f1441b78c80fe3bce5c86bcaa410917 EVENT MIX count share price_change 85,283,370 90.29% best_bid_ask 9,022,012 9.55% book 107,056 0.11% last_trade_price 37,949 0.04% tick_size_change 2,424 <0.01% market_resolved 1,756 <0.01% new_market 312 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,022,182 9,022,012 170 69 FULL book 107,056 107,056 0 13,291 FULL last_trade_price 37,950 37,949 1 0 FULL market_resolved 1,756 1,756 0 0 FULL new_market 312 312 0 0 FULL price_change 85,284,856 85,283,370 1,486 213 FULL tick_size_change 2,424 2,424 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,020,976 215 78ms 93ms 175ms 9.9s 0 transport_latency_assumed best_bid_ask h 9,020,922 40,437 17ms 21ms 63ms 19.7s 0 transport_latency_assumed best_bid_ask i 9,021,172 20,204 20ms 24ms 52ms 4.2s 0 transport_latency_assumed best_bid_ask k 9,021,376 183,344 13ms 19ms 49ms 5.2s 0 transport_latency_assumed best_bid_ask m 9,020,552 8,777,812 4ms 7ms 34ms 2.7s 0 transport_latency_assumed book g 81,594 5,450 82ms 209ms 1.1d 126.2d 0 book_staleness book h 81,745 6,609 20ms 66ms 1.1d 107.7d 0 book_staleness book i 79,458 3,713 22ms 48ms 9.3h 107.7d 0 book_staleness book k 81,952 8,497 16ms 55ms 1.1d 126.2d 0 book_staleness book m 86,438 82,787 6ms 38.7s 1.1d 55.6d 0 book_staleness last_trade_price g 37,940 7 80ms 129ms 346ms 1.1s 0 transport_latency_assumed last_trade_price h 37,734 386 18ms 28ms 165ms 2.3s 0 transport_latency_assumed last_trade_price i 37,760 248 21ms 32ms 164ms 1.0s 0 transport_latency_assumed last_trade_price k 37,794 1,318 14ms 23ms 167ms 1.0s 0 transport_latency_assumed last_trade_price m 37,753 35,990 5ms 11ms 93ms 1.0s 0 transport_latency_assumed market_resolved g 1,629 78 80ms 33.1s 54.5s 56.7s 0 transport_latency_assumed market_resolved h 1,629 7 18ms 34.5s 50.9s 52.4s 0 transport_latency_assumed market_resolved i 1,629 15 22ms 26.9s 44.9s 56.9s 0 transport_latency_assumed market_resolved k 1,629 67 15ms 37.6s 51.6s 55.1s 0 transport_latency_assumed market_resolved m 1,629 1,589 5ms 26.1s 43.2s 56.2s 0 transport_latency_assumed new_market g 228 22 98ms 9.1s 1.4min 1.4min 0 transport_latency_assumed new_market h 228 36 43ms 8.7s 15.2s 1.3min 0 transport_latency_assumed new_market i 228 41 30ms 263ms 1.3min 1.5min 0 transport_latency_assumed new_market k 228 42 39ms 8.2s 1.0min 1.5min 0 transport_latency_assumed new_market m 228 171 21ms 10.2s 1.4min 1.7min 0 transport_latency_assumed price_change g 85,170,756 2,330 78ms 94ms 279ms 10.0s 0 transport_latency_assumed price_change h 85,243,964 440,292 17ms 22ms 98ms 19.7s 0 transport_latency_assumed price_change i 85,237,800 253,266 20ms 25ms 91ms 4.2s 0 transport_latency_assumed price_change k 85,255,338 1,831,840 13ms 20ms 61ms 5.2s 0 transport_latency_assumed price_change m 85,218,488 82,755,642 4ms 8ms 39ms 2.9s 0 transport_latency_assumed tick_size_change g 2,424 not meas. 78ms 92ms 272ms 732ms 0 transport_latency_assumed tick_size_change h 2,424 4 17ms 21ms 85ms 1.0s 0 transport_latency_assumed tick_size_change i 2,424 4 20ms 24ms 55ms 515ms 0 transport_latency_assumed tick_size_change k 2,424 24 13ms 17ms 35ms 843ms 0 transport_latency_assumed tick_size_change m 2,424 2,392 4ms 6ms 15ms 211ms 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/03/2026-10-03T03.parquet sha256sum 2026-10-03T03.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.