Hour audit: 2026-10-02T17
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-02T17 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T17:00:00.000101284+00:00 · last event 2026-10-02T17:59:59.999900270+00:00
VOLUME 114,953,942 rows · 1,274,428,811 bytes (1.19 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured m: 114,857,912 · k: 114,843,927 · i: 114,839,467 · h: 114,835,088 · g: 113,221,396 (each machine's own feed; these overlap and do not sum to the file)
supplied m: 102,016,625 (88.75%) · k: 8,223,002 (7.15%) · i: 1,726,941 (1.50%) · h: 2,923,064 (2.54%) · g: 64,310 (0.06%) (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 114,953,942 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 17c3686be4b874648373a78d6b769a67422e8742b7549acc8bef63f9749862d5
the corpus checksum ledger names this file with the same digest
joined 114,956,624 to merged 114,953,942, minus 2,682 (minus 0.0023%)
boundary drops 2,682 · 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-02T19:46:46Z 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,124,454 114,603,546 0-34 504b4a5824d1b651689112bfd5e5172e2bcfda34430dcf5ceae6e01f8cbcec17 book 245,043 25,179,324 35-35 d78078a5583f0172ee61d1aefd63738d134411cef0d9d3c4a941f8a7ed2ef180 last_trade_price 74,256 4,174,744 36-36 67e10d68bcabc2033dbb7617c9694ebd55f53f918f2f7c7cd362d11be5b31106 market_resolved 1,163 184,924 37-37 838ab8de2aa291d21d42c241f42006bba1fd708488c970d15e31ee1e3b638051 new_market 5,634 491,953 38-38 ad30b64e88c4df8226f18be3ec66c56a04554e01b04edf7e5fc0d1238abe1f54 price_change 105,499,048 1,128,324,055 39-441 d8b98a141a6a45e1ee66001a25e05afa03f3d4b1142280e70de1ce051520bc7a tick_size_change 4,344 160,840 442-442 d50059ab4e12027eca31b6b8305fbbc01114adba23be76b28295f3cdb442e2e5 EVENT MIX count share price_change 105,499,048 91.78% best_bid_ask 9,124,454 7.94% book 245,043 0.21% last_trade_price 74,256 0.06% new_market 5,634 <0.01% tick_size_change 4,344 <0.01% market_resolved 1,163 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 9,124,684 9,124,454 230 85 FULL book 245,125 245,043 82 37,213 FULL last_trade_price 74,256 74,256 0 3 FULL market_resolved 1,163 1,163 0 5 FULL new_market 5,634 5,634 0 0 FULL price_change 105,501,418 105,499,048 2,370 67 FULL tick_size_change 4,344 4,344 0 0 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 9,093,991 2,207 81ms 210ms 2.9s 47.1s 0 transport_latency_assumed best_bid_ask h 9,123,359 223,358 19ms 51ms 702ms 1.5min 0 transport_latency_assumed best_bid_ask i 9,123,601 139,589 22ms 50ms 345ms 17.7s 0 transport_latency_assumed best_bid_ask k 9,123,456 659,913 14ms 46ms 403ms 1.1min 0 transport_latency_assumed best_bid_ask m 9,124,308 8,099,387 5ms 23ms 216ms 6.0s 0 transport_latency_assumed book g 175,877 35,168 233ms 53.1min 22.3d 107.3d 0 book_staleness book h 168,765 18,415 28ms 4.5s 18.6h 107.3d 0 book_staleness book i 168,496 16,830 33ms 5.4s 1.1d 107.3d 0 book_staleness book k 172,627 26,943 25ms 8.7s 2.9d 107.3d 0 book_staleness book m 167,236 147,687 8ms 2.0s 16.7h 62.2d 0 book_staleness last_trade_price g 67,070 11 119ms 6.1s 20.1s 42.0s 0 transport_latency_assumed last_trade_price h 74,120 1,863 21ms 218ms 2.1s 1.0min 0 transport_latency_assumed last_trade_price i 74,132 874 28ms 554ms 5.8s 17.7s 0 transport_latency_assumed last_trade_price k 74,225 4,930 17ms 164ms 843ms 55.5s 0 transport_latency_assumed last_trade_price m 74,230 66,578 6ms 34ms 281ms 4.6s 0 transport_latency_assumed market_resolved g 1,143 2 91ms 754ms 45.4s 52.1s 0 transport_latency_assumed market_resolved h 1,143 36 21ms 519ms 49.1s 55.1s 0 transport_latency_assumed market_resolved i 1,143 24 24ms 327ms 53.5s 53.6s 0 transport_latency_assumed market_resolved k 1,138 62 17ms 378ms 51.9s 52.0s 0 transport_latency_assumed market_resolved m 1,143 1,039 6ms 223ms 53.4s 53.5s 0 transport_latency_assumed new_market g 3,171 666 491ms 2.5min 3.6min 4.1min 0 transport_latency_assumed new_market h 3,171 958 267ms 2.2min 3.5min 3.8min 0 transport_latency_assumed new_market i 3,171 1,060 231ms 2.3min 3.4min 3.9min 0 transport_latency_assumed new_market k 3,171 853 295ms 2.5min 3.5min 4.2min 0 transport_latency_assumed new_market m 3,171 2,097 85ms 2.4min 3.4min 3.8min 0 transport_latency_assumed price_change g 103,875,800 26,256 84ms 440ms 12.0s 49.3s 0 transport_latency_assumed price_change h 105,460,186 2,678,386 20ms 69ms 931ms 1.7min 0 transport_latency_assumed price_change i 105,464,580 1,568,548 22ms 75ms 863ms 17.8s 0 transport_latency_assumed price_change k 105,464,966 7,530,108 14ms 60ms 494ms 1.3min 0 transport_latency_assumed price_change m 105,483,480 93,695,750 5ms 25ms 234ms 7.5s 0 transport_latency_assumed tick_size_change g 4,344 not meas. 79ms 204ms 834ms 37.3s 0 transport_latency_assumed tick_size_change h 4,344 48 19ms 41ms 573ms 26.4s 0 transport_latency_assumed tick_size_change i 4,344 16 21ms 39ms 343ms 4.5s 0 transport_latency_assumed tick_size_change k 4,344 193 14ms 41ms 2.0s 34.1s 0 transport_latency_assumed tick_size_change m 4,344 4,087 5ms 13ms 97ms 374ms 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/17/2026-10-02T17.parquet sha256sum 2026-10-02T17.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.