Hour audit: 2026-08-30T02
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-30T02 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T02:00:00.034133309+00:00 · last event 2026-08-30T02:59:59.999979814+00:00
VOLUME 114,717,395 rows · 1,192,665,117 bytes (1.11 GiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 114,025,672 · h: 113,890,105 · e: 113,841,485 · a: 105,746,785 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 132,361 (0.12%) · h: 62,263 (0.05%) · e: 113,840,219 (99.24%) · a: 682,552 (0.59%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 114,717,395 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 bc85a10a00ed625e5de1fc37e00eee813a9b4214764e59075c12e28bf6558ff2
the corpus checksum ledger names this file with the same digest
joined 114,718,745 to merged 114,717,395, minus 1,350 (minus 0.0012%)
boundary drops 1,350 · 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-30T05:42:32Z 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 10,526,252 115,749,914 0-40 b004aa79370f1e3b62975a911b755c6785c39f09530dca467d2df5f3e6b597c4 book 809,870 58,618,399 41-44 8b64c5fbd4dd8cb0d830f403ed34c35ca94ed5e9285d9f8edf2b045c725dbc10 last_trade_price 55,341 3,101,566 45-45 097cfe6f5bd8a0bd41d776ad6e00eb93a77df538779de88462ca7cadae45165e market_resolved 1,815 268,129 46-46 baf37fc39b8af87d1e1cd80ab468571806809d56cc979cc87544a64300312810 new_market 517 54,957 47-47 c94fe8d2b3510fdceb737bfa87ec4e32cfdb3172e622dd65d5efd57579352c81 price_change 103,317,788 1,013,355,095 48-442 d56f6b819bd5564bed7939b5bbcc0abd10bbbc77f5b3620fa85c1b94555fdd79 tick_size_change 5,812 208,390 443-443 a13786386a5903cd0ba5dfc295286c9a3159727451457002032af99b4a0503d8 EVENT MIX count share price_change 103,317,788 90.06% best_bid_ask 10,526,252 9.18% book 809,870 0.71% last_trade_price 55,341 0.05% tick_size_change 5,812 <0.01% market_resolved 1,815 <0.01% new_market 517 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,526,362 10,526,252 110 68,018 PARTIAL book 809,932 809,870 62 171,761 PARTIAL last_trade_price 55,341 55,341 0 3,226 PARTIAL market_resolved 1,815 1,815 0 1,664 PARTIAL new_market 517 517 0 348 PARTIAL price_change 103,318,966 103,317,788 1,178 125,917 PARTIAL tick_size_change 5,812 5,812 0 1,453 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 9,727,414 8 39ms 46ms 185ms 9.9s 0 transport_latency_assumed best_bid_ask c 10,526,102 294 4ms 7ms 39ms 1.1s 0 transport_latency_assumed best_bid_ask e 10,521,731 10,521,623 43ms 91ms 1.4s 17.4s 0 transport_latency_assumed best_bid_ask h 10,525,818 4,327 12ms 22ms 79ms 5.6s 0 transport_latency_assumed book a 794,042 681,838 1.8min 8.1h 27.6d 92.2d 0 book_staleness book c 120,782 7,446 6ms 48ms 4.8h 73.7d 0 book_staleness book e 114,648 114,646 72ms 3.4s 3.9min 21.5d 0 book_staleness book h 117,976 5,940 19ms 145ms 1.3h 73.7d 0 book_staleness last_trade_price a 51,756 not meas. 55ms 1.4s 6.1s 8.1s 0 transport_latency_assumed last_trade_price c 55,328 2 9ms 35ms 158ms 5.0s 0 transport_latency_assumed last_trade_price e 54,734 54,734 69ms 2.8s 9.3s 17.4s 0 transport_latency_assumed last_trade_price h 55,316 605 19ms 82ms 586ms 5.0s 0 transport_latency_assumed market_resolved a 1,726 122 42ms 307ms 9.1min 10.1min 0 transport_latency_assumed market_resolved c 1,664 25 4ms 7ms 97ms 53.1s 0 transport_latency_assumed market_resolved e 1,664 1,664 43ms 207ms 56.7s 1.2min 0 transport_latency_assumed market_resolved h 1,664 4 13ms 53ms 58.6s 1.0min 0 transport_latency_assumed new_market a 380 52 158ms 17.5s 7.4min 7.4min 0 transport_latency_assumed new_market c 348 42 48ms 13.1s 29.2s 1.2min 0 transport_latency_assumed new_market e 348 348 183ms 16.7s 1.0min 3.7min 0 transport_latency_assumed new_market h 348 75 60ms 10.0s 40.7s 1.4min 0 transport_latency_assumed price_change a 95,166,027 532 39ms 56ms 467ms 12.4s 0 transport_latency_assumed price_change c 103,315,636 124,552 4ms 7ms 47ms 1.7s 0 transport_latency_assumed price_change e 103,142,548 103,141,392 43ms 136ms 2.6s 17.4s 0 transport_latency_assumed price_change h 103,183,171 51,312 12ms 24ms 95ms 5.7s 0 transport_latency_assumed tick_size_change a 5,440 not meas. 39ms 44ms 143ms 886ms 0 transport_latency_assumed tick_size_change c 5,812 not meas. 4ms 7ms 28ms 234ms 0 transport_latency_assumed tick_size_change e 5,812 5,812 44ms 117ms 1.5s 6.4s 0 transport_latency_assumed tick_size_change h 5,812 not meas. 12ms 19ms 61ms 456ms 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/02/2026-08-30T02.parquet sha256sum 2026-08-30T02.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.