Hour audit: 2026-10-06T14
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-06T14 · corpus v3 · verdict AUDIT PASS* (1 finding)
COVERAGE minutes present 60/60 · first event 2026-10-06T14:00:00.000019810+00:00 · last event 2026-10-06T14:59:59.999926507+00:00
VOLUME 121,077,120 rows · 1,391,262,470 bytes (1.30 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 121,000,846 · o: 120,983,803 · h: 120,955,397 · i: 120,928,957 · n: 120,495,947 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 61,532,732 (50.82%) · o: 57,432,026 (47.43%) · h: 1,111,301 (0.92%) · i: 943,207 (0.78%) · n: 57,854 (0.05%) (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 121,077,120 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 fb1bd89dde232d98d5564c28c54f1e43728ef60381fd37e50c6dbde98b2651b3
no line in the corpus checksum ledger names this file
joined 121,087,894 to merged 121,077,120, minus 10,774 (minus 0.0089%)
boundary drops 10,774 · 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-06T16:07:38Z 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,795,090 141,634,745 0-41 1edd45103c5681fab903e9a191cf94cdddbaca0f87d2e283303087c9e112d8ed book 159,858 17,779,940 42-42 7607c219a4bb3bf0d147056098cf26ae983a009a1a4146940203f6bfdca50281 last_trade_price 60,009 3,508,141 43-43 258345bab26d4d4fbc296d6bdeab3d40de4def78c2319479d205afd09ef80137 market_resolved 1,095 172,030 44-44 869a748ac651ba8def5484c2282cdfd49c66ddd6df5598892bc8f4c4c84b1a98 new_market 2,344 283,541 45-45 ff00675f157c9144806046a33d305feaf00f4a1c4edd184a7c9a45048305366b price_change 110,054,960 1,226,365,639 46-465 3a709b45ee3121da1b99b37fea7d8b8fa59216966de699c0c5ab477430f19e4b tick_size_change 3,764 138,521 466-466 7e9e58b7c96795a454d2181cea493d85ff97c754d93714ed68db5fe7f6138190 EVENT MIX count share price_change 110,054,960 90.90% best_bid_ask 10,795,090 8.92% book 159,858 0.13% last_trade_price 60,009 0.05% tick_size_change 3,764 <0.01% new_market 2,344 <0.01% market_resolved 1,095 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,796,122 10,795,090 1,032 82 FULL book 159,906 159,858 48 14,745 FULL last_trade_price 60,015 60,009 6 13 FULL market_resolved 1,095 1,095 0 0 FULL new_market 2,344 2,344 0 0 FULL price_change 110,064,644 110,054,960 9,684 129 FULL tick_size_change 3,768 3,764 4 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,791,768 93,714 20ms 39ms 660ms 2.1min 0 transport_latency_assumed best_bid_ask i 10,792,458 82,389 22ms 38ms 230ms 9.8s 0 transport_latency_assumed best_bid_ask m 10,794,340 5,504,414 6ms 19ms 143ms 7.6s 0 transport_latency_assumed best_bid_ask n 10,787,858 3,222 45ms 71ms 475ms 36.3s 0 transport_latency_assumed best_bid_ask o 10,794,520 5,111,351 6ms 20ms 163ms 9.3s 0 transport_latency_assumed book h 139,833 17,155 29ms 47.7s 4.8d 111.2d 0 book_staleness book i 127,118 5,700 28ms 918ms 1.7h 111.2d 0 book_staleness book m 125,606 64,291 8ms 50ms 6.1min 111.1d 0 book_staleness book n 133,043 12,800 59ms 10.5s 1.5d 111.1d 0 book_staleness book o 125,716 59,912 8ms 56ms 8.8min 50.8d 0 book_staleness last_trade_price h 59,796 558 23ms 236ms 2.1s 1.4min 0 transport_latency_assumed last_trade_price i 59,815 423 28ms 336ms 2.6s 8.8s 0 transport_latency_assumed last_trade_price m 59,866 30,403 7ms 29ms 201ms 1.3s 0 transport_latency_assumed last_trade_price n 58,382 37 56ms 1.7s 10.9s 36.4s 0 transport_latency_assumed last_trade_price o 59,923 28,588 7ms 31ms 234ms 4.1s 0 transport_latency_assumed market_resolved h 1,071 2 22ms 18.7s 49.6s 54.7s 0 transport_latency_assumed market_resolved i 1,071 139 24ms 13.5s 54.6s 55.7s 0 transport_latency_assumed market_resolved m 1,071 522 7ms 15.5s 50.9s 58.2s 0 transport_latency_assumed market_resolved n 1,071 10 47ms 437ms 55.8s 57.1s 0 transport_latency_assumed market_resolved o 1,071 422 7ms 21.7s 53.4s 57.3s 0 transport_latency_assumed new_market h 1,903 350 20.0s 55.2s 1.1min 70.5d 0 transport_latency_assumed new_market i 1,903 572 20.1s 51.6s 1.1min 70.5d 0 transport_latency_assumed new_market m 1,903 606 19.8s 51.8s 1.1min 70.5d 0 transport_latency_assumed new_market n 1,903 355 20.4s 54.0s 1.2min 70.5d 0 transport_latency_assumed new_market o 1,903 461 19.9s 53.7s 1.1min 70.5d 0 transport_latency_assumed price_change h 109,957,258 999,506 20ms 54ms 1.1s 2.1min 0 transport_latency_assumed price_change i 109,942,828 853,972 22ms 54ms 872ms 10.2s 0 transport_latency_assumed price_change m 110,014,296 55,930,610 6ms 22ms 162ms 7.6s 0 transport_latency_assumed price_change n 109,509,926 41,430 46ms 123ms 3.7s 37.1s 0 transport_latency_assumed price_change o 109,996,906 52,229,442 6ms 22ms 178ms 11.1s 0 transport_latency_assumed tick_size_change h 3,768 16 19ms 32ms 82ms 27.7s 0 transport_latency_assumed tick_size_change i 3,764 12 22ms 33ms 70ms 106ms 0 transport_latency_assumed tick_size_change m 3,764 1,886 5ms 18ms 79ms 222ms 0 transport_latency_assumed tick_size_change n 3,764 not meas. 45ms 55ms 100ms 303ms 0 transport_latency_assumed tick_size_change o 3,764 1,850 6ms 14ms 52ms 254ms 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/14/2026-10-06T14.parquet sha256sum 2026-10-06T14.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.