Hour audit: 2026-10-04T18
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-04T18 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-04T18:00:00.000030474+00:00 · last event 2026-10-04T18:59:59.999958273+00:00
VOLUME 130,210,010 rows · 1,561,094,332 bytes (1.45 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured i: 128,635,800 · h: 128,577,678 · m: 128,523,237 · o: 123,700,300 · n: 123,537,330 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 1,104,401 (0.85%) · h: 1,550,140 (1.19%) · m: 64,527,071 (49.56%) · o: 62,594,267 (48.07%) · n: 434,131 (0.33%) (rows of the merged file that came from it; these partition it)
5 expected, all 5 contributed
INTEGRITY sha256 2a85d5bcc368cd28885273728d2006429389274e68358f1b03fb9e1aacf5e372
the corpus checksum ledger names this file with the same digest
joined 130,211,989 to merged 130,210,010, minus 1,979 (minus 0.0015%)
boundary drops 1,979 · 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-04T20:16:07Z 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,499,046 133,893,996 0-40 9550b7222bea7b671a37f2e1d9794909dff5e926dbe609cd888b19147ac03985 book 905,510 73,931,243 41-44 5b99279f9f0b9129e0b5594dfccda82f99e6913bff7fd11c58343a5f03a2dd27 last_trade_price 63,225 3,701,066 45-45 1adf33c4ea93fdfa34e78216f4c519afffb882fddea7ecf8ace0458903ecab20 market_resolved 2,875 382,929 46-46 514040f069c69fefd60bf8800f310d2bfbd6fa2bf41e5941e3fb0756def180a9 new_market 6,479 554,430 47-47 bd70e9ab87723dea4bff5b84ceff2fe65c62b0676d326fad2ad99fc94707f97f price_change 118,728,711 1,346,993,897 48-500 facfc8ceef403ad4b43ee12987578d457467983f2b7a866e2befb9546ae8a5ec tick_size_change 4,164 154,439 501-501 9e699726693383f66ef6576389e4f323791a46fb463a5cd9693a2b4da18ea9d6 EVENT MIX count share price_change 118,728,711 91.18% best_bid_ask 10,499,046 8.06% book 905,510 0.70% last_trade_price 63,225 0.05% new_market 6,479 <0.01% tick_size_change 4,164 <0.01% market_resolved 2,875 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,499,260 10,499,046 214 2,818 FULL book 905,534 905,510 24 233,610 FULL last_trade_price 63,228 63,225 3 252 FULL market_resolved 2,875 2,875 0 146 FULL new_market 6,479 6,479 0 0 FULL price_change 118,730,449 118,728,711 1,738 4,340 FULL tick_size_change 4,164 4,164 0 83 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,417,456 124,565 19ms 41ms 755ms 1.4min 0 transport_latency_assumed best_bid_ask i 10,453,781 90,255 20ms 40ms 334ms 30.0s 0 transport_latency_assumed best_bid_ask m 10,426,866 5,243,094 6ms 19ms 187ms 9.6s 0 transport_latency_assumed best_bid_ask n 9,997,668 16,351 48ms 90ms 496ms 24.8s 0 transport_latency_assumed best_bid_ask o 9,983,180 5,024,781 6ms 19ms 195ms 9.0s 0 transport_latency_assumed book h 138,595 6,393 25ms 631ms 6.0h 109.3d 0 book_staleness book i 132,653 3,580 25ms 417ms 45.3min 109.3d 0 book_staleness book m 138,812 67,727 9ms 176ms 6.0h 109.3d 0 book_staleness book n 664,291 234,754 9.2min 1.2d 43.2d 127.8d 0 book_staleness book o 662,395 593,056 8.0min 1.2d 43.2d 127.8d 0 book_staleness last_trade_price h 63,058 756 21ms 108ms 1.1s 53.0s 0 transport_latency_assumed last_trade_price i 61,539 424 23ms 125ms 1.2s 4.5s 0 transport_latency_assumed last_trade_price m 62,975 30,928 7ms 26ms 228ms 4.1s 0 transport_latency_assumed last_trade_price n 60,244 74 55ms 451ms 6.2s 24.6s 0 transport_latency_assumed last_trade_price o 59,801 31,043 7ms 24ms 250ms 6.4s 0 transport_latency_assumed market_resolved h 2,349 51 22ms 276ms 51.9s 2.4min 0 transport_latency_assumed market_resolved i 2,352 14 22ms 142ms 52.9s 56.1s 0 transport_latency_assumed market_resolved m 2,353 1,311 7ms 72ms 54.4s 2.1min 0 transport_latency_assumed market_resolved n 2,388 200 52ms 53.8s 9.4min 10.1min 0 transport_latency_assumed market_resolved o 2,386 1,299 8ms 59.0s 5.9min 7.9min 0 transport_latency_assumed new_market h 3,520 861 202ms 2.2min 3.6min 4.3min 0 transport_latency_assumed new_market i 3,520 675 168ms 2.2min 3.6min 4.2min 0 transport_latency_assumed new_market m 3,520 1,557 97ms 2.2min 3.6min 4.2min 0 transport_latency_assumed new_market n 3,598 797 181ms 2.3min 6.2min 6.5min 0 transport_latency_assumed new_market o 4,177 2,589 121ms 3.6min 6.5min 7.9min 0 transport_latency_assumed price_change h 117,948,560 1,417,480 20ms 49ms 901ms 1.4min 0 transport_latency_assumed price_change i 117,977,811 1,009,408 21ms 48ms 451ms 44.0s 0 transport_latency_assumed price_change m 117,884,571 59,180,414 6ms 20ms 196ms 10.2s 0 transport_latency_assumed price_change n 112,805,117 181,948 49ms 111ms 1.3s 25.1s 0 transport_latency_assumed price_change o 112,984,329 56,939,461 6ms 20ms 208ms 9.0s 0 transport_latency_assumed tick_size_change h 4,140 34 19ms 40ms 540ms 8.6s 0 transport_latency_assumed tick_size_change i 4,144 45 20ms 40ms 362ms 1.2s 0 transport_latency_assumed tick_size_change m 4,140 2,040 6ms 19ms 155ms 690ms 0 transport_latency_assumed tick_size_change n 4,024 7 48ms 81ms 484ms 917ms 0 transport_latency_assumed tick_size_change o 4,032 2,038 6ms 23ms 218ms 497ms 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/18/2026-10-04T18.parquet sha256sum 2026-10-04T18.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.