Hour audit: 2026-09-09T15
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-09T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T15:00:00.000065479+00:00 · last event 2026-09-09T15:59:59.999989416+00:00
VOLUME 125,346,805 rows · 1,385,013,709 bytes (1.29 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 122,556,180 · h: 122,502,563 · e: 118,617,753 · f: 118,149,833 · c: 93,811,288 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 181,366 (0.14%) · h: 34,628,369 (27.63%) · e: 2,306,013 (1.84%) · f: 975,994 (0.78%) · c: 87,255,063 (69.61%) (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,346,805 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 34bcb163b0183ff463b70bd2f2eb9ae912d85be6211035d07c9eb3ba4a9ea5a4
the corpus checksum ledger names this file with the same digest
joined 125,367,824 to merged 125,346,805, minus 21,019 (minus 0.0168%)
boundary drops 21,019 · 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-09T17:36:40Z 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,406,350 131,786,652 0-43 5a964e42c1df77cb40fad966c323f4df33d06bae93f9e8f91e6de91ab43f089f book 2,959,707 122,717,036 44-55 7c30fe46b56a20405c1ff1b9e74c0bda3f44ef6b269aaa2bd50d03ec3a8796c0 last_trade_price 84,218 4,765,313 56-56 3d862b5eaac22e5d66e89f9976c1a7ed5b53036347bc14c8bfce1ddb7c5b12fa market_resolved 1,789 166,965 57-57 b077b5f660a20a9c906f0339fb67ab420013379407a32eed4d2e15a9aaf7771c new_market 4,215 400,168 58-58 7f51515912193037e3033e4f55a81ff22bd7122c264dded8901d29f213233602 price_change 110,887,390 1,123,633,839 59-482 e6100c1e0651e0352b942a6c06cdfd1bff4a8612cc251b822f0fcc0ba850d4f0 tick_size_change 3,136 115,906 483-483 b5eab99079c788a9bb359be9681e9daeb74724e3403837409b95eb4bfe86517a EVENT MIX count share price_change 110,887,390 88.46% best_bid_ask 11,406,350 9.10% book 2,959,707 2.36% last_trade_price 84,218 0.07% new_market 4,215 <0.01% tick_size_change 3,136 <0.01% market_resolved 1,789 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,406,596 11,406,350 246 4,732 FULL book 2,977,433 2,959,707 17,726 151,507 FULL last_trade_price 84,219 84,218 1 771 FULL market_resolved 1,817 1,789 28 112 FULL new_market 4,215 4,215 0 149 FULL price_change 110,890,408 110,887,390 3,018 3,902 FULL tick_size_change 3,136 3,136 0 251 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,585,963 7,998,094 5ms 18ms 192ms 5.8s 0 transport_latency_assumed best_bid_ask e 10,987,412 187,000 41ms 63ms 342ms 27.3s 0 transport_latency_assumed best_bid_ask f 10,951,498 68,659 46ms 70ms 334ms 14.3s 0 transport_latency_assumed best_bid_ask g 11,393,755 4,753 86ms 137ms 717ms 24.4s 0 transport_latency_assumed best_bid_ask h 11,403,070 3,147,844 17ms 35ms 356ms 50.6s 0 transport_latency_assumed book c 2,476,413 2,315,575 22.1min 21.3h 31.9d 102.7d 0 book_staleness book e 809,288 233,334 6.1min 14.9h 28.8d 102.7d 0 book_staleness book f 771,371 196,497 5.4min 14.7h 28.0d 102.7d 0 book_staleness book g 550,032 120,744 1.9min 12.6h 24.5d 102.7d 0 book_staleness book h 287,140 93,557 44ms 4.2h 14.9d 102.7d 0 book_staleness last_trade_price c 61,093 56,281 11ms 50ms 306ms 5.2s 0 transport_latency_assumed last_trade_price e 81,312 1,527 50ms 350ms 5.4s 27.3s 0 transport_latency_assumed last_trade_price f 79,750 585 55ms 291ms 5.8s 14.3s 0 transport_latency_assumed last_trade_price g 82,719 104 100ms 829ms 10.8s 24.7s 0 transport_latency_assumed last_trade_price h 84,104 25,721 23ms 73ms 544ms 40.3s 0 transport_latency_assumed market_resolved c 1,531 1,464 4.0min 18.0min 24.1min 24.7min 0 transport_latency_assumed market_resolved e 941 59 42ms 319ms 5.2min 5.2min 0 transport_latency_assumed market_resolved f 897 8 47ms 196ms 794ms 2.5min 0 transport_latency_assumed market_resolved g 924 3 87ms 354ms 1.1s 1.7min 0 transport_latency_assumed market_resolved h 924 255 18ms 79ms 2.4s 59.6s 0 transport_latency_assumed new_market c 2,792 1,547 135ms 7.3min 14.3min 53.7d 0 transport_latency_assumed new_market e 2,518 488 198ms 58.5s 3.4min 3.7min 0 transport_latency_assumed new_market f 2,504 540 216ms 1.3min 3.5min 53.7d 0 transport_latency_assumed new_market g 2,508 470 337ms 1.2min 3.5min 3.6min 0 transport_latency_assumed new_market h 2,510 1,170 130ms 2.0min 3.5min 53.7d 0 transport_latency_assumed price_change c 82,681,172 76,879,893 6ms 20ms 209ms 5.8s 0 transport_latency_assumed price_change e 106,733,258 1,883,493 42ms 79ms 679ms 27.3s 0 transport_latency_assumed price_change f 106,340,757 709,676 47ms 86ms 594ms 14.3s 0 transport_latency_assumed price_change g 110,523,106 55,292 87ms 178ms 2.1s 24.7s 0 transport_latency_assumed price_change h 110,721,679 31,359,036 17ms 39ms 375ms 50.6s 0 transport_latency_assumed tick_size_change c 2,324 2,209 5ms 12ms 303ms 342ms 0 transport_latency_assumed tick_size_change e 3,024 112 41ms 63ms 224ms 1.1s 0 transport_latency_assumed tick_size_change f 3,056 29 46ms 81ms 298ms 1.4s 0 transport_latency_assumed tick_size_change g 3,136 not meas. 85ms 150ms 511ms 2.9s 0 transport_latency_assumed tick_size_change h 3,136 786 17ms 37ms 278ms 39.5s 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-09/15/2026-09-09T15.parquet sha256sum 2026-09-09T15.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.