Hour audit: 2026-10-02T01
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-02T01 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T01:00:00.000189063+00:00 · last event 2026-10-02T01:59:59.998359903+00:00
VOLUME 121,175,741 rows · 1,263,780,467 bytes (1.18 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 120,584,698 · m: 120,568,988 · i: 120,551,987 · k: 114,937,343 · g: 114,827,301 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 340,528 (0.28%) · m: 118,270,717 (97.60%) · i: 103,678 (0.09%) · k: 2,024,898 (1.67%) · g: 435,920 (0.36%) (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 121,175,741 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 54fa3cc064e3d942a320cba8333e00e4a15cdf94fb59a6bdca1dfb83f20aec09
the corpus checksum ledger names this file with the same digest
joined 121,247,873 to merged 121,175,741, minus 72,132 (minus 0.0595%)
boundary drops 72,132 · 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-02T03:49:33Z 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 10,172,824 116,798,741 0-38 c1166fe80c95daa2f0cf7faf9c84a872a3a80ae4469a143458abc9ab3736daa1 book 718,792 64,171,856 39-41 1f3c91cce4dfaa1a321ea224b1c727bd47a0ec9e15f233a862f2d43c277f8044 last_trade_price 49,332 2,723,286 42-42 af27a2bf5b39bc74734f651cec0a5bdf266c2f9962af52f9c85af5ecf81f6a21 market_resolved 714 95,428 43-43 6e22a987304a688f8bd527179f422a66a9d6bf54af853d130654efc1d1355787 new_market 443 48,482 44-44 bc4a21b6f78cfe7173efa48a01dd4809be089e058cde280d3d79bf75a3d19a7b price_change 110,231,172 1,078,472,868 45-465 b2aab9b336cdd6f427e5b62a868484a9982ec5311481de8e0b9d7c6110876bc6 tick_size_change 2,464 89,679 466-466 0f25ea10cf45f34a4e443ec1c9416598dddf56659d109d3a528e8f2c017ad4d7 EVENT MIX count share price_change 110,231,172 90.97% best_bid_ask 10,172,824 8.40% book 718,792 0.59% last_trade_price 49,332 0.04% tick_size_change 2,464 <0.01% market_resolved 714 <0.01% new_market 443 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,174,601 10,172,824 1,777 1,318 FULL book 768,685 718,792 49,893 234,518 FULL last_trade_price 49,335 49,332 3 119 FULL market_resolved 714 714 0 17 FULL new_market 460 443 17 18 FULL price_change 110,251,614 110,231,172 20,442 1,500 FULL tick_size_change 2,464 2,464 0 49 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,601,078 507 75ms 90ms 170ms 7.0s 0 transport_latency_assumed best_bid_ask h 10,172,433 23,975 17ms 31ms 57ms 48.4s 0 transport_latency_assumed best_bid_ask i 10,171,417 6,944 27ms 44ms 59ms 7.5s 0 transport_latency_assumed best_bid_ask k 9,610,870 153,011 12ms 20ms 117ms 9.6s 0 transport_latency_assumed best_bid_ask m 10,172,125 9,988,387 5ms 7ms 26ms 2.4s 0 transport_latency_assumed book g 595,054 430,465 10.4min 1.1d 40.5d 125.1d 0 book_staleness book h 136,222 21,705 28ms 36.0min 24.6d 125.1d 0 book_staleness book i 130,859 16,201 41ms 27.0min 24.6d 125.1d 0 book_staleness book k 593,579 138,019 11.5min 1.2d 40.5d 125.1d 0 book_staleness book m 130,814 112,402 6ms 22.4min 12.5d 125.1d 0 book_staleness last_trade_price g 46,893 6 77ms 93ms 251ms 4.7s 0 transport_latency_assumed last_trade_price h 49,312 167 18ms 32ms 93ms 8.6s 0 transport_latency_assumed last_trade_price i 49,306 21 39ms 46ms 111ms 7.0s 0 transport_latency_assumed last_trade_price k 46,861 840 13ms 26ms 126ms 2.0s 0 transport_latency_assumed last_trade_price m 49,312 48,298 5ms 8ms 27ms 1.5s 0 transport_latency_assumed market_resolved g 571 19 79ms 207ms 47.3s 5.3min 0 transport_latency_assumed market_resolved h 588 5 20ms 48ms 51.5s 1.3min 0 transport_latency_assumed market_resolved i 588 47 41ms 25.8s 51.3s 1.0min 0 transport_latency_assumed market_resolved k 588 115 14ms 53.9s 5.6min 5.6min 0 transport_latency_assumed market_resolved m 588 528 5ms 18.3s 51.7s 1.0min 0 transport_latency_assumed new_market g 292 21 119ms 9.1s 28.0s 1.4min 0 transport_latency_assumed new_market h 301 42 56ms 7.7s 13.2s 1.8min 0 transport_latency_assumed new_market i 301 65 58ms 10.5s 1.3min 1.7min 0 transport_latency_assumed new_market k 310 65 69ms 9.7s 2.0min 2.7min 0 transport_latency_assumed new_market m 301 250 24ms 11.2s 1.6min 2.2min 0 transport_latency_assumed price_change g 104,581,089 4,902 76ms 91ms 218ms 7.7s 0 transport_latency_assumed price_change h 110,223,378 294,626 18ms 31ms 74ms 48.4s 0 transport_latency_assumed price_change i 110,197,052 80,400 28ms 45ms 76ms 7.5s 0 transport_latency_assumed price_change k 104,682,763 1,732,812 12ms 20ms 120ms 9.7s 0 transport_latency_assumed price_change m 110,213,384 108,118,432 5ms 8ms 29ms 2.4s 0 transport_latency_assumed tick_size_change g 2,324 not meas. 75ms 88ms 104ms 225ms 0 transport_latency_assumed tick_size_change h 2,464 8 17ms 30ms 34ms 152ms 0 transport_latency_assumed tick_size_change i 2,464 not meas. 30ms 45ms 51ms 64ms 0 transport_latency_assumed tick_size_change k 2,372 36 13ms 18ms 114ms 119ms 0 transport_latency_assumed tick_size_change m 2,464 2,420 5ms 7ms 16ms 26ms 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/01/2026-10-02T01.parquet sha256sum 2026-10-02T01.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.