Hour audit: 2026-09-12T15
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-12T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T15:00:00.000009460+00:00 · last event 2026-09-12T15:59:59.999986794+00:00
VOLUME 135,080,676 rows · 1,490,380,992 bytes (1.39 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 130,643,542 · e: 130,619,193 · g: 125,162,436 · f: 120,224,726 · c: 72,971,260 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 61,280,665 (45.37%) · e: 2,362,320 (1.75%) · g: 177,751 (0.13%) · f: 857,146 (0.63%) · c: 70,402,794 (52.12%) (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 135,080,676 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f92d77dc03c0a30152554c405fb21827bec780f5a61b83ac1a8ce89b39361e37
the corpus checksum ledger names this file with the same digest
joined 135,087,505 to merged 135,080,676, minus 6,829 (minus 0.0051%)
boundary drops 6,829 · 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-12T17:02:04Z 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,686,138 142,646,248 0-48 d6805f712265478eb107a0c2d363b5a08f916a6e104d4febe5279416223fabb7 book 4,653,263 143,452,594 49-66 936875fa5b60b50a7907ebf95bbb93575f8a575c7c5a3f2b16ad69892433b386 last_trade_price 70,003 4,174,898 67-67 8354e5f182060f68221f50f1a01400d6b10c290ce841fc2c470e2605a516744d market_resolved 5,337 434,708 68-68 b8cd6fdeb4e7f3c0e266df98244a560685665b8a8a85e34f4a123840f4f3776d new_market 1,771 92,903 69-69 ff82fa2420fd4a3e30b429aa6818f2de686945b89577fbf37d52b21dc6db24dc price_change 117,650,964 1,197,558,261 70-518 409f8cb123649faaa3da9258411e9331d4f11caf6158d2102fb52815ab5cb909 tick_size_change 13,200 486,932 519-519 0d5f15f4853a341d9616367d7b2f4a8f97d444fe41f8cfed440475c6a0524c33 EVENT MIX count share price_change 117,650,964 87.10% best_bid_ask 12,686,138 9.39% book 4,653,263 3.44% last_trade_price 70,003 0.05% tick_size_change 13,200 <0.01% market_resolved 5,337 <0.01% new_market 1,771 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,686,358 12,686,138 220 10,608 FULL book 4,656,979 4,653,263 3,716 188,502 FULL last_trade_price 70,004 70,003 1 1,660 FULL market_resolved 5,337 5,337 0 118 FULL new_market 1,771 1,771 0 0 FULL price_change 117,653,856 117,650,964 2,892 7,190 FULL tick_size_change 13,200 13,200 0 1,650 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,734,497 6,516,557 6ms 11ms 57ms 4.4s 0 transport_latency_assumed best_bid_ask e 12,684,363 216,667 43ms 48ms 118ms 3.3s 0 transport_latency_assumed best_bid_ask f 11,592,091 44,254 47ms 53ms 134ms 3.9s 0 transport_latency_assumed best_bid_ask g 12,121,846 2,460 77ms 92ms 254ms 13.6s 0 transport_latency_assumed best_bid_ask h 12,684,909 5,906,200 18ms 26ms 86ms 12.1s 0 transport_latency_assumed book c 4,281,518 3,996,475 18.3min 21.7h 31.9d 105.7d 0 book_staleness book e 239,455 38,436 55ms 3.1h 15.8d 105.7d 0 book_staleness book f 1,005,702 354,391 7.6min 21.6h 30.8d 105.7d 0 book_staleness book g 571,330 148,155 3.4min 17.2h 23.8d 105.7d 0 book_staleness book h 272,016 115,806 66ms 5.3h 21.1d 105.7d 0 book_staleness last_trade_price c 33,738 32,341 11ms 45ms 219ms 5.0s 0 transport_latency_assumed last_trade_price e 69,941 1,640 50ms 105ms 477ms 5.0s 0 transport_latency_assumed last_trade_price f 63,477 509 54ms 116ms 682ms 5.0s 0 transport_latency_assumed last_trade_price g 66,199 43 92ms 216ms 2.1s 9.8s 0 transport_latency_assumed last_trade_price h 69,926 35,470 24ms 65ms 285ms 6.7s 0 transport_latency_assumed market_resolved c 4,293 4,133 6.1min 16.9min 21.9min 22.2min 0 transport_latency_assumed market_resolved e 2,473 70 44ms 121ms 294ms 719ms 0 transport_latency_assumed market_resolved f 2,595 98 49ms 59.0s 10.9min 12.5min 0 transport_latency_assumed market_resolved g 2,491 38 84ms 234ms 4.8min 6.3min 0 transport_latency_assumed market_resolved h 2,473 998 19ms 54ms 53.5s 1.0min 0 transport_latency_assumed new_market c 1,682 1,435 7.7min 16.7min 20.0min 24.6min 0 transport_latency_assumed new_market e 515 88 120ms 14.1s 28.4s 5.7min 0 transport_latency_assumed new_market f 532 72 133ms 16.5s 10.3min 10.9min 0 transport_latency_assumed new_market g 515 32 210ms 11.4s 1.0min 5.3min 0 transport_latency_assumed new_market h 515 144 71ms 11.7s 52.4s 1.8min 0 transport_latency_assumed price_change c 61,908,644 59,845,230 6ms 12ms 63ms 5.4s 0 transport_latency_assumed price_change e 117,609,246 2,105,323 43ms 50ms 162ms 3.8s 0 transport_latency_assumed price_change f 107,547,869 457,802 47ms 56ms 177ms 4.0s 0 transport_latency_assumed price_change g 112,387,119 27,023 77ms 94ms 343ms 13.8s 0 transport_latency_assumed price_change h 117,600,503 55,215,586 18ms 28ms 102ms 15.6s 0 transport_latency_assumed tick_size_change c 6,888 6,623 6ms 12ms 45ms 149ms 0 transport_latency_assumed tick_size_change e 13,200 96 43ms 48ms 120ms 2.0s 0 transport_latency_assumed tick_size_change f 12,460 20 47ms 54ms 134ms 474ms 0 transport_latency_assumed tick_size_change g 12,936 not meas. 77ms 91ms 240ms 1.4s 0 transport_latency_assumed tick_size_change h 13,200 6,461 18ms 23ms 69ms 1.0s 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-12/15/2026-09-12T15.parquet sha256sum 2026-09-12T15.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.