Hour audit: 2026-09-07T03
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-07T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-07T03:00:00.002990952+00:00 · last event 2026-09-07T03:59:59.999988308+00:00
VOLUME 103,892,805 rows · 1,019,503,871 bytes (972.27 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 103,779,732 · f: 103,768,808 · g: 103,736,498 · e: 103,683,389 · h: 103,633,206 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 99,977,994 (96.23%) · f: 137,310 (0.13%) · g: 28,582 (0.03%) · e: 416,559 (0.40%) · h: 3,332,360 (3.21%) (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 103,892,805 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ffef1df23d2321c50eac88fc091f36adc433caaea13f7ea36a4ca08bbbeeb9d5
the corpus checksum ledger names this file with the same digest
joined 103,898,089 to merged 103,892,805, minus 5,284 (minus 0.0051%)
boundary drops 5,284 · 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-07T04:58:06Z 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 11,292,187 121,247,996 0-43 b965349b29c0b6641bbc99589795e744c125e8e361060f63f9241fc5010dfc3c book 151,357 14,968,934 44-44 86e839cf16a7ac01f028b6654159793808474cb0db9a87239021932267334257 last_trade_price 56,661 3,130,416 45-45 c1c64529b62c10e032e9222c7ac3e78fcfb428a496fbab0fb82731eef56b408e market_resolved 1,659 270,174 46-46 3c41c3fe777287452394310d81af9fd81e195845c8299af7f6be653c1a60547a new_market 2,023 202,225 47-47 45d8580eba1eb59573c2b2f3049494ad1d94dd13d04c858acf45f6d0b1914d67 price_change 92,386,566 878,412,141 48-400 5286680089839313b5e9570438f5aadd698ce891cdb78c84b0d5d0231810ade1 tick_size_change 2,352 86,581 401-401 51f4f3a7cb32708b0b00e21934b1830066ae2761c72378824a9bb184ded5a46c EVENT MIX count share price_change 92,386,566 88.92% best_bid_ask 11,292,187 10.87% book 151,357 0.15% last_trade_price 56,661 0.05% tick_size_change 2,352 <0.01% new_market 2,023 <0.01% market_resolved 1,659 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,292,663 11,292,187 476 432 FULL book 151,361 151,357 4 13,853 FULL last_trade_price 56,663 56,661 2 0 FULL market_resolved 1,659 1,659 0 0 FULL new_market 2,023 2,023 0 0 FULL price_change 92,391,368 92,386,566 4,802 791 FULL tick_size_change 2,352 2,352 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,290,707 10,893,609 4ms 9ms 105ms 3.6s 0 transport_latency_assumed best_bid_ask e 11,289,392 35,068 39ms 45ms 170ms 4.9s 0 transport_latency_assumed best_bid_ask f 11,288,975 14,425 49ms 56ms 188ms 3.9s 0 transport_latency_assumed best_bid_ask g 11,288,613 2,261 81ms 99ms 373ms 11.1s 0 transport_latency_assumed best_bid_ask h 11,289,864 346,824 18ms 24ms 177ms 40.2s 0 transport_latency_assumed book c 122,030 114,688 6ms 34ms 1.1h 81.7d 0 book_staleness book e 128,758 11,294 41ms 466ms 13.6h 81.7d 0 book_staleness book f 125,454 7,300 52ms 241ms 8.3h 100.2d 0 book_staleness book g 128,802 10,631 90ms 1.1s 14.6h 82.1d 0 book_staleness book h 120,041 7,444 21ms 59ms 6.8s 35.6d 0 book_staleness last_trade_price c 56,630 53,921 9ms 41ms 226ms 5.0s 0 transport_latency_assumed last_trade_price e 56,627 313 45ms 106ms 891ms 5.0s 0 transport_latency_assumed last_trade_price f 56,585 96 55ms 120ms 811ms 5.0s 0 transport_latency_assumed last_trade_price g 56,570 49 94ms 189ms 2.9s 11.1s 0 transport_latency_assumed last_trade_price h 56,517 2,282 23ms 62ms 360ms 9.5s 0 transport_latency_assumed market_resolved c 1,639 1,588 4ms 10ms 149ms 414ms 0 transport_latency_assumed market_resolved e 1,639 23 41ms 123ms 44.3s 1.0min 0 transport_latency_assumed market_resolved f 1,639 not meas. 51ms 134ms 442ms 674ms 0 transport_latency_assumed market_resolved g 1,639 not meas. 87ms 249ms 734ms 10.3s 0 transport_latency_assumed market_resolved h 1,639 48 18ms 60ms 524ms 1.0min 0 transport_latency_assumed new_market c 1,306 751 97ms 18.8s 27.3s 6.3h 0 transport_latency_assumed new_market e 1,306 330 170ms 20.5s 31.4s 43.9min 0 transport_latency_assumed new_market f 1,306 170 187ms 19.4s 25.7s 2.6h 0 transport_latency_assumed new_market g 1,306 208 271ms 19.0s 26.9s 4.6h 0 transport_latency_assumed new_market h 1,306 564 125ms 18.3s 25.6s 8.5min 0 transport_latency_assumed price_change c 92,305,068 88,911,121 5ms 10ms 112ms 4.4s 0 transport_latency_assumed price_change e 92,203,315 369,527 40ms 48ms 213ms 4.9s 0 transport_latency_assumed price_change f 92,292,497 115,319 49ms 60ms 225ms 4.0s 0 transport_latency_assumed price_change g 92,257,216 15,433 82ms 102ms 461ms 12.2s 0 transport_latency_assumed price_change h 92,161,487 2,975,166 18ms 27ms 183ms 41.2s 0 transport_latency_assumed tick_size_change c 2,352 2,316 4ms 7ms 27ms 263ms 0 transport_latency_assumed tick_size_change e 2,352 4 39ms 43ms 75ms 133ms 0 transport_latency_assumed tick_size_change f 2,352 not meas. 49ms 53ms 175ms 304ms 0 transport_latency_assumed tick_size_change g 2,352 not meas. 80ms 94ms 149ms 280ms 0 transport_latency_assumed tick_size_change h 2,352 32 18ms 20ms 60ms 3.3s 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-07/03/2026-09-07T03.parquet sha256sum 2026-09-07T03.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.