Hour audit: 2026-09-23T01
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-23T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T01:00:00.000100782+00:00 · last event 2026-09-23T01:59:59.999991207+00:00
VOLUME 125,048,893 rows · 1,353,040,781 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured h: 122,232,296 · i: 121,090,172 · f: 117,720,459 · c: 99,115,854 · k: 98,150,660 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 10,915,400 (8.73%) · i: 4,964,844 (3.97%) · f: 252,210 (0.20%) · c: 91,174,514 (72.91%) · k: 17,741,925 (14.19%) (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 125,048,893 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 65f3323126d90191334c01ed1ab1be84d60c174f91d4c831dc78bffb342f6f5e
the corpus checksum ledger names this file with the same digest
joined 125,050,369 to merged 125,048,893, minus 1,476 (minus 0.0012%)
boundary drops 1,476 · 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-23T03:37:59Z as cfhik
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,935,449 145,758,408 0-49 1de5c210ef3eb1a23d3b6f508aa2d846e29968266ea1523186efd278c140f217 book 2,772,217 106,032,313 50-60 b16797456d78d21caee9715508d4d2c592c3cae0d0d997cd81eab31128c17275 last_trade_price 53,934 3,050,332 61-61 e3428432c6e682cdafc0cc93cb37f681222fe2441066f94b8e0b30ddb5fce6d4 market_resolved 3,406 319,848 62-62 0a8f41fbd5480d4f3371e1339f00d1432a275776c7901295d96a4a72b950e875 new_market 583 52,218 63-63 1d9ff2a229ea9c8ae9e25b9fc4ab366c426f0fbd4595fe98b2701f35db67344d price_change 109,273,984 1,096,071,280 64-480 dc3df85b7c4a1276988cf2a8e73f350c6f1c1d9dcb6b1df75649c09d81579b67 tick_size_change 9,320 334,140 481-481 03bb1d7792217f54a77e294ffd4eaaee9a7354db8225ec17a5e78aa48c1e5dcf EVENT MIX count share price_change 109,273,984 87.39% best_bid_ask 12,935,449 10.34% book 2,772,217 2.22% last_trade_price 53,934 0.04% tick_size_change 9,320 <0.01% market_resolved 3,406 <0.01% new_market 583 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,935,607 12,935,449 158 5,814 FULL book 2,772,481 2,772,217 264 191,760 FULL last_trade_price 53,934 53,934 0 512 FULL market_resolved 3,406 3,406 0 168 FULL new_market 583 583 0 9 FULL price_change 109,275,038 109,273,984 1,054 3,500 FULL tick_size_change 9,320 9,320 0 1,111 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,188,648 9,472,164 4ms 12ms 79ms 1.8s 0 transport_latency_assumed best_bid_ask f 12,416,259 8,182 49ms 58ms 142ms 2.2s 0 transport_latency_assumed best_bid_ask h 12,929,051 1,143,586 18ms 33ms 97ms 21.1s 0 transport_latency_assumed best_bid_ask i 12,768,409 510,590 20ms 27ms 87ms 4.0s 0 transport_latency_assumed best_bid_ask k 10,224,483 1,800,927 13ms 19ms 73ms 877ms 0 transport_latency_assumed book c 2,128,543 1,742,180 13.8min 3.5d 42.3d 116.1d 0 book_staleness book f 530,341 139,787 6.7min 2.3d 38.3d 116.1d 0 book_staleness book h 160,692 32,365 29ms 34.8min 17.5d 116.1d 0 book_staleness book i 176,055 27,096 39ms 5.1h 25.5d 116.1d 0 book_staleness book k 2,057,432 830,789 13.6min 3.5d 42.3d 116.1d 0 book_staleness last_trade_price c 43,282 38,920 6ms 23ms 165ms 1.2s 0 transport_latency_assumed last_trade_price f 51,015 103 50ms 95ms 438ms 2.3s 0 transport_latency_assumed last_trade_price h 53,261 4,610 19ms 54ms 253ms 3.8s 0 transport_latency_assumed last_trade_price i 53,468 2,745 22ms 56ms 318ms 2.7s 0 transport_latency_assumed last_trade_price k 41,609 7,556 14ms 31ms 162ms 1.2s 0 transport_latency_assumed market_resolved c 2,810 2,280 30.1s 13.8min 22.5min 26.2min 0 transport_latency_assumed market_resolved f 1,893 112 49ms 349ms 4.7min 5.9min 0 transport_latency_assumed market_resolved h 1,879 133 18ms 29.3s 1.0min 1.0min 0 transport_latency_assumed market_resolved i 1,871 243 21ms 29.8s 58.8s 2.4min 0 transport_latency_assumed market_resolved k 1,893 638 14ms 5.1min 11.1min 15.0min 0 transport_latency_assumed new_market c 499 291 141ms 11.8min 16.3min 16.4min 0 transport_latency_assumed new_market f 313 18 77ms 532ms 58.2s 1.7min 0 transport_latency_assumed new_market h 313 51 55ms 248ms 15.4s 2.0min 0 transport_latency_assumed new_market i 313 29 61ms 294ms 11.3s 1.4min 0 transport_latency_assumed new_market k 349 194 40ms 5.3min 10.4min 55.9min 0 transport_latency_assumed price_change c 86,744,624 79,911,400 5ms 15ms 92ms 3.4s 0 transport_latency_assumed price_change f 104,711,566 104,008 49ms 63ms 181ms 2.5s 0 transport_latency_assumed price_change h 109,077,780 9,733,864 18ms 37ms 122ms 21.2s 0 transport_latency_assumed price_change i 108,080,784 4,423,883 21ms 31ms 120ms 4.0s 0 transport_latency_assumed price_change k 85,819,054 15,100,829 13ms 22ms 87ms 1.0s 0 transport_latency_assumed tick_size_change c 7,448 7,279 4ms 7ms 19ms 79ms 0 transport_latency_assumed tick_size_change f 9,072 not meas. 48ms 52ms 94ms 835ms 0 transport_latency_assumed tick_size_change h 9,320 791 18ms 32ms 74ms 236ms 0 transport_latency_assumed tick_size_change i 9,272 258 21ms 32ms 98ms 132ms 0 transport_latency_assumed tick_size_change k 5,840 992 12ms 15ms 27ms 64ms 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-23/01/2026-09-23T01.parquet sha256sum 2026-09-23T01.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.