Hour audit: 2026-08-30T20
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-30T20 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T20:00:00.038623697+00:00 · last event 2026-08-30T20:59:59.999981121+00:00
VOLUME 106,195,313 rows · 1,114,525,894 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 105,825,528 · h: 105,790,634 · e: 105,067,670 · a: 101,634,375 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 23,007 (0.02%) · h: 757,738 (0.71%) · e: 105,066,512 (98.94%) · a: 348,056 (0.33%) (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 106,195,313 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 71e1f29c1fc4bc3b51dfcd97eadf12d906e11c914424970cd3e2adf7d235ba2c
the corpus checksum ledger names this file with the same digest
joined 106,196,487 to merged 106,195,313, minus 1,174 (minus 0.0011%)
boundary drops 1,174 · 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-08-30T22:54:55Z as aceh
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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,804,700 98,750,574 0-33 a01a046fc202885a98cd3047652ec010d74e3bea740bf00ccea3ee2d29aa5325 book 518,756 53,346,748 34-35 fb63596df88042a30f307097a96cea5d27d7a47444888a921e07116ed01eb9e2 last_trade_price 79,458 4,468,892 36-36 766513eed843db9fd9a61948d981ab5fc087e504bc8732fe8e771e66deb74683 market_resolved 2,120 326,352 37-37 a9aefb29da29e1982fc9b5999f1caee3c71daaf14ae40131545e4a13f72998a6 new_market 1,551 161,697 38-38 6f5face234e3ec080b09bb4703ece6c6710e53895be6ee80a7fa77320726ecf2 price_change 96,781,868 956,015,473 39-408 2983d9f75cf6dea698aba5115a76d1b78806ca91da7c61313d7759c9eb75f494 tick_size_change 6,860 246,544 409-409 df044879407ec5cade7b6c616e5a19ef3a37a7336fb6ef2f9709e5ddd39969fa EVENT MIX count share price_change 96,781,868 91.14% best_bid_ask 8,804,700 8.29% book 518,756 0.49% last_trade_price 79,458 0.07% tick_size_change 6,860 <0.01% market_resolved 2,120 <0.01% new_market 1,551 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,804,766 8,804,700 66 70,666 PARTIAL book 518,756 518,756 0 172,131 PARTIAL last_trade_price 79,458 79,458 0 4,490 PARTIAL market_resolved 2,120 2,120 0 2,046 PARTIAL new_market 1,551 1,551 0 1,059 PARTIAL price_change 96,782,976 96,781,868 1,108 123,332 PARTIAL tick_size_change 6,860 6,860 0 1,715 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,439,327 54 39ms 57ms 400ms 15.2s 0 transport_latency_assumed best_bid_ask c 8,804,196 956 5ms 8ms 113ms 2.8s 0 transport_latency_assumed best_bid_ask e 8,754,449 8,754,383 44ms 154ms 6.0s 23.8s 0 transport_latency_assumed best_bid_ask h 8,803,392 49,307 13ms 20ms 170ms 33.7s 0 transport_latency_assumed book a 500,340 344,105 48.3s 1.8h 26.9d 92.9d 0 book_staleness book c 164,699 1,167 7ms 24ms 676ms 31.9d 0 book_staleness book e 168,688 168,688 79ms 4.2s 21.6min 2.8d 0 book_staleness book h 164,819 4,796 20ms 106ms 1.5s 74.4d 0 book_staleness last_trade_price a 74,961 2 53ms 1.2s 8.7s 15.1s 0 transport_latency_assumed last_trade_price c 79,430 10 10ms 40ms 224ms 5.0s 0 transport_latency_assumed last_trade_price e 77,854 77,854 67ms 2.5s 13.8s 23.9s 0 transport_latency_assumed last_trade_price h 79,400 1,592 19ms 95ms 741ms 13.3s 0 transport_latency_assumed market_resolved a 2,045 50 40ms 178ms 3.8min 4.9min 0 transport_latency_assumed market_resolved c 2,046 not meas. 4ms 9ms 57.0s 59.6s 0 transport_latency_assumed market_resolved e 2,046 2,046 44ms 223ms 58.2s 1.0min 0 transport_latency_assumed market_resolved h 2,046 24 13ms 35ms 358ms 1.0min 0 transport_latency_assumed new_market a 1,059 39 230ms 14.1s 29.2s 12.5min 0 transport_latency_assumed new_market c 1,059 238 85ms 19.0s 30.3s 47.1min 0 transport_latency_assumed new_market e 1,059 1,059 247ms 17.0s 35.3s 18.6min 0 transport_latency_assumed new_market h 1,059 215 133ms 15.3s 27.1s 28.7s 0 transport_latency_assumed price_change a 92,610,015 3,806 40ms 77ms 1.0s 15.4s 0 transport_latency_assumed price_change c 96,767,238 20,636 5ms 9ms 142ms 3.3s 0 transport_latency_assumed price_change e 96,056,734 96,055,642 44ms 225ms 7.5s 24.0s 0 transport_latency_assumed price_change h 96,733,058 701,784 13ms 22ms 220ms 37.3s 0 transport_latency_assumed tick_size_change a 6,628 not meas. 39ms 44ms 108ms 406ms 0 transport_latency_assumed tick_size_change c 6,860 not meas. 4ms 7ms 25ms 232ms 0 transport_latency_assumed tick_size_change e 6,840 6,840 44ms 119ms 947ms 12.9s 0 transport_latency_assumed tick_size_change h 6,860 20 13ms 17ms 37ms 138ms 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-08-30/20/2026-08-30T20.parquet sha256sum 2026-08-30T20.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.