Hour audit: 2026-09-05T06
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-05T06 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T06:00:00.026531620+00:00 · last event 2026-09-05T06:59:59.999925098+00:00
VOLUME 93,114,691 rows · 922,769,392 bytes (880.02 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured b: 92,706,530 · h: 92,690,881 · e: 92,687,586 · c: 82,902,927 (each machine's own feed; these overlap and do not sum to the file)
supplied b: 14,675 (0.02%) · h: 24,388 (0.03%) · e: 92,686,410 (99.54%) · c: 389,218 (0.42%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 93,114,691 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 066855adc28868ae24c3abcb21d8340f232d9e05dd5aee36fc8e0489bf8af1a7
the corpus checksum ledger names this file with the same digest
joined 93,116,225 to merged 93,114,691, minus 1,534 (minus 0.0016%)
boundary drops 1,534 · 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-05T07:51:42Z 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,524,389 93,123,558 0-32 f3f8c593c60e27f710145c3f77c21e1e2f2909db5608ab617ffd9119f1ff57e3 book 507,333 54,525,205 33-34 595c6b014e8a68b16641cc76165a6b524c27a381cd6eb4a73a1014591e01bc10 last_trade_price 53,407 2,985,997 35-35 65bc8448af1e3a0e7048a774b24121c12ed96b3436877ba958197c474c4c89e9 market_resolved 740 112,905 36-36 c3dd23497ff3bd2fd701a74ee264600d0af3d23fb5fcd45474820b9d887e66d9 new_market 704 78,428 37-37 10751e4172911807dbb27398cd62ac6aa017fc4c45618e5ac50ba6eff0b2c50b price_change 84,026,194 770,809,835 38-358 da6909ea5fe05612ee431f56240dc51ed00059192b35f14f7f56b371cf3e5511 tick_size_change 1,924 71,074 359-359 dc8560e4d7ec36268be76a502cba49d7f91cf7c8f679597504878d094c13d9e6 EVENT MIX count share price_change 84,026,194 90.24% best_bid_ask 8,524,389 9.15% book 507,333 0.54% last_trade_price 53,407 0.06% tick_size_change 1,924 <0.01% market_resolved 740 <0.01% new_market 704 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,524,483 8,524,389 94 1,181 FULL book 507,347 507,333 14 186,470 FULL last_trade_price 53,407 53,407 0 203 FULL market_resolved 740 740 0 0 FULL new_market 704 704 0 0 FULL price_change 84,027,620 84,026,194 1,426 886 FULL tick_size_change 1,924 1,924 0 71 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,522,322 18 55ms 67ms 134ms 2.4s 0 transport_latency_assumed best_bid_ask c 7,549,789 569 3ms 6ms 35ms 4.5s 0 transport_latency_assumed best_bid_ask e 8,522,627 8,522,545 41ms 46ms 154ms 1.8s 0 transport_latency_assumed best_bid_ask h 8,523,418 1,257 18ms 20ms 65ms 8.3s 0 transport_latency_assumed book b 130,745 10,603 58ms 1.6min 5.4d 98.3d 0 book_staleness book c 479,266 379,322 1.7min 8.9h 32.3d 98.3d 0 book_staleness book e 116,038 116,038 43ms 93ms 9.3h 45.5d 0 book_staleness book h 111,330 1,370 20ms 31ms 2.6s 15.9h 0 book_staleness last_trade_price b 53,382 4 61ms 92ms 333ms 5.0s 0 transport_latency_assumed last_trade_price c 47,013 1 8ms 32ms 169ms 5.0s 0 transport_latency_assumed last_trade_price e 53,346 53,346 47ms 76ms 289ms 5.0s 0 transport_latency_assumed last_trade_price h 53,354 56 22ms 48ms 222ms 5.7s 0 transport_latency_assumed market_resolved b 696 not meas. 57ms 219ms 52.8s 53.7s 0 transport_latency_assumed market_resolved c 702 43 4ms 11ms 8.4min 9.6min 0 transport_latency_assumed market_resolved e 696 696 43ms 189ms 46.3s 47.3s 0 transport_latency_assumed market_resolved h 696 1 18ms 60ms 43.3s 1.0min 0 transport_latency_assumed new_market b 521 24 143ms 12.6s 54.9s 1.5min 0 transport_latency_assumed new_market c 521 63 41ms 12.0s 58.5s 4.3min 0 transport_latency_assumed new_market e 521 521 87ms 14.4s 53.0s 1.3min 0 transport_latency_assumed new_market h 521 96 98ms 16.7s 48.3s 1.0min 0 transport_latency_assumed price_change b 83,996,940 4,026 55ms 67ms 152ms 3.6s 0 transport_latency_assumed price_change c 74,823,996 9,220 3ms 6ms 41ms 4.5s 0 transport_latency_assumed price_change e 83,992,434 83,991,340 41ms 50ms 173ms 2.3s 0 transport_latency_assumed price_change h 83,999,638 21,608 18ms 21ms 75ms 8.3s 0 transport_latency_assumed tick_size_change b 1,924 not meas. 56ms 68ms 492ms 592ms 0 transport_latency_assumed tick_size_change c 1,640 not meas. 4ms 7ms 334ms 586ms 0 transport_latency_assumed tick_size_change e 1,924 1,924 41ms 88ms 355ms 582ms 0 transport_latency_assumed tick_size_change h 1,924 not meas. 18ms 30ms 289ms 5.1s 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-05/06/2026-09-05T06.parquet sha256sum 2026-09-05T06.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.