Hour audit: 2026-09-13T03
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-13T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T03:00:00.000004978+00:00 · last event 2026-09-13T03:59:59.999981530+00:00
VOLUME 126,761,670 rows · 1,366,028,827 bytes (1.27 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 124,223,903 · h: 119,123,613 · g: 118,997,596 · f: 114,758,713 · c: 92,964,212 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 5,241,985 (4.14%) · h: 29,908,855 (23.59%) · g: 119,248 (0.09%) · f: 1,281,865 (1.01%) · c: 90,209,717 (71.16%) (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 126,761,670 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 50f1704c4429861a605a2bb06c369433df36ad9ac7e22d2966f4060fc5770ac9
the corpus checksum ledger names this file with the same digest
joined 126,768,416 to merged 126,761,670, minus 6,746 (minus 0.0053%)
boundary drops 6,746 · 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-13T05:01:41Z 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,301,649 135,828,068 0-46 95333e4bba713756cfdd51b92186633021372491d7ea2043b0e68bda43ed9947 book 2,634,184 104,322,322 47-57 d3b2331af28037579599e210c40df20e2749a31c7e724642012d5c520630c87f last_trade_price 56,705 3,151,116 58-58 b5ac6e98a904a520da58b71b294830e1a1a66f9529f117aaca7c3181e2a30e8d market_resolved 5,872 671,802 59-59 0882aa392bd420601eca20e7ea6f0d6a01ddccbb18695c54d40411865865bf5a new_market 896 82,975 60-60 62dca8301c93fdd024048a3f74b731f46ab6d95ecbda135a1e59d2ad9ab57d41 price_change 111,754,884 1,120,257,733 61-487 c4636bde4f3cb4e2863a2a4020c1d98d2e7b9d342f7c62624b2b2cb8c9aa8cfc tick_size_change 7,480 273,210 488-488 25481ab16df20f731c8c3ee057f4f094e70ad92bbc1599fa4b0ee251724480d6 EVENT MIX count share price_change 111,754,884 88.16% best_bid_ask 12,301,649 9.70% book 2,634,184 2.08% last_trade_price 56,705 0.04% tick_size_change 7,480 <0.01% market_resolved 5,872 <0.01% new_market 896 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,301,897 12,301,649 248 7,051 FULL book 2,638,032 2,634,184 3,848 179,274 FULL last_trade_price 56,705 56,705 0 563 FULL market_resolved 5,872 5,872 0 561 FULL new_market 896 896 0 2 FULL price_change 111,757,534 111,754,884 2,650 3,849 FULL tick_size_change 7,480 7,480 0 526 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,035,436 8,788,874 5ms 9ms 66ms 3.1s 0 transport_latency_assumed best_bid_ask e 12,299,927 505,302 41ms 46ms 113ms 8.3s 0 transport_latency_assumed best_bid_ask f 11,325,877 100,981 46ms 51ms 127ms 6.3s 0 transport_latency_assumed best_bid_ask g 11,747,698 2,970 77ms 91ms 271ms 15.4s 0 transport_latency_assumed best_bid_ask h 11,764,119 2,903,522 17ms 27ms 97ms 8.3s 0 transport_latency_assumed book c 2,295,831 2,165,725 23.0min 1.4d 35.4d 106.2d 0 book_staleness book e 122,015 8,001 43ms 76ms 1.4min 87.7d 0 book_staleness book f 866,692 243,400 8.5min 1.4d 32.4d 106.2d 0 book_staleness book g 519,042 73,047 4.0min 1.2d 31.5d 106.2d 0 book_staleness book h 500,339 144,011 3.7min 1.1d 31.5d 106.2d 0 book_staleness last_trade_price c 40,860 39,126 10ms 38ms 185ms 4.9s 0 transport_latency_assumed last_trade_price e 56,548 3,079 47ms 93ms 366ms 5.0s 0 transport_latency_assumed last_trade_price f 51,443 908 53ms 117ms 1.1s 6.4s 0 transport_latency_assumed last_trade_price g 53,128 13 90ms 284ms 3.0s 15.4s 0 transport_latency_assumed last_trade_price h 53,371 13,579 22ms 60ms 255ms 5.7s 0 transport_latency_assumed market_resolved c 4,310 3,738 6ms 8.6min 13.3min 13.9min 0 transport_latency_assumed market_resolved e 3,998 167 44ms 122ms 278ms 39.0s 0 transport_latency_assumed market_resolved f 4,250 466 52ms 5.4min 9.7min 10.2min 0 transport_latency_assumed market_resolved g 3,997 213 89ms 254ms 4.4min 4.9min 0 transport_latency_assumed market_resolved h 3,876 1,288 24ms 62ms 167ms 2.5min 0 transport_latency_assumed new_market c 669 516 109ms 8.3min 3.1h 6.7h 0 transport_latency_assumed new_market e 517 71 148ms 16.9s 26.9s 5.2h 0 transport_latency_assumed new_market f 530 70 145ms 17.7s 1.8h 6.6h 0 transport_latency_assumed new_market g 517 73 290ms 16.6s 26.2s 6.7h 0 transport_latency_assumed new_market h 517 166 112ms 15.4s 26.9s 6.7h 0 transport_latency_assumed price_change c 81,581,502 79,206,210 5ms 9ms 79ms 4.0s 0 transport_latency_assumed price_change e 111,733,418 4,725,173 41ms 47ms 141ms 8.6s 0 transport_latency_assumed price_change f 102,503,077 935,988 46ms 52ms 143ms 11.8s 0 transport_latency_assumed price_change g 106,665,998 42,932 77ms 93ms 343ms 15.4s 0 transport_latency_assumed price_change h 106,794,115 26,844,581 17ms 29ms 118ms 8.3s 0 transport_latency_assumed tick_size_change c 5,604 5,528 5ms 8ms 22ms 69ms 0 transport_latency_assumed tick_size_change e 7,480 192 41ms 45ms 68ms 140ms 0 transport_latency_assumed tick_size_change f 6,844 52 46ms 50ms 92ms 186ms 0 transport_latency_assumed tick_size_change g 7,216 not meas. 77ms 90ms 163ms 453ms 0 transport_latency_assumed tick_size_change h 7,276 1,708 17ms 23ms 66ms 103ms 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/03/2026-09-13T03.parquet sha256sum 2026-09-13T03.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.