Hour audit: 2026-09-17T14
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-17T14 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T14:00:00.000400248+00:00 · last event 2026-09-17T14:59:59.999954698+00:00
VOLUME 125,838,969 rows · 1,373,093,673 bytes (1.28 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 124,562,353 · e: 124,078,039 · f: 119,147,219 · g: 116,913,830 · c: 111,101,385 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 19,119,513 (15.19%) · e: 1,638,495 (1.30%) · f: 593,506 (0.47%) · g: 272,525 (0.22%) · c: 104,214,930 (82.82%) (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 125,838,969 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a6719851fdeb9447d90803e4d3d2e6dee4bf8ab5420070e4809722a3054bc53e
the corpus checksum ledger names this file with the same digest
joined 125,855,474 to merged 125,838,969, minus 16,505 (minus 0.0131%)
boundary drops 16,505 · 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-17T16:01:19Z 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,769,642 148,598,931 0-48 630901bfb6cf893590969da00581e60c67ed3854366b2c3314ece6ef5e60e76b book 1,635,884 96,131,585 49-55 667c1793c77effcc5b5ab6efe61e01d002495d9d5372165632611cb838d40422 last_trade_price 60,909 3,566,275 56-56 af2296cd0314d598963500d321864b6856226a763d0516c0c3032563d250b108 market_resolved 720 96,115 57-57 c0d50bf419485744832f980d8484addf218f806ffd1f3c66bf84935ea066ccd1 new_market 1,778 174,498 58-58 35068247ffacc110b0b94e71de63f0034dfb464b80ede0026efa0d1ab8c36404 price_change 111,365,864 1,122,942,151 59-483 faca3d9d571d9c1a702a183a96c9186b4832162bfb6eaf9c9a4359cf07bd1e29 tick_size_change 4,172 153,853 484-484 2574ecee27bb5469973557e51e38debcc3daa11d3c7d6a493dfe250e94bb14ae EVENT MIX count share price_change 111,365,864 88.50% best_bid_ask 12,769,642 10.15% book 1,635,884 1.30% last_trade_price 60,909 0.05% tick_size_change 4,172 <0.01% new_market 1,778 <0.01% market_resolved 720 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,769,880 12,769,642 238 2,168 FULL book 1,641,026 1,635,884 5,142 163,736 FULL last_trade_price 60,910 60,909 1 543 FULL market_resolved 720 720 0 28 FULL new_market 1,778 1,778 0 2 FULL price_change 111,376,988 111,365,864 11,124 306 FULL tick_size_change 4,172 4,172 0 152 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,277,664 10,643,942 6ms 15ms 124ms 3.8s 0 transport_latency_assumed best_bid_ask e 12,764,502 153,062 41ms 54ms 260ms 21.8s 0 transport_latency_assumed best_bid_ask f 12,240,922 31,238 47ms 65ms 279ms 20.4s 0 transport_latency_assumed best_bid_ask g 11,982,496 3,810 78ms 110ms 550ms 32.5s 0 transport_latency_assumed best_bid_ask h 12,763,617 1,937,590 18ms 34ms 191ms 48.3s 0 transport_latency_assumed book c 1,207,698 1,034,239 3.9min 2.9d 39.0d 110.7d 0 book_staleness book e 147,281 14,613 51ms 1.8min 10.1d 110.7d 0 book_staleness book f 495,470 193,406 1.6min 14.9h 35.8d 110.7d 0 book_staleness book g 488,417 187,580 2.3min 16.2h 35.8d 110.7d 0 book_staleness book h 471,262 206,046 1.5min 10.6h 35.5d 110.7d 0 book_staleness last_trade_price c 52,969 49,997 11ms 49ms 229ms 4.9s 0 transport_latency_assumed last_trade_price e 59,975 771 61ms 1.2s 7.5s 21.9s 0 transport_latency_assumed last_trade_price f 57,290 217 66ms 976ms 8.2s 20.4s 0 transport_latency_assumed last_trade_price g 55,275 99 103ms 2.8s 15.2s 32.7s 0 transport_latency_assumed last_trade_price h 60,665 9,825 26ms 108ms 755ms 7.5s 0 transport_latency_assumed market_resolved c 579 546 6ms 3.0min 5.3min 6.9min 0 transport_latency_assumed market_resolved e 578 18 42ms 187ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 566 6 48ms 199ms 49.1s 5.5min 0 transport_latency_assumed market_resolved g 574 48 81ms 1.5s 5.3min 5.3min 0 transport_latency_assumed market_resolved h 578 102 19ms 63ms 24.3s 46.1s 0 transport_latency_assumed new_market c 1,124 716 87ms 19.7s 1.2min 54.5min 0 transport_latency_assumed new_market e 1,119 246 201ms 21.7s 52.2s 2.1min 0 transport_latency_assumed new_market f 1,121 279 200ms 22.6s 1.7min 53.2min 0 transport_latency_assumed new_market g 1,119 126 297ms 19.6s 1.5min 4.1min 0 transport_latency_assumed new_market h 1,119 411 126ms 23.2s 54.5s 2.1min 0 transport_latency_assumed price_change c 98,557,411 92,481,763 6ms 19ms 173ms 4.0s 0 transport_latency_assumed price_change e 111,100,412 1,469,784 42ms 86ms 3.0s 21.9s 0 transport_latency_assumed price_change f 106,347,870 368,356 47ms 94ms 2.5s 20.5s 0 transport_latency_assumed price_change g 104,381,981 80,862 79ms 178ms 7.1s 32.6s 0 transport_latency_assumed price_change h 111,260,940 16,965,099 19ms 42ms 325ms 49.1s 0 transport_latency_assumed tick_size_change c 3,940 3,727 6ms 13ms 67ms 264ms 0 transport_latency_assumed tick_size_change e 4,172 1 41ms 53ms 179ms 457ms 0 transport_latency_assumed tick_size_change f 3,980 4 47ms 60ms 210ms 529ms 0 transport_latency_assumed tick_size_change g 3,968 not meas. 78ms 97ms 301ms 9.7s 0 transport_latency_assumed tick_size_change h 4,172 440 19ms 29ms 80ms 897ms 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-17/14/2026-09-17T14.parquet sha256sum 2026-09-17T14.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.