Hour audit: 2026-10-07T07
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-10-07T07 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T07:00:00.000131898+00:00 · last event 2026-10-07T07:59:59.999982261+00:00
VOLUME 102,477,587 rows · 1,141,286,688 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 102,313,581 · h: 102,298,972 · o: 102,296,351 · m: 102,252,098 · n: 102,226,823 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 561,285 (0.55%) · h: 588,081 (0.57%) · o: 51,870,464 (50.62%) · m: 49,414,453 (48.22%) · n: 43,304 (0.04%) (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 102,477,587 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0758df8297793698d199f32f469a6e8084bc929a0210c8560420f16d31983681
the corpus checksum ledger names this file with the same digest
joined 102,478,507 to merged 102,477,587, minus 920 (minus 0.0009%)
boundary drops 920 · 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-10-07T09:00:17Z as himno
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 status feed unobserved for this hour. Our incident register was last checked against the venue's feed at 2026-09-23T20:35Z, before this hour ended, so nothing has looked yet. This is a could-not-look and never an all-clear.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,079,780 125,661,599 0-38 1f6fd86c19087ddb227f6fe73a8f82c3ec6fbc623ae175e9c5b6d1785f1e6414 book 218,231 22,751,337 39-39 3c82fa29f484a2cc5c8b3ed0a010e69759912fd3f205fae76f9c20075748050a last_trade_price 43,244 2,530,020 40-40 4887a7a6bc01236f5ea00da8eeddc62e04914575c62754f670ae026c16ac8bec market_resolved 606 95,149 41-41 acb9f57ec3c99df258a3dc8dcb263fb311262ab29cbfef76cf14a99b5015d74e new_market 1,074 101,906 42-42 3e811ea34cd3d420cadcac55204e395b43c418b26e8e68831e6de95dc7ba6d08 price_change 92,132,476 988,895,150 43-394 99ef21acbd5896a104f0b5dc220963c41c30de44ddd290c370aac97766d9c0b3 tick_size_change 2,176 81,440 395-395 152967001c0279235103f24549d53c5ef5fa8703cf2f3c34fc13fb8b35f4b171 EVENT MIX count share price_change 92,132,476 89.91% best_bid_ask 10,079,780 9.84% book 218,231 0.21% last_trade_price 43,244 0.04% tick_size_change 2,176 <0.01% new_market 1,074 <0.01% market_resolved 606 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,079,874 10,079,780 94 59 FULL book 218,327 218,231 96 57,695 FULL last_trade_price 43,246 43,244 2 0 FULL market_resolved 606 606 0 6 FULL new_market 1,074 1,074 0 0 FULL price_change 92,133,204 92,132,476 728 166 FULL tick_size_change 2,176 2,176 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,077,871 49,016 18ms 31ms 254ms 47.1s 0 transport_latency_assumed best_bid_ask i 10,076,497 40,331 21ms 29ms 122ms 3.9s 0 transport_latency_assumed best_bid_ask m 10,078,404 4,867,221 4ms 12ms 81ms 14.0s 0 transport_latency_assumed best_bid_ask n 10,077,713 2,585 43ms 55ms 215ms 10.3s 0 transport_latency_assumed best_bid_ask o 10,078,561 5,120,627 4ms 12ms 83ms 31.3s 0 transport_latency_assumed book h 103,410 15,113 27ms 6.3min 16.6d 111.9d 0 book_staleness book i 183,463 96,515 6.7s 17.1h 37.7d 130.4d 0 book_staleness book m 97,322 47,369 7ms 3.4s 1.9d 111.9d 0 book_staleness book n 92,938 5,812 48ms 1.2s 21.8h 111.8d 0 book_staleness book o 93,907 53,422 7ms 101ms 1.1d 111.9d 0 book_staleness last_trade_price h 43,071 301 21ms 95ms 692ms 21.2s 0 transport_latency_assumed last_trade_price i 42,975 266 24ms 90ms 817ms 3.1s 0 transport_latency_assumed last_trade_price m 43,036 19,405 6ms 23ms 225ms 2.5s 0 transport_latency_assumed last_trade_price n 42,898 64 47ms 236ms 4.1s 10.3s 0 transport_latency_assumed last_trade_price o 43,063 23,208 6ms 22ms 204ms 3.0s 0 transport_latency_assumed market_resolved h 568 not meas. 22ms 97ms 53.5s 56.5s 0 transport_latency_assumed market_resolved i 568 50 23ms 321ms 54.6s 56.1s 0 transport_latency_assumed market_resolved m 568 251 5ms 31ms 55.9s 56.3s 0 transport_latency_assumed market_resolved n 574 18 45ms 128ms 32.5s 32.6s 0 transport_latency_assumed market_resolved o 568 287 5ms 13ms 54.8s 54.8s 0 transport_latency_assumed new_market h 650 145 191ms 21.4s 40.3s 1.3min 0 transport_latency_assumed new_market i 650 139 133ms 18.0s 53.0s 1.7min 0 transport_latency_assumed new_market m 650 410 51ms 18.5s 33.2s 1.6min 0 transport_latency_assumed new_market n 650 47 235ms 20.7s 35.0s 1.2min 0 transport_latency_assumed new_market o 650 333 91ms 25.4s 55.0s 1.7min 0 transport_latency_assumed price_change h 92,071,226 523,490 19ms 38ms 392ms 47.1s 0 transport_latency_assumed price_change i 92,007,252 423,964 22ms 35ms 310ms 4.0s 0 transport_latency_assumed price_change m 92,029,942 44,478,742 5ms 13ms 101ms 15.8s 0 transport_latency_assumed price_change n 92,009,874 34,778 43ms 71ms 812ms 10.3s 0 transport_latency_assumed price_change o 92,077,426 46,671,502 5ms 13ms 101ms 31.3s 0 transport_latency_assumed tick_size_change h 2,176 16 19ms 32ms 68ms 192ms 0 transport_latency_assumed tick_size_change i 2,176 20 22ms 36ms 66ms 379ms 0 transport_latency_assumed tick_size_change m 2,176 1,055 5ms 13ms 60ms 204ms 0 transport_latency_assumed tick_size_change n 2,176 not meas. 43ms 55ms 107ms 2.2s 0 transport_latency_assumed tick_size_change o 2,176 1,085 5ms 16ms 51ms 102ms 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-10-07/07/2026-10-07T07.parquet sha256sum 2026-10-07T07.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.