Hour audit: 2026-10-04T23
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-04T23 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T23:00:00.000012556+00:00 · last event 2026-10-04T23:59:59.999911656+00:00
VOLUME 125,801,803 rows · 1,420,802,055 bytes (1.32 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 125,728,941 · m: 125,676,356 · h: 125,656,484 · n: 125,494,891 · i: 125,140,281 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 61,073,481 (48.55%) · m: 62,503,832 (49.68%) · h: 1,399,192 (1.11%) · n: 82,408 (0.07%) · i: 742,890 (0.59%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 4cd509a0a0f8e1881435425fa051ea4adcca3213dcdde00f82d6528962af92fc
the corpus checksum ledger names this file with the same digest
joined 125,803,741 to merged 125,801,803, minus 1,938 (minus 0.0015%)
boundary drops 1,938 · 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-05T01:22:06Z 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 10,649,644 133,614,330 0-40 9c00964b3d63224505f4c9ad258fc543d27d025c7924a6760323bfde3a456f3d book 167,166 17,736,693 41-41 d0ad34e2c25b815aba2c17699186206d1123cb68e9edbbd3e1af615bfeca30d3 last_trade_price 62,233 3,553,051 42-42 525ed7cbaebba2d890862002dcdde1ba2ec948f76b2d77d4988a38fec5c1ee20 market_resolved 2,344 363,180 43-43 8732bd71ac05298e05af4a3f4175420fb05ecd5034255557892a3eaf60e01ffd new_market 1,914 192,254 44-44 250a2444534168be9c06ef07ddb2a70e17f45f80cb916ed6093f8deb23e07da8 price_change 114,912,130 1,263,676,247 45-483 ba2eb95f72b8e1dd50635cf6f81b648cedd0da88b6d32e3e6b80d755dd1fdf8f tick_size_change 6,372 233,317 484-484 35bb76e2ed8c040ad839f78197c69c4792a64250708780063ec227fa5893ec42 EVENT MIX count share price_change 114,912,130 91.34% best_bid_ask 10,649,644 8.47% book 167,166 0.13% last_trade_price 62,233 0.05% tick_size_change 6,372 <0.01% market_resolved 2,344 <0.01% new_market 1,914 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,649,786 10,649,644 142 201 FULL book 167,182 167,166 16 14,582 FULL last_trade_price 62,242 62,233 9 0 FULL market_resolved 2,357 2,344 13 13 FULL new_market 1,914 1,914 0 0 FULL price_change 114,913,888 114,912,130 1,758 1,474 FULL tick_size_change 6,372 6,372 0 2 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,646,773 104,621 18ms 33ms 248ms 1.0min 0 transport_latency_assumed best_bid_ask i 10,628,651 55,311 21ms 37ms 253ms 43.5s 0 transport_latency_assumed best_bid_ask m 10,648,472 5,358,327 5ms 18ms 113ms 8.7s 0 transport_latency_assumed best_bid_ask n 10,644,889 4,413 48ms 77ms 303ms 30.6s 0 transport_latency_assumed best_bid_ask o 10,648,580 5,126,972 5ms 17ms 105ms 7.7s 0 transport_latency_assumed book h 131,004 7,141 23ms 217ms 2.1h 109.5d 0 book_staleness book i 133,855 10,729 26ms 589ms 2.7h 109.5d 0 book_staleness book m 129,389 61,954 8ms 58ms 59.6min 63.5d 0 book_staleness book n 141,931 16,670 58ms 31.5s 4.1d 109.6d 0 book_staleness book o 133,867 70,672 8ms 84ms 11.4h 109.5d 0 book_staleness last_trade_price h 62,085 871 20ms 108ms 824ms 58.9s 0 transport_latency_assumed last_trade_price i 61,123 450 24ms 156ms 1.6s 11.5s 0 transport_latency_assumed last_trade_price m 62,147 29,964 6ms 32ms 237ms 8.7s 0 transport_latency_assumed last_trade_price n 61,595 28 55ms 531ms 5.6s 30.5s 0 transport_latency_assumed last_trade_price o 62,035 30,920 6ms 26ms 198ms 4.0s 0 transport_latency_assumed market_resolved h 2,237 13 20ms 13.1s 53.6s 58.7s 0 transport_latency_assumed market_resolved i 2,237 154 23ms 20.5s 51.3s 56.1s 0 transport_latency_assumed market_resolved m 2,237 1,112 7ms 20.6s 51.4s 56.0s 0 transport_latency_assumed market_resolved n 2,250 22 50ms 193ms 54.9s 56.7s 0 transport_latency_assumed market_resolved o 2,237 1,043 7ms 47ms 51.7s 58.3s 0 transport_latency_assumed new_market h 1,246 335 334ms 12.2min 16.2min 17.1min 0 transport_latency_assumed new_market i 1,246 223 258ms 12.0min 16.0min 17.3min 0 transport_latency_assumed new_market m 1,246 533 179ms 12.0min 16.0min 16.8min 0 transport_latency_assumed new_market n 1,246 224 287ms 12.0min 13.1min 17.3min 0 transport_latency_assumed new_market o 1,246 599 86ms 12.1min 16.2min 17.1min 0 transport_latency_assumed price_change h 114,806,767 1,286,135 19ms 40ms 377ms 1.5min 0 transport_latency_assumed price_change i 114,306,805 675,995 21ms 46ms 519ms 44.3s 0 transport_latency_assumed price_change m 114,826,493 57,048,661 5ms 21ms 140ms 12.4s 0 transport_latency_assumed price_change n 114,636,608 61,040 49ms 92ms 1.5s 30.6s 0 transport_latency_assumed price_change o 114,874,604 55,840,299 5ms 20ms 121ms 7.8s 0 transport_latency_assumed tick_size_change h 6,372 76 19ms 40ms 552ms 18.1s 0 transport_latency_assumed tick_size_change i 6,364 28 21ms 51ms 759ms 2.9s 0 transport_latency_assumed tick_size_change m 6,372 3,281 5ms 18ms 176ms 920ms 0 transport_latency_assumed tick_size_change n 6,372 11 49ms 96ms 396ms 662ms 0 transport_latency_assumed tick_size_change o 6,372 2,976 5ms 20ms 251ms 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-04/23/2026-10-04T23.parquet sha256sum 2026-10-04T23.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.