Hour audit: 2026-09-18T07
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-18T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T07:00:00.000035976+00:00 · last event 2026-09-18T07:59:59.999986556+00:00
VOLUME 106,626,639 rows · 1,080,948,249 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 106,535,909 · h: 106,503,772 · f: 106,471,220 · e: 106,348,630 · g: 106,313,874 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 101,332,409 (95.03%) · h: 4,591,399 (4.31%) · f: 189,095 (0.18%) · e: 475,600 (0.45%) · g: 38,136 (0.04%) (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 106,626,639 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f5b6e5640cefbdfe263b2db9fa78cd5cf4e4a71e62d10f7119aeedcab4012d6f
the corpus checksum ledger names this file with the same digest
joined 106,628,889 to merged 106,626,639, minus 2,250 (minus 0.0021%)
boundary drops 2,250 · 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-18T08:58:57Z 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 9,874,119 115,511,165 0-37 0b886b4b27dbb345a6bfc2c202e9f6314c09a5ccab19e7e03b90d28574b89e59 book 187,704 18,263,856 38-38 e5699b21d7b866f2659b777edf22926208209028ab3180a224d2758c3d66c61d last_trade_price 68,561 3,778,765 39-39 7a9c06448815d159c6e7328a89f13ff4191a3cf6faf98d3a2c0eb5dc264a88a5 market_resolved 503 77,948 40-40 88e173f7b3b3c367ee6692fd49693e3ee422db66b2eaecb037817a79e5283e37 new_market 1,841 192,949 41-41 d85b3498f084e388d43290a679c7d6545e094961d3b7e3c4c90538f4904b22f5 price_change 96,491,775 941,829,080 42-410 f419fd42969cd4aa4b56403cf01a6242828e4ecd60d2a8aa3f635d785bcb8eb4 tick_size_change 2,136 78,865 411-411 1babee3eb371940fc7d5b875f05778d8d89c6baf51a795082916ebac06c26c58 EVENT MIX count share price_change 96,491,775 90.49% best_bid_ask 9,874,119 9.26% book 187,704 0.18% last_trade_price 68,561 0.06% tick_size_change 2,136 <0.01% new_market 1,841 <0.01% market_resolved 503 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,874,317 9,874,119 198 251 FULL book 187,706 187,704 2 14,525 FULL last_trade_price 68,563 68,561 2 0 FULL market_resolved 503 503 0 0 FULL new_market 1,841 1,841 0 0 FULL price_change 96,493,823 96,491,775 2,048 395 FULL tick_size_change 2,136 2,136 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,871,511 9,414,049 5ms 11ms 115ms 13.3s 0 transport_latency_assumed best_bid_ask e 9,866,066 40,450 39ms 49ms 212ms 19.4s 0 transport_latency_assumed best_bid_ask f 9,869,284 15,217 48ms 60ms 248ms 13.3s 0 transport_latency_assumed best_bid_ask g 9,867,389 2,387 79ms 100ms 379ms 36.4s 0 transport_latency_assumed best_bid_ask h 9,870,634 402,016 18ms 27ms 194ms 15.9s 0 transport_latency_assumed book c 167,161 157,431 7ms 39.0s 6.6d 92.9d 0 book_staleness book e 150,764 8,305 42ms 1.1s 25.2min 92.9d 0 book_staleness book f 149,605 4,770 52ms 1.0s 14.8min 89.9d 0 book_staleness book g 150,600 5,177 86ms 876ms 27.5min 92.9d 0 book_staleness book h 150,838 12,021 22ms 227ms 11.4min 92.9d 0 book_staleness last_trade_price c 68,290 64,342 10ms 45ms 237ms 9.5s 0 transport_latency_assumed last_trade_price e 67,220 596 48ms 293ms 6.1s 19.4s 0 transport_latency_assumed last_trade_price f 67,644 349 60ms 489ms 5.7s 13.3s 0 transport_latency_assumed last_trade_price g 67,289 97 96ms 410ms 14.0s 32.9s 0 transport_latency_assumed last_trade_price h 68,170 3,177 24ms 136ms 919ms 6.5s 0 transport_latency_assumed market_resolved c 480 461 5ms 13ms 187ms 46.6s 0 transport_latency_assumed market_resolved e 480 2 41ms 200ms 57.1s 57.1s 0 transport_latency_assumed market_resolved f 480 4 49ms 202ms 516ms 677ms 0 transport_latency_assumed market_resolved g 480 not meas. 87ms 335ms 887ms 2.0s 0 transport_latency_assumed market_resolved h 480 36 19ms 100ms 56.8s 56.8s 0 transport_latency_assumed new_market c 1,260 735 81ms 19.6s 1.5min 1.9min 0 transport_latency_assumed new_market e 1,260 305 155ms 19.1s 1.1min 2.0min 0 transport_latency_assumed new_market f 1,260 107 215ms 19.5s 1.1min 2.1min 0 transport_latency_assumed new_market g 1,260 157 266ms 19.5s 1.4min 1.9min 0 transport_latency_assumed new_market h 1,260 537 114ms 19.7s 1.1min 1.9min 0 transport_latency_assumed price_change c 96,425,071 91,693,352 5ms 13ms 126ms 13.4s 0 transport_latency_assumed price_change e 96,260,704 425,930 40ms 58ms 430ms 19.5s 0 transport_latency_assumed price_change f 96,380,811 168,644 48ms 71ms 577ms 13.3s 0 transport_latency_assumed price_change g 96,224,720 30,318 80ms 112ms 798ms 36.6s 0 transport_latency_assumed price_change h 96,410,254 4,173,531 18ms 32ms 252ms 17.3s 0 transport_latency_assumed tick_size_change c 2,136 2,039 5ms 9ms 101ms 230ms 0 transport_latency_assumed tick_size_change e 2,136 12 40ms 88ms 194ms 328ms 0 transport_latency_assumed tick_size_change f 2,136 4 47ms 59ms 138ms 282ms 0 transport_latency_assumed tick_size_change g 2,136 not meas. 79ms 105ms 297ms 414ms 0 transport_latency_assumed tick_size_change h 2,136 81 18ms 35ms 157ms 1.3s 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-18/07/2026-09-18T07.parquet sha256sum 2026-09-18T07.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.