Hour audit: 2026-09-04T08
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-04T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-04T08:00:00.000628521+00:00 · last event 2026-09-04T08:59:59.999822541+00:00
VOLUME 99,524,134 rows · 958,317,316 bytes (913.92 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured c: 99,430,330 · e: 78,676,695 · h: 76,480,243 · b: 70,884,532 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 9,866,719 (9.91%) · e: 78,675,365 (79.05%) · h: 10,961,686 (11.01%) · b: 20,364 (0.02%) (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 99,524,134 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 772738c72df15a9f17da769a7b768b10d5f4d9e6a04590283c615e44c61bb6a6
the corpus checksum ledger names this file with the same digest
joined 99,525,782 to merged 99,524,134, minus 1,648 (minus 0.0017%)
boundary drops 1,648 · 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-04T09:50:54Z 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 8,869,372 97,315,821 0-33 b3c39b5b1025c231408b4e924552e6a8534aae28553e2beecfc0af7f02162887 book 230,281 23,128,862 34-34 a72e40395a370d74ecc78476835cdf39b7ae269b4b792749b9d3640506e92689 last_trade_price 73,575 3,973,597 35-35 8c9b8a3a3ab94dd8b74591441e8b34b7b59c3fc84a12061aafff349a8de45226 market_resolved 603 97,363 36-36 51169f0e141232db0b5a6d0e0e59b14e6c843e78f3e834c0f8b7498d7929566d new_market 1,059 113,643 37-37 1ce3906492e13f478859ddda9460c1dfbcc5fd6f120e7947ee7cf9db94c1491a price_change 90,347,060 832,476,330 38-382 710067e747c2c3457c31a474a454ed2a6633f0ecb9bee8dc1bf699096ef58669 tick_size_change 2,184 78,699 383-383 ea3312e62636119974575809eebb4def5800cb52437f7308f192c1cc9c8dbd1f EVENT MIX count share price_change 90,347,060 90.78% best_bid_ask 8,869,372 8.91% book 230,281 0.23% last_trade_price 73,575 0.07% tick_size_change 2,184 <0.01% new_market 1,059 <0.01% market_resolved 603 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,869,572 8,869,372 200 113 FULL book 230,303 230,281 22 33,451 FULL last_trade_price 73,575 73,575 0 0 FULL market_resolved 603 603 0 0 FULL new_market 1,059 1,059 0 0 FULL price_change 90,348,486 90,347,060 1,426 90,628 FULL tick_size_change 2,184 2,184 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,867,150 82 49ms 61ms 199ms 4.3s 0 transport_latency_assumed best_bid_ask c 8,869,146 578 4ms 8ms 64ms 3.8s 0 transport_latency_assumed best_bid_ask e 8,863,292 8,863,122 42ms 54ms 272ms 8.5s 0 transport_latency_assumed best_bid_ask h 8,868,712 5,590 18ms 25ms 121ms 47.5s 0 transport_latency_assumed book b 172,801 18,264 55ms 11.0s 19.2h 78.9d 0 book_staleness book c 154,766 1,272 6ms 25ms 2.4s 78.9d 0 book_staleness book e 209,856 209,834 55ms 39.9min 12.8d 97.4d 0 book_staleness book h 153,812 911 22ms 66ms 371ms 12.8s 0 book_staleness last_trade_price b 73,516 9 59ms 177ms 1.2s 5.1s 0 transport_latency_assumed last_trade_price c 73,491 10 9ms 38ms 210ms 5.0s 0 transport_latency_assumed last_trade_price e 73,248 73,248 50ms 206ms 2.0s 8.4s 0 transport_latency_assumed last_trade_price h 73,526 308 24ms 69ms 333ms 5.5s 0 transport_latency_assumed market_resolved b 592 not meas. 55ms 545ms 1.0min 1.0min 0 transport_latency_assumed market_resolved c 592 11 4ms 22ms 59.8s 59.8s 0 transport_latency_assumed market_resolved e 592 592 44ms 594ms 60.0s 1.0min 0 transport_latency_assumed market_resolved h 592 not meas. 20ms 172ms 1.0min 1.0min 0 transport_latency_assumed new_market b 739 119 226ms 56.6s 7.9min 17.8min 0 transport_latency_assumed new_market c 739 86 67ms 26.0s 6.0min 7.4min 0 transport_latency_assumed new_market e 739 739 193ms 35.6s 3.7min 7.8min 0 transport_latency_assumed new_market h 739 115 120ms 37.1s 3.7min 7.8min 0 transport_latency_assumed price_change b 61,767,550 1,890 49ms 68ms 307ms 4.3s 0 transport_latency_assumed price_change c 90,329,412 9,864,762 4ms 8ms 75ms 4.0s 0 transport_latency_assumed price_change e 69,526,784 69,525,646 43ms 70ms 411ms 8.5s 0 transport_latency_assumed price_change h 67,380,678 10,954,762 18ms 28ms 148ms 47.6s 0 transport_latency_assumed tick_size_change b 2,184 not meas. 48ms 60ms 127ms 178ms 0 transport_latency_assumed tick_size_change c 2,184 not meas. 4ms 6ms 24ms 111ms 0 transport_latency_assumed tick_size_change e 2,184 2,184 42ms 48ms 117ms 299ms 0 transport_latency_assumed tick_size_change h 2,184 not meas. 18ms 21ms 38ms 114ms 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/08/2026-09-04T08.parquet sha256sum 2026-09-04T08.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.