Hour audit: 2026-09-01T14
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-01T14 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T14:00:00.023532014+00:00 · last event 2026-09-01T14:59:59.999954320+00:00
VOLUME 96,230,062 rows · 1,008,011,111 bytes (961.31 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured h: 95,616,573 · e: 95,243,263 · c: 85,635,167 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 632,976 (0.66%) · e: 95,238,725 (98.97%) · c: 358,361 (0.37%) (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 96,230,062 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
INTEGRITY sha256 9ae6e0ddaf69f4dcfa068bab5e859106d94963e7e7a9c7092f3b1de00c01a799
the corpus checksum ledger names this file with the same digest
joined 96,237,204 to merged 96,230,062, minus 7,142 (minus 0.0074%)
boundary drops 7,142 · 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-01T21:16:46Z 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 7,171,108 83,728,609 0-27 61bafb1fe7ded322dffa383a987097e786064bdef272ca9ebdcad356f847dd6a book 1,092,981 78,273,646 28-32 f7c1caf2398d2af0b92bf3878ce9adc38b6fee24c0ba932134a98db002b73b58 last_trade_price 81,376 4,487,990 33-33 4631d31b9631dde48c6dfd96b54829ac9535819aba11fafb4fab8eda10beef07 market_resolved 862 124,267 34-34 81b82dcfe134e47fa2939b658d80aeb14c8314d3cd3bb643355d6c910d63ac61 new_market 1,311 138,307 35-35 e501f9d11b54fd2b1dca34f8d25f761d150b72e378a1815d7f2d1dabd0e17c22 price_change 87,879,920 840,067,660 36-371 277972735f9cdb7e0d78dce6b768b2d65d3f56de8f37901d227195307210ee1e tick_size_change 2,504 92,140 372-372 4c456916609c287b1e6860d2fc8fc6c1817196f310acb5c3dddf009941832086 EVENT MIX count share price_change 87,879,920 91.32% best_bid_ask 7,171,108 7.45% book 1,092,981 1.14% last_trade_price 81,376 0.08% tick_size_change 2,504 <0.01% new_market 1,311 <0.01% market_resolved 862 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,171,204 7,171,108 96 79,500 PARTIAL book 1,099,223 1,092,981 6,242 176,432 PARTIAL last_trade_price 81,376 81,376 0 3,982 PARTIAL market_resolved 862 862 0 767 PARTIAL new_market 1,311 1,311 0 912 PARTIAL price_change 87,880,724 87,879,920 804 139,095 PARTIAL tick_size_change 2,504 2,504 0 626 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,446,870 819 2ms 6ms 85ms 3.0s 0 transport_latency_assumed best_bid_ask e 7,155,978 7,155,884 42ms 92ms 1.1s 30.8s 0 transport_latency_assumed best_bid_ask h 7,168,025 14,405 18ms 29ms 193ms 45.2s 0 transport_latency_assumed book c 638,316 343,891 1.3min 7.6h 29.9d 94.7d 0 book_staleness book e 493,407 489,765 49.2s 5.9h 28.3d 94.7d 0 book_staleness book h 531,356 259,325 52.7s 5.9h 27.9d 94.7d 0 book_staleness last_trade_price c 73,592 90 7ms 37ms 180ms 5.0s 0 transport_latency_assumed last_trade_price e 78,244 78,244 75ms 3.4s 15.9s 30.8s 0 transport_latency_assumed last_trade_price h 81,153 3,042 25ms 157ms 774ms 12.6s 0 transport_latency_assumed market_resolved c 754 89 2ms 3.7min 8.6min 8.6min 0 transport_latency_assumed market_resolved e 762 762 42ms 283ms 2.2s 1.0min 0 transport_latency_assumed market_resolved h 767 11 18ms 72ms 150ms 230ms 0 transport_latency_assumed new_market c 912 140 123ms 1.0min 1.4min 6.8d 0 transport_latency_assumed new_market e 912 912 265ms 58.8s 1.4min 6.8d 0 transport_latency_assumed new_market h 912 259 167ms 57.3s 1.4min 1.4min 0 transport_latency_assumed price_change c 78,472,483 13,332 2ms 7ms 147ms 3.7s 0 transport_latency_assumed price_change e 87,511,456 87,510,654 42ms 144ms 4.2s 30.8s 0 transport_latency_assumed price_change h 87,831,856 355,934 18ms 33ms 304ms 51.4s 0 transport_latency_assumed tick_size_change c 2,240 not meas. 2ms 5ms 21ms 230ms 0 transport_latency_assumed tick_size_change e 2,504 2,504 42ms 107ms 419ms 12.2s 0 transport_latency_assumed tick_size_change h 2,504 not meas. 18ms 26ms 215ms 2.2s 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/14/2026-09-01T14.parquet sha256sum 2026-09-01T14.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.