Hour audit: 2026-09-22T05
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-22T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-09-22T05:00:00.000131792+00:00 · last event 2026-09-22T05:59:59.999640204+00:00
VOLUME 108,231,742 rows · 1,114,895,356 bytes (1.04 GiB) · 7 products, all holding rows
WITNESSES cefh — 4 machines contributed rows
captured h: 107,529,276 · e: 107,196,591 · c: 103,288,336 · f: 103,227,891 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 9,185,086 (8.49%) · e: 538,595 (0.50%) · c: 97,878,247 (90.43%) · f: 629,814 (0.58%) (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 108,231,742 rows exactly, so those pairs supplied none
4 expected, all 4 contributed
INTEGRITY sha256 5ec04b76b560d296568a8044cd0d32cc8ae4db32f5b954e16e09e3d7396f7faf
the corpus checksum ledger names this file with the same digest
joined 108,234,788 to merged 108,231,742, minus 3,046 (minus 0.0028%)
boundary drops 3,046 · 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-22T07:03:02Z as cefh
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,227,960 114,328,275 0-39 817a6115a8f780e2e35281dbe91ca5ff169a4795be741714c4803612aa6c5d8f book 901,944 64,367,812 40-43 8a8941e312631bfa837230ce8515e754be22b0fe7548cf4059972c5efb52f5a8 last_trade_price 49,009 2,774,477 44-44 947ff86057c7a602f0cd6e1a54f688dd159a13bbdf34398def4d18b7a269f06d market_resolved 2,106 315,499 45-45 b94925fc7d984fe33d92f8d5b922217d39e17b098e0ad6b7e34929f878c51466 new_market 1,221 127,369 46-46 c4e68d1d8c71c1f7957f72e02f94a92acc33012ab6593d07ef31888497a9bc04 price_change 97,046,162 931,627,508 47-417 2b7eaf92769c9022c012362c56bb88bc11c372be0c746920ffc27f8751a73422 tick_size_change 3,340 119,869 418-418 c72df24da89b110de747613cc508b73586d851d40a8fc0d09af76b79fab169ac EVENT MIX count share price_change 97,046,162 89.67% best_bid_ask 10,227,960 9.45% book 901,944 0.83% last_trade_price 49,009 0.05% tick_size_change 3,340 <0.01% market_resolved 2,106 <0.01% new_market 1,221 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,228,104 10,227,960 144 485 FULL book 902,076 901,944 132 151,298 FULL last_trade_price 49,009 49,009 0 92 FULL market_resolved 2,106 2,106 0 12 FULL new_market 1,221 1,221 0 0 FULL price_change 97,048,932 97,046,162 2,770 381 FULL tick_size_change 3,340 3,340 0 19 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask c 9,835,190 9,411,490 4ms 11ms 89ms 2.7s 0 transport_latency_assumed best_bid_ask e 10,225,723 35,140 41ms 49ms 153ms 3.9s 0 transport_latency_assumed best_bid_ask f 9,824,278 13,497 47ms 57ms 168ms 11.9s 0 transport_latency_assumed best_bid_ask h 10,226,649 767,833 17ms 28ms 113ms 47.4s 0 transport_latency_assumed book c 612,447 295,798 6.4min 2.7d 41.4d 115.3d 0 book_staleness book e 235,238 75,355 26.4s 10.7h 30.7d 115.3d 0 book_staleness book f 577,304 440,486 6.2min 2.6d 41.4d 115.3d 0 book_staleness book h 234,354 90,305 24.4s 10.7h 30.7d 115.3d 0 book_staleness last_trade_price c 46,484 43,587 5ms 19ms 153ms 1.1s 0 transport_latency_assumed last_trade_price e 48,878 320 43ms 90ms 662ms 3.9s 0 transport_latency_assumed last_trade_price f 46,482 128 49ms 95ms 437ms 5.9s 0 transport_latency_assumed last_trade_price h 48,952 4,974 19ms 40ms 214ms 8.2s 0 transport_latency_assumed market_resolved c 1,954 1,798 5ms 29ms 4.7min 4.8min 0 transport_latency_assumed market_resolved e 1,965 15 42ms 118ms 16.7s 29.1s 0 transport_latency_assumed market_resolved f 1,959 88 48ms 131ms 4.2min 4.2min 0 transport_latency_assumed market_resolved h 1,964 205 18ms 50ms 16.7s 29.3s 0 transport_latency_assumed new_market c 847 526 74ms 36.5s 2.0min 5.4min 0 transport_latency_assumed new_market e 845 156 144ms 17.7s 1.5min 2.1min 0 transport_latency_assumed new_market f 845 189 143ms 24.0s 1.3min 4.8min 0 transport_latency_assumed new_market h 845 350 106ms 21.6s 1.2min 1.8min 0 transport_latency_assumed price_change c 92,788,150 88,121,958 5ms 14ms 114ms 3.1s 0 transport_latency_assumed price_change e 96,680,602 427,587 41ms 57ms 236ms 4.0s 0 transport_latency_assumed price_change f 92,773,727 175,426 47ms 64ms 252ms 11.9s 0 transport_latency_assumed price_change h 97,013,172 8,321,191 18ms 33ms 151ms 47.9s 0 transport_latency_assumed tick_size_change c 3,264 3,090 5ms 10ms 136ms 341ms 0 transport_latency_assumed tick_size_change e 3,340 22 41ms 49ms 198ms 620ms 0 transport_latency_assumed tick_size_change f 3,296 not meas. 47ms 65ms 252ms 421ms 0 transport_latency_assumed tick_size_change h 3,340 228 18ms 27ms 129ms 916ms 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-22/05/2026-09-22T05.parquet sha256sum 2026-09-22T05.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.