Hour audit: 2026-09-13T07
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-13T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-13T07:00:00.000063362+00:00 · last event 2026-09-13T07:59:59.999486554+00:00
VOLUME 93,503,655 rows · 900,582,561 bytes (858.86 MiB) · 7 products, all holding rows
WITNESSES cefgh — 5 machines contributed rows
captured c: 93,482,999 · h: 93,473,939 · e: 93,461,403 · g: 93,461,369 · f: 93,459,837 (each machine's own feed; these overlap and do not sum to the file)
supplied c: 91,083,834 (97.41%) · h: 2,261,941 (2.42%) · e: 98,788 (0.11%) · g: 17,926 (0.02%) · f: 41,166 (0.04%) (rows of the merged file that came from it; these partition it)
6 product-machine pairs publish no supplied count; the figures above still sum to the file's 93,503,655 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 04d5e1261c213eccb90c9d0fe3b35fc5ba7ecc612cd126ffcacec875c0a499d9
the corpus checksum ledger names this file with the same digest
joined 93,507,297 to merged 93,503,655, minus 3,642 (minus 0.0039%)
boundary drops 3,642 · 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-13T08:54:53Z 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,182,804 106,608,736 0-38 17943646f7d41f955061567ea11819f457ab422aeaeedbccd0740515e7e8e5cf book 111,511 11,215,930 39-39 7e15e18bf02491ee3263e03ff048f2b153e7d39dd72063afc75c6db0189be4e3 last_trade_price 44,072 2,553,758 40-40 3236ce13ae0aad3744c872dbaa93919c06e31747b2baec20bc3095f4c75ce0d7 market_resolved 918 148,157 41-41 ab99bd9be1a9f4f4b62b646346ebfe73807a1455d4d8df28657a7f51877af679 new_market 522 59,056 42-42 6cccf1ff0dbbb2ac2648dc97ba9372f39b2c4b73a4f3acb3de46586edd821e2d price_change 83,161,688 778,850,205 43-360 d7f9ccadce34ad0131a611b2ba304c041fe25f11efba6181401aec8140a74e7a tick_size_change 2,140 79,016 361-361 8a1872a4a423e1e4f42bfccdbd09a06af9df6571e9ded1cb6b5acfe5c10d0f12 EVENT MIX count share price_change 83,161,688 88.94% best_bid_ask 10,182,804 10.89% book 111,511 0.12% last_trade_price 44,072 0.05% tick_size_change 2,140 <0.01% market_resolved 918 <0.01% new_market 522 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,183,026 10,182,804 222 173 FULL book 111,511 111,511 0 9,097 FULL last_trade_price 44,072 44,072 0 0 FULL market_resolved 918 918 0 0 FULL new_market 522 522 0 0 FULL price_change 83,165,108 83,161,688 3,420 89 FULL tick_size_change 2,140 2,140 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 10,182,679 9,941,083 4ms 8ms 45ms 8.7s 0 transport_latency_assumed best_bid_ask e 10,181,190 9,667 40ms 43ms 85ms 4.5s 0 transport_latency_assumed best_bid_ask f 10,181,289 3,705 47ms 50ms 97ms 7.6s 0 transport_latency_assumed best_bid_ask g 10,179,923 248 80ms 98ms 212ms 13.6s 0 transport_latency_assumed best_bid_ask h 10,182,089 228,101 17ms 20ms 57ms 12.5s 0 transport_latency_assumed book c 94,253 90,962 6ms 16ms 3.8h 87.9d 0 book_staleness book e 92,214 1,504 42ms 70ms 3.9s 87.8d 0 book_staleness book f 92,115 960 49ms 83ms 2.6s 40.6d 0 book_staleness book g 106,002 14,852 88ms 1.5min 3.9d 87.9d 0 book_staleness book h 91,750 3,233 20ms 38ms 611ms 35.7d 0 book_staleness last_trade_price c 44,043 42,551 10ms 38ms 193ms 4.7s 0 transport_latency_assumed last_trade_price e 43,922 103 46ms 96ms 643ms 4.8s 0 transport_latency_assumed last_trade_price f 43,969 55 54ms 105ms 698ms 4.8s 0 transport_latency_assumed last_trade_price g 44,036 20 93ms 195ms 1.2s 10.4s 0 transport_latency_assumed last_trade_price h 44,026 1,343 22ms 54ms 336ms 9.3s 0 transport_latency_assumed market_resolved c 918 904 5ms 8ms 23ms 114ms 0 transport_latency_assumed market_resolved e 918 not meas. 41ms 121ms 273ms 423ms 0 transport_latency_assumed market_resolved f 918 not meas. 48ms 127ms 278ms 426ms 0 transport_latency_assumed market_resolved g 918 not meas. 85ms 238ms 455ms 1.0s 0 transport_latency_assumed market_resolved h 918 14 18ms 55ms 117ms 160ms 0 transport_latency_assumed new_market c 380 250 42ms 17.5s 11.7min 3.7h 0 transport_latency_assumed new_market e 380 40 63ms 11.5s 26.5s 28.0s 0 transport_latency_assumed new_market f 380 48 74ms 454ms 11.0min 4.5h 0 transport_latency_assumed new_market g 380 16 105ms 12.2s 6.8min 4.9h 0 transport_latency_assumed new_market h 380 168 46ms 12.0s 1.5min 6.1h 0 transport_latency_assumed price_change c 83,158,586 81,005,996 5ms 8ms 56ms 8.8s 0 transport_latency_assumed price_change e 83,140,639 87,474 40ms 44ms 119ms 4.7s 0 transport_latency_assumed price_change f 83,139,026 36,398 47ms 51ms 129ms 9.7s 0 transport_latency_assumed price_change g 83,127,970 2,790 80ms 99ms 266ms 14.4s 0 transport_latency_assumed price_change h 83,152,636 2,029,030 17ms 21ms 71ms 13.5s 0 transport_latency_assumed tick_size_change c 2,140 2,088 5ms 7ms 42ms 76ms 0 transport_latency_assumed tick_size_change e 2,140 not meas. 40ms 43ms 79ms 121ms 0 transport_latency_assumed tick_size_change f 2,140 not meas. 47ms 49ms 73ms 148ms 0 transport_latency_assumed tick_size_change g 2,140 not meas. 79ms 93ms 194ms 245ms 0 transport_latency_assumed tick_size_change h 2,140 52 17ms 19ms 39ms 91ms 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-13/07/2026-09-13T07.parquet sha256sum 2026-09-13T07.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.