Hour audit: 2026-09-01T11
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-01T11 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T11:00:00.038107978+00:00 · last event 2026-09-01T11:59:59.999996400+00:00
VOLUME 89,810,499 rows · 909,961,515 bytes (867.81 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 89,528,444 · h: 89,471,139 · e: 88,927,389 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 140,138 (0.16%) · h: 744,138 (0.83%) · e: 88,926,223 (99.02%) (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 89,810,499 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 ca10c9b6f44fc3a3bab3ab204d8b3da47366ef04a8203821500392fb5f97e5be
the corpus checksum ledger names this file with the same digest
joined 89,811,669 to merged 89,810,499, minus 1,170 (minus 0.0013%)
boundary drops 1,170 · 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-01T14:41:29Z 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 7,166,229 80,476,362 0-27 6fc23561d2d14c83c671e718eea7b588c973345f4b85b4a35c100a684200aed6 book 602,542 55,890,993 28-30 efa906448ca4de60ec111469297692562f982c90f9b6bbd8ffcac8e626f31bef last_trade_price 62,117 3,484,273 31-31 5bbf4beb49f076dccf3f45e2b71c167a4554126f35715360ce6f2254002837b4 market_resolved 956 156,655 32-32 68db023c1e21b271a05a6a1905eababcd182d4d9dcb4074883578615f32783a3 new_market 805 94,247 33-33 a70da0495c265b42cd853775a4e0a71e534f82c6dfe9985d8e120d122def13d0 price_change 81,975,014 768,730,105 34-346 81946518194a50c48a279e546a7ce823bb4899659493f76e84819966c5e30af4 tick_size_change 2,836 103,854 347-347 cc774c04d88d311b1fd149876192434917a3e6faf3b967e72b889caaf25579fb EVENT MIX count share price_change 81,975,014 91.28% best_bid_ask 7,166,229 7.98% book 602,542 0.67% last_trade_price 62,117 0.07% tick_size_change 2,836 <0.01% market_resolved 956 <0.01% new_market 805 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,166,301 7,166,229 72 68,008 PARTIAL book 602,546 602,542 4 161,570 PARTIAL last_trade_price 62,117 62,117 0 3,301 PARTIAL market_resolved 956 956 0 956 PARTIAL new_market 805 805 0 610 PARTIAL price_change 81,976,108 81,975,014 1,094 125,711 PARTIAL tick_size_change 2,836 2,836 0 709 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,165,560 771 4ms 7ms 64ms 6.2s 0 transport_latency_assumed best_bid_ask e 7,142,036 7,141,964 42ms 92ms 1.2s 34.5s 0 transport_latency_assumed best_bid_ask h 7,164,232 23,494 18ms 27ms 226ms 7.6s 0 transport_latency_assumed book c 334,827 122,358 29.1s 3.7h 24.0d 94.6d 0 book_staleness book e 351,697 351,693 40.9s 4.6h 23.9d 94.6d 0 book_staleness book h 300,999 128,491 15.8s 3.2h 23.9d 94.6d 0 book_staleness last_trade_price c 62,091 88 9ms 42ms 243ms 5.0s 0 transport_latency_assumed last_trade_price e 58,460 58,460 89ms 4.7s 15.4s 34.0s 0 transport_latency_assumed last_trade_price h 61,952 3,569 29ms 505ms 2.5s 5.7s 0 transport_latency_assumed market_resolved c 956 not meas. 4ms 6ms 86ms 643ms 0 transport_latency_assumed market_resolved e 956 956 42ms 192ms 771ms 1.3s 0 transport_latency_assumed market_resolved h 956 not meas. 19ms 66ms 224ms 885ms 0 transport_latency_assumed new_market c 610 69 62ms 27.8s 1.3min 1.4min 0 transport_latency_assumed new_market e 610 610 232ms 20.7s 1.3min 1.3min 0 transport_latency_assumed new_market h 610 126 150ms 54.3s 1.4min 1.4min 0 transport_latency_assumed price_change c 81,961,564 16,852 4ms 7ms 88ms 6.2s 0 transport_latency_assumed price_change e 81,370,794 81,369,704 43ms 132ms 5.1s 34.5s 0 transport_latency_assumed price_change h 81,939,554 588,458 19ms 32ms 388ms 7.6s 0 transport_latency_assumed tick_size_change c 2,836 not meas. 4ms 7ms 46ms 251ms 0 transport_latency_assumed tick_size_change e 2,836 2,836 42ms 104ms 371ms 540ms 0 transport_latency_assumed tick_size_change h 2,836 not meas. 19ms 26ms 80ms 1.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-01/11/2026-09-01T11.parquet sha256sum 2026-09-01T11.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.