Hour audit: 2026-10-05T22
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-05T22 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T22:00:00.000422302+00:00 · last event 2026-10-05T22:59:59.999760794+00:00
VOLUME 108,845,370 rows · 1,199,920,751 bytes (1.12 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 108,663,628 · m: 108,638,655 · h: 108,614,090 · i: 108,589,564 · n: 106,639,966 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 52,719,314 (48.44%) · m: 54,675,704 (50.23%) · h: 697,073 (0.64%) · i: 671,912 (0.62%) · n: 81,367 (0.07%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 ac4ac15fc17dd4ef753820d7aaa271cfe4180c94e5d57e243c917cf0ba5b3238
the corpus checksum ledger names this file with the same digest
joined 108,846,596 to merged 108,845,370, minus 1,226 (minus 0.0011%)
boundary drops 1,226 · 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-05T23:59: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,781,600 121,611,697 0-37 f44c721ce4996d61a5b812c220b1e5d13b700fcb5b5bde667eec372a8cea0057 book 238,498 23,413,086 38-38 9cc5b46d2941a11b82a240ca1bf18268d4bdcc32cffa906e69ac07454b95cc9e last_trade_price 58,051 3,309,630 39-39 34714d9202a8affc27c15ef947bf05e21dd1fdd1afa20971fe11de6ad8d94661 market_resolved 2,490 374,311 40-40 d2b5a65c69583ad03ca4e23894b3982957bac339cd02f25cf84bc2cc3eb15bcb new_market 4,376 435,953 41-41 95bb7ccf9dd7c92b0859d751079ddd62fafaa2fb9df71306189357fa7ad4d2e2 price_change 98,757,279 1,049,420,780 42-418 5af1b35bbef296e60cbb65f0eae6469812bc5b5da8cc841c063ff1ddab1e6128 tick_size_change 3,076 114,162 419-419 39e44b55e43130d855d951e63c68095a5c08066f04b382d464484266bf7bc06c EVENT MIX count share price_change 98,757,279 90.73% best_bid_ask 9,781,600 8.99% book 238,498 0.22% last_trade_price 58,051 0.05% new_market 4,376 <0.01% tick_size_change 3,076 <0.01% market_resolved 2,490 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,781,706 9,781,600 106 87 FULL book 238,510 238,498 12 45,639 FULL last_trade_price 58,051 58,051 0 1 FULL market_resolved 2,490 2,490 0 2 FULL new_market 4,376 4,376 0 0 FULL price_change 98,758,387 98,757,279 1,108 1,360 FULL tick_size_change 3,076 3,076 0 10 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 9,780,518 53,138 19ms 31ms 384ms 1.6min 0 transport_latency_assumed best_bid_ask i 9,779,832 56,689 21ms 31ms 143ms 14.2s 0 transport_latency_assumed best_bid_ask m 9,780,978 4,955,023 4ms 13ms 96ms 5.2s 0 transport_latency_assumed best_bid_ask n 9,722,156 3,391 44ms 70ms 410ms 24.3s 0 transport_latency_assumed best_bid_ask o 9,780,952 4,713,359 4ms 14ms 115ms 5.9s 0 transport_latency_assumed book h 127,105 7,409 23ms 549ms 9.7h 110.5d 0 book_staleness book i 158,335 37,819 36ms 1.8h 28.5d 129.0d 0 book_staleness book m 153,855 90,751 8ms 1.1h 26.6d 129.0d 0 book_staleness book n 138,280 25,117 71ms 20.6min 8.4d 129.0d 0 book_staleness book o 142,642 77,402 8ms 5.1min 13.2d 129.0d 0 book_staleness last_trade_price h 57,914 625 21ms 113ms 804ms 30.2s 0 transport_latency_assumed last_trade_price i 57,796 232 26ms 264ms 2.5s 14.1s 0 transport_latency_assumed last_trade_price m 57,971 28,297 6ms 23ms 220ms 1.6s 0 transport_latency_assumed last_trade_price n 53,586 29 51ms 1.6s 8.1s 21.8s 0 transport_latency_assumed last_trade_price o 57,965 28,868 6ms 26ms 194ms 1.3s 0 transport_latency_assumed market_resolved h 2,317 95 21ms 89ms 45.1s 56.6s 0 transport_latency_assumed market_resolved i 2,317 317 23ms 20.7s 52.6s 54.4s 0 transport_latency_assumed market_resolved m 2,318 1,048 6ms 18.0s 47.6s 59.6s 0 transport_latency_assumed market_resolved n 2,316 9 46ms 251ms 48.3s 49.0s 0 transport_latency_assumed market_resolved o 2,318 1,021 6ms 23.9s 53.5s 53.7s 0 transport_latency_assumed new_market h 2,884 370 232ms 1.8min 2.4min 2.9min 0 transport_latency_assumed new_market i 2,884 657 128ms 1.7min 2.4min 2.9min 0 transport_latency_assumed new_market m 2,884 1,558 95ms 1.7min 2.4min 2.9min 0 transport_latency_assumed new_market n 2,884 509 228ms 1.7min 2.4min 2.8min 0 transport_latency_assumed new_market o 2,884 1,282 105ms 1.7min 2.4min 2.9min 0 transport_latency_assumed price_change h 98,640,276 635,412 19ms 39ms 570ms 1.6min 0 transport_latency_assumed price_change i 98,585,324 576,170 21ms 41ms 535ms 14.2s 0 transport_latency_assumed price_change m 98,637,573 49,597,515 5ms 15ms 113ms 5.5s 0 transport_latency_assumed price_change n 96,717,708 52,300 45ms 94ms 2.9s 24.4s 0 transport_latency_assumed price_change o 98,673,791 47,895,882 5ms 16ms 132ms 6.1s 0 transport_latency_assumed tick_size_change h 3,076 24 19ms 79ms 1.5s 16.3s 0 transport_latency_assumed tick_size_change i 3,076 28 21ms 66ms 499ms 997ms 0 transport_latency_assumed tick_size_change m 3,076 1,512 5ms 29ms 393ms 704ms 0 transport_latency_assumed tick_size_change n 3,036 12 45ms 174ms 1.1s 13.4s 0 transport_latency_assumed tick_size_change o 3,076 1,500 5ms 22ms 421ms 937ms 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/22/2026-10-05T22.parquet sha256sum 2026-10-05T22.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.