Hour audit: 2026-09-27T17
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-27T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-27T17:00:00.000003777+00:00 · last event 2026-09-27T17:59:59.999999931+00:00
VOLUME 145,204,396 rows · 1,723,682,770 bytes (1.61 GiB) · 7 products, all holding rows
WITNESSES cghik — 5 machines contributed rows
captured h: 140,442,360 · g: 125,571,409 · k: 123,318,818 · i: 122,688,033 · c: 83,479,940 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 16,430,290 (11.32%) · g: 372,913 (0.26%) · k: 49,163,524 (33.86%) · i: 6,394,571 (4.40%) · c: 72,843,098 (50.17%) (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 145,204,396 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0b9d9bd61b67038859b1f06ad41d951ae4f848ff4e51101d5e0499ac32fb8335
the corpus checksum ledger names this file with the same digest
joined 145,205,786 to merged 145,204,396, minus 1,390 (minus 0.0010%)
boundary drops 1,390 · 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-27T20:16:27Z 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 14,616,652 175,578,673 0-55 05e00c8ff1edb175dbca5b0d1cb0581e673e451f58f412bada1b4e9512624565 book 4,796,267 129,234,849 56-74 e4bf2e83790f69d31fe5b7d1fa273335e3d4839a82741b33440529b223b1116c last_trade_price 69,928 4,008,817 75-75 055b95455004371c76b7ca4077b1afb6b3c732fca44ab02e9b841344dbd33f5e market_resolved 3,524 159,230 76-76 2241c98fd756103e9bf87bd1396975a9c71a0918aaae03aef04efc311afe2973 new_market 18,539 746,270 77-77 09369c4136f4098fde0ad3cceb5bf527f54d6af936cd79fc9a2c1fd5b14739e5 price_change 125,694,142 1,412,110,500 78-557 4299fc9282fc6d21cf11b9401aabc4a3c3484e05ad117da33debc7b0b200f916 tick_size_change 5,344 196,034 558-558 ce901bf0a6194415a56de290ca2f9caac90a47d31b1b16c39d3996e6956fe11d EVENT MIX count share price_change 125,694,142 86.56% best_bid_ask 14,616,652 10.07% book 4,796,267 3.30% last_trade_price 69,928 0.05% new_market 18,539 0.01% tick_size_change 5,344 <0.01% market_resolved 3,524 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,616,804 14,616,652 152 10,686 FULL book 4,796,287 4,796,267 20 203,098 FULL last_trade_price 69,932 69,928 4 1,196 FULL market_resolved 3,524 3,524 0 119 FULL new_market 18,539 18,539 0 76 FULL price_change 125,695,356 125,694,142 1,214 20,367 FULL tick_size_change 5,344 5,344 0 795 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,295,018 7,218,337 6ms 26ms 288ms 10.1s 0 transport_latency_assumed best_bid_ask g 13,055,665 19,382 80ms 200ms 1.1s 37.0s 0 transport_latency_assumed best_bid_ask h 14,612,824 1,689,459 19ms 45ms 682ms 1.5min 0 transport_latency_assumed best_bid_ask i 12,575,589 629,546 21ms 41ms 214ms 14.4s 0 transport_latency_assumed best_bid_ask k 12,697,115 5,059,928 13ms 34ms 274ms 2.3min 0 transport_latency_assumed book c 4,189,356 4,063,644 1.6h 4.9d 46.0d 120.8d 0 book_staleness book g 975,727 154,106 55.0min 2.8d 42.5d 120.8d 0 book_staleness book h 154,708 19,554 27ms 708ms 13.6h 102.3d 0 book_staleness book i 1,429,970 212,747 1.1h 2.8d 43.2d 120.8d 0 book_staleness book k 1,396,877 346,216 1.0h 2.8d 43.2d 120.8d 0 book_staleness last_trade_price c 38,625 32,826 7ms 47ms 383ms 7.7s 0 transport_latency_assumed last_trade_price g 57,642 88 98ms 1.2s 19.4s 37.2s 0 transport_latency_assumed last_trade_price h 69,693 8,018 21ms 120ms 956ms 55.0s 0 transport_latency_assumed last_trade_price i 62,044 2,761 23ms 157ms 1.1s 3.3s 0 transport_latency_assumed last_trade_price k 62,889 26,235 15ms 68ms 443ms 8.4s 0 transport_latency_assumed market_resolved c 3,117 2,919 15.2min 38.4min 48.9min 51.9min 0 transport_latency_assumed market_resolved g 785 10 83ms 18.0s 6.7min 6.7min 0 transport_latency_assumed market_resolved h 842 121 20ms 142ms 52.1s 52.1s 0 transport_latency_assumed market_resolved i 926 110 23ms 4.5min 8.0min 8.0min 0 transport_latency_assumed market_resolved k 848 364 14ms 6.8s 7.4min 7.4min 0 transport_latency_assumed new_market c 17,229 13,486 13.1min 32.8min 47.1min 52.4min 0 transport_latency_assumed new_market g 4,039 305 316ms 1.5min 5.1min 5.2min 0 transport_latency_assumed new_market h 4,115 1,202 143ms 1.2min 2.2min 4.0min 0 transport_latency_assumed new_market i 5,329 2,318 157ms 4.0min 9.5min 10.3min 0 transport_latency_assumed new_market k 4,749 1,228 151ms 3.0min 8.4min 10.2min 0 transport_latency_assumed price_change c 70,933,563 61,509,442 6ms 29ms 321ms 10.5s 0 transport_latency_assumed price_change g 111,473,051 199,022 81ms 259ms 3.0s 37.2s 0 transport_latency_assumed price_change h 125,594,834 14,711,370 19ms 54ms 754ms 1.5min 0 transport_latency_assumed price_change i 108,609,223 5,546,905 21ms 49ms 320ms 14.5s 0 transport_latency_assumed price_change k 109,151,796 43,727,403 13ms 38ms 302ms 2.3min 0 transport_latency_assumed tick_size_change c 3,032 2,444 6ms 40ms 188ms 432ms 0 transport_latency_assumed tick_size_change g 4,500 not meas. 80ms 186ms 537ms 1.2s 0 transport_latency_assumed tick_size_change h 5,344 566 19ms 36ms 531ms 37.6s 0 transport_latency_assumed tick_size_change i 4,952 184 21ms 34ms 116ms 244ms 0 transport_latency_assumed tick_size_change k 4,544 2,150 13ms 27ms 95ms 323ms 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/17/2026-09-27T17.parquet sha256sum 2026-09-27T17.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.