Hour audit: 2026-08-31T18
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 4 machines expected to be capturing this hour, 1 contributed no rows: b. The hour is still whole on minutes; it simply rests on 3 machines rather than 4.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-08-31T18 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-08-31T18:00:00.039577153+00:00 · last event 2026-08-31T18:59:59.999998048+00:00
VOLUME 98,002,073 rows · 971,702,712 bytes (926.69 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 97,993,972 · h: 97,874,261 · e: 97,696,962 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 53,662 (0.05%) · h: 252,949 (0.26%) · e: 97,695,462 (99.69%) (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 98,002,073 rows exactly, so those pairs supplied none
4 expected (bceh), 1 contributed nothing: b
the listing string reads "bche"; the letters above are the machines whose rows are in the file
INTEGRITY sha256 a044e8d844a199866e473f696fdf6f199fd6ea100342683252a7afb9e76892ac
the corpus checksum ledger names this file with the same digest
joined 98,003,577 to merged 98,002,073, minus 1,504 (minus 0.0015%)
boundary drops 1,504 · 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-02T03:29:19Z as ceh
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,438,054 95,350,946 0-32 ed1fb77081d51c93064d19bb83ee1182db2244a7346c35b4515927297f93df1f book 153,807 15,101,014 33-33 9cbd567b1cd4327263513c61b0d44b78bad4dd9a301567d797b6ba9eb0c0a0f1 last_trade_price 71,444 4,062,247 34-34 767167e51314ef729dc8704992d1afd5c7be6bc055b1ad405613b6eb17c694f5 market_resolved 1,889 308,124 35-35 c3a3da478d13f206fdd7f0aa089c9b8b5b8e0c0a2691fad795a587650f5c61d5 new_market 1,471 172,475 36-36 673e9ac65fa2aab15cd95fef6993a06a1db0999d98c3242c92c6094a6b44f9b0 price_change 89,330,728 855,420,886 37-377 7344c9e8a3a063f8f3a6b85769f467433d97b77c2f7a8c4767263eef1fe2f4c0 tick_size_change 4,680 171,370 378-378 61aeb2848d598e3e7ceca110d819c6187281cbd29cb342998b9c5baa2a95ac4a EVENT MIX count share price_change 89,330,728 91.15% best_bid_ask 8,438,054 8.61% book 153,807 0.16% last_trade_price 71,444 0.07% tick_size_change 4,680 <0.01% market_resolved 1,889 <0.01% new_market 1,471 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,438,134 8,438,054 80 81,625 PARTIAL book 153,807 153,807 0 6,548 PARTIAL last_trade_price 71,444 71,444 0 4,024 PARTIAL market_resolved 1,889 1,889 0 1,884 PARTIAL new_market 1,471 1,471 0 1,086 PARTIAL price_change 89,332,152 89,330,728 1,424 130,941 PARTIAL tick_size_change 4,680 4,680 0 1,170 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,437,760 668 4ms 8ms 99ms 3.1s 0 transport_latency_assumed best_bid_ask e 8,428,910 8,428,830 45ms 99ms 898ms 22.6s 0 transport_latency_assumed best_bid_ask h 8,437,012 8,556 13ms 20ms 168ms 25.2s 0 transport_latency_assumed book c 148,756 1,180 7ms 21ms 2.3s 75.3d 0 book_staleness book e 148,573 148,573 66ms 4.7s 5.8min 6.0d 0 book_staleness book h 148,442 4,054 18ms 90ms 2.2s 33.1d 0 book_staleness last_trade_price c 71,420 31 9ms 37ms 218ms 5.0s 0 transport_latency_assumed last_trade_price e 70,017 70,017 69ms 3.5s 16.0s 22.6s 0 transport_latency_assumed last_trade_price h 71,397 1,396 18ms 88ms 496ms 9.5s 0 transport_latency_assumed market_resolved c 1,884 not meas. 4ms 8ms 53.1s 59.2s 0 transport_latency_assumed market_resolved e 1,884 1,884 46ms 268ms 50.9s 59.0s 0 transport_latency_assumed market_resolved h 1,884 5 13ms 48ms 53.1s 1.0min 0 transport_latency_assumed new_market c 1,086 91 64ms 14.8s 58.8s 15.6min 0 transport_latency_assumed new_market e 1,086 1,086 205ms 15.0s 44.6s 20.3min 0 transport_latency_assumed new_market h 1,086 294 97ms 14.1s 23.5s 53.6s 0 transport_latency_assumed price_change c 89,328,386 51,692 4ms 9ms 129ms 3.3s 0 transport_latency_assumed price_change e 89,041,812 89,040,392 45ms 154ms 4.2s 22.6s 0 transport_latency_assumed price_change h 89,209,760 238,644 13ms 22ms 214ms 27.9s 0 transport_latency_assumed tick_size_change c 4,680 not meas. 4ms 9ms 194ms 447ms 0 transport_latency_assumed tick_size_change e 4,680 4,680 45ms 115ms 404ms 6.2s 0 transport_latency_assumed tick_size_change h 4,680 not meas. 13ms 23ms 243ms 5.2s 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/18/2026-08-31T18.parquet sha256sum 2026-08-31T18.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.