Hour audit: 2026-09-13T21
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-13T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T21:00:00.000706287+00:00 · last event 2026-09-13T21:59:59.999924143+00:00
VOLUME 131,505,072 rows · 1,433,549,144 bytes (1.34 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 129,076,373 · h: 129,054,608 · f: 124,309,828 · g: 111,115,525 · c: 100,537,523 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 3,906,806 (2.97%) · h: 29,589,211 (22.50%) · f: 819,545 (0.62%) · g: 406,072 (0.31%) · c: 96,783,438 (73.60%) (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 131,505,072 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8b294833baf5e70101c06c9c9f45f9a49c41f0cdde7d836a4682b653601afe9a
the corpus checksum ledger names this file with the same digest
joined 131,507,953 to merged 131,505,072, minus 2,881 (minus 0.0022%)
boundary drops 2,881 · 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-13T23:08:54Z 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 13,997,764 155,023,370 0-53 0ff2ca7b808177036417091625e99140001298a6e91126778710979103398cfe book 2,522,736 99,609,275 54-63 8f100382bc67ec6c91370494c489f15568db6843e1a5bfb9ff2fa2d64cdcf722 last_trade_price 53,787 3,172,179 64-64 2cb6cde54417c61d48764993b47db855bf846efdd361399f28f5c0ecd0fbd327 market_resolved 7,977 705,182 65-65 2c4915d45c316bd18857deceb3fa002585e08c9c69940152ccf0adf89cbb2cb8 new_market 1,974 147,274 66-66 9a3fe845b74d98c154fd1c0707b793a647b96d07ca32ec55c495d83a799a6dd6 price_change 114,914,282 1,173,154,643 67-505 dc1635717b97aaf12b7d3c7f5567d204bfcceef2cbd65c9098d67f5d1f5fb312 tick_size_change 6,552 241,971 506-506 50960f33ca9137b250aaf88f5041407008754ec83e123d99be50b2b1098bbe55 EVENT MIX count share price_change 114,914,282 87.38% best_bid_ask 13,997,764 10.64% book 2,522,736 1.92% last_trade_price 53,787 0.04% market_resolved 7,977 <0.01% tick_size_change 6,552 <0.01% new_market 1,974 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,998,057 13,997,764 293 5,353 FULL book 2,522,792 2,522,736 56 172,157 FULL last_trade_price 53,787 53,787 0 753 FULL market_resolved 7,977 7,977 0 259 FULL new_market 1,974 1,974 0 0 FULL price_change 114,916,814 114,914,282 2,532 3,912 FULL tick_size_change 6,552 6,552 0 767 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,671,348 10,309,166 5ms 10ms 90ms 7.6s 0 transport_latency_assumed best_bid_ask e 13,995,807 412,311 41ms 49ms 175ms 4.4s 0 transport_latency_assumed best_bid_ask f 13,452,630 67,981 46ms 57ms 204ms 10.0s 0 transport_latency_assumed best_bid_ask g 11,862,004 1,909 82ms 101ms 371ms 14.8s 0 transport_latency_assumed best_bid_ask h 13,988,794 3,206,397 17ms 37ms 132ms 9.9s 0 transport_latency_assumed book c 2,178,606 1,956,883 28.0min 2.1d 36.3d 107.0d 0 book_staleness book e 112,451 5,305 44ms 126ms 1.8s 4.5s 0 book_staleness book f 474,925 128,404 3.9min 1.2d 33.1d 107.0d 0 book_staleness book g 1,548,974 384,145 22.5min 2.1d 36.2d 107.0d 0 book_staleness book h 173,969 47,999 38ms 5.1h 21.1d 107.0d 0 book_staleness last_trade_price c 39,727 37,843 10ms 45ms 256ms 5.0s 0 transport_latency_assumed last_trade_price e 53,747 1,743 49ms 134ms 1.1s 5.0s 0 transport_latency_assumed last_trade_price f 50,714 420 53ms 145ms 958ms 5.0s 0 transport_latency_assumed last_trade_price g 44,942 23 93ms 226ms 1.5s 10.1s 0 transport_latency_assumed last_trade_price h 53,655 13,758 24ms 74ms 336ms 5.5s 0 transport_latency_assumed market_resolved c 6,440 6,052 3.8min 13.5min 19.0min 19.9min 0 transport_latency_assumed market_resolved e 4,115 102 64ms 160ms 386ms 50.3s 0 transport_latency_assumed market_resolved f 4,108 234 74ms 207ms 4.5min 5.0min 0 transport_latency_assumed market_resolved g 4,333 433 185ms 5.0min 9.3min 9.7min 0 transport_latency_assumed market_resolved h 4,109 1,156 34ms 77ms 298ms 36.7s 0 transport_latency_assumed new_market c 1,423 1,087 24.1s 10.3min 1.0h 2.1h 0 transport_latency_assumed new_market e 891 176 191ms 16.0s 24.6s 7.7min 0 transport_latency_assumed new_market f 891 214 202ms 16.0s 24.4s 1.2h 0 transport_latency_assumed new_market g 1,014 126 392ms 3.6min 19.5min 2.0h 0 transport_latency_assumed new_market h 891 371 153ms 18.8s 25.4s 1.3h 0 transport_latency_assumed price_change c 87,636,223 84,468,791 5ms 11ms 105ms 8.2s 0 transport_latency_assumed price_change e 114,902,810 3,486,847 42ms 53ms 243ms 4.5s 0 transport_latency_assumed price_change f 110,320,312 622,256 46ms 62ms 276ms 10.2s 0 transport_latency_assumed price_change g 97,649,238 19,436 83ms 109ms 501ms 15.0s 0 transport_latency_assumed price_change h 114,826,638 26,316,952 17ms 40ms 156ms 9.9s 0 transport_latency_assumed tick_size_change c 3,756 3,616 5ms 9ms 108ms 415ms 0 transport_latency_assumed tick_size_change e 6,552 322 41ms 45ms 122ms 480ms 0 transport_latency_assumed tick_size_change f 6,248 36 46ms 52ms 113ms 507ms 0 transport_latency_assumed tick_size_change g 5,020 not meas. 82ms 99ms 315ms 1.2s 0 transport_latency_assumed tick_size_change h 6,552 2,578 17ms 40ms 202ms 743ms 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/21/2026-09-13T21.parquet sha256sum 2026-09-13T21.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.