Hour audit: 2026-09-17T12
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-17T12 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T12:00:00.000001670+00:00 · last event 2026-09-17T12:59:59.999973349+00:00
VOLUME 120,805,167 rows · 1,292,335,534 bytes (1.20 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 120,057,969 · e: 119,944,869 · f: 119,897,694 · g: 119,403,292 · c: 116,124,755 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 10,658,992 (8.82%) · e: 766,221 (0.63%) · f: 285,599 (0.24%) · g: 118,170 (0.10%) · c: 108,976,185 (90.21%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 120,805,167 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 dfc153aef1a7fd8e2c30e6e996b6e4ed169d7ec53847254feed8afc40aa0826f
the corpus checksum ledger names this file with the same digest
joined 120,809,763 to merged 120,805,167, minus 4,596 (minus 0.0038%)
boundary drops 4,596 · 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-17T14:00:48Z 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 11,594,329 135,046,851 0-44 6a0d74c9b31132875e5bc8702187f2a70e63fd4f648f1ae19995bc5c6a204bce book 837,897 70,892,809 45-48 075002acf298fdf48a71b32a153ae3fc351362c704ed949f7c098d7094e49ea0 last_trade_price 71,145 4,004,103 49-49 8a5179347062be218ade77e0bb30e86521f392efc8caf7f3a850f3793f87726b market_resolved 732 120,535 50-50 1183d37e53cbacc9a348cd2b6fb0030ac54c59ff87ebbbbbbce2215c4fa64809 new_market 1,438 148,699 51-51 d8831dbe0cee7ecce88a45788867cc941b42e44bc17e89d7627a48a09530fc84 price_change 108,296,038 1,080,613,299 52-465 6cca081756bc6b45b3f38c22a9c2f533da9ba4aebe37cc67a54625fe0459b18a tick_size_change 3,588 132,247 466-466 6c9fcea27c2a12a3600c394d756243fb41a40457ced0b548331a8c7111b8edc6 EVENT MIX count share price_change 108,296,038 89.65% best_bid_ask 11,594,329 9.60% book 837,897 0.69% last_trade_price 71,145 0.06% tick_size_change 3,588 <0.01% new_market 1,438 <0.01% market_resolved 732 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,594,667 11,594,329 338 525 FULL book 839,497 837,897 1,600 171,011 FULL last_trade_price 71,147 71,145 2 98 FULL market_resolved 732 732 0 1 FULL new_market 1,438 1,438 0 0 FULL price_change 108,298,694 108,296,038 2,656 49 FULL tick_size_change 3,588 3,588 0 47 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,235,619 10,575,423 6ms 15ms 117ms 4.2s 0 transport_latency_assumed best_bid_ask e 11,587,503 62,403 39ms 53ms 267ms 15.1s 0 transport_latency_assumed best_bid_ask f 11,587,975 19,528 48ms 65ms 289ms 14.2s 0 transport_latency_assumed best_bid_ask g 11,579,216 2,046 78ms 105ms 519ms 29.5s 0 transport_latency_assumed best_bid_ask h 11,587,338 934,929 19ms 32ms 169ms 18.9s 0 transport_latency_assumed book c 559,398 484,618 1.4min 14.2h 35.7d 110.6d 0 book_staleness book e 244,380 73,001 475ms 21.9min 25.9d 110.6d 0 book_staleness book f 242,645 69,501 419ms 22.2min 25.9d 110.6d 0 book_staleness book g 266,324 93,073 3.0s 26.0min 25.9d 110.6d 0 book_staleness book h 283,677 117,704 172ms 27.3min 25.9d 110.6d 0 book_staleness last_trade_price c 68,647 64,061 12ms 51ms 247ms 5.0s 0 transport_latency_assumed last_trade_price e 69,938 485 61ms 2.0s 9.3s 15.0s 0 transport_latency_assumed last_trade_price f 69,964 196 70ms 1.7s 10.6s 14.3s 0 transport_latency_assumed last_trade_price g 67,372 31 102ms 2.3s 13.8s 24.5s 0 transport_latency_assumed last_trade_price h 70,394 6,372 26ms 92ms 509ms 8.3s 0 transport_latency_assumed market_resolved c 707 690 6ms 25ms 4.8min 4.8min 0 transport_latency_assumed market_resolved e 708 3 117ms 284ms 551ms 49.6s 0 transport_latency_assumed market_resolved f 708 2 124ms 252ms 442ms 49.6s 0 transport_latency_assumed market_resolved g 708 not meas. 213ms 360ms 662ms 876ms 0 transport_latency_assumed market_resolved h 708 37 45ms 91ms 168ms 49.9s 0 transport_latency_assumed new_market c 968 580 95ms 16.9s 26.5s 1.1min 0 transport_latency_assumed new_market e 968 259 188ms 13.7s 24.6s 1.2min 0 transport_latency_assumed new_market f 968 92 225ms 16.4s 26.7s 1.4min 0 transport_latency_assumed new_market g 968 130 306ms 16.9s 30.3s 1.1min 0 transport_latency_assumed new_market h 968 377 129ms 13.6s 24.6s 1.2min 0 transport_latency_assumed price_change c 104,256,008 97,847,620 6ms 17ms 133ms 4.4s 0 transport_latency_assumed price_change e 108,037,784 630,054 39ms 73ms 2.9s 15.1s 0 transport_latency_assumed price_change f 107,991,846 196,268 48ms 87ms 2.7s 14.5s 0 transport_latency_assumed price_change g 107,485,124 22,890 79ms 150ms 4.5s 29.5s 0 transport_latency_assumed price_change h 108,111,296 9,599,206 19ms 37ms 238ms 20.2s 0 transport_latency_assumed tick_size_change c 3,408 3,193 6ms 17ms 61ms 3.8s 0 transport_latency_assumed tick_size_change e 3,588 16 39ms 73ms 182ms 430ms 0 transport_latency_assumed tick_size_change f 3,588 12 48ms 61ms 156ms 269ms 0 transport_latency_assumed tick_size_change g 3,580 not meas. 77ms 95ms 264ms 644ms 0 transport_latency_assumed tick_size_change h 3,588 367 19ms 35ms 75ms 4.3s 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/12/2026-09-17T12.parquet sha256sum 2026-09-17T12.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.