Hour audit: 2026-09-02T13
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-02T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-02T13:00:00.032804250+00:00 · last event 2026-09-02T13:59:59.999987735+00:00
VOLUME 104,195,718 rows · 1,102,732,399 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 103,548,275 · c: 103,541,744 · e: 103,053,848 · b: 102,111,113 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 772,770 (0.74%) · c: 204,894 (0.20%) · e: 103,052,079 (98.90%) · b: 165,975 (0.16%) (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 104,195,718 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 807e5f96dccc21dd63e78ae47e29deed142a86b1c9bfb5acdb6a6f46310c022d
the corpus checksum ledger names this file with the same digest
joined 104,198,124 to merged 104,195,718, minus 2,406 (minus 0.0023%)
boundary drops 2,406 · 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-02T16:02:15Z 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,815,470 101,157,074 0-33 c292df0ecf7d0047899b85c533843e5b54359fe350f5871b0c4bf3c00782c354 book 1,141,736 78,066,922 34-38 17c99b9a39a1b6c2ce31f00a24d8befae182bf977fb2de43a4974cbc691c1c5e last_trade_price 76,472 4,257,840 39-39 f117bffc98489d995351153a04ed9b2e10eb4d09194ef043c4895aedbe042191 market_resolved 1,101 180,517 40-40 419c49c69d150508c7431026c53e8ca7fa4bb45b2880c9434104b5ff7a7f93ba new_market 735 78,592 41-41 1d21d89807c4985e2fc855d583a4e648771f036a2d90828e2cc286a37a164592 price_change 94,156,952 917,684,312 42-401 967346bd580c98d953e8b4c37d3b282db8fe6c31542353a374f97197606ad4b0 tick_size_change 3,252 118,405 402-402 b4e6584c321d78c0a1dfd349b03cbe94e9f6414418a7d585f56ea95742c7a3e9 EVENT MIX count share price_change 94,156,952 90.37% best_bid_ask 8,815,470 8.46% book 1,141,736 1.10% last_trade_price 76,472 0.07% tick_size_change 3,252 <0.01% market_resolved 1,101 <0.01% new_market 735 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,815,626 8,815,470 156 132 FULL book 1,141,972 1,141,736 236 84,494 FULL last_trade_price 76,472 76,472 0 3 FULL market_resolved 1,101 1,101 0 18 FULL new_market 735 735 0 0 FULL price_change 94,158,966 94,156,952 2,014 26 FULL tick_size_change 3,252 3,252 0 4 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 8,741,243 60 52ms 90ms 1.8s 22.0s 0 transport_latency_assumed best_bid_ask c 8,813,538 647 4ms 8ms 57ms 5.3s 0 transport_latency_assumed best_bid_ask e 8,795,158 8,795,031 44ms 90ms 1.3s 29.8s 0 transport_latency_assumed best_bid_ask h 8,812,451 19,732 18ms 26ms 132ms 7.3s 0 transport_latency_assumed book b 472,642 165,727 55.0s 5.6h 25.1d 95.6d 0 book_staleness book c 513,821 196,581 54.7s 5.7h 25.9d 95.6d 0 book_staleness book e 527,435 527,349 1.0min 5.5h 25.0d 95.6d 0 book_staleness book h 531,692 252,079 57.8s 5.9h 26.6d 95.6d 0 book_staleness last_trade_price b 69,488 6 81ms 3.4s 12.6s 22.0s 0 transport_latency_assumed last_trade_price c 76,371 24 10ms 37ms 175ms 4.9s 0 transport_latency_assumed last_trade_price e 73,507 73,507 72ms 3.5s 13.3s 29.1s 0 transport_latency_assumed last_trade_price h 76,408 2,935 25ms 214ms 1.3s 5.0s 0 transport_latency_assumed market_resolved b 1,074 9 54ms 455ms 59.8s 1.0min 0 transport_latency_assumed market_resolved c 1,092 not meas. 4ms 18ms 46.1s 49.8s 0 transport_latency_assumed market_resolved e 1,092 1,092 44ms 431ms 50.7s 54.7s 0 transport_latency_assumed market_resolved h 1,092 not meas. 18ms 149ms 44.7s 48.5s 0 transport_latency_assumed new_market b 490 69 248ms 16.9s 45.2s 1.3min 0 transport_latency_assumed new_market c 490 56 48ms 11.2s 18.8s 1.3min 0 transport_latency_assumed new_market e 490 490 198ms 14.3s 24.0s 1.3min 0 transport_latency_assumed new_market h 490 120 100ms 15.7s 37.5s 1.4min 0 transport_latency_assumed price_change b 92,822,940 104 53ms 132ms 5.2s 23.7s 0 transport_latency_assumed price_change c 94,133,180 7,586 4ms 9ms 85ms 8.6s 0 transport_latency_assumed price_change e 93,652,914 93,651,358 45ms 132ms 4.4s 29.8s 0 transport_latency_assumed price_change h 94,122,890 497,904 18ms 31ms 260ms 7.3s 0 transport_latency_assumed tick_size_change b 3,236 not meas. 53ms 125ms 546ms 1.3s 0 transport_latency_assumed tick_size_change c 3,252 not meas. 5ms 10ms 43ms 259ms 0 transport_latency_assumed tick_size_change e 3,252 3,252 45ms 74ms 165ms 441ms 0 transport_latency_assumed tick_size_change h 3,252 not meas. 18ms 30ms 69ms 261ms 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/13/2026-09-02T13.parquet sha256sum 2026-09-02T13.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.