Hour audit: 2026-09-28T20
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-28T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T20:00:00.000045521+00:00 · last event 2026-09-28T20:59:59.999861825+00:00
VOLUME 99,016,723 rows · 1,083,019,546 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured c: 98,739,601 · k: 98,717,659 · i: 98,711,737 · h: 98,652,684 · g: 97,934,560 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 87,063,441 (87.93%) · k: 7,325,353 (7.40%) · i: 2,588,584 (2.61%) · h: 1,971,084 (1.99%) · g: 68,261 (0.07%) (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 99,016,723 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f95335860f60cd737af2f4614b527b3b5dca40b8c5f4e0bf9d8e8e30e9a0bfe7
the corpus checksum ledger names this file with the same digest
joined 99,018,992 to merged 99,016,723, minus 2,269 (minus 0.0023%)
boundary drops 2,269 · 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-28T23:07:26Z 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,205,453 120,217,582 0-38 ca96645abf4e1438ad5cb2d56465d2f11ee9018ac4d0ba1887a8306e9e3983e9 book 391,948 36,934,832 39-40 729f16237b0a17a4548902702648802469774bde7e0a8f8b93aff4e287bd6a0b last_trade_price 54,972 3,135,440 41-41 1f3c2e986a0ad1930e2f5c7b3afee7dd09e1377022c70688951fdb878496388f market_resolved 2,415 356,365 42-42 5cb7a15cfbb808358a74f858be57489e983f12e602d2dbededaccb3c8309a42e new_market 3,779 386,217 43-43 d6db354bf21060ebd2d96014e9b87b1047865083ec5801dfe47e047690f7d1f8 price_change 88,354,416 920,720,577 44-381 c10de6ae7eafd5c8781068de04397642abc05a691961a8b817c96a37e09e329b tick_size_change 3,740 138,155 382-382 e662e45e7f7722b405a97e08fae0c3d3a4a067dba3b5966035f938cd30aa53d9 EVENT MIX count share price_change 88,354,416 89.23% best_bid_ask 10,205,453 10.31% book 391,948 0.40% last_trade_price 54,972 0.06% new_market 3,779 <0.01% tick_size_change 3,740 <0.01% market_resolved 2,415 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,205,758 10,205,453 305 142 FULL book 391,956 391,948 8 110,866 FULL last_trade_price 54,972 54,972 0 1 FULL market_resolved 2,415 2,415 0 1 FULL new_market 3,779 3,779 0 0 FULL price_change 88,356,372 88,354,416 1,956 288 FULL tick_size_change 3,740 3,740 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,203,360 9,061,921 5ms 20ms 274ms 23.4s 0 transport_latency_assumed best_bid_ask g 10,183,790 1,938 80ms 131ms 1.2s 47.9s 0 transport_latency_assumed best_bid_ask h 10,199,124 186,093 19ms 31ms 457ms 1.7min 0 transport_latency_assumed best_bid_ask i 10,203,225 253,412 19ms 29ms 266ms 23.7s 0 transport_latency_assumed best_bid_ask k 10,202,902 702,089 13ms 26ms 269ms 1.1min 0 transport_latency_assumed book c 201,065 169,860 47ms 17.4h 31.6d 121.9d 0 book_staleness book g 167,470 50,016 319ms 9.7h 23.3d 103.4d 0 book_staleness book h 169,493 48,152 43ms 9.7h 23.3d 121.9d 0 book_staleness book i 190,436 64,176 97ms 12.5h 29.0d 121.9d 0 book_staleness book k 174,996 59,744 29ms 9.9h 23.3d 121.9d 0 book_staleness last_trade_price c 54,647 47,693 7ms 37ms 388ms 3.6s 0 transport_latency_assumed last_trade_price g 52,056 11 93ms 1.2s 16.8s 46.1s 0 transport_latency_assumed last_trade_price h 54,750 1,209 20ms 104ms 889ms 55.0s 0 transport_latency_assumed last_trade_price i 54,715 1,221 22ms 165ms 1.1s 8.4s 0 transport_latency_assumed last_trade_price k 54,586 4,838 15ms 53ms 368ms 12.8s 0 transport_latency_assumed market_resolved c 2,229 1,856 6ms 97ms 53.6s 55.1s 0 transport_latency_assumed market_resolved g 2,228 not meas. 81ms 560ms 46.0s 57.4s 0 transport_latency_assumed market_resolved h 2,229 32 19ms 117ms 49.4s 49.6s 0 transport_latency_assumed market_resolved i 2,229 387 21ms 27.3s 53.6s 57.1s 0 transport_latency_assumed market_resolved k 2,229 140 14ms 71ms 48.1s 1.1min 0 transport_latency_assumed new_market c 2,430 921 249ms 1.4min 1.8min 2.1min 0 transport_latency_assumed new_market g 2,430 368 422ms 1.4min 1.8min 2.1min 0 transport_latency_assumed new_market h 2,430 755 233ms 1.4min 1.8min 2.2min 0 transport_latency_assumed new_market i 2,430 1,124 246ms 1.4min 1.8min 2.1min 0 transport_latency_assumed new_market k 2,430 611 253ms 1.4min 1.8min 2.1min 0 transport_latency_assumed price_change c 88,272,130 77,778,044 6ms 24ms 298ms 23.7s 0 transport_latency_assumed price_change g 87,522,850 15,926 81ms 217ms 5.1s 47.9s 0 transport_latency_assumed price_change h 88,220,918 1,734,716 19ms 41ms 571ms 1.7min 0 transport_latency_assumed price_change i 88,254,962 2,268,040 20ms 42ms 445ms 24.6s 0 transport_latency_assumed price_change k 88,276,776 6,557,690 14ms 31ms 295ms 1.1min 0 transport_latency_assumed tick_size_change c 3,740 3,146 6ms 33ms 175ms 780ms 0 transport_latency_assumed tick_size_change g 3,736 2 81ms 165ms 942ms 10.8s 0 transport_latency_assumed tick_size_change h 3,740 127 19ms 42ms 356ms 13.3s 0 transport_latency_assumed tick_size_change i 3,740 224 19ms 38ms 280ms 752ms 0 transport_latency_assumed tick_size_change k 3,740 241 14ms 40ms 413ms 11.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-28/20/2026-09-28T20.parquet sha256sum 2026-09-28T20.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.