Hour audit: 2026-09-11T20
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: f. 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-09-11T20 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-11T20:00:00.000027400+00:00 · last event 2026-09-11T20:59:59.999902860+00:00
VOLUME 118,571,138 rows · 1,293,751,037 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES cegh — 4 machines contributed rows
captured h: 116,863,219 · e: 116,774,436 · g: 116,401,092 · c: 98,062,709 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 24,180,882 (20.39%) · e: 3,580,354 (3.02%) · g: 209,683 (0.18%) · c: 90,600,219 (76.41%) (rows of the merged file that came from it; these partition it)
5 expected (cefgh), 1 contributed nothing: f
INTEGRITY sha256 c0eff682397ef3813be5b800fc25fd00f7200631daaf1224360f4a65cd1e2a2d
the corpus checksum ledger names this file with the same digest
joined 118,583,198 to merged 118,571,138, minus 12,060 (minus 0.0102%)
boundary drops 12,060 · 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-12T01:51:53Z as cegh
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 11,714,381 135,430,972 0-44 a4e4a94eb98b9949fa7d89de0f20edc8a10bf979b755fcfee595b860f7df2fb4 book 2,115,200 103,371,568 45-53 c4cdc5e56130c2ea21c4997e54dedc4953a2ee17fc7b3ed521908c7060569a08 last_trade_price 51,138 2,976,379 54-54 8a3055c08aaaee5171e977a300d93d58dca1fd02d300504c442cdf0e9e7aaeee market_resolved 2,551 356,515 55-55 8fc0a252112672badc362e53c1b8ea4d4c76ebc65af29e8066026d70d5d67129 new_market 10,042 987,920 56-56 7d45f0319102377f91c405d464b135bbe9076ea608d4318fc42a2cb6276a09a6 price_change 104,672,502 1,049,081,639 57-456 9e0c97eab8d9140be435387730fb44c833cb51142abf0ac995d192ccb3bc5cfa tick_size_change 5,324 196,853 457-457 68330c8145fed21414a2c77f61c90d38776e8e4d6385af47cf6d8eed0f483cd3 EVENT MIX count share price_change 104,672,502 88.28% best_bid_ask 11,714,381 9.88% book 2,115,200 1.78% last_trade_price 51,138 0.04% new_market 10,042 <0.01% tick_size_change 5,324 <0.01% market_resolved 2,551 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,715,223 11,714,381 842 88,488 PARTIAL book 2,116,014 2,115,200 814 215,843 PARTIAL last_trade_price 51,150 51,138 12 3,535 PARTIAL market_resolved 2,551 2,551 0 2,207 PARTIAL new_market 10,042 10,042 0 6,346 PARTIAL price_change 104,682,894 104,672,502 10,392 150,801 PARTIAL tick_size_change 5,324 5,324 0 1,331 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,721,411 8,959,829 5ms 25ms 279ms 8.2s 0 transport_latency_assumed best_bid_ask e 11,708,928 355,981 40ms 81ms 345ms 15.7s 0 transport_latency_assumed best_bid_ask g 11,704,261 19,682 85ms 215ms 735ms 33.7s 0 transport_latency_assumed best_bid_ask h 11,710,057 2,378,889 18ms 52ms 773ms 54.5s 0 transport_latency_assumed book c 1,870,951 1,779,327 9.2min 3.3h 31.1d 104.9d 0 book_staleness book e 391,854 125,706 1.5min 3.2h 20.3d 104.9d 0 book_staleness book g 169,571 26,306 489ms 2.0h 7.0d 104.9d 0 book_staleness book h 470,776 183,861 2.3min 3.2h 22.6d 104.9d 0 book_staleness last_trade_price c 40,735 37,791 11ms 72ms 402ms 7.0s 0 transport_latency_assumed last_trade_price e 50,968 1,492 69ms 518ms 4.8s 13.9s 0 transport_latency_assumed last_trade_price g 50,153 94 135ms 2.0s 13.9s 33.7s 0 transport_latency_assumed last_trade_price h 51,029 11,761 27ms 166ms 1.2s 49.4s 0 transport_latency_assumed market_resolved c 2,176 2,112 5ms 4.1min 11.2min 11.4min 0 transport_latency_assumed market_resolved e 2,207 38 47ms 194ms 494ms 912ms 0 transport_latency_assumed market_resolved g 2,207 1 96ms 371ms 925ms 1.5s 0 transport_latency_assumed market_resolved h 2,207 400 26ms 83ms 2.2s 1.0min 0 transport_latency_assumed new_market c 7,144 4,859 98ms 4.8min 7.9min 12.2min 0 transport_latency_assumed new_market e 6,335 1,393 171ms 49.3s 2.0min 2.9min 0 transport_latency_assumed new_market g 6,335 831 267ms 48.9s 2.1min 7.8min 0 transport_latency_assumed new_market h 6,346 2,959 134ms 52.8s 2.0min 3.0min 0 transport_latency_assumed price_change c 86,416,120 79,812,490 5ms 27ms 298ms 9.4s 0 transport_latency_assumed price_change e 104,608,820 3,095,506 41ms 106ms 613ms 17.8s 0 transport_latency_assumed price_change g 104,463,245 162,766 86ms 274ms 2.3s 34.1s 0 transport_latency_assumed price_change h 104,617,480 21,601,740 18ms 59ms 752ms 54.6s 0 transport_latency_assumed tick_size_change c 4,172 3,811 5ms 57ms 334ms 586ms 0 transport_latency_assumed tick_size_change e 5,324 238 41ms 112ms 372ms 2.1s 0 transport_latency_assumed tick_size_change g 5,320 3 86ms 279ms 662ms 7.9s 0 transport_latency_assumed tick_size_change h 5,324 1,272 19ms 77ms 688ms 7.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-09-11/20/2026-09-11T20.parquet sha256sum 2026-09-11T20.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.