Hour audit: 2026-10-03T10
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-03T10 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-03T10:00:00.000040352+00:00 · last event 2026-10-03T10:59:59.999974856+00:00
VOLUME 109,414,668 rows · 1,134,682,671 bytes (1.06 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured k: 109,322,652 · m: 109,318,013 · i: 109,297,777 · h: 109,291,986 · g: 109,245,753 (each machine's own feed; these overlap and do not sum to the file)
supplied k: 4,260,668 (3.89%) · m: 103,667,210 (94.75%) · i: 508,003 (0.46%) · h: 936,325 (0.86%) · g: 42,462 (0.04%) (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 109,414,668 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 ee2427cd923bb74326b152678a9a12a22c4101417edf1a93673f3f7874c0c344
the corpus checksum ledger names this file with the same digest
joined 109,416,824 to merged 109,414,668, minus 2,156 (minus 0.0020%)
boundary drops 2,156 · 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-03T12:45:17Z as ghikm
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 9,134,445 110,063,581 0-34 975cf220a3f8d21c5f660ea71e40242bfdba64e16f4d9134d02818d655e41c8a book 151,499 15,368,745 35-35 0a83f71a22c5739b4f98a1f6e8c6fd6535618f3f8455693b83f9d09b63e181b3 last_trade_price 58,856 3,304,768 36-36 bfed825e77864381b3076ed6cf98e75f383ca5eb3e9ad409051dc4d3ff9aaa46 market_resolved 690 103,071 37-37 0596f7198488b6993bc6b9710b99d975f16d6d99e20a2112ded7426563f8dba6 new_market 1,046 100,082 38-38 72290aa740e0ccee7653035e07c2d2cc4ecf48dcd839eb5237f7fc1d17626983 price_change 100,064,552 1,004,364,142 39-420 0054fc9a6eb06a0cf3f0f836a959ebf7b495de0f106ae25088a751ba1f406b7f tick_size_change 3,580 131,063 421-421 09a26ec7a08e95604c35ab6126d4cc527ceda12353de8c8d00810b621cf01175 EVENT MIX count share price_change 100,064,552 91.45% best_bid_ask 9,134,445 8.35% book 151,499 0.14% last_trade_price 58,856 0.05% tick_size_change 3,580 <0.01% new_market 1,046 <0.01% market_resolved 690 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,134,625 9,134,445 180 82 FULL book 151,501 151,499 2 13,894 FULL last_trade_price 58,856 58,856 0 0 FULL market_resolved 690 690 0 0 FULL new_market 1,046 1,046 0 0 FULL price_change 100,066,526 100,064,552 1,974 305 FULL tick_size_change 3,580 3,580 0 3 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,131,782 649 78ms 97ms 376ms 11.6s 0 transport_latency_assumed best_bid_ask h 9,133,528 68,998 18ms 25ms 150ms 49.9s 0 transport_latency_assumed best_bid_ask i 9,133,616 36,563 21ms 27ms 97ms 6.8s 0 transport_latency_assumed best_bid_ask k 9,133,245 337,555 13ms 22ms 112ms 1.0min 0 transport_latency_assumed best_bid_ask m 9,133,375 8,690,680 4ms 10ms 59ms 5.4s 0 transport_latency_assumed book g 137,964 19,775 91ms 2.6min 6.9d 126.5d 0 book_staleness book h 123,409 6,403 22ms 70ms 12.6h 108.0d 0 book_staleness book i 121,492 3,468 23ms 65ms 1.2h 126.5d 0 book_staleness book k 122,690 9,422 17ms 51ms 5.9h 108.0d 0 book_staleness book m 120,992 112,431 6ms 20ms 28.5min 41.8d 0 book_staleness last_trade_price g 58,573 11 86ms 542ms 5.0s 11.6s 0 transport_latency_assumed last_trade_price h 58,755 799 19ms 39ms 415ms 44.1s 0 transport_latency_assumed last_trade_price i 58,731 428 22ms 46ms 396ms 3.5s 0 transport_latency_assumed last_trade_price k 58,713 3,205 15ms 31ms 284ms 9.3s 0 transport_latency_assumed last_trade_price m 58,718 54,413 6ms 15ms 144ms 2.5s 0 transport_latency_assumed market_resolved g 635 not meas. 81ms 348ms 57.7s 57.7s 0 transport_latency_assumed market_resolved h 635 5 20ms 135ms 57.1s 58.5s 0 transport_latency_assumed market_resolved i 635 2 22ms 43.8s 52.6s 52.7s 0 transport_latency_assumed market_resolved k 635 69 15ms 35ms 55.0s 55.9s 0 transport_latency_assumed market_resolved m 635 614 5ms 42.0s 50.4s 51.7s 0 transport_latency_assumed new_market g 641 77 286ms 17.7s 30.8s 1.5min 0 transport_latency_assumed new_market h 641 214 188ms 18.0s 1.2min 1.6min 0 transport_latency_assumed new_market i 641 194 96ms 18.5s 53.8s 1.6min 0 transport_latency_assumed new_market k 641 153 166ms 24.3s 40.9s 1.5min 0 transport_latency_assumed new_market m 641 408 61ms 17.5s 30.2s 1.5min 0 transport_latency_assumed price_change g 99,912,590 21,950 78ms 107ms 949ms 11.7s 0 transport_latency_assumed price_change h 99,971,438 859,888 18ms 27ms 274ms 51.5s 0 transport_latency_assumed price_change i 99,979,082 467,344 21ms 29ms 246ms 7.1s 0 transport_latency_assumed price_change k 100,003,148 3,910,118 13ms 23ms 199ms 1.2min 0 transport_latency_assumed price_change m 100,000,072 94,805,252 5ms 11ms 84ms 5.6s 0 transport_latency_assumed tick_size_change g 3,568 not meas. 77ms 91ms 150ms 685ms 0 transport_latency_assumed tick_size_change h 3,580 18 18ms 25ms 67ms 140ms 0 transport_latency_assumed tick_size_change i 3,580 4 20ms 27ms 49ms 259ms 0 transport_latency_assumed tick_size_change k 3,580 146 13ms 20ms 56ms 92ms 0 transport_latency_assumed tick_size_change m 3,580 3,412 4ms 9ms 45ms 126ms 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-03/10/2026-10-03T10.parquet sha256sum 2026-10-03T10.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.