Hour audit: 2026-09-14T23
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-14T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T23:00:00.000000952+00:00 · last event 2026-09-14T23:59:59.999999694+00:00
VOLUME 113,093,465 rows · 1,200,426,069 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 111,760,486 · g: 111,607,142 · h: 111,564,363 · e: 111,534,813 · c: 99,196,229 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 484,062 (0.43%) · g: 244,044 (0.22%) · h: 16,866,073 (14.91%) · e: 669,647 (0.59%) · c: 94,829,639 (83.85%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 113,093,465 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 5d105bbcc2f758d7015eda77a7871eed18bb8d6c36bacd5ceaa92745f5e3d81a
the corpus checksum ledger names this file with the same digest
joined 113,099,415 to merged 113,093,465, minus 5,950 (minus 0.0053%)
boundary drops 5,950 · 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-15T00:59:03Z 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,793,924 130,548,884 0-44 c862e0581fff63c9b502e183fd2bc99091b32e6a112f1cc58b91a0630a50ab1c book 1,927,952 98,659,380 45-52 7872c119c21e341de621ec07dc07442b0ebc86d67d705145f5e50b58d9b64acd last_trade_price 47,067 2,690,214 53-53 274ff16df721dd2cef379f994c2f4f7affa20c116cd91cd4c489e45691d976ff market_resolved 944 151,625 54-54 9f16373461d15b67123f0c209782c39cb74ace57bb09202dbb36375eefb29bb5 new_market 810 91,307 55-55 3fba2710cf9a0b84277aa959ebc96460032beee9e49bdeca5f18fec31012a4fd price_change 99,320,392 966,910,766 56-434 0b7c82e5b71723d21d49e055be55a292b20632e92006efa815cdb65ec6165b4e tick_size_change 2,376 87,908 435-435 0af42de15dae5086f6192f5f05c592c3330a56a79935606b15ffb7b103e4fe6b EVENT MIX count share price_change 99,320,392 87.82% best_bid_ask 11,793,924 10.43% book 1,927,952 1.70% last_trade_price 47,067 0.04% tick_size_change 2,376 <0.01% market_resolved 944 <0.01% new_market 810 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,794,210 11,793,924 286 1,279 FULL book 1,931,662 1,927,952 3,710 88,422 FULL last_trade_price 47,069 47,067 2 210 FULL market_resolved 944 944 0 36 FULL new_market 810 810 0 14 FULL price_change 99,322,344 99,320,392 1,952 748 FULL tick_size_change 2,376 2,376 0 64 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,391,517 9,978,998 5ms 10ms 78ms 12.9s 0 transport_latency_assumed best_bid_ask e 11,788,327 49,833 42ms 53ms 138ms 7.5s 0 transport_latency_assumed best_bid_ask f 11,787,564 19,145 48ms 56ms 157ms 5.4s 0 transport_latency_assumed best_bid_ask g 11,786,415 1,234 79ms 95ms 266ms 13.0s 0 transport_latency_assumed best_bid_ask h 11,789,900 1,744,714 17ms 23ms 86ms 8.2s 0 transport_latency_assumed book c 1,322,354 1,082,729 10.9min 2.7d 37.2d 108.1d 0 book_staleness book e 449,385 151,914 3.5min 1.4d 34.2d 108.1d 0 book_staleness book f 692,735 274,442 6.2min 1.9d 34.2d 108.1d 0 book_staleness book g 571,953 227,812 4.9min 1.6d 34.2d 108.1d 0 book_staleness book h 467,485 191,055 3.6min 1.4d 34.2d 108.1d 0 book_staleness last_trade_price c 41,446 39,068 10ms 48ms 225ms 4.8s 0 transport_latency_assumed last_trade_price e 46,734 356 51ms 137ms 889ms 5.8s 0 transport_latency_assumed last_trade_price f 46,973 271 55ms 151ms 1.2s 5.4s 0 transport_latency_assumed last_trade_price g 46,790 61 93ms 225ms 3.9s 12.5s 0 transport_latency_assumed last_trade_price h 46,858 7,311 23ms 73ms 297ms 6.9s 0 transport_latency_assumed market_resolved c 880 858 5ms 14ms 5.4min 5.5min 0 transport_latency_assumed market_resolved e 899 1 43ms 124ms 415ms 55.1s 0 transport_latency_assumed market_resolved f 898 1 48ms 128ms 391ms 806ms 0 transport_latency_assumed market_resolved g 899 not meas. 85ms 242ms 727ms 1.6s 0 transport_latency_assumed market_resolved h 899 84 18ms 53ms 334ms 1.0min 0 transport_latency_assumed new_market c 587 345 74ms 28.9s 15.4min 77.1d 0 transport_latency_assumed new_market e 573 83 127ms 12.9s 41.6s 1.2min 0 transport_latency_assumed new_market f 578 41 150ms 14.6s 58.3s 77.1d 0 transport_latency_assumed new_market g 573 51 246ms 22.7s 44.4s 51.8s 0 transport_latency_assumed new_market h 573 290 59ms 12.5s 36.7s 53.0s 0 transport_latency_assumed price_change c 87,437,313 83,725,549 5ms 11ms 89ms 13.7s 0 transport_latency_assumed price_change e 99,246,519 467,456 42ms 56ms 218ms 9.9s 0 transport_latency_assumed price_change f 99,229,362 190,162 48ms 60ms 231ms 5.4s 0 transport_latency_assumed price_change g 99,198,144 14,886 80ms 101ms 402ms 13.5s 0 transport_latency_assumed price_change h 99,256,276 14,922,339 18ms 25ms 111ms 8.2s 0 transport_latency_assumed tick_size_change c 2,132 2,092 5ms 8ms 31ms 130ms 0 transport_latency_assumed tick_size_change e 2,376 4 42ms 51ms 92ms 303ms 0 transport_latency_assumed tick_size_change f 2,376 not meas. 48ms 55ms 139ms 164ms 0 transport_latency_assumed tick_size_change g 2,368 not meas. 79ms 93ms 146ms 242ms 0 transport_latency_assumed tick_size_change h 2,372 280 17ms 22ms 52ms 87ms 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-14/23/2026-09-14T23.parquet sha256sum 2026-09-14T23.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.