Hour audit: 2026-09-18T04
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-18T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-18T04:00:00.000058061+00:00 · last event 2026-09-18T04:59:59.999870040+00:00
VOLUME 106,440,753 rows · 1,077,133,700 bytes (1.00 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 106,383,991 · h: 106,318,371 · e: 106,300,652 · f: 106,300,625 · g: 106,220,972 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 101,023,296 (94.91%) · h: 4,501,668 (4.23%) · e: 589,010 (0.55%) · f: 267,520 (0.25%) · g: 59,259 (0.06%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 106,440,753 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e285f8508ef483f879e3e185b28ff11e87d7e7ccc1081977f051ff43ae1f072e
the corpus checksum ledger names this file with the same digest
joined 106,442,825 to merged 106,440,753, minus 2,072 (minus 0.0019%)
boundary drops 2,072 · 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-18T05:57:27Z 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 11,663,862 131,180,392 0-44 71d4e1398370849ae2c8156d2bf3a7710268ea79979dc7621d925cfe33ec4580 book 135,192 13,784,305 45-45 eff6f357319eaec78ddd1ed9b89a696b156ef821be120247208797de5432406e last_trade_price 48,246 2,750,384 46-46 96cab420aa7f23f04a528ea44183d2bfb42c2eb4f908d1dd95c6162c2123718b market_resolved 1,278 204,296 47-47 d0705cb4f95daedd68cb7d6857472d2c5f4f573f271acf834159f6ad0a30acf8 new_market 2,661 265,702 48-48 d20a1f2c6f2bb62b03fce22595a360416f0185f2ea9508751b44355cadbba093 price_change 94,586,066 927,610,476 49-409 76c9b515343c8a12f1ee4cade9dd554a1208f6bf9a304cda460bd5bc4054903f tick_size_change 3,448 125,821 410-410 2c9f45567356847f30bf7223d504934c755df809db8b30b9106805a52327cc4c EVENT MIX count share price_change 94,586,066 88.86% best_bid_ask 11,663,862 10.96% book 135,192 0.13% last_trade_price 48,246 0.05% tick_size_change 3,448 <0.01% new_market 2,661 <0.01% market_resolved 1,278 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,664,022 11,663,862 160 164 FULL book 135,244 135,192 52 10,706 FULL last_trade_price 48,246 48,246 0 1 FULL market_resolved 1,278 1,278 0 1 FULL new_market 2,661 2,661 0 0 FULL price_change 94,587,926 94,586,066 1,860 310 FULL tick_size_change 3,448 3,448 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,663,028 11,136,352 5ms 10ms 178ms 9.7s 0 transport_latency_assumed best_bid_ask e 11,660,638 60,636 43ms 50ms 232ms 7.9s 0 transport_latency_assumed best_bid_ask f 11,661,490 24,196 47ms 57ms 272ms 7.6s 0 transport_latency_assumed best_bid_ask g 11,660,832 5,127 81ms 101ms 447ms 23.4s 0 transport_latency_assumed best_bid_ask h 11,661,434 437,551 18ms 25ms 344ms 47.1s 0 transport_latency_assumed book c 108,107 98,737 6ms 141ms 1.6h 92.7d 0 book_staleness book e 107,350 6,837 45ms 472ms 39.9min 92.7d 0 book_staleness book f 114,779 13,047 50ms 7.8s 6.4d 92.8d 0 book_staleness book g 107,875 5,698 85ms 1.2s 2.3h 92.7d 0 book_staleness book h 106,616 10,873 21ms 149ms 38.3min 92.7d 0 book_staleness last_trade_price c 48,074 44,686 10ms 48ms 304ms 4.8s 0 transport_latency_assumed last_trade_price e 48,022 497 50ms 128ms 2.3s 6.5s 0 transport_latency_assumed last_trade_price f 47,999 161 54ms 153ms 3.2s 9.5s 0 transport_latency_assumed last_trade_price g 47,854 90 93ms 214ms 5.2s 23.5s 0 transport_latency_assumed last_trade_price h 47,928 2,812 23ms 68ms 479ms 11.9s 0 transport_latency_assumed market_resolved c 1,267 1,200 5ms 17ms 473ms 701ms 0 transport_latency_assumed market_resolved e 1,267 13 74ms 205ms 656ms 1.0min 0 transport_latency_assumed market_resolved f 1,267 4 103ms 210ms 583ms 778ms 0 transport_latency_assumed market_resolved g 1,266 not meas. 157ms 369ms 957ms 4.9s 0 transport_latency_assumed market_resolved h 1,267 61 33ms 88ms 4.7s 59.3s 0 transport_latency_assumed new_market c 1,731 911 168ms 22.1s 49.8s 1.2min 0 transport_latency_assumed new_market e 1,731 515 182ms 20.7s 59.7s 1.7min 0 transport_latency_assumed new_market f 1,731 380 205ms 22.4s 59.0s 1.3min 0 transport_latency_assumed new_market g 1,731 178 347ms 22.6s 55.2s 1.3min 0 transport_latency_assumed new_market h 1,731 677 160ms 20.5s 49.0s 1.2min 0 transport_latency_assumed price_change c 94,558,336 89,738,086 5ms 12ms 203ms 9.7s 0 transport_latency_assumed price_change e 94,478,196 520,500 43ms 58ms 399ms 8.6s 0 transport_latency_assumed price_change f 94,469,911 229,732 48ms 65ms 429ms 8.1s 0 transport_latency_assumed price_change g 94,397,966 48,166 81ms 108ms 703ms 23.5s 0 transport_latency_assumed price_change h 94,495,947 4,049,582 18ms 30ms 371ms 47.1s 0 transport_latency_assumed tick_size_change c 3,448 3,324 5ms 7ms 89ms 803ms 0 transport_latency_assumed tick_size_change e 3,448 12 43ms 56ms 180ms 226ms 0 transport_latency_assumed tick_size_change f 3,448 not meas. 47ms 58ms 176ms 245ms 0 transport_latency_assumed tick_size_change g 3,448 not meas. 81ms 101ms 356ms 652ms 0 transport_latency_assumed tick_size_change h 3,448 112 18ms 24ms 99ms 5.2s 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-18/04/2026-09-18T04.parquet sha256sum 2026-09-18T04.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.