Hour audit: 2026-09-26T18
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-26T18 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T18:00:00.000000912+00:00 · last event 2026-09-26T18:59:59.999995603+00:00
VOLUME 136,924,125 rows · 1,563,672,672 bytes (1.46 GiB) · 7 products, all holding rows
WITNESSES chik — 4 machines contributed rows
captured i: 131,533,543 · h: 121,373,593 · k: 99,632,391 · c: 67,197,908 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 14,272,188 (10.42%) · h: 19,307,625 (14.10%) · k: 42,364,785 (30.94%) · c: 60,979,527 (44.54%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 1 contributed nothing: g
INTEGRITY sha256 1c9f72d09fc11c07e1f6c5696a44f25716e8a1844a0080db77e4af2ce8ffbd5a
the corpus checksum ledger names this file with the same digest
joined 136,936,366 to merged 136,924,125, minus 12,241 (minus 0.0089%)
boundary drops 12,241 · 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-27T01:28:58Z 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 12,674,932 149,147,801 0-48 76dcdb2b8ea45bb2c7a10a00f3730796910570de549597115defb789ccc27144 book 5,483,362 142,704,990 49-69 0e729d62c0a72bbf5b4779d20e00a8080503b5a1ae2a59d47558cbc17fe1d310 last_trade_price 68,875 3,916,631 70-70 abc1ff1e1540352c7acb41c20d77ecc508146762a09a569111b56e3b9b1abfe6 market_resolved 9,791 567,658 71-71 fbb6803071e481ae5281b2b0d69e1a9177b7c955b63f3f49c0d1dfbd9b5f4582 new_market 11,239 416,579 72-72 6ea928f39e7456de410cf176909204d484e06d43a9bac47261ee15e6304cb1a9 price_change 118,670,338 1,265,159,751 73-525 a43dbc299f1dacad81f38c5baedaafdb92df80fad48022b2b63e67303edc8d31 tick_size_change 5,588 204,126 526-526 cba1810dfb85063255942a9391220cfd3284c0be8c416aa3b5cd98d3ceee7689 EVENT MIX count share price_change 118,670,338 86.67% best_bid_ask 12,674,932 9.26% book 5,483,362 4.00% last_trade_price 68,875 0.05% new_market 11,239 <0.01% market_resolved 9,791 <0.01% tick_size_change 5,588 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,675,102 12,674,932 170 65,481 PARTIAL book 5,494,199 5,483,362 10,837 214,060 PARTIAL last_trade_price 68,875 68,875 0 4,371 PARTIAL market_resolved 9,791 9,791 0 3,121 PARTIAL new_market 11,239 11,239 0 2,378 PARTIAL price_change 118,671,572 118,670,338 1,234 101,655 PARTIAL tick_size_change 5,588 5,588 0 1,397 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,042,139 5,493,378 6ms 15ms 124ms 2.4s 0 transport_latency_assumed best_bid_ask h 11,611,784 1,840,544 19ms 60ms 221ms 6.6s 0 transport_latency_assumed best_bid_ask i 12,673,887 1,378,173 21ms 32ms 139ms 7.5s 0 transport_latency_assumed best_bid_ask k 9,301,486 3,962,837 13ms 22ms 111ms 4.0s 0 transport_latency_assumed book c 4,961,621 4,592,769 1.5h 5.3d 45.1d 119.9d 0 book_staleness book h 976,430 251,875 31.3min 4.9d 40.9d 119.9d 0 book_staleness book i 141,846 22,922 24ms 100ms 3.4s 119.8d 0 book_staleness book k 2,642,389 615,796 1.2h 4.9d 45.0d 119.9d 0 book_staleness last_trade_price c 29,899 26,533 7ms 24ms 236ms 1.5s 0 transport_latency_assumed last_trade_price h 62,763 10,754 24ms 84ms 824ms 6.0s 0 transport_latency_assumed last_trade_price i 68,746 8,387 23ms 72ms 599ms 3.8s 0 transport_latency_assumed last_trade_price k 49,903 23,201 14ms 34ms 232ms 2.6s 0 transport_latency_assumed market_resolved c 7,407 4,575 11.4min 26.8min 34.8min 36.7min 0 transport_latency_assumed market_resolved h 3,068 844 42ms 7.8min 12.1min 12.3min 0 transport_latency_assumed market_resolved i 2,582 502 23ms 12.5s 48.0s 56.5s 0 transport_latency_assumed market_resolved k 5,373 3,870 5.8min 16.8min 22.9min 23.6min 0 transport_latency_assumed new_market c 10,887 9,281 14.3min 30.0min 32.2min 36.6min 0 transport_latency_assumed new_market h 1,848 550 153ms 6.8min 7.5min 8.7min 0 transport_latency_assumed new_market i 1,502 320 88ms 12.6s 3.4min 4.2min 0 transport_latency_assumed new_market k 2,522 1,088 14.5s 14.3min 26.5min 27.0min 0 transport_latency_assumed price_change c 56,143,135 50,850,344 6ms 17ms 153ms 2.6s 0 transport_latency_assumed price_change h 108,712,612 17,202,399 20ms 63ms 274ms 7.0s 0 transport_latency_assumed price_change i 118,639,392 12,861,338 22ms 37ms 189ms 7.7s 0 transport_latency_assumed price_change k 87,626,414 37,756,257 13ms 24ms 134ms 5.9s 0 transport_latency_assumed tick_size_change c 2,820 2,647 5ms 10ms 41ms 87ms 0 transport_latency_assumed tick_size_change h 5,088 659 19ms 54ms 151ms 3.6s 0 transport_latency_assumed tick_size_change i 5,588 546 21ms 31ms 120ms 1.2s 0 transport_latency_assumed tick_size_change k 4,304 1,736 13ms 18ms 67ms 442ms 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/18/2026-09-26T18.parquet sha256sum 2026-09-26T18.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.