Hour audit: 2026-10-06T03
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-06T03 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-06T03:00:00.000175155+00:00 · last event 2026-10-06T03:59:59.999978362+00:00
VOLUME 113,212,840 rows · 1,280,280,576 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 112,824,714 · h: 112,686,050 · o: 112,632,557 · m: 112,535,780 · n: 111,913,900 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,151,879 (1.02%) · h: 835,931 (0.74%) · o: 56,463,235 (49.87%) · m: 54,690,360 (48.31%) · n: 71,435 (0.06%) (rows of the merged file that came from it; these partition it)
1 product-machine pair publish no supplied count; the figures above still sum to the file's 113,212,840 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 733f76f2c41cc0eed6555c3c9372c5bf840c0f6fefa8b97309b938c5962911bb
the corpus checksum ledger names this file with the same digest
joined 113,214,466 to merged 113,212,840, minus 1,626 (minus 0.0014%)
boundary drops 1,626 · 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-06T05:00:28Z 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 11,036,324 138,665,467 0-42 c270f10a7c43a6a6f7f83cd7d426ea641859f30d11165e58414bfe4a1819faf7 book 519,143 49,218,591 43-44 818a5c056a407980d96b94e0256284ffc9b537efca7db03c224c96f681fe4b19 last_trade_price 42,141 2,463,450 45-45 44017f73ca20ae24ff84990b4521f95f6999c9a1151477717f7165d9fa52756a market_resolved 1,509 234,944 46-46 48c17e320103b5140939f4428cba59650b1746fa92a127b03457f30ef8e84b84 new_market 2,421 224,230 47-47 d63675e8fc6eed78011a8cf616eb488bbd56d03795486594c492b8e0b6b5cb61 price_change 101,606,726 1,088,016,878 48-435 aa3a4ea7747e960fe9ebc44ad99b46b185241413b17909bc25bb7a81c4b89f8a tick_size_change 4,576 166,633 436-436 40a8dbdf0584168d1bf1cf9c619825f0f053ecda6103cd6b0f889fa8b523b602 EVENT MIX count share price_change 101,606,726 89.75% best_bid_ask 11,036,324 9.75% book 519,143 0.46% last_trade_price 42,141 0.04% tick_size_change 4,576 <0.01% new_market 2,421 <0.01% market_resolved 1,509 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,036,468 11,036,324 144 173 FULL book 519,489 519,143 346 175,105 FULL last_trade_price 42,141 42,141 0 0 FULL market_resolved 1,509 1,509 0 12 FULL new_market 2,421 2,421 0 0 FULL price_change 101,607,862 101,606,726 1,136 1,208 FULL tick_size_change 4,576 4,576 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,032,304 61,682 19ms 33ms 645ms 1.5min 0 transport_latency_assumed best_bid_ask i 11,024,816 65,405 21ms 30ms 132ms 4.5s 0 transport_latency_assumed best_bid_ask m 11,033,800 5,402,713 4ms 13ms 101ms 8.1s 0 transport_latency_assumed best_bid_ask n 11,015,114 4,904 44ms 60ms 255ms 21.8s 0 transport_latency_assumed best_bid_ask o 11,035,116 5,501,620 4ms 13ms 104ms 8.2s 0 transport_latency_assumed book h 114,842 19,321 28ms 2.7h 27.4d 129.2d 0 book_staleness book i 475,098 384,807 12.6min 1.5d 44.6d 129.2d 0 book_staleness book m 102,297 56,228 7ms 6.1min 7.6d 110.7d 0 book_staleness book n 97,380 11,409 47ms 13.1s 18.3h 129.2d 0 book_staleness book o 97,760 47,378 7ms 21.9s 1.6d 110.7d 0 book_staleness last_trade_price h 42,032 437 21ms 80ms 928ms 50.1s 0 transport_latency_assumed last_trade_price i 41,471 345 23ms 78ms 1.2s 4.5s 0 transport_latency_assumed last_trade_price m 41,930 21,394 6ms 25ms 216ms 1.5s 0 transport_latency_assumed last_trade_price n 40,950 45 46ms 175ms 6.3s 21.6s 0 transport_latency_assumed last_trade_price o 42,059 19,920 6ms 23ms 190ms 4.0s 0 transport_latency_assumed market_resolved h 1,461 16 21ms 66ms 42.4s 58.6s 0 transport_latency_assumed market_resolved i 1,471 107 22ms 61ms 46.1s 56.0s 0 transport_latency_assumed market_resolved m 1,471 634 5ms 24ms 53.7s 58.2s 0 transport_latency_assumed market_resolved n 1,459 not meas. 45ms 104ms 42.2s 42.4s 0 transport_latency_assumed market_resolved o 1,461 752 5ms 17ms 30.3s 47.4s 0 transport_latency_assumed new_market h 1,452 220 215ms 29.3s 48.5s 1.7min 0 transport_latency_assumed new_market i 1,452 375 106ms 31.4s 47.5s 1.5min 0 transport_latency_assumed new_market m 1,452 904 65ms 32.5s 42.9s 1.7min 0 transport_latency_assumed new_market n 1,452 125 203ms 31.3s 45.8s 1.4min 0 transport_latency_assumed new_market o 1,452 797 93ms 34.0s 48.3s 1.3min 0 transport_latency_assumed price_change h 101,489,383 754,187 20ms 40ms 732ms 1.5min 0 transport_latency_assumed price_change i 101,275,830 700,780 21ms 35ms 285ms 4.5s 0 transport_latency_assumed price_change m 101,350,254 49,206,362 5ms 15ms 121ms 10.0s 0 transport_latency_assumed price_change n 100,752,969 54,944 44ms 74ms 769ms 21.8s 0 transport_latency_assumed price_change o 101,450,133 50,890,453 4ms 16ms 122ms 8.3s 0 transport_latency_assumed tick_size_change h 4,576 68 19ms 34ms 535ms 2.7s 0 transport_latency_assumed tick_size_change i 4,576 60 21ms 39ms 254ms 4.0s 0 transport_latency_assumed tick_size_change m 4,576 2,125 4ms 18ms 101ms 255ms 0 transport_latency_assumed tick_size_change n 4,576 8 44ms 66ms 257ms 453ms 0 transport_latency_assumed tick_size_change o 4,576 2,315 4ms 19ms 267ms 1.1s 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/03/2026-10-06T03.parquet sha256sum 2026-10-06T03.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.