Hour audit: 2026-08-30T08
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-30T08 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-30T08:00:00.033168213+00:00 · last event 2026-08-30T08:59:59.999999052+00:00
VOLUME 89,986,062 rows · 879,561,595 bytes (838.82 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured a: 89,944,650 · h: 89,861,642 · e: 89,758,871 · c: 87,432,087 (each machine's own feed; these overlap and do not sum to the file)
supplied a: 8,973 (0.01%) · h: 202,043 (0.22%) · e: 89,757,178 (99.75%) · c: 17,868 (0.02%) (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 89,986,062 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 8b2c79659d8ac437be2e577bcc7e5afd62bd21464015725ab2ff38ac4d1ed46a
the corpus checksum ledger names this file with the same digest
joined 89,987,791 to merged 89,986,062, minus 1,729 (minus 0.0019%)
boundary drops 1,729 · 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-31T14:28:48Z 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,009,199 88,777,097 0-30 a8fb7905c2377810297ce6c4e62ff48769edb08dd46954a4820d84497839ba68 book 128,076 12,135,317 31-31 711e372e5b272d6b1b094f1740cf7125426ba61a11b6cbd288e14a65b56794fe last_trade_price 49,116 2,835,724 32-32 e4cbf5fa8cf44d9c2355e28905f05593e39086fbabf630cfc5c97fa755e8b709 market_resolved 452 73,615 33-33 5fe3aa1247940fab39375f5ff5a7a7380fa3663f8063e90761a5dd7a4fbcfff4 new_market 2,705 252,792 34-34 b09a60c23e5a876c82440fd6f0a3c3ba9184f59817e7285159750699b57223e6 price_change 81,794,810 774,396,079 35-347 17136014c2da4cc191a1da696682df9cf2e04222a591b01142ac26b6ebed84ec tick_size_change 1,704 62,290 348-348 57a74e992c0d85980f3875e1a48bff1ed18821530bb3303118084e2e1a132635 EVENT MIX count share price_change 81,794,810 90.90% best_bid_ask 8,009,199 8.90% book 128,076 0.14% last_trade_price 49,116 0.05% new_market 2,705 <0.01% tick_size_change 1,704 <0.01% market_resolved 452 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,009,318 8,009,199 119 65,541 PARTIAL book 128,114 128,076 38 13,068 PARTIAL last_trade_price 49,116 49,116 0 3,263 PARTIAL market_resolved 452 452 0 452 PARTIAL new_market 2,705 2,705 0 1,684 PARTIAL price_change 81,796,382 81,794,810 1,572 125,356 PARTIAL tick_size_change 1,704 1,704 0 426 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 8,005,028 342 40ms 47ms 374ms 13.9s 0 transport_latency_assumed best_bid_ask c 7,784,966 1,844 4ms 7ms 149ms 2.0s 0 transport_latency_assumed best_bid_ask e 7,998,819 7,998,706 42ms 82ms 783ms 24.1s 0 transport_latency_assumed best_bid_ask h 8,001,695 8,307 11ms 16ms 307ms 44.9s 0 transport_latency_assumed book a 108,981 6,167 57ms 1.7s 2.3h 73.9d 0 book_staleness book c 103,809 3,670 7ms 38ms 3.2min 73.9d 0 book_staleness book e 110,330 110,308 77ms 6.5s 3.6h 21.8d 0 book_staleness book h 106,600 7,931 18ms 653ms 1.7h 73.7d 0 book_staleness last_trade_price a 49,065 5 52ms 706ms 3.8s 13.9s 0 transport_latency_assumed last_trade_price c 48,124 50 9ms 38ms 204ms 5.0s 0 transport_latency_assumed last_trade_price e 48,040 48,040 62ms 3.1s 9.7s 24.1s 0 transport_latency_assumed last_trade_price h 48,301 1,021 17ms 260ms 1.6s 9.1s 0 transport_latency_assumed market_resolved a 452 not meas. 42ms 352ms 556ms 45.6s 0 transport_latency_assumed market_resolved c 447 not meas. 4ms 6ms 34ms 42.5s 0 transport_latency_assumed market_resolved e 452 452 43ms 401ms 1.0s 45.6s 0 transport_latency_assumed market_resolved h 452 not meas. 12ms 44ms 228ms 42.8s 0 transport_latency_assumed new_market a 1,684 273 267ms 23.0s 35.4s 2.5min 0 transport_latency_assumed new_market c 1,683 400 110ms 23.5s 35.1s 1.0min 0 transport_latency_assumed new_market e 1,684 1,684 259ms 24.8s 34.0s 2.4min 0 transport_latency_assumed new_market h 1,684 348 153ms 22.9s 34.0s 55.9s 0 transport_latency_assumed price_change a 81,777,736 2,186 40ms 58ms 497ms 13.9s 0 transport_latency_assumed price_change c 79,491,378 11,904 4ms 7ms 163ms 2.9s 0 transport_latency_assumed price_change e 81,597,846 81,596,288 43ms 109ms 2.1s 24.1s 0 transport_latency_assumed price_change h 81,701,218 184,432 12ms 17ms 352ms 44.9s 0 transport_latency_assumed tick_size_change a 1,704 not meas. 40ms 44ms 131ms 143ms 0 transport_latency_assumed tick_size_change c 1,680 not meas. 4ms 6ms 15ms 23ms 0 transport_latency_assumed tick_size_change e 1,700 1,700 43ms 93ms 3.7s 5.3s 0 transport_latency_assumed tick_size_change h 1,692 4 12ms 16ms 34ms 52ms 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/08/2026-08-30T08.parquet sha256sum 2026-08-30T08.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.