Hour audit: 2026-10-07T02
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-07T02 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-07T02:00:00.000034055+00:00 · last event 2026-10-07T02:59:59.999744145+00:00
VOLUME 126,271,235 rows · 1,425,222,883 bytes (1.33 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured m: 126,205,241 · o: 126,196,997 · h: 126,171,244 · n: 126,066,386 · i: 125,993,580 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 61,878,223 (49.00%) · o: 61,979,650 (49.08%) · h: 1,559,119 (1.23%) · n: 79,463 (0.06%) · i: 774,780 (0.61%) (rows of the merged file that came from it; these partition it)
2 product-machine pairs publish no supplied count; the figures above still sum to the file's 126,271,235 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 0b2a1f72f9c3f6040c9690904fa3b5dfabc42f426b4a12bdad3bbd6e03197713
the corpus checksum ledger names this file with the same digest
joined 126,272,446 to merged 126,271,235, minus 1,211 (minus 0.0010%)
boundary drops 1,211 · 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-07T04:06:52Z 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,797,100 149,421,262 0-45 fe3a8548fa785a722df7bf01184ec8f0979156951f45fd01090dae0d51ba3bfa book 162,783 17,907,578 46-46 fc26cc0939117824f1d618c913a70a988de7853c2409a50ba61d18245a117e5b last_trade_price 58,954 3,301,745 47-47 6e8055d463874621c556009672fce5b949d7c4b70d8c8cdf6a47fc7a5b57b034 market_resolved 1,148 168,592 48-48 4b268cae271833cb589879a1ab35f80bb811e1ea9a9cbf70a64b7a39caa1ccc8 new_market 620 64,073 49-49 b80639c3eb7b84564411ebfeb42b23e919325e9f1704d2b1b65fe0781e4086e4 price_change 114,248,134 1,252,828,080 50-485 48b5ecc52bf085caba59e74def2213feeeedeacc0d76b6c9413006f2f1eca295 tick_size_change 2,496 92,951 486-486 593941a30b6706f7b94381f36dec1d9fd0cedfb5858e2d24fe2948173dee6c69 EVENT MIX count share price_change 114,248,134 90.48% best_bid_ask 11,797,100 9.34% book 162,783 0.13% last_trade_price 58,954 0.05% tick_size_change 2,496 <0.01% market_resolved 1,148 <0.01% new_market 620 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 11,797,239 11,797,100 139 53 FULL book 162,810 162,783 27 18,058 FULL last_trade_price 58,957 58,954 3 0 FULL market_resolved 1,148 1,148 0 0 FULL new_market 620 620 0 0 FULL price_change 114,249,176 114,248,134 1,042 65 FULL tick_size_change 2,496 2,496 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 11,796,511 131,029 19ms 34ms 147ms 23.7s 0 transport_latency_assumed best_bid_ask i 11,790,916 65,935 22ms 37ms 156ms 4.8s 0 transport_latency_assumed best_bid_ask m 11,796,510 5,767,295 5ms 19ms 99ms 4.6s 0 transport_latency_assumed best_bid_ask n 11,795,219 4,331 44ms 62ms 195ms 8.4s 0 transport_latency_assumed best_bid_ask o 11,796,388 5,828,510 5ms 19ms 98ms 4.4s 0 transport_latency_assumed book h 127,399 10,366 23ms 153ms 1.2d 111.7d 0 book_staleness book i 122,676 6,088 26ms 194ms 2.2h 111.7d 0 book_staleness book m 132,238 68,289 8ms 3.3s 3.5d 111.7d 0 book_staleness book n 123,876 6,002 49ms 447ms 12.0h 111.7d 0 book_staleness book o 129,760 72,038 7ms 143ms 1.6d 111.7d 0 book_staleness last_trade_price h 58,872 907 21ms 61ms 281ms 8.1s 0 transport_latency_assumed last_trade_price i 58,438 406 25ms 102ms 845ms 4.0s 0 transport_latency_assumed last_trade_price m 58,829 27,139 7ms 28ms 150ms 1.6s 0 transport_latency_assumed last_trade_price n 58,623 34 48ms 188ms 2.3s 8.4s 0 transport_latency_assumed last_trade_price o 58,789 30,468 6ms 27ms 164ms 2.2s 0 transport_latency_assumed market_resolved h 1,047 4 21ms 29.7s 55.8s 55.9s 0 transport_latency_assumed market_resolved i 1,047 128 24ms 27.3s 54.8s 1.0min 0 transport_latency_assumed market_resolved m 1,047 494 6ms 27.2s 55.2s 1.0min 0 transport_latency_assumed market_resolved n 1,047 56 45ms 126ms 49.1s 49.2s 0 transport_latency_assumed market_resolved o 1,047 466 6ms 35.0s 53.8s 56.2s 0 transport_latency_assumed new_market h 401 81 110ms 27.1s 1.4min 1.8min 0 transport_latency_assumed new_market i 401 125 60ms 12.2s 1.2min 1.6min 0 transport_latency_assumed new_market m 401 194 42ms 10.1s 39.6s 1.3min 0 transport_latency_assumed new_market n 401 52 127ms 9.9s 37.0s 1.8min 0 transport_latency_assumed new_market o 401 168 43ms 8.8s 46.7s 1.3min 0 transport_latency_assumed price_change h 114,184,518 1,416,708 19ms 39ms 241ms 26.3s 0 transport_latency_assumed price_change i 114,017,606 702,098 22ms 44ms 407ms 5.0s 0 transport_latency_assumed price_change m 114,213,720 56,013,614 5ms 21ms 128ms 4.7s 0 transport_latency_assumed price_change n 114,084,724 68,988 45ms 75ms 969ms 8.4s 0 transport_latency_assumed price_change o 114,208,116 56,046,726 5ms 21ms 128ms 5.1s 0 transport_latency_assumed tick_size_change h 2,496 24 18ms 29ms 63ms 206ms 0 transport_latency_assumed tick_size_change i 2,496 not meas. 22ms 33ms 102ms 378ms 0 transport_latency_assumed tick_size_change m 2,496 1,198 5ms 15ms 73ms 144ms 0 transport_latency_assumed tick_size_change n 2,496 not meas. 44ms 58ms 101ms 219ms 0 transport_latency_assumed tick_size_change o 2,496 1,274 4ms 15ms 58ms 117ms 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-07/02/2026-10-07T02.parquet sha256sum 2026-10-07T02.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.