Hour audit: 2026-10-08T04
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 hour is short of its sixty minutes. 59 of the 60 minutes carry events; 1 do not.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-08T04 · corpus v3 · verdict AUDIT PARTIAL (1 finding)
COVERAGE minutes present 59/60 · first event 2026-10-08T04:00:00.000014912+00:00 · last event 2026-10-08T04:59:59.999962193+00:00
VOLUME 95,518,870 rows · 1,065,119,330 bytes (1015.78 MiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 95,401,180 · o: 95,389,990 · h: 95,378,086 · m: 95,372,015 · n: 95,328,823 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 919,427 (0.96%) · o: 45,149,733 (47.27%) · h: 920,911 (0.96%) · m: 48,431,172 (50.70%) · n: 97,627 (0.10%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 15423286e7913ac9ccabb885e8fc8145be6b26d720b1f4d75c45be7afd64ff4b
the corpus checksum ledger names this file with the same digest
joined 95,520,484 to merged 95,518,870, minus 1,614 (minus 0.0017%)
boundary drops 1,614 · 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-08T05:57: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 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
PASS the checksum ledger names this file
FINDING the hour is short of its sixty minutes
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,681,984 124,112,503 0-36 b65df7a64ff388d2f07cce6cc5bbd59c3da1edf9d0716f26e47de2238edf1959 book 197,821 20,393,943 37-37 c02e10c5fbdd0644757b80da2e39d20e66fb1f629056a1870fb240203825643f last_trade_price 43,155 2,479,974 38-38 67e94e958b05380f50ed5cd2277141df573ac47099f41f67fc54a0a0eca26158 market_resolved 3,018 459,025 39-39 62cd1d32c79770a693a99446f6c910e1054deb2d78730340ee22feba39924c2a new_market 2,190 206,075 40-40 ec8e98edb9ba2e425e33ef2c0a603d581f7e852a489f4e62436fdbab9c7e6f43 price_change 85,588,534 916,295,919 41-367 d841f801c3682afba18ab964bf5c186c1f87744f7ae1e12615b037e5883ea5db tick_size_change 2,168 81,429 368-368 c6a7d7ad54a37a3d74c8df3464e661c7eee8278c89541f4087b6b437d00567ae EVENT MIX count share price_change 85,588,534 89.60% best_bid_ask 9,681,984 10.14% book 197,821 0.21% last_trade_price 43,155 0.05% market_resolved 3,018 <0.01% new_market 2,190 <0.01% tick_size_change 2,168 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,682,172 9,681,984 188 83 FULL book 197,825 197,821 4 48,690 FULL last_trade_price 43,157 43,155 2 0 FULL market_resolved 3,018 3,018 0 0 FULL new_market 2,190 2,190 0 0 FULL price_change 85,589,954 85,588,534 1,420 139 FULL tick_size_change 2,168 2,168 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,677,981 69,907 18ms 34ms 1.2s 1.7min 0 transport_latency_assumed best_bid_ask i 9,681,023 78,501 21ms 31ms 265ms 4.7s 0 transport_latency_assumed best_bid_ask m 9,681,026 5,008,707 4ms 14ms 269ms 6.7s 0 transport_latency_assumed best_bid_ask n 9,680,330 6,573 43ms 62ms 547ms 7.2s 0 transport_latency_assumed best_bid_ask o 9,681,396 4,518,296 4ms 14ms 297ms 10.2s 0 transport_latency_assumed book h 137,190 48,588 36ms 29.8min 32.6d 131.3d 0 book_staleness book i 124,348 36,588 29ms 4.9min 30.7d 113.2d 0 book_staleness book m 98,874 55,050 7ms 5.6s 16.0h 112.8d 0 book_staleness book n 95,970 7,790 48ms 2.9s 54.9min 112.8d 0 book_staleness book o 97,982 49,805 7ms 3.2s 5.9h 112.7d 0 book_staleness last_trade_price h 43,117 554 19ms 64ms 845ms 28.3s 0 transport_latency_assumed last_trade_price i 43,075 341 24ms 65ms 350ms 1.7s 0 transport_latency_assumed last_trade_price m 43,045 22,144 6ms 22ms 194ms 1.8s 0 transport_latency_assumed last_trade_price n 42,949 34 48ms 376ms 3.8s 7.2s 0 transport_latency_assumed last_trade_price o 43,064 20,082 6ms 23ms 198ms 1.3s 0 transport_latency_assumed market_resolved h 2,834 157 20ms 2.1s 46.4s 58.5s 0 transport_latency_assumed market_resolved i 2,834 363 23ms 25.1s 49.9s 51.8s 0 transport_latency_assumed market_resolved m 2,834 1,465 5ms 25.9s 50.4s 51.7s 0 transport_latency_assumed market_resolved n 2,834 38 45ms 336ms 54.3s 56.0s 0 transport_latency_assumed market_resolved o 2,834 995 6ms 27.1s 52.1s 53.3s 0 transport_latency_assumed new_market h 1,326 243 319ms 18.8s 27.1s 1.7min 0 transport_latency_assumed new_market i 1,326 681 110ms 18.5s 31.5s 1.7min 0 transport_latency_assumed new_market m 1,326 517 102ms 18.3s 44.2s 1.5min 0 transport_latency_assumed new_market n 1,326 276 173ms 18.9s 26.0s 1.7min 0 transport_latency_assumed new_market o 1,326 473 121ms 17.8s 32.2s 1.5min 0 transport_latency_assumed price_change h 85,513,470 801,438 18ms 42ms 1.2s 1.7min 0 transport_latency_assumed price_change i 85,546,406 802,908 21ms 40ms 504ms 4.7s 0 transport_latency_assumed price_change m 85,542,742 43,342,248 5ms 18ms 364ms 8.3s 0 transport_latency_assumed price_change n 85,503,246 82,914 44ms 93ms 1.6s 14.4s 0 transport_latency_assumed price_change o 85,561,220 40,559,026 5ms 18ms 394ms 10.4s 0 transport_latency_assumed tick_size_change h 2,168 24 18ms 39ms 1.1s 4.0s 0 transport_latency_assumed tick_size_change i 2,168 45 21ms 32ms 178ms 289ms 0 transport_latency_assumed tick_size_change m 2,168 1,041 5ms 21ms 188ms 2.6s 0 transport_latency_assumed tick_size_change n 2,168 2 44ms 105ms 390ms 789ms 0 transport_latency_assumed tick_size_change o 2,168 1,056 5ms 14ms 177ms 802ms 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-08/04/2026-10-08T04.parquet sha256sum 2026-10-08T04.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.