Hour audit: 2026-09-08T04
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-08T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-08T04:00:00.000136605+00:00 · last event 2026-09-08T04:59:59.999990439+00:00
VOLUME 87,302,319 rows · 862,143,061 bytes (822.20 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 87,274,253 · h: 87,262,518 · f: 87,196,460 · e: 87,170,845 · g: 87,168,226 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 84,018,180 (96.24%) · h: 2,677,276 (3.07%) · f: 168,026 (0.19%) · e: 410,754 (0.47%) · g: 28,083 (0.03%) (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 87,302,319 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 146d7be605c2608525d88b99136adc3b98878a4b9e43f669ae7e7cefca52a92b
the corpus checksum ledger names this file with the same digest
joined 87,304,243 to merged 87,302,319, minus 1,924 (minus 0.0022%)
boundary drops 1,924 · 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-08T05:54:07Z as cefgh
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,434,291 93,473,713 0-32 34681a634aecd1beda63ee039cd684e26d400f8d2583da087883e073adaccc1c book 128,589 12,718,602 33-33 e7c9e98bc948fe95af2b22eb14f8a3d152b4b190e00a4db8b410855bc7d80eb6 last_trade_price 51,357 2,902,572 34-34 eb5f3b882a8f96634218798b420733364213b3d124c3f6d6acd2c1e25e187a68 market_resolved 1,752 286,638 35-35 edf13ef74c28a927a8f1b778d9d18f0917ba1c07d15fadb981e898770355d6ed new_market 2,834 283,314 36-36 b41a07140d386c91bba1d0ae72bf7a1fb85ff32459b605b5a80df41056ec8648 price_change 78,680,284 751,361,431 37-337 bc65b663992bc620160a57214e1b98a97ad28548e75957e64c88d88802631ee6 tick_size_change 3,212 116,779 338-338 21483cbb4531cf200a7606036495de92bee09d3b04524eb281d73dfcab286f47 EVENT MIX count share price_change 78,680,284 90.12% best_bid_ask 8,434,291 9.66% book 128,589 0.15% last_trade_price 51,357 0.06% tick_size_change 3,212 <0.01% new_market 2,834 <0.01% market_resolved 1,752 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,434,507 8,434,291 216 203 FULL book 128,591 128,589 2 8,744 FULL last_trade_price 51,357 51,357 0 0 FULL market_resolved 1,752 1,752 0 0 FULL new_market 2,834 2,834 0 0 FULL price_change 78,681,990 78,680,284 1,706 253 FULL tick_size_change 3,212 3,212 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,433,817 8,126,279 5ms 8ms 162ms 6.3s 0 transport_latency_assumed best_bid_ask e 8,432,618 39,902 39ms 45ms 233ms 5.3s 0 transport_latency_assumed best_bid_ask f 8,432,554 15,902 47ms 55ms 259ms 6.6s 0 transport_latency_assumed best_bid_ask g 8,430,637 1,651 79ms 101ms 539ms 15.6s 0 transport_latency_assumed best_bid_ask h 8,433,024 250,557 17ms 23ms 312ms 36.9s 0 transport_latency_assumed book c 112,872 105,438 6ms 71ms 4.1h 82.7d 0 book_staleness book e 110,358 3,626 41ms 222ms 5.3min 82.7d 0 book_staleness book f 108,986 1,714 50ms 175ms 3.3s 82.6d 0 book_staleness book g 117,973 10,621 88ms 3.5s 17.3h 82.8d 0 book_staleness book h 110,106 7,190 20ms 85ms 12.9min 82.8d 0 book_staleness last_trade_price c 51,292 48,803 9ms 40ms 276ms 5.0s 0 transport_latency_assumed last_trade_price e 51,325 381 45ms 126ms 1.7s 5.0s 0 transport_latency_assumed last_trade_price f 51,339 173 54ms 127ms 1.2s 6.7s 0 transport_latency_assumed last_trade_price g 51,146 39 94ms 238ms 5.8s 15.6s 0 transport_latency_assumed last_trade_price h 51,168 1,961 22ms 61ms 463ms 7.4s 0 transport_latency_assumed market_resolved c 1,749 1,698 5ms 10ms 104ms 58.7s 0 transport_latency_assumed market_resolved e 1,749 5 42ms 147ms 425ms 54.2s 0 transport_latency_assumed market_resolved f 1,749 5 52ms 148ms 444ms 53.8s 0 transport_latency_assumed market_resolved g 1,749 not meas. 96ms 256ms 733ms 56.7s 0 transport_latency_assumed market_resolved h 1,749 44 30ms 63ms 225ms 1.3min 0 transport_latency_assumed new_market c 1,839 904 172ms 22.5s 1.0min 1.7min 0 transport_latency_assumed new_market e 1,839 600 167ms 20.7s 43.8s 1.6min 0 transport_latency_assumed new_market f 1,839 242 229ms 21.1s 46.5s 7.4min 0 transport_latency_assumed new_market g 1,839 208 338ms 21.9s 46.7s 1.7min 0 transport_latency_assumed new_market h 1,839 880 152ms 18.8s 43.6s 1.5min 0 transport_latency_assumed price_change c 78,669,472 75,731,954 5ms 9ms 175ms 8.2s 0 transport_latency_assumed price_change e 78,569,744 366,220 39ms 51ms 334ms 5.5s 0 transport_latency_assumed price_change f 78,596,781 149,982 48ms 61ms 354ms 7.8s 0 transport_latency_assumed price_change g 78,561,670 15,564 80ms 115ms 788ms 15.6s 0 transport_latency_assumed price_change h 78,661,420 2,416,564 17ms 25ms 325ms 37.3s 0 transport_latency_assumed tick_size_change c 3,212 3,104 5ms 7ms 200ms 389ms 0 transport_latency_assumed tick_size_change e 3,212 20 39ms 43ms 245ms 588ms 0 transport_latency_assumed tick_size_change f 3,212 8 48ms 56ms 320ms 403ms 0 transport_latency_assumed tick_size_change g 3,212 not meas. 80ms 98ms 333ms 541ms 0 transport_latency_assumed tick_size_change h 3,212 80 17ms 26ms 415ms 3.9s 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-08/04/2026-09-08T04.parquet sha256sum 2026-09-08T04.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.