Hour audit: 2026-10-05T20
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-05T20 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-05T20:00:00.000056698+00:00 · last event 2026-10-05T20:59:59.999986221+00:00
VOLUME 112,479,204 rows · 1,265,804,078 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES himno — 5 machines contributed rows
captured o: 112,281,744 · m: 112,277,346 · i: 112,236,417 · h: 112,209,529 · n: 112,087,409 (each machine's own feed; these overlap and do not sum to the file)
supplied o: 56,470,949 (50.21%) · m: 54,365,648 (48.33%) · i: 812,403 (0.72%) · h: 716,091 (0.64%) · n: 114,113 (0.10%) (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 112,479,204 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 d869f57f59a87dd01a3b6ebf92de872ad948a4993a09c13ec7e3f81ce6c38b80
the corpus checksum ledger names this file with the same digest
joined 112,481,094 to merged 112,479,204, minus 1,890 (minus 0.0017%)
boundary drops 1,890 · 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-05T22:00:21Z 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,127,631 128,748,219 0-38 73a5302a1b0d8fbf1146e762f3572c651fd93b07f13e5df73d1605a1f2ee8c27 book 164,342 17,273,131 39-39 041fef32b63caf1937bee633ace7eeb6ff19d92a56a3ab4e694f24a8dd59ed56 last_trade_price 61,547 3,529,652 40-40 6193b93771533da5794eb8966155390ad7af77e201b7cb4bbc8aed263ff8dade market_resolved 1,348 197,002 41-41 884bb40f680b66524e0ec5527bf5000d1fc7c2b2b4e2a093a542ceaa8b7eea10 new_market 3,426 401,304 42-42 3df298c9e0eff6c02f366a329d94dc0f0d475938ba032c1a2f33e6de68728872 price_change 102,116,718 1,114,218,400 43-432 799632c7c60b1dad185963bffc105f4952a620811f74756629dec7e08879f534 tick_size_change 4,192 154,141 433-433 d32803272c33cfbd907562b78d6a54a1440e4fcfdf801e400b02a0c67dbb5f3d EVENT MIX count share price_change 102,116,718 90.79% best_bid_ask 10,127,631 9.00% book 164,342 0.15% last_trade_price 61,547 0.05% tick_size_change 4,192 <0.01% new_market 3,426 <0.01% market_resolved 1,348 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,127,787 10,127,631 156 144 FULL book 164,380 164,342 38 12,397 FULL last_trade_price 61,547 61,547 0 0 FULL market_resolved 1,348 1,348 0 0 FULL new_market 3,426 3,426 0 0 FULL price_change 102,118,414 102,116,718 1,696 1,630 FULL tick_size_change 4,192 4,192 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask h 10,123,185 59,568 19ms 34ms 735ms 2.3min 0 transport_latency_assumed best_bid_ask i 10,125,284 70,178 21ms 33ms 214ms 13.1s 0 transport_latency_assumed best_bid_ask m 10,125,380 4,882,033 5ms 15ms 146ms 10.9s 0 transport_latency_assumed best_bid_ask n 10,123,748 6,043 45ms 73ms 461ms 25.3s 0 transport_latency_assumed best_bid_ask o 10,125,246 5,109,809 5ms 15ms 180ms 13.8s 0 transport_latency_assumed book h 138,466 12,089 25ms 3.0s 11.5h 110.4d 0 book_staleness book i 132,336 5,617 25ms 676ms 3.1h 110.4d 0 book_staleness book m 133,432 67,938 7ms 101ms 3.5h 127.3d 0 book_staleness book n 137,138 11,720 54ms 5.2s 1.2d 110.4d 0 book_staleness book o 132,848 66,978 7ms 88ms 3.7h 110.4d 0 book_staleness last_trade_price h 61,149 373 21ms 158ms 1.3s 1.2min 0 transport_latency_assumed last_trade_price i 61,241 341 24ms 186ms 1.8s 13.1s 0 transport_latency_assumed last_trade_price m 61,337 29,631 6ms 22ms 239ms 2.2s 0 transport_latency_assumed last_trade_price n 60,761 86 52ms 913ms 6.0s 25.1s 0 transport_latency_assumed last_trade_price o 61,366 31,116 6ms 24ms 257ms 5.2s 0 transport_latency_assumed market_resolved h 1,227 48 22ms 39.2s 53.9s 59.4s 0 transport_latency_assumed market_resolved i 1,227 255 25ms 32.3s 46.4s 55.4s 0 transport_latency_assumed market_resolved m 1,227 496 6ms 39.4s 54.3s 54.5s 0 transport_latency_assumed market_resolved n 1,227 23 49ms 29.2s 55.3s 56.8s 0 transport_latency_assumed market_resolved o 1,227 526 6ms 36.1s 52.4s 52.5s 0 transport_latency_assumed new_market h 2,660 468 18.2s 34.4s 1.1min 1.6min 0 transport_latency_assumed new_market i 2,660 389 18.7s 33.2s 1.0min 1.6min 0 transport_latency_assumed new_market m 2,660 1,192 18.4s 33.4s 1.0min 1.6min 0 transport_latency_assumed new_market n 2,660 533 17.4s 34.0s 59.0s 1.4min 0 transport_latency_assumed new_market o 2,660 844 18.2s 32.9s 59.3s 1.6min 0 transport_latency_assumed price_change h 101,878,650 643,535 19ms 44ms 980ms 2.3min 0 transport_latency_assumed price_change i 101,909,477 735,595 21ms 43ms 570ms 13.1s 0 transport_latency_assumed price_change m 101,949,118 49,382,367 5ms 17ms 162ms 11.4s 0 transport_latency_assumed price_change n 101,757,683 95,708 45ms 101ms 2.2s 25.6s 0 transport_latency_assumed price_change o 101,954,205 51,259,513 5ms 17ms 194ms 15.3s 0 transport_latency_assumed tick_size_change h 4,192 10 19ms 36ms 721ms 17.5s 0 transport_latency_assumed tick_size_change i 4,192 28 21ms 33ms 339ms 617ms 0 transport_latency_assumed tick_size_change m 4,192 1,991 5ms 15ms 244ms 439ms 0 transport_latency_assumed tick_size_change n 4,192 not meas. 45ms 73ms 594ms 1.4s 0 transport_latency_assumed tick_size_change o 4,192 2,163 5ms 15ms 259ms 587ms 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-05/20/2026-10-05T20.parquet sha256sum 2026-10-05T20.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.