Hour audit: 2026-10-05T17
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-05T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T17:00:00.000449755+00:00 · last event 2026-10-05T17:59:59.999762001+00:00
VOLUME 106,855,014 rows · 1,211,522,338 bytes (1.13 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 106,448,674 · h: 106,439,731 · o: 106,427,657 · m: 106,417,349 · n: 105,982,319 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 772,389 (0.72%) · h: 748,568 (0.70%) · o: 49,799,084 (46.60%) · m: 55,458,877 (51.90%) · n: 76,096 (0.07%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 106,855,014 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0e8c309987c295f9b0e7a8a327d39941971d2cb987160f79d83e70756bf5019f
the corpus checksum ledger names this file with the same digest
joined 106,855,983 to merged 106,855,014, minus 969 (minus 0.0009%)
boundary drops 969 · 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-05T18:58:59Z 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,403,630 120,589,199 0-35 1dbec8bead79ff046544ec5f34433cd4d96258e62af2a74a758e17a7636a48af book 165,736 17,999,386 36-36 d84347e24bd65389811942641753ec9debce933564b0b8b109130065b4529d77 last_trade_price 61,462 3,594,919 37-37 8b8c6f0dc38add0ad25a1073db690c8b34cd93ab57dfee06c635cf351d63221b market_resolved 1,332 202,179 38-38 106d6876ac3b84e28e93be6c91f6a69a7a1e37bfb4eb6d7a8eb557ea4be12ac7 new_market 6,065 555,263 39-39 5dcc108060a68d33ac66d0f94f4fdee8532037d5160be4b08d389db2e0310787 price_change 97,213,349 1,067,236,315 40-410 29c83406ea62f9bdec6b51e21f29b5edcc102b0fb89667e8639e11ff5f54d6b4 tick_size_change 3,440 127,740 411-411 0474c5794ab88ace3002107be99edf91ed4e616ca210e8e18b2433d010353b18 EVENT MIX count share price_change 97,213,349 90.98% best_bid_ask 9,403,630 8.80% book 165,736 0.16% last_trade_price 61,462 0.06% new_market 6,065 <0.01% tick_size_change 3,440 <0.01% market_resolved 1,332 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,403,707 9,403,630 77 686 FULL book 165,736 165,736 0 14,387 FULL last_trade_price 61,462 61,462 0 24 FULL market_resolved 1,332 1,332 0 9 FULL new_market 6,065 6,065 0 0 FULL price_change 97,214,241 97,213,349 892 2,051 FULL tick_size_change 3,440 3,440 0 9 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,382,044 59,756 18ms 34ms 615ms 1.0min 0 transport_latency_assumed best_bid_ask i 9,374,448 65,044 21ms 33ms 188ms 11.9s 0 transport_latency_assumed best_bid_ask m 9,358,014 4,939,914 5ms 15ms 162ms 8.9s 0 transport_latency_assumed best_bid_ask n 9,380,675 4,885 45ms 77ms 457ms 25.0s 0 transport_latency_assumed best_bid_ask o 9,371,734 4,334,031 5ms 15ms 196ms 23.5s 0 transport_latency_assumed book h 135,697 8,749 25ms 1.1s 8.3h 110.3d 0 book_staleness book i 134,696 7,575 26ms 983ms 6.2h 110.3d 0 book_staleness book m 135,603 70,184 8ms 210ms 7.8h 110.3d 0 book_staleness book n 135,698 12,105 58ms 7.4s 1.4d 128.8d 0 book_staleness book o 136,038 67,123 8ms 279ms 7.8h 110.2d 0 book_staleness last_trade_price h 61,022 451 21ms 135ms 1.1s 58.9s 0 transport_latency_assumed last_trade_price i 61,257 401 25ms 153ms 4.5s 11.9s 0 transport_latency_assumed last_trade_price m 61,372 31,111 6ms 26ms 243ms 2.7s 0 transport_latency_assumed last_trade_price n 58,550 40 55ms 1.1s 9.0s 23.7s 0 transport_latency_assumed last_trade_price o 61,300 29,459 6ms 26ms 261ms 7.3s 0 transport_latency_assumed market_resolved h 1,262 33 20ms 88ms 47.8s 2.1min 0 transport_latency_assumed market_resolved i 1,261 120 23ms 219ms 54.9s 2.5min 0 transport_latency_assumed market_resolved m 1,263 670 6ms 37ms 52.0s 1.6min 0 transport_latency_assumed market_resolved n 1,260 1 46ms 212ms 47.7s 1.9min 0 transport_latency_assumed market_resolved o 1,259 508 6ms 33ms 49.9s 2.4min 0 transport_latency_assumed new_market h 3,585 898 220ms 2.0min 3.3min 3.9min 0 transport_latency_assumed new_market i 3,585 1,115 160ms 2.1min 3.4min 3.9min 0 transport_latency_assumed new_market m 3,585 2,138 90ms 2.1min 3.3min 4.0min 0 transport_latency_assumed new_market n 3,585 503 290ms 1.9min 3.3min 4.0min 0 transport_latency_assumed new_market o 3,585 1,411 129ms 2.1min 3.4min 3.9min 0 transport_latency_assumed price_change h 96,852,689 678,669 19ms 45ms 722ms 1.0min 0 transport_latency_assumed price_change i 96,869,995 698,134 21ms 45ms 439ms 11.9s 0 transport_latency_assumed price_change m 96,854,084 50,413,059 5ms 17ms 173ms 9.5s 0 transport_latency_assumed price_change n 96,399,119 58,562 45ms 123ms 3.2s 25.2s 0 transport_latency_assumed price_change o 96,850,301 45,364,925 5ms 18ms 206ms 23.7s 0 transport_latency_assumed tick_size_change h 3,432 12 19ms 28ms 567ms 14.6s 0 transport_latency_assumed tick_size_change i 3,432 not meas. 21ms 30ms 84ms 318ms 0 transport_latency_assumed tick_size_change m 3,428 1,801 5ms 14ms 172ms 484ms 0 transport_latency_assumed tick_size_change n 3,432 not meas. 44ms 59ms 238ms 793ms 0 transport_latency_assumed tick_size_change o 3,440 1,627 5ms 11ms 42ms 321ms 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/17/2026-10-05T17.parquet sha256sum 2026-10-05T17.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.