Hour audit: 2026-09-02T02
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-02T02 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-02T02:00:00.023041057+00:00 · last event 2026-09-02T02:59:59.125662752+00:00
VOLUME 302,168 rows · 12,609,541 bytes (12.03 MiB) · 7 products, 2 holding no rows
WITNESSES eh — 2 machines contributed rows
captured h: 289,074 · e: 249,217 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 52,971 (17.53%) · e: 249,197 (82.47%) (rows of the merged file that came from it; these partition it)
4 expected (bceh), 2 contributed nothing: b, c
INTEGRITY sha256 12e5f5a32a2b50e113ad3f40e97e9237407c57b960899ee2a03ea7e80ea4945e
the corpus checksum ledger names this file with the same digest
joined 302,264 to merged 302,168, minus 96 (minus 0.0318%)
boundary drops 96 · 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:22Z 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 10,068 505,273 0-0 b4920f7ad6ab1255a4d3f14576be66c1565b289e67f06cf063971d6130bdde72 book 63,663 6,991,902 1-1 eab22cf6148b9af44859e2d496cd4110b627b5b3d13376722f51879df13d596f last_trade_price 0 not meas. 2-1 not published market_resolved 759 123,826 2-2 b569aebfc57e0546a69f348ac2e4565c661d47601d30b113b50fb8b62d263bda new_market 1,586 168,303 3-3 6914f3038edb13f987dc93363ac4ab5f4b126449885567d3c59b4e1fcdfa2d26 price_change 226,092 4,802,385 4-4 fbe9ad7ca4f9acaebe9cfdffae75a62e3e13ffd22ecfbf88f8469f81c4d47711 tick_size_change 0 not meas. 5-4 not published EVENT MIX count share price_change 226,092 74.82% book 63,663 21.07% best_bid_ask 10,068 3.33% new_market 1,586 0.52% market_resolved 759 0.25% last_trade_price 0 0.00% tick_size_change 0 0.00% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,068 10,068 0 3,555 PARTIAL book 63,759 63,663 96 31,320 PARTIAL last_trade_price 0 0 0 0 NO-SOURCE market_resolved 759 759 0 754 PARTIAL new_market 1,586 1,586 0 1,127 PARTIAL price_change 226,092 226,092 0 24,369 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 9,840 9,840 41ms 127ms 1.0s 2.0s 0 transport_latency_assumed best_bid_ask h 10,068 228 20ms 45ms 274ms 572ms 0 transport_latency_assumed book e 16,878 16,858 1.3h 3.2h 24.5d 76.6d 0 book_staleness book h 51,035 46,805 47.3min 3.0h 30.6d 95.2d 0 book_staleness market_resolved e 748 748 40ms 117ms 897ms 2.2min 0 transport_latency_assumed market_resolved h 754 11 19ms 30ms 269ms 1.0min 0 transport_latency_assumed new_market e 1,127 1,127 218ms 36.9s 1.1min 1.3min 0 transport_latency_assumed new_market h 1,127 459 142ms 39.9s 1.1min 1.5min 0 transport_latency_assumed price_change e 220,624 220,624 41ms 361ms 1.3s 2.1s 0 transport_latency_assumed price_change h 226,090 5,468 22ms 102ms 330ms 2.0s 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/02/2026-09-02T02.parquet sha256sum 2026-09-02T02.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.