Hour audit: 2026-10-01T01
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-01T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-01T01:00:00.000081552+00:00 · last event 2026-10-01T01:59:59.999997820+00:00
VOLUME 101,751,857 rows · 1,065,424,389 bytes (1016.07 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 92,221,595 · m: 91,656,729 · i: 89,770,987 · g: 87,359,740 · k: 86,076,643 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 5,263,609 (5.17%) · m: 76,426,209 (75.11%) · i: 4,243,271 (4.17%) · g: 50,167 (0.05%) · k: 15,768,601 (15.50%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 101,751,857 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2b9883c1a3cc8b75b21b760e69a544cc59e053f6de261f408dbbb68ec7b3f4d0
the corpus checksum ledger names this file with the same digest
joined 101,756,236 to merged 101,751,857, minus 4,379 (minus 0.0043%)
boundary drops 4,379 · 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-01T04:09:50Z 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,817,482 114,683,252 0-37 5807727edc5c7877e3cb156e9daa0db8e514636e68a57893e6e843e182bad8fd book 297,665 30,354,927 38-39 d9b14f0e6d55a0220273879f8441d46a8257b497437dbf449b355b55aed11c18 last_trade_price 56,020 3,103,641 40-40 4de49da6c645e54ba54e15de21001cd93e9a4ca44088e625fbb34d90b5b38431 market_resolved 579 91,385 41-41 8cdeaaa287e779c65adaac8bcd6c6cfdf9a926682d657949904f9f3c8077dfd8 new_market 435 48,377 42-42 ef1d828e8125340e8e34bcc2128f94b53e63a463dedd46bb03a5933d32a55e83 price_change 91,576,552 915,863,812 43-392 81357704d5b6377593e3bae58c025109c25e0997628225f6136228268ca82084 tick_size_change 3,124 115,823 393-393 103826e4475a5227423de68be97e0a1e660480b487ac9d621ce7de44346bcbc3 EVENT MIX count share price_change 91,576,552 90.00% best_bid_ask 9,817,482 9.65% book 297,665 0.29% last_trade_price 56,020 0.06% tick_size_change 3,124 <0.01% market_resolved 579 <0.01% new_market 435 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,817,666 9,817,482 184 93 FULL book 297,757 297,665 92 84,098 FULL last_trade_price 56,021 56,020 1 1 FULL market_resolved 579 579 0 0 FULL new_market 435 435 0 0 FULL price_change 91,580,654 91,576,552 4,102 66,050 FULL tick_size_change 3,124 3,124 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,816,438 469 80ms 97ms 189ms 13.3s 0 transport_latency_assumed best_bid_ask h 9,816,474 208,904 17ms 25ms 86ms 30.4s 0 transport_latency_assumed best_bid_ask i 9,817,016 240,331 19ms 50ms 100ms 4.9s 0 transport_latency_assumed best_bid_ask k 9,816,441 1,179,014 13ms 22ms 100ms 5.4s 0 transport_latency_assumed best_bid_ask m 9,817,366 8,188,764 5ms 19ms 71ms 1.3s 0 transport_latency_assumed book g 112,692 353 83ms 158ms 10.7s 13.2s 0 book_staleness book h 219,462 104,147 111ms 1.3d 36.3d 124.1d 0 book_staleness book i 118,527 7,626 22ms 83ms 1.2d 105.6d 0 book_staleness book k 197,168 90,568 31ms 20.8h 28.6d 105.7d 0 book_staleness book m 116,928 94,971 7ms 37ms 4.3h 102.6d 0 book_staleness last_trade_price g 55,990 24 83ms 173ms 10.7s 13.3s 0 transport_latency_assumed last_trade_price h 55,988 2,116 19ms 36ms 258ms 7.0s 0 transport_latency_assumed last_trade_price i 56,005 1,159 21ms 59ms 239ms 1.4s 0 transport_latency_assumed last_trade_price k 56,001 7,580 15ms 33ms 141ms 4.9s 0 transport_latency_assumed last_trade_price m 55,998 45,141 6ms 27ms 119ms 1.0s 0 transport_latency_assumed market_resolved g 560 not meas. 84ms 221ms 55.2s 55.2s 0 transport_latency_assumed market_resolved h 560 25 19ms 44ms 46.5s 46.6s 0 transport_latency_assumed market_resolved i 560 28 34ms 81ms 50.0s 50.0s 0 transport_latency_assumed market_resolved k 560 57 15ms 46ms 53.9s 54.0s 0 transport_latency_assumed market_resolved m 560 469 6ms 29ms 48.1s 48.2s 0 transport_latency_assumed new_market g 297 21 119ms 2.8s 14.2s 1.3min 0 transport_latency_assumed new_market h 297 68 48ms 9.5s 16.5s 1.6min 0 transport_latency_assumed new_market i 297 75 40ms 10.1s 1.4min 1.7min 0 transport_latency_assumed new_market k 297 56 54ms 299ms 12.3s 1.6min 0 transport_latency_assumed new_market m 297 215 27ms 7.4s 14.0s 1.4min 0 transport_latency_assumed price_change g 77,370,639 49,300 81ms 101ms 291ms 13.3s 0 transport_latency_assumed price_change h 82,125,690 4,948,262 18ms 28ms 121ms 30.4s 0 transport_latency_assumed price_change i 79,775,458 3,993,964 20ms 53ms 138ms 4.9s 0 transport_latency_assumed price_change k 76,003,052 14,490,962 14ms 25ms 117ms 5.7s 0 transport_latency_assumed price_change m 81,662,456 68,094,064 5ms 21ms 81ms 1.6s 0 transport_latency_assumed tick_size_change g 3,124 not meas. 81ms 105ms 180ms 8.5s 0 transport_latency_assumed tick_size_change h 3,124 87 18ms 34ms 155ms 234ms 0 transport_latency_assumed tick_size_change i 3,124 88 20ms 52ms 126ms 208ms 0 transport_latency_assumed tick_size_change k 3,124 364 13ms 27ms 121ms 182ms 0 transport_latency_assumed tick_size_change m 3,124 2,585 5ms 23ms 71ms 260ms 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/01/2026-10-01T01.parquet sha256sum 2026-10-01T01.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.