Hour audit: 2026-09-15T02
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-15T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-15T02:00:00.000229385+00:00 · last event 2026-09-15T02:59:59.999902695+00:00
VOLUME 120,516,975 rows · 1,258,523,909 bytes (1.17 GiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured e: 119,636,906 · h: 119,604,294 · f: 115,406,895 · g: 115,129,362 · c: 110,650,116 (each machine's own feed; these overlap and do not sum to the file)
supplied e: 1,071,807 (0.89%) · h: 13,118,255 (10.88%) · f: 266,674 (0.22%) · g: 195,386 (0.16%) · c: 105,864,853 (87.84%) (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 120,516,975 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 4ca3ce5d444b0f7176d99df7268cb095dbca4b64552660ae778f43dc138e191a
the corpus checksum ledger names this file with the same digest
joined 120,519,264 to merged 120,516,975, minus 2,289 (minus 0.0019%)
boundary drops 2,289 · 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-15T04:00:08Z 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,808,221 140,332,414 0-48 a8d50b02aada1019837e6433e7ce6ffec80e308c747ec1b7a7b6b8aa935c7b13 book 941,752 67,179,496 49-52 f47b8085d26004b3e3b101188c7114b28c4d787e46ab4e441b0a34dbb78a753e last_trade_price 48,062 2,711,487 53-53 de6e70791f16dff3067ccfcaab681880aa4d043f0220b1d8fcf1ab34e21ccb25 market_resolved 2,896 418,039 54-54 b69a43f53a9ccc1c7134b67352361ff0b33cb6b143bb631c8c0463afa7d616f9 new_market 424 50,557 55-55 78efe42eaff90e2c2c9bf2926340c71038526740524c63b74dadd37c7941dbb4 price_change 106,711,076 1,046,293,482 56-463 5d73d71beef3422e1f522abc67f1c00d867ed79fa373594221abd3200d289d50 tick_size_change 4,544 166,859 464-464 e168e74faf4cb74f7d6335055f1a992163cd05458757805b64b0c9cfcedfb5cd EVENT MIX count share price_change 106,711,076 88.54% best_bid_ask 12,808,221 10.63% book 941,752 0.78% last_trade_price 48,062 0.04% tick_size_change 4,544 <0.01% market_resolved 2,896 <0.01% new_market 424 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,808,477 12,808,221 256 1,105 FULL book 941,830 941,752 78 171,276 FULL last_trade_price 48,063 48,062 1 163 FULL market_resolved 2,896 2,896 0 257 FULL new_market 424 424 0 1 FULL price_change 106,713,030 106,711,076 1,954 748 FULL tick_size_change 4,544 4,544 0 243 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 11,809,581 11,348,898 5ms 10ms 73ms 2.5s 0 transport_latency_assumed best_bid_ask e 12,806,114 100,342 42ms 50ms 120ms 3.7s 0 transport_latency_assumed best_bid_ask f 12,346,821 16,705 49ms 58ms 138ms 2.8s 0 transport_latency_assumed best_bid_ask g 12,306,898 1,176 86ms 131ms 290ms 12.2s 0 transport_latency_assumed best_bid_ask h 12,806,032 1,341,100 18ms 27ms 91ms 8.5s 0 transport_latency_assumed book c 784,424 663,276 6.6min 2.3d 36.6d 108.2d 0 book_staleness book e 103,216 4,662 45ms 121ms 2.5h 89.7d 0 book_staleness book f 446,685 74,942 3.6min 1.4d 34.3d 108.2d 0 book_staleness book g 472,090 180,832 3.7min 1.4d 34.3d 108.2d 0 book_staleness book h 104,141 18,040 21ms 90ms 24.7min 89.5d 0 book_staleness last_trade_price c 43,074 40,504 10ms 47ms 250ms 5.0s 0 transport_latency_assumed last_trade_price e 47,783 878 49ms 104ms 451ms 5.0s 0 transport_latency_assumed last_trade_price f 45,852 217 56ms 117ms 431ms 5.0s 0 transport_latency_assumed last_trade_price g 46,011 91 98ms 230ms 861ms 9.3s 0 transport_latency_assumed last_trade_price h 47,620 6,372 23ms 72ms 261ms 8.1s 0 transport_latency_assumed market_resolved c 2,473 2,324 5ms 3.3min 6.0min 6.2min 0 transport_latency_assumed market_resolved e 2,572 34 51ms 124ms 278ms 965ms 0 transport_latency_assumed market_resolved f 2,398 4 69ms 133ms 4.7min 5.6min 0 transport_latency_assumed market_resolved g 2,417 89 118ms 268ms 4.4min 4.9min 0 transport_latency_assumed market_resolved h 2,574 445 28ms 54ms 113ms 9.7s 0 transport_latency_assumed new_market c 316 195 42ms 14.2s 1.7min 1.7min 0 transport_latency_assumed new_market e 315 36 70ms 370ms 25.8s 26.2s 0 transport_latency_assumed new_market f 316 38 73ms 246ms 23.3s 1.2h 0 transport_latency_assumed new_market g 316 14 110ms 429ms 25.5s 1.2h 0 transport_latency_assumed new_market h 315 141 45ms 338ms 26.4s 27.6s 0 transport_latency_assumed price_change c 98,006,204 93,805,744 5ms 12ms 84ms 2.5s 0 transport_latency_assumed price_change e 106,672,362 965,810 43ms 53ms 148ms 3.8s 0 transport_latency_assumed price_change f 102,560,787 174,764 49ms 62ms 172ms 3.0s 0 transport_latency_assumed price_change g 102,297,542 13,184 86ms 138ms 348ms 12.4s 0 transport_latency_assumed price_change h 106,639,068 11,751,574 18ms 30ms 108ms 8.5s 0 transport_latency_assumed tick_size_change c 4,044 3,912 5ms 9ms 42ms 373ms 0 transport_latency_assumed tick_size_change e 4,544 45 42ms 50ms 105ms 176ms 0 transport_latency_assumed tick_size_change f 4,036 4 49ms 55ms 98ms 187ms 0 transport_latency_assumed tick_size_change g 4,088 not meas. 83ms 103ms 185ms 520ms 0 transport_latency_assumed tick_size_change h 4,544 583 18ms 27ms 70ms 356ms 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-15/02/2026-09-15T02.parquet sha256sum 2026-09-15T02.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.