Hour audit: 2026-09-26T00
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 2 contributed no rows: c, g. The hour is still whole on minutes; it simply rests on 3 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-26T00 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T00:00:00.000001490+00:00 · last event 2026-09-26T00:59:59.999117058+00:00
VOLUME 123,235,313 rows · 1,320,127,046 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES hik — 3 machines contributed rows
captured h: 122,122,437 · i: 115,799,425 · k: 111,797,415 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 13,862,409 (11.25%) · i: 10,958,052 (8.89%) · k: 98,414,852 (79.86%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 2 contributed nothing: c, g
INTEGRITY sha256 c3e574c78d9a324dda2ebef52d44e553cdb3946c18211dd5f69df4060f4bc533
the corpus checksum ledger names this file with the same digest
joined 123,238,125 to merged 123,235,313, minus 2,812 (minus 0.0023%)
boundary drops 2,812 · 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-09-26T02:38:58Z as hik
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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,419,132 139,473,873 0-47 d1ed72747492a5e3c44d6d5502475e6179670c01ecb4a5c4e209522a8d9f28b0 book 1,164,920 71,385,031 48-52 5695430e4e66cf327dd7420dd093b1a4251f57b3d34bd2469837f343e7894d43 last_trade_price 47,659 2,766,430 53-53 dff8da1af6607ecf9b06f77b5fbced8f13a387c98c79b571247e2fd0e9ee0d97 market_resolved 1,191 159,672 54-54 d0d88fc4b90e55a551d97269aa5057e564e82a1049022f7c282f640c0817a542 new_market 2,793 284,611 55-55 00bb5888b26de8b41ba4f5e03a08d6ae5f34f38f1c2842e78627bc58eff3cb52 price_change 109,594,246 1,104,458,467 56-474 95c4246f48b7e43e2f4aa407bfa856fd93adc6b606be6d9ef9a1fb2298be4abe tick_size_change 5,372 197,812 475-475 f1f5bbb4bcc94af4f09204a2b3a70bd7ecc29436d72dcd570663a3fd45acd2c8 EVENT MIX count share price_change 109,594,246 88.93% best_bid_ask 12,419,132 10.08% book 1,164,920 0.95% last_trade_price 47,659 0.04% tick_size_change 5,372 <0.01% new_market 2,793 <0.01% market_resolved 1,191 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,419,162 12,419,132 30 54,638 PARTIAL book 1,165,172 1,164,920 252 217,468 PARTIAL last_trade_price 47,659 47,659 0 3,452 PARTIAL market_resolved 1,191 1,191 0 979 PARTIAL new_market 2,793 2,793 0 1,834 PARTIAL price_change 109,596,776 109,594,246 2,530 91,875 PARTIAL tick_size_change 5,372 5,372 0 1,343 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,417,842 1,338,959 18ms 50ms 288ms 34.7s 0 transport_latency_assumed best_bid_ask i 11,828,149 1,009,344 20ms 27ms 114ms 2.1s 0 transport_latency_assumed best_bid_ask k 11,347,712 10,070,829 13ms 22ms 149ms 12.0s 0 transport_latency_assumed book h 101,917 13,248 24ms 200ms 13.8h 100.6d 0 book_staleness book i 719,878 376,614 1.2h 4.2d 36.2d 119.1d 0 book_staleness book k 987,972 775,058 1.6h 4.2d 41.4d 119.1d 0 book_staleness last_trade_price h 47,440 5,736 20ms 82ms 522ms 15.2s 0 transport_latency_assumed last_trade_price i 44,179 4,900 22ms 60ms 394ms 1.0s 0 transport_latency_assumed last_trade_price k 43,408 37,023 14ms 40ms 300ms 8.1s 0 transport_latency_assumed market_resolved h 979 127 19ms 16.6s 41.5s 47.9s 0 transport_latency_assumed market_resolved i 972 186 21ms 13.0s 4.5min 7.2min 0 transport_latency_assumed market_resolved k 1,091 878 15ms 6.0min 9.4min 11.3min 0 transport_latency_assumed new_market h 1,831 584 122ms 17.3s 2.3min 4.1min 0 transport_latency_assumed new_market i 1,937 1,078 92ms 4.4min 6.4min 19.9h 0 transport_latency_assumed new_market k 2,213 1,131 118ms 7.0min 19.4h 20.0h 0 transport_latency_assumed price_change h 109,547,056 12,503,220 18ms 55ms 322ms 34.9s 0 transport_latency_assumed price_change i 103,199,190 9,565,553 20ms 31ms 157ms 2.1s 0 transport_latency_assumed price_change k 99,409,843 87,525,473 13ms 24ms 159ms 12.0s 0 transport_latency_assumed tick_size_change h 5,372 535 18ms 53ms 239ms 3.5s 0 transport_latency_assumed tick_size_change i 5,120 377 20ms 36ms 113ms 332ms 0 transport_latency_assumed tick_size_change k 5,176 4,460 13ms 28ms 202ms 5.0s 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-09-26/00/2026-09-26T00.parquet sha256sum 2026-09-26T00.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.