Hour audit: 2026-09-17T22
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-17T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T22:00:00.000064269+00:00 · last event 2026-09-17T22:59:59.999900758+00:00
VOLUME 108,396,569 rows · 1,124,791,544 bytes (1.05 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 107,812,780 · f: 107,662,478 · h: 107,482,339 · g: 107,439,362 · c: 103,339,458 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 485,396 (0.45%) · f: 207,872 (0.19%) · h: 9,323,326 (8.60%) · g: 40,196 (0.04%) · c: 98,339,779 (90.72%) (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 108,396,569 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 6c33fefb4f7962b2ad2cb32948eaf266747d98d9b4c6246506751d5c5c3724db
the corpus checksum ledger names this file with the same digest
joined 108,398,820 to merged 108,396,569, minus 2,251 (minus 0.0021%)
boundary drops 2,251 · 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-18T00:03:10Z 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,011,076 123,441,846 0-42 0231dde21a93656d3bfc4385e92d023b23e9f759f9b68778c2d0a9f4958a2861 book 563,449 56,883,047 43-45 958a0dadaec40e60b2db6037d97e6e5762f5aefd385f961e7641399df1b97028 last_trade_price 47,224 2,676,347 46-46 e786724b4c09f109a452db85c7849d06016994ba10f6e36bef5bd9caefa1cd9a market_resolved 1,820 280,712 47-47 a7cd552d568cfa7f1c1d5e02bc54aabd255943fc2fbb76e3d807582955db3927 new_market 1,662 173,125 48-48 8e9e3b9b8ffcbd8b83d5a74380e470b1220c9beda20ce4560585bfb7ac897f7f price_change 96,768,394 939,990,297 49-418 c656f070a14e0e23a66029c9d449102418e1a80e50eb7e5ea62ed52fdfcc8063 tick_size_change 2,944 107,779 419-419 4d280f812ca7c22751cb25923772ab501fbfa76dac369246699575e26a226a35 EVENT MIX count share price_change 96,768,394 89.27% best_bid_ask 11,011,076 10.16% book 563,449 0.52% last_trade_price 47,224 0.04% tick_size_change 2,944 <0.01% market_resolved 1,820 <0.01% new_market 1,662 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,011,302 11,011,076 226 1,001 FULL book 563,491 563,449 42 187,436 FULL last_trade_price 47,225 47,224 1 128 FULL market_resolved 1,820 1,820 0 6 FULL new_market 1,662 1,662 0 0 FULL price_change 96,770,376 96,768,394 1,982 741 FULL tick_size_change 2,944 2,944 0 36 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,499,656 10,028,113 5ms 11ms 111ms 5.8s 0 transport_latency_assumed best_bid_ask e 11,007,370 41,367 39ms 48ms 188ms 12.2s 0 transport_latency_assumed best_bid_ask f 10,990,494 16,218 48ms 56ms 214ms 7.3s 0 transport_latency_assumed best_bid_ask g 10,986,868 2,072 80ms 100ms 381ms 16.3s 0 transport_latency_assumed best_bid_ask h 10,994,558 923,306 18ms 25ms 145ms 41.6s 0 transport_latency_assumed book c 515,413 487,190 2.4min 3.8h 36.1d 111.0d 0 book_staleness book e 134,500 33,381 52ms 8.2min 10.5d 92.5d 0 book_staleness book f 112,773 13,126 51ms 22.0s 6.2d 92.5d 0 book_staleness book g 111,906 11,748 96ms 28.9s 6.2d 111.0d 0 book_staleness book h 106,466 18,004 22ms 989ms 6.1h 92.5d 0 book_staleness last_trade_price c 45,051 42,160 10ms 53ms 264ms 5.0s 0 transport_latency_assumed last_trade_price e 46,940 425 51ms 294ms 5.7s 12.2s 0 transport_latency_assumed last_trade_price f 47,055 269 60ms 425ms 5.5s 7.3s 0 transport_latency_assumed last_trade_price g 46,627 94 100ms 555ms 10.0s 16.4s 0 transport_latency_assumed last_trade_price h 46,014 4,276 24ms 100ms 709ms 10.1s 0 transport_latency_assumed market_resolved c 1,734 1,688 5ms 23ms 4.2min 5.3min 0 transport_latency_assumed market_resolved e 1,734 10 66ms 188ms 401ms 930ms 0 transport_latency_assumed market_resolved f 1,730 1 93ms 200ms 436ms 763ms 0 transport_latency_assumed market_resolved g 1,733 2 125ms 324ms 746ms 1.9min 0 transport_latency_assumed market_resolved h 1,733 119 34ms 68ms 195ms 4.8s 0 transport_latency_assumed new_market c 1,112 634 81ms 16.7s 53.6s 4.2min 0 transport_latency_assumed new_market e 1,112 247 163ms 18.6s 51.6s 1.7min 0 transport_latency_assumed new_market f 1,112 218 157ms 17.4s 48.1s 1.3min 0 transport_latency_assumed new_market g 1,112 100 297ms 19.0s 46.8s 1.3min 0 transport_latency_assumed new_market h 1,112 463 118ms 21.3s 52.1s 1.2min 0 transport_latency_assumed price_change c 92,273,672 87,777,258 5ms 13ms 135ms 8.0s 0 transport_latency_assumed price_change e 96,618,180 409,958 39ms 56ms 499ms 12.2s 0 transport_latency_assumed price_change f 96,506,374 178,032 48ms 65ms 556ms 7.9s 0 transport_latency_assumed price_change g 96,288,184 26,180 81ms 110ms 997ms 16.4s 0 transport_latency_assumed price_change h 96,329,516 8,376,966 18ms 29ms 234ms 41.6s 0 transport_latency_assumed tick_size_change c 2,820 2,736 5ms 8ms 77ms 366ms 0 transport_latency_assumed tick_size_change e 2,944 8 39ms 48ms 113ms 657ms 0 transport_latency_assumed tick_size_change f 2,940 8 48ms 54ms 121ms 174ms 0 transport_latency_assumed tick_size_change g 2,932 not meas. 80ms 96ms 166ms 1.1s 0 transport_latency_assumed tick_size_change h 2,940 192 18ms 28ms 79ms 206ms 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-17/22/2026-09-17T22.parquet sha256sum 2026-09-17T22.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.