Hour audit: 2026-09-28T10
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-28T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-28T10:00:00.000008144+00:00 · last event 2026-09-28T10:59:59.999994728+00:00
VOLUME 106,119,226 rows · 1,182,634,351 bytes (1.10 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 105,240,466 · c: 102,318,311 · k: 102,288,306 · i: 102,249,754 · g: 101,992,733 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 5,571,908 (5.25%) · c: 89,457,176 (84.30%) · k: 6,760,364 (6.37%) · i: 4,303,800 (4.06%) · g: 25,978 (0.02%) (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 106,119,226 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1c8c60c139047ecd817a2f42a325ef09f89bbeb40a77563f1813c01e7110ff0f
the corpus checksum ledger names this file with the same digest
joined 106,124,014 to merged 106,119,226, minus 4,788 (minus 0.0045%)
boundary drops 4,788 · 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-28T12:38: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,213,069 120,226,750 0-38 84f52973870d3d1bf9f4a7a75bd5d6b46847430aa3de442b8a0ad7f152f67454 book 3,861,357 95,564,819 39-53 ca054eb03e17c0c8d153cc59816534f79dabbab1b048d70c908ff70e76d864ec last_trade_price 48,957 2,851,501 54-54 f0cff93a57b832033078353768bbb5c3d77a2285c69d4ae4e37976951ec2623a market_resolved 650 100,763 55-55 4434d65f80a525cd16100b3d2b59b1556bcba3278e13dcbabf205d1d7926b5c4 new_market 3,037 296,992 56-56 15f871120011ef4f8b8e18deda5bfabac91a05f085fd63cf5ee30be61dfabfb9 price_change 91,989,200 962,277,847 57-407 6226d63a77986d59e0514b2889a269bc43a34c33a85a691e5ee060114583ca69 tick_size_change 2,956 108,392 408-408 3a33c3932d7e94c6db59b40ee59c3049164d8f6255e4b5e97c6d3e88eabe24dd EVENT MIX count share price_change 91,989,200 86.68% best_bid_ask 10,213,069 9.62% book 3,861,357 3.64% last_trade_price 48,957 0.05% new_market 3,037 <0.01% tick_size_change 2,956 <0.01% market_resolved 650 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,213,289 10,213,069 220 474 FULL book 3,864,147 3,861,357 2,790 198,143 FULL last_trade_price 48,959 48,957 2 13 FULL market_resolved 650 650 0 12 FULL new_market 3,037 3,037 0 0 FULL price_change 91,990,976 91,989,200 1,776 326 FULL tick_size_change 2,956 2,956 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,210,416 9,012,814 5ms 18ms 249ms 6.1s 0 transport_latency_assumed best_bid_ask g 10,205,515 1,862 78ms 116ms 741ms 33.8s 0 transport_latency_assumed best_bid_ask h 10,132,222 161,478 17ms 31ms 403ms 1.1min 0 transport_latency_assumed best_bid_ask i 10,209,152 412,189 16ms 26ms 236ms 32.1s 0 transport_latency_assumed best_bid_ask k 10,210,218 624,726 12ms 23ms 209ms 57.3s 0 transport_latency_assumed book c 115,587 95,686 8ms 1.9min 9.8d 103.0d 0 book_staleness book g 106,861 2,845 89ms 5.6s 1.9d 103.0d 0 book_staleness book h 3,854,850 3,745,663 1.9h 3.5d 43.8d 121.5d 0 book_staleness book i 106,425 6,938 20ms 441ms 1.3d 102.9d 0 book_staleness book k 106,794 10,225 17ms 216ms 1.3d 103.0d 0 book_staleness last_trade_price c 48,794 41,965 7ms 39ms 416ms 5.6s 0 transport_latency_assumed last_trade_price g 47,978 11 88ms 873ms 11.2s 33.4s 0 transport_latency_assumed last_trade_price h 48,148 1,087 19ms 92ms 804ms 55.2s 0 transport_latency_assumed last_trade_price i 48,476 1,831 19ms 107ms 928ms 7.8s 0 transport_latency_assumed last_trade_price k 48,764 4,063 14ms 53ms 353ms 9.3s 0 transport_latency_assumed market_resolved c 611 559 6ms 13ms 297ms 473ms 0 transport_latency_assumed market_resolved g 611 not meas. 79ms 226ms 51.2s 56.8s 0 transport_latency_assumed market_resolved h 599 10 18ms 54ms 567ms 58.0s 0 transport_latency_assumed market_resolved i 611 51 18ms 94ms 39.8s 42.5s 0 transport_latency_assumed market_resolved k 611 30 13ms 64ms 48.5s 52.1s 0 transport_latency_assumed new_market c 1,891 703 191ms 28.1s 1.2min 1.7min 0 transport_latency_assumed new_market g 1,891 274 368ms 31.2s 1.1min 1.6min 0 transport_latency_assumed new_market h 1,891 678 187ms 31.8s 1.2min 1.5min 0 transport_latency_assumed new_market i 1,891 607 193ms 28.3s 1.1min 1.8min 0 transport_latency_assumed new_market k 1,891 775 202ms 29.4s 42.3s 1.5min 0 transport_latency_assumed price_change c 91,938,056 80,302,630 5ms 23ms 291ms 6.6s 0 transport_latency_assumed price_change g 91,626,921 20,986 79ms 174ms 3.2s 33.9s 0 transport_latency_assumed price_change h 91,199,804 1,662,990 18ms 40ms 508ms 1.1min 0 transport_latency_assumed price_change i 91,880,243 3,882,138 16ms 36ms 366ms 34.9s 0 transport_latency_assumed price_change k 91,917,072 6,120,456 13ms 28ms 255ms 57.6s 0 transport_latency_assumed tick_size_change c 2,956 2,819 5ms 9ms 44ms 55ms 0 transport_latency_assumed tick_size_change g 2,956 not meas. 77ms 92ms 434ms 1.8s 0 transport_latency_assumed tick_size_change h 2,952 2 17ms 20ms 55ms 7.5s 0 transport_latency_assumed tick_size_change i 2,956 46 15ms 22ms 56ms 403ms 0 transport_latency_assumed tick_size_change k 2,956 89 12ms 17ms 31ms 59ms 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/10/2026-09-28T10.parquet sha256sum 2026-09-28T10.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.