Hour audit: 2026-09-19T08
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-19T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-19T08:00:00.000040825+00:00 · last event 2026-09-19T08:59:59.999993074+00:00
VOLUME 120,747,531 rows · 1,276,209,598 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 120,082,107 · e: 120,062,896 · h: 120,055,492 · f: 120,018,755 · g: 119,853,243 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 114,830,954 (95.10%) · e: 526,655 (0.44%) · h: 4,909,437 (4.07%) · f: 324,728 (0.27%) · g: 155,757 (0.13%) (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 120,747,531 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d0114a6c7c313e6c59668fcc8db0df819005d1af0673c7ae81a2c2e77afeb570
the corpus checksum ledger names this file with the same digest
joined 120,750,562 to merged 120,747,531, minus 3,031 (minus 0.0025%)
boundary drops 3,031 · 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-19T10:01:04Z 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,562,974 144,159,334 0-47 f1a110abe1830afa2dc3d6808eb943ccbd75ca2fac31c11b3731dd3182b50481 book 1,001,471 80,777,482 48-51 3691b75c1cc2fd248494e29d6a90794742ebce5f896bf6ad0651adf89dbb6a42 last_trade_price 51,593 3,018,955 52-52 608f58fdf79e94dfebbd3b1999502299aea29a958eefa47d7a9dde6613ad330c market_resolved 646 107,460 53-53 9598799b47455608a333212acdc110176c058bbd5606d3b4e9120b9209779ae0 new_market 405 46,958 54-54 9d12570372b902cd560385e0d600b71179657967072e78d42fcd7d8f776f96da price_change 107,127,474 1,046,618,428 55-463 92f33590293b7e73307fed4c7c0a0e55a66f4cee2425694c8186e4d31c7640aa tick_size_change 2,968 109,569 464-464 f47aade21b0c478e95d10618bf791588d88720936e1024207ea7fe6207f66b9e EVENT MIX count share price_change 107,127,474 88.72% best_bid_ask 12,562,974 10.40% book 1,001,471 0.83% last_trade_price 51,593 0.04% tick_size_change 2,968 <0.01% market_resolved 646 <0.01% new_market 405 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,563,212 12,562,974 238 103 FULL book 1,001,473 1,001,471 2 180,470 FULL last_trade_price 51,594 51,593 1 3 FULL market_resolved 646 646 0 1 FULL new_market 405 405 0 0 FULL price_change 107,130,264 107,127,474 2,790 126 FULL tick_size_change 2,968 2,968 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,561,054 12,068,694 4ms 10ms 73ms 3.4s 0 transport_latency_assumed best_bid_ask e 12,558,592 26,309 41ms 47ms 128ms 8.1s 0 transport_latency_assumed best_bid_ask f 12,559,018 10,008 49ms 55ms 141ms 5.3s 0 transport_latency_assumed best_bid_ask g 12,557,862 1,284 77ms 91ms 216ms 24.4s 0 transport_latency_assumed best_bid_ask h 12,555,772 456,679 18ms 25ms 87ms 14.3s 0 transport_latency_assumed book c 389,365 272,218 1.7min 9.7h 27.8d 112.4d 0 book_staleness book e 457,694 220,661 2.4min 12.5h 27.8d 112.4d 0 book_staleness book f 400,867 180,121 1.9min 10.2h 27.8d 112.4d 0 book_staleness book g 335,281 130,501 1.2min 4.9h 27.8d 112.4d 0 book_staleness book h 424,201 197,970 2.0min 12.4h 27.8d 112.4d 0 book_staleness last_trade_price c 51,422 48,494 10ms 48ms 251ms 5.0s 0 transport_latency_assumed last_trade_price e 51,197 243 49ms 181ms 3.0s 8.1s 0 transport_latency_assumed last_trade_price f 51,211 114 57ms 168ms 1.7s 5.3s 0 transport_latency_assumed last_trade_price g 50,950 53 90ms 261ms 5.9s 24.3s 0 transport_latency_assumed last_trade_price h 51,415 2,689 24ms 75ms 455ms 5.0s 0 transport_latency_assumed market_resolved c 646 624 5ms 12ms 66ms 163ms 0 transport_latency_assumed market_resolved e 646 not meas. 42ms 194ms 470ms 737ms 0 transport_latency_assumed market_resolved f 646 not meas. 50ms 200ms 492ms 749ms 0 transport_latency_assumed market_resolved g 646 not meas. 80ms 311ms 620ms 948ms 0 transport_latency_assumed market_resolved h 645 22 18ms 68ms 153ms 612ms 0 transport_latency_assumed new_market c 302 198 43ms 11.4s 22.1s 1.0min 0 transport_latency_assumed new_market e 302 34 71ms 12.8s 56.2s 1.1min 0 transport_latency_assumed new_market f 302 55 96ms 14.2s 22.5s 1.1min 0 transport_latency_assumed new_market g 302 23 92ms 551ms 24.1s 1.1min 0 transport_latency_assumed new_market h 302 95 54ms 13.8s 1.0min 1.1min 0 transport_latency_assumed price_change c 107,076,350 102,438,000 5ms 12ms 96ms 4.9s 0 transport_latency_assumed price_change e 106,991,497 279,372 41ms 52ms 262ms 8.1s 0 transport_latency_assumed price_change f 107,003,743 134,422 49ms 61ms 264ms 5.3s 0 transport_latency_assumed price_change g 106,905,234 23,896 77ms 96ms 371ms 24.4s 0 transport_latency_assumed price_change h 107,020,189 4,251,784 18ms 28ms 132ms 14.3s 0 transport_latency_assumed tick_size_change c 2,968 2,726 5ms 24ms 352ms 429ms 0 transport_latency_assumed tick_size_change e 2,968 36 41ms 63ms 308ms 443ms 0 transport_latency_assumed tick_size_change f 2,968 8 49ms 60ms 211ms 762ms 0 transport_latency_assumed tick_size_change g 2,968 not meas. 78ms 94ms 365ms 777ms 0 transport_latency_assumed tick_size_change h 2,968 198 18ms 31ms 456ms 6.4s 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-19/08/2026-09-19T08.parquet sha256sum 2026-09-19T08.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.