Hour audit: 2026-09-15T01
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-15T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T01:00:00.003473535+00:00 · last event 2026-09-15T01:59:59.999668692+00:00
VOLUME 125,504,228 rows · 1,332,434,902 bytes (1.24 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 123,550,266 · h: 123,510,311 · g: 118,902,986 · f: 118,453,973 · c: 100,392,884 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,790,559 (1.43%) · h: 27,194,428 (21.67%) · g: 140,904 (0.11%) · f: 443,661 (0.35%) · c: 95,934,676 (76.44%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 125,504,228 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 1d7e3222f28117be854139a80254301f5edadea111372654bf0b8f0be99fdd46
the corpus checksum ledger names this file with the same digest
joined 125,507,176 to merged 125,504,228, minus 2,948 (minus 0.0023%)
boundary drops 2,948 · 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-15T03:01:01Z as cefgh
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 our incident register was checked against the venue's own status feed at 2026-09-23T20:35Z and names no event in this hour. That is a statement about what they published, not a check that every message they sent reached us.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 13,493,764 148,683,178 0-51 4716152e4b40c663d241b6f48d4ea603d78198ffc56414a9c481f96f7903f38b book 2,057,861 90,725,410 52-59 d76429ead57d416f4928afce5dba7b0ae409fa997d8690cb29e8afb906b55bca last_trade_price 47,540 2,677,544 60-60 6249e00b9c57b464d857a8d7d5eec3fbbba4f8a7a9a34ac76f47b2e2c9cfc06f market_resolved 1,510 154,679 61-61 9d55333c35131202d1b308c2340289c2c63b2457e1522328f82bf26b49e2dda7 new_market 681 56,493 62-62 ec4cd68c34e280c2470eb849a304a0fa49d2d7fd2377684f77eb8b00eaec61e6 price_change 109,899,380 1,088,581,866 63-482 075dc8e2a6140ee016f14facba85d70690a1bcf136c97a764485d2f1a5f3c3bb tick_size_change 3,492 128,270 483-483 0793986967cec31e9e165c1d04a89b0375384076002f3cbf7e89985aa3e58983 EVENT MIX count share price_change 109,899,380 87.57% best_bid_ask 13,493,764 10.75% book 2,057,861 1.64% last_trade_price 47,540 0.04% tick_size_change 3,492 <0.01% market_resolved 1,510 <0.01% new_market 681 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 13,493,944 13,493,764 180 4,460 FULL book 2,059,349 2,057,861 1,488 171,316 FULL last_trade_price 47,540 47,540 0 342 FULL market_resolved 1,510 1,510 0 242 FULL new_market 681 681 0 2 FULL price_change 109,900,660 109,899,380 1,280 3,347 FULL tick_size_change 3,492 3,492 0 295 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,852,943 10,406,365 5ms 10ms 73ms 2.9s 0 transport_latency_assumed best_bid_ask e 13,491,284 173,497 39ms 47ms 123ms 3.6s 0 transport_latency_assumed best_bid_ask f 12,910,259 29,331 48ms 58ms 152ms 3.2s 0 transport_latency_assumed best_bid_ask g 12,932,927 1,778 83ms 101ms 230ms 12.8s 0 transport_latency_assumed best_bid_ask h 13,491,914 2,882,793 18ms 27ms 94ms 23.5s 0 transport_latency_assumed book c 1,819,811 1,776,087 9.9min 3.2d 37.4d 108.1d 0 book_staleness book e 153,195 24,023 49ms 2.0h 23.5d 108.1d 0 book_staleness book f 464,536 112,694 3.3min 1.4d 34.3d 108.1d 0 book_staleness book g 467,204 113,971 3.9min 1.4d 34.3d 108.1d 0 book_staleness book h 115,067 31,086 21ms 2.4min 4.7d 108.1d 0 book_staleness last_trade_price c 36,765 34,445 10ms 47ms 218ms 4.9s 0 transport_latency_assumed last_trade_price e 47,358 999 46ms 110ms 690ms 5.0s 0 transport_latency_assumed last_trade_price f 44,967 443 55ms 121ms 561ms 5.0s 0 transport_latency_assumed last_trade_price g 45,285 59 93ms 199ms 1.7s 10.3s 0 transport_latency_assumed last_trade_price h 47,261 11,594 23ms 70ms 268ms 7.2s 0 transport_latency_assumed market_resolved c 1,222 1,160 24ms 9.5min 18.2min 18.2min 0 transport_latency_assumed market_resolved e 916 29 43ms 124ms 276ms 634ms 0 transport_latency_assumed market_resolved f 895 9 69ms 236ms 5.8min 5.8min 0 transport_latency_assumed market_resolved g 770 16 97ms 270ms 2.2min 6.5min 0 transport_latency_assumed market_resolved h 916 296 20ms 56ms 1.0min 1.0min 0 transport_latency_assumed new_market c 595 479 294ms 10.0min 15.6min 15.9min 0 transport_latency_assumed new_market e 341 50 74ms 12.0s 23.1s 1.1min 0 transport_latency_assumed new_market f 342 48 80ms 12.9s 47.4s 4.4min 0 transport_latency_assumed new_market g 343 18 112ms 12.4s 4.2min 1.6h 0 transport_latency_assumed new_market h 341 86 54ms 11.1s 19.0s 21.9s 0 transport_latency_assumed price_change c 87,678,784 83,713,484 5ms 12ms 83ms 2.9s 0 transport_latency_assumed price_change e 109,853,680 1,591,926 39ms 51ms 159ms 4.3s 0 transport_latency_assumed price_change f 105,029,722 301,136 49ms 63ms 188ms 3.5s 0 transport_latency_assumed price_change g 105,453,345 25,062 83ms 103ms 286ms 12.8s 0 transport_latency_assumed price_change h 109,851,320 24,267,772 18ms 30ms 113ms 23.8s 0 transport_latency_assumed tick_size_change c 2,764 2,656 5ms 10ms 53ms 516ms 0 transport_latency_assumed tick_size_change e 3,492 35 40ms 49ms 114ms 744ms 0 transport_latency_assumed tick_size_change f 3,252 not meas. 48ms 56ms 205ms 443ms 0 transport_latency_assumed tick_size_change g 3,112 not meas. 82ms 102ms 312ms 507ms 0 transport_latency_assumed tick_size_change h 3,492 801 18ms 28ms 80ms 249ms 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-15/01/2026-09-15T01.parquet sha256sum 2026-09-15T01.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.