Hour audit: 2026-09-03T16
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-03T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-03T16:00:00.021102487+00:00 · last event 2026-09-03T16:59:59.999939093+00:00
VOLUME 112,072,991 rows · 1,186,391,525 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES bceh — 4 machines contributed rows
captured h: 111,248,043 · c: 111,219,053 · e: 110,408,005 · b: 101,631,408 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 946,791 (0.84%) · c: 38,474 (0.03%) · e: 110,406,217 (98.51%) · b: 681,509 (0.61%) (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 112,072,991 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 a12c2f6cb937857ed7213695cd90234fd04fc6c21fff848a62baae2cc044e413
the corpus checksum ledger names this file with the same digest
joined 112,075,286 to merged 112,072,991, minus 2,295 (minus 0.0020%)
boundary drops 2,295 · 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-03T18:00:24Z 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 10,520,164 120,611,896 0-40 9fdb97bc50f771af1fb73aeb655e23f661c0680712facb33781c66dbd47a50ec book 1,045,209 74,328,263 41-44 121dabffc57262a88e522442405237b84ec9f30e5f32b232dafa69363f2da1dd last_trade_price 85,698 4,691,279 45-45 200bc58089d41f0528cef6bedd9ac13706635dd88d27e04fb5408e896f282da8 market_resolved 1,923 233,611 46-46 b35ad231b4b9e3d8ec0d056d5dc85b9d83042eff25927dd7efe7decbe48749b5 new_market 1,155 121,105 47-47 c4688b475deb906aa5d5a2c5575e0c57ad2df709a1bce0f0ebe897d53c220847 price_change 100,414,906 984,986,852 48-431 b14cd73d4f6ee5fa31f9cfb12bf0ceb678c16c3830aa54ff97d9b06c86c097fd tick_size_change 3,936 141,765 432-432 2ebc3e6a26753881d6071e57134485b9e288ac7fe95d04c44d72edb138c10be4 EVENT MIX count share price_change 100,414,906 89.60% best_bid_ask 10,520,164 9.39% book 1,045,209 0.93% last_trade_price 85,698 0.08% tick_size_change 3,936 <0.01% market_resolved 1,923 <0.01% new_market 1,155 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,520,273 10,520,164 109 937 FULL book 1,045,421 1,045,209 212 183,503 FULL last_trade_price 85,698 85,698 0 161 FULL market_resolved 1,923 1,923 0 42 FULL new_market 1,155 1,155 0 0 FULL price_change 100,416,880 100,414,906 1,974 380 FULL tick_size_change 3,936 3,936 0 96 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask b 9,631,122 8 50ms 74ms 417ms 32.7s 0 transport_latency_assumed best_bid_ask c 10,519,618 898 20ms 31ms 94ms 2.1s 0 transport_latency_assumed best_bid_ask e 10,506,510 10,506,434 42ms 77ms 633ms 18.9s 0 transport_latency_assumed best_bid_ask h 10,518,418 12,824 18ms 28ms 130ms 8.5s 0 transport_latency_assumed book b 930,363 680,562 2.3min 4.2h 31.1d 96.8d 0 book_staleness book c 214,409 32,370 26ms 2.8min 8.1d 96.8d 0 book_staleness book e 269,159 269,131 365ms 1.7h 12.1d 89.0d 0 book_staleness book h 240,570 63,146 39ms 36.1min 12.1d 96.8d 0 book_staleness last_trade_price b 76,026 9 74ms 3.1s 15.4s 32.7s 0 transport_latency_assumed last_trade_price c 85,655 13 27ms 53ms 173ms 4.4s 0 transport_latency_assumed last_trade_price e 82,965 82,965 63ms 2.7s 13.4s 18.8s 0 transport_latency_assumed last_trade_price h 85,652 2,711 26ms 117ms 601ms 8.4s 0 transport_latency_assumed market_resolved b 1,737 483 110ms 8.2min 10.1min 12.4min 0 transport_latency_assumed market_resolved c 1,412 23 25ms 32ms 57.6s 1.0min 0 transport_latency_assumed market_resolved e 1,412 1,412 44ms 345ms 50.6s 1.2min 0 transport_latency_assumed market_resolved h 1,412 5 20ms 127ms 50.8s 53.6s 0 transport_latency_assumed new_market b 847 121 246ms 4.1min 9.4min 10.9min 0 transport_latency_assumed new_market c 783 74 67ms 13.9s 1.7min 2.6min 0 transport_latency_assumed new_market e 783 783 209ms 14.9s 31.3s 3.4min 0 transport_latency_assumed new_market h 783 177 112ms 13.3s 1.7min 4.0min 0 transport_latency_assumed price_change b 90,987,753 326 51ms 114ms 4.6s 32.8s 0 transport_latency_assumed price_change c 100,393,240 5,096 20ms 32ms 142ms 5.8s 0 transport_latency_assumed price_change e 99,543,248 99,541,564 42ms 135ms 5.1s 19.0s 0 transport_latency_assumed price_change h 100,397,272 867,920 19ms 35ms 231ms 8.8s 0 transport_latency_assumed tick_size_change b 3,560 not meas. 50ms 61ms 148ms 1.4s 0 transport_latency_assumed tick_size_change c 3,936 not meas. 20ms 30ms 48ms 91ms 0 transport_latency_assumed tick_size_change e 3,928 3,928 42ms 92ms 136ms 1.0s 0 transport_latency_assumed tick_size_change h 3,936 8 18ms 24ms 56ms 177ms 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/16/2026-09-03T16.parquet sha256sum 2026-09-03T16.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.