Hour audit: 2026-09-04T21
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.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-04T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T21:00:00.031053133+00:00 · last event 2026-09-04T21:59:59.999989924+00:00
VOLUME 92,301,912 rows · 921,525,709 bytes (878.84 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured b: 92,205,612 · h: 92,156,603 · c: 92,084,291 · e: 91,804,789 (each machine's own feed; these overlap and do not sum to the file)
supplied b: 60,898 (0.07%) · h: 387,299 (0.42%) · c: 50,062 (0.05%) · e: 91,803,653 (99.46%) (rows of the merged file that came from it; these partition it)
5 product-machine pairs publish no supplied count; the figures above still sum to the file's 92,301,912 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 e83781a17955043f352496fd19fcdc5868c58fd10f60d85733d6b332e3cc9cc6
the corpus checksum ledger names this file with the same digest
joined 92,303,421 to merged 92,301,912, minus 1,509 (minus 0.0016%)
boundary drops 1,509 · 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-04T22:51:48Z as bceh
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 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
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 11,076,293 121,117,779 0-42 c6add1ea7b61f70d13a5276b9f8b44989df8c0f89e72c87f355881afccdc1b5c book 256,896 25,075,105 43-43 c2a5e8f82f169aedb760d82ed86cad7e35e7e0983904df577762b18a9f19e0ff last_trade_price 61,067 3,463,415 44-44 1b4687f6004782cc71976b26f381381a5a89854dd755a9eb1548aa505499c80e market_resolved 1,885 305,942 45-45 5e19177b7ebaaffec1cd21d92394edeb7c920ef8e95616a813b4e7faad32abc4 new_market 1,449 168,391 46-46 1e49840f04ef548b49b201aa48ed3d9afc0f55564b312a7f7e547f5a34396f8f price_change 80,901,354 770,233,514 47-355 ed2ca3fb06495e4dd9dc7a45635afb3b8180f81345d36f08af3459108fddb3a9 tick_size_change 2,968 109,431 356-356 5dc54039929eb6f94a864a069797ff126bcf5ee9646c2761c33318b305500ed6 EVENT MIX count share price_change 80,901,354 87.65% best_bid_ask 11,076,293 12.00% book 256,896 0.28% last_trade_price 61,067 0.07% tick_size_change 2,968 <0.01% market_resolved 1,885 <0.01% new_market 1,449 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,076,525 11,076,293 232 150 FULL book 256,902 256,896 6 56,772 FULL last_trade_price 61,068 61,067 1 0 FULL market_resolved 1,885 1,885 0 0 FULL new_market 1,449 1,449 0 0 FULL price_change 80,902,624 80,901,354 1,270 353 FULL tick_size_change 2,968 2,968 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 11,074,011 26 50ms 63ms 225ms 9.7s 0 transport_latency_assumed best_bid_ask c 11,069,044 669 4ms 7ms 66ms 3.6s 0 transport_latency_assumed best_bid_ask e 11,061,133 11,060,965 41ms 50ms 280ms 21.7s 0 transport_latency_assumed best_bid_ask h 11,075,178 14,633 19ms 23ms 153ms 32.6s 0 transport_latency_assumed book b 180,939 47,141 70ms 11.8min 13.3d 79.5d 0 book_staleness book c 167,196 38,620 7ms 7.0min 13.2d 90.2d 0 book_staleness book e 149,156 149,156 46ms 3.2min 9.1d 48.5d 0 book_staleness book h 145,755 21,979 24ms 32.7s 1.1d 79.5d 0 book_staleness last_trade_price b 61,014 3 60ms 277ms 4.2s 9.8s 0 transport_latency_assumed last_trade_price c 60,263 11 9ms 36ms 215ms 5.0s 0 transport_latency_assumed last_trade_price e 59,072 59,072 50ms 573ms 9.6s 21.6s 0 transport_latency_assumed last_trade_price h 61,000 1,981 24ms 88ms 606ms 6.7s 0 transport_latency_assumed market_resolved b 1,877 not meas. 51ms 200ms 620ms 36.6s 0 transport_latency_assumed market_resolved c 1,877 8 4ms 7ms 94ms 1.0min 0 transport_latency_assumed market_resolved e 1,877 1,877 42ms 171ms 609ms 38.2s 0 transport_latency_assumed market_resolved h 1,877 not meas. 19ms 68ms 215ms 32.4s 0 transport_latency_assumed new_market b 1,107 68 145ms 16.5s 1.4min 2.5min 0 transport_latency_assumed new_market c 1,107 74 53ms 14.1s 1.4min 9.2min 0 transport_latency_assumed new_market e 1,107 1,107 162ms 14.6s 1.6min 27.4min 0 transport_latency_assumed new_market h 1,107 200 114ms 15.7s 1.5min 2.5min 0 transport_latency_assumed price_change b 80,883,696 13,660 50ms 67ms 384ms 9.8s 0 transport_latency_assumed price_change c 80,781,836 10,680 4ms 7ms 77ms 6.9s 0 transport_latency_assumed price_change e 80,529,476 80,528,508 41ms 66ms 801ms 21.8s 0 transport_latency_assumed price_change h 80,868,718 348,506 19ms 26ms 188ms 33.8s 0 transport_latency_assumed tick_size_change b 2,968 not meas. 50ms 64ms 198ms 310ms 0 transport_latency_assumed tick_size_change c 2,968 not meas. 4ms 8ms 80ms 417ms 0 transport_latency_assumed tick_size_change e 2,968 2,968 41ms 108ms 581ms 701ms 0 transport_latency_assumed tick_size_change h 2,968 not meas. 19ms 29ms 160ms 642ms 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-04/21/2026-09-04T21.parquet sha256sum 2026-09-04T21.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.