Hour audit: 2026-08-31T03
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-31T03 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T03:00:00.035343090+00:00 · last event 2026-08-31T03:59:59.999933366+00:00
VOLUME 75,580,813 rows · 730,917,627 bytes (697.06 MiB) · 7 products, all holding rows
WITNESSES aceh — 4 machines contributed rows
captured c: 75,565,090 · a: 75,548,080 · h: 75,477,153 · e: 75,141,518 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 33,010 (0.04%) · a: 1,802 (0.00%) · h: 405,505 (0.54%) · e: 75,140,496 (99.42%) (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 75,580,813 rows exactly, so those pairs supplied none
5 expected (abceh), 1 contributed nothing: b
INTEGRITY sha256 68e8d01fee49f63b9c48d21929fc0164f69c19928d76156e70bcbffa3e50a1ac
the corpus checksum ledger names this file with the same digest
joined 75,581,835 to merged 75,580,813, minus 1,022 (minus 0.0014%)
boundary drops 1,022 · 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-31T04:49:28Z 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 7,291,518 79,636,750 0-27 48ab41a12ac414bf81ea790175a7f600e2c4b273f03cd067a1dc78e7301c3c5f book 127,780 11,737,055 28-28 449a933453bcd47056bf3fbe4ce2654690830076b3714b37602809d033f4547b last_trade_price 55,281 3,027,557 29-29 937ef47df0c0803c6ab4a9a94ae6b666aac6ae93e998f39d520dfc85b69b75af market_resolved 864 135,525 30-30 79272d857af38494a5789788f86aa52daca5f0a54865262382f1876711d64d12 new_market 542 56,213 31-31 dded5d6bb1f2cca2427b25776fec18ffd03efec6648eb42005d13fc1b0f21489 price_change 68,103,152 635,399,426 32-291 f3bbae33f78edfbd90f441e70acd925bf54928ffdfb1c0eb14afebb091feba52 tick_size_change 1,676 60,997 292-292 f449dbae42d3a34e9c6e6cf1d0b662a126c65965866027c2fc1425342cfa9dda EVENT MIX count share price_change 68,103,152 90.11% best_bid_ask 7,291,518 9.65% book 127,780 0.17% last_trade_price 55,281 0.07% tick_size_change 1,676 <0.01% market_resolved 864 <0.01% new_market 542 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,291,600 7,291,518 82 65,532 PARTIAL book 127,780 127,780 0 8,327 PARTIAL last_trade_price 55,281 55,281 0 2,765 PARTIAL market_resolved 864 864 0 850 PARTIAL new_market 542 542 0 361 PARTIAL price_change 68,104,092 68,103,152 940 119,531 PARTIAL tick_size_change 1,676 1,676 0 419 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask a 7,290,126 16 38ms 44ms 207ms 11.8s 0 transport_latency_assumed best_bid_ask c 7,291,380 650 4ms 6ms 34ms 1.5s 0 transport_latency_assumed best_bid_ask e 7,279,220 7,279,138 43ms 73ms 1.2s 20.5s 0 transport_latency_assumed best_bid_ask h 7,288,468 11,714 12ms 15ms 82ms 45.0s 0 transport_latency_assumed book a 114,230 695 60ms 1.8s 7.4s 74.5d 0 book_staleness book c 117,637 4,156 6ms 25ms 51.2min 74.7d 0 book_staleness book e 113,852 113,852 105ms 5.1s 1.1h 3.0d 0 book_staleness book h 118,231 9,077 17ms 225ms 1.8h 74.7d 0 book_staleness last_trade_price a 55,219 4 59ms 1.7s 6.3s 11.8s 0 transport_latency_assumed last_trade_price c 55,252 76 9ms 36ms 148ms 5.0s 0 transport_latency_assumed last_trade_price e 53,457 53,457 83ms 4.0s 10.4s 20.5s 0 transport_latency_assumed last_trade_price h 54,856 1,744 18ms 119ms 977ms 44.0s 0 transport_latency_assumed market_resolved a 850 1 39ms 208ms 788ms 1.7s 0 transport_latency_assumed market_resolved c 850 4 4ms 6ms 75ms 462ms 0 transport_latency_assumed market_resolved e 848 848 43ms 250ms 1.8s 1.0min 0 transport_latency_assumed market_resolved h 849 11 12ms 31ms 33.6s 1.0min 0 transport_latency_assumed new_market a 361 40 151ms 15.2s 57.8s 1.2min 0 transport_latency_assumed new_market c 361 62 44ms 16.9s 55.4s 1.2min 0 transport_latency_assumed new_market e 361 361 186ms 14.4s 57.5s 1.1min 0 transport_latency_assumed new_market h 361 79 63ms 16.9s 23.4s 1.3min 0 transport_latency_assumed price_change a 68,085,618 1,046 39ms 59ms 1.6s 11.8s 0 transport_latency_assumed price_change c 68,097,934 28,062 4ms 7ms 53ms 1.6s 0 transport_latency_assumed price_change e 67,692,104 67,691,164 43ms 126ms 4.3s 20.5s 0 transport_latency_assumed price_change h 68,012,712 382,880 12ms 18ms 172ms 45.0s 0 transport_latency_assumed tick_size_change a 1,676 not meas. 38ms 42ms 105ms 1.3s 0 transport_latency_assumed tick_size_change c 1,676 not meas. 4ms 6ms 26ms 41ms 0 transport_latency_assumed tick_size_change e 1,676 1,676 43ms 91ms 193ms 1.7s 0 transport_latency_assumed tick_size_change h 1,676 not meas. 12ms 15ms 50ms 87ms 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-31/03/2026-08-31T03.parquet sha256sum 2026-08-31T03.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.