Hour audit: 2026-09-20T06
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-20T06 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-20T06:00:00.000046125+00:00 · last event 2026-09-20T06:59:59.999923674+00:00
VOLUME 109,535,918 rows · 1,106,164,483 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES cegh — 4 machines contributed rows
captured c: 109,464,874 · h: 109,417,683 · g: 109,397,893 · e: 109,378,858 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 103,399,756 (94.40%) · h: 5,546,896 (5.06%) · g: 53,462 (0.05%) · e: 535,804 (0.49%) (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 109,535,918 rows exactly, so those pairs supplied none
5 expected (cefgh), 1 contributed nothing: f
INTEGRITY sha256 bd3f3cc923dc419ac9b7c56688ca14a99952af31fe617476a43f646a10f2158d
the corpus checksum ledger names this file with the same digest
joined 109,538,540 to merged 109,535,918, minus 2,622 (minus 0.0024%)
boundary drops 2,622 · 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-20T09:36:07Z 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 13,094,132 144,536,635 0-49 2ecd06d3a74890e218be1d9880ff9f163b091fe030cac09fb5f8f0d136f47961 book 144,305 15,535,984 50-50 850451e032f8370103d6af62f1c82e69679370644d8d2df5cecfbde25a60d80a last_trade_price 53,049 3,063,717 51-51 090ce0964df1b2aea6701aca25bcc894f8346f79a97e2927b5b861028dcfcf19 market_resolved 2,485 402,602 52-52 597160cb843b79fc2025bcec84aa13425129ba55da497964e65a99e6a187042c new_market 1,835 185,418 53-53 545a2acdadc5b49b3072f4c8e8abae1c4ce9e0aa8f05cacf93dc510c8b4c6ec8 price_change 96,236,508 941,063,586 54-421 cf29cd5ddfad3f683a058158911f44a76ecaf34b66e09e8baa19f9e60e54c448 tick_size_change 3,604 131,551 422-422 7cd24dd99bf21d6b3c49129e04d884ff15effbb4a9e8e68b48085d97426f8e44 EVENT MIX count share price_change 96,236,508 87.86% best_bid_ask 13,094,132 11.95% book 144,305 0.13% last_trade_price 53,049 0.05% tick_size_change 3,604 <0.01% market_resolved 2,485 <0.01% new_market 1,835 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,094,464 13,094,132 332 76,601 PARTIAL book 144,307 144,305 2 18,462 PARTIAL last_trade_price 53,049 53,049 0 3,777 PARTIAL market_resolved 2,485 2,485 0 2,461 PARTIAL new_market 1,835 1,835 0 1,220 PARTIAL price_change 96,238,796 96,236,508 2,288 138,361 PARTIAL tick_size_change 3,604 3,604 0 901 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 13,092,228 12,447,978 5ms 13ms 119ms 6.9s 0 transport_latency_assumed best_bid_ask e 13,090,914 54,348 40ms 50ms 198ms 5.5s 0 transport_latency_assumed best_bid_ask g 13,090,626 4,314 75ms 95ms 378ms 21.1s 0 transport_latency_assumed best_bid_ask h 13,091,939 587,492 18ms 28ms 170ms 14.3s 0 transport_latency_assumed book c 118,322 107,743 7ms 492ms 1.6d 94.8d 0 book_staleness book e 114,860 7,655 43ms 470ms 10.9h 113.3d 0 book_staleness book g 113,861 6,462 83ms 1.0s 5.2h 94.8d 0 book_staleness book h 122,791 22,445 21ms 26.7s 9.9d 94.8d 0 book_staleness last_trade_price c 52,777 48,622 6ms 28ms 242ms 1.5s 0 transport_latency_assumed last_trade_price e 52,619 515 43ms 132ms 1.9s 5.5s 0 transport_latency_assumed last_trade_price g 52,495 67 82ms 257ms 6.1s 21.1s 0 transport_latency_assumed last_trade_price h 52,776 3,845 19ms 51ms 319ms 6.7s 0 transport_latency_assumed market_resolved c 2,461 2,363 5ms 14ms 378ms 59.0s 0 transport_latency_assumed market_resolved e 2,461 32 43ms 187ms 1.1s 1.0min 0 transport_latency_assumed market_resolved g 2,461 14 83ms 240ms 706ms 2.6s 0 transport_latency_assumed market_resolved h 2,461 76 22ms 68ms 797ms 1.0min 0 transport_latency_assumed new_market c 1,220 813 94ms 24.7s 1.1min 2.4h 0 transport_latency_assumed new_market e 1,220 316 191ms 22.8s 1.1min 6.7h 0 transport_latency_assumed new_market g 1,220 184 284ms 24.8s 1.0min 8.6h 0 transport_latency_assumed new_market h 1,220 522 137ms 26.5s 1.2min 2.3h 0 transport_latency_assumed price_change c 96,194,262 90,788,728 5ms 16ms 140ms 7.7s 0 transport_latency_assumed price_change e 96,113,180 472,931 41ms 60ms 300ms 5.5s 0 transport_latency_assumed price_change g 96,133,626 42,421 76ms 109ms 668ms 21.2s 0 transport_latency_assumed price_change h 96,142,892 4,932,428 18ms 33ms 193ms 18.2s 0 transport_latency_assumed tick_size_change c 3,604 3,509 5ms 8ms 184ms 382ms 0 transport_latency_assumed tick_size_change e 3,604 7 41ms 50ms 341ms 564ms 0 transport_latency_assumed tick_size_change g 3,604 not meas. 76ms 92ms 587ms 1.3s 0 transport_latency_assumed tick_size_change h 3,604 88 18ms 25ms 349ms 4.2s 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/06/2026-09-20T06.parquet sha256sum 2026-09-20T06.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.