Hour audit: 2026-09-01T16
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 4 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 3 machines rather than 4.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-01T16 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T16:00:00.035422244+00:00 · last event 2026-09-01T16:59:59.999982560+00:00
VOLUME 100,534,842 rows · 1,002,394,863 bytes (955.96 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 100,445,798 · h: 100,416,529 · e: 99,460,687 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 58,466 (0.06%) · h: 1,016,960 (1.01%) · e: 99,459,416 (98.93%) (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 100,534,842 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 fb613d53295a2343fa2da3d8ab6b83782aac6ecb0afcb1ffd12dea69c716dafe
the corpus checksum ledger names this file with the same digest
joined 100,536,189 to merged 100,534,842, minus 1,347 (minus 0.0013%)
boundary drops 1,347 · 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-01T21:49:08Z as ceh
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 8,441,560 94,102,015 0-32 43187dc78d31c34c2b356f7228797f6ff329fdff736d015af77074c5733fa068 book 294,999 29,961,316 33-34 161a9280636dec7c27684c82cc987412f6003ce44f5a8b8094ed93557ff6d561 last_trade_price 82,536 4,510,079 35-35 20ff72da7dd42cdce764feaa2bf5eafab6c59edfde09b337b4d1968024c8d262 market_resolved 1,312 212,310 36-36 8bfa85044c93def964eda95aa32f20db3cc81838885c2ce940140cf728bd4206 new_market 3,181 339,994 37-37 557284b7ae499f1f57c39caf816fcd209015af05ccd8e6e00b5b93002007b4cb price_change 91,707,516 871,991,369 38-387 54edcdb37a171696fb6338b4df56445792cb6c17fbedfd5e04eda9f53ecbd3c6 tick_size_change 3,738 132,581 388-388 ff6efd47ebd0853be19e9d13c8ffa76967979efe0f96bf57cfc73473ca6d1ea4 EVENT MIX count share price_change 91,707,516 91.22% best_bid_ask 8,441,560 8.40% book 294,999 0.29% last_trade_price 82,536 0.08% tick_size_change 3,738 <0.01% new_market 3,181 <0.01% market_resolved 1,312 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,441,641 8,441,560 81 71,399 PARTIAL book 295,175 294,999 176 57,518 PARTIAL last_trade_price 82,536 82,536 0 3,981 PARTIAL market_resolved 1,312 1,312 0 1,291 PARTIAL new_market 3,181 3,181 0 2,218 PARTIAL price_change 91,708,606 91,707,516 1,090 128,538 PARTIAL tick_size_change 3,738 3,738 0 934 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,441,038 776 2ms 6ms 160ms 3.0s 0 transport_latency_assumed best_bid_ask e 8,415,786 8,415,705 44ms 172ms 1.9s 1.1min 0 transport_latency_assumed best_bid_ask h 8,440,304 25,079 18ms 31ms 235ms 7.5s 0 transport_latency_assumed book c 216,496 40,228 6ms 3.9min 10.1d 94.8d 0 book_staleness book e 215,739 215,639 235ms 7.7min 17.1d 94.7d 0 book_staleness book h 204,167 39,132 34ms 1.4min 10.1d 76.7d 0 book_staleness last_trade_price c 82,515 6 7ms 38ms 226ms 5.0s 0 transport_latency_assumed last_trade_price e 78,350 78,350 98ms 4.7s 17.9s 1.1min 0 transport_latency_assumed last_trade_price h 82,497 4,180 26ms 186ms 1.3s 5.3s 0 transport_latency_assumed market_resolved c 1,291 10 2ms 27ms 57.4s 1.0min 0 transport_latency_assumed market_resolved e 1,290 1,290 113ms 1.1s 59.0s 1.0min 0 transport_latency_assumed market_resolved h 1,291 12 20ms 188ms 58.5s 60.0s 0 transport_latency_assumed new_market c 2,218 304 61ms 33.1s 1.7min 2.0min 0 transport_latency_assumed new_market e 2,218 2,218 236ms 36.7s 1.6min 1.9min 0 transport_latency_assumed new_market h 2,218 659 112ms 40.4s 1.6min 2.0min 0 transport_latency_assumed price_change c 91,698,502 17,142 2ms 7ms 188ms 3.5s 0 transport_latency_assumed price_change e 90,743,578 90,742,488 45ms 208ms 8.7s 1.2min 0 transport_latency_assumed price_change h 91,682,314 947,886 18ms 37ms 339ms 9.6s 0 transport_latency_assumed tick_size_change c 3,738 not meas. 2ms 9ms 366ms 746ms 0 transport_latency_assumed tick_size_change e 3,726 3,726 45ms 171ms 913ms 12.6s 0 transport_latency_assumed tick_size_change h 3,738 12 18ms 32ms 457ms 2.9s 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-01/16/2026-09-01T16.parquet sha256sum 2026-09-01T16.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.