Hour audit: 2026-09-11T08
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-11T08 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-11T08:00:00.000908621+00:00 · last event 2026-09-11T08:59:59.997525802+00:00
VOLUME 105,695,949 rows · 1,099,828,678 bytes (1.02 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured g: 104,853,877 · f: 104,815,798 · h: 104,813,241 · e: 104,805,863 · c: 96,214,411 (each machine's own feed; these overlap and do not sum to the file)
supplied g: 62,604 (0.06%) · f: 99,739 (0.09%) · h: 12,311,144 (11.65%) · e: 535,550 (0.51%) · c: 92,686,912 (87.69%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 105,695,949 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 67c85f8d473828e0bdf76e5d2c3d0fa1c1470006180614743d847c8bba215423
the corpus checksum ledger names this file with the same digest
joined 105,699,038 to merged 105,695,949, minus 3,089 (minus 0.0029%)
boundary drops 3,089 · 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-11T09:57:50Z 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 9,289,795 106,270,569 0-35 22fcb9588f6ce6433696165ba6e98594f848e62748de78bea26f0cd5c3cc19b4 book 952,395 70,073,161 36-39 aa9f7c9a421377cfb43069f0aca322eb31d26748c5bf9f82785cf9c928eea0e4 last_trade_price 49,215 2,865,089 40-40 0bb1bdc5a3165f6b89d50b7c3e229a51434c32f6969e277053ca3b0e3499a792 market_resolved 661 94,459 41-41 544d150a73f820140a8b756d1e6cbf8196a8b7cbcfd1303f1bdaeadf817c7a70 new_market 659 72,064 42-42 dcf6ed416808a8a182246da6da5dabee26896f68f0b9e5e07d762309fbdcd728 price_change 95,401,012 919,167,649 43-406 441c84e921c8889f9426c035ea6028ea8f4ca565e748e86b8accd37181143a60 tick_size_change 2,212 81,237 407-407 b94e8addc14d2def811fe8d60965a3b5220dd03fef5a6dd919411c898bfd8903 EVENT MIX count share price_change 95,401,012 90.26% best_bid_ask 9,289,795 8.79% book 952,395 0.90% last_trade_price 49,215 0.05% tick_size_change 2,212 <0.01% market_resolved 661 <0.01% new_market 659 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,289,941 9,289,795 146 1,759 FULL book 952,843 952,395 448 203,016 FULL last_trade_price 49,218 49,215 3 186 FULL market_resolved 661 661 0 29 FULL new_market 659 659 0 7 FULL price_change 95,403,504 95,401,012 2,492 689 FULL tick_size_change 2,212 2,212 0 36 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 8,461,955 8,160,503 5ms 10ms 82ms 3.5s 0 transport_latency_assumed best_bid_ask e 9,288,278 45,808 39ms 44ms 123ms 2.8s 0 transport_latency_assumed best_bid_ask f 9,288,254 8,081 45ms 51ms 139ms 2.2s 0 transport_latency_assumed best_bid_ask g 9,287,604 1,047 77ms 95ms 274ms 10.7s 0 transport_latency_assumed best_bid_ask h 9,288,880 1,074,356 18ms 22ms 88ms 31.9s 0 transport_latency_assumed book c 918,916 885,112 11.1min 1.1d 30.6d 104.4d 0 book_staleness book e 103,705 2,521 41ms 121ms 11.0min 85.9d 0 book_staleness book f 103,107 1,894 48ms 125ms 3.5min 42.0d 0 book_staleness book g 155,908 50,357 101ms 4.0h 9.4d 104.4d 0 book_staleness book h 103,121 12,511 21ms 45ms 5.2min 85.8d 0 book_staleness last_trade_price c 44,996 43,052 10ms 39ms 182ms 5.0s 0 transport_latency_assumed last_trade_price e 49,136 304 46ms 112ms 511ms 5.0s 0 transport_latency_assumed last_trade_price f 49,097 80 53ms 118ms 639ms 5.0s 0 transport_latency_assumed last_trade_price g 49,107 6 92ms 235ms 1.2s 6.2s 0 transport_latency_assumed last_trade_price h 49,088 5,773 23ms 57ms 221ms 7.0s 0 transport_latency_assumed market_resolved c 541 518 6ms 3.8min 5.4min 5.4min 0 transport_latency_assumed market_resolved e 570 29 40ms 191ms 1.0min 1.0min 0 transport_latency_assumed market_resolved f 570 1 47ms 208ms 1.0min 1.0min 0 transport_latency_assumed market_resolved g 570 10 84ms 341ms 637ms 797ms 0 transport_latency_assumed market_resolved h 570 103 18ms 67ms 56.1s 57.5s 0 transport_latency_assumed new_market c 453 244 91ms 11.8s 1.2min 4.6min 0 transport_latency_assumed new_market e 460 112 162ms 14.0s 48.6s 1.5min 0 transport_latency_assumed new_market f 460 77 169ms 12.6s 25.9s 1.1min 0 transport_latency_assumed new_market g 460 36 299ms 14.2s 51.0s 1.1min 0 transport_latency_assumed new_market h 460 190 118ms 10.3s 50.1s 59.8s 0 transport_latency_assumed price_change c 86,785,482 83,595,480 5ms 11ms 90ms 7.1s 0 transport_latency_assumed price_change e 95,361,502 486,768 39ms 45ms 159ms 5.1s 0 transport_latency_assumed price_change f 95,372,098 89,606 45ms 53ms 180ms 5.0s 0 transport_latency_assumed price_change g 95,358,016 11,148 78ms 101ms 346ms 12.5s 0 transport_latency_assumed price_change h 95,368,910 11,218,010 18ms 24ms 103ms 35.5s 0 transport_latency_assumed tick_size_change c 2,068 2,003 5ms 10ms 37ms 74ms 0 transport_latency_assumed tick_size_change e 2,212 8 39ms 48ms 109ms 156ms 0 transport_latency_assumed tick_size_change f 2,212 not meas. 45ms 50ms 83ms 126ms 0 transport_latency_assumed tick_size_change g 2,212 not meas. 77ms 93ms 129ms 305ms 0 transport_latency_assumed tick_size_change h 2,212 201 18ms 24ms 46ms 62ms 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-11/08/2026-09-11T08.parquet sha256sum 2026-09-11T08.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.