Hour audit: 2026-09-21T12
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-21T12 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-21T12:00:00.000033729+00:00 · last event 2026-09-21T12:59:59.999443384+00:00
VOLUME 120,502,517 rows · 1,306,996,072 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 118,722,345 · e: 118,145,103 · f: 114,127,659 · c: 102,851,339 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 23,486,324 (19.49%) · e: 1,738,041 (1.44%) · f: 858,568 (0.71%) · c: 94,419,584 (78.35%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: g
INTEGRITY sha256 90d28202ecc4eeccc0fb7492529c832680e9ae6e73e38d782ebbb7ba023387eb
the corpus checksum ledger names this file with the same digest
joined 120,506,007 to merged 120,502,517, minus 3,490 (minus 0.0029%)
boundary drops 3,490 · 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-21T14:00:03Z 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 12,024,638 138,974,834 0-45 f57c39e9a76259adeb1fd45938290edece4be1c1a2fee17fb4ddb4635257c85e book 1,823,137 87,531,762 46-52 eb1bc2d540eb1264735e4acf8c005e0aa7b77a63a609b64703b67c18f0ad333f last_trade_price 62,412 3,504,481 53-53 4c68e53d934a5a162a111a4d36c52150a1c0e8b03181fe6e314940116ec7d202 market_resolved 831 116,922 54-54 3e164b3fcc7be96442618159419c5a0809fa00dcab284f19a42995000b9128fa new_market 7,236 700,237 55-55 6e8c00fa767d92340aa1d4c2a2b214b1dad94b275472b8f539a0d0b8b9ef816b price_change 106,580,659 1,074,671,753 56-462 8b91df9ca3fa3c2d2460310e8cf119c163b7a757b09f03a7e3f2f60178f9ee9b tick_size_change 3,604 129,213 463-463 00b1e31c65ede7e4047f553f0c1a04362e77d4bf8c03598db1879b51c2541e49 EVENT MIX count share price_change 106,580,659 88.45% best_bid_ask 12,024,638 9.98% book 1,823,137 1.51% last_trade_price 62,412 0.05% new_market 7,236 <0.01% tick_size_change 3,604 <0.01% market_resolved 831 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,024,790 12,024,638 152 71,758 PARTIAL book 1,825,683 1,823,137 2,546 155,038 PARTIAL last_trade_price 62,412 62,412 0 3,435 PARTIAL market_resolved 831 831 0 708 PARTIAL new_market 7,236 7,236 0 4,500 PARTIAL price_change 106,581,451 106,580,659 792 119,283 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 10,300,273 9,500,372 6ms 25ms 217ms 5.0s 0 transport_latency_assumed best_bid_ask e 12,005,075 151,955 41ms 82ms 445ms 28.7s 0 transport_latency_assumed best_bid_ask f 11,643,170 55,499 49ms 96ms 473ms 25.2s 0 transport_latency_assumed best_bid_ask h 12,015,201 2,316,812 19ms 44ms 454ms 31.2s 0 transport_latency_assumed book c 1,411,882 1,258,586 6.4min 3.7d 44.8d 114.6d 0 book_staleness book e 465,326 186,757 1.5min 1.9d 40.7d 114.6d 0 book_staleness book f 724,352 280,801 4.0min 2.9d 43.8d 114.6d 0 book_staleness book h 265,996 96,993 1.2s 4.7h 30.0d 114.6d 0 book_staleness last_trade_price c 54,246 49,852 7ms 40ms 245ms 3.1s 0 transport_latency_assumed last_trade_price e 59,773 652 59ms 1.6s 11.9s 23.7s 0 transport_latency_assumed last_trade_price f 57,148 296 69ms 1.5s 12.1s 25.1s 0 transport_latency_assumed last_trade_price h 62,321 11,612 21ms 114ms 792ms 8.2s 0 transport_latency_assumed market_resolved c 706 533 8ms 44.8s 7.2min 8.5min 0 transport_latency_assumed market_resolved e 708 135 44ms 23.3s 1.0min 1.2min 0 transport_latency_assumed market_resolved f 725 60 57ms 40.7s 4.6min 4.6min 0 transport_latency_assumed market_resolved h 708 103 21ms 20.2s 59.3s 59.8s 0 transport_latency_assumed new_market c 4,782 3,344 103ms 2.0min 4.7min 1.1h 0 transport_latency_assumed new_market e 4,497 997 226ms 26.4s 56.0s 1.4min 0 transport_latency_assumed new_market f 4,497 1,030 225ms 28.3s 59.3s 1.7min 0 transport_latency_assumed new_market h 4,497 1,865 157ms 27.3s 51.5s 1.7min 0 transport_latency_assumed price_change c 91,076,314 83,603,951 6ms 30ms 227ms 5.5s 0 transport_latency_assumed price_change e 105,606,124 1,397,511 42ms 152ms 4.5s 28.8s 0 transport_latency_assumed price_change f 101,694,375 520,872 50ms 167ms 4.4s 25.2s 0 transport_latency_assumed price_change h 106,370,018 21,058,325 19ms 54ms 598ms 31.2s 0 transport_latency_assumed tick_size_change c 3,136 2,946 6ms 24ms 243ms 285ms 0 transport_latency_assumed tick_size_change e 3,600 34 41ms 65ms 339ms 774ms 0 transport_latency_assumed tick_size_change f 3,392 10 49ms 129ms 444ms 850ms 0 transport_latency_assumed tick_size_change h 3,604 614 19ms 40ms 460ms 5.4s 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/12/2026-09-21T12.parquet sha256sum 2026-09-21T12.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.