Hour audit: 2026-09-01T21
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-01T21 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T21:00:00.037317674+00:00 · last event 2026-09-01T21:59:59.999954835+00:00
VOLUME 80,010,651 rows · 866,445,402 bytes (826.31 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 79,365,227 · h: 79,342,153 · e: 79,163,105 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 255,949 (0.32%) · h: 592,883 (0.74%) · e: 79,161,819 (98.94%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 80,010,651 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 ee4c5add7d23cda375beaeafa0833969059e3d7ad0c5bf246d20b4eb9316c4d3
the corpus checksum ledger names this file with the same digest
joined 80,012,183 to merged 80,010,651, minus 1,532 (minus 0.0019%)
boundary drops 1,532 · 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-01T23:39:14Z 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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.The 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 6,602,490 87,245,113 0-25 5fee09241f0d995404894218b76ea25182bd631192590dd9b1cc24f490d7a52e book 1,063,510 81,710,917 26-30 71bf7335dd7f28a289397aeed8523cec5ce0b3ed3f9764db847259abdad5b1e9 last_trade_price 52,689 2,948,856 31-31 9b5828a66cc3006b762a6746c3e1722343907961e8b4ee46d03275bfaaca0e27 market_resolved 2,090 340,275 32-32 1c367e7882f084681ddcf13a7c052102636336b06ed7c8325ebc7f8513d3f1f4 new_market 1,014 112,632 33-33 6fcaf244eccf2b7dc3c757480e57b7d8e71af230946a332be629a989173395cf price_change 72,286,682 693,091,800 34-309 1581a5c6bb997bee85f41a870dd0617263062ce128fa4f42f9cbc25826cfce26 tick_size_change 2,176 79,747 310-310 21dd8c87f5ad4d3d96ad59dd73d85c922f9ffbdd5f4aee72d896cc541d23df56 EVENT MIX count share price_change 72,286,682 90.35% best_bid_ask 6,602,490 8.25% book 1,063,510 1.33% last_trade_price 52,689 0.07% tick_size_change 2,176 <0.01% market_resolved 2,090 <0.01% new_market 1,014 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 6,602,548 6,602,490 58 128,746 PARTIAL book 1,064,040 1,063,510 530 181,483 PARTIAL last_trade_price 52,689 52,689 0 3,060 PARTIAL market_resolved 2,090 2,090 0 2,075 PARTIAL new_market 1,014 1,014 0 741 PARTIAL price_change 72,287,626 72,286,682 944 160,530 PARTIAL tick_size_change 2,176 2,176 0 544 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,600,915 402 4ms 8ms 124ms 12.8s 0 transport_latency_assumed best_bid_ask e 6,591,300 6,591,242 45ms 120ms 1.2s 24.6s 0 transport_latency_assumed best_bid_ask h 6,600,082 10,846 18ms 27ms 221ms 43.8s 0 transport_latency_assumed book c 444,547 242,810 57.6s 51.6min 29.0d 95.0d 0 book_staleness book e 540,931 540,647 1.1min 39.8min 24.3d 95.0d 0 book_staleness book h 449,393 280,053 58.1s 49.4min 29.2d 95.0d 0 book_staleness last_trade_price c 52,631 6 10ms 42ms 240ms 8.6s 0 transport_latency_assumed last_trade_price e 51,340 51,340 91ms 5.6s 14.9s 24.6s 0 transport_latency_assumed last_trade_price h 52,658 1,343 28ms 375ms 1.5s 5.0s 0 transport_latency_assumed market_resolved c 2,075 not meas. 4ms 9ms 48.9s 59.3s 0 transport_latency_assumed market_resolved e 2,075 2,075 47ms 375ms 50.9s 1.0min 0 transport_latency_assumed market_resolved h 2,075 15 20ms 84ms 46.8s 53.1s 0 transport_latency_assumed new_market c 741 57 50ms 11.5s 14.9s 2.5min 0 transport_latency_assumed new_market e 741 741 189ms 12.3s 16.4s 12.3min 0 transport_latency_assumed new_market h 741 216 103ms 13.0s 18.6s 3.4min 0 transport_latency_assumed price_change c 72,262,142 12,674 5ms 8ms 201ms 14.0s 0 transport_latency_assumed price_change e 71,974,542 71,973,598 46ms 167ms 4.6s 24.6s 0 transport_latency_assumed price_change h 72,235,028 300,410 18ms 35ms 360ms 44.3s 0 transport_latency_assumed tick_size_change c 2,176 not meas. 4ms 7ms 24ms 687ms 0 transport_latency_assumed tick_size_change e 2,176 2,176 45ms 105ms 441ms 7.8s 0 transport_latency_assumed tick_size_change h 2,176 not meas. 18ms 21ms 43ms 558ms 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/21/2026-09-01T21.parquet sha256sum 2026-09-01T21.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.