Hour audit: 2026-09-20T22
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-20T22 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-20T22:00:00.000027675+00:00 · last event 2026-09-20T22:59:59.999977717+00:00
VOLUME 133,554,006 rows · 1,460,817,249 bytes (1.36 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured e: 131,895,439 · h: 129,090,020 · f: 118,385,147 · c: 112,856,748 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,680,065 (1.26%) · h: 25,113,540 (18.80%) · f: 759,301 (0.57%) · c: 106,001,100 (79.37%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 1d33a7a5e23f169b81bcc96c069d4f88c1357e5d213dd7ad99d6074261c68953
the corpus checksum ledger names this file with the same digest
joined 133,555,467 to merged 133,554,006, minus 1,461 (minus 0.0011%)
boundary drops 1,461 · 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-21T04:22:36Z 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 13,697,820 155,144,698 0-52 44375f3693ccfcd8a5930753cfb904e9419573d5c16c4e3f330829f9cc835eac book 1,718,394 80,714,847 53-59 9fd217528bb939629054643e17be1c715dc8adf91a5c333dbf953b4a001acb80 last_trade_price 58,979 3,392,200 60-60 16cc5b40c7592d47cb1a696e6fd54852ea4a903607f0bdc95fbc3436a30f939c market_resolved 6,213 706,797 61-61 b2140ca441ad88dec1461d2da27044f16b3e2cdfbcabaa90fc2e631bfc98eecd new_market 802 79,753 62-62 9f245c0cebd7a0688a380cc3ae8b229636109cff0d3c3102ee8ca2bbaf6dfeba price_change 118,064,946 1,219,012,329 63-513 732a0f960b4b64bf45adfa00ae1c886191d85010e2781e99a16766c5fd8c1127 tick_size_change 6,852 249,271 514-514 9f087cb50eec5b5e6dedfb1075930b30acd3505398822bb78fa3caaaf6efa649 EVENT MIX count share price_change 118,064,946 88.40% best_bid_ask 13,697,820 10.26% book 1,718,394 1.29% last_trade_price 58,979 0.04% tick_size_change 6,852 <0.01% market_resolved 6,213 <0.01% new_market 802 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,698,028 13,697,820 208 75,415 PARTIAL book 1,718,402 1,718,394 8 162,810 PARTIAL last_trade_price 58,980 58,979 1 3,787 PARTIAL market_resolved 6,213 6,213 0 4,233 PARTIAL new_market 802 802 0 506 PARTIAL price_change 118,066,190 118,064,946 1,244 124,834 PARTIAL tick_size_change 6,852 6,852 0 1,713 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,566,212 10,897,458 5ms 15ms 112ms 1.6s 0 transport_latency_assumed best_bid_ask e 13,696,352 170,586 42ms 55ms 184ms 7.6s 0 transport_latency_assumed best_bid_ask f 12,193,376 40,319 46ms 62ms 194ms 8.3s 0 transport_latency_assumed best_bid_ask h 13,419,586 2,589,457 18ms 30ms 113ms 15.6s 0 transport_latency_assumed book c 1,389,513 1,364,173 7.9min 2.3d 43.3d 114.0d 0 book_staleness book e 121,903 3,908 44ms 386ms 20.4min 95.5d 0 book_staleness book f 1,067,549 327,092 7.0min 2.3d 43.3d 114.0d 0 book_staleness book h 117,696 23,221 21ms 59ms 1.8s 95.4d 0 book_staleness last_trade_price c 50,144 46,378 6ms 26ms 213ms 1.4s 0 transport_latency_assumed last_trade_price e 58,776 773 45ms 236ms 3.0s 7.6s 0 transport_latency_assumed last_trade_price f 52,288 261 49ms 267ms 5.9s 8.3s 0 transport_latency_assumed last_trade_price h 58,076 11,567 19ms 49ms 248ms 7.3s 0 transport_latency_assumed market_resolved c 5,194 5,004 6ms 9.7min 15.3min 15.8min 0 transport_latency_assumed market_resolved e 4,233 54 43ms 120ms 348ms 982ms 0 transport_latency_assumed market_resolved f 4,116 462 48ms 2.8min 5.0min 6.3min 0 transport_latency_assumed market_resolved h 4,155 693 19ms 56ms 584ms 2.4min 0 transport_latency_assumed new_market c 626 450 106ms 7.9min 4.4h 8.5h 0 transport_latency_assumed new_market e 504 93 192ms 12.4s 18.2s 19.3s 0 transport_latency_assumed new_market f 510 96 177ms 527ms 4.7h 8.7h 0 transport_latency_assumed new_market h 504 163 143ms 13.3s 18.9s 1.8h 0 transport_latency_assumed price_change c 99,839,495 93,682,302 5ms 18ms 127ms 2.5s 0 transport_latency_assumed price_change e 118,006,819 1,504,587 42ms 65ms 401ms 7.6s 0 transport_latency_assumed price_change f 105,061,068 391,048 46ms 72ms 453ms 8.4s 0 transport_latency_assumed price_change h 115,483,275 22,487,009 18ms 33ms 140ms 15.6s 0 transport_latency_assumed tick_size_change c 5,564 5,335 5ms 9ms 75ms 279ms 0 transport_latency_assumed tick_size_change e 6,852 64 41ms 47ms 105ms 208ms 0 transport_latency_assumed tick_size_change f 6,240 23 45ms 51ms 95ms 171ms 0 transport_latency_assumed tick_size_change h 6,728 1,430 18ms 23ms 59ms 291ms 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/22/2026-09-20T22.parquet sha256sum 2026-09-20T22.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.