Hour audit: 2026-09-09T04
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-09T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T04:00:00.000033049+00:00 · last event 2026-09-09T04:59:59.999830338+00:00
VOLUME 96,807,475 rows · 949,424,559 bytes (905.44 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 96,700,406 · f: 96,655,440 · g: 96,597,006 · h: 96,585,697 · e: 96,549,569 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 92,585,284 (95.64%) · f: 205,087 (0.21%) · g: 58,273 (0.06%) · h: 3,392,768 (3.50%) · e: 566,063 (0.58%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 96,807,475 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 cefcaa15c9aada299a7f6b0b931cdc526a4c1ffe392653def40b56a99c74fcd6
the corpus checksum ledger names this file with the same digest
joined 96,810,237 to merged 96,807,475, minus 2,762 (minus 0.0029%)
boundary drops 2,762 · 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-09T05:55:53Z 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 9,174,032 99,841,824 0-34 db84c77b3c386f5a727cf3531851111e1e738647f7bf07c5133e83ecdb77cd7e book 158,634 16,351,395 35-35 46e6243047420eba47ce902993cd105987a40a11a8f6507c94455cdb1bec5b12 last_trade_price 55,402 3,121,236 36-36 5ad185d99a66dd295afeee8b8897cbe6101b4133e456649f3039bca3cdab3155 market_resolved 2,264 369,181 37-37 988fb1ea09d3bd7b6145c6957be1f5a7ac622ed15d7e54419e04dd14522d779c new_market 2,525 257,616 38-38 c5574a62eff3a9368396c295790b0804aa9b025eb57d41dfc0b2c91f010abd63 price_change 87,411,118 828,252,534 39-372 dac6327659c2643babc496a10b964a7e2b6d5eba58805fae88c187738645ddca tick_size_change 3,500 127,394 373-373 a9a4547e80321220913db3e7aaa05788dc4db5b5f58da5861b31352e986fd1c7 EVENT MIX count share price_change 87,411,118 90.29% best_bid_ask 9,174,032 9.48% book 158,634 0.16% last_trade_price 55,402 0.06% tick_size_change 3,500 <0.01% new_market 2,525 <0.01% market_resolved 2,264 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,174,268 9,174,032 236 213 FULL book 158,643 158,634 9 19,211 FULL last_trade_price 55,411 55,402 9 1 FULL market_resolved 2,264 2,264 0 0 FULL new_market 2,525 2,525 0 0 FULL price_change 87,413,626 87,411,118 2,508 458 FULL tick_size_change 3,500 3,500 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,173,540 8,794,489 5ms 9ms 203ms 8.5s 0 transport_latency_assumed best_bid_ask e 9,172,458 53,499 38ms 46ms 230ms 7.6s 0 transport_latency_assumed best_bid_ask f 9,172,253 17,587 46ms 55ms 265ms 5.2s 0 transport_latency_assumed best_bid_ask g 9,170,356 2,679 85ms 109ms 515ms 20.2s 0 transport_latency_assumed best_bid_ask h 9,172,929 305,778 17ms 23ms 339ms 37.5s 0 transport_latency_assumed book c 126,820 118,479 7ms 1.4s 1.0d 83.8d 0 book_staleness book e 121,504 6,643 41ms 443ms 8.6h 94.5d 0 book_staleness book f 124,086 8,862 49ms 695ms 13.7h 83.7d 0 book_staleness book g 128,933 13,420 91ms 11.4s 1.2d 83.7d 0 book_staleness book h 121,164 11,230 21ms 123ms 4.7h 83.8d 0 book_staleness last_trade_price c 55,350 52,391 9ms 41ms 354ms 5.0s 0 transport_latency_assumed last_trade_price e 55,364 371 45ms 130ms 2.0s 5.0s 0 transport_latency_assumed last_trade_price f 55,327 122 52ms 129ms 1.2s 5.0s 0 transport_latency_assumed last_trade_price g 54,997 24 95ms 281ms 7.4s 20.1s 0 transport_latency_assumed last_trade_price h 55,275 2,494 22ms 59ms 526ms 9.5s 0 transport_latency_assumed market_resolved c 2,245 2,175 5ms 10ms 281ms 1.1min 0 transport_latency_assumed market_resolved e 2,245 11 55ms 156ms 650ms 1.0min 0 transport_latency_assumed market_resolved f 2,245 2 68ms 178ms 650ms 1.0min 0 transport_latency_assumed market_resolved g 2,245 2 96ms 277ms 898ms 1.8s 0 transport_latency_assumed market_resolved h 2,245 74 33ms 65ms 2.9s 1.0min 0 transport_latency_assumed new_market c 1,661 914 115ms 20.0s 43.7s 58.1s 0 transport_latency_assumed new_market e 1,661 433 167ms 20.4s 42.8s 1.1min 0 transport_latency_assumed new_market f 1,661 381 216ms 19.1s 41.9s 5.2min 0 transport_latency_assumed new_market g 1,661 162 336ms 21.4s 42.6s 1.0min 0 transport_latency_assumed new_market h 1,661 635 153ms 20.2s 40.0s 58.1s 0 transport_latency_assumed price_change c 87,337,290 83,613,500 5ms 10ms 219ms 10.3s 0 transport_latency_assumed price_change e 87,192,837 505,094 39ms 51ms 336ms 8.7s 0 transport_latency_assumed price_change f 87,296,368 178,133 46ms 61ms 359ms 5.4s 0 transport_latency_assumed price_change g 87,235,314 41,986 85ms 122ms 736ms 20.3s 0 transport_latency_assumed price_change h 87,228,923 3,072,405 18ms 26ms 350ms 39.2s 0 transport_latency_assumed tick_size_change c 3,500 3,336 5ms 8ms 112ms 280ms 0 transport_latency_assumed tick_size_change e 3,500 12 38ms 45ms 107ms 1.9s 0 transport_latency_assumed tick_size_change f 3,500 not meas. 46ms 50ms 93ms 1.6s 0 transport_latency_assumed tick_size_change g 3,500 not meas. 82ms 94ms 155ms 2.9s 0 transport_latency_assumed tick_size_change h 3,500 152 17ms 20ms 92ms 2.4s 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/04/2026-09-09T04.parquet sha256sum 2026-09-09T04.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.