Hour audit: 2026-09-07T05
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.
No findings
Every check that could be evaluated for this hour passed. That is not the same as the hour being perfect: it means the records this archive keeps about it agree with each other and with the corpus ledger.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-07T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T05:00:00.000387539+00:00 · last event 2026-09-07T05:59:59.999964915+00:00
VOLUME 85,749,152 rows · 822,535,791 bytes (784.43 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 85,627,633 · f: 85,613,074 · c: 85,591,679 · e: 85,416,394 · h: 85,375,603 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 58,385 (0.07%) · f: 119,507 (0.14%) · c: 83,229,436 (97.06%) · e: 285,122 (0.33%) · h: 2,056,702 (2.40%) (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 85,749,152 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0ecc15db449d0e0325372d6eb06d0c052f114aaa51820831ddfb736f8d72421d
the corpus checksum ledger names this file with the same digest
joined 85,751,367 to merged 85,749,152, minus 2,215 (minus 0.0026%)
boundary drops 2,215 · 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-07T06:52:59Z as cefgh
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 8/8 pass
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
PASS every expected machine contributed
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,652,305 84,360,428 0-29 ed8242ba1e11b04c836aebd682a6f8fd8b4dd9bb5e3b13c618c52786db483099 book 133,987 13,147,438 30-30 3fce3763238704734a074261fd86b38193f41c2bd575e9eef6b8e817ac7dfead last_trade_price 49,791 2,766,383 31-31 26b6a4884d44baaf16da699adfdbdc06494c20a24f35e336787d02130fe16461 market_resolved 1,799 288,351 32-32 67c90630942309ab431f26a296603eb44b62c0f2ca0139a04c93fba0d602de13 new_market 2,016 187,484 33-33 d85e01b89f39776fd5f71183d8e1b5c28ef171599749e1bfb4781c4cc0c4de78 price_change 77,906,666 720,708,746 34-331 5f62ed35ae90e928203cf74c9edc8e50e79e889c0e7182f1b37a271801876394 tick_size_change 2,588 94,701 332-332 20e1d423942a859edd2e5318246dece0fd0d4ec441561054933991b0d940faca EVENT MIX count share price_change 77,906,666 90.85% best_bid_ask 7,652,305 8.92% book 133,987 0.16% last_trade_price 49,791 0.06% tick_size_change 2,588 <0.01% new_market 2,016 <0.01% market_resolved 1,799 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 7,652,455 7,652,305 150 325 FULL book 133,988 133,987 1 12,573 FULL last_trade_price 49,791 49,791 0 0 FULL market_resolved 1,799 1,799 0 0 FULL new_market 2,016 2,016 0 0 FULL price_change 77,908,730 77,906,666 2,064 876 FULL tick_size_change 2,588 2,588 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 7,650,565 7,453,843 4ms 7ms 83ms 4.8s 0 transport_latency_assumed best_bid_ask e 7,649,228 19,991 38ms 43ms 152ms 5.7s 0 transport_latency_assumed best_bid_ask f 7,649,224 8,377 50ms 54ms 167ms 3.9s 0 transport_latency_assumed best_bid_ask g 7,648,408 1,210 81ms 99ms 356ms 11.0s 0 transport_latency_assumed best_bid_ask h 7,649,634 168,884 18ms 21ms 138ms 49.5s 0 transport_latency_assumed book c 108,725 103,056 6ms 37ms 6.2h 81.8d 0 book_staleness book e 110,325 6,865 41ms 195ms 10.0h 92.6d 0 book_staleness book f 110,001 5,871 52ms 187ms 8.6h 100.3d 0 book_staleness book g 115,793 11,898 89ms 3.9s 23.5h 81.8d 0 book_staleness book h 105,730 6,297 21ms 46ms 25.5s 81.7d 0 book_staleness last_trade_price c 49,762 47,836 9ms 37ms 195ms 5.0s 0 transport_latency_assumed last_trade_price e 49,706 173 45ms 93ms 857ms 5.8s 0 transport_latency_assumed last_trade_price f 49,740 56 56ms 102ms 709ms 5.2s 0 transport_latency_assumed last_trade_price g 49,683 16 93ms 167ms 3.0s 11.1s 0 transport_latency_assumed last_trade_price h 49,626 1,710 23ms 53ms 288ms 29.6s 0 transport_latency_assumed market_resolved c 1,758 1,704 4ms 8ms 26.0s 1.0min 0 transport_latency_assumed market_resolved e 1,758 29 41ms 123ms 48.3s 53.4s 0 transport_latency_assumed market_resolved f 1,758 1 52ms 177ms 52.9s 57.8s 0 transport_latency_assumed market_resolved g 1,758 18 89ms 250ms 531ms 1.3s 0 transport_latency_assumed market_resolved h 1,758 47 20ms 60ms 48.3s 53.8s 0 transport_latency_assumed new_market c 1,217 711 102ms 34.2s 1.4min 1.5min 0 transport_latency_assumed new_market e 1,217 459 153ms 31.1s 1.3min 3.3h 0 transport_latency_assumed new_market f 1,217 175 184ms 31.9s 1.3min 3.3h 0 transport_latency_assumed new_market g 1,217 209 260ms 25.2s 41.7s 19.9min 0 transport_latency_assumed new_market h 1,217 462 144ms 30.6s 1.4min 2.2h 0 transport_latency_assumed price_change c 77,777,064 75,619,734 4ms 8ms 97ms 5.6s 0 transport_latency_assumed price_change e 77,601,572 257,605 39ms 44ms 193ms 5.8s 0 transport_latency_assumed price_change f 77,798,546 105,027 50ms 56ms 208ms 4.0s 0 transport_latency_assumed price_change g 77,808,186 45,034 81ms 102ms 431ms 11.2s 0 transport_latency_assumed price_change h 77,565,050 1,879,266 18ms 22ms 161ms 49.5s 0 transport_latency_assumed tick_size_change c 2,588 2,552 4ms 6ms 23ms 46ms 0 transport_latency_assumed tick_size_change e 2,588 not meas. 39ms 42ms 83ms 141ms 0 transport_latency_assumed tick_size_change f 2,588 not meas. 50ms 54ms 115ms 222ms 0 transport_latency_assumed tick_size_change g 2,588 not meas. 80ms 97ms 291ms 5.1s 0 transport_latency_assumed tick_size_change h 2,588 36 18ms 20ms 56ms 2.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-07/05/2026-09-07T05.parquet sha256sum 2026-09-07T05.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.