Hour audit: 2026-09-26T14
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-26T14 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-09-26T14:00:00.000206961+00:00 · last event 2026-09-26T14:59:59.999881032+00:00
VOLUME 114,228,523 rows · 1,245,924,354 bytes (1.16 GiB) · 7 products, all holding rows
WITNESSES chik — 4 machines contributed rows
captured i: 112,657,279 · k: 106,289,856 · h: 101,419,017 · c: 99,069,281 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 4,453,609 (3.90%) · k: 15,018,416 (13.15%) · h: 4,114,691 (3.60%) · c: 90,641,807 (79.35%) (rows of the merged file that came from it; these partition it)
5 expected (cghik), 1 contributed nothing: g
INTEGRITY sha256 404d1e7ef2cbb935d0f5af30052163af5762ddc1703e23ade62146bd603f96cc
the corpus checksum ledger names this file with the same digest
joined 114,232,284 to merged 114,228,523, minus 3,761 (minus 0.0033%)
boundary drops 3,761 · 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:51:57Z 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,218,204 138,601,005 0-46 dc958abc7e6a4036db8febfdca178784af7021e79012e1e2e752b112c5941507 book 1,669,436 85,968,007 47-53 e5c048fd9079f29e707ea370d1561a066534c3e98e5fd51249a525d47a620eef last_trade_price 65,859 3,733,970 54-54 22999f60e5ea5ba9562a160582fcbd4a8cc3826e535aa287e7fad4f65305ae5a market_resolved 1,097 125,201 55-55 b5bb793b7226d5b49e2f16ceff3c1578a27c9158023fd6d9930d5fd907819c05 new_market 3,725 338,126 56-56 5e205a6d93730150e96518af6cc05cdd3b2c9dd8a2f86e09acf4e3bde79cc93d price_change 100,263,266 1,015,608,859 57-439 82603be3f6679a39bca7cf5ca6ae1f1d2661822988c45fa52b91fdc9c2a89080 tick_size_change 6,936 249,514 440-440 f46aed8449a830db6b991f114ff81290956f01867c5d6d0281cb0bc7be63d66b EVENT MIX count share price_change 100,263,266 87.77% best_bid_ask 12,218,204 10.70% book 1,669,436 1.46% last_trade_price 65,859 0.06% tick_size_change 6,936 <0.01% new_market 3,725 <0.01% market_resolved 1,097 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,218,616 12,218,204 412 58,148 PARTIAL book 1,669,469 1,669,436 33 213,214 PARTIAL last_trade_price 65,859 65,859 0 4,110 PARTIAL market_resolved 1,097 1,097 0 748 PARTIAL new_market 3,725 3,725 0 2,112 PARTIAL price_change 100,266,582 100,263,266 3,316 96,277 PARTIAL tick_size_change 6,936 6,936 0 1,734 PARTIAL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,575,934 9,760,920 5ms 12ms 209ms 15.8s 0 transport_latency_assumed best_bid_ask h 10,869,548 379,926 18ms 59ms 499ms 1.4min 0 transport_latency_assumed best_bid_ask i 12,216,539 481,427 22ms 28ms 137ms 4.3s 0 transport_latency_assumed best_bid_ask k 11,473,760 1,595,931 12ms 19ms 180ms 9.1s 0 transport_latency_assumed book c 1,380,683 642,340 1.4h 4.8d 42.2d 119.7d 0 book_staleness book h 978,558 575,713 52.2min 4.8d 40.8d 119.7d 0 book_staleness book i 136,337 10,951 24ms 63ms 5.2s 101.1d 0 book_staleness book k 546,746 440,432 12.3min 4.7d 35.0d 119.7d 0 book_staleness last_trade_price c 53,828 49,119 6ms 17ms 237ms 2.8s 0 transport_latency_assumed last_trade_price h 60,333 3,235 21ms 70ms 535ms 1.1min 0 transport_latency_assumed last_trade_price i 65,785 3,848 23ms 44ms 246ms 3.7s 0 transport_latency_assumed last_trade_price k 59,171 9,657 13ms 28ms 286ms 2.6s 0 transport_latency_assumed market_resolved c 765 584 7ms 4.1min 5.9min 6.0min 0 transport_latency_assumed market_resolved h 785 136 30ms 2.6min 7.7min 7.7min 0 transport_latency_assumed market_resolved i 748 160 23ms 43.8s 54.5s 56.4s 0 transport_latency_assumed market_resolved k 731 217 13ms 46.2s 4.2min 6.2min 0 transport_latency_assumed new_market c 2,682 1,276 481ms 5.6min 5.7min 5.8min 0 transport_latency_assumed new_market h 2,139 550 274ms 1.5min 5.2min 6.2min 0 transport_latency_assumed new_market i 2,112 1,062 151ms 1.4min 1.7min 1.8min 0 transport_latency_assumed new_market k 2,112 837 195ms 1.4min 1.7min 1.8min 0 transport_latency_assumed price_change c 87,049,089 80,181,671 5ms 13ms 214ms 17.4s 0 transport_latency_assumed price_change h 89,501,426 3,155,055 19ms 61ms 511ms 1.5min 0 transport_latency_assumed price_change i 100,228,822 3,956,120 22ms 30ms 168ms 5.0s 0 transport_latency_assumed price_change k 94,200,868 12,970,420 12ms 21ms 186ms 10.5s 0 transport_latency_assumed tick_size_change c 6,300 5,897 5ms 9ms 76ms 509ms 0 transport_latency_assumed tick_size_change h 6,228 76 18ms 43ms 76ms 57.3s 0 transport_latency_assumed tick_size_change i 6,936 41 21ms 25ms 60ms 236ms 0 transport_latency_assumed tick_size_change k 6,468 922 12ms 15ms 36ms 139ms 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/14/2026-09-26T14.parquet sha256sum 2026-09-26T14.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.