Hour audit: 2026-09-17T10
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-17T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-17T10:00:00.000003966+00:00 · last event 2026-09-17T10:59:59.999927973+00:00
VOLUME 109,222,098 rows · 1,163,349,630 bytes (1.08 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 108,514,904 · e: 108,461,255 · h: 108,449,709 · g: 108,444,840 · f: 108,428,272 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 103,493,379 (94.75%) · e: 536,257 (0.49%) · h: 4,643,302 (4.25%) · g: 227,168 (0.21%) · f: 321,992 (0.29%) (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 109,222,098 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 b26d6822aa75dff73e925cf044a9ae5ce7e12b88f41ba161d39f9e0ef1c46379
the corpus checksum ledger names this file with the same digest
joined 109,237,468 to merged 109,222,098, minus 15,370 (minus 0.0141%)
boundary drops 15,370 · 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-17T11:58:21Z 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 10,390,952 120,085,117 0-39 67829972855049d9a8d0bce9b5dd4957c9622866175947e8222d4ea2d13b5754 book 1,036,925 76,469,490 40-43 e1e2cb35000b53c85c3f429bb3198af5641179742f8645c668e6b0e3c673d527 last_trade_price 50,566 2,862,155 44-44 d38f42d093dbb1f074f4546a5d5583100a98851b24b255618e141e970aaa0603 market_resolved 743 123,775 45-45 bacc6bffa0eaa17e064bc0c8871d8ddee90a3df9e890c8668b1091e97a67f190 new_market 1,084 116,749 46-46 8f8fd811ce09d558b7bde3c4ed64fbdbb99a3d0ca71590494486cef2ca57915a price_change 97,738,648 962,333,672 47-419 36b0dc4ca7643e534501545cbebcea3fc7cbd40174a500d3a25e9d738407a368 tick_size_change 3,180 116,731 420-420 594e333b1238b078000eed762580cad7ef7e87ea23dd03512f3e3ac865240580 EVENT MIX count share price_change 97,738,648 89.49% best_bid_ask 10,390,952 9.51% book 1,036,925 0.95% last_trade_price 50,566 0.05% tick_size_change 3,180 <0.01% new_market 1,084 <0.01% market_resolved 743 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,391,180 10,390,952 228 194 FULL book 1,049,097 1,036,925 12,172 143,323 FULL last_trade_price 50,566 50,566 0 1 FULL market_resolved 745 743 2 59 FULL new_market 1,084 1,084 0 0 FULL price_change 97,741,616 97,738,648 2,968 58 FULL tick_size_change 3,180 3,180 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,381,552 9,945,360 5ms 12ms 88ms 13.5s 0 transport_latency_assumed best_bid_ask e 10,386,452 29,400 39ms 45ms 172ms 9.8s 0 transport_latency_assumed best_bid_ask f 10,386,942 11,490 47ms 55ms 201ms 6.9s 0 transport_latency_assumed best_bid_ask g 10,385,121 1,474 77ms 96ms 334ms 14.2s 0 transport_latency_assumed best_bid_ask h 10,385,026 403,228 18ms 26ms 123ms 8.8s 0 transport_latency_assumed book c 461,083 335,598 2.0min 17.8h 35.8d 110.5d 0 book_staleness book e 351,841 162,493 1.2min 6.7h 32.8d 110.5d 0 book_staleness book f 341,216 158,869 1.1min 5.9h 32.7d 110.5d 0 book_staleness book g 416,390 197,776 1.7min 14.0h 35.6d 110.5d 0 book_staleness book h 391,297 182,189 1.6min 10.6h 32.9d 110.5d 0 book_staleness last_trade_price c 49,886 47,321 11ms 48ms 242ms 13.1s 0 transport_latency_assumed last_trade_price e 50,240 386 48ms 204ms 2.2s 5.0s 0 transport_latency_assumed last_trade_price f 50,304 237 57ms 236ms 2.4s 6.1s 0 transport_latency_assumed last_trade_price g 50,178 69 93ms 355ms 8.2s 13.1s 0 transport_latency_assumed last_trade_price h 50,088 2,553 24ms 85ms 579ms 5.5s 0 transport_latency_assumed market_resolved c 708 689 6ms 15ms 95ms 336ms 0 transport_latency_assumed market_resolved e 689 1 119ms 284ms 595ms 1.1s 0 transport_latency_assumed market_resolved f 704 15 123ms 211ms 473ms 858ms 0 transport_latency_assumed market_resolved g 715 19 211ms 352ms 832ms 1.1s 0 transport_latency_assumed market_resolved h 688 19 44ms 86ms 249ms 660ms 0 transport_latency_assumed new_market c 765 490 80ms 14.0s 39.5s 1.2min 0 transport_latency_assumed new_market e 765 150 176ms 13.3s 24.5s 33.0s 0 transport_latency_assumed new_market f 765 59 207ms 14.1s 51.3s 1.0min 0 transport_latency_assumed new_market g 765 82 268ms 15.6s 29.1s 59.5s 0 transport_latency_assumed new_market h 765 303 133ms 15.5s 25.6s 1.2min 0 transport_latency_assumed price_change c 97,617,730 93,160,864 6ms 13ms 116ms 14.0s 0 transport_latency_assumed price_change e 97,668,088 343,822 40ms 52ms 369ms 10.9s 0 transport_latency_assumed price_change f 97,645,161 151,322 47ms 64ms 414ms 11.5s 0 transport_latency_assumed price_change g 97,588,491 27,748 78ms 106ms 661ms 15.9s 0 transport_latency_assumed price_change h 97,618,669 4,054,892 18ms 30ms 184ms 9.5s 0 transport_latency_assumed tick_size_change c 3,180 3,057 5ms 11ms 73ms 246ms 0 transport_latency_assumed tick_size_change e 3,180 5 40ms 108ms 213ms 292ms 0 transport_latency_assumed tick_size_change f 3,180 not meas. 47ms 51ms 167ms 360ms 0 transport_latency_assumed tick_size_change g 3,180 not meas. 78ms 93ms 246ms 540ms 0 transport_latency_assumed tick_size_change h 3,176 118 18ms 29ms 72ms 3.0s 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-17/10/2026-09-17T10.parquet sha256sum 2026-09-17T10.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.