Hour audit: 2026-09-23T09
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-23T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-23T09:00:00.000039332+00:00 · last event 2026-09-23T09:59:59.998114588+00:00
VOLUME 117,937,560 rows · 1,252,153,376 bytes (1.17 GiB) · 7 products, all holding rows
WITNESSES cfhik — 5 machines contributed rows
captured c: 117,469,988 · k: 117,422,231 · i: 117,414,506 · h: 117,025,212 · f: 112,875,148 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 107,664,330 (91.29%) · k: 6,946,544 (5.89%) · i: 988,921 (0.84%) · h: 1,895,991 (1.61%) · f: 441,774 (0.37%) (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 117,937,560 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 a9bc5c5331dbfc1661486004c0b36b5356810d5fd0bc2a80886c3ae22ee3e261
the corpus checksum ledger names this file with the same digest
joined 117,939,672 to merged 117,937,560, minus 2,112 (minus 0.0018%)
boundary drops 2,112 · 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-23T12:08:15Z 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 10,701,300 126,224,354 0-40 0015f50316d8c38e66c0a16c0a7477b41c839baf65a78a1ebeb25a4d5725231b book 540,469 52,809,202 41-43 8574e327917de3514d6e4e07d6e39e27dc143e6ecec1ce151407d18293322a7d last_trade_price 53,580 2,997,137 44-44 8bc7f22c5be1f8aefee2f5a12a2b72efef8be556fc6b3ae38de68b0d90549852 market_resolved 758 106,913 45-45 11e81a3d599d32b672aa29b7e880ce2f9491dd96b73ef9e15932f141951f7819 new_market 365 43,928 46-46 e3e2c7184966dead7792bd28eb144178c951a007a3e15648133f5d270ef1237e price_change 106,637,900 1,068,511,462 47-453 366130009afad4028e3c047cd5d965b60e3c0d8346c0318c539e5f1099d9e9db tick_size_change 3,188 116,921 454-454 066ffb9763a8d24db9cecf074b13cfaa9b6c82f3e6645277856fddbd4092a67a EVENT MIX count share price_change 106,637,900 90.42% best_bid_ask 10,701,300 9.07% book 540,469 0.46% last_trade_price 53,580 0.05% tick_size_change 3,188 <0.01% market_resolved 758 <0.01% new_market 365 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,701,418 10,701,300 118 352 FULL book 541,319 540,469 850 191,094 FULL last_trade_price 53,580 53,580 0 49 FULL market_resolved 758 758 0 5 FULL new_market 365 365 0 0 FULL price_change 106,639,044 106,637,900 1,144 136 FULL tick_size_change 3,188 3,188 0 13 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,700,262 9,897,141 5ms 13ms 82ms 1.1s 0 transport_latency_assumed best_bid_ask f 10,293,343 2,017 50ms 63ms 169ms 6.2s 0 transport_latency_assumed best_bid_ask h 10,698,174 148,876 19ms 30ms 109ms 1.2min 0 transport_latency_assumed best_bid_ask i 10,700,186 81,659 21ms 30ms 109ms 3.0s 0 transport_latency_assumed best_bid_ask k 10,699,697 571,607 13ms 22ms 87ms 2.3s 0 transport_latency_assumed book c 114,658 99,507 7ms 90ms 1.6d 98.0d 0 book_staleness book f 513,686 401,633 8.1min 2.6d 38.8d 116.5d 0 book_staleness book h 114,650 9,699 23ms 273ms 3.1d 97.9d 0 book_staleness book i 111,886 3,265 24ms 325ms 14.6h 97.9d 0 book_staleness book k 127,636 26,365 16ms 5.9min 14.0d 116.5d 0 book_staleness last_trade_price c 53,277 47,381 6ms 31ms 216ms 1.1s 0 transport_latency_assumed last_trade_price f 50,661 74 52ms 198ms 3.0s 5.5s 0 transport_latency_assumed last_trade_price h 52,889 1,165 20ms 83ms 508ms 1.8s 0 transport_latency_assumed last_trade_price i 53,449 446 24ms 194ms 828ms 2.1s 0 transport_latency_assumed last_trade_price k 53,181 4,514 14ms 48ms 243ms 1.1s 0 transport_latency_assumed market_resolved c 644 614 5ms 11ms 49ms 228ms 0 transport_latency_assumed market_resolved f 653 34 51ms 53.9s 5.4min 5.4min 0 transport_latency_assumed market_resolved h 644 32 21ms 45.3s 1.0min 1.0min 0 transport_latency_assumed market_resolved i 644 55 22ms 45.7s 59.9s 1.7min 0 transport_latency_assumed market_resolved k 644 23 14ms 44ms 95ms 134ms 0 transport_latency_assumed new_market c 275 152 37ms 369ms 20.5s 1.4min 0 transport_latency_assumed new_market f 279 28 96ms 13.6s 5.4min 5.4min 0 transport_latency_assumed new_market h 275 52 56ms 10.0s 21.9s 1.4min 0 transport_latency_assumed new_market i 275 46 63ms 9.4s 31.3s 1.5min 0 transport_latency_assumed new_market k 275 87 46ms 9.7s 17.1s 1.7min 0 transport_latency_assumed price_change c 106,597,684 97,616,476 5ms 17ms 103ms 1.6s 0 transport_latency_assumed price_change f 102,013,390 37,988 50ms 73ms 317ms 8.3s 0 transport_latency_assumed price_change h 106,155,392 1,736,152 19ms 36ms 177ms 1.2min 0 transport_latency_assumed price_change i 106,544,878 903,442 21ms 38ms 242ms 3.3s 0 transport_latency_assumed price_change k 106,537,610 6,343,842 13ms 26ms 121ms 2.4s 0 transport_latency_assumed tick_size_change c 3,188 3,059 5ms 8ms 31ms 174ms 0 transport_latency_assumed tick_size_change f 3,136 not meas. 50ms 55ms 104ms 391ms 0 transport_latency_assumed tick_size_change h 3,188 15 19ms 37ms 62ms 80ms 0 transport_latency_assumed tick_size_change i 3,188 8 21ms 47ms 77ms 114ms 0 transport_latency_assumed tick_size_change k 3,188 106 13ms 19ms 44ms 272ms 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/09/2026-09-23T09.parquet sha256sum 2026-09-23T09.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.