Hour audit: 2026-09-14T10
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-14T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-14T10:00:00.000009643+00:00 · last event 2026-09-14T10:59:59.999934868+00:00
VOLUME 106,211,208 rows · 1,109,993,416 bytes (1.03 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 104,808,218 · e: 104,796,328 · h: 104,793,390 · g: 104,745,951 · c: 89,967,529 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 260,041 (0.24%) · e: 637,549 (0.60%) · h: 19,934,838 (18.77%) · g: 38,304 (0.04%) · c: 85,340,476 (80.35%) (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 106,211,208 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 70186def3fb6c10f1ffc67ff1a595de505f747242c3701d73b5eef0269404c84
the corpus checksum ledger names this file with the same digest
joined 106,214,604 to merged 106,211,208, minus 3,396 (minus 0.0032%)
boundary drops 3,396 · 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-14T11:57:10Z 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,655,699 116,344,768 0-40 715d7b39efa510636be12bfb9997be4c772a8447050149ffa4b9a3be34f8988a book 1,452,410 73,991,449 41-46 cc34546c87e40725e438921b22bbafec14bff2497fed77d1e6bc8255fbbac9c6 last_trade_price 51,139 2,861,265 47-47 a383d181620482811c64990b248d62b8d8a596f5bb5ba9ef03dd4bb80328a549 market_resolved 945 128,222 48-48 099dc50d6c6b5fe48c92a7e41d6fd8e781e82fd8cb104130396b58d366a764df new_market 1,607 152,643 49-49 85dd4a3da6cbe6cc54790ef65883a4aaaa57222aa92c47efdfdecc5a732212aa price_change 94,047,416 915,231,608 50-408 0d469d13755ee1dcc0761597990fb73f9c4850e31e716907ac54c633d2b9c161 tick_size_change 1,992 74,009 409-409 30bfdae0b5e13e800be782f28c48b9f81b1aedd3a28e23d90fcbb211cb2dfa5c EVENT MIX count share price_change 94,047,416 88.55% best_bid_ask 10,655,699 10.03% book 1,452,410 1.37% last_trade_price 51,139 0.05% tick_size_change 1,992 <0.01% new_market 1,607 <0.01% market_resolved 945 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,655,961 10,655,699 262 1,571 FULL book 1,452,428 1,452,410 18 163,084 FULL last_trade_price 51,141 51,139 2 292 FULL market_resolved 945 945 0 59 FULL new_market 1,607 1,607 0 0 FULL price_change 94,050,530 94,047,416 3,114 1,171 FULL tick_size_change 1,992 1,992 0 59 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,964,737 8,518,089 5ms 13ms 111ms 3.7s 0 transport_latency_assumed best_bid_ask e 10,652,820 60,670 41ms 47ms 187ms 11.3s 0 transport_latency_assumed best_bid_ask f 10,652,438 23,409 48ms 55ms 196ms 9.2s 0 transport_latency_assumed best_bid_ask g 10,649,071 1,872 80ms 99ms 389ms 23.6s 0 transport_latency_assumed best_bid_ask h 10,653,216 2,051,659 18ms 24ms 141ms 15.1s 0 transport_latency_assumed book c 1,425,318 1,410,824 39.6min 2.7d 36.9d 107.5d 0 book_staleness book e 110,434 3,334 43ms 265ms 2.2h 88.9d 0 book_staleness book f 109,806 3,021 50ms 270ms 1.2h 89.0d 0 book_staleness book g 133,009 14,091 91ms 53.6min 7.0d 107.5d 0 book_staleness book h 110,729 21,140 22ms 105ms 6.1h 89.0d 0 book_staleness last_trade_price c 44,105 41,486 11ms 52ms 246ms 5.0s 0 transport_latency_assumed last_trade_price e 50,932 445 50ms 190ms 2.1s 11.4s 0 transport_latency_assumed last_trade_price f 50,826 243 57ms 204ms 2.6s 9.2s 0 transport_latency_assumed last_trade_price g 50,547 39 95ms 381ms 5.1s 23.5s 0 transport_latency_assumed last_trade_price h 50,827 8,926 24ms 85ms 436ms 9.1s 0 transport_latency_assumed market_resolved c 858 806 6ms 5.7min 9.3min 10.3min 0 transport_latency_assumed market_resolved e 788 21 42ms 162ms 41.3s 41.4s 0 transport_latency_assumed market_resolved f 788 3 49ms 140ms 41.3s 41.4s 0 transport_latency_assumed market_resolved g 788 not meas. 85ms 265ms 54.5s 54.6s 0 transport_latency_assumed market_resolved h 788 115 18ms 62ms 41.7s 41.7s 0 transport_latency_assumed new_market c 1,307 792 126ms 6.4min 6.9min 7.3min 0 transport_latency_assumed new_market e 1,002 189 192ms 18.9s 31.7s 2.0min 0 transport_latency_assumed new_market f 1,002 161 190ms 14.4s 29.5s 1.0min 0 transport_latency_assumed new_market g 1,002 96 307ms 13.0s 24.9s 1.3min 0 transport_latency_assumed new_market h 1,002 369 137ms 14.4s 28.5s 55.9s 0 transport_latency_assumed price_change c 79,529,448 75,366,750 5ms 14ms 124ms 4.4s 0 transport_latency_assumed price_change e 93,978,360 572,882 41ms 53ms 308ms 11.4s 0 transport_latency_assumed price_change f 93,991,366 233,204 48ms 62ms 317ms 9.3s 0 transport_latency_assumed price_change g 93,909,542 22,206 81ms 111ms 743ms 23.7s 0 transport_latency_assumed price_change h 93,974,836 17,852,374 18ms 27ms 178ms 15.5s 0 transport_latency_assumed tick_size_change c 1,756 1,729 5ms 9ms 46ms 259ms 0 transport_latency_assumed tick_size_change e 1,992 8 40ms 44ms 112ms 197ms 0 transport_latency_assumed tick_size_change f 1,992 not meas. 47ms 59ms 263ms 368ms 0 transport_latency_assumed tick_size_change g 1,992 not meas. 80ms 93ms 297ms 381ms 0 transport_latency_assumed tick_size_change h 1,992 255 18ms 22ms 80ms 100ms 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/10/2026-09-14T10.parquet sha256sum 2026-09-14T10.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.