Hour audit: 2026-09-15T15
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-15T15 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T15:00:00.000021842+00:00 · last event 2026-09-15T15:59:59.999701712+00:00
VOLUME 121,466,522 rows · 1,325,905,366 bytes (1.23 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 120,128,181 · e: 119,723,054 · f: 115,587,540 · g: 114,799,275 · c: 105,819,016 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 20,033,652 (16.49%) · e: 1,326,729 (1.09%) · f: 580,652 (0.48%) · g: 295,332 (0.24%) · c: 99,230,157 (81.69%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 121,466,522 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 c3a348982f31d19551702356322b5bc7c73ae0f3e28af326205f56993b789c33
the corpus checksum ledger names this file with the same digest
joined 121,469,905 to merged 121,466,522, minus 3,383 (minus 0.0028%)
boundary drops 3,383 · 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-15T17:05:19Z 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,114,236 140,720,076 0-46 beda572bd250bc6f9ffc5d4d0b983fb98745a2e83586d50ba5636ed95b77926f book 1,439,683 86,930,584 47-52 5be9bfa41ff7f9299ba3b9e0ef179dfb58725b7fdf43da1fa9b2ca6a2d0a21df last_trade_price 69,985 4,027,829 53-53 43a98c0ccddd1d2fbe4286b0024c91c9ff37b9794d89bc7022de4d522c8f044a market_resolved 996 132,617 54-54 bc1a8938a74154be0fa981b4c14fabebcae547c311f19e60bc7fbe65dfa0d012 new_market 446 52,622 55-55 2f95c6caece4ddfd10fdbfe734ec3c131c63c0615ff9a24412f4820c2b31dd87 price_change 107,838,300 1,092,551,236 56-467 fad82a2511eef322347300d3d9b7e619d2d52304b69a378be5f72cb83fbdf015 tick_size_change 2,876 106,855 468-468 e4e2bfd37d0f0307de7d791c8e10b5adf40e2c8e01f8bb00ad2eb1ea3a1848c7 EVENT MIX count share price_change 107,838,300 88.78% best_bid_ask 12,114,236 9.97% book 1,439,683 1.19% last_trade_price 69,985 0.06% tick_size_change 2,876 <0.01% market_resolved 996 <0.01% new_market 446 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,114,576 12,114,236 340 9,008 FULL book 1,439,805 1,439,683 122 169,747 FULL last_trade_price 69,986 69,985 1 377 FULL market_resolved 996 996 0 7 FULL new_market 446 446 0 1 FULL price_change 107,841,220 107,838,300 2,920 3,072 FULL tick_size_change 2,876 2,876 0 78 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,707,002 10,128,608 6ms 14ms 104ms 4.3s 0 transport_latency_assumed best_bid_ask e 12,099,281 113,019 39ms 53ms 448ms 19.2s 0 transport_latency_assumed best_bid_ask f 11,654,913 28,097 44ms 56ms 200ms 10.9s 0 transport_latency_assumed best_bid_ask g 11,634,374 5,898 81ms 105ms 360ms 20.6s 0 transport_latency_assumed best_bid_ask h 12,112,983 1,838,614 18ms 28ms 114ms 7.5s 0 transport_latency_assumed book c 1,212,022 1,084,263 3.9min 2.5d 37.7d 108.7d 0 book_staleness book e 149,397 7,502 45ms 4.4s 6.2h 90.2d 0 book_staleness book f 502,496 132,740 1.1min 17.2h 33.8d 108.7d 0 book_staleness book g 516,950 188,246 1.1min 19.9h 33.8d 108.7d 0 book_staleness book h 146,786 26,932 22ms 69ms 1.5min 90.2d 0 book_staleness last_trade_price c 59,877 55,994 12ms 47ms 228ms 5.0s 0 transport_latency_assumed last_trade_price e 68,349 674 59ms 1.7s 9.9s 19.3s 0 transport_latency_assumed last_trade_price f 67,393 350 62ms 1.0s 6.2s 10.8s 0 transport_latency_assumed last_trade_price g 65,084 106 108ms 4.0s 14.5s 19.7s 0 transport_latency_assumed last_trade_price h 69,821 12,861 25ms 80ms 330ms 5.8s 0 transport_latency_assumed market_resolved c 847 808 7ms 1.7min 9.8min 11.6min 0 transport_latency_assumed market_resolved e 813 2 41ms 265ms 55.3s 58.8s 0 transport_latency_assumed market_resolved f 825 8 46ms 212ms 5.0min 5.0min 0 transport_latency_assumed market_resolved g 809 39 87ms 375ms 3.8min 3.8min 0 transport_latency_assumed market_resolved h 813 139 19ms 126ms 58.0s 58.0s 0 transport_latency_assumed new_market c 366 258 50ms 3.3min 8.2min 76.0d 0 transport_latency_assumed new_market e 340 20 115ms 295ms 1.1min 76.0d 0 transport_latency_assumed new_market f 340 61 102ms 26.9s 1.1min 76.0d 0 transport_latency_assumed new_market g 339 17 111ms 627ms 33.2s 59.7d 0 transport_latency_assumed new_market h 340 90 62ms 236ms 1.2min 76.0d 0 transport_latency_assumed price_change c 93,836,334 87,957,762 6ms 17ms 178ms 5.0s 0 transport_latency_assumed price_change e 107,401,998 1,205,500 40ms 89ms 4.1s 19.3s 0 transport_latency_assumed price_change f 103,358,785 419,392 44ms 78ms 1.7s 11.0s 0 transport_latency_assumed price_change g 102,578,891 101,026 84ms 163ms 5.7s 21.0s 0 transport_latency_assumed price_change h 107,794,562 18,154,620 18ms 35ms 230ms 7.6s 0 transport_latency_assumed tick_size_change c 2,568 2,464 6ms 12ms 51ms 133ms 0 transport_latency_assumed tick_size_change e 2,876 12 39ms 50ms 189ms 1.1s 0 transport_latency_assumed tick_size_change f 2,788 4 44ms 60ms 177ms 288ms 0 transport_latency_assumed tick_size_change g 2,828 not meas. 80ms 97ms 373ms 6.9s 0 transport_latency_assumed tick_size_change h 2,876 396 18ms 30ms 78ms 214ms 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/15/2026-09-15T15.parquet sha256sum 2026-09-15T15.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.