Hour audit: 2026-09-18T16
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-18T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T16:00:00.000005013+00:00 · last event 2026-09-18T16:59:59.999999421+00:00
VOLUME 131,646,606 rows · 1,450,151,397 bytes (1.35 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 128,675,434 · e: 128,583,447 · g: 122,437,177 · f: 112,554,953 · c: 96,548,290 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 36,689,132 (27.87%) · e: 2,144,375 (1.63%) · g: 313,649 (0.24%) · f: 1,774,073 (1.35%) · c: 90,725,377 (68.92%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 80423bcac73b199c204de5831ca2b86f46a8de77ebc1a52a8f15b49fc162474d
the corpus checksum ledger names this file with the same digest
joined 131,690,192 to merged 131,646,606, minus 43,586 (minus 0.0331%)
boundary drops 43,586 · 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-18T20:09:08Z 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 15,079,913 170,959,185 0-57 546d6490b49c470ceb49c5113be54e957863731c5b30f93ecc8dd6a012584d46 book 2,870,839 115,665,630 58-68 fbb68eea657938547cc7d884c41557f6e404ae98cf30b7ecf7d15cdba90a0445 last_trade_price 66,177 3,864,694 69-69 f2d2bb09046410c6a05164df271130eac11cfe8fb3b621c19483f7c58bbf40da market_resolved 3,071 296,511 70-70 bc1b081c54f67318fd416f7207d0178335bec368c3a35427d18759fcf48ce1d6 new_market 3,242 293,118 71-71 d1dbe2f939a8dc1fdf6546676b2c0465020f812040970df768b57d52254d8576 price_change 113,617,616 1,157,366,051 72-505 2dda71a29f6ff75477d52c91875dcadf79fd224c3d6f06dca36b2554eed7f84f tick_size_change 5,748 210,971 506-506 8b3c574bc2d406220d0c8b0232fecaf86e337453f0eddf2323a1a21e1c2d04cf EVENT MIX count share price_change 113,617,616 86.31% best_bid_ask 15,079,913 11.45% book 2,870,839 2.18% last_trade_price 66,177 0.05% tick_size_change 5,748 <0.01% new_market 3,242 <0.01% market_resolved 3,071 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 15,080,191 15,079,913 278 6,688 FULL book 2,911,912 2,870,839 41,073 198,719 FULL last_trade_price 66,178 66,177 1 976 FULL market_resolved 3,071 3,071 0 25 FULL new_market 3,242 3,242 0 209 FULL price_change 113,619,850 113,617,616 2,234 3,864 FULL tick_size_change 5,748 5,748 0 444 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,972,645 10,362,196 6ms 15ms 141ms 4.3s 0 transport_latency_assumed best_bid_ask e 15,071,964 237,364 49ms 66ms 337ms 28.4s 0 transport_latency_assumed best_bid_ask f 13,043,469 159,340 48ms 69ms 371ms 20.3s 0 transport_latency_assumed best_bid_ask g 14,385,105 11,563 81ms 120ms 697ms 35.9s 0 transport_latency_assumed best_bid_ask h 15,073,744 4,309,450 18ms 39ms 353ms 58.5s 0 transport_latency_assumed book c 2,575,816 2,273,607 11.7min 2.4h 37.9d 111.8d 0 book_staleness book e 184,677 19,112 86ms 41.4min 11.3d 111.8d 0 book_staleness book f 1,367,444 360,719 10.1min 2.0h 37.6d 111.8d 0 book_staleness book g 574,631 171,257 4.1min 1.1h 30.9d 111.8d 0 book_staleness book h 148,227 46,144 24ms 374ms 1.1h 93.1d 0 book_staleness last_trade_price c 47,356 44,556 12ms 51ms 349ms 5.0s 0 transport_latency_assumed last_trade_price e 64,951 1,209 69ms 918ms 11.8s 28.4s 0 transport_latency_assumed last_trade_price f 56,121 643 69ms 1.2s 10.0s 20.3s 0 transport_latency_assumed last_trade_price g 60,129 239 105ms 2.2s 12.8s 35.9s 0 transport_latency_assumed last_trade_price h 65,755 19,530 26ms 124ms 1.3s 50.0s 0 transport_latency_assumed market_resolved c 2,557 2,255 45ms 9.5min 12.9min 15.9min 0 transport_latency_assumed market_resolved e 1,731 17 51ms 211ms 540ms 1.0min 0 transport_latency_assumed market_resolved f 2,119 270 121ms 9.3min 12.5min 12.7min 0 transport_latency_assumed market_resolved g 1,734 27 91ms 363ms 3.4min 5.7min 0 transport_latency_assumed market_resolved h 1,731 502 25ms 95ms 56.7s 1.0min 0 transport_latency_assumed new_market c 2,174 1,380 130ms 5.9min 9.5min 11.3min 0 transport_latency_assumed new_market e 1,840 376 210ms 27.7s 53.5s 3.0min 0 transport_latency_assumed new_market f 2,042 379 243ms 2.4min 7.5min 9.4min 0 transport_latency_assumed new_market g 1,844 306 346ms 27.9s 52.9s 7.4min 0 transport_latency_assumed new_market h 1,840 801 159ms 27.6s 53.9s 2.2min 0 transport_latency_assumed price_change c 82,943,510 78,037,335 6ms 18ms 196ms 4.7s 0 transport_latency_assumed price_change e 113,252,536 1,886,187 49ms 102ms 3.0s 28.4s 0 transport_latency_assumed price_change f 98,078,558 1,252,655 48ms 110ms 3.3s 20.3s 0 transport_latency_assumed price_change g 107,408,106 130,256 82ms 208ms 6.6s 35.9s 0 transport_latency_assumed price_change h 113,378,389 32,311,183 19ms 48ms 510ms 58.6s 0 transport_latency_assumed tick_size_change c 4,232 4,048 6ms 12ms 86ms 401ms 0 transport_latency_assumed tick_size_change e 5,748 110 48ms 77ms 416ms 5.9s 0 transport_latency_assumed tick_size_change f 5,200 67 48ms 105ms 405ms 2.9s 0 transport_latency_assumed tick_size_change g 5,628 1 81ms 158ms 626ms 1.0s 0 transport_latency_assumed tick_size_change h 5,748 1,522 19ms 41ms 553ms 5.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-18/16/2026-09-18T16.parquet sha256sum 2026-09-18T16.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.