Hour audit: 2026-10-06T18
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.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-06T18 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-06T18:00:00.000529643+00:00 · last event 2026-10-06T18:59:59.999995398+00:00
VOLUME 112,919,834 rows · 1,355,791,014 bytes (1.26 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 111,854,656 · m: 111,802,268 · h: 111,689,674 · i: 111,413,537 · n: 106,489,366 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 55,876,364 (49.48%) · m: 53,209,248 (47.12%) · h: 1,094,420 (0.97%) · i: 2,081,866 (1.84%) · n: 657,936 (0.58%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 ec57f930cf93f8f4398ee597c30283ab96937b0839b9afd95765015d994b11ed
no line in the corpus checksum ledger names this file
joined 112,938,101 to merged 112,919,834, minus 18,267 (minus 0.0162%)
boundary drops 18,267 · 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-06T20:02:55Z 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 7/8 pass, 1 finding
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
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,738,460 138,686,086 0-40 ea64cc171691a9b6b3f26984782e694f3c329c839ad50eb065d7c8fef3f2561f book 1,702,456 103,753,506 41-47 dc1e9565f564b5a0da1b18cfad53ef465045fef00ad63ae79209b875bdb54387 last_trade_price 55,945 3,260,174 48-48 e37ca2f6ed9e6420c40aedcb75bcb3b54ed5b573ca8c4c257950805293a69629 market_resolved 1,239 189,955 49-49 4129576bdf5fe135a682003eb3ec69c909c5a796cd903c446eaa53291dfed671 new_market 5,986 733,996 50-50 2b8f40c7504ea174f03a11c7bbc14bf286800c9659b78b2d45fba58b7dacc3da price_change 100,412,168 1,107,745,369 51-434 f6f9c50eac3394aa71bc292285a370e7a8d52671109568839746afc8eb98084e tick_size_change 3,580 133,663 435-435 41fd8199ddbade76ffe66ebcca6813dd4ed30e129f378b3c5bd4a4abd2b13f44 EVENT MIX count share price_change 100,412,168 88.92% best_bid_ask 10,738,460 9.51% book 1,702,456 1.51% last_trade_price 55,945 0.05% new_market 5,986 <0.01% tick_size_change 3,580 <0.01% market_resolved 1,239 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,739,747 10,738,460 1,287 894 FULL book 1,706,906 1,702,456 4,450 145,421 FULL last_trade_price 55,949 55,945 4 111 FULL market_resolved 1,239 1,239 0 6 FULL new_market 5,986 5,986 0 0 FULL price_change 100,424,694 100,412,168 12,526 671 FULL tick_size_change 3,580 3,580 0 58 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,729,634 73,145 20ms 89ms 1.9s 2.5min 0 transport_latency_assumed best_bid_ask i 10,731,197 178,602 21ms 37ms 266ms 25.4s 0 transport_latency_assumed best_bid_ask m 10,734,013 5,121,081 5ms 18ms 250ms 8.4s 0 transport_latency_assumed best_bid_ask n 10,252,503 9,239 45ms 102ms 596ms 27.3s 0 transport_latency_assumed best_bid_ask o 10,734,871 5,356,393 5ms 21ms 337ms 21.5s 0 transport_latency_assumed book h 710,669 293,255 7.4min 1.4d 45.2d 129.9d 0 book_staleness book i 498,919 196,127 4.3min 1.2d 45.2d 129.8d 0 book_staleness book m 683,289 342,581 7.2min 1.4d 45.2d 129.8d 0 book_staleness book n 945,830 512,929 9.6min 1.4d 45.2d 129.9d 0 book_staleness book o 695,389 357,564 7.4min 1.4d 45.2d 129.9d 0 book_staleness last_trade_price h 55,673 451 23ms 239ms 5.2s 1.9min 0 transport_latency_assumed last_trade_price i 55,315 702 25ms 179ms 8.0s 24.6s 0 transport_latency_assumed last_trade_price m 55,736 25,745 6ms 37ms 354ms 7.1s 0 transport_latency_assumed last_trade_price n 52,189 136 52ms 466ms 7.5s 26.4s 0 transport_latency_assumed last_trade_price o 55,826 28,911 6ms 42ms 501ms 8.4s 0 transport_latency_assumed market_resolved h 1,164 13 26ms 25.9s 45.0s 2.1min 0 transport_latency_assumed market_resolved i 1,166 154 24ms 1.7s 34.8s 1.4min 0 transport_latency_assumed market_resolved m 1,166 524 7ms 781ms 35.1s 38.2s 0 transport_latency_assumed market_resolved n 1,162 73 54ms 42.0s 4.5min 5.8min 0 transport_latency_assumed market_resolved o 1,166 475 7ms 785ms 41.2s 43.7s 0 transport_latency_assumed new_market h 5,162 1,207 1.4min 2.8min 3.5min 4.3min 0 transport_latency_assumed new_market i 5,162 921 1.4min 2.8min 3.5min 4.2min 0 transport_latency_assumed new_market m 5,162 1,331 1.4min 2.7min 3.5min 4.3min 0 transport_latency_assumed new_market n 5,162 693 1.4min 2.8min 3.6min 4.3min 0 transport_latency_assumed new_market o 5,162 1,834 1.4min 2.8min 3.5min 4.2min 0 transport_latency_assumed price_change h 100,183,796 726,332 20ms 118ms 4.0s 2.5min 0 transport_latency_assumed price_change i 100,118,202 1,705,256 21ms 52ms 879ms 25.5s 0 transport_latency_assumed price_change m 100,319,322 47,716,242 5ms 21ms 269ms 9.4s 0 transport_latency_assumed price_change n 95,229,160 134,862 45ms 166ms 2.2s 27.7s 0 transport_latency_assumed price_change o 100,358,666 50,129,476 5ms 25ms 377ms 23.6s 0 transport_latency_assumed tick_size_change h 3,576 17 20ms 206ms 7.2s 1.2min 0 transport_latency_assumed tick_size_change i 3,576 104 22ms 56ms 340ms 996ms 0 transport_latency_assumed tick_size_change m 3,580 1,744 5ms 31ms 318ms 3.2s 0 transport_latency_assumed tick_size_change n 3,360 4 46ms 204ms 686ms 4.8s 0 transport_latency_assumed tick_size_change o 3,576 1,711 5ms 34ms 268ms 9.0s 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/18/2026-10-06T18.parquet sha256sum 2026-10-06T18.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.