Hour audit: 2026-10-03T16
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-03T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T16:00:00.000249549+00:00 · last event 2026-10-03T16:59:59.999873397+00:00
VOLUME 142,409,537 rows · 1,644,931,166 bytes (1.53 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 139,887,561 · h: 139,881,674 · i: 133,685,151 · g: 127,278,903 · k: 111,969,449 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 129,048,597 (90.62%) · h: 2,758,604 (1.94%) · i: 1,762,977 (1.24%) · g: 982,362 (0.69%) · k: 7,856,997 (5.52%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 0bd037fbde0a274bcd8c3378248b1eaecb0e0200f54031ab6f3fa160b68f7fc1
the corpus checksum ledger names this file with the same digest
joined 142,412,980 to merged 142,409,537, minus 3,443 (minus 0.0024%)
boundary drops 3,443 · 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-03T18:52:07Z 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 12,161,316 148,727,591 0-46 6b1f3ff406b14672b69dfb3bbb0e7db549716e91ab10e4067580a093f425647e book 2,529,082 111,287,775 47-56 d99698d9e08de71e65111e13b90d05547efa4f4d88d0ad7ff5b53c30c5944c9f last_trade_price 64,277 3,795,095 57-57 f67f0ac3cf6e2f4580b94c5bf9ca7e7d8ba710ef013e31ace2fa6f6001aaff12 market_resolved 7,915 474,579 58-58 e9cfd1656d74a69cc4d58ec4fa1c69b1d07ccd6c43b119a3a529a296753aaf46 new_market 8,553 412,835 59-59 5f328079587617d9ae7a4d17ba778f7d1e09036823d3a8a0b2ee1af57bbb4c0c price_change 127,630,874 1,378,339,543 60-546 c572c24d6950587276f3fce5055dca96a0743ab843f63a989a0bc322ad7af0d6 tick_size_change 7,520 275,359 547-547 82e0931a66c42e0ea5edc6a866e41e2b8007fa32e35bcec3ff76410e1f70cb33 EVENT MIX count share price_change 127,630,874 89.62% best_bid_ask 12,161,316 8.54% book 2,529,082 1.78% last_trade_price 64,277 0.05% new_market 8,553 <0.01% market_resolved 7,915 <0.01% tick_size_change 7,520 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,161,586 12,161,316 270 7,509 FULL book 2,529,874 2,529,082 792 237,522 FULL last_trade_price 64,280 64,277 3 759 FULL market_resolved 7,915 7,915 0 187 FULL new_market 8,553 8,553 0 3 FULL price_change 127,633,252 127,630,874 2,378 5,013 FULL tick_size_change 7,520 7,520 0 471 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,988,476 2,364 80ms 124ms 755ms 28.9s 0 transport_latency_assumed best_bid_ask h 12,157,948 228,036 19ms 34ms 523ms 59.4s 0 transport_latency_assumed best_bid_ask i 11,584,713 132,955 21ms 35ms 279ms 44.7s 0 transport_latency_assumed best_bid_ask k 9,531,870 548,184 14ms 30ms 257ms 46.3s 0 transport_latency_assumed best_bid_ask m 12,158,606 11,249,777 5ms 15ms 142ms 6.4s 0 transport_latency_assumed book g 1,095,260 948,367 13.3min 1.6d 42.1d 126.7d 0 book_staleness book h 135,890 6,202 26ms 203ms 58.8min 104.3d 0 book_staleness book i 613,914 126,682 8.0min 1.6d 42.1d 126.8d 0 book_staleness book k 2,137,039 1,327,879 24.0min 1.8d 42.1d 126.8d 0 book_staleness book m 136,084 119,952 8ms 54ms 1.3h 15.3d 0 book_staleness last_trade_price g 57,748 45 89ms 657ms 10.5s 28.9s 0 transport_latency_assumed last_trade_price h 64,004 1,622 21ms 75ms 965ms 53.6s 0 transport_latency_assumed last_trade_price i 61,341 990 24ms 76ms 858ms 27.7s 0 transport_latency_assumed last_trade_price k 51,773 3,969 16ms 47ms 512ms 12.8s 0 transport_latency_assumed last_trade_price m 63,993 57,651 6ms 23ms 228ms 5.0s 0 transport_latency_assumed market_resolved g 2,732 179 88ms 5.4min 8.5min 10.5min 0 transport_latency_assumed market_resolved h 2,643 83 21ms 92ms 47.6s 51.3s 0 transport_latency_assumed market_resolved i 3,256 97 27ms 8.9min 12.3min 12.5min 0 transport_latency_assumed market_resolved k 7,000 5,120 9.7min 26.3min 37.2min 38.0min 0 transport_latency_assumed market_resolved m 2,643 2,436 6ms 63ms 47.8s 55.3s 0 transport_latency_assumed new_market g 2,445 485 455ms 1.3min 5.6min 5.7min 0 transport_latency_assumed new_market h 2,394 707 232ms 57.6s 1.5min 1.7min 0 transport_latency_assumed new_market i 2,550 565 219ms 1.4min 6.0min 9.2min 0 transport_latency_assumed new_market k 7,665 5,132 9.6min 30.7min 32.8min 32.9min 0 transport_latency_assumed new_market m 2,394 1,664 88ms 54.0s 1.5min 1.7min 0 transport_latency_assumed price_change g 115,125,178 30,918 81ms 165ms 1.8s 29.0s 0 transport_latency_assumed price_change h 127,511,275 2,521,776 19ms 39ms 644ms 59.7s 0 transport_latency_assumed price_change i 121,412,169 1,501,611 22ms 40ms 372ms 44.8s 0 transport_latency_assumed price_change k 100,228,122 5,966,448 14ms 32ms 312ms 46.3s 0 transport_latency_assumed price_change m 127,516,321 117,610,121 5ms 17ms 174ms 7.5s 0 transport_latency_assumed tick_size_change g 7,064 4 80ms 146ms 559ms 3.5s 0 transport_latency_assumed tick_size_change h 7,520 178 19ms 35ms 552ms 11.9s 0 transport_latency_assumed tick_size_change i 7,208 77 22ms 43ms 336ms 8.5s 0 transport_latency_assumed tick_size_change k 5,980 265 15ms 42ms 197ms 4.6s 0 transport_latency_assumed tick_size_change m 7,520 6,996 5ms 16ms 76ms 259ms 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/16/2026-10-03T16.parquet sha256sum 2026-10-03T16.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.