Hour audit: 2026-09-13T09
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-13T09 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T09:00:00.000007912+00:00 · last event 2026-09-13T09:59:59.999988154+00:00
VOLUME 104,576,080 rows · 1,091,683,970 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 103,823,009 · e: 103,800,959 · f: 103,791,884 · g: 103,769,616 · c: 95,766,878 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 12,322,615 (11.78%) · e: 699,107 (0.67%) · f: 326,391 (0.31%) · g: 63,810 (0.06%) · c: 91,164,157 (87.17%) (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 104,576,080 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 26b7ba0050140208858e5e362a8b47161fc11b52cd471ef87f34ee8d6e350271
the corpus checksum ledger names this file with the same digest
joined 104,577,546 to merged 104,576,080, minus 1,466 (minus 0.0014%)
boundary drops 1,466 · 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-13T10:57:44Z 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,100,863 111,104,499 0-38 1790771f7fbb653ea6a956fc261660218b1e1504cd675a22a07ce844fb8d085b book 838,840 62,154,724 39-42 7af94315487d51663f0c6962581df353492a0ca46350a037557da13741027559 last_trade_price 52,406 3,052,148 43-43 faf4782e7701674ecd070743b6a8a78de58c8568dc2d8efef3744ec2b62caa0b market_resolved 954 117,191 44-44 0d7b603fb4e33a5646c5ed09fb4d3f5d01daa586689ac428a9b14dcc03111f2d new_market 3,319 299,095 45-45 fc5d5b1ab893691e00b2611bbd069f90fa54db0017f4d8bd3c0dda93c6c8babb price_change 93,576,514 913,647,436 46-402 6bede897ecf59d97a888b1da901f313a413e0f9831fccc572c824d43e59e53a0 tick_size_change 3,184 117,209 403-403 6f831cbd9d621021f8607716ca046ac07d0a37db256f34e3e156b5bff2f87203 EVENT MIX count share price_change 93,576,514 89.48% best_bid_ask 10,100,863 9.66% book 838,840 0.80% last_trade_price 52,406 0.05% new_market 3,319 <0.01% tick_size_change 3,184 <0.01% market_resolved 954 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,100,951 10,100,863 88 2,077 FULL book 838,868 838,840 28 175,029 FULL last_trade_price 52,406 52,406 0 180 FULL market_resolved 954 954 0 4 FULL new_market 3,319 3,319 0 0 FULL price_change 93,577,864 93,576,514 1,350 947 FULL tick_size_change 3,184 3,184 0 75 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,234,832 8,811,140 5ms 10ms 183ms 5.7s 0 transport_latency_assumed best_bid_ask e 10,095,434 63,512 40ms 46ms 237ms 9.2s 0 transport_latency_assumed best_bid_ask f 10,094,970 27,976 47ms 55ms 268ms 11.8s 0 transport_latency_assumed best_bid_ask g 10,093,948 3,725 81ms 101ms 526ms 21.7s 0 transport_latency_assumed best_bid_ask h 10,096,648 1,194,510 17ms 23ms 251ms 40.9s 0 transport_latency_assumed book c 816,419 806,326 11.3min 1.6d 32.6d 106.5d 0 book_staleness book e 112,594 2,826 42ms 191ms 7.2s 87.8d 0 book_staleness book f 112,612 2,190 50ms 216ms 12.2s 87.9d 0 book_staleness book g 129,857 11,805 89ms 2.1min 4.0d 98.7d 0 book_staleness book h 112,042 15,693 21ms 63ms 2.5s 87.9d 0 book_staleness last_trade_price c 47,516 44,951 10ms 47ms 293ms 5.0s 0 transport_latency_assumed last_trade_price e 52,330 379 48ms 152ms 1.3s 9.3s 0 transport_latency_assumed last_trade_price f 52,257 210 56ms 168ms 2.7s 11.8s 0 transport_latency_assumed last_trade_price g 52,225 111 95ms 270ms 5.6s 21.8s 0 transport_latency_assumed last_trade_price h 52,359 6,755 23ms 68ms 366ms 12.1s 0 transport_latency_assumed market_resolved c 816 778 6ms 8.0min 11.4min 11.4min 0 transport_latency_assumed market_resolved e 704 90 41ms 48.2s 57.1s 57.2s 0 transport_latency_assumed market_resolved f 704 3 49ms 48.2s 57.1s 57.2s 0 transport_latency_assumed market_resolved g 703 not meas. 87ms 792ms 1.0min 1.0min 0 transport_latency_assumed market_resolved h 701 83 18ms 73ms 4.9s 1.1min 0 transport_latency_assumed new_market c 2,208 1,327 195ms 2.4min 46.2min 5.7h 0 transport_latency_assumed new_market e 1,901 424 194ms 23.4s 1.4min 3.5h 0 transport_latency_assumed new_market f 1,901 474 189ms 25.2s 1.5min 1.6h 0 transport_latency_assumed new_market g 1,901 239 332ms 24.7s 1.5min 50.5min 0 transport_latency_assumed new_market h 1,901 855 137ms 21.1s 1.7min 1.9h 0 transport_latency_assumed price_change c 85,662,203 81,496,926 5ms 12ms 197ms 7.2s 0 transport_latency_assumed price_change e 93,534,812 631,872 40ms 53ms 359ms 9.3s 0 transport_latency_assumed price_change f 93,526,256 295,538 47ms 64ms 465ms 11.9s 0 transport_latency_assumed price_change g 93,487,798 47,930 83ms 119ms 894ms 21.8s 0 transport_latency_assumed price_change h 93,556,174 11,104,248 18ms 26ms 291ms 42.5s 0 transport_latency_assumed tick_size_change c 2,884 2,709 5ms 9ms 223ms 538ms 0 transport_latency_assumed tick_size_change e 3,184 4 40ms 43ms 179ms 827ms 0 transport_latency_assumed tick_size_change f 3,184 not meas. 47ms 50ms 193ms 841ms 0 transport_latency_assumed tick_size_change g 3,184 not meas. 81ms 97ms 395ms 884ms 0 transport_latency_assumed tick_size_change h 3,184 471 17ms 20ms 108ms 2.1s 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-13/09/2026-09-13T09.parquet sha256sum 2026-09-13T09.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.