Hour audit: 2026-09-01T08
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-01T08 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T08:00:00.032262132+00:00 · last event 2026-09-01T08:59:59.999956296+00:00
VOLUME 91,294,797 rows · 938,401,604 bytes (894.93 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured h: 90,692,904 · e: 90,126,611 · c: 81,412,614 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 839,337 (0.92%) · e: 90,125,348 (98.72%) · c: 330,112 (0.36%) (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 91,294,797 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 f8bf7434d7314bdaa0aceb9d89c6f693a541b0f3df4091c2f4c8c5cbe1078be5
the corpus checksum ledger names this file with the same digest
joined 91,296,078 to merged 91,294,797, minus 1,281 (minus 0.0014%)
boundary drops 1,281 · 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-01T13:58:00Z 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 an incident recorded by the venue intersects this hour: Venue maintenance on a market this archive does not record, 2026-09-01T07:30Z to 2026-09-01T09:30ZThe 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,850,417 87,652,593 0-29 166adb0a41f0abd7e8b1bee747a582b2e3ca0e29056470d0a7e2583a15e088d2 book 653,797 59,716,445 30-32 2f5c6ea2d824e36b4003c4137966fd227c09b4534285d42adad618fd156ddea6 last_trade_price 77,707 4,235,492 33-33 0cce411fe609eee53a86872db0da68f91d7cb7d839024874bede55998743a802 market_resolved 973 136,630 34-34 9b1866de184f1ccd0c01ea5beb1daaa2b63b4d4a83e46cf2a8dda7d6913ea19b new_market 2,205 231,413 35-35 91755806b6694a6452c363afccffd41b857127265dbf0533e5b719eb3cab95da price_change 82,707,470 785,306,527 36-351 7adbe88840d73597c1e5d1f886c2226a12add2ccb1ed6e0c1690c1b60ecb059b tick_size_change 2,228 82,477 352-352 99e2ce2e856e0749f5df8d175cc2cfaa26858cb1d34e47cb6df48b6009b55acb EVENT MIX count share price_change 82,707,470 90.59% best_bid_ask 7,850,417 8.60% book 653,797 0.72% last_trade_price 77,707 0.09% tick_size_change 2,228 <0.01% new_market 2,205 <0.01% market_resolved 973 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,850,505 7,850,417 88 69,169 PARTIAL book 653,835 653,797 38 177,706 PARTIAL last_trade_price 77,708 77,707 1 3,511 PARTIAL market_resolved 973 973 0 837 PARTIAL new_market 2,205 2,205 0 1,536 PARTIAL price_change 82,708,624 82,707,470 1,154 138,319 PARTIAL tick_size_change 2,228 2,228 0 555 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,948,881 2,632 1ms 6ms 135ms 2.5s 0 transport_latency_assumed best_bid_ask e 7,819,707 7,819,619 42ms 104ms 2.0s 32.9s 0 transport_latency_assumed best_bid_ask h 7,842,964 28,166 19ms 27ms 397ms 47.4s 0 transport_latency_assumed book c 531,006 283,257 1.1min 7.1h 28.5d 94.4d 0 book_staleness book e 349,338 349,316 18.2s 2.0h 23.8d 94.4d 0 book_staleness book h 172,655 21,224 29ms 1.7s 2.8h 75.9d 0 book_staleness last_trade_price c 70,282 364 7ms 39ms 211ms 4.9s 0 transport_latency_assumed last_trade_price e 72,531 72,530 98ms 8.3s 21.2s 32.9s 0 transport_latency_assumed last_trade_price h 76,888 4,813 29ms 513ms 3.6s 9.0s 0 transport_latency_assumed market_resolved c 837 135 2ms 4.6min 8.9min 8.9min 0 transport_latency_assumed market_resolved e 836 836 42ms 202ms 1.1s 1.0min 0 transport_latency_assumed market_resolved h 837 2 20ms 66ms 923ms 39.5s 0 transport_latency_assumed new_market c 1,536 262 77ms 20.1s 47.6s 1.9min 0 transport_latency_assumed new_market e 1,536 1,536 291ms 23.0s 56.0s 2.5min 0 transport_latency_assumed new_market h 1,536 407 155ms 19.6s 47.1s 1.2min 0 transport_latency_assumed price_change c 73,858,044 43,462 1ms 7ms 167ms 3.4s 0 transport_latency_assumed price_change e 81,880,439 81,879,287 42ms 160ms 8.2s 32.9s 0 transport_latency_assumed price_change h 82,595,796 784,721 19ms 33ms 668ms 47.7s 0 transport_latency_assumed tick_size_change c 2,028 not meas. 2ms 8ms 208ms 296ms 0 transport_latency_assumed tick_size_change e 2,224 2,224 42ms 116ms 1.5s 18.9s 0 transport_latency_assumed tick_size_change h 2,228 4 19ms 40ms 772ms 1.2s 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/08/2026-09-01T08.parquet sha256sum 2026-09-01T08.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.