Hour audit: 2026-10-10T05
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.
1 finding
- the checksum ledger does not name this file. No line in the corpus checksum ledger names this file, so the documented verification step passes over it in silence rather than checking it. The manifest below still carries the digest.
1 check could not be evaluated for this hour, listed with the reason in the block below. A check we could not run is recorded as exactly that, and never counted as a pass.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-10T05 · corpus v3 · verdict AUDIT PENDING
COVERAGE not measured (this hour is not in the corpus attestation, so we have not looked at it)
VOLUME 123,274,222 rows · 1,414,209,540 bytes (1.32 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 122,795,614 · h: 122,787,706 · o: 122,744,217 · n: 122,689,171 · i: 122,623,278 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 60,569,803 (49.13%) · h: 745,646 (0.60%) · o: 61,066,104 (49.54%) · n: 233,307 (0.19%) · i: 659,362 (0.53%) (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 123,274,222 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 83fc61b4b44d8fc44a369313c12f0119e1e69c77c26a29015d673a348b60a344
no line in the corpus checksum ledger names this file
joined 123,275,774 to merged 123,274,222, minus 1,552 (minus 0.0013%)
boundary drops 1,552 · 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-10T12:27:09Z 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 6/8 pass, 1 finding, 1 not evaluated
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
FINDING the checksum ledger does not name this file
SKIPPED the hour's minutes have not been measured
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 12,311,920 150,899,344 0-46 8c4510af2b87304246359e63978f50107796fd4882f712d526d7aef7d5bc8b0c book 827,569 78,557,888 47-50 6655c8328220eee1eeba5271db9e516c7dee425ed4028271bdd26bf2a1940170 last_trade_price 39,718 2,392,463 51-51 3eff1847d3272e226f0a388a292945d2a4b42f06fbea7abff4be57023a8d3cf4 market_resolved 1,193 188,979 52-52 97fdcff1a2f39627af806c2dc330f7546c49ae315dcee899c9dad1c61d6e084d new_market 1,915 187,243 53-53 d4a5a513f4a062599b0448034152094b970f492a431d800394348b5e66b113cf price_change 110,088,051 1,180,438,597 54-473 2d31ddf667d52c40837717a2970aaf4e6978ed52392686fd05de5776c2b8a06e tick_size_change 3,856 142,292 474-474 c154f5b20edd5156cce8dd38aec4f0b6a9af1a325857b05fac5749a93c9b6238 EVENT MIX count share price_change 110,088,051 89.30% best_bid_ask 12,311,920 9.99% book 827,569 0.67% last_trade_price 39,718 0.03% tick_size_change 3,856 <0.01% new_market 1,915 <0.01% market_resolved 1,193 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 12,312,073 12,311,920 153 121 FULL book 827,735 827,569 166 255,693 FULL last_trade_price 39,719 39,718 1 0 FULL market_resolved 1,193 1,193 0 3 FULL new_market 1,915 1,915 0 0 FULL price_change 110,089,283 110,088,051 1,232 416 FULL tick_size_change 3,856 3,856 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 12,307,807 44,613 17ms 24ms 693ms 1.6min 0 transport_latency_assumed best_bid_ask i 12,310,178 55,693 21ms 39ms 137ms 3.4s 0 transport_latency_assumed best_bid_ask m 12,310,572 6,047,312 4ms 10ms 174ms 10.1s 0 transport_latency_assumed best_bid_ask n 12,309,448 10,635 43ms 53ms 275ms 6.2s 0 transport_latency_assumed best_bid_ask o 12,310,400 6,153,667 4ms 9ms 156ms 9.7s 0 transport_latency_assumed book h 418,510 223,196 6.7min 2.1d 48.7d 133.3d 0 book_staleness book i 217,474 75,750 1.2min 22.9h 45.5d 133.3d 0 book_staleness book m 378,774 213,606 5.7min 1.9d 48.7d 133.3d 0 book_staleness book n 317,565 125,489 3.9min 1.5d 48.7d 133.3d 0 book_staleness book o 344,473 189,528 4.8min 1.7d 48.7d 133.3d 0 book_staleness last_trade_price h 39,568 265 19ms 37ms 752ms 49.7s 0 transport_latency_assumed last_trade_price i 39,593 208 22ms 42ms 270ms 1.5s 0 transport_latency_assumed last_trade_price m 39,705 19,886 5ms 13ms 202ms 3.6s 0 transport_latency_assumed last_trade_price n 39,609 60 45ms 103ms 610ms 6.1s 0 transport_latency_assumed last_trade_price o 39,604 19,299 5ms 13ms 175ms 4.0s 0 transport_latency_assumed market_resolved h 1,169 7 20ms 88ms 49.6s 56.9s 0 transport_latency_assumed market_resolved i 1,167 94 23ms 105ms 51.2s 57.4s 0 transport_latency_assumed market_resolved m 1,167 542 5ms 37ms 52.2s 57.7s 0 transport_latency_assumed market_resolved n 1,167 not meas. 45ms 199ms 50.2s 57.2s 0 transport_latency_assumed market_resolved o 1,166 550 5ms 18ms 48.9s 56.2s 0 transport_latency_assumed new_market h 1,208 144 226ms 32.7s 1.2min 1.4min 0 transport_latency_assumed new_market i 1,208 364 149ms 25.0s 1.2min 1.7min 0 transport_latency_assumed new_market m 1,208 743 96ms 16.7s 57.9s 1.2min 0 transport_latency_assumed new_market n 1,208 229 252ms 40.6s 1.2min 1.4min 0 transport_latency_assumed new_market o 1,208 435 142ms 36.4s 1.3min 1.7min 0 transport_latency_assumed price_change h 110,015,588 477,408 17ms 26ms 835ms 1.8min 0 transport_latency_assumed price_change i 110,049,802 527,202 21ms 40ms 243ms 3.7s 0 transport_latency_assumed price_change m 110,060,332 54,286,002 4ms 10ms 221ms 34.2s 0 transport_latency_assumed price_change n 110,016,318 96,886 44ms 59ms 495ms 7.6s 0 transport_latency_assumed price_change o 110,043,510 54,700,553 4ms 10ms 203ms 9.8s 0 transport_latency_assumed tick_size_change h 3,856 13 17ms 25ms 525ms 28.5s 0 transport_latency_assumed tick_size_change i 3,856 51 21ms 40ms 208ms 444ms 0 transport_latency_assumed tick_size_change m 3,856 1,712 4ms 11ms 311ms 2.6s 0 transport_latency_assumed tick_size_change n 3,856 8 43ms 53ms 302ms 531ms 0 transport_latency_assumed tick_size_change o 3,856 2,072 4ms 9ms 197ms 902ms 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-10/05/2026-10-10T05.parquet sha256sum 2026-10-10T05.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.