Hour audit: 2026-09-26T13
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.
1 finding
- a machine expected this hour contributed nothing. Of the 5 machines expected to be capturing this hour, 1 contributed no rows: g. The hour is still whole on minutes; it simply rests on 4 machines rather than 5.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-09-26T13 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T13:00:00.000052615+00:00 · last event 2026-09-26T13:59:59.999691854+00:00
VOLUME 106,872,098 rows · 1,152,061,372 bytes (1.07 GiB) · 7 products, all holding rows
WITNESSES chik — 4 machines contributed rows
captured i: 106,468,983 · c: 103,523,013 · k: 103,389,420 · h: 102,940,232 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,973,990 (1.85%) · c: 95,651,836 (89.50%) · k: 7,765,283 (7.27%) · h: 1,480,989 (1.39%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 1 contributed nothing: g
INTEGRITY sha256 00b74301145be27ac9927cdacc01ae16f28bef733a857b82b272a183c75e77a6
the corpus checksum ledger names this file with the same digest
joined 106,872,593 to merged 106,872,098, minus 495 (minus 0.0005%)
boundary drops 495 · 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-26T23:29:44Z as chik
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 7/8 pass, 1 finding
PASS all products present
PASS row counts reconcile
PASS byte ranges tile the file
PASS the merge delta is explained
FINDING a machine expected this hour contributed nothing
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,251,752 127,808,644 0-42 ccab2d44de4128d5063dbaee2fe79498b0e57377e40ce0031a7723d78299a5f8 book 493,780 50,072,761 43-44 42181e075e173d96c1d65433ee7b3158b96b04c00b59e8804d19c374307d629a last_trade_price 70,251 3,965,036 45-45 3ab04a1fb5ea87de8cd8c0440027cde260cccb2c5e5d69baf5cea722bfb77f68 market_resolved 604 93,476 46-46 37c12fa308a2c5ecfdd7a122e8814863de25c3ad5ff4d0b52c7c98cda66a3cb8 new_market 3,929 406,075 47-47 ece951f7065a11231921c8e1e468a3e24c0257f02650e38b0f8530e0b782dd8c price_change 95,048,890 968,394,095 48-410 0261623bfa6d905f80a2ea72b26eb63a651b7361236a0eb3fc8392439d34897f tick_size_change 2,892 107,117 411-411 d7d0468b4274de0693f0711a3fb3c48b19d271841eb5dfd131875e90ea3ffbe7 EVENT MIX count share price_change 95,048,890 88.94% best_bid_ask 11,251,752 10.53% book 493,780 0.46% last_trade_price 70,251 0.07% new_market 3,929 <0.01% tick_size_change 2,892 <0.01% market_resolved 604 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,251,786 11,251,752 34 52,958 PARTIAL book 493,862 493,780 82 165,793 PARTIAL last_trade_price 70,251 70,251 0 4,079 PARTIAL market_resolved 604 604 0 565 PARTIAL new_market 3,974 3,929 45 2,683 PARTIAL price_change 95,049,224 95,048,890 334 91,264 PARTIAL tick_size_change 2,892 2,892 0 723 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,868,056 10,072,291 5ms 13ms 182ms 5.6s 0 transport_latency_assumed best_bid_ask h 10,919,850 143,152 18ms 55ms 443ms 55.5s 0 transport_latency_assumed best_bid_ask i 11,249,953 203,239 20ms 29ms 178ms 7.9s 0 transport_latency_assumed best_bid_ask k 11,008,598 833,070 13ms 21ms 242ms 55.1s 0 transport_latency_assumed book c 481,452 466,072 2.3min 4.7d 41.9d 119.6d 0 book_staleness book h 131,837 4,771 24ms 206ms 6.3h 101.1d 0 book_staleness book i 151,058 8,651 23ms 227ms 1.7d 119.6d 0 book_staleness book k 144,578 14,286 16ms 101ms 2.3h 101.1d 0 book_staleness last_trade_price c 67,532 61,354 6ms 22ms 254ms 2.5s 0 transport_latency_assumed last_trade_price h 61,945 1,208 20ms 84ms 731ms 20.1s 0 transport_latency_assumed last_trade_price i 70,005 1,684 22ms 81ms 532ms 7.1s 0 transport_latency_assumed last_trade_price k 68,392 6,005 14ms 42ms 319ms 7.7s 0 transport_latency_assumed market_resolved c 562 479 5ms 286ms 51.7s 53.9s 0 transport_latency_assumed market_resolved h 552 42 20ms 107ms 57.9s 1.1min 0 transport_latency_assumed market_resolved i 565 59 22ms 242ms 41.3s 43.4s 0 transport_latency_assumed market_resolved k 550 24 15ms 12.4s 41.9s 2.3min 0 transport_latency_assumed new_market c 2,683 1,539 114ms 38.4s 37.5min 38.3min 0 transport_latency_assumed new_market h 2,622 681 193ms 32.8s 1.8min 2.1min 0 transport_latency_assumed new_market i 2,622 911 157ms 34.3s 1.9min 2.1min 0 transport_latency_assumed new_market k 2,622 798 202ms 34.3s 1.8min 2.1min 0 transport_latency_assumed price_change c 92,099,836 85,047,772 5ms 14ms 192ms 5.6s 0 transport_latency_assumed price_change h 91,820,610 1,331,004 18ms 58ms 463ms 56.3s 0 transport_latency_assumed price_change i 94,991,888 1,759,278 20ms 35ms 238ms 8.1s 0 transport_latency_assumed price_change k 92,161,848 6,910,836 13ms 25ms 251ms 58.8s 0 transport_latency_assumed tick_size_change c 2,892 2,329 5ms 151ms 365ms 515ms 0 transport_latency_assumed tick_size_change h 2,816 131 18ms 152ms 896ms 5.7s 0 transport_latency_assumed tick_size_change i 2,892 168 20ms 83ms 233ms 264ms 0 transport_latency_assumed tick_size_change k 2,832 264 13ms 102ms 377ms 767ms 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-26/13/2026-09-26T13.parquet sha256sum 2026-09-26T13.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.