Hour audit: 2026-09-02T12
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-02T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-02T12:00:00.037897772+00:00 · last event 2026-09-02T12:59:59.999964078+00:00
VOLUME 99,601,650 rows · 1,027,847,430 bytes (980.23 MiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 99,257,917 · c: 99,250,377 · e: 98,888,686 · b: 98,010,043 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 495,611 (0.50%) · c: 128,918 (0.13%) · e: 98,887,492 (99.28%) · b: 89,629 (0.09%) (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 99,601,650 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 14247030e7cae327e3f38c916c8bb928afa89c287dbf7740c959187a7b08f5ae
the corpus checksum ledger names this file with the same digest
joined 99,603,422 to merged 99,601,650, minus 1,772 (minus 0.0018%)
boundary drops 1,772 · 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-02T14:31:21Z 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,835,099 100,812,046 0-33 7a7cb57ef55a75563c263e63975b18d03ca104501f73f1eaff64b77fcad4f661 book 608,885 53,361,832 34-36 2b69f1bacac1d0d2631c4b89b18d6754a2c0d6fcae6a2a17a93a819ff91dd855 last_trade_price 68,410 3,870,055 37-37 fc7341f8bf1af7880babe157323a2a1a471d20ef12f657b0598f287e19577b62 market_resolved 1,817 292,219 38-38 eacfaa68fc5c330e12815b7d13602b0ce263c1f979d4b696c0677fc15cc1d3f6 new_market 1,227 124,847 39-39 89dae6f39a808b253a8d61ba016eac6f0752584b0cff22e81be4a2bc475f2bbc price_change 90,082,476 868,112,939 40-383 5b34eead6ea9100bbc4b88e9e45e3cf6643581cc111acc07ebd9ffc6ba7b4616 tick_size_change 3,736 137,253 384-384 c33832680c8497506e8bcffc1e466499b3b49d41c2b27c9595a5b97f7889a209 EVENT MIX count share price_change 90,082,476 90.44% best_bid_ask 8,835,099 8.87% book 608,885 0.61% last_trade_price 68,410 0.07% tick_size_change 3,736 <0.01% market_resolved 1,817 <0.01% new_market 1,227 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,835,235 8,835,099 136 251 FULL book 609,473 608,885 588 143,293 FULL last_trade_price 68,410 68,410 0 2 FULL market_resolved 1,817 1,817 0 8 FULL new_market 1,227 1,227 0 0 FULL price_change 90,083,524 90,082,476 1,048 38 FULL tick_size_change 3,736 3,736 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,752,574 36 53ms 89ms 2.9s 23.3s 0 transport_latency_assumed best_bid_ask c 8,832,999 2,051 4ms 8ms 90ms 13.8s 0 transport_latency_assumed best_bid_ask e 8,822,771 8,822,647 44ms 87ms 776ms 19.6s 0 transport_latency_assumed best_bid_ask h 8,831,608 10,365 18ms 26ms 208ms 8.1s 0 transport_latency_assumed book b 254,359 89,489 3.9s 2.5h 24.9d 95.6d 0 book_staleness book c 281,175 108,533 260ms 2.6h 24.9d 95.6d 0 book_staleness book e 265,528 265,330 4.1s 2.4h 24.9d 95.6d 0 book_staleness book h 301,896 145,533 5.8s 3.1h 24.9d 95.6d 0 book_staleness last_trade_price b 63,321 6 78ms 3.5s 13.2s 23.3s 0 transport_latency_assumed last_trade_price c 68,345 205 10ms 40ms 202ms 12.9s 0 transport_latency_assumed last_trade_price e 66,338 66,338 82ms 3.0s 14.4s 19.6s 0 transport_latency_assumed last_trade_price h 68,176 1,861 27ms 310ms 1.4s 7.4s 0 transport_latency_assumed market_resolved b 1,778 27 55ms 248ms 782ms 3.8s 0 transport_latency_assumed market_resolved c 1,786 1 4ms 10ms 60.0s 1.0min 0 transport_latency_assumed market_resolved e 1,786 1,786 45ms 259ms 59.5s 1.0min 0 transport_latency_assumed market_resolved h 1,786 3 19ms 93ms 1.0min 1.0min 0 transport_latency_assumed new_market b 825 37 122ms 13.8s 23.4s 1.4min 0 transport_latency_assumed new_market c 825 144 70ms 16.2s 23.5s 1.9min 0 transport_latency_assumed new_market e 825 825 296ms 18.0s 23.1s 1.6min 0 transport_latency_assumed new_market h 825 221 158ms 17.6s 22.4s 1.0min 0 transport_latency_assumed price_change b 88,933,450 34 53ms 132ms 4.9s 23.3s 0 transport_latency_assumed price_change c 90,061,511 17,984 4ms 8ms 128ms 14.2s 0 transport_latency_assumed price_change e 89,727,706 89,726,834 44ms 129ms 3.0s 19.6s 0 transport_latency_assumed price_change h 90,049,890 337,624 18ms 32ms 318ms 11.3s 0 transport_latency_assumed tick_size_change b 3,736 not meas. 53ms 123ms 841ms 4.9s 0 transport_latency_assumed tick_size_change c 3,736 not meas. 4ms 7ms 18ms 155ms 0 transport_latency_assumed tick_size_change e 3,732 3,732 44ms 110ms 243ms 525ms 0 transport_latency_assumed tick_size_change h 3,736 4 18ms 24ms 49ms 808ms 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-02/12/2026-09-02T12.parquet sha256sum 2026-09-02T12.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.