Hour audit: 2026-09-01T04
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-09-01T04 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-01T04:00:00.036733193+00:00 · last event 2026-09-01T04:59:59.999939503+00:00
VOLUME 86,446,275 rows · 830,064,096 bytes (791.61 MiB) · 7 products, all holding rows
WITNESSES ceh — 3 machines contributed rows
captured c: 86,407,233 · h: 86,346,150 · e: 86,073,994 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 23,937 (0.03%) · h: 349,159 (0.40%) · e: 86,073,179 (99.57%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 86,446,275 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 3ac7a2b3029e82dd77a3d8fb4912c9bb7297c1f4ef7ce7a4fa049663a5f2de05
the corpus checksum ledger names this file with the same digest
joined 86,447,090 to merged 86,446,275, minus 815 (minus 0.0009%)
boundary drops 815 · 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-02T05:45:55Z 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,653,568 93,429,753 0-33 9242d3e59148a382b372620f2828b109cf64f08deb58e307384e218bdfd325c3 book 155,400 13,438,103 34-34 66e89f3e7eedb31036f5d01d9f48f2410dc284992f6803e6ace32b9a720a4e8e last_trade_price 59,929 3,292,079 35-35 22ba6651f076c1ee2e5fc9cb33d489ab26a4329fecc67cf1be83824e6f6561b3 market_resolved 1,179 184,411 36-36 f62eb19a48a42bfdf3959587370324d87e740ec0dd8a1784948cf8b9d93a5830 new_market 2,243 238,525 37-37 bd177dd4e7fd722ccd3d15aa588294d0029cdd9c45028ecb81a766b6d7ae4c96 price_change 77,570,896 718,385,768 38-333 3d413bbfba4abce342cbd195a2153aff371797c6f191ade482efe65c0c5ac7eb tick_size_change 3,060 109,704 334-334 e00e4495a2c8686cd253d6005e372b2028913bf1390e0e1e86b96dd5990f417e EVENT MIX count share price_change 77,570,896 89.73% best_bid_ask 8,653,568 10.01% book 155,400 0.18% last_trade_price 59,929 0.07% tick_size_change 3,060 <0.01% new_market 2,243 <0.01% market_resolved 1,179 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,653,630 8,653,568 62 72,660 PARTIAL book 155,408 155,400 8 15,802 PARTIAL last_trade_price 59,930 59,929 1 3,252 PARTIAL market_resolved 1,179 1,179 0 1,154 PARTIAL new_market 2,243 2,243 0 1,596 PARTIAL price_change 77,571,640 77,570,896 744 127,600 PARTIAL tick_size_change 3,060 3,060 0 765 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,653,084 468 4ms 7ms 134ms 3.3s 0 transport_latency_assumed best_bid_ask e 8,646,189 8,646,127 44ms 96ms 1.4s 25.5s 0 transport_latency_assumed best_bid_ask h 8,651,948 6,973 12ms 17ms 266ms 46.9s 0 transport_latency_assumed book c 133,163 5,366 6ms 60ms 1.8h 75.7d 0 book_staleness book e 133,644 133,636 129ms 8.3s 3.1h 30.8d 0 book_staleness book h 140,757 16,398 18ms 2.1s 5.3h 86.5d 0 book_staleness last_trade_price c 59,881 12 9ms 38ms 233ms 4.7s 0 transport_latency_assumed last_trade_price e 58,391 58,390 87ms 4.0s 14.4s 25.6s 0 transport_latency_assumed last_trade_price h 59,837 1,527 18ms 128ms 761ms 45.2s 0 transport_latency_assumed market_resolved c 1,154 21 4ms 14ms 1.0min 1.0min 0 transport_latency_assumed market_resolved e 1,154 1,154 44ms 282ms 57.4s 1.0min 0 transport_latency_assumed market_resolved h 1,154 4 12ms 54ms 56.8s 1.0min 0 transport_latency_assumed new_market c 1,596 220 87ms 20.2s 32.1s 1.2min 0 transport_latency_assumed new_market e 1,596 1,596 240ms 20.0s 35.9s 2.2min 0 transport_latency_assumed new_market h 1,596 427 184ms 19.1s 35.2s 47.4s 0 transport_latency_assumed price_change c 77,555,295 17,850 4ms 7ms 164ms 3.6s 0 transport_latency_assumed price_change e 77,229,960 77,229,216 44ms 148ms 3.8s 25.7s 0 transport_latency_assumed price_change h 77,487,798 323,830 12ms 19ms 319ms 47.6s 0 transport_latency_assumed tick_size_change c 3,060 not meas. 4ms 6ms 15ms 41ms 0 transport_latency_assumed tick_size_change e 3,060 3,060 44ms 96ms 523ms 3.9s 0 transport_latency_assumed tick_size_change h 3,060 not meas. 12ms 17ms 45ms 2.0s 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-09-01/04/2026-09-01T04.parquet sha256sum 2026-09-01T04.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.