Hour audit: 2026-09-12T11
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-12T11 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-12T11:00:00.000014929+00:00 · last event 2026-09-12T11:59:59.999992720+00:00
VOLUME 121,705,019 rows · 1,306,218,038 bytes (1.22 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 118,290,115 · h: 117,960,608 · e: 117,932,360 · f: 117,931,633 · c: 74,671,511 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 205,197 (0.17%) · h: 45,748,896 (37.59%) · e: 3,341,906 (2.75%) · f: 312,661 (0.26%) · c: 72,096,359 (59.24%) (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,705,019 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 8c30c11bdbaf481155701014a9d1d60e1d4982f44854ce45b715668b7ee5c7c4
the corpus checksum ledger names this file with the same digest
joined 121,708,631 to merged 121,705,019, minus 3,612 (minus 0.0030%)
boundary drops 3,612 · 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-12T13:02:29Z 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,492,296 117,854,230 0-40 87094ec6f23270eb541e650c779ce4d9d8fad7636d6da03e15ab906f138be454 book 3,854,252 124,501,226 41-55 706afa07eb581617bb16f53392b30e089c58aa1bfe345d8923d11a3027176a2b last_trade_price 50,374 2,955,379 56-56 75af91ec62226bf7af30c84f5de03b323586c525a742016bda668a198ab94704 market_resolved 2,056 172,824 57-57 b7b1a3e6f8ab1905110f4b052863267e9c55c683752d28cc215259f89adcbed3 new_market 1,039 71,063 58-58 fa0ffa684669cf24a867a000657f1967d0e4e398314c1c6e83dd7babfce13006 price_change 107,299,078 1,059,058,360 59-468 005cb080e3a0aa73ef79a2ac4d54d5a0b52d109617ae73773532ef91348c2cad tick_size_change 5,924 217,438 469-469 4732a98755a1c0ace523048d8bde5cdf82da07827f536b08c16fb514fb53d09c EVENT MIX count share price_change 107,299,078 88.16% best_bid_ask 10,492,296 8.62% book 3,854,252 3.17% last_trade_price 50,374 0.04% tick_size_change 5,924 <0.01% market_resolved 2,056 <0.01% new_market 1,039 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,492,480 10,492,296 184 7,273 FULL book 3,855,364 3,854,252 1,112 204,472 FULL last_trade_price 50,376 50,374 2 949 FULL market_resolved 2,056 2,056 0 25 FULL new_market 1,039 1,039 0 4 FULL price_change 107,301,392 107,299,078 2,314 5,507 FULL tick_size_change 5,924 5,924 0 455 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 6,412,577 6,195,380 5ms 10ms 86ms 3.0s 0 transport_latency_assumed best_bid_ask e 10,491,107 288,032 40ms 44ms 109ms 4.1s 0 transport_latency_assumed best_bid_ask f 10,491,140 22,714 47ms 54ms 149ms 3.9s 0 transport_latency_assumed best_bid_ask g 10,487,102 3,051 77ms 96ms 253ms 7.8s 0 transport_latency_assumed best_bid_ask h 10,491,657 3,983,119 18ms 27ms 92ms 14.5s 0 transport_latency_assumed book c 3,701,690 3,613,472 18.2min 17.8h 31.7d 105.6d 0 book_staleness book e 122,125 16,503 43ms 2.4min 1.8d 105.5d 0 book_staleness book f 118,242 8,187 50ms 27.1s 17.6h 87.0d 0 book_staleness book g 513,195 166,265 4.5min 16.9h 27.7d 105.6d 0 book_staleness book h 121,512 49,825 22ms 1.7min 17.6h 97.8d 0 book_staleness last_trade_price c 29,900 28,503 11ms 45ms 330ms 4.9s 0 transport_latency_assumed last_trade_price e 50,304 1,763 47ms 100ms 347ms 4.9s 0 transport_latency_assumed last_trade_price f 50,281 269 54ms 111ms 384ms 4.9s 0 transport_latency_assumed last_trade_price g 50,317 60 90ms 201ms 645ms 5.0s 0 transport_latency_assumed last_trade_price h 50,279 19,779 23ms 63ms 281ms 7.2s 0 transport_latency_assumed market_resolved c 1,772 1,764 6.1min 16.3min 23.9min 24.6min 0 transport_latency_assumed market_resolved e 1,006 11 41ms 120ms 271ms 41.4s 0 transport_latency_assumed market_resolved f 1,006 1 49ms 129ms 293ms 41.4s 0 transport_latency_assumed market_resolved g 1,006 not meas. 85ms 229ms 494ms 56.4s 0 transport_latency_assumed market_resolved h 1,006 280 19ms 57ms 125ms 52.9s 0 transport_latency_assumed new_market c 899 675 5.0min 11.6min 17.5min 19.5min 0 transport_latency_assumed new_market e 425 80 142ms 18.5s 23.4s 1.6min 0 transport_latency_assumed new_market f 425 56 165ms 643ms 21.2s 3.0min 0 transport_latency_assumed new_market g 425 73 302ms 18.5s 24.9s 1.5min 0 transport_latency_assumed new_market h 425 155 131ms 12.7s 20.2s 58.6s 0 transport_latency_assumed price_change c 64,520,565 62,252,797 5ms 11ms 110ms 4.0s 0 transport_latency_assumed price_change e 107,261,469 3,035,300 40ms 45ms 155ms 4.5s 0 transport_latency_assumed price_change f 107,264,615 281,412 48ms 55ms 198ms 4.9s 0 transport_latency_assumed price_change g 107,232,150 35,734 77ms 101ms 322ms 10.2s 0 transport_latency_assumed price_change h 107,289,805 41,693,835 18ms 29ms 122ms 17.0s 0 transport_latency_assumed tick_size_change c 4,108 3,768 5ms 15ms 568ms 1.3s 0 transport_latency_assumed tick_size_change e 5,924 217 40ms 48ms 300ms 2.2s 0 transport_latency_assumed tick_size_change f 5,924 22 48ms 57ms 280ms 1.9s 0 transport_latency_assumed tick_size_change g 5,920 14 78ms 120ms 491ms 3.4s 0 transport_latency_assumed tick_size_change h 5,924 1,903 18ms 31ms 324ms 4.9s 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-12/11/2026-09-12T11.parquet sha256sum 2026-09-12T11.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.