Hour audit: 2026-09-13T13
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-13T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T13:00:00.000330419+00:00 · last event 2026-09-13T13:59:59.999951207+00:00
VOLUME 115,583,209 rows · 1,221,972,961 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 113,733,901 · g: 113,730,639 · e: 113,728,458 · f: 113,727,772 · c: 91,903,474 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 25,573,003 (22.13%) · g: 32,589 (0.03%) · e: 990,473 (0.86%) · f: 208,347 (0.18%) · c: 88,778,797 (76.81%) (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 115,583,209 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 9146ccf1a69c65443f55eaa07be986d35020bf85308280158de08ebd39d68ee8
the corpus checksum ledger names this file with the same digest
joined 115,585,283 to merged 115,583,209, minus 2,074 (minus 0.0018%)
boundary drops 2,074 · 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-13T15:01:24Z 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,393,086 135,232,438 0-47 a6f67d13b2efb047653204fb7e76b387845fea1d5a773be97d12b6ac6653d2df book 1,943,567 83,635,065 48-55 179954a41d8af8f3f9f13b487a9a34a25be09545f69848bb7c2c293768c5246f last_trade_price 56,647 3,361,580 56-56 8f457f1c1d82f7b168fb77d4c42ea0f4b64a5a32f117bfc1c8eddf100ba0398f market_resolved 1,610 212,462 57-57 5d9dea4a4daf79cd8e3bdd4c7a664ae8843d229dfcd5eb5dbad261b71282298e new_market 1,149 100,575 58-58 41e1b83bacb8a6eb805857abbcb9819cf95d311452cff0664451691ec63b6db5 price_change 101,179,126 997,833,409 59-444 4d0808c3f2d341eb94f514ea70b35f06480727f16372b2e32f2ba07b201299e6 tick_size_change 8,024 282,085 445-445 8e5a2859b8c1e5dc49318b88801cbe9df7cdcc9fce31ad2f045895cb919d31e2 EVENT MIX count share price_change 101,179,126 87.54% best_bid_ask 12,393,086 10.72% book 1,943,567 1.68% last_trade_price 56,647 0.05% tick_size_change 8,024 <0.01% market_resolved 1,610 <0.01% new_market 1,149 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,393,320 12,393,086 234 3,660 FULL book 1,943,633 1,943,567 66 175,383 FULL last_trade_price 56,647 56,647 0 485 FULL market_resolved 1,610 1,610 0 180 FULL new_market 1,149 1,149 0 1 FULL price_change 101,180,900 101,179,126 1,774 2,100 FULL tick_size_change 8,024 8,024 0 322 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,872,678 9,549,426 5ms 10ms 71ms 4.0s 0 transport_latency_assumed best_bid_ask e 12,391,774 102,660 39ms 43ms 117ms 3.8s 0 transport_latency_assumed best_bid_ask f 12,391,606 19,296 47ms 52ms 143ms 4.1s 0 transport_latency_assumed best_bid_ask g 12,389,483 1,810 80ms 96ms 257ms 13.4s 0 transport_latency_assumed best_bid_ask h 12,392,270 2,719,894 18ms 23ms 83ms 42.4s 0 transport_latency_assumed book c 1,908,321 1,897,159 25.3min 1.8d 35.8d 106.6d 0 book_staleness book e 117,235 2,282 41ms 75ms 1.3s 88.0d 0 book_staleness book f 119,676 1,919 49ms 111ms 1.6h 88.1d 0 book_staleness book g 140,684 12,760 86ms 7.8min 6.1d 88.1d 0 book_staleness book h 117,961 29,447 21ms 40ms 3.2s 85.1d 0 book_staleness last_trade_price c 43,778 41,779 10ms 41ms 181ms 5.0s 0 transport_latency_assumed last_trade_price e 56,622 667 46ms 98ms 681ms 5.0s 0 transport_latency_assumed last_trade_price f 56,575 156 54ms 108ms 663ms 5.0s 0 transport_latency_assumed last_trade_price g 56,617 66 90ms 181ms 749ms 7.7s 0 transport_latency_assumed last_trade_price h 56,607 13,979 23ms 56ms 234ms 7.5s 0 transport_latency_assumed market_resolved c 1,192 1,095 6ms 4.6min 9.6min 10.4min 0 transport_latency_assumed market_resolved e 1,289 92 40ms 123ms 57.6s 1.0min 0 transport_latency_assumed market_resolved f 1,289 4 48ms 153ms 57.6s 1.0min 0 transport_latency_assumed market_resolved g 1,289 1 84ms 223ms 443ms 837ms 0 transport_latency_assumed market_resolved h 1,289 418 19ms 46ms 285ms 59.4s 0 transport_latency_assumed new_market c 806 493 436ms 4.4min 6.4min 1.2h 0 transport_latency_assumed new_market e 618 170 193ms 18.1s 27.5s 1.1min 0 transport_latency_assumed new_market f 618 90 190ms 19.1s 27.1s 1.1min 0 transport_latency_assumed new_market g 618 78 312ms 16.4s 26.5s 1.3min 0 transport_latency_assumed new_market h 618 318 142ms 20.3s 28.8s 1.6min 0 transport_latency_assumed price_change c 80,069,963 77,282,255 5ms 11ms 79ms 8.7s 0 transport_latency_assumed price_change e 101,152,896 884,580 39ms 45ms 166ms 3.8s 0 transport_latency_assumed price_change f 101,149,984 186,882 47ms 55ms 190ms 4.5s 0 transport_latency_assumed price_change g 101,133,924 17,874 81ms 99ms 345ms 14.1s 0 transport_latency_assumed price_change h 101,157,132 22,807,535 18ms 25ms 98ms 42.5s 0 transport_latency_assumed tick_size_change c 6,736 6,590 5ms 9ms 28ms 247ms 0 transport_latency_assumed tick_size_change e 8,024 22 39ms 43ms 95ms 201ms 0 transport_latency_assumed tick_size_change f 8,024 not meas. 47ms 52ms 102ms 220ms 0 transport_latency_assumed tick_size_change g 8,024 not meas. 80ms 95ms 169ms 592ms 0 transport_latency_assumed tick_size_change h 8,024 1,412 18ms 23ms 65ms 238ms 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-13/13/2026-09-13T13.parquet sha256sum 2026-09-13T13.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.