Hour audit: 2026-09-21T18
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: g. 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-21T18 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T18:00:00.000040844+00:00 · last event 2026-09-21T18:59:59.999924692+00:00
VOLUME 105,401,734 rows · 1,133,547,716 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 103,856,510 · f: 103,664,777 · e: 103,156,953 · c: 89,005,741 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 21,515,184 (20.41%) · f: 629,296 (0.60%) · e: 1,215,112 (1.15%) · c: 82,042,142 (77.84%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 ddc6866d61ca25b4302041292f1f2deb3b5993f87c096d1668d76f265e00c923
the corpus checksum ledger names this file with the same digest
joined 105,419,410 to merged 105,401,734, minus 17,676 (minus 0.0168%)
boundary drops 17,676 · 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-21T19:53:46Z as cefh
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 10,008,628 115,718,615 0-38 6139623ab8ef0b063cab3ae7e63733616dd8e598356cd035a1d72c4dac568024 book 1,519,587 73,186,208 39-44 b15e787f3bc7dcd6e2f465c486ff99e8708ad0ec150dd8061561146aa6531076 last_trade_price 60,360 3,367,344 45-45 241386e5bec2f0fdbff90232ae26d95c85e448880c4c620fd7b70c56be04b347 market_resolved 1,057 132,009 46-46 bf563ec846bec786d1c58eca6b7f77a98e20cff3664e11bdf4082139d5997115 new_market 4,402 436,290 47-47 f89e4b451620928b8b84e4a55fe92aa614726c88ee02385cc94cbb9599ce26e8 price_change 93,804,172 939,378,891 48-405 1d009ae38f78c0a8228efdc2ec37e114239ff7d04cbb6870ab1431a4c4299bdf tick_size_change 3,528 128,896 406-406 03fb377467eb725984a4421fcaea2afeb4ff0df5e43778904142834b9514e6d3 EVENT MIX count share price_change 93,804,172 89.00% best_bid_ask 10,008,628 9.50% book 1,519,587 1.44% last_trade_price 60,360 0.06% new_market 4,402 <0.01% tick_size_change 3,528 <0.01% market_resolved 1,057 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,008,721 10,008,628 93 71,017 PARTIAL book 1,535,917 1,519,587 16,330 158,984 PARTIAL last_trade_price 60,360 60,360 0 3,308 PARTIAL market_resolved 1,058 1,057 1 806 PARTIAL new_market 4,410 4,402 8 2,871 PARTIAL price_change 93,805,416 93,804,172 1,244 123,347 PARTIAL tick_size_change 3,528 3,528 0 882 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,382,314 7,757,651 6ms 20ms 148ms 3.6s 0 transport_latency_assumed best_bid_ask e 9,989,964 112,606 41ms 68ms 389ms 17.7s 0 transport_latency_assumed best_bid_ask f 10,002,419 50,808 48ms 73ms 330ms 18.1s 0 transport_latency_assumed best_bid_ask h 10,004,113 2,087,563 19ms 34ms 236ms 12.1s 0 transport_latency_assumed book c 1,473,005 1,432,574 7.7min 3.1d 44.2d 114.9d 0 book_staleness book e 196,749 34,820 487ms 28.4min 30.2d 114.8d 0 book_staleness book f 148,254 12,241 82ms 3.6min 14.3d 96.3d 0 book_staleness book h 152,559 39,952 25ms 5.8min 14.3d 114.8d 0 book_staleness last_trade_price c 51,171 46,557 7ms 36ms 224ms 1.1s 0 transport_latency_assumed last_trade_price e 57,614 634 53ms 1.5s 9.6s 17.7s 0 transport_latency_assumed last_trade_price f 59,353 425 60ms 1.2s 7.9s 18.1s 0 transport_latency_assumed last_trade_price h 59,869 12,744 20ms 78ms 411ms 7.8s 0 transport_latency_assumed market_resolved c 923 766 30ms 5.7min 9.0min 9.3min 0 transport_latency_assumed market_resolved e 708 8 46ms 46.2s 56.1s 59.0s 0 transport_latency_assumed market_resolved f 708 3 53ms 46.2s 56.1s 59.0s 0 transport_latency_assumed market_resolved h 708 280 23ms 43.2s 53.0s 55.6s 0 transport_latency_assumed new_market c 2,926 1,896 75ms 1.7min 5.7min 6.2min 0 transport_latency_assumed new_market e 2,863 683 160ms 59.4s 1.9min 2.9min 0 transport_latency_assumed new_market f 2,863 648 170ms 45.5s 2.0min 2.6min 0 transport_latency_assumed new_market h 2,863 1,175 102ms 54.6s 2.0min 2.7min 0 transport_latency_assumed price_change c 79,092,362 72,799,835 6ms 24ms 176ms 3.8s 0 transport_latency_assumed price_change e 92,905,527 1,066,334 42ms 113ms 3.9s 17.8s 0 transport_latency_assumed price_change f 93,447,652 565,148 48ms 109ms 2.6s 18.2s 0 transport_latency_assumed price_change h 93,632,870 19,372,855 19ms 41ms 327ms 12.1s 0 transport_latency_assumed tick_size_change c 3,040 2,863 6ms 15ms 118ms 177ms 0 transport_latency_assumed tick_size_change e 3,528 27 42ms 83ms 210ms 303ms 0 transport_latency_assumed tick_size_change f 3,528 23 48ms 69ms 192ms 629ms 0 transport_latency_assumed tick_size_change h 3,528 615 19ms 35ms 104ms 531ms 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-21/18/2026-09-21T18.parquet sha256sum 2026-09-21T18.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.