Hour audit: 2026-09-10T09
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-10T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-10T09:00:00.000006033+00:00 · last event 2026-09-10T09:59:59.999957584+00:00
VOLUME 106,633,567 rows · 1,065,836,129 bytes (1016.46 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 106,614,437 · c: 106,609,855 · f: 106,595,065 · e: 106,594,412 · g: 106,582,339 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 4,146,944 (3.89%) · c: 101,981,199 (95.64%) · f: 132,263 (0.12%) · e: 350,072 (0.33%) · g: 23,089 (0.02%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 106,633,567 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f50c19a55937b03db3a5d6d3a6b0082ad34677d51a96cb66dd853cf5bdab8d50
the corpus checksum ledger names this file with the same digest
joined 106,635,091 to merged 106,633,567, minus 1,524 (minus 0.0014%)
boundary drops 1,524 · 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-10T11:34:51Z 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,215,783 112,152,397 0-38 f0c9873e791b11b3db9b668787df8df09d85fc7542b08ac964ff31dd3fd38343 book 127,832 13,066,661 39-39 2c5f1d9d7c9ad2930a7c1223aa71a3cdcbaa57ec3693fb92b9ad68a8864254ec last_trade_price 54,804 3,117,195 40-40 9fb7e294e8669d98c82102c493694e5eb923c0fdfd513a838ff35577fd366c3a market_resolved 632 102,325 41-41 7b7ea6653bf96f6ef544c80817c6b0af437d825423cb37182798ad4a74a98ee8 new_market 1,124 114,166 42-42 651a5492578f31b9d61a39efce2d2812d6c7fe881fe5c656a4b0e834316bae56 price_change 96,230,780 935,971,829 43-410 b5069b3212c2dde5f0363b1a2c92c60d72e18b77273761b6a4f431cf8f4c2702 tick_size_change 2,612 96,016 411-411 652c60dc802cd17fb38c43d61ed3834cd7815d1e9d14229441d2341df2a2677a EVENT MIX count share price_change 96,230,780 90.24% best_bid_ask 10,215,783 9.58% book 127,832 0.12% last_trade_price 54,804 0.05% tick_size_change 2,612 <0.01% new_market 1,124 <0.01% market_resolved 632 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,215,969 10,215,783 186 131 FULL book 127,832 127,832 0 5,547 FULL last_trade_price 54,806 54,804 2 0 FULL market_resolved 632 632 0 0 FULL new_market 1,124 1,124 0 0 FULL price_change 96,232,116 96,230,780 1,336 53 FULL tick_size_change 2,612 2,612 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,215,217 9,789,115 5ms 11ms 97ms 4.9s 0 transport_latency_assumed best_bid_ask e 10,214,216 31,091 39ms 44ms 139ms 4.0s 0 transport_latency_assumed best_bid_ask f 10,214,081 11,764 45ms 53ms 159ms 5.5s 0 transport_latency_assumed best_bid_ask g 10,213,588 1,183 77ms 98ms 286ms 9.4s 0 transport_latency_assumed best_bid_ask h 10,215,062 382,630 18ms 23ms 112ms 7.2s 0 transport_latency_assumed book c 115,775 109,012 7ms 29ms 3.0s 84.8d 0 book_staleness book e 115,703 2,359 41ms 151ms 3.4s 84.9d 0 book_staleness book f 115,907 2,026 48ms 172ms 5.4s 46.4d 0 book_staleness book g 123,445 8,852 84ms 483ms 19.4h 85.0d 0 book_staleness book h 115,181 5,583 21ms 80ms 1.4s 84.8d 0 book_staleness last_trade_price c 54,701 51,811 11ms 48ms 244ms 5.0s 0 transport_latency_assumed last_trade_price e 54,681 366 47ms 146ms 1.7s 5.0s 0 transport_latency_assumed last_trade_price f 54,665 168 54ms 163ms 1.7s 5.6s 0 transport_latency_assumed last_trade_price g 54,656 23 92ms 226ms 1.1s 5.1s 0 transport_latency_assumed last_trade_price h 54,764 2,436 24ms 93ms 513ms 6.2s 0 transport_latency_assumed market_resolved c 626 594 5ms 15ms 114ms 473ms 0 transport_latency_assumed market_resolved e 626 10 39ms 184ms 718ms 1.0min 0 transport_latency_assumed market_resolved f 626 1 47ms 189ms 1.0s 1.0min 0 transport_latency_assumed market_resolved g 626 not meas. 84ms 345ms 765ms 1.2s 0 transport_latency_assumed market_resolved h 626 27 18ms 68ms 1.1s 1.0min 0 transport_latency_assumed new_market c 732 425 75ms 22.0s 55.6s 1.1min 0 transport_latency_assumed new_market e 732 198 153ms 27.2s 55.5s 1.1min 0 transport_latency_assumed new_market f 732 174 153ms 22.9s 53.4s 1.3min 0 transport_latency_assumed new_market g 732 105 257ms 19.3s 59.3s 1.1min 0 transport_latency_assumed new_market h 732 222 94ms 20.6s 56.2s 1.1min 0 transport_latency_assumed price_change c 96,220,192 92,027,774 5ms 12ms 104ms 5.8s 0 transport_latency_assumed price_change e 96,205,842 316,048 39ms 47ms 187ms 4.2s 0 transport_latency_assumed price_change f 96,206,442 118,130 46ms 56ms 212ms 6.2s 0 transport_latency_assumed price_change g 96,186,680 12,926 77ms 107ms 352ms 9.4s 0 transport_latency_assumed price_change h 96,225,460 3,755,902 18ms 25ms 137ms 7.2s 0 transport_latency_assumed tick_size_change c 2,612 2,468 5ms 11ms 88ms 260ms 0 transport_latency_assumed tick_size_change e 2,612 not meas. 39ms 53ms 125ms 203ms 0 transport_latency_assumed tick_size_change f 2,612 not meas. 45ms 51ms 103ms 258ms 0 transport_latency_assumed tick_size_change g 2,612 not meas. 77ms 90ms 169ms 235ms 0 transport_latency_assumed tick_size_change h 2,612 144 18ms 31ms 67ms 223ms 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-10/09/2026-09-10T09.parquet sha256sum 2026-09-10T09.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.