Hour audit: 2026-10-02T19
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-02T19 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T19:00:00.000297909+00:00 · last event 2026-10-02T19:59:59.999999303+00:00
VOLUME 120,185,124 rows · 1,377,590,699 bytes (1.28 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 119,622,827 · m: 119,554,379 · h: 119,231,482 · k: 113,615,431 · g: 111,778,171 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 2,203,836 (1.83%) · m: 101,244,097 (84.24%) · h: 4,340,255 (3.61%) · k: 11,857,717 (9.87%) · g: 539,219 (0.45%) (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 120,185,124 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 7c3e7959b64ad463a5bf742188fd5bb79f64cba96664350c0bfad41aee4b0ff8
the corpus checksum ledger names this file with the same digest
joined 120,187,743 to merged 120,185,124, minus 2,619 (minus 0.0022%)
boundary drops 2,619 · 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-02T21:47:37Z 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,913,003 122,498,137 0-37 b12faf7cede01c7abffb746015eb5736b64822b0f36366b26fc49f1480d51c2a book 708,873 68,967,159 38-40 cdb95c46519a8305e12553a89a0021e64f1957ad791331c523b0d1597a0b5f54 last_trade_price 65,690 3,812,826 41-41 012ce90c5b8dad97338adcc9ce45e90f75d05d768c1eff0fef00720d57d7fb73 market_resolved 923 144,657 42-42 870faa1e7f590072808b67a0aec09d1f6782f1ccba0a065e4b0c23b7428fc02f new_market 3,375 301,519 43-43 743e083db98da48b2fdfee45e5a678cace70e09d831224b5f9d5a2ece2e70dde price_change 109,489,120 1,180,346,250 44-461 767bfe70c846f3393c061f026f613daf3157bd727361d65555a89879b41578b9 tick_size_change 4,140 152,240 462-462 dca1e09f7ba173abae9b354aa7db8f07239131cb7e481d2a060ee1adcd087014 EVENT MIX count share price_change 109,489,120 91.10% best_bid_ask 9,913,003 8.25% book 708,873 0.59% last_trade_price 65,690 0.05% tick_size_change 4,140 <0.01% new_market 3,375 <0.01% market_resolved 923 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,913,228 9,913,003 225 1,929 FULL book 708,923 708,873 50 236,039 FULL last_trade_price 65,690 65,690 0 128 FULL market_resolved 923 923 0 48 FULL new_market 3,375 3,375 0 0 FULL price_change 109,491,464 109,489,120 2,344 1,525 FULL tick_size_change 4,140 4,140 0 48 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,357,101 3,364 82ms 171ms 1.5s 45.1s 0 transport_latency_assumed best_bid_ask h 9,903,576 341,365 20ms 55ms 618ms 1.4min 0 transport_latency_assumed best_bid_ask i 9,911,225 173,004 24ms 57ms 351ms 16.8s 0 transport_latency_assumed best_bid_ask k 9,387,496 902,176 14ms 44ms 324ms 33.7s 0 transport_latency_assumed best_bid_ask m 9,912,457 8,493,094 6ms 31ms 247ms 8.9s 0 transport_latency_assumed book g 616,643 494,971 14.4min 18.8h 41.2d 125.9d 0 book_staleness book h 135,531 6,406 28ms 386ms 44.5s 107.3d 0 book_staleness book i 187,011 28,232 61ms 3.3h 25.4d 125.9d 0 book_staleness book k 610,286 65,569 11.7min 18.3h 41.2d 125.9d 0 book_staleness book m 134,999 113,695 9ms 73ms 2.6s 9.3s 0 book_staleness last_trade_price g 56,631 33 101ms 3.2s 19.6s 44.2s 0 transport_latency_assumed last_trade_price h 65,165 2,418 23ms 255ms 2.4s 54.0s 0 transport_latency_assumed last_trade_price i 65,663 993 30ms 414ms 3.3s 7.9s 0 transport_latency_assumed last_trade_price k 61,686 6,728 17ms 103ms 556ms 9.2s 0 transport_latency_assumed last_trade_price m 65,673 55,518 7ms 52ms 392ms 3.0s 0 transport_latency_assumed market_resolved g 885 18 88ms 26.5s 6.2min 6.7min 0 transport_latency_assumed market_resolved h 903 22 21ms 486ms 44.6s 45.3s 0 transport_latency_assumed market_resolved i 903 9 27ms 452ms 35.3s 35.9s 0 transport_latency_assumed market_resolved k 871 47 17ms 22.4s 6.7min 7.2min 0 transport_latency_assumed market_resolved m 903 827 6ms 246ms 34.9s 35.1s 0 transport_latency_assumed new_market g 2,059 567 520ms 1.5min 5.0min 5.5min 0 transport_latency_assumed new_market h 1,845 406 204ms 20.8s 40.7s 1.5min 0 transport_latency_assumed new_market i 1,845 354 180ms 22.5s 43.0s 1.2min 0 transport_latency_assumed new_market k 2,150 727 296ms 4.7min 5.4min 5.9min 0 transport_latency_assumed new_market m 1,845 1,321 71ms 34.4s 44.0s 1.7min 0 transport_latency_assumed price_change g 101,740,856 40,266 84ms 326ms 10.5s 46.1s 0 transport_latency_assumed price_change h 109,120,322 3,989,590 20ms 80ms 1.1s 1.5min 0 transport_latency_assumed price_change i 109,452,040 2,001,240 25ms 87ms 959ms 16.8s 0 transport_latency_assumed price_change k 103,548,990 10,882,270 15ms 55ms 372ms 37.5s 0 transport_latency_assumed price_change m 109,434,362 92,575,754 6ms 38ms 276ms 8.9s 0 transport_latency_assumed tick_size_change g 3,996 not meas. 80ms 98ms 204ms 408ms 0 transport_latency_assumed tick_size_change h 4,140 48 19ms 29ms 108ms 9.0s 0 transport_latency_assumed tick_size_change i 4,140 4 23ms 32ms 72ms 348ms 0 transport_latency_assumed tick_size_change k 3,952 200 14ms 24ms 90ms 480ms 0 transport_latency_assumed tick_size_change m 4,140 3,888 5ms 12ms 52ms 484ms 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-02/19/2026-10-02T19.parquet sha256sum 2026-10-02T19.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.