Hour audit: 2026-10-06T20
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 checksum ledger does not name this file. No line in the corpus checksum ledger names this file, so the documented verification step passes over it in silence rather than checking it. The manifest below still carries the digest.
The report
POLYMARKET ORDERBOOK ARCHIVE — HOUR AUDIT
hour 2026-10-06T20 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-06T20:00:00.000012172+00:00 · last event 2026-10-06T20:59:59.999772913+00:00
VOLUME 110,131,261 rows · 1,274,441,877 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 109,705,339 · h: 109,699,724 · m: 109,659,133 · n: 109,559,995 · i: 109,486,688 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 52,813,732 (47.96%) · h: 835,724 (0.76%) · m: 55,862,129 (50.72%) · n: 165,496 (0.15%) · i: 454,180 (0.41%) (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 110,131,261 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 489aa2ed424aa7c6908aaa7d07faef00246988772149b6d7cffb6fa459b8531f
no line in the corpus checksum ledger names this file
joined 110,133,038 to merged 110,131,261, minus 1,777 (minus 0.0016%)
boundary drops 1,777 · 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-06T22:01:37Z 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
FINDING the checksum ledger does not name 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 10,807,992 135,043,827 0-41 fdc11fc9cc608a8ad8b8e29a6873d2b478d646353681da55f6220cae8b4f8510 book 679,065 59,530,042 42-44 511dd783e2a7d320d5ced6a4570fcf7eef0132385cdd8696b043b3be3a0f21f6 last_trade_price 62,724 3,570,088 45-45 80e4d0f1db0108b1cdeb6738cdac2c7b1a26934c332bbfec51e250e0fc260c7a market_resolved 1,363 202,994 46-46 a7a44612a22885ce9d48022f123e2c7952f61371ab2575897caddf4b944c6b3c new_market 1,185 127,349 47-47 e8cba4d89b3a7c2da83e0e18c746a88a34bb2811c33530bcd6cf79b8392fc7d7 price_change 98,573,492 1,074,513,893 48-424 6e7301d01e783b4d7aedfed3a9ddf1112cb892a7515d9a20d16b1a92f67861ae tick_size_change 5,440 195,313 425-425 2b463bce78129b6b0c2c05d9e624e85370651d6e481e912cb02d4ba390d7fd96 EVENT MIX count share price_change 98,573,492 89.51% best_bid_ask 10,807,992 9.81% book 679,065 0.62% last_trade_price 62,724 0.06% tick_size_change 5,440 <0.01% market_resolved 1,363 <0.01% new_market 1,185 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,808,129 10,807,992 137 80 FULL book 679,381 679,065 316 193,673 FULL last_trade_price 62,724 62,724 0 0 FULL market_resolved 1,363 1,363 0 0 FULL new_market 1,185 1,185 0 0 FULL price_change 98,574,816 98,573,492 1,324 62 FULL tick_size_change 5,440 5,440 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,806,280 65,336 18ms 28ms 221ms 58.9s 0 transport_latency_assumed best_bid_ask i 10,805,558 45,396 21ms 31ms 170ms 6.8s 0 transport_latency_assumed best_bid_ask m 10,805,969 5,504,993 5ms 13ms 82ms 7.3s 0 transport_latency_assumed best_bid_ask n 10,804,317 2,619 45ms 58ms 282ms 22.8s 0 transport_latency_assumed best_bid_ask o 10,806,572 5,189,648 5ms 14ms 101ms 25.9s 0 transport_latency_assumed book h 295,979 141,276 36.7s 16.3h 41.2d 129.9d 0 book_staleness book i 149,036 17,158 29ms 6.4min 10.4d 129.9d 0 book_staleness book m 293,119 193,705 32.8s 17.9h 42.1d 129.9d 0 book_staleness book n 301,448 139,567 43.5s 18.8h 42.1d 129.9d 0 book_staleness book o 290,392 187,359 29.8s 19.1h 42.1d 129.9d 0 book_staleness last_trade_price h 62,610 410 20ms 123ms 915ms 50.1s 0 transport_latency_assumed last_trade_price i 62,301 211 26ms 334ms 2.4s 5.8s 0 transport_latency_assumed last_trade_price m 62,506 31,932 6ms 23ms 206ms 2.6s 0 transport_latency_assumed last_trade_price n 62,143 20 51ms 752ms 10.0s 22.8s 0 transport_latency_assumed last_trade_price o 62,616 30,151 6ms 24ms 236ms 5.6s 0 transport_latency_assumed market_resolved h 1,248 22 20ms 113ms 47.9s 57.6s 0 transport_latency_assumed market_resolved i 1,248 177 23ms 26.2s 51.4s 1.1min 0 transport_latency_assumed market_resolved m 1,248 553 6ms 27.0s 50.1s 1.1min 0 transport_latency_assumed market_resolved n 1,248 55 46ms 127ms 48.7s 56.5s 0 transport_latency_assumed market_resolved o 1,248 556 6ms 24.3s 55.3s 56.1s 0 transport_latency_assumed new_market h 781 132 200ms 15.1s 22.2s 1.3min 0 transport_latency_assumed new_market i 781 272 117ms 16.4s 23.8s 1.6min 0 transport_latency_assumed new_market m 781 423 69ms 14.9s 24.4s 1.5min 0 transport_latency_assumed new_market n 781 79 269ms 15.2s 19.7s 23.6s 0 transport_latency_assumed new_market o 781 279 89ms 15.1s 18.2s 1.7min 0 transport_latency_assumed price_change h 98,527,386 628,448 18ms 33ms 419ms 58.9s 0 transport_latency_assumed price_change i 98,462,324 390,936 21ms 42ms 856ms 8.2s 0 transport_latency_assumed price_change m 98,490,070 50,127,848 5ms 14ms 97ms 7.4s 0 transport_latency_assumed price_change n 98,384,618 23,156 45ms 78ms 1.8s 22.8s 0 transport_latency_assumed price_change o 98,538,290 47,403,104 5ms 15ms 115ms 28.8s 0 transport_latency_assumed tick_size_change h 5,440 100 18ms 34ms 233ms 4.6s 0 transport_latency_assumed tick_size_change i 5,440 30 21ms 37ms 155ms 1.7s 0 transport_latency_assumed tick_size_change m 5,440 2,675 5ms 18ms 132ms 389ms 0 transport_latency_assumed tick_size_change n 5,440 not meas. 45ms 68ms 209ms 7.6s 0 transport_latency_assumed tick_size_change o 5,440 2,635 5ms 17ms 93ms 289ms 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/20/2026-10-06T20.parquet sha256sum 2026-10-06T20.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.