Hour audit: 2026-09-01T00
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.
1 check could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-01T00 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T00:00:00.043511055+00:00 · last event 2026-09-01T00:59:59.995127977+00:00
VOLUME 2,873,621 rows · 64,401,079 bytes (61.42 MiB) · 7 products, 1 holding no rows
WITNESSES ceh — 3 machines contributed rows
captured h: 2,824,593 · c: 2,820,362 · e: 2,812,088 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 39,425 (1.37%) · c: 22,108 (0.77%) · e: 2,812,088 (97.86%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 2,873,621 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
the listing string reads "bche"; the letters above are the machines whose rows are in the file
INTEGRITY sha256 5ac69840e305c5e20968c50cfa22b1ab3944f628d4a3cb93435e968b98507c5b
the corpus checksum ledger names this file with the same digest
joined 2,873,625 to merged 2,873,621, minus 4 (minus 0.0001%)
boundary drops 4 · 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-02T04:27:47Z 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 6/8 pass, 1 finding, 1 not evaluated
PASS all products present
PASS row counts reconcile
SKIPPED the byte ranges could not be checked
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 paused trading, cancel-only mode, 2026-08-31T23:09Z to 2026-09-01T01:07ZThe 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 340,366 13,551,179 0-1 61fad4faaba3452f268fd7743e6978351c4d2fbb392806e48cf097f14e4d4a91 book 74,769 8,680,857 2-2 da7099a496b45874bd9210bc29e29c9e1f54462df7a01fc58bd1283ee7716591 last_trade_price 0 not meas. 3-2 not published market_resolved 688 112,813 3-3 cea2a6f4a4843e9e14eb269acab6becdbd5dc5ef22ac7020370fc349e0a52601 new_market 812 88,258 4-4 53b04b5b8cbaf06216bdb35371e05253a25a48ffd43cd345669c0580bb27e164 price_change 2,456,958 41,915,447 5-14 3cedcefec806bd10c9dcf666efe9b7862ecdf1b41ac15612fa4eb001d1e34fe2 tick_size_change 28 3,000 15-15 43c097f012dd096fad9c681d717f8a30599b0fa4b6e2cdce514b66286cf87350 EVENT MIX count share price_change 2,456,958 85.50% best_bid_ask 340,366 11.84% book 74,769 2.60% new_market 812 0.03% market_resolved 688 0.02% tick_size_change 28 <0.01% last_trade_price 0 0.00% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 340,366 340,366 0 88,864 PARTIAL book 74,773 74,769 4 36,479 PARTIAL last_trade_price 0 0 0 0 NO-SOURCE market_resolved 688 688 0 688 PARTIAL new_market 812 812 0 584 PARTIAL price_change 2,456,958 2,456,958 0 137,610 PARTIAL tick_size_change 28 28 0 7 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 340,343 not meas. 5ms 8ms 206ms 1.1s 0 transport_latency_assumed best_bid_ask e 340,326 340,326 45ms 59ms 788ms 4.4s 0 transport_latency_assumed best_bid_ask h 340,322 40 13ms 18ms 305ms 1.5s 0 transport_latency_assumed book c 23,867 19,130 1.1h 8.4h 31.2d 94.1d 0 book_staleness book e 24,039 24,039 1.1h 5.5h 29.5d 94.1d 0 book_staleness book h 34,954 31,600 1.1h 9.9h 29.5d 94.1d 0 book_staleness market_resolved c 688 not meas. 5ms 6ms 54.8s 54.8s 0 transport_latency_assumed market_resolved e 688 688 44ms 122ms 55.7s 55.7s 0 transport_latency_assumed market_resolved h 688 not meas. 13ms 19ms 58.6s 58.6s 0 transport_latency_assumed new_market c 584 184 43ms 25.6s 31.9s 1.2min 0 transport_latency_assumed new_market e 584 584 174ms 19.8s 30.8s 1.2min 0 transport_latency_assumed new_market h 584 44 80ms 22.0s 31.1s 1.6min 0 transport_latency_assumed price_change c 2,454,852 2,794 5ms 228ms 649ms 1.3s 0 transport_latency_assumed price_change e 2,446,423 2,446,423 46ms 794ms 2.6s 5.0s 0 transport_latency_assumed price_change h 2,448,017 7,741 13ms 294ms 784ms 1.6s 0 transport_latency_assumed tick_size_change c 28 not meas. 4ms 13ms 13ms 13ms 0 transport_latency_assumed tick_size_change e 28 28 45ms 47ms 47ms 47ms 0 transport_latency_assumed tick_size_change h 28 not meas. 13ms 14ms 14ms 14ms 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/00/2026-09-01T00.parquet sha256sum 2026-09-01T00.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.