Hour audit: 2026-09-22T13
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-09-22T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T13:00:00.000018259+00:00 · last event 2026-09-22T13:59:59.999445983+00:00
VOLUME 122,600,029 rows · 1,385,276,930 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES cefhij — 6 machines contributed rows
captured h: 117,641,981 · f: 117,479,516 · e: 117,435,281 · i: 115,122,620 · c: 113,770,643 · j: 57,009,131 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 7,024,078 (5.73%) · f: 60,382 (0.05%) · e: 116,858 (0.10%) · i: 1,201,451 (0.98%) · c: 69,560,002 (56.74%) · j: 44,637,258 (36.41%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 122,600,029 rows exactly, so those pairs supplied none
6 expected, all 6 contributed
INTEGRITY sha256 b33757d0b968c45fe2b32b7ce0a3969863043ed24383a6fd76029b490a38075a
the corpus checksum ledger names this file with the same digest
joined 122,603,306 to merged 122,600,029, minus 3,277 (minus 0.0027%)
boundary drops 3,277 · 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-22T16:38:02Z as cefhij
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 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 11,251,838 134,303,446 0-42 a098b0eec992b76bdb9c86f1de18552e6f46bc7a2cbde745c5e2a8779ad6d24f book 5,034,345 124,116,957 43-62 619536699769dead900fb6b6758ca8674a4bd6816402c6712455ef2d97a2ece2 last_trade_price 69,176 3,933,559 63-63 4fdedb353115db994bb1f8a6e56c8c1cb949c49d480cb4145a7dcfc530f57890 market_resolved 4,453 173,120 64-64 a1d59754cd17f796319ff7559990efc004e6ac855600799ff3ccf0834414bd3e new_market 6,561 152,658 65-65 78e3f7668e7065985dd90652cd40036fdd0491df215aab08e53bf0583904cbd1 price_change 106,230,816 1,121,095,330 66-471 e94e1e0676242e2bd4f632cedbc53aa959e628def43810df062b84fbc7007caa tick_size_change 2,840 104,988 472-472 7db2efc9a66c8cdd8624d67cba73229bdbb86211de530c64c3dc22f87a74f309 EVENT MIX count share price_change 106,230,816 86.65% best_bid_ask 11,251,838 9.18% book 5,034,345 4.11% last_trade_price 69,176 0.06% new_market 6,561 <0.01% market_resolved 4,453 <0.01% tick_size_change 2,840 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,252,051 11,251,838 213 13,602 FULL book 5,034,699 5,034,345 354 174,413 FULL last_trade_price 69,178 69,176 2 1,540 FULL market_resolved 4,456 4,453 3 254 FULL new_market 6,594 6,561 33 203 FULL price_change 106,233,488 106,230,816 2,672 12,606 FULL tick_size_change 2,840 2,840 0 385 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,810,699 6,567,975 6ms 15ms 102ms 2.4s 0 transport_latency_assumed best_bid_ask e 11,245,620 8,209 41ms 56ms 229ms 33.3s 0 transport_latency_assumed best_bid_ask f 11,246,532 3,651 49ms 63ms 234ms 20.9s 0 transport_latency_assumed best_bid_ask h 11,250,291 667,655 19ms 27ms 105ms 18.0s 0 transport_latency_assumed best_bid_ask i 11,140,935 115,594 23ms 43ms 890ms 10.6s 0 transport_latency_assumed best_bid_ask j 5,024,340 3,888,754 2ms 11ms 73ms 2.9s 0 transport_latency_assumed book c 528,172 147,472 3.2min 2.0d 38.0d 115.6d 0 book_staleness book e 158,053 7,452 48ms 1.1min 10.8d 114.0d 0 book_staleness book f 155,513 6,694 55ms 21.4s 6.4d 107.9d 0 book_staleness book h 143,344 9,445 22ms 71ms 22.4min 97.1d 0 book_staleness book i 172,275 36,287 49ms 12.0min 1.9d 54.8d 0 book_staleness book j 4,864,977 4,826,995 11.0min 3.9d 44.8d 115.7d 0 book_staleness last_trade_price c 66,971 42,320 7ms 22ms 176ms 1.1s 0 transport_latency_assumed last_trade_price e 68,216 106 46ms 713ms 7.0s 33.2s 0 transport_latency_assumed last_trade_price f 68,143 56 54ms 639ms 8.5s 20.8s 0 transport_latency_assumed last_trade_price h 69,052 4,301 20ms 49ms 288ms 6.2s 0 transport_latency_assumed last_trade_price i 63,018 533 25ms 787ms 5.1s 10.3s 0 transport_latency_assumed last_trade_price j 30,282 21,860 4ms 18ms 133ms 1.1s 0 transport_latency_assumed market_resolved c 711 379 6ms 41.2s 5.8min 5.8min 0 transport_latency_assumed market_resolved e 710 34 44ms 31.2s 1.0min 1.0min 0 transport_latency_assumed market_resolved f 710 not meas. 52ms 31.0s 1.0min 1.0min 0 transport_latency_assumed market_resolved h 710 145 21ms 30.7s 1.0min 1.0min 0 transport_latency_assumed market_resolved i 686 7 24ms 40.1s 59.8s 59.9s 0 transport_latency_assumed market_resolved j 4,068 3,888 22.5min 56.1min 1.2h 1.2h 0 transport_latency_assumed new_market c 646 258 78ms 16.2s 4.5min 4.5min 0 transport_latency_assumed new_market e 622 55 158ms 12.0s 22.9s 31.6s 0 transport_latency_assumed new_market f 622 119 183ms 17.5s 23.2s 1.7min 0 transport_latency_assumed new_market h 622 138 112ms 17.0s 27.3s 1.6min 0 transport_latency_assumed new_market i 622 110 110ms 15.3s 25.6s 1.8min 0 transport_latency_assumed new_market j 6,341 5,881 21.7min 53.8min 1.1h 1.3h 0 transport_latency_assumed price_change c 102,360,684 62,799,906 6ms 17ms 117ms 2.7s 0 transport_latency_assumed price_change e 105,959,220 101,002 42ms 78ms 2.0s 33.5s 0 transport_latency_assumed price_change f 106,005,156 49,862 50ms 84ms 2.0s 21.0s 0 transport_latency_assumed price_change h 106,175,122 6,342,262 19ms 31ms 132ms 18.1s 0 transport_latency_assumed price_change i 103,742,268 1,048,902 24ms 69ms 2.3s 10.6s 0 transport_latency_assumed price_change j 47,077,803 35,888,882 3ms 12ms 87ms 4.7s 0 transport_latency_assumed tick_size_change c 2,760 1,692 6ms 11ms 59ms 243ms 0 transport_latency_assumed tick_size_change e 2,840 not meas. 41ms 69ms 174ms 1.4s 0 transport_latency_assumed tick_size_change f 2,840 not meas. 50ms 60ms 175ms 219ms 0 transport_latency_assumed tick_size_change h 2,840 132 19ms 29ms 59ms 106ms 0 transport_latency_assumed tick_size_change i 2,816 18 24ms 50ms 3.1s 3.2s 0 transport_latency_assumed tick_size_change j 1,320 998 2ms 10ms 49ms 84ms 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-22/13/2026-09-22T13.parquet sha256sum 2026-09-22T13.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.