Hour audit: 2026-09-05T15
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-05T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-05T15:00:00.056834677+00:00 · last event 2026-09-05T15:59:59.999985592+00:00
VOLUME 115,335,068 rows · 1,245,627,855 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 113,764,674 · h: 113,742,277 · f: 113,620,128 · g: 113,604,502 · c: 94,803,750 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 88,388 (0.08%) · h: 8,621 (0.01%) · f: 114,351 (0.10%) · g: 113,600,954 (98.50%) · c: 1,522,754 (1.32%) (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 115,335,068 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b3180dc53662704fbae05a8dd4b7ccb5ac561ec9fac0685746afb6af982255df
the corpus checksum ledger names this file with the same digest
joined 115,338,674 to merged 115,335,068, minus 3,606 (minus 0.0031%)
boundary drops 3,606 · 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-05T20:51:13Z as cefgh
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 9,446,756 111,567,995 0-36 0ff17b025637055bcfc00b40a75711da6259daaf91645cf9e6502c4a2bf5765a book 1,681,487 85,366,898 37-43 38c5a0a3155533c3fa9ec006b0d783f0d97d0aaeb0e8f3d533857896aa4237a9 last_trade_price 71,275 4,174,520 44-44 987e2e29d0c7a4ea63f71e996a95add5ddf848270e018504b0446a6de451e34c market_resolved 3,550 463,555 45-45 8a9c3c3f858ea97a6ecb06692602e2a53078c2aa5f96f5df311f0faa8bdc8ea7 new_market 1,098 118,463 46-46 f87f72848ac9c34cfb55f038a3b13bc2ae22cae4582b878a0949d37910c62210 price_change 104,111,162 1,041,911,971 47-444 5db0a3f8364af63a380deeb2ccd06a8d1c6eb312e1271ae1aab9dff11b4bccd3 tick_size_change 19,740 708,308 445-445 ce4d51f3660e056f513af3501bee485347e9ae92132c2b77c14ef9a6c9a36df9 EVENT MIX count share price_change 104,111,162 90.27% best_bid_ask 9,446,756 8.19% book 1,681,487 1.46% last_trade_price 71,275 0.06% tick_size_change 19,740 0.02% market_resolved 3,550 <0.01% new_market 1,098 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,447,042 9,446,756 286 3,037 FULL book 1,681,569 1,681,487 82 187,818 FULL last_trade_price 71,277 71,275 2 590 FULL market_resolved 3,550 3,550 0 38 FULL new_market 1,098 1,098 0 0 FULL price_change 104,114,398 104,111,162 3,236 1,899 FULL tick_size_change 19,740 19,740 0 1,076 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,807,834 392 6ms 11ms 94ms 7.5s 0 transport_latency_assumed best_bid_ask e 9,445,296 6,032 39ms 46ms 148ms 5.0s 0 transport_latency_assumed best_bid_ask f 9,434,443 6,106 47ms 62ms 281ms 5.0s 0 transport_latency_assumed best_bid_ask g 9,433,635 9,433,349 81ms 131ms 665ms 16.3s 0 transport_latency_assumed best_bid_ask h 9,445,786 877 18ms 25ms 118ms 7.5s 0 transport_latency_assumed book c 1,643,748 1,514,556 2.5min 13.1h 34.1d 98.7d 0 book_staleness book e 146,890 2,123 41ms 96ms 1.0s 34.2d 0 book_staleness book f 151,622 4,404 49ms 234ms 49.4min 23.9h 0 book_staleness book g 159,614 159,590 83ms 3.1s 6.9h 80.2d 0 book_staleness book h 147,073 814 21ms 49ms 776ms 80.2d 0 book_staleness last_trade_price c 58,988 4 11ms 41ms 269ms 5.0s 0 transport_latency_assumed last_trade_price e 71,187 732 45ms 92ms 754ms 5.0s 0 transport_latency_assumed last_trade_price f 69,987 641 52ms 129ms 1.2s 5.5s 0 transport_latency_assumed last_trade_price g 69,898 69,896 87ms 223ms 3.9s 16.3s 0 transport_latency_assumed last_trade_price h 71,170 2 23ms 61ms 441ms 5.0s 0 transport_latency_assumed market_resolved c 3,109 682 7ms 6.6min 13.0min 15.3min 0 transport_latency_assumed market_resolved e 2,818 not meas. 40ms 121ms 410ms 1.1min 0 transport_latency_assumed market_resolved f 2,818 30 47ms 116ms 437ms 1.0min 0 transport_latency_assumed market_resolved g 2,818 2,818 84ms 225ms 57.3s 1.0min 0 transport_latency_assumed market_resolved h 2,818 20 19ms 63ms 56.1s 1.0min 0 transport_latency_assumed new_market c 789 60 84ms 27.2s 7.3min 10.7min 0 transport_latency_assumed new_market e 769 80 127ms 19.6s 34.7s 10.3min 0 transport_latency_assumed new_market f 769 129 133ms 13.3s 26.8s 10.6min 0 transport_latency_assumed new_market g 769 769 241ms 12.7s 34.2s 1.4min 0 transport_latency_assumed new_market h 769 60 106ms 14.7s 31.7s 7.3min 0 transport_latency_assumed price_change c 85,273,846 7,060 6ms 12ms 123ms 8.4s 0 transport_latency_assumed price_change e 104,077,974 79,421 40ms 49ms 198ms 5.0s 0 transport_latency_assumed price_change f 103,940,749 103,041 47ms 71ms 343ms 5.0s 0 transport_latency_assumed price_change g 103,918,028 103,914,792 81ms 158ms 878ms 16.3s 0 transport_latency_assumed price_change h 104,054,921 6,848 18ms 28ms 153ms 8.3s 0 transport_latency_assumed tick_size_change c 15,436 not meas. 6ms 9ms 60ms 1.6s 0 transport_latency_assumed tick_size_change e 19,740 not meas. 39ms 43ms 74ms 492ms 0 transport_latency_assumed tick_size_change f 19,740 not meas. 49ms 128ms 265ms 802ms 0 transport_latency_assumed tick_size_change g 19,740 19,740 89ms 259ms 663ms 13.1s 0 transport_latency_assumed tick_size_change h 19,740 not meas. 18ms 21ms 52ms 379ms 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/15/2026-09-05T15.parquet sha256sum 2026-09-05T15.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.