Hour audit: 2026-09-04T03
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-04T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T03:00:00.000028190+00:00 · last event 2026-09-04T03:59:59.999951271+00:00
VOLUME 100,895,817 rows · 956,316,715 bytes (912.01 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 100,847,531 · h: 74,712,920 · e: 64,638,097 · b: 59,987,593 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 18,144,945 (17.98%) · h: 18,110,290 (17.95%) · e: 64,637,386 (64.06%) · b: 3,196 (0.00%) (rows of the merged file that came from it; these partition it)
6 product-machine pairs publish no supplied count; the figures above still sum to the file's 100,895,817 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 96187dd9e4c939125a56bc6f098584fd643bcf6fc4b83a5bc62427153248fba7
the corpus checksum ledger names this file with the same digest
joined 100,896,811 to merged 100,895,817, minus 994 (minus 0.0010%)
boundary drops 994 · 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-04T04:49:58Z 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 9,231,932 102,153,273 0-35 eaeec0bc1f0a14d5b63e9b2f3a0ce0bb42602dec08b74f982fd9ded6042b157d book 172,793 15,880,002 36-36 70f4787a3e500bcae2047f4f71bd184c663c8f1873bd3c427c90c26380ba3ba5 last_trade_price 64,822 3,550,112 37-37 58ac012e7402356d8c1e9a20fc9ba18e9a8049b21566eba7f1c956de454969bb market_resolved 1,111 180,439 38-38 5b3393b8c1a320df120ee510a995a70d8e22b885dde35b273f329339b11752e3 new_market 1,961 205,796 39-39 b36f64ed2b5a74d81e90872a9adea4f968bd5dbc8c59a22a118f7a61cf78fbf3 price_change 91,420,810 833,107,912 40-388 febe03eff4e7daf00d32e1c20563abc272d78d80027986f385eceb2ba53e69b9 tick_size_change 2,388 88,344 389-389 51a7c55b20fff883a43e8ac9c5c5afef6b7b6fa7c058eefaabeb1d3ebc7d0334 EVENT MIX count share price_change 91,420,810 90.61% best_bid_ask 9,231,932 9.15% book 172,793 0.17% last_trade_price 64,822 0.06% tick_size_change 2,388 <0.01% new_market 1,961 <0.01% market_resolved 1,111 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,232,067 9,231,932 135 249 FULL book 172,793 172,793 0 15,093 FULL last_trade_price 64,823 64,822 1 1 FULL market_resolved 1,111 1,111 0 0 FULL new_market 1,961 1,961 0 0 FULL price_change 91,421,668 91,420,810 858 106,960 FULL tick_size_change 2,388 2,388 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,225,617 116 51ms 81ms 729ms 20.7s 0 transport_latency_assumed best_bid_ask c 9,231,329 1,215 4ms 7ms 143ms 2.0s 0 transport_latency_assumed best_bid_ask e 9,208,916 9,208,798 41ms 105ms 2.3s 20.3s 0 transport_latency_assumed best_bid_ask h 9,230,169 21,803 17ms 24ms 244ms 42.5s 0 transport_latency_assumed book b 135,871 2,466 67ms 3.7s 1.1min 78.5d 0 book_staleness book c 140,302 4,959 6ms 51ms 1.1h 78.7d 0 book_staleness book e 153,885 153,885 148ms 1.5min 16.9h 97.2d 0 book_staleness book h 142,014 11,483 28ms 549ms 3.9h 78.7d 0 book_staleness last_trade_price b 63,837 5 73ms 2.9s 13.4s 20.7s 0 transport_latency_assumed last_trade_price c 64,745 17 9ms 42ms 289ms 4.9s 0 transport_latency_assumed last_trade_price e 62,498 62,497 79ms 4.5s 13.1s 20.0s 0 transport_latency_assumed last_trade_price h 64,769 2,303 27ms 299ms 1.2s 13.7s 0 transport_latency_assumed market_resolved b 1,111 not meas. 52ms 213ms 716ms 1.3s 0 transport_latency_assumed market_resolved c 1,111 not meas. 4ms 8ms 134ms 500ms 0 transport_latency_assumed market_resolved e 1,111 1,111 41ms 204ms 709ms 7.0s 0 transport_latency_assumed market_resolved h 1,111 not meas. 18ms 76ms 236ms 2.1s 0 transport_latency_assumed new_market b 1,381 191 259ms 18.8s 43.9s 7.8min 0 transport_latency_assumed new_market c 1,381 60 80ms 15.5s 49.5s 1.4min 0 transport_latency_assumed new_market e 1,381 1,381 205ms 13.9s 42.1s 1.2min 0 transport_latency_assumed new_market h 1,381 329 151ms 13.9s 34.2s 1.1min 0 transport_latency_assumed price_change b 50,557,388 418 52ms 141ms 4.7s 20.7s 0 transport_latency_assumed price_change c 91,406,275 18,138,694 4ms 8ms 176ms 3.3s 0 transport_latency_assumed price_change e 55,207,918 55,207,326 42ms 191ms 6.1s 20.3s 0 transport_latency_assumed price_change h 65,271,088 18,074,372 17ms 31ms 380ms 45.1s 0 transport_latency_assumed tick_size_change b 2,388 not meas. 51ms 66ms 172ms 287ms 0 transport_latency_assumed tick_size_change c 2,388 not meas. 4ms 6ms 37ms 238ms 0 transport_latency_assumed tick_size_change e 2,388 2,388 40ms 75ms 247ms 1.2s 0 transport_latency_assumed tick_size_change h 2,388 not meas. 17ms 23ms 74ms 297ms 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/03/2026-09-04T03.parquet sha256sum 2026-09-04T03.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.