Hour audit: 2026-09-18T08
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-18T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T08:00:00.000021215+00:00 · last event 2026-09-18T08:59:59.999943866+00:00
VOLUME 105,231,701 rows · 1,075,354,814 bytes (1.00 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 105,102,886 · f: 105,041,086 · h: 104,995,485 · g: 104,952,295 · e: 104,848,427 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 100,425,813 (95.43%) · f: 247,504 (0.24%) · h: 3,924,660 (3.73%) · g: 63,065 (0.06%) · e: 570,659 (0.54%) (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 105,231,701 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0ccae2cc78163fb23ddcf39bfd8fbc49c59b9c35401f252271793593de3c20ec
the corpus checksum ledger names this file with the same digest
joined 105,233,385 to merged 105,231,701, minus 1,684 (minus 0.0016%)
boundary drops 1,684 · 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-18T09:58:39Z 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 9,478,722 110,884,693 0-36 53f353232bf50d613b52796e48ff45c5a26be890feac358d8e9d38b87746e2b0 book 215,443 23,331,116 37-37 9a35d6de1577055fe89bbc394f33bbcc90247fa7fe34e02f7160de326fe9ef03 last_trade_price 51,048 3,192,759 38-38 d6eefe207a4b14e088f7c8958a149ef2f986a139a53f4ac9d04c0a075380b4fb market_resolved 503 81,357 39-39 0e2b760db36cb156c366a2e23f56785d45d4d38e181698d39a8432325ca2330e new_market 2,384 235,967 40-40 63d00ca4851cecc894272e2c1e262063ed2f6414d1b5d34365b1b78b194de706 price_change 95,480,965 936,331,616 41-405 f30e545ed7013a369ee4faa2b627c4c5b04dd8827dcbb92e3d23b4fa8e3d2723 tick_size_change 2,636 96,391 406-406 779956a4c4c37c6bf3def72af9d49c77eb6209775f519fb347da8cbf8c2768a5 EVENT MIX count share price_change 95,480,965 90.73% best_bid_ask 9,478,722 9.01% book 215,443 0.20% last_trade_price 51,048 0.05% tick_size_change 2,636 <0.01% new_market 2,384 <0.01% market_resolved 503 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,478,916 9,478,722 194 575 FULL book 215,453 215,443 10 43,904 FULL last_trade_price 51,048 51,048 0 0 FULL market_resolved 503 503 0 0 FULL new_market 2,384 2,384 0 0 FULL price_change 95,482,445 95,480,965 1,480 404 FULL tick_size_change 2,636 2,636 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,472,119 9,075,260 5ms 10ms 133ms 13.4s 0 transport_latency_assumed best_bid_ask e 9,469,689 43,656 40ms 47ms 218ms 16.7s 0 transport_latency_assumed best_bid_ask f 9,474,279 18,863 47ms 57ms 241ms 11.5s 0 transport_latency_assumed best_bid_ask g 9,472,283 3,775 78ms 99ms 375ms 25.1s 0 transport_latency_assumed best_bid_ask h 9,473,067 337,168 18ms 28ms 241ms 45.0s 0 transport_latency_assumed book c 193,533 186,485 33ms 30.1min 26.8d 111.4d 0 book_staleness book e 112,577 8,804 42ms 1.0s 38.0min 92.9d 0 book_staleness book f 110,379 4,091 50ms 544ms 15.1min 92.9d 0 book_staleness book g 111,056 5,820 84ms 1.6s 34.0min 111.4d 0 book_staleness book h 112,349 10,243 22ms 292ms 1.2h 92.7d 0 book_staleness last_trade_price c 50,868 48,321 10ms 48ms 272ms 12.1s 0 transport_latency_assumed last_trade_price e 49,933 401 47ms 175ms 6.0s 16.7s 0 transport_latency_assumed last_trade_price f 50,735 252 56ms 252ms 4.6s 11.6s 0 transport_latency_assumed last_trade_price g 50,055 106 90ms 322ms 11.6s 25.2s 0 transport_latency_assumed last_trade_price h 50,618 1,968 24ms 122ms 789ms 10.6s 0 transport_latency_assumed market_resolved c 492 477 5ms 13ms 190ms 456ms 0 transport_latency_assumed market_resolved e 492 3 41ms 193ms 513ms 955ms 0 transport_latency_assumed market_resolved f 492 1 49ms 214ms 681ms 809ms 0 transport_latency_assumed market_resolved g 492 not meas. 84ms 362ms 920ms 1.8s 0 transport_latency_assumed market_resolved h 492 22 19ms 117ms 1.0min 1.0min 0 transport_latency_assumed new_market c 1,549 1,006 91ms 18.6s 27.3s 1.2min 0 transport_latency_assumed new_market e 1,549 391 168ms 19.9s 27.2s 57.6s 0 transport_latency_assumed new_market f 1,549 288 238ms 19.3s 31.1s 1.1min 0 transport_latency_assumed new_market g 1,549 192 234ms 18.2s 27.1s 1.2min 0 transport_latency_assumed new_market h 1,549 507 151ms 17.5s 25.2s 1.1min 0 transport_latency_assumed price_change c 95,381,689 91,111,660 5ms 12ms 164ms 13.8s 0 transport_latency_assumed price_change e 95,211,551 517,404 40ms 57ms 410ms 16.8s 0 transport_latency_assumed price_change f 95,401,016 224,009 48ms 67ms 493ms 11.5s 0 transport_latency_assumed price_change g 95,314,224 53,172 79ms 107ms 697ms 25.1s 0 transport_latency_assumed price_change h 95,354,774 3,574,720 18ms 34ms 350ms 46.8s 0 transport_latency_assumed tick_size_change c 2,636 2,604 5ms 7ms 22ms 620ms 0 transport_latency_assumed tick_size_change e 2,636 not meas. 40ms 43ms 114ms 183ms 0 transport_latency_assumed tick_size_change f 2,636 not meas. 47ms 51ms 152ms 190ms 0 transport_latency_assumed tick_size_change g 2,636 not meas. 78ms 92ms 209ms 349ms 0 transport_latency_assumed tick_size_change h 2,636 32 18ms 27ms 72ms 1.2s 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-18/08/2026-09-18T08.parquet sha256sum 2026-09-18T08.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.