Hour audit: 2026-09-16T18
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-16T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T18:00:00.000019431+00:00 · last event 2026-09-16T18:59:59.999751464+00:00
VOLUME 147,825,051 rows · 1,667,352,013 bytes (1.55 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 144,765,313 · e: 143,984,171 · f: 123,322,512 · g: 123,140,944 · c: 107,321,472 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 42,497,011 (28.75%) · e: 3,656,261 (2.47%) · f: 1,649,905 (1.12%) · g: 657,050 (0.44%) · c: 99,364,824 (67.22%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 147,825,051 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 02cdbf05ee7fe80426f9095222157e22fcd020a23090144a1c22e17a8101144b
the corpus checksum ledger names this file with the same digest
joined 147,836,331 to merged 147,825,051, minus 11,280 (minus 0.0076%)
boundary drops 11,280 · 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-16T20:04:37Z 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 14,311,674 171,106,788 0-54 eb3866277032e3e202ebcfed62840033fed425ae618b559ce55ca765a4560b83 book 3,147,903 134,040,743 55-67 959d5a6c307032c36c2d980ca581a61826450e02ca4f1b816054fe75b4e68128 last_trade_price 87,748 4,987,552 68-68 5365d7cec763efa16ebf6a7d788cb1f38360bf6e64e267596016e1c27bd13f59 market_resolved 1,399 128,736 69-69 d334737f275cb86c6ee7cb56eedf79e478175c9f0183aa4d9fda7063cb3b6245 new_market 3,217 234,269 70-70 c8690d22a5677224b48067f28fba4be0130a51dab0288ab9f57d419718d97f90 price_change 130,267,802 1,354,978,107 71-567 8aa0996384329f1013f49191a4990b315cdf69ffab6f588c992153ae92e03492 tick_size_change 5,308 197,018 568-568 594da52f90b18ed3203f908e183a581e46ebdc5ad2d6a80267deef38b0b13973 EVENT MIX count share price_change 130,267,802 88.12% best_bid_ask 14,311,674 9.68% book 3,147,903 2.13% last_trade_price 87,748 0.06% tick_size_change 5,308 <0.01% new_market 3,217 <0.01% market_resolved 1,399 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,312,936 14,311,674 1,262 6,484 FULL book 3,148,145 3,147,903 242 174,761 FULL last_trade_price 87,809 87,748 61 999 FULL market_resolved 1,400 1,399 1 137 FULL new_market 3,217 3,217 0 0 FULL price_change 130,277,516 130,267,802 9,714 2,523 FULL tick_size_change 5,308 5,308 0 604 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,564,105 9,823,309 7ms 18ms 123ms 2.9s 0 transport_latency_assumed best_bid_ask e 14,292,566 341,227 40ms 61ms 346ms 19.2s 0 transport_latency_assumed best_bid_ask f 12,189,918 76,862 45ms 68ms 397ms 33.4s 0 transport_latency_assumed best_bid_ask g 12,181,061 5,608 82ms 130ms 3.8s 34.1s 0 transport_latency_assumed best_bid_ask h 14,307,823 4,064,668 19ms 39ms 234ms 33.1s 0 transport_latency_assumed book c 2,276,304 1,726,244 4.6min 2.9d 38.8d 109.9d 0 book_staleness book e 185,063 12,211 47ms 5.2s 24.8min 91.3d 0 book_staleness book f 1,578,919 786,003 3.9min 2.1d 36.0d 109.8d 0 book_staleness book g 1,587,412 565,226 4.0min 2.1d 36.0d 109.8d 0 book_staleness book h 188,659 58,219 25ms 148ms 9.8min 91.3d 0 book_staleness last_trade_price c 61,808 57,347 13ms 55ms 278ms 5.0s 0 transport_latency_assumed last_trade_price e 83,584 2,498 63ms 2.3s 10.5s 19.0s 0 transport_latency_assumed last_trade_price f 68,697 688 67ms 2.6s 13.5s 33.3s 0 transport_latency_assumed last_trade_price g 67,275 182 108ms 3.9s 16.0s 30.5s 0 transport_latency_assumed last_trade_price h 87,395 27,033 28ms 117ms 1.2s 8.4s 0 transport_latency_assumed market_resolved c 1,169 1,091 3.0min 14.9min 20.1min 21.2min 0 transport_latency_assumed market_resolved e 748 42 42ms 197ms 58.8s 2.4min 0 transport_latency_assumed market_resolved f 839 74 73ms 8.5min 13.5min 14.3min 0 transport_latency_assumed market_resolved g 660 6 88ms 367ms 8.9min 8.9min 0 transport_latency_assumed market_resolved h 748 186 21ms 87ms 58.3s 1.0min 0 transport_latency_assumed new_market c 2,361 1,666 55.7s 16.7min 17.7min 17.8min 0 transport_latency_assumed new_market e 1,416 320 213ms 17.6s 28.7s 1.5min 0 transport_latency_assumed new_market f 1,579 399 198ms 2.6min 9.1min 9.9min 0 transport_latency_assumed new_market g 1,492 136 274ms 18.1s 5.2min 5.2min 0 transport_latency_assumed new_market h 1,416 696 123ms 15.8s 27.7s 1.4min 0 transport_latency_assumed price_change c 94,411,897 87,751,667 7ms 20ms 140ms 4.0s 0 transport_latency_assumed price_change e 129,415,486 3,299,859 40ms 89ms 4.5s 19.4s 0 transport_latency_assumed price_change f 109,477,680 785,860 46ms 90ms 4.3s 33.4s 0 transport_latency_assumed price_change g 109,298,732 85,892 83ms 187ms 7.6s 34.1s 0 transport_latency_assumed price_change h 130,173,964 38,344,524 19ms 45ms 349ms 33.1s 0 transport_latency_assumed tick_size_change c 3,828 3,500 7ms 21ms 185ms 266ms 0 transport_latency_assumed tick_size_change e 5,308 104 39ms 51ms 127ms 931ms 0 transport_latency_assumed tick_size_change f 4,880 19 45ms 58ms 183ms 706ms 0 transport_latency_assumed tick_size_change g 4,312 not meas. 80ms 100ms 347ms 3.9s 0 transport_latency_assumed tick_size_change h 5,308 1,685 19ms 35ms 101ms 5.8s 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-16/18/2026-09-16T18.parquet sha256sum 2026-09-16T18.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.