Hour audit: 2026-09-03T01
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-03T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T01:00:00.033713430+00:00 · last event 2026-09-03T01:59:59.999958880+00:00
VOLUME 109,038,487 rows · 1,125,340,516 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 108,235,206 · c: 108,224,355 · e: 107,734,819 · b: 99,622,841 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 523,602 (0.48%) · c: 30,271 (0.03%) · e: 107,733,309 (98.80%) · b: 751,305 (0.69%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 109,038,487 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 47a88b2eec68a55a8992a3ec1dcbf0a5ae9e4821fd5e9689276f2b256c15e4e9
the corpus checksum ledger names this file with the same digest
joined 109,040,659 to merged 109,038,487, minus 2,172 (minus 0.0020%)
boundary drops 2,172 · 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-03T03:39:45Z 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 12,136,136 133,940,154 0-46 11eca28ce4fe47ad1c87094916166044f04b5d8c4a10afd42bd9f9d5e04c2c10 book 921,976 65,168,491 47-50 a4a4f07de9b075f42e7fb27ed2cc0c56041606caf90580568925fa43dd8922cc last_trade_price 59,816 3,326,475 51-51 95ad8a29b7ab6cfc04c109b0558611645f1b6fb9d9b0aae9effeb9ae60610081 market_resolved 918 129,127 52-52 1ee92fdfcadbe53b708818c8bf8a44b094d5f9c9d2df83b71bfc06c1741d822d new_market 1,053 108,938 53-53 466f50482df4a69ab248ef6a9a9e0f059d6a18bbc5661aad75c789ada9c7f8af price_change 95,914,792 921,287,064 54-419 79ac8a4598acb1f5efaeba1d45ff5c4f1dc4af8d2aa0444db9dfb90b7919675c tick_size_change 3,796 139,336 420-420 32a044c127d240297bf996cf32d19985d60ccd4ba3faf891dedbf9c2ff365a9f EVENT MIX count share price_change 95,914,792 87.96% best_bid_ask 12,136,136 11.13% book 921,976 0.85% last_trade_price 59,816 0.05% tick_size_change 3,796 <0.01% new_market 1,053 <0.01% market_resolved 918 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,136,318 12,136,136 182 1,188 FULL book 922,062 921,976 86 188,725 FULL last_trade_price 59,816 59,816 0 102 FULL market_resolved 918 918 0 1 FULL new_market 1,053 1,053 0 0 FULL price_change 95,916,696 95,914,792 1,904 466 FULL tick_size_change 3,796 3,796 0 102 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 11,116,071 74 56ms 91ms 592ms 22.7s 0 transport_latency_assumed best_bid_ask c 12,133,404 2,931 3ms 8ms 79ms 6.2s 0 transport_latency_assumed best_bid_ask e 12,108,960 12,108,836 43ms 114ms 1.2s 29.2s 0 transport_latency_assumed best_bid_ask h 12,130,109 24,295 18ms 30ms 172ms 7.6s 0 transport_latency_assumed book b 883,548 747,370 3.5min 7.3h 31.4d 96.1d 0 book_staleness book c 132,154 8,732 6ms 91ms 5.6h 96.1d 0 book_staleness book e 126,413 126,379 117ms 8.3s 5.8h 11.5d 0 book_staleness book h 157,524 39,495 40ms 15.4min 11.5d 96.1d 0 book_staleness last_trade_price b 54,188 5 100ms 4.0s 13.3s 22.7s 0 transport_latency_assumed last_trade_price c 59,789 30 9ms 40ms 204ms 5.0s 0 transport_latency_assumed last_trade_price e 57,232 57,232 91ms 4.9s 14.9s 29.2s 0 transport_latency_assumed last_trade_price h 59,759 2,549 28ms 282ms 1.1s 6.5s 0 transport_latency_assumed market_resolved b 879 124 65ms 7.3min 10.9min 11.4min 0 transport_latency_assumed market_resolved c 790 3 3ms 8ms 230ms 1.0min 0 transport_latency_assumed market_resolved e 790 790 44ms 380ms 1.1s 2.3s 0 transport_latency_assumed market_resolved h 790 1 18ms 111ms 284ms 1.0min 0 transport_latency_assumed new_market b 737 86 240ms 33.7s 7.9min 8.0min 0 transport_latency_assumed new_market c 682 91 69ms 15.9s 26.3s 60.0s 0 transport_latency_assumed new_market e 682 682 208ms 18.5s 28.0s 1.0min 0 transport_latency_assumed new_market h 682 194 130ms 14.0s 29.2s 1.3min 0 transport_latency_assumed price_change b 87,564,030 3,646 56ms 120ms 3.9s 22.8s 0 transport_latency_assumed price_change c 95,893,740 18,484 3ms 7ms 101ms 6.8s 0 transport_latency_assumed price_change e 95,436,946 95,435,594 43ms 140ms 4.9s 29.3s 0 transport_latency_assumed price_change h 95,882,546 457,068 18ms 32ms 289ms 7.6s 0 transport_latency_assumed tick_size_change b 3,388 not meas. 56ms 124ms 591ms 1.0s 0 transport_latency_assumed tick_size_change c 3,796 not meas. 3ms 8ms 163ms 512ms 0 transport_latency_assumed tick_size_change e 3,796 3,796 43ms 121ms 691ms 7.7s 0 transport_latency_assumed tick_size_change h 3,796 not meas. 18ms 37ms 304ms 5.3s 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-03/01/2026-09-03T01.parquet sha256sum 2026-09-03T01.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.