Hour audit: 2026-09-01T15
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-01T15 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T15:00:00.038247583+00:00 · last event 2026-09-01T15:59:59.999964523+00:00
VOLUME 98,869,166 rows · 996,936,275 bytes (950.75 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured h: 98,656,866 · c: 98,626,690 · e: 97,987,019 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 817,644 (0.83%) · c: 65,761 (0.07%) · e: 97,985,761 (99.11%) (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 98,869,166 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 be1140f147ee686857349081aaef160349a1e321c749e87f783689c68ca3a3cf
the corpus checksum ledger names this file with the same digest
joined 98,870,492 to merged 98,869,166, minus 1,326 (minus 0.0013%)
boundary drops 1,326 · 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:32:48Z 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,436,752 85,135,750 0-28 bb7bd52b940d354e98edce227474f0a897fa1fc47303489aeecf4dccf9925513 book 476,641 45,838,669 29-30 3c98e10b82d4b3c5951611a7f624f0cee1b3f55473ebaf346f3152e3d3e65f20 last_trade_price 81,720 4,456,811 31-31 3e134da9c56a714e7075b1e6b28a62a5d677dbc28c13a4b8694b56a98a865aa4 market_resolved 852 138,148 32-32 2a6e593aca84395612accf01388b6cb71f7e35bffcc2b4a263984e00469a88d4 new_market 597 65,830 33-33 9b8daf68ff983b6abfefb6356ba2300d5ae87b66a36125925904c2c61888ad85 price_change 90,869,628 860,067,812 34-380 90e2ef27254007583c9f61d1a83941c744df66656975dfced8b6754703c7edcf tick_size_change 2,976 108,173 381-381 09fac8f0582f340b3fa9fef8b949f2cd7fb5d37d57bce3b7cc86fab412dc84a1 EVENT MIX count share price_change 90,869,628 91.91% best_bid_ask 7,436,752 7.52% book 476,641 0.48% last_trade_price 81,720 0.08% tick_size_change 2,976 <0.01% market_resolved 852 <0.01% new_market 597 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,436,862 7,436,752 110 76,706 PARTIAL book 476,809 476,641 168 116,106 PARTIAL last_trade_price 81,720 81,720 0 3,784 PARTIAL market_resolved 852 852 0 852 PARTIAL new_market 597 597 0 433 PARTIAL price_change 90,870,676 90,869,628 1,048 132,738 PARTIAL tick_size_change 2,976 2,976 0 744 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,436,116 526 2ms 6ms 54ms 2.1s 0 transport_latency_assumed best_bid_ask e 7,413,603 7,413,493 44ms 97ms 2.8s 22.9s 0 transport_latency_assumed best_bid_ask h 7,435,067 22,733 18ms 31ms 133ms 8.0s 0 transport_latency_assumed book c 245,631 60,641 7ms 19.5min 24.0d 94.7d 0 book_staleness book e 298,957 298,857 5.5s 1.1h 24.1d 94.7d 0 book_staleness book h 291,798 117,143 136ms 46.6min 24.1d 94.7d 0 book_staleness last_trade_price c 81,624 17 7ms 37ms 175ms 4.9s 0 transport_latency_assumed last_trade_price e 77,060 77,060 89ms 6.1s 15.4s 22.9s 0 transport_latency_assumed last_trade_price h 81,604 4,643 26ms 229ms 1.1s 6.2s 0 transport_latency_assumed market_resolved c 852 not meas. 2ms 9ms 49.6s 49.9s 0 transport_latency_assumed market_resolved e 852 852 44ms 347ms 44.3s 44.4s 0 transport_latency_assumed market_resolved h 852 not meas. 18ms 114ms 47.8s 47.9s 0 transport_latency_assumed new_market c 433 61 36ms 22.9s 46.0s 1.1min 0 transport_latency_assumed new_market e 433 433 204ms 16.8s 33.3s 1.1min 0 transport_latency_assumed new_market h 433 103 88ms 17.3s 42.7s 1.1min 0 transport_latency_assumed price_change c 90,859,058 4,516 1ms 6ms 65ms 2.6s 0 transport_latency_assumed price_change e 90,193,138 90,192,090 44ms 137ms 6.1s 22.9s 0 transport_latency_assumed price_change h 90,844,136 673,022 18ms 34ms 256ms 8.5s 0 transport_latency_assumed tick_size_change c 2,976 not meas. 1ms 6ms 49ms 242ms 0 transport_latency_assumed tick_size_change e 2,976 2,976 44ms 95ms 2.6s 9.3s 0 transport_latency_assumed tick_size_change h 2,976 not meas. 17ms 24ms 69ms 495ms 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/15/2026-09-01T15.parquet sha256sum 2026-09-01T15.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.