Hour audit: 2026-09-13T11
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-13T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T11:00:00.000008765+00:00 · last event 2026-09-13T11:59:59.999952512+00:00
VOLUME 107,743,466 rows · 1,143,556,015 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 105,909,722 · f: 105,902,504 · e: 105,900,365 · g: 105,868,304 · c: 85,979,746 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 23,728,550 (22.02%) · f: 348,705 (0.32%) · e: 1,154,214 (1.07%) · g: 40,417 (0.04%) · c: 82,471,580 (76.54%) (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 107,743,466 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4a5b1d3445d92be7576c44d4ba719f529c3d661f16f3d83f188358a7308372f5
the corpus checksum ledger names this file with the same digest
joined 107,747,644 to merged 107,743,466, minus 4,178 (minus 0.0039%)
boundary drops 4,178 · 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-13T12:57:26Z 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 10,453,919 115,087,736 0-39 869f43bf0ea855e95e901631ede183d83e936f60beb99fc122bf30df33e5a76e book 1,923,605 83,627,947 40-47 4833f566a7df22c4e8ef5feb6b8650055557c3fcf433d29b58cfaf9739d658e2 last_trade_price 52,852 3,066,742 48-48 6e90e11f8b5327de6f732d742772fd4a6d7a4d3eeca43308536bb04173c6d5e9 market_resolved 1,991 223,147 49-49 d31923b2b9a1d1e7c0c0cb0a52cee2b4c781a2f7d21271b0e9b17ea3c1bf99d6 new_market 2,396 211,678 50-50 1518ee87b54f87eb4378856fa88451f72136afbb6e5c2741b601f9d41590aa33 price_change 95,304,943 939,973,721 51-414 6adaf693649c24828aa78ef6f8803113659138dee507ec99da217be2c954e5cf tick_size_change 3,760 137,889 415-415 84de71fb4cb80128fd161c274a1891db5fef6a8acf3eec09fa0644bc2d070e55 EVENT MIX count share price_change 95,304,943 88.46% best_bid_ask 10,453,919 9.70% book 1,923,605 1.79% last_trade_price 52,852 0.05% tick_size_change 3,760 <0.01% new_market 2,396 <0.01% market_resolved 1,991 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,454,137 10,453,919 218 3,421 FULL book 1,924,183 1,923,605 578 176,975 FULL last_trade_price 52,854 52,852 2 341 FULL market_resolved 1,991 1,991 0 86 FULL new_market 2,396 2,396 0 0 FULL price_change 95,308,323 95,304,943 3,380 1,799 FULL tick_size_change 3,760 3,760 0 232 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,293,148 7,972,710 5ms 11ms 109ms 5.4s 0 transport_latency_assumed best_bid_ask e 10,451,131 110,806 40ms 45ms 199ms 12.4s 0 transport_latency_assumed best_bid_ask f 10,450,779 32,724 47ms 54ms 225ms 13.9s 0 transport_latency_assumed best_bid_ask g 10,448,376 3,289 83ms 107ms 478ms 25.6s 0 transport_latency_assumed best_bid_ask h 10,451,829 2,334,390 18ms 23ms 190ms 1.0min 0 transport_latency_assumed book c 1,892,613 1,882,634 22.0min 1.7d 35.7d 106.6d 0 book_staleness book e 111,520 3,066 42ms 120ms 3.6s 41.8d 0 book_staleness book f 112,630 2,269 50ms 153ms 56.3s 85.0d 0 book_staleness book g 125,809 7,541 88ms 36.2s 1.8d 106.6d 0 book_staleness book h 113,000 28,095 22ms 56ms 3.8min 88.0d 0 book_staleness last_trade_price c 41,479 39,189 11ms 46ms 225ms 5.0s 0 transport_latency_assumed last_trade_price e 52,823 681 47ms 117ms 2.0s 12.4s 0 transport_latency_assumed last_trade_price f 52,749 241 55ms 134ms 2.8s 14.0s 0 transport_latency_assumed last_trade_price g 52,557 47 94ms 248ms 6.9s 25.6s 0 transport_latency_assumed last_trade_price h 52,807 12,694 23ms 64ms 382ms 31.8s 0 transport_latency_assumed market_resolved c 1,594 1,572 7ms 8.2min 14.2min 15.2min 0 transport_latency_assumed market_resolved e 1,356 38 40ms 143ms 688ms 59.8s 0 transport_latency_assumed market_resolved f 1,355 9 48ms 136ms 723ms 59.8s 0 transport_latency_assumed market_resolved g 1,355 not meas. 88ms 250ms 736ms 3.1s 0 transport_latency_assumed market_resolved h 1,356 372 18ms 60ms 476ms 47.9s 0 transport_latency_assumed new_market c 1,582 751 15.3s 4.9min 9.6min 11.3min 0 transport_latency_assumed new_market e 1,357 388 209ms 24.1s 37.6s 1.0min 0 transport_latency_assumed new_market f 1,357 342 192ms 22.9s 31.1s 1.1min 0 transport_latency_assumed new_market g 1,357 216 330ms 23.5s 37.8s 1.9min 0 transport_latency_assumed new_market h 1,357 699 137ms 23.6s 30.7s 57.6s 0 transport_latency_assumed price_change c 75,746,498 72,572,106 5ms 12ms 123ms 6.2s 0 transport_latency_assumed price_change e 95,278,418 1,039,192 40ms 50ms 300ms 12.4s 0 transport_latency_assumed price_change f 95,279,874 313,110 47ms 60ms 341ms 14.0s 0 transport_latency_assumed price_change g 95,235,090 29,324 83ms 126ms 759ms 25.6s 0 transport_latency_assumed price_change h 95,285,613 21,351,211 18ms 26ms 216ms 1.0min 0 transport_latency_assumed tick_size_change c 2,832 2,618 5ms 15ms 193ms 399ms 0 transport_latency_assumed tick_size_change e 3,760 43 40ms 44ms 181ms 627ms 0 transport_latency_assumed tick_size_change f 3,760 10 47ms 53ms 177ms 369ms 0 transport_latency_assumed tick_size_change g 3,760 not meas. 83ms 98ms 463ms 1.0s 0 transport_latency_assumed tick_size_change h 3,760 1,089 18ms 23ms 157ms 5.8s 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/11/2026-09-13T11.parquet sha256sum 2026-09-13T11.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.