Hour audit: 2026-09-13T17
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-13T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T17:00:00.000014871+00:00 · last event 2026-09-13T17:59:59.999956301+00:00
VOLUME 149,389,883 rows · 1,690,710,214 bytes (1.57 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 145,080,407 · e: 145,052,736 · g: 118,250,743 · f: 116,634,777 · c: 92,985,720 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 53,058,278 (35.52%) · e: 5,483,274 (3.67%) · g: 601,025 (0.40%) · f: 1,349,543 (0.90%) · c: 88,897,763 (59.51%) (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 149,389,883 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 e7b4c152c21441f4d4652077e09e95e8be2ccca6ba12d524efd1ba1712fdc9ae
the corpus checksum ledger names this file with the same digest
joined 149,394,137 to merged 149,389,883, minus 4,254 (minus 0.0028%)
boundary drops 4,254 · 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-13T19:04:12Z 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 14,675,098 167,503,128 0-55 b8ef5b6c4200d6ccfceb26d3ef9bc3e9f164ec192812af6a3dbd955819a36a70 book 4,391,645 139,169,221 56-72 198db6d9ad22d99084b0e282763c1a84303ff6e8beaf6d65d62e501b2ac3e4ca last_trade_price 59,597 3,566,346 73-73 3fbd55a068ad406905236979c3e516cd58f6edfb64becb454e37cc227a99175a market_resolved 4,018 357,777 74-74 7d938cf05c90861c649d0c131dd00ff0a717054ccaee852ab47565f6643bc2da new_market 6,483 377,736 75-75 efd7be62929ab8ae0559dd574ff29f60e3173c9cae3750f413bd4914e2013419 price_change 130,245,786 1,377,776,240 76-572 3dacf9f520eab0c12f5ba91cee5b4532370dc82c54acb685072ca0dd1d3603e9 tick_size_change 7,256 266,963 573-573 4379d4a53e088f8fc9dafe5f0165c6024ae390457ab45631467f5e91f39495ec EVENT MIX count share price_change 130,245,786 87.19% best_bid_ask 14,675,098 9.82% book 4,391,645 2.94% last_trade_price 59,597 0.04% tick_size_change 7,256 <0.01% new_market 6,483 <0.01% market_resolved 4,018 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 14,675,380 14,675,098 282 10,057 FULL book 4,391,803 4,391,645 158 173,083 FULL last_trade_price 59,599 59,597 2 1,659 FULL market_resolved 4,018 4,018 0 540 FULL new_market 6,483 6,483 0 25 FULL price_change 130,249,598 130,245,786 3,812 7,289 FULL tick_size_change 7,256 7,256 0 946 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,059,939 8,678,571 5ms 12ms 95ms 4.4s 0 transport_latency_assumed best_bid_ask e 14,671,606 544,526 41ms 57ms 342ms 15.7s 0 transport_latency_assumed best_bid_ask f 11,622,560 92,347 47ms 62ms 310ms 14.3s 0 transport_latency_assumed best_bid_ask g 11,803,169 14,797 86ms 168ms 1.1s 34.0s 0 transport_latency_assumed best_bid_ask h 14,669,491 5,344,857 18ms 40ms 436ms 2.0min 0 transport_latency_assumed book c 3,600,711 3,504,306 23.7min 2.0d 36.1d 106.8d 0 book_staleness book e 127,528 8,493 44ms 207ms 11.1s 88.3d 0 book_staleness book f 1,964,476 380,587 18.6min 2.0d 36.0d 106.8d 0 book_staleness book g 1,748,576 445,328 17.8min 2.0d 36.0d 106.8d 0 book_staleness book h 147,920 52,931 25ms 2.0min 4.4d 88.7d 0 book_staleness last_trade_price c 35,288 33,464 11ms 51ms 257ms 5.0s 0 transport_latency_assumed last_trade_price e 59,315 2,221 51ms 161ms 1.6s 15.3s 0 transport_latency_assumed last_trade_price f 46,119 577 56ms 157ms 1.7s 14.4s 0 transport_latency_assumed last_trade_price g 48,221 199 103ms 337ms 6.4s 30.0s 0 transport_latency_assumed last_trade_price h 59,541 23,136 26ms 93ms 935ms 51.1s 0 transport_latency_assumed market_resolved c 2,809 2,324 4.4min 15.9min 21.5min 24.1min 0 transport_latency_assumed market_resolved e 2,054 136 42ms 175ms 42.7s 58.6s 0 transport_latency_assumed market_resolved f 2,257 589 59ms 9.4min 13.9min 14.0min 0 transport_latency_assumed market_resolved g 1,911 95 93ms 5.6min 9.8min 9.8min 0 transport_latency_assumed market_resolved h 2,054 874 20ms 73ms 7.5s 1.0min 0 transport_latency_assumed new_market c 5,400 4,567 9.2min 21.6min 28.0min 57.5min 0 transport_latency_assumed new_market e 2,197 458 278ms 13.0min 14.2min 14.5min 0 transport_latency_assumed new_market f 2,314 482 260ms 13.6min 27.3min 37.1min 0 transport_latency_assumed new_market g 2,360 326 442ms 12.9min 14.5min 46.1min 0 transport_latency_assumed new_market h 2,197 650 182ms 10.2min 14.2min 14.6min 0 transport_latency_assumed price_change c 80,276,773 76,669,947 5ms 13ms 118ms 8.5s 0 transport_latency_assumed price_change e 130,182,780 4,927,254 42ms 64ms 416ms 15.8s 0 transport_latency_assumed price_change f 102,991,295 874,907 47ms 68ms 380ms 14.4s 0 transport_latency_assumed price_change g 104,640,378 140,280 86ms 183ms 1.5s 34.3s 0 transport_latency_assumed price_change h 130,191,948 47,633,398 19ms 44ms 457ms 2.0min 0 transport_latency_assumed tick_size_change c 4,800 4,584 5ms 12ms 85ms 512ms 0 transport_latency_assumed tick_size_change e 7,256 186 41ms 59ms 287ms 621ms 0 transport_latency_assumed tick_size_change f 5,756 54 47ms 57ms 150ms 496ms 0 transport_latency_assumed tick_size_change g 6,128 not meas. 85ms 154ms 598ms 3.3s 0 transport_latency_assumed tick_size_change h 7,256 2,432 18ms 33ms 435ms 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-13/17/2026-09-13T17.parquet sha256sum 2026-09-13T17.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.