Hour audit: 2026-09-16T08
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-16T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-16T08:00:00.000035550+00:00 · last event 2026-09-16T08:59:59.999790141+00:00
VOLUME 117,793,490 rows · 1,242,539,523 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 117,109,835 · e: 117,105,644 · f: 117,066,543 · g: 116,731,479 · c: 112,868,906 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 9,506,572 (8.07%) · e: 634,221 (0.54%) · f: 261,589 (0.22%) · g: 69,961 (0.06%) · c: 107,321,147 (91.11%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 117,793,490 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 12ef05b2033b270ae9906e1c76f28d3b8ae6920a36620168d04becf834c73e17
the corpus checksum ledger names this file with the same digest
joined 117,797,687 to merged 117,793,490, minus 4,197 (minus 0.0036%)
boundary drops 4,197 · 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-16T10:37:14Z 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 12,130,199 137,692,309 0-46 14cd9b031f139ced14bcc36f9866c294f029a83a1a7fbd035afed8049c382fa8 book 871,160 68,204,290 47-50 5b81d4ce1efd51e3f80570cb65f11af0e91e43c20be51c76ee67c16be168f060 last_trade_price 54,488 3,047,417 51-51 3e74af669a28326391ee5a6461b4c44fe213e31fcb0bd71f987667b517021f6d market_resolved 664 100,559 52-52 c1b9a56f9fd085db8eb6604d39a2f1dd3ea2a2a596a65d6b20672fecc68e625b new_market 669 68,164 53-53 318bea2c0d355f5da1a45e062a92d7a02ac5f9507296f1f878a00165b0a12a6c price_change 104,733,358 1,031,976,406 54-453 7c81d2714a3a5d8ce24b5fa0b537962e36a6830e867f41a5b922db189f82ee57 tick_size_change 2,952 108,350 454-454 66da98ec6903e4615f0ef681c4413c43490813007d557b207dd008260b8a6227 EVENT MIX count share price_change 104,733,358 88.91% best_bid_ask 12,130,199 10.30% book 871,160 0.74% last_trade_price 54,488 0.05% tick_size_change 2,952 <0.01% new_market 669 <0.01% market_resolved 664 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,130,321 12,130,199 122 456 FULL book 871,226 871,160 66 168,583 FULL last_trade_price 54,489 54,488 1 37 FULL market_resolved 664 664 0 3 FULL new_market 669 669 0 0 FULL price_change 104,737,366 104,733,358 4,008 147 FULL tick_size_change 2,952 2,952 0 35 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,655,733 11,129,179 5ms 11ms 80ms 4.8s 0 transport_latency_assumed best_bid_ask e 12,126,623 43,178 39ms 45ms 127ms 6.2s 0 transport_latency_assumed best_bid_ask f 12,126,046 11,775 46ms 55ms 158ms 6.9s 0 transport_latency_assumed best_bid_ask g 12,117,588 867 80ms 98ms 289ms 17.7s 0 transport_latency_assumed best_bid_ask h 12,127,966 945,200 17ms 25ms 97ms 17.8s 0 transport_latency_assumed book c 648,866 500,829 3.2min 1.3d 35.6d 109.4d 0 book_staleness book e 294,500 118,766 30.6s 1.3h 24.8d 109.4d 0 book_staleness book f 294,598 116,793 30.6s 1.4h 24.8d 109.4d 0 book_staleness book g 212,780 53,493 961ms 31.0min 24.8d 109.4d 0 book_staleness book h 237,840 81,279 3.4s 32.6min 24.8d 109.4d 0 book_staleness last_trade_price c 51,654 48,702 11ms 49ms 225ms 5.0s 0 transport_latency_assumed last_trade_price e 54,170 631 47ms 143ms 830ms 6.2s 0 transport_latency_assumed last_trade_price f 54,064 256 55ms 185ms 3.2s 7.0s 0 transport_latency_assumed last_trade_price g 53,313 60 95ms 391ms 7.2s 17.7s 0 transport_latency_assumed last_trade_price h 54,182 4,839 24ms 95ms 427ms 13.9s 0 transport_latency_assumed market_resolved c 627 606 5ms 27ms 3.4min 5.7min 0 transport_latency_assumed market_resolved e 624 5 40ms 189ms 43.4s 59.2s 0 transport_latency_assumed market_resolved f 624 not meas. 46ms 194ms 45.1s 1.0min 0 transport_latency_assumed market_resolved g 623 not meas. 85ms 317ms 671ms 1.4s 0 transport_latency_assumed market_resolved h 624 53 18ms 69ms 176ms 733ms 0 transport_latency_assumed new_market c 456 258 76ms 23.5s 4.9min 5.0min 0 transport_latency_assumed new_market e 445 65 153ms 15.4s 47.8s 1.2min 0 transport_latency_assumed new_market f 445 111 150ms 22.1s 55.2s 1.0min 0 transport_latency_assumed new_market g 445 15 317ms 16.0s 52.7s 1.2min 0 transport_latency_assumed new_market h 445 220 69ms 15.3s 53.6s 1.1min 0 transport_latency_assumed price_change c 100,508,758 95,638,878 5ms 13ms 96ms 4.8s 0 transport_latency_assumed price_change e 104,626,330 471,568 39ms 50ms 233ms 7.7s 0 transport_latency_assumed price_change f 104,587,814 132,654 46ms 61ms 298ms 6.9s 0 transport_latency_assumed price_change g 104,343,778 15,526 80ms 106ms 636ms 17.7s 0 transport_latency_assumed price_change h 104,685,826 8,474,732 17ms 29ms 150ms 24.2s 0 transport_latency_assumed tick_size_change c 2,812 2,695 5ms 14ms 59ms 181ms 0 transport_latency_assumed tick_size_change e 2,952 8 39ms 49ms 117ms 199ms 0 transport_latency_assumed tick_size_change f 2,952 not meas. 46ms 84ms 179ms 435ms 0 transport_latency_assumed tick_size_change g 2,952 not meas. 79ms 95ms 199ms 321ms 0 transport_latency_assumed tick_size_change h 2,952 249 17ms 32ms 86ms 129ms 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/08/2026-09-16T08.parquet sha256sum 2026-09-16T08.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.