Hour audit: 2026-09-07T09
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-07T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T09:00:00.000087875+00:00 · last event 2026-09-07T09:59:59.999987349+00:00
VOLUME 93,230,608 rows · 944,364,414 bytes (900.62 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 93,074,087 · f: 92,909,465 · c: 92,870,169 · h: 92,839,425 · e: 92,830,749 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 177,106 (0.19%) · f: 188,342 (0.20%) · c: 90,283,400 (96.84%) · h: 2,372,062 (2.54%) · e: 209,698 (0.22%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 93,230,608 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 3ca19afbd1630b89cabaf060df6fd671136b6cf821cba3b6867b2476b01b1dff
the corpus checksum ledger names this file with the same digest
joined 93,232,451 to merged 93,230,608, minus 1,843 (minus 0.0020%)
boundary drops 1,843 · 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-07T10:54:43Z as cefgh
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 9,274,384 100,116,389 0-35 a4db99faaf73207b12a07520443879537238f942e7f58ca0d93aa917d8af2f14 book 322,110 32,428,662 36-37 3b489a8362cfe19d9a02ccbccbb73fab13195785105b39e0e02ec2f2f1ba4840 last_trade_price 49,798 2,859,322 38-38 fea37b1269351e52180f2cc21946ba7a55e85a51f18479ec2a147afe540d1015 market_resolved 576 89,766 39-39 5ac11fcbc69b6bbbfa942553933469f3590c9dd43e7013922ce53254329cd557 new_market 1,906 184,688 40-40 f9b20f90e478a321a83903118fa6a6ef2881ebe1546377b8a9d902b82434b0af price_change 83,579,642 807,540,421 41-359 316122688e96ce128077ad4983e3d881ea7b4d5b16a7f9c6e4d154cd136d606b tick_size_change 2,192 80,032 360-360 040f35a38f1813cd3e6f13fe8d975fa57f7afeb0feae4c07fe0a2712d5c150a1 EVENT MIX count share price_change 83,579,642 89.65% best_bid_ask 9,274,384 9.95% book 322,110 0.35% last_trade_price 49,798 0.05% tick_size_change 2,192 <0.01% new_market 1,906 <0.01% market_resolved 576 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,274,581 9,274,384 197 472 FULL book 322,112 322,110 2 88,594 FULL last_trade_price 49,798 49,798 0 0 FULL market_resolved 576 576 0 0 FULL new_market 1,906 1,906 0 0 FULL price_change 83,581,286 83,579,642 1,644 1,223 FULL tick_size_change 2,192 2,192 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,272,854 9,028,046 5ms 8ms 85ms 3.5s 0 transport_latency_assumed best_bid_ask e 9,270,598 17,277 40ms 45ms 164ms 3.9s 0 transport_latency_assumed best_bid_ask f 9,270,562 11,514 43ms 48ms 168ms 2.5s 0 transport_latency_assumed best_bid_ask g 9,268,875 1,247 79ms 97ms 361ms 9.1s 0 transport_latency_assumed best_bid_ask h 9,272,136 216,300 18ms 22ms 134ms 28.2s 0 transport_latency_assumed book c 126,413 118,321 7ms 3.3min 7.7d 100.5d 0 book_staleness book e 120,862 16,041 42ms 1.0min 3.9d 82.0d 0 book_staleness book f 120,621 15,472 47ms 56.8s 2.4d 100.5d 0 book_staleness book g 267,090 158,877 27.8s 12.6h 29.8d 100.5d 0 book_staleness book h 114,844 13,399 22ms 1.9s 1.0d 81.9d 0 book_staleness last_trade_price c 49,752 47,961 10ms 37ms 187ms 4.9s 0 transport_latency_assumed last_trade_price e 49,727 123 45ms 113ms 684ms 4.9s 0 transport_latency_assumed last_trade_price f 49,772 90 50ms 114ms 547ms 4.9s 0 transport_latency_assumed last_trade_price g 49,767 5 95ms 219ms 1.3s 6.9s 0 transport_latency_assumed last_trade_price h 49,774 1,619 23ms 55ms 335ms 8.1s 0 transport_latency_assumed market_resolved c 545 534 5ms 10ms 50ms 454ms 0 transport_latency_assumed market_resolved e 545 32 41ms 327ms 56.5s 57.0s 0 transport_latency_assumed market_resolved f 545 not meas. 45ms 331ms 56.5s 57.0s 0 transport_latency_assumed market_resolved g 545 not meas. 83ms 368ms 865ms 1.2s 0 transport_latency_assumed market_resolved h 545 10 18ms 113ms 57.0s 57.7s 0 transport_latency_assumed new_market c 1,217 835 92ms 19.2s 58.0s 25.6min 0 transport_latency_assumed new_market e 1,217 265 166ms 20.0s 26.8s 32.0min 0 transport_latency_assumed new_market f 1,217 93 197ms 19.3s 26.6s 57.6min 0 transport_latency_assumed new_market g 1,217 257 267ms 20.3s 26.6s 4.6min 0 transport_latency_assumed new_market h 1,217 456 128ms 18.8s 43.3s 32.0min 0 transport_latency_assumed price_change c 83,417,196 81,085,590 5ms 9ms 101ms 6.0s 0 transport_latency_assumed price_change e 83,385,608 175,960 40ms 47ms 215ms 3.9s 0 transport_latency_assumed price_change f 83,464,556 161,169 44ms 51ms 219ms 2.5s 0 transport_latency_assumed price_change g 83,484,401 16,720 80ms 100ms 462ms 9.2s 0 transport_latency_assumed price_change h 83,398,717 2,140,203 18ms 23ms 162ms 29.7s 0 transport_latency_assumed tick_size_change c 2,192 2,113 5ms 9ms 127ms 183ms 0 transport_latency_assumed tick_size_change e 2,192 not meas. 40ms 45ms 120ms 306ms 0 transport_latency_assumed tick_size_change f 2,192 4 44ms 49ms 129ms 189ms 0 transport_latency_assumed tick_size_change g 2,192 not meas. 80ms 94ms 264ms 631ms 0 transport_latency_assumed tick_size_change h 2,192 75 18ms 21ms 48ms 968ms 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-07/09/2026-09-07T09.parquet sha256sum 2026-09-07T09.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.