Hour audit: 2026-09-09T16
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-09T16 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T16:00:00.000029221+00:00 · last event 2026-09-09T16:59:59.999995696+00:00
VOLUME 121,007,726 rows · 1,312,172,567 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured h: 118,592,158 · g: 118,460,471 · e: 118,448,153 · f: 113,662,632 · c: 89,760,407 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 32,002,768 (26.45%) · g: 162,806 (0.13%) · e: 2,787,229 (2.30%) · f: 715,544 (0.59%) · c: 85,339,379 (70.52%) (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,007,726 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 407bc19f5812a4325dcdfa77cba7809afc0dc0fe52a76eb4519183ca4aaf738b
the corpus checksum ledger names this file with the same digest
joined 121,026,004 to merged 121,007,726, minus 18,278 (minus 0.0151%)
boundary drops 18,278 · 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-09T18:05:03Z 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,712,593 123,957,102 0-40 4fd0dc4f6bf0e53c470b028f176c9f04142ff618d8735ab31fe5eb3cf2161122 book 2,737,890 113,555,675 41-51 6cc41f6441bb24036b339d7598e9c94784ae4332ea306d16470027b126f0f124 last_trade_price 70,302 4,054,091 52-52 cd01a87c8a685e849948696e764e43016af7f520559c5b72fb1c2711381b30e3 market_resolved 1,736 218,401 53-53 554e4446394016af5cfe30ebca536aa4663d5f4a4a0d0aa3a9c1b15755f8c237 new_market 2,243 232,942 54-54 abe12378667be361227957960928b3bbff30453cb33c66a628d9e5ef7543b7ac price_change 107,479,274 1,068,644,989 55-465 13f7e4d70d2a7fd220921caac9f1832109c750401713790541a58c3bdf7d50e5 tick_size_change 3,688 131,489 466-466 3768804cf0465072e0d01f29fb227c29786612cdeb0243807b31973e2d2215ba EVENT MIX count share price_change 107,479,274 88.82% best_bid_ask 10,712,593 8.85% book 2,737,890 2.26% last_trade_price 70,302 0.06% tick_size_change 3,688 <0.01% new_market 2,243 <0.01% market_resolved 1,736 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,712,809 10,712,593 216 4,571 FULL book 2,752,346 2,737,890 14,456 185,361 FULL last_trade_price 70,302 70,302 0 586 FULL market_resolved 1,736 1,736 0 206 FULL new_market 2,287 2,243 44 135 FULL price_change 107,482,836 107,479,274 3,562 2,892 FULL tick_size_change 3,688 3,688 0 160 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,028,513 7,647,579 5ms 13ms 138ms 7.0s 0 transport_latency_assumed best_bid_ask e 10,710,098 243,598 39ms 50ms 239ms 6.4s 0 transport_latency_assumed best_bid_ask f 10,256,718 46,219 46ms 60ms 275ms 6.5s 0 transport_latency_assumed best_bid_ask g 10,706,570 4,042 85ms 113ms 519ms 21.8s 0 transport_latency_assumed best_bid_ask h 10,708,861 2,771,155 17ms 31ms 253ms 37.1s 0 transport_latency_assumed book c 2,477,083 2,308,967 29.4min 21.8h 32.0d 102.8d 0 book_staleness book e 208,398 29,003 54ms 3.4h 7.7d 102.7d 0 book_staleness book f 573,844 147,154 4.3min 15.2h 27.9d 102.8d 0 book_staleness book g 311,498 108,694 8.1s 7.8h 18.1d 102.8d 0 book_staleness book h 457,883 144,072 1.7min 11.8h 25.0d 102.8d 0 book_staleness last_trade_price c 50,717 47,921 10ms 42ms 239ms 5.0s 0 transport_latency_assumed last_trade_price e 70,251 1,713 46ms 161ms 2.0s 6.4s 0 transport_latency_assumed last_trade_price f 66,113 426 53ms 168ms 1.5s 6.5s 0 transport_latency_assumed last_trade_price g 69,832 50 97ms 339ms 5.3s 21.8s 0 transport_latency_assumed last_trade_price h 70,225 20,192 23ms 70ms 455ms 10.5s 0 transport_latency_assumed market_resolved c 1,274 1,220 7ms 6.0min 12.2min 13.6min 0 transport_latency_assumed market_resolved e 1,290 17 42ms 203ms 559ms 1.0min 0 transport_latency_assumed market_resolved f 1,179 36 48ms 270ms 4.8min 4.9min 0 transport_latency_assumed market_resolved g 1,290 1 92ms 381ms 935ms 1.8s 0 transport_latency_assumed market_resolved h 1,290 462 19ms 88ms 56.2s 1.0min 0 transport_latency_assumed new_market c 1,764 1,095 110ms 5.3min 7.6min 9.4min 0 transport_latency_assumed new_market e 1,394 284 153ms 14.2s 1.1min 53.7d 0 transport_latency_assumed new_market f 1,392 229 167ms 8.5s 56.9s 4.5min 0 transport_latency_assumed new_market g 1,394 109 337ms 14.4s 56.3s 53.7d 0 transport_latency_assumed new_market h 1,392 526 115ms 13.6s 54.4s 1.1min 0 transport_latency_assumed price_change c 79,198,004 75,329,602 5ms 14ms 157ms 9.1s 0 transport_latency_assumed price_change e 107,453,034 2,512,564 39ms 59ms 403ms 6.4s 0 transport_latency_assumed price_change f 102,759,718 521,468 46ms 70ms 426ms 6.5s 0 transport_latency_assumed price_change g 107,366,203 49,910 85ms 137ms 906ms 21.8s 0 transport_latency_assumed price_change h 107,348,819 29,065,730 17ms 35ms 291ms 1.2min 0 transport_latency_assumed tick_size_change c 3,052 2,995 5ms 9ms 107ms 423ms 0 transport_latency_assumed tick_size_change e 3,688 50 39ms 46ms 204ms 448ms 0 transport_latency_assumed tick_size_change f 3,668 12 46ms 54ms 260ms 631ms 0 transport_latency_assumed tick_size_change g 3,684 not meas. 84ms 101ms 466ms 12.3s 0 transport_latency_assumed tick_size_change h 3,688 631 17ms 27ms 141ms 1.4s 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-09/16/2026-09-09T16.parquet sha256sum 2026-09-09T16.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.