Hour audit: 2026-09-27T23
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-27T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T23:00:00.000279236+00:00 · last event 2026-09-27T23:59:59.999983261+00:00
VOLUME 107,897,120 rows · 1,141,844,708 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured k: 107,818,644 · h: 107,756,202 · g: 107,500,060 · i: 106,608,747 · c: 105,690,573 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 7,781,180 (7.21%) · h: 2,115,083 (1.96%) · g: 24,348 (0.02%) · i: 3,109,680 (2.88%) · c: 94,866,829 (87.92%) (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 107,897,120 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 bf3cac296e25c9b5a889f0f4109b0cb3d540735a4ac83a351ce67c7fd025b413
the corpus checksum ledger names this file with the same digest
joined 107,916,682 to merged 107,897,120, minus 19,562 (minus 0.0181%)
boundary drops 19,562 · 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-28T02:06:42Z 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 11,448,155 129,361,450 0-43 f55cddbf448fbbca98303c3feddcb6d227d12ba1faeb9db108d7eccb62a95d88 book 137,175 13,670,099 44-44 3968df62f26ab311be8986dfa5ec38c915b10842c2494d2c177fbb90c538b256 last_trade_price 50,860 2,919,075 45-45 672e49f51c2faf6b98d4839f005c261e1a43c9304237f127dfb4d9fa07326b86 market_resolved 5,478 802,180 46-46 6418a3fbdcffb675f2bbd07eec328d8c487f04e299fd4ddc53a7b6f4a290d466 new_market 2,920 279,856 47-47 c794e58cbb1043f0e9a79d7fd2f76f10e750b29a69c0e8f5442ef38beb1eadd4 price_change 96,247,160 993,391,317 48-415 75eec0b07f9e2382158261dffefe35e7b7884b9c4b36e5ae4fd200efe478c989 tick_size_change 5,372 190,840 416-416 555701247abba8639c2a5b1d7d6a6a2d4be3a93441d10fdd2ff40f44b2138f51 EVENT MIX count share price_change 96,247,160 89.20% best_bid_ask 11,448,155 10.61% book 137,175 0.13% last_trade_price 50,860 0.05% market_resolved 5,478 <0.01% tick_size_change 5,372 <0.01% new_market 2,920 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,449,854 11,448,155 1,699 1,146 FULL book 137,188 137,175 13 10,021 FULL last_trade_price 50,866 50,860 6 84 FULL market_resolved 5,478 5,478 0 94 FULL new_market 2,920 2,920 0 10 FULL price_change 96,265,004 96,247,160 17,844 975 FULL tick_size_change 5,372 5,372 0 57 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,275,947 10,207,421 5ms 15ms 230ms 13.4s 0 transport_latency_assumed best_bid_ask g 11,440,387 1,397 81ms 119ms 855ms 33.3s 0 transport_latency_assumed best_bid_ask h 11,444,689 200,244 18ms 28ms 372ms 59.9s 0 transport_latency_assumed best_bid_ask i 11,282,324 303,090 19ms 27ms 139ms 4.3s 0 transport_latency_assumed best_bid_ask k 11,444,842 736,003 12ms 25ms 299ms 1.1min 0 transport_latency_assumed book c 105,818 91,745 7ms 231ms 19.7h 102.6d 0 book_staleness book g 112,610 8,643 89ms 7.2s 3.1d 102.5d 0 book_staleness book h 110,557 8,136 22ms 262ms 19.7h 102.5d 0 book_staleness book i 109,740 8,727 22ms 235ms 19.5h 102.5d 0 book_staleness book k 115,833 19,924 17ms 2.4s 5.2d 102.6d 0 book_staleness last_trade_price c 47,921 42,494 6ms 27ms 375ms 12.9s 0 transport_latency_assumed last_trade_price g 49,721 23 86ms 448ms 9.9s 32.9s 0 transport_latency_assumed last_trade_price h 50,526 1,233 19ms 66ms 615ms 46.4s 0 transport_latency_assumed last_trade_price i 50,410 1,619 21ms 78ms 630ms 4.4s 0 transport_latency_assumed last_trade_price k 50,746 5,491 14ms 52ms 461ms 20.9s 0 transport_latency_assumed market_resolved c 4,984 3,968 5ms 24.0s 54.1s 2.5min 0 transport_latency_assumed market_resolved g 5,031 327 82ms 233ms 51.8s 57.4s 0 transport_latency_assumed market_resolved h 5,032 67 19ms 19.3s 49.5s 57.1s 0 transport_latency_assumed market_resolved i 4,986 765 20ms 21.0s 55.2s 2.5min 0 transport_latency_assumed market_resolved k 5,032 351 13ms 17.3s 52.3s 58.9s 0 transport_latency_assumed new_market c 1,833 994 149ms 41.6s 1.0min 1.6min 0 transport_latency_assumed new_market g 1,823 280 359ms 23.8s 57.3s 1.7min 0 transport_latency_assumed new_market h 1,833 514 200ms 42.1s 1.0min 1.3min 0 transport_latency_assumed new_market i 1,833 755 113ms 24.3s 57.0s 1.7min 0 transport_latency_assumed new_market k 1,833 377 245ms 23.9s 55.5s 1.5min 0 transport_latency_assumed price_change c 94,248,854 84,515,170 5ms 19ms 259ms 13.4s 0 transport_latency_assumed price_change g 95,885,116 13,678 82ms 164ms 3.8s 33.3s 0 transport_latency_assumed price_change h 96,138,193 1,904,870 18ms 35ms 469ms 1.0min 0 transport_latency_assumed price_change i 95,154,154 2,794,676 20ms 33ms 230ms 4.4s 0 transport_latency_assumed price_change k 96,194,986 7,018,766 13ms 31ms 338ms 1.1min 0 transport_latency_assumed tick_size_change c 5,216 5,037 5ms 7ms 41ms 982ms 0 transport_latency_assumed tick_size_change g 5,372 not meas. 80ms 97ms 254ms 1.9s 0 transport_latency_assumed tick_size_change h 5,372 19 18ms 21ms 61ms 753ms 0 transport_latency_assumed tick_size_change i 5,300 48 18ms 24ms 60ms 673ms 0 transport_latency_assumed tick_size_change k 5,372 268 12ms 16ms 54ms 849ms 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-27/23/2026-09-27T23.parquet sha256sum 2026-09-27T23.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.