Hour audit: 2026-09-14T20
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-14T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T20:00:00.000005402+00:00 · last event 2026-09-14T20:59:59.999942163+00:00
VOLUME 112,958,344 rows · 1,218,968,102 bytes (1.14 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 111,788,979 · f: 111,638,590 · e: 111,564,130 · g: 111,458,894 · c: 99,782,351 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 17,701,067 (15.67%) · f: 639,941 (0.57%) · e: 1,077,371 (0.95%) · g: 129,586 (0.11%) · c: 93,410,379 (82.69%) (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 112,958,344 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 bc7701891f841fcaffab16c6666ab781846fff7a4d08f7f2e4da677d8739458c
the corpus checksum ledger names this file with the same digest
joined 112,960,419 to merged 112,958,344, minus 2,075 (minus 0.0018%)
boundary drops 2,075 · 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-14T21:59:02Z 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,109,961 127,306,862 0-42 cc4d8794f921e3a525427d74f2cb4af89f342611ff38acd1648e08db7c2ab30b book 1,241,929 75,230,070 43-47 e91ff875020f669cc329d45d73d95e8cc44c5088ab3c3bbae0f998550a3657c0 last_trade_price 54,630 3,198,620 48-48 1500567445a389f8fbd3b0ab659ed79b4601be436e4ebe71d83b153d4d717b7b market_resolved 1,461 207,200 49-49 50ce3528625f8df9fd91c1f2a5280d8f90a88ebfa9bbd22a5ee0af0da9ebf37c new_market 6,929 672,489 50-50 f729b25166b797e940aa57120ba0cb9036915be2775fcc4755cf102b21e456f7 price_change 100,539,058 1,010,905,711 51-434 2937713f39d8d405ff32e60654413a88b7d1de483098990df56180759b74bdca tick_size_change 4,376 161,262 435-435 76eeab7c248d2bc97787250216bd74554fa3840882d0d8c04b29fa81b8b8665a EVENT MIX count share price_change 100,539,058 89.01% best_bid_ask 11,109,961 9.84% book 1,241,929 1.10% last_trade_price 54,630 0.05% new_market 6,929 <0.01% tick_size_change 4,376 <0.01% market_resolved 1,461 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,110,176 11,109,961 215 1,674 FULL book 1,241,967 1,241,929 38 169,245 FULL last_trade_price 54,632 54,630 2 250 FULL market_resolved 1,461 1,461 0 21 FULL new_market 6,929 6,929 0 9 FULL price_change 100,540,878 100,539,058 1,820 1,342 FULL tick_size_change 4,376 4,376 0 132 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,812,413 9,202,046 5ms 18ms 266ms 8.2s 0 transport_latency_assumed best_bid_ask e 11,103,233 104,640 46ms 85ms 467ms 28.9s 0 transport_latency_assumed best_bid_ask f 11,104,880 61,469 49ms 87ms 482ms 25.5s 0 transport_latency_assumed best_bid_ask g 11,096,697 5,273 80ms 208ms 1.1s 48.9s 0 transport_latency_assumed best_bid_ask h 11,108,732 1,736,533 18ms 39ms 657ms 56.5s 0 transport_latency_assumed book c 1,155,196 1,131,021 17.0min 2.4d 37.1d 107.9d 0 book_staleness book e 132,577 8,806 58ms 16.4s 3.1d 89.4d 0 book_staleness book f 135,303 9,477 58ms 26.1s 3.1d 89.4d 0 book_staleness book g 272,337 68,248 19.5s 23.1h 23.3d 107.9d 0 book_staleness book h 126,899 24,377 23ms 1.9s 19.2h 89.4d 0 book_staleness last_trade_price c 47,519 44,372 11ms 62ms 387ms 5.0s 0 transport_latency_assumed last_trade_price e 53,570 474 65ms 375ms 9.9s 28.8s 0 transport_latency_assumed last_trade_price f 53,968 356 69ms 450ms 12.7s 25.5s 0 transport_latency_assumed last_trade_price g 52,797 45 107ms 1.3s 18.3s 47.3s 0 transport_latency_assumed last_trade_price h 54,598 9,383 25ms 113ms 810ms 38.8s 0 transport_latency_assumed market_resolved c 1,381 1,337 6ms 4.5min 7.4min 10.9min 0 transport_latency_assumed market_resolved e 1,276 3 55ms 199ms 52.4s 1.0min 0 transport_latency_assumed market_resolved f 1,276 5 52ms 194ms 459ms 792ms 0 transport_latency_assumed market_resolved g 1,276 not meas. 91ms 262ms 751ms 1.1s 0 transport_latency_assumed market_resolved h 1,276 116 23ms 80ms 59.9s 1.0min 0 transport_latency_assumed new_market c 4,605 2,817 168ms 4.4min 7.4min 10.4min 0 transport_latency_assumed new_market e 4,166 859 240ms 54.6s 3.2min 4.4min 0 transport_latency_assumed new_market f 4,159 689 275ms 57.3s 2.4min 4.3min 0 transport_latency_assumed new_market g 4,165 586 389ms 1.0min 3.6min 4.4min 0 transport_latency_assumed new_market h 4,164 1,978 176ms 1.0min 3.6min 4.4min 0 transport_latency_assumed price_change c 88,757,389 83,025,093 6ms 21ms 281ms 8.3s 0 transport_latency_assumed price_change e 100,264,932 962,564 47ms 120ms 1.1s 28.9s 0 transport_latency_assumed price_change f 100,334,628 567,941 49ms 121ms 1.0s 25.7s 0 transport_latency_assumed price_change g 100,027,246 55,434 81ms 285ms 4.0s 49.0s 0 transport_latency_assumed price_change h 100,488,934 15,928,026 18ms 45ms 664ms 56.6s 0 transport_latency_assumed tick_size_change c 3,848 3,693 5ms 11ms 67ms 302ms 0 transport_latency_assumed tick_size_change e 4,376 25 45ms 61ms 237ms 11.6s 0 transport_latency_assumed tick_size_change f 4,376 4 48ms 61ms 269ms 1.3s 0 transport_latency_assumed tick_size_change g 4,376 not meas. 79ms 124ms 528ms 17.8s 0 transport_latency_assumed tick_size_change h 4,376 654 18ms 25ms 244ms 6.9s 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/20/2026-09-14T20.parquet sha256sum 2026-09-14T20.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.