Hour audit: 2026-10-05T10
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-05T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T10:00:00.000010566+00:00 · last event 2026-10-05T10:59:59.999943010+00:00
VOLUME 107,513,680 rows · 1,203,303,938 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 107,369,069 · h: 107,365,651 · m: 107,363,869 · n: 107,342,521 · i: 107,338,516 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 52,377,823 (48.72%) · h: 451,961 (0.42%) · m: 54,126,232 (50.34%) · n: 54,969 (0.05%) · i: 502,695 (0.47%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 1048df596fb208aafd69f5c863b086b1017f18503c18b86b3c22fedecbd98edf
the corpus checksum ledger names this file with the same digest
joined 107,514,995 to merged 107,513,680, minus 1,315 (minus 0.0012%)
boundary drops 1,315 · 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-05T12:00:29Z 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 9,779,502 122,072,463 0-37 f28764cc8db14a8141c8af76bd31d0710d4e43b80630d85ac95590ae50e1e1dd book 159,055 16,840,314 38-38 a8c08c9a9d35b5cef65e8babc74d43bf8c8d6d16833802a9eec831a987a5d878 last_trade_price 52,215 2,991,858 39-39 446c0b3f68594edfdcfe3c27d5f35546e87af674533eb749ed7b07ef4fccd85b market_resolved 945 151,604 40-40 4b3f5454a16f382e47d7b7a561ef07cfee049fd944955ac4b8e813513d05bb0e new_market 1,459 132,371 41-41 4c1c98c7cda92c400000fa76652e42116852e1a3125d081d0db7944b13483ef5 price_change 97,517,456 1,059,777,593 42-413 6f127c46381fe6ac45b77517c038c2e6e3443fb74e11a78a339942521ea12507 tick_size_change 3,048 111,372 414-414 ff48c5b5f56a086734c456f1fed156de813e685c5eb9b19174dc0ce17dcfaae6 EVENT MIX count share price_change 97,517,456 90.70% best_bid_ask 9,779,502 9.10% book 159,055 0.15% last_trade_price 52,215 0.05% tick_size_change 3,048 <0.01% new_market 1,459 <0.01% market_resolved 945 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,779,646 9,779,502 144 153 FULL book 159,059 159,055 4 21,290 FULL last_trade_price 52,216 52,215 1 0 FULL market_resolved 945 945 0 0 FULL new_market 1,459 1,459 0 0 FULL price_change 97,518,622 97,517,456 1,166 1,097 FULL tick_size_change 3,048 3,048 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,776,371 34,807 20ms 38ms 520ms 1.9min 0 transport_latency_assumed best_bid_ask i 9,778,186 42,841 21ms 29ms 130ms 2.8s 0 transport_latency_assumed best_bid_ask m 9,778,486 4,926,538 5ms 12ms 80ms 4.1s 0 transport_latency_assumed best_bid_ask n 9,777,320 3,618 43ms 60ms 244ms 19.4s 0 transport_latency_assumed best_bid_ask o 9,778,582 4,771,698 5ms 12ms 85ms 8.2s 0 transport_latency_assumed book h 138,564 33,156 38ms 55.2min 28.0d 128.5d 0 book_staleness book i 109,900 4,746 24ms 350ms 3.8h 110.0d 0 book_staleness book m 108,593 57,821 7ms 34ms 59.4min 110.0d 0 book_staleness book n 116,158 10,451 50ms 5.2s 1.8d 110.0d 0 book_staleness book o 109,394 52,881 7ms 40ms 2.3h 109.8d 0 book_staleness last_trade_price h 52,065 209 23ms 142ms 1.3s 47.0s 0 transport_latency_assumed last_trade_price i 52,123 202 23ms 173ms 1.3s 2.9s 0 transport_latency_assumed last_trade_price m 52,053 26,972 6ms 19ms 183ms 2.9s 0 transport_latency_assumed last_trade_price n 51,974 76 49ms 414ms 7.1s 19.4s 0 transport_latency_assumed last_trade_price o 52,138 24,756 6ms 21ms 207ms 1.2s 0 transport_latency_assumed market_resolved h 892 12 22ms 527ms 57.5s 57.6s 0 transport_latency_assumed market_resolved i 892 140 23ms 19.7s 54.6s 55.8s 0 transport_latency_assumed market_resolved m 892 407 6ms 19.6s 52.1s 55.6s 0 transport_latency_assumed market_resolved n 892 3 46ms 276ms 55.6s 55.7s 0 transport_latency_assumed market_resolved o 892 383 6ms 17.1s 52.6s 52.6s 0 transport_latency_assumed new_market h 845 190 227ms 25.9s 33.0s 1.6min 0 transport_latency_assumed new_market i 845 198 152ms 21.4s 43.3s 1.7min 0 transport_latency_assumed new_market m 845 536 61ms 18.4s 34.1s 1.7min 0 transport_latency_assumed new_market n 845 87 207ms 13.7s 36.0s 1.4min 0 transport_latency_assumed new_market o 845 448 76ms 17.6s 48.5s 1.5min 0 transport_latency_assumed price_change h 97,393,866 383,582 21ms 48ms 713ms 1.9min 0 transport_latency_assumed price_change i 97,393,522 454,556 21ms 35ms 388ms 2.9s 0 transport_latency_assumed price_change m 97,419,952 49,112,433 5ms 13ms 99ms 4.2s 0 transport_latency_assumed price_change n 97,392,284 40,730 44ms 76ms 1.4s 19.4s 0 transport_latency_assumed price_change o 97,424,170 47,526,155 5ms 14ms 104ms 8.7s 0 transport_latency_assumed tick_size_change h 3,048 5 20ms 38ms 371ms 8.8s 0 transport_latency_assumed tick_size_change i 3,048 12 21ms 49ms 139ms 295ms 0 transport_latency_assumed tick_size_change m 3,048 1,525 5ms 12ms 241ms 295ms 0 transport_latency_assumed tick_size_change n 3,048 4 43ms 53ms 283ms 673ms 0 transport_latency_assumed tick_size_change o 3,048 1,502 5ms 12ms 218ms 476ms 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-05/10/2026-10-05T10.parquet sha256sum 2026-10-05T10.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.