Hour audit: 2026-09-15T05
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-15T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T05:00:00.001284195+00:00 · last event 2026-09-15T05:59:59.999983783+00:00
VOLUME 104,163,231 rows · 1,040,010,405 bytes (991.83 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 103,957,871 · f: 103,927,503 · e: 103,925,403 · h: 103,876,001 · g: 103,798,880 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 99,931,063 (95.94%) · f: 197,663 (0.19%) · e: 370,919 (0.36%) · h: 3,578,148 (3.44%) · g: 85,438 (0.08%) (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 104,163,231 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ee4ed8a9d6e1ddca9e80da89c62aa3ace93bdaf0a6b7a4bb5e0b463b317352a6
the corpus checksum ledger names this file with the same digest
joined 104,168,030 to merged 104,163,231, minus 4,799 (minus 0.0046%)
boundary drops 4,799 · 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-15T06:57:04Z 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 12,241,366 132,323,451 0-46 3546de7a4238f643c3648d45c21290e6803d4517015e43dbfd60cfb508826a01 book 309,234 32,080,583 47-48 b7f6e8b6a53fff950a7440aaecd378821e3210100f0071284185d125f326d7d4 last_trade_price 46,889 2,672,733 49-49 b990c742c77bb948cab751aee9e74fd8958c86f982babe981aaa211240a65cda market_resolved 938 149,086 50-50 5830c763f83ddd41365775ddc328a96e1f39703f731a2b133657ad4a0b608235 new_market 2,154 210,545 51-51 e159b9f5dc684d9a682a24c6c6d9824e0b838880daa08b803e3355760392672a price_change 91,560,598 871,309,453 52-401 f478ec89027cec6c868c4b71e8946565fe474227c793dbb02d954aa3e5dfcc2e tick_size_change 2,052 76,416 402-402 8fc4e4dd1d82057dcdbd8feed5d85007a213e8a735e844749dd47a6da7701dce EVENT MIX count share price_change 91,560,598 87.90% best_bid_ask 12,241,366 11.75% book 309,234 0.30% last_trade_price 46,889 0.05% new_market 2,154 <0.01% tick_size_change 2,052 <0.01% market_resolved 938 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,241,646 12,241,366 280 156 FULL book 311,572 309,234 2,338 86,046 FULL last_trade_price 46,890 46,889 1 0 FULL market_resolved 938 938 0 0 FULL new_market 2,154 2,154 0 0 FULL price_change 91,562,778 91,560,598 2,180 110 FULL tick_size_change 2,052 2,052 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 12,240,390 11,801,789 5ms 9ms 96ms 8.8s 0 transport_latency_assumed best_bid_ask e 12,239,698 37,923 41ms 47ms 159ms 5.6s 0 transport_latency_assumed best_bid_ask f 12,239,145 16,428 48ms 54ms 172ms 5.6s 0 transport_latency_assumed best_bid_ask g 12,235,575 1,269 82ms 100ms 363ms 24.5s 0 transport_latency_assumed best_bid_ask h 12,235,685 383,957 17ms 23ms 143ms 30.4s 0 transport_latency_assumed book c 134,544 120,735 7ms 36.9min 9.6d 108.3d 0 book_staleness book e 117,709 16,012 45ms 3.3min 6.4d 108.3d 0 book_staleness book f 150,627 43,460 56ms 1.8h 20.4d 108.3d 0 book_staleness book g 181,177 69,625 399ms 4.9h 23.6d 108.3d 0 book_staleness book h 159,027 59,402 35ms 2.7h 20.4d 108.3d 0 book_staleness last_trade_price c 46,718 44,466 10ms 45ms 211ms 5.0s 0 transport_latency_assumed last_trade_price e 46,799 337 49ms 113ms 1.1s 5.6s 0 transport_latency_assumed last_trade_price f 46,706 168 55ms 123ms 1.4s 5.0s 0 transport_latency_assumed last_trade_price g 46,335 11 94ms 249ms 6.4s 24.6s 0 transport_latency_assumed last_trade_price h 46,346 1,907 23ms 71ms 310ms 7.8s 0 transport_latency_assumed market_resolved c 920 871 5ms 11ms 56.9s 58.5s 0 transport_latency_assumed market_resolved e 920 not meas. 72ms 194ms 46.4s 48.7s 0 transport_latency_assumed market_resolved f 920 19 58ms 166ms 616ms 1.0min 0 transport_latency_assumed market_resolved g 920 not meas. 105ms 325ms 44.4s 47.4s 0 transport_latency_assumed market_resolved h 920 48 31ms 77ms 44.1s 47.0s 0 transport_latency_assumed new_market c 1,345 821 96ms 39.0s 1.4min 6.9min 0 transport_latency_assumed new_market e 1,345 284 174ms 36.6s 1.4min 4.1min 0 transport_latency_assumed new_market f 1,345 206 186ms 37.4s 1.4min 1.6min 0 transport_latency_assumed new_market g 1,345 186 298ms 38.5s 1.4min 1.6min 0 transport_latency_assumed new_market h 1,345 657 118ms 31.1s 1.5min 2.3min 0 transport_latency_assumed price_change c 91,531,902 87,960,384 5ms 10ms 105ms 9.7s 0 transport_latency_assumed price_change e 91,516,880 316,358 41ms 51ms 263ms 14.9s 0 transport_latency_assumed price_change f 91,486,708 137,378 48ms 60ms 263ms 6.0s 0 transport_latency_assumed price_change g 91,331,476 14,344 82ms 110ms 565ms 24.8s 0 transport_latency_assumed price_change h 91,430,626 3,132,134 18ms 27ms 171ms 30.6s 0 transport_latency_assumed tick_size_change c 2,052 1,997 5ms 9ms 82ms 175ms 0 transport_latency_assumed tick_size_change e 2,052 5 42ms 61ms 204ms 231ms 0 transport_latency_assumed tick_size_change f 2,052 4 48ms 52ms 205ms 255ms 0 transport_latency_assumed tick_size_change g 2,052 3 82ms 112ms 311ms 667ms 0 transport_latency_assumed tick_size_change h 2,052 43 17ms 24ms 141ms 703ms 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/05/2026-09-15T05.parquet sha256sum 2026-09-15T05.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.