Hour audit: 2026-09-02T03
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, 2 contributed no rows: b, c. The hour is still whole on minutes; it simply rests on 2 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-02T03 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-02T03:00:00.038343837+00:00 · last event 2026-09-02T03:59:59.133332049+00:00
VOLUME 256,990 rows · 7,296,036 bytes (6.96 MiB) · 7 products, 2 holding no rows
WITNESSES eh — 2 machines contributed rows
captured e: 239,750 · h: 235,376 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 239,740 (93.29%) · h: 17,250 (6.71%) (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 256,990 rows exactly, so those pairs supplied none
4 expected (bceh), 2 contributed nothing: b, c
INTEGRITY sha256 584cf0fb342be0b623247576dcd336aa8e4a17e735dae12e6e268bef2c38ba2e
the corpus checksum ledger names this file with the same digest
joined 257,004 to merged 256,990, minus 14 (minus 0.0054%)
boundary drops 14 · 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-02T05:32:50Z as eh
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 restart, then a paused database migration, 2026-09-01T22:30Z to 2026-09-02T04:58ZThe 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 5,134 167,194 0-0 c8bde65668638e52130cad65f800cd89032974e858c69f9b04f6b38ddfef7313 book 35,625 4,011,718 1-1 78947a04a22a94ac35e5c6b97479115149b8aa53cf315723338d88cd77a839d0 last_trade_price 0 not meas. 2-1 not published market_resolved 814 132,816 2-2 3f600bde636415539e148681b27682d82fd19558ff0a26e0258d4bfb49030b19 new_market 451 51,311 3-3 4f800fd8381a407d60d4b3ccef5d73a32d524863e54d4fc4f54d6138059d6470 price_change 214,966 2,915,252 4-4 328318e431850c77f8e1598f7d69fee4dcd3b55582b9659854e7ffcefeec090d tick_size_change 0 not meas. 5-4 not published EVENT MIX count share price_change 214,966 83.65% book 35,625 13.86% best_bid_ask 5,134 2.00% market_resolved 814 0.32% new_market 451 0.18% last_trade_price 0 0.00% tick_size_change 0 0.00% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 5,134 5,134 0 931 PARTIAL book 35,639 35,625 14 17,544 PARTIAL last_trade_price 0 0 0 0 NO-SOURCE market_resolved 814 814 0 814 PARTIAL new_market 451 451 0 343 PARTIAL price_change 214,966 214,966 0 9,713 PARTIAL tick_size_change 0 0 0 0 NO-SOURCE ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask e 5,124 5,124 48ms 465ms 3.7s 6.1s 0 transport_latency_assumed best_bid_ask h 5,134 10 22ms 79ms 306ms 587ms 0 transport_latency_assumed book e 22,967 22,957 1.8h 4.4h 31.4d 76.7d 0 book_staleness book h 14,119 12,668 2.0h 6.4h 30.6d 76.7d 0 book_staleness market_resolved e 814 814 44ms 125ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 814 not meas. 19ms 39ms 1.0min 1.0min 0 transport_latency_assumed new_market e 343 343 138ms 15.5s 25.6s 1.2min 0 transport_latency_assumed new_market h 343 108 59ms 17.4s 24.9s 1.1min 0 transport_latency_assumed price_change e 210,502 210,502 60ms 3.7s 5.8s 6.3s 0 transport_latency_assumed price_change h 214,966 4,464 39ms 118ms 354ms 1.1s 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-02/03/2026-09-02T03.parquet sha256sum 2026-09-02T03.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.