Hour audit: 2026-09-28T18
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-28T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T18:00:00.000244227+00:00 · last event 2026-09-28T18:59:59.999998009+00:00
VOLUME 106,118,240 rows · 1,181,485,931 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured i: 105,503,682 · k: 104,610,593 · h: 104,458,112 · g: 103,368,023 · c: 101,306,543 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,647,805 (1.55%) · k: 11,364,149 (10.71%) · h: 2,980,062 (2.81%) · g: 110,757 (0.10%) · c: 90,015,467 (84.83%) (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 106,118,240 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 cdbc2519d055232277ead3383361e466fdc62a89dc34545e683c362bf8240b73
the corpus checksum ledger names this file with the same digest
joined 106,122,929 to merged 106,118,240, minus 4,689 (minus 0.0044%)
boundary drops 4,689 · 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-28T21:07:32Z as cghik
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,403,405 122,227,467 0-39 33c416d58928d4b676e943d710bd35e597347cd9d45a64973cfe8e6efaa9b49c book 861,647 67,544,909 40-43 fba4b39945a6c56840e86c07ecf099d5f4bb804e4249e05acd1614f20332ffca last_trade_price 56,834 3,260,154 44-44 a18c65e8ea36b1a0d8a3b2ad8e0390522a2183c1045c9ff7cfd68ec9b9e3e733 market_resolved 739 112,214 45-45 3469199733bb25eed6c2a5b8f3c10a1c4f22f30d75c252fbd7d84d34118e1826 new_market 1,421 174,945 46-46 dd288d6587eb9d98972cb99a7b8055af70bddce6f5f90a0121ffbbd4f6e27c14 price_change 94,791,470 986,854,470 47-408 ef5893aa6f933896888843317de9d15f158be756a4d35a29bc35c79509beb6a0 tick_size_change 2,724 101,508 409-409 105109102f33b481fe46c8fd539e9836818ac0b4ecd6f0f957103f69a2d24677 EVENT MIX count share price_change 94,791,470 89.33% best_bid_ask 10,403,405 9.80% book 861,647 0.81% last_trade_price 56,834 0.05% tick_size_change 2,724 <0.01% new_market 1,421 <0.01% market_resolved 739 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,403,628 10,403,405 223 1,943 FULL book 863,537 861,647 1,890 202,036 FULL last_trade_price 56,836 56,834 2 211 FULL market_resolved 739 739 0 70 FULL new_market 1,421 1,421 0 0 FULL price_change 94,794,044 94,791,470 2,574 3,205 FULL tick_size_change 2,724 2,724 0 60 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,940,364 8,913,809 6ms 18ms 143ms 6.2s 0 transport_latency_assumed best_bid_ask g 10,229,992 1,056 80ms 118ms 582ms 28.5s 0 transport_latency_assumed best_bid_ask h 10,290,530 257,351 19ms 29ms 163ms 11.6s 0 transport_latency_assumed best_bid_ask i 10,400,095 143,618 20ms 32ms 153ms 5.4s 0 transport_latency_assumed best_bid_ask k 10,284,837 1,087,571 14ms 25ms 168ms 45.9s 0 transport_latency_assumed book c 617,513 447,039 47.5min 1.6d 37.2d 121.9d 0 book_staleness book g 299,976 92,567 2.2min 1.4d 37.2d 121.9d 0 book_staleness book h 305,567 98,504 1.8min 1.4d 37.2d 121.9d 0 book_staleness book i 341,822 135,306 3.6min 1.5d 37.2d 121.9d 0 book_staleness book k 268,720 88,231 38.2s 1.1d 37.2d 121.9d 0 book_staleness last_trade_price c 53,653 47,495 7ms 29ms 244ms 1.9s 0 transport_latency_assumed last_trade_price g 53,277 6 96ms 1.9s 12.1s 28.4s 0 transport_latency_assumed last_trade_price h 56,388 1,959 21ms 70ms 439ms 8.7s 0 transport_latency_assumed last_trade_price i 56,534 675 22ms 196ms 1.1s 2.1s 0 transport_latency_assumed last_trade_price k 56,382 6,699 16ms 58ms 565ms 43.9s 0 transport_latency_assumed market_resolved c 676 587 7ms 43.5s 11.1min 11.1min 0 transport_latency_assumed market_resolved g 673 2 83ms 382ms 44.5s 1.7min 0 transport_latency_assumed market_resolved h 678 25 20ms 91ms 52.0s 1.8min 0 transport_latency_assumed market_resolved i 680 56 22ms 118ms 39.3s 57.8s 0 transport_latency_assumed market_resolved k 671 69 15ms 66ms 49.4s 1.3min 0 transport_latency_assumed new_market c 1,149 535 89ms 7.9s 6.1min 6.1min 0 transport_latency_assumed new_market g 1,133 38 261ms 673ms 48.0s 1.7min 0 transport_latency_assumed new_market h 1,133 328 96ms 340ms 29.2s 1.4min 0 transport_latency_assumed new_market i 1,133 276 92ms 293ms 15.9s 1.4min 0 transport_latency_assumed new_market k 1,133 244 106ms 339ms 12.7s 47.5s 0 transport_latency_assumed price_change c 90,690,640 80,603,688 6ms 21ms 183ms 8.7s 0 transport_latency_assumed price_change g 92,780,276 17,088 81ms 218ms 6.1s 28.6s 0 transport_latency_assumed price_change h 93,801,112 2,621,838 19ms 37ms 266ms 33.9s 0 transport_latency_assumed price_change i 94,700,694 1,367,818 21ms 47ms 434ms 6.9s 0 transport_latency_assumed price_change k 93,996,146 10,181,038 14ms 32ms 431ms 45.9s 0 transport_latency_assumed tick_size_change c 2,548 2,314 6ms 17ms 158ms 257ms 0 transport_latency_assumed tick_size_change g 2,696 not meas. 80ms 139ms 359ms 1.1s 0 transport_latency_assumed tick_size_change h 2,704 57 19ms 32ms 202ms 10.2s 0 transport_latency_assumed tick_size_change i 2,724 56 21ms 30ms 176ms 361ms 0 transport_latency_assumed tick_size_change k 2,704 297 14ms 28ms 195ms 3.6s 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-28/18/2026-09-28T18.parquet sha256sum 2026-09-28T18.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.