Hour audit: 2026-09-20T03
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, 1 contributed no rows: f. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-20T03 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-20T03:00:00.001091643+00:00 · last event 2026-09-20T03:59:59.999977699+00:00
VOLUME 135,611,919 rows · 1,454,173,130 bytes (1.35 GiB) · 7 products, all holding rows
WITNESSES cegh — 4 machines contributed rows
captured h: 133,842,670 · e: 133,834,957 · c: 123,442,031 · g: 110,519,079 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 15,098,785 (11.13%) · e: 1,591,160 (1.17%) · c: 117,556,354 (86.69%) · g: 1,365,620 (1.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 135,611,919 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: f
INTEGRITY sha256 0e93c56bbf3d5b169164b6ac4db99d252cf5d0e3f2923f7bce02559ed861d6ee
the corpus checksum ledger names this file with the same digest
joined 135,616,323 to merged 135,611,919, minus 4,404 (minus 0.0032%)
boundary drops 4,404 · 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-20T08:25:29Z as cegh
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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 16,520,138 181,191,266 0-63 6e7105b221a7551557ad8b8cd88fa10f0195ee45a06ac7400ff88ffd3334ff80 book 1,875,449 87,197,631 64-71 67ec5469fdaf129cec2fa5c327c2c32a30e60f2f23d4ac5fc091fb4c536c8b41 last_trade_price 60,539 3,409,405 72-72 ea926c648ef9dead2abe0738b1719361ad5617e071ac5981a4d16e4f24914a61 market_resolved 4,890 537,589 73-73 31e985fa2269f051859949f454b352470287506836e12f15d2572e4223c43aaf new_market 573 50,377 74-74 04e0487e7253718306ef2426581b05815b5276ab9845ca8194fcaea6cb31cb5c price_change 117,142,726 1,179,969,334 75-521 0267519ad0b1f42460f304cc05be7d027ce5c01c3bf4f47f400dbf006b53a61f tick_size_change 7,604 277,643 522-522 483a3d4be6e251c15cdb41a8b733fd21d8edcc327df8f3b727964831d2d1218e EVENT MIX count share price_change 117,142,726 86.38% best_bid_ask 16,520,138 12.18% book 1,875,449 1.38% last_trade_price 60,539 0.04% tick_size_change 7,604 <0.01% market_resolved 4,890 <0.01% new_market 573 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 16,520,368 16,520,138 230 80,125 PARTIAL book 1,875,471 1,875,449 22 180,857 PARTIAL last_trade_price 60,539 60,539 0 3,917 PARTIAL market_resolved 4,890 4,890 0 3,270 PARTIAL new_market 583 573 10 307 PARTIAL price_change 117,146,868 117,142,726 4,142 140,420 PARTIAL tick_size_change 7,604 7,604 0 1,901 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 15,135,202 14,505,414 4ms 10ms 70ms 2.6s 0 transport_latency_assumed best_bid_ask e 16,519,462 186,855 43ms 48ms 109ms 3.4s 0 transport_latency_assumed best_bid_ask g 13,563,562 2,401 78ms 91ms 183ms 7.9s 0 transport_latency_assumed best_bid_ask h 16,519,706 1,825,468 18ms 27ms 77ms 9.6s 0 transport_latency_assumed book c 894,977 516,882 4.9min 1.5d 39.4d 113.2d 0 book_staleness book e 122,988 2,934 44ms 71ms 14.0s 94.6d 0 book_staleness book g 1,608,151 1,340,731 7.3min 1.5d 41.5d 113.2d 0 book_staleness book h 122,048 14,902 20ms 42ms 202ms 94.7d 0 book_staleness last_trade_price c 55,764 52,286 5ms 15ms 120ms 1.3s 0 transport_latency_assumed last_trade_price e 60,481 922 44ms 75ms 241ms 2.3s 0 transport_latency_assumed last_trade_price g 47,042 4 78ms 123ms 328ms 7.9s 0 transport_latency_assumed last_trade_price h 60,491 7,327 19ms 36ms 124ms 8.9s 0 transport_latency_assumed market_resolved c 3,445 3,392 5ms 4.4min 11.1min 11.4min 0 transport_latency_assumed market_resolved e 3,152 12 98ms 127ms 315ms 40.6s 0 transport_latency_assumed market_resolved g 4,450 1,303 214ms 16.1min 20.0min 20.7min 0 transport_latency_assumed market_resolved h 3,152 183 34ms 60ms 117ms 25.6s 0 transport_latency_assumed new_market c 335 224 77ms 6.3min 3.3h 6.1h 0 transport_latency_assumed new_market e 281 60 130ms 14.8s 40.3s 5.1h 0 transport_latency_assumed new_market g 496 175 17.8s 16.1min 5.0h 6.1h 0 transport_latency_assumed new_market h 281 114 63ms 12.5s 38.4s 2.2h 0 transport_latency_assumed price_change c 107,345,488 102,471,540 5ms 11ms 78ms 2.6s 0 transport_latency_assumed price_change e 117,120,989 1,400,354 43ms 51ms 133ms 3.5s 0 transport_latency_assumed price_change g 95,289,602 21,006 78ms 92ms 223ms 8.0s 0 transport_latency_assumed price_change h 117,129,388 13,249,826 18ms 29ms 87ms 9.7s 0 transport_latency_assumed tick_size_change c 6,820 6,616 4ms 9ms 38ms 83ms 0 transport_latency_assumed tick_size_change e 7,604 23 43ms 47ms 101ms 239ms 0 transport_latency_assumed tick_size_change g 5,776 not meas. 77ms 89ms 134ms 459ms 0 transport_latency_assumed tick_size_change h 7,604 965 18ms 26ms 64ms 676ms 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-20/03/2026-09-20T03.parquet sha256sum 2026-09-20T03.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.