Hour audit: 2026-10-04T04
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-04T04 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T04:00:00.000823568+00:00 · last event 2026-10-04T04:59:59.999995533+00:00
VOLUME 103,763,684 rows · 1,088,417,701 bytes (1.01 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 103,679,488 · i: 103,669,586 · k: 103,663,164 · h: 103,600,683 · g: 103,278,849 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 99,188,868 (95.59%) · i: 541,755 (0.52%) · k: 3,137,301 (3.02%) · h: 857,756 (0.83%) · g: 38,004 (0.04%) (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 103,763,684 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f842e97a4760ec4fb73a006f0b1259aa1902ee0cf20953bbb3648bbbb9df863a
the corpus checksum ledger names this file with the same digest
joined 103,765,627 to merged 103,763,684, minus 1,943 (minus 0.0019%)
boundary drops 1,943 · 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-04T06:47:01Z as ghikm
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,964,917 115,670,023 0-38 f5a791cda0dd8e1e0dff11dd3418045abe94651978a8cd9e19617af287aca400 book 167,797 16,522,085 39-39 cd96cb18d677a16c653838e70331187aed116941673df6dc5ff3cfb8f61adac2 last_trade_price 43,880 2,556,815 40-40 2b96df90c70706d477e307a1f7e4f208ed59a449bc5a2682e7bd5749d99097f8 market_resolved 1,470 229,038 41-41 bc5f9a367294b19e7fa1e2d194cf84598a1a436c8af58b6c6298caab79fdf03f new_market 4,244 448,843 42-42 af8dbeebe6dcf7c6e5f6cad47657234a51a35636224ed3b9b9545f340270d65d price_change 93,576,060 951,611,381 43-399 3b5bd24df413f0d59bca0ff0227e05b11ef2e2020244239591118991344ddd6d tick_size_change 5,316 195,029 400-400 a9c846c5bfb93dc943f86d3019b85006de8b447a1eeb39547db9119d53f18035 EVENT MIX count share price_change 93,576,060 90.18% best_bid_ask 9,964,917 9.60% book 167,797 0.16% last_trade_price 43,880 0.04% tick_size_change 5,316 <0.01% new_market 4,244 <0.01% market_resolved 1,470 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,965,137 9,964,917 220 309 FULL book 167,801 167,797 4 31,368 FULL last_trade_price 43,881 43,880 1 1 FULL market_resolved 1,470 1,470 0 0 FULL new_market 4,244 4,244 0 0 FULL price_change 93,577,778 93,576,060 1,718 255 FULL tick_size_change 5,316 5,316 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,957,144 2,166 77ms 130ms 1.2s 32.7s 0 transport_latency_assumed best_bid_ask h 9,954,595 77,729 18ms 28ms 2.0s 2.2min 0 transport_latency_assumed best_bid_ask i 9,962,626 48,670 21ms 29ms 432ms 51.1s 0 transport_latency_assumed best_bid_ask k 9,962,072 295,715 13ms 26ms 659ms 1.2min 0 transport_latency_assumed best_bid_ask m 9,963,441 9,540,637 4ms 10ms 168ms 11.2s 0 transport_latency_assumed book g 106,448 15,856 86ms 3.2min 13.9d 108.7d 0 book_staleness book h 123,074 29,640 25ms 3.6h 26.7d 127.3d 0 book_staleness book i 103,392 11,280 23ms 6.2s 2.1d 108.8d 0 book_staleness book k 111,622 20,780 18ms 15.7min 17.2d 108.8d 0 book_staleness book m 97,690 90,241 6ms 244ms 7.8h 108.7d 0 book_staleness last_trade_price g 42,822 14 83ms 317ms 11.2s 31.9s 0 transport_latency_assumed last_trade_price h 43,821 442 20ms 46ms 2.2s 2.0min 0 transport_latency_assumed last_trade_price i 43,869 264 22ms 44ms 619ms 6.8s 0 transport_latency_assumed last_trade_price k 43,867 1,591 14ms 38ms 936ms 48.2s 0 transport_latency_assumed last_trade_price m 43,866 41,569 5ms 13ms 244ms 4.1s 0 transport_latency_assumed market_resolved g 1,420 not meas. 81ms 919ms 52.9s 1.0min 0 transport_latency_assumed market_resolved h 1,420 15 20ms 480ms 54.7s 59.7s 0 transport_latency_assumed market_resolved i 1,420 18 22ms 210ms 48.3s 53.2s 0 transport_latency_assumed market_resolved k 1,420 68 15ms 388ms 49.8s 57.4s 0 transport_latency_assumed market_resolved m 1,420 1,369 5ms 14.2s 46.6s 46.7s 0 transport_latency_assumed new_market g 3,103 954 17.6s 52.0s 1.0min 1.2min 0 transport_latency_assumed new_market h 3,103 504 16.3s 52.3s 1.0min 1.7min 0 transport_latency_assumed new_market i 3,103 601 16.3s 52.3s 59.8s 1.1min 0 transport_latency_assumed new_market k 3,103 639 16.4s 52.1s 1.0min 1.3min 0 transport_latency_assumed new_market m 3,103 1,546 16.0s 52.1s 1.0min 1.6min 0 transport_latency_assumed price_change g 93,162,596 19,014 77ms 172ms 2.7s 33.7s 0 transport_latency_assumed price_change h 93,469,354 749,404 18ms 32ms 2.4s 2.2min 0 transport_latency_assumed price_change i 93,549,860 480,904 21ms 32ms 505ms 53.3s 0 transport_latency_assumed price_change k 93,535,764 2,818,381 13ms 28ms 701ms 1.2min 0 transport_latency_assumed price_change m 93,564,652 89,508,357 5ms 10ms 179ms 11.7s 0 transport_latency_assumed tick_size_change g 5,316 not meas. 77ms 155ms 995ms 10.7s 0 transport_latency_assumed tick_size_change h 5,316 22 18ms 26ms 1.5s 58.9s 0 transport_latency_assumed tick_size_change i 5,316 18 21ms 28ms 476ms 1.0s 0 transport_latency_assumed tick_size_change k 5,316 127 13ms 28ms 591ms 4.9s 0 transport_latency_assumed tick_size_change m 5,316 5,149 4ms 10ms 122ms 286ms 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-04/04/2026-10-04T04.parquet sha256sum 2026-10-04T04.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.