Hour audit: 2026-10-06T10
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-06T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-06T10:00:00.000082236+00:00 · last event 2026-10-06T10:59:59.999774013+00:00
VOLUME 116,729,946 rows · 1,294,362,591 bytes (1.21 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 116,679,410 · o: 116,663,217 · h: 116,653,691 · i: 116,632,492 · n: 116,500,192 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 60,151,146 (51.53%) · o: 55,081,416 (47.19%) · h: 844,173 (0.72%) · i: 590,584 (0.51%) · n: 62,627 (0.05%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 a85e01c5c813b98da9fda2e367707b850401dfc2c0979fc0dd5c9c0aaf13a2d2
the corpus checksum ledger names this file with the same digest
joined 116,732,205 to merged 116,729,946, minus 2,259 (minus 0.0019%)
boundary drops 2,259 · 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-06T12:03:50Z 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,800,864 136,194,227 0-41 4d1dfdd94a4dbf4fc635906f5bb8df5675334f811694cac90e50fb625eed8e90 book 134,637 14,322,638 42-42 cf135b82ea33e6657dcab48acba1358a66173a339c300ec28b458a69964d54dc last_trade_price 52,533 2,991,609 43-43 21f118086cb6dedf7378cd7ed635c23e3075bcf84dd645116ff4c474bac70dad market_resolved 913 146,140 44-44 d44a736727542ac6d351a166301cbf510904d500127254fd1027ba6f1553052d new_market 1,157 108,595 45-45 77370ecb16bcb0a5704566dd780fe13ad4d01266978ee7ba4662eef1ce21826d price_change 105,736,198 1,139,135,266 46-449 3ed4e99fc280fd6d58171be63c259fc09db457b0357939d0bdbb2134004e0059 tick_size_change 3,644 131,572 450-450 22049a2caa51f4d5ce0ed6abe2cb8967ef7b1241308cbbd4acb8013bdd21d29f EVENT MIX count share price_change 105,736,198 90.58% best_bid_ask 10,800,864 9.25% book 134,637 0.12% last_trade_price 52,533 0.05% tick_size_change 3,644 <0.01% new_market 1,157 <0.01% market_resolved 913 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,801,098 10,800,864 234 83 FULL book 134,641 134,637 4 10,803 FULL last_trade_price 52,534 52,533 1 1 FULL market_resolved 913 913 0 0 FULL new_market 1,157 1,157 0 0 FULL price_change 105,738,218 105,736,198 2,020 117 FULL tick_size_change 3,644 3,644 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,799,618 71,488 18ms 29ms 269ms 1.3min 0 transport_latency_assumed best_bid_ask i 10,799,361 52,132 21ms 31ms 165ms 4.3s 0 transport_latency_assumed best_bid_ask m 10,800,243 5,602,094 5ms 13ms 106ms 6.8s 0 transport_latency_assumed best_bid_ask n 10,798,256 4,303 43ms 57ms 296ms 17.0s 0 transport_latency_assumed best_bid_ask o 10,800,054 5,070,847 5ms 14ms 114ms 14.7s 0 transport_latency_assumed book h 116,487 10,425 25ms 1.2s 1.9d 129.5d 0 book_staleness book i 108,669 3,587 26ms 329ms 1.6h 111.0d 0 book_staleness book m 107,872 55,423 7ms 34ms 2.1min 110.9d 0 book_staleness book n 116,806 11,346 50ms 6.5s 2.5d 111.0d 0 book_staleness book o 108,902 53,856 7ms 38ms 1.4h 110.9d 0 book_staleness last_trade_price h 52,395 367 21ms 131ms 926ms 17.5s 0 transport_latency_assumed last_trade_price i 52,245 232 26ms 223ms 1.1s 3.8s 0 transport_latency_assumed last_trade_price m 52,432 26,805 6ms 24ms 200ms 1.4s 0 transport_latency_assumed last_trade_price n 51,923 21 50ms 1.1s 6.0s 17.0s 0 transport_latency_assumed last_trade_price o 52,352 25,108 6ms 23ms 191ms 1.7s 0 transport_latency_assumed market_resolved h 869 3 20ms 54ms 50.4s 59.0s 0 transport_latency_assumed market_resolved i 869 74 23ms 116ms 54.3s 57.3s 0 transport_latency_assumed market_resolved m 869 429 6ms 19ms 55.9s 55.9s 0 transport_latency_assumed market_resolved n 869 2 45ms 116ms 48.4s 58.0s 0 transport_latency_assumed market_resolved o 869 405 6ms 19ms 57.2s 57.2s 0 transport_latency_assumed new_market h 698 80 228ms 36.2s 40.7s 1.6min 0 transport_latency_assumed new_market i 698 179 139ms 17.3s 39.9s 1.7min 0 transport_latency_assumed new_market m 698 378 71ms 36.5s 40.2s 1.7min 0 transport_latency_assumed new_market n 698 125 267ms 19.8s 40.4s 1.4min 0 transport_latency_assumed new_market o 698 395 75ms 34.8s 39.5s 1.5min 0 transport_latency_assumed price_change h 105,679,980 761,790 19ms 35ms 453ms 1.3min 0 transport_latency_assumed price_change i 105,667,006 534,360 22ms 39ms 427ms 4.3s 0 transport_latency_assumed price_change m 105,713,652 54,464,294 5ms 15ms 121ms 7.2s 0 transport_latency_assumed price_change n 105,527,996 46,826 44ms 80ms 1.8s 17.1s 0 transport_latency_assumed price_change o 105,696,698 49,928,928 5ms 15ms 131ms 17.7s 0 transport_latency_assumed tick_size_change h 3,644 20 19ms 29ms 62ms 168ms 0 transport_latency_assumed tick_size_change i 3,644 20 22ms 44ms 71ms 256ms 0 transport_latency_assumed tick_size_change m 3,644 1,723 5ms 14ms 70ms 234ms 0 transport_latency_assumed tick_size_change n 3,644 4 43ms 52ms 137ms 3.1s 0 transport_latency_assumed tick_size_change o 3,644 1,877 5ms 12ms 40ms 223ms 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-06/10/2026-10-06T10.parquet sha256sum 2026-10-06T10.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.