Hour audit: 2026-10-01T23
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-01T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T23:00:00.000001680+00:00 · last event 2026-10-01T23:59:59.999842754+00:00
VOLUME 104,408,591 rows · 1,077,077,933 bytes (1.00 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 103,941,537 · h: 103,789,751 · k: 103,741,903 · m: 103,730,567 · g: 103,723,442 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 449,066 (0.43%) · h: 399,388 (0.38%) · k: 1,611,979 (1.54%) · m: 101,765,780 (97.47%) · g: 182,378 (0.17%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 104,408,591 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e5b80931fe0f554c7a338e84529680225659c73626885b7662de16528631027c
the corpus checksum ledger names this file with the same digest
joined 104,412,510 to merged 104,408,591, minus 3,919 (minus 0.0038%)
boundary drops 3,919 · 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-02T01:45:13Z 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,368,171 106,348,067 0-35 8c6e70dd4249b6ad6a85246ba6f55e5f6d278f21865913551962cb5d07a5b0a1 book 936,929 73,399,866 36-39 57512f2b37c4b8f76bf4cb5406b5585e055673a15033a8eef300826c01434cfe last_trade_price 58,264 3,182,988 40-40 3e0e284777c022398a8797a3206f584f7d270f85cc51d675e7fa837f82ca51d0 market_resolved 1,739 265,090 41-41 b125a4cc7af1319c5c076319c59e57866a66bd4c7d509988a966269768e5fd37 new_market 1,250 121,093 42-42 df127ab78295c27956f13d0b078ab50b5c929fa53b5691d781950b6487fbebf9 price_change 94,039,770 892,478,859 43-401 4cb9ea2b1010369d19c99aeb21e631138961c235bcf554d0aec28173329dc227 tick_size_change 2,468 90,889 402-402 4f7b8a728f1b7c18c8cb1c16d03fe89a4e6b4a4513087c521fb506da29e31ad9 EVENT MIX count share price_change 94,039,770 90.07% best_bid_ask 9,368,171 8.97% book 936,929 0.90% last_trade_price 58,264 0.06% tick_size_change 2,468 <0.01% market_resolved 1,739 <0.01% new_market 1,250 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,368,310 9,368,171 139 153 FULL book 939,271 936,929 2,342 218,558 FULL last_trade_price 58,264 58,264 0 0 FULL market_resolved 1,739 1,739 0 0 FULL new_market 1,250 1,250 0 0 FULL price_change 94,041,208 94,039,770 1,438 79 FULL tick_size_change 2,468 2,468 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,364,259 1,689 76ms 90ms 204ms 16.0s 0 transport_latency_assumed best_bid_ask h 9,365,927 23,157 19ms 31ms 155ms 46.3s 0 transport_latency_assumed best_bid_ask i 9,364,822 10,237 35ms 48ms 78ms 13.3s 0 transport_latency_assumed best_bid_ask k 9,366,289 139,142 13ms 19ms 118ms 34.1s 0 transport_latency_assumed best_bid_ask m 9,367,039 9,193,946 5ms 7ms 31ms 4.0s 0 transport_latency_assumed book g 373,483 162,290 3.2min 2.4d 40.4d 125.1d 0 book_staleness book h 339,075 129,495 2.0min 2.3d 40.4d 125.1d 0 book_staleness book i 509,233 333,593 9.3min 2.9d 40.4d 125.1d 0 book_staleness book k 302,515 103,698 1.0min 1.6d 40.4d 125.0d 0 book_staleness book m 284,553 207,853 41.3s 1.3d 40.4d 125.1d 0 book_staleness last_trade_price g 58,146 11 76ms 103ms 508ms 15.7s 0 transport_latency_assumed last_trade_price h 58,220 153 21ms 32ms 212ms 32.3s 0 transport_latency_assumed last_trade_price i 58,148 77 37ms 50ms 145ms 7.7s 0 transport_latency_assumed last_trade_price k 58,231 962 14ms 21ms 94ms 5.0s 0 transport_latency_assumed last_trade_price m 58,232 57,061 5ms 8ms 41ms 1.3s 0 transport_latency_assumed market_resolved g 1,671 not meas. 78ms 469ms 49.5s 49.6s 0 transport_latency_assumed market_resolved h 1,671 5 20ms 197ms 51.7s 53.7s 0 transport_latency_assumed market_resolved i 1,671 150 45ms 443ms 52.9s 55.5s 0 transport_latency_assumed market_resolved k 1,671 92 14ms 65ms 52.6s 52.7s 0 transport_latency_assumed market_resolved m 1,671 1,492 5ms 123ms 40.5s 56.5s 0 transport_latency_assumed new_market g 764 152 140ms 18.6s 26.5s 1.8min 0 transport_latency_assumed new_market h 764 240 199ms 20.3s 48.4s 1.7min 0 transport_latency_assumed new_market i 764 87 130ms 16.5s 26.4s 1.6min 0 transport_latency_assumed new_market k 764 126 140ms 16.3s 47.8s 1.7min 0 transport_latency_assumed new_market m 764 645 41ms 17.7s 45.4s 1.6min 0 transport_latency_assumed price_change g 93,922,651 18,236 76ms 93ms 303ms 16.6s 0 transport_latency_assumed price_change h 94,021,626 246,338 19ms 32ms 176ms 46.3s 0 transport_latency_assumed price_change i 94,004,431 104,922 36ms 48ms 101ms 13.7s 0 transport_latency_assumed price_change k 94,009,965 1,367,909 13ms 20ms 118ms 42.3s 0 transport_latency_assumed price_change m 94,015,840 92,302,365 5ms 8ms 33ms 4.2s 0 transport_latency_assumed tick_size_change g 2,468 not meas. 76ms 87ms 102ms 151ms 0 transport_latency_assumed tick_size_change h 2,468 not meas. 19ms 31ms 44ms 563ms 0 transport_latency_assumed tick_size_change i 2,468 not meas. 36ms 48ms 243ms 261ms 0 transport_latency_assumed tick_size_change k 2,468 50 13ms 18ms 38ms 122ms 0 transport_latency_assumed tick_size_change m 2,468 2,418 5ms 8ms 20ms 58ms 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/23/2026-10-01T23.parquet sha256sum 2026-10-01T23.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.