Hour audit: 2026-10-02T21
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-02T21 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T21:00:00.001842013+00:00 · last event 2026-10-02T21:59:59.999997737+00:00
VOLUME 94,538,955 rows · 969,038,095 bytes (924.15 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured i: 94,487,264 · k: 94,477,109 · h: 94,459,973 · m: 94,436,785 · g: 94,254,849 (each machine's own feed; these overlap and do not sum to the file)
supplied i: 377,437 (0.40%) · k: 3,740,942 (3.96%) · h: 738,380 (0.78%) · m: 89,663,056 (94.84%) · g: 19,140 (0.02%) (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 94,538,955 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 784fc27ed69367f09d425ba5a3e3ce6f88fde3548270f8663d8b6e8fbe6755fc
the corpus checksum ledger names this file with the same digest
joined 94,541,493 to merged 94,538,955, minus 2,538 (minus 0.0027%)
boundary drops 2,538 · 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-02T23:41:26Z 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,182,912 107,612,110 0-35 5abbc909732f4060d0522d4a157ca8c31a8c51f79a75cc98ff600be7ae08f15b book 116,767 12,341,587 36-36 4a850317b1f996990d16709d7adff4966da8b7984b987e0fe9965cd533257f49 last_trade_price 45,270 2,617,928 37-37 6c5b1da24899abe5efd7378bd5f0f630187cf3a290714301d6f673f931746511 market_resolved 756 119,058 38-38 24635f6a97d29fa5764ee2fa56e8ef8cbb57031b3a3067bb14fd5fba9ac7e956 new_market 894 88,876 39-39 4a58bce1139fd20e0fefe5c56e2f5955ace1887d13abd538dee74e3014746091 price_change 85,190,192 845,097,022 40-364 6b4b2fc28523c2f8ad8e9fd050d1107da1af831e7b3211038282ff2dba23ad63 tick_size_change 2,164 80,313 365-365 3ce22f62050513ee9b1128c04a3a29a4023f6b58addf6d5fc18d0c61650aaf79 EVENT MIX count share price_change 85,190,192 90.11% best_bid_ask 9,182,912 9.71% book 116,767 0.12% last_trade_price 45,270 0.05% tick_size_change 2,164 <0.01% new_market 894 <0.01% market_resolved 756 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,183,112 9,182,912 200 110 FULL book 116,805 116,767 38 8,626 FULL last_trade_price 45,270 45,270 0 0 FULL market_resolved 756 756 0 0 FULL new_market 894 894 0 0 FULL price_change 85,192,492 85,190,192 2,300 65 FULL tick_size_change 2,164 2,164 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,179,401 400 81ms 98ms 320ms 20.2s 0 transport_latency_assumed best_bid_ask h 9,182,179 62,528 18ms 24ms 120ms 48.8s 0 transport_latency_assumed best_bid_ask i 9,182,106 29,946 21ms 27ms 95ms 9.1s 0 transport_latency_assumed best_bid_ask k 9,182,182 333,564 13ms 20ms 83ms 27.6s 0 transport_latency_assumed best_bid_ask m 9,180,913 8,756,474 5ms 9ms 58ms 3.0s 0 transport_latency_assumed book g 104,830 14,772 95ms 3.4min 4.3d 107.5d 0 book_staleness book h 92,990 2,738 22ms 117ms 8.6min 107.4d 0 book_staleness book i 93,268 2,685 24ms 178ms 7.9min 107.4d 0 book_staleness book k 93,720 6,972 16ms 61ms 1.1h 107.4d 0 book_staleness book m 95,790 89,600 7ms 40ms 2.9h 2.1d 0 book_staleness last_trade_price g 44,522 5 95ms 1.0s 15.2s 20.3s 0 transport_latency_assumed last_trade_price h 45,186 426 20ms 84ms 561ms 7.6s 0 transport_latency_assumed last_trade_price i 45,212 239 23ms 119ms 783ms 1.7s 0 transport_latency_assumed last_trade_price k 45,207 2,455 14ms 38ms 300ms 7.1s 0 transport_latency_assumed last_trade_price m 45,028 42,145 6ms 16ms 159ms 1.2s 0 transport_latency_assumed market_resolved g 729 not meas. 85ms 367ms 51.1s 51.2s 0 transport_latency_assumed market_resolved h 729 6 21ms 75ms 52.9s 52.9s 0 transport_latency_assumed market_resolved i 729 26 24ms 118ms 42.2s 58.2s 0 transport_latency_assumed market_resolved k 729 46 15ms 40ms 1.0s 56.1s 0 transport_latency_assumed market_resolved m 729 678 6ms 16ms 41.9s 41.9s 0 transport_latency_assumed new_market g 563 55 294ms 18.7s 56.3s 1.4min 0 transport_latency_assumed new_market h 563 180 128ms 21.4s 1.2min 2.5d 0 transport_latency_assumed new_market i 563 135 93ms 10.4s 38.7s 1.7min 0 transport_latency_assumed new_market k 563 115 111ms 19.7s 58.7s 2.5d 0 transport_latency_assumed new_market m 563 409 48ms 16.3s 1.0min 2.5d 0 transport_latency_assumed price_change g 84,922,640 3,908 81ms 117ms 2.6s 20.3s 0 transport_latency_assumed price_change h 85,136,162 672,498 18ms 28ms 247ms 48.8s 0 transport_latency_assumed price_change i 85,163,222 344,402 22ms 32ms 311ms 9.1s 0 transport_latency_assumed price_change k 85,152,544 3,397,678 13ms 23ms 143ms 25.7s 0 transport_latency_assumed price_change m 85,111,598 80,771,706 5ms 11ms 75ms 4.2s 0 transport_latency_assumed tick_size_change g 2,164 not meas. 81ms 97ms 610ms 986ms 0 transport_latency_assumed tick_size_change h 2,164 4 18ms 23ms 263ms 933ms 0 transport_latency_assumed tick_size_change i 2,164 4 21ms 28ms 140ms 318ms 0 transport_latency_assumed tick_size_change k 2,164 112 13ms 18ms 124ms 2.9s 0 transport_latency_assumed tick_size_change m 2,164 2,044 5ms 9ms 51ms 171ms 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/21/2026-10-02T21.parquet sha256sum 2026-10-02T21.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.