Hour audit: 2026-10-02T05
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-02T05 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T05:00:00.000024857+00:00 · last event 2026-10-02T05:59:59.999884698+00:00
VOLUME 97,694,847 rows · 971,568,537 bytes (926.56 MiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 97,642,302 · h: 97,625,822 · k: 97,618,249 · i: 97,608,164 · g: 97,576,699 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 95,330,031 (97.58%) · h: 369,485 (0.38%) · k: 1,683,806 (1.72%) · i: 235,646 (0.24%) · g: 75,879 (0.08%) (rows of the merged file that came from it; these partition it)
4 product-machine pairs publish no supplied count; the figures above still sum to the file's 97,694,847 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 2f2997ec60e9c20228a03fe886a471b6e632a7ced0c6f87145b3393fa9586eb4
the corpus checksum ledger names this file with the same digest
joined 97,697,215 to merged 97,694,847, minus 2,368 (minus 0.0024%)
boundary drops 2,368 · 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-02T07:42: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 8,203,174 94,700,721 0-31 d4e6ef091bb203cad0c462a8f59197fd7592271c30e05d22cafa03415077cab0 book 135,252 15,068,256 32-32 8703d00ca8fe5c203150cdfcf7f88ec64a33a54b34367d60879d5ae8848ea2f9 last_trade_price 46,035 2,596,991 33-33 6d102101c7ed190de40cf0a56c22f2663038bafcfd60ec008c21bb566933db34 market_resolved 859 133,208 34-34 b6a27c313c46c794b0a0f8c690ad581ec57de478b9133bb2a1d7702f9fed55b4 new_market 2,319 215,254 35-35 a2d19a57339d801480e4d2c3776eaa406f0a2248a65ce07a284265a6e5dfc81b price_change 89,304,672 857,643,811 36-376 4511496eab45cca20f62b6ca759addd90569797641a19966cdad82586fc0413d tick_size_change 2,536 93,478 377-377 6de8ce9442517101f49a98618b65a9a61b4b7efbca60fcdfb78eaf0a354210c4 EVENT MIX count share price_change 89,304,672 91.41% best_bid_ask 8,203,174 8.40% book 135,252 0.14% last_trade_price 46,035 0.05% tick_size_change 2,536 <0.01% new_market 2,319 <0.01% market_resolved 859 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 8,203,448 8,203,174 274 316 FULL book 135,268 135,252 16 18,839 FULL last_trade_price 46,035 46,035 0 0 FULL market_resolved 859 859 0 0 FULL new_market 2,319 2,319 0 0 FULL price_change 89,306,750 89,304,672 2,078 81 FULL tick_size_change 2,536 2,536 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 8,199,911 5,285 73ms 90ms 353ms 21.0s 0 transport_latency_assumed best_bid_ask h 8,201,330 29,788 18ms 32ms 495ms 1.5min 0 transport_latency_assumed best_bid_ask i 8,201,101 20,266 22ms 41ms 160ms 6.3s 0 transport_latency_assumed best_bid_ask k 8,200,830 120,454 12ms 24ms 249ms 1.6min 0 transport_latency_assumed best_bid_ask m 8,201,808 8,027,381 5ms 7ms 70ms 7.2s 0 transport_latency_assumed book g 109,203 15,099 76ms 4.1min 6.2d 106.8d 0 book_staleness book h 100,038 6,213 21ms 127ms 9.1h 125.3d 0 book_staleness book i 95,536 1,850 24ms 50ms 3.4s 106.8d 0 book_staleness book k 104,110 11,394 15ms 1.8s 3.2d 125.3d 0 book_staleness book m 104,034 100,696 6ms 1.5s 24.0h 106.7d 0 book_staleness last_trade_price g 45,922 31 75ms 124ms 756ms 21.1s 0 transport_latency_assumed last_trade_price h 46,027 159 18ms 34ms 551ms 54.0s 0 transport_latency_assumed last_trade_price i 46,022 67 24ms 44ms 232ms 4.1s 0 transport_latency_assumed last_trade_price k 46,028 762 13ms 23ms 290ms 10.1s 0 transport_latency_assumed last_trade_price m 46,025 45,016 5ms 8ms 77ms 1.7s 0 transport_latency_assumed market_resolved g 823 not meas. 75ms 275ms 45.5s 45.5s 0 transport_latency_assumed market_resolved h 823 3 19ms 62ms 52.0s 52.0s 0 transport_latency_assumed market_resolved i 823 10 38ms 235ms 53.7s 53.7s 0 transport_latency_assumed market_resolved k 823 39 13ms 44ms 54.5s 54.5s 0 transport_latency_assumed market_resolved m 823 807 5ms 19ms 52.8s 52.9s 0 transport_latency_assumed new_market g 1,392 130 291ms 19.1s 56.3s 1.2min 0 transport_latency_assumed new_market h 1,392 312 176ms 23.3s 54.9s 1.6min 0 transport_latency_assumed new_market i 1,392 363 134ms 22.0s 55.9s 1.7min 0 transport_latency_assumed new_market k 1,392 317 208ms 19.6s 57.0s 1.6min 0 transport_latency_assumed new_market m 1,392 1,197 40ms 19.5s 55.6s 1.7min 0 transport_latency_assumed price_change g 89,216,912 55,334 73ms 93ms 736ms 21.1s 0 transport_latency_assumed price_change h 89,273,676 333,010 18ms 32ms 573ms 1.5min 0 transport_latency_assumed price_change i 89,260,754 213,090 22ms 42ms 239ms 7.4s 0 transport_latency_assumed price_change k 89,262,530 1,550,786 13ms 22ms 287ms 1.7min 0 transport_latency_assumed price_change m 89,285,684 87,152,452 5ms 8ms 96ms 7.2s 0 transport_latency_assumed tick_size_change g 2,536 not meas. 73ms 81ms 102ms 282ms 0 transport_latency_assumed tick_size_change h 2,536 not meas. 18ms 34ms 47ms 2.4s 0 transport_latency_assumed tick_size_change i 2,536 not meas. 22ms 43ms 61ms 289ms 0 transport_latency_assumed tick_size_change k 2,536 54 12ms 19ms 117ms 123ms 0 transport_latency_assumed tick_size_change m 2,536 2,482 5ms 7ms 271ms 326ms 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/05/2026-10-02T05.parquet sha256sum 2026-10-02T05.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.