Hour audit: 2026-09-28T03
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-28T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T03:00:00.005111364+00:00 · last event 2026-09-28T03:59:59.999998489+00:00
VOLUME 101,876,334 rows · 1,041,560,876 bytes (993.31 MiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 101,783,733 · g: 101,733,325 · h: 100,869,792 · c: 100,594,930 · i: 100,308,691 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 6,756,108 (6.63%) · g: 8,680 (0.01%) · h: 1,187,957 (1.17%) · c: 93,340,150 (91.62%) · i: 583,439 (0.57%) (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 101,876,334 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0018d838b49ca2797e44f25a3f9d3b8a59472f13e071be4488132aa5161919db
the corpus checksum ledger names this file with the same digest
joined 101,878,106 to merged 101,876,334, minus 1,772 (minus 0.0017%)
boundary drops 1,772 · 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-28T05:38:59Z 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,186,484 112,734,691 0-38 009d269fc53b0738931e71c81934a0e3a7214487b0cffa9fd3d8b5938753ee98 book 173,385 15,261,527 39-39 68b7d646b104777ef94b844386c19fcef11852f5cd9c725c46799fcf16094c01 last_trade_price 48,490 2,741,222 40-40 60a9461982a9aa724e23832246a8adcc922c87fe31bebc71a19d8770c7400324 market_resolved 1,787 269,148 41-41 80006d56c14d7df1dfcc1dcd1d28f47a5f5fe7c948ff364f410da2aa9bb83d3d new_market 296 37,759 42-42 130ab9efc21d721137f37a974fa23ae067c9dd406227ac96f7376567d8a975b7 price_change 91,463,496 909,268,092 43-391 0d5137d04698e559ddd123a06f9a2226c5ae7e3556928ce081ea2f04b7b5d57e tick_size_change 2,396 88,703 392-392 64fefc3b77e4fcc4a76c2d4ea90ca7d9b7a47e7265db1d580a3f46b7b5d752c8 EVENT MIX count share price_change 91,463,496 89.78% best_bid_ask 10,186,484 10.00% book 173,385 0.17% last_trade_price 48,490 0.05% tick_size_change 2,396 <0.01% market_resolved 1,787 <0.01% new_market 296 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,186,672 10,186,484 188 558 FULL book 173,403 173,385 18 16,673 FULL last_trade_price 48,490 48,490 0 48 FULL market_resolved 1,787 1,787 0 16 FULL new_market 296 296 0 0 FULL price_change 91,465,062 91,463,496 1,566 810 FULL tick_size_change 2,396 2,396 0 11 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,085,199 9,431,959 4ms 10ms 67ms 2.4s 0 transport_latency_assumed best_bid_ask g 10,184,772 208 78ms 94ms 213ms 8.0s 0 transport_latency_assumed best_bid_ask h 10,149,991 101,488 17ms 23ms 87ms 1.1min 0 transport_latency_assumed best_bid_ask i 10,070,214 47,404 22ms 29ms 81ms 1.3s 0 transport_latency_assumed best_bid_ask k 10,185,662 605,425 12ms 18ms 68ms 21.7s 0 transport_latency_assumed book c 114,438 104,519 6ms 1.0h 18.8d 102.7d 0 book_staleness book g 102,490 4,196 80ms 262ms 23.6h 102.7d 0 book_staleness book h 131,393 39,358 23ms 41.2min 23.6h 102.7d 0 book_staleness book i 108,621 12,401 27ms 45.0s 8.7d 102.7d 0 book_staleness book k 103,372 12,911 15ms 54ms 23.8h 102.7d 0 book_staleness last_trade_price c 47,926 43,483 5ms 18ms 153ms 1.0s 0 transport_latency_assumed last_trade_price g 48,348 17 79ms 183ms 2.2s 8.0s 0 transport_latency_assumed last_trade_price h 46,424 612 19ms 36ms 206ms 1.7s 0 transport_latency_assumed last_trade_price i 47,690 360 26ms 46ms 233ms 1.1s 0 transport_latency_assumed last_trade_price k 48,400 4,018 13ms 25ms 165ms 4.0s 0 transport_latency_assumed market_resolved c 1,687 1,376 5ms 22.2s 55.1s 2.0min 0 transport_latency_assumed market_resolved g 1,696 not meas. 80ms 379ms 47.8s 52.5s 0 transport_latency_assumed market_resolved h 1,696 14 18ms 19.5s 53.9s 58.6s 0 transport_latency_assumed market_resolved i 1,689 254 25ms 20.5s 52.7s 2.4min 0 transport_latency_assumed market_resolved k 1,696 143 13ms 87ms 44.9s 51.0s 0 transport_latency_assumed new_market c 240 145 26ms 259ms 19.0s 1.5min 0 transport_latency_assumed new_market g 240 19 113ms 1.4s 21.7s 1.6min 0 transport_latency_assumed new_market h 240 91 27ms 304ms 1.5min 1.9min 0 transport_latency_assumed new_market i 240 24 47ms 226ms 15.8s 28.0s 0 transport_latency_assumed new_market k 240 17 53ms 462ms 22.5s 1.7min 0 transport_latency_assumed price_change c 90,343,068 83,756,468 4ms 12ms 79ms 2.4s 0 transport_latency_assumed price_change g 91,393,383 4,240 78ms 99ms 350ms 8.1s 0 transport_latency_assumed price_change h 90,537,652 1,046,348 18ms 26ms 106ms 1.2min 0 transport_latency_assumed price_change i 90,077,865 522,978 23ms 32ms 115ms 1.8s 0 transport_latency_assumed price_change k 91,441,967 6,133,462 12ms 20ms 80ms 24.2s 0 transport_latency_assumed tick_size_change c 2,372 2,200 5ms 12ms 58ms 168ms 0 transport_latency_assumed tick_size_change g 2,396 not meas. 78ms 96ms 264ms 372ms 0 transport_latency_assumed tick_size_change h 2,396 46 18ms 26ms 82ms 284ms 0 transport_latency_assumed tick_size_change i 2,372 18 25ms 30ms 70ms 161ms 0 transport_latency_assumed tick_size_change k 2,396 132 13ms 20ms 65ms 130ms 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/03/2026-09-28T03.parquet sha256sum 2026-09-28T03.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.