Hour audit: 2026-08-31T08
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 5 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
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-08-31T08 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T08:00:00.042932481+00:00 · last event 2026-08-31T08:59:59.999619685+00:00
VOLUME 152,120 rows · 3,785,585 bytes (3.61 MiB) · 7 products, 2 holding no rows
WITNESSES aceh — 4 machines contributed rows
captured a: 147,949 · e: 143,024 · h: 141,936 · c: 141,750 (each machine's own feed; these overlap and do not sum to the file)
supplied a: 6,730 (4.42%) · e: 143,024 (94.02%) · h: 1,750 (1.15%) · c: 616 (0.40%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 152,120 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 649f243d3fc1f4947c80adc08a13b4949756e59b1ff1f3aa0d6d78f3b69aa4ec
the corpus checksum ledger names this file with the same digest
joined 152,132 to merged 152,120, minus 12 (minus 0.0079%)
boundary drops 12 · 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-08-31T11:44:17Z as aceh
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 stopped trading for four hours, 2026-08-31T06:30Z to 2026-08-31T10:47ZThe 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 2,834 145,734 0-0 de65feb42cb4add1cf4aca7256519184a1f295a6cace227e53c474b86ab78232 book 11,762 1,349,423 1-1 a0cdebf9569df5234b1c7f2f8197e7a6ad59f00df1b9d9177d385439149e853a last_trade_price 0 not meas. 2-1 not published market_resolved 477 76,453 2-2 17ea48ad8919b817d927527eb952f8c0ecf7b32faef8ade6cdab9f995fb5de26 new_market 847 89,789 3-3 9b261b2d6de34f909d4be45c3666e23aad2c29f8e04019ed80533899f845ee66 price_change 136,200 2,106,428 4-4 645662012007094abde2733c778dadef8e129e2be4e27e57684c7eb4115328a5 tick_size_change 0 not meas. 5-4 not published EVENT MIX count share price_change 136,200 89.53% book 11,762 7.73% best_bid_ask 2,834 1.86% new_market 847 0.56% market_resolved 477 0.31% last_trade_price 0 0.00% tick_size_change 0 0.00% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 2,834 2,834 0 979 PARTIAL book 11,774 11,762 12 5,882 PARTIAL last_trade_price 0 0 0 0 NO-SOURCE market_resolved 477 477 0 467 PARTIAL new_market 847 847 0 593 PARTIAL price_change 136,200 136,200 0 7,723 PARTIAL tick_size_change 0 0 0 0 NO-SOURCE ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 2,832 not meas. 36ms 104ms 394ms 1.9s 0 transport_latency_assumed best_bid_ask c 2,834 2 1ms 5ms 26ms 260ms 0 transport_latency_assumed best_bid_ask e 2,830 2,830 44ms 211ms 914ms 1.4s 0 transport_latency_assumed best_bid_ask h 2,832 2 14ms 29ms 119ms 484ms 0 transport_latency_assumed book a 7,931 6,708 1.9h 9.3h 27.3d 74.9d 0 book_staleness book c 1,656 496 2.7s 1.9h 22.8d 74.8d 0 book_staleness book e 3,328 3,328 1.5h 3.7h 29.6d 31.0d 0 book_staleness book h 2,390 1,230 24.2min 2.4h 22.8d 74.8d 0 book_staleness market_resolved a 467 3 70ms 383ms 49.1s 1.1min 0 transport_latency_assumed market_resolved c 467 5 1ms 4ms 59.7s 1.0min 0 transport_latency_assumed market_resolved e 467 467 68ms 580ms 49.1s 1.1min 0 transport_latency_assumed market_resolved h 467 2 14ms 22ms 48.8s 53.6s 0 transport_latency_assumed new_market a 593 19 150ms 21.0s 37.4s 1.6min 0 transport_latency_assumed new_market c 593 51 41ms 11.8s 26.6s 1.2min 0 transport_latency_assumed new_market e 593 593 190ms 20.5s 37.7s 1.4min 0 transport_latency_assumed new_market h 593 184 91ms 13.8s 25.8s 56.0s 0 transport_latency_assumed price_change a 136,126 not meas. 38ms 187ms 1.0s 1.9s 0 transport_latency_assumed price_change c 136,200 62 2ms 11ms 50ms 587ms 0 transport_latency_assumed price_change e 135,806 135,806 44ms 295ms 962ms 1.7s 0 transport_latency_assumed price_change h 135,654 332 18ms 64ms 187ms 839ms 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-08-31/08/2026-08-31T08.parquet sha256sum 2026-08-31T08.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.