Hour audit: 2026-09-28T19
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-28T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T19:00:00.000003211+00:00 · last event 2026-09-28T19:59:59.999997074+00:00
VOLUME 111,649,822 rows · 1,269,570,643 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 110,604,582 · h: 110,455,570 · k: 110,188,719 · g: 104,738,174 · c: 101,517,895 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 6,638,393 (5.95%) · h: 4,383,436 (3.93%) · k: 14,200,226 (12.72%) · g: 144,940 (0.13%) · c: 86,282,827 (77.28%) (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 111,649,822 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 cb0e0ebefcfdbfc0c942cddcda6597cfb270fccf80df9e7c6ee84a94f9afd90b
the corpus checksum ledger names this file with the same digest
joined 111,652,300 to merged 111,649,822, minus 2,478 (minus 0.0022%)
boundary drops 2,478 · 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-28T22:06:58Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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 10,962,417 131,364,650 0-41 bdb4aeb03800354a75024b53256679713f5e20cc7abcdc5c4f2d65f937a5e550 book 1,128,783 70,004,591 42-46 afbd50c3d9768ed4673dfb30858395ad38c85a5f4ec66a7e43b6579391314809 last_trade_price 53,127 3,066,836 47-47 d15ec02e3377d4a9a497d6a529ee8aaa796b372bf284917aef8252b796b7dcb0 market_resolved 1,741 233,125 48-48 6db29f520e2942bda8d91791173bf23e9690530831761de83dc4dbf2365010d4 new_market 4,978 467,934 49-49 43e2f49e38f72890d2576da84b3d444cf032eae5b9a4a9cbb82ea09ad59d7d6f price_change 99,495,620 1,063,044,152 50-429 50db4adda22b1ff69de8d0c74d7d9eeb98fc0a246756eb74c4699d00cbe64c3d tick_size_change 3,156 117,619 430-430 c6c35cebca09c0ab892859e2b02de1411ad58f799badee7ad132028621883fa6 EVENT MIX count share price_change 99,495,620 89.11% best_bid_ask 10,962,417 9.82% book 1,128,783 1.01% last_trade_price 53,127 0.05% new_market 4,978 <0.01% tick_size_change 3,156 <0.01% market_resolved 1,741 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,962,644 10,962,417 227 1,704 FULL book 1,129,395 1,128,783 612 208,567 FULL last_trade_price 53,128 53,127 1 179 FULL market_resolved 1,741 1,741 0 44 FULL new_market 4,978 4,978 0 0 FULL price_change 99,497,258 99,495,620 1,638 1,992 FULL tick_size_change 3,156 3,156 0 106 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,940,640 8,517,607 6ms 26ms 356ms 12.0s 0 transport_latency_assumed best_bid_ask g 10,737,138 3,459 81ms 186ms 2.5s 58.2s 0 transport_latency_assumed best_bid_ask h 10,933,084 414,962 19ms 37ms 724ms 1.5min 0 transport_latency_assumed best_bid_ask i 10,960,200 646,335 17ms 34ms 387ms 1.1min 0 transport_latency_assumed best_bid_ask k 10,910,922 1,380,054 14ms 35ms 549ms 3.5min 0 transport_latency_assumed book c 980,232 844,848 1.4h 1.6d 44.2d 121.9d 0 book_staleness book g 283,026 105,243 4.6min 1.1d 37.2d 121.9d 0 book_staleness book h 259,779 74,554 37.8s 1.2d 37.2d 121.9d 0 book_staleness book i 134,408 20,191 25ms 52.8min 19.4d 121.9d 0 book_staleness book k 258,353 83,947 38.7s 1.1d 37.2d 121.9d 0 book_staleness last_trade_price c 48,307 40,466 7ms 49ms 525ms 4.8s 0 transport_latency_assumed last_trade_price g 44,028 24 94ms 1.0s 12.4s 57.6s 0 transport_latency_assumed last_trade_price h 52,911 2,240 20ms 124ms 1.2s 59.2s 0 transport_latency_assumed last_trade_price i 52,987 2,911 20ms 162ms 1.1s 8.0s 0 transport_latency_assumed last_trade_price k 52,380 7,486 16ms 74ms 1.3s 3.4min 0 transport_latency_assumed market_resolved c 1,424 1,195 7ms 3.7min 14.0min 14.2min 0 transport_latency_assumed market_resolved g 1,421 13 82ms 38.1s 56.2s 1.9min 0 transport_latency_assumed market_resolved h 1,421 35 19ms 31.3s 51.8s 1.0min 0 transport_latency_assumed market_resolved i 1,422 312 20ms 30.4s 54.5s 55.2s 0 transport_latency_assumed market_resolved k 1,419 186 14ms 34.7s 56.7s 1.1min 0 transport_latency_assumed new_market c 3,930 2,059 49.3s 4.3min 10.4min 10.8min 0 transport_latency_assumed new_market g 2,969 567 735ms 1.2min 1.3min 1.6min 0 transport_latency_assumed new_market h 2,969 804 319ms 1.2min 1.4min 1.6min 0 transport_latency_assumed new_market i 2,969 859 416ms 1.2min 1.3min 1.7min 0 transport_latency_assumed new_market k 2,969 689 350ms 1.2min 1.4min 1.7min 0 transport_latency_assumed price_change c 90,540,566 76,874,307 6ms 31ms 384ms 12.1s 0 transport_latency_assumed price_change g 93,666,488 35,634 82ms 302ms 6.7s 58.2s 0 transport_latency_assumed price_change h 99,202,254 3,890,668 19ms 48ms 830ms 1.5min 0 transport_latency_assumed price_change i 99,449,440 5,967,608 17ms 47ms 532ms 1.1min 0 transport_latency_assumed price_change k 98,959,532 12,727,403 15ms 43ms 696ms 3.5min 0 transport_latency_assumed tick_size_change c 2,796 2,345 6ms 55ms 493ms 1.3s 0 transport_latency_assumed tick_size_change g 3,104 not meas. 82ms 276ms 5.9s 6.0s 0 transport_latency_assumed tick_size_change h 3,152 173 19ms 41ms 400ms 5.7s 0 transport_latency_assumed tick_size_change i 3,156 177 17ms 35ms 371ms 604ms 0 transport_latency_assumed tick_size_change k 3,144 461 14ms 34ms 27.9s 53.5s 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-28/19/2026-09-28T19.parquet sha256sum 2026-09-28T19.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.