Hour audit: 2026-09-09T02
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-09T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-09T02:00:00.000980153+00:00 · last event 2026-09-09T02:59:59.999984134+00:00
VOLUME 100,384,315 rows · 988,743,915 bytes (942.94 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured f: 100,257,401 · c: 100,256,959 · g: 100,237,684 · h: 100,179,011 · e: 100,163,334 (each machine's own feed; these overlap and do not sum to the file)
supplied f: 146,212 (0.15%) · c: 96,564,199 (96.19%) · g: 43,525 (0.04%) · h: 3,210,928 (3.20%) · e: 419,451 (0.42%) (rows of the merged file that came from it; these partition it)
3 product-machine pairs publish no supplied count; the figures above still sum to the file's 100,384,315 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f8c937b42b6daaf6946cedeee12dc3e99178f023e414fc234465ebdfc661b45b
the corpus checksum ledger names this file with the same digest
joined 100,387,771 to merged 100,384,315, minus 3,456 (minus 0.0034%)
boundary drops 3,456 · 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-09T03:56:52Z 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,984,935 108,872,804 0-38 9ed767056b0faf84debaf412ceeb5b5aa6847a942f8141dfe15e5ed79b9a76ca book 151,978 15,061,487 39-39 462e60c7a9c81e5e5711a99a21e0c27ae50f317367307bdfba6a62d5fe38bfc0 last_trade_price 52,885 2,937,766 40-40 8075a575147d23837b6bcfad18ac4f64cd4c96ce2a2b2f4f92e07740be1fd047 market_resolved 2,200 350,401 41-41 ccb98de7667ce3a54efe1f2ecffed3edbc520a83ce95cfa1a3ace90554d511f2 new_market 1,713 185,386 42-42 7030bfce670dd2b8fdd5071285f82ac41e32d1f7bea3f5a1ad88cf30916d8797 price_change 90,186,896 860,054,054 43-387 3ebfedc6bb7d2ef68ac25180fa60dd85615cfc8c30c870b63d5fb2ee22467a43 tick_size_change 3,708 134,676 388-388 f978931e73c511d828d7988e459fa909a304b4a941236d8abce89ec77dd95bde EVENT MIX count share price_change 90,186,896 89.84% best_bid_ask 9,984,935 9.95% book 151,978 0.15% last_trade_price 52,885 0.05% tick_size_change 3,708 <0.01% market_resolved 2,200 <0.01% new_market 1,713 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,985,243 9,984,935 308 295 FULL book 151,980 151,978 2 18,359 FULL last_trade_price 52,885 52,885 0 1 FULL market_resolved 2,200 2,200 0 0 FULL new_market 1,713 1,713 0 0 FULL price_change 90,190,042 90,186,896 3,146 508 FULL tick_size_change 3,708 3,708 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,984,225 9,634,797 4ms 9ms 109ms 6.9s 0 transport_latency_assumed best_bid_ask e 9,982,752 36,405 39ms 46ms 148ms 4.8s 0 transport_latency_assumed best_bid_ask f 9,983,034 12,600 46ms 55ms 166ms 2.2s 0 transport_latency_assumed best_bid_ask g 9,982,320 1,931 83ms 101ms 309ms 10.6s 0 transport_latency_assumed best_bid_ask h 9,983,419 299,202 19ms 24ms 150ms 45.5s 0 transport_latency_assumed book c 124,833 118,151 6ms 12.8s 1.4d 83.7d 0 book_staleness book e 116,914 7,161 41ms 175ms 7.3h 83.7d 0 book_staleness book f 117,052 6,574 49ms 166ms 7.1h 83.7d 0 book_staleness book g 121,440 10,567 88ms 2.0s 21.1h 102.2d 0 book_staleness book h 115,290 9,525 22ms 73ms 4.3h 83.6d 0 book_staleness last_trade_price c 52,834 50,420 9ms 39ms 230ms 5.0s 0 transport_latency_assumed last_trade_price e 52,776 235 45ms 91ms 1.4s 8.7s 0 transport_latency_assumed last_trade_price f 52,838 158 52ms 99ms 483ms 5.1s 0 transport_latency_assumed last_trade_price g 52,788 13 93ms 174ms 1.8s 7.0s 0 transport_latency_assumed last_trade_price h 52,712 2,059 24ms 57ms 304ms 38.3s 0 transport_latency_assumed market_resolved c 2,172 2,103 4ms 10ms 134ms 52.9s 0 transport_latency_assumed market_resolved e 2,172 8 43ms 124ms 57.3s 1.0min 0 transport_latency_assumed market_resolved f 2,172 2 54ms 146ms 57.4s 1.0min 0 transport_latency_assumed market_resolved g 2,172 not meas. 94ms 252ms 734ms 58.5s 0 transport_latency_assumed market_resolved h 2,172 87 27ms 59ms 57.0s 1.0min 0 transport_latency_assumed new_market c 1,187 757 80ms 23.2s 1.2min 5.8min 0 transport_latency_assumed new_market e 1,187 282 142ms 34.7s 1.2min 7.1min 0 transport_latency_assumed new_market f 1,187 133 164ms 32.4s 1.3min 4.6min 0 transport_latency_assumed new_market g 1,187 117 234ms 27.0s 1.4min 5.8min 0 transport_latency_assumed new_market h 1,187 424 114ms 12.8s 1.1min 3.3min 0 transport_latency_assumed price_change c 90,088,000 86,754,381 5ms 10ms 122ms 8.2s 0 transport_latency_assumed price_change e 90,003,825 375,352 39ms 49ms 188ms 4.8s 0 transport_latency_assumed price_change f 90,097,410 126,745 46ms 59ms 200ms 2.4s 0 transport_latency_assumed price_change g 90,074,069 30,897 83ms 108ms 372ms 13.0s 0 transport_latency_assumed price_change h 90,020,523 2,899,521 19ms 26ms 169ms 47.0s 0 transport_latency_assumed tick_size_change c 3,708 3,590 5ms 10ms 79ms 575ms 0 transport_latency_assumed tick_size_change e 3,708 8 39ms 51ms 106ms 162ms 0 transport_latency_assumed tick_size_change f 3,708 not meas. 46ms 67ms 163ms 384ms 0 transport_latency_assumed tick_size_change g 3,708 not meas. 83ms 112ms 309ms 671ms 0 transport_latency_assumed tick_size_change h 3,708 110 19ms 31ms 140ms 534ms 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/02/2026-09-09T02.parquet sha256sum 2026-09-09T02.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.