Hour audit: 2026-10-02T13
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-02T13 · corpus v3 · verdict AUDIT PASS
COVERAGE minutes present 60/60 · first event 2026-10-02T13:00:00.000048207+00:00 · last event 2026-10-02T13:59:59.999964745+00:00
VOLUME 122,814,253 rows · 1,376,190,348 bytes (1.28 GiB) · 7 products, all holding rows
WITNESSES ghikm — 5 machines contributed rows
captured h: 122,450,553 · m: 122,296,439 · k: 122,279,742 · i: 122,137,738 · g: 120,250,967 (each machine's own feed; these overlap and do not sum to the file)
supplied h: 3,290,201 (2.68%) · m: 108,200,488 (88.10%) · k: 9,222,894 (7.51%) · i: 1,859,841 (1.51%) · g: 240,829 (0.20%) (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 122,814,253 rows exactly, so those pairs supplied none
5 expected, all 5 contributed
INTEGRITY sha256 f5094f6ecfc14f57e18d6fb278c4b77c2003c15daa1f294c5e976a31fbe45d00
the corpus checksum ledger names this file with the same digest
joined 122,816,509 to merged 122,814,253, minus 2,256 (minus 0.0018%)
boundary drops 2,256 · 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-02T15:48: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 10,293,373 127,031,690 0-39 3673dd75ac15bb387661b65ae1de5680458e37ee6b4c5126f096f29c9b677eaf book 736,280 65,079,547 40-42 f12a4811cfbed3195c13cd7b338a3cd12654abab19593522a2db3ff2c88b6dbc last_trade_price 61,500 3,527,403 43-43 a17cc57fd9e4b672256d95903b94b8f48aaac76a402bbbe9d71d04c40196f563 market_resolved 740 121,788 44-44 e5d386e598ef4fd4f885cc544971004689cb6f2cb55b3ba6f4feb7f4919a0d9b new_market 1,982 183,196 45-45 f71ffbb6cd0065d812e975dc0b159b910efd61b2aa881a5a7b06e36c5f5b369e price_change 111,716,862 1,178,718,678 46-472 03fafd1d36c74c2ee8e0c791a810cc6ed78dd637f32ed6a4beddf9ec697989d4 tick_size_change 3,516 127,738 473-473 2ae1573306727d6649f234b52f76f974c1273770d5ccbc0c36efea74b3d82fe3 EVENT MIX count share price_change 111,716,862 90.96% best_bid_ask 10,293,373 8.38% book 736,280 0.60% last_trade_price 61,500 0.05% tick_size_change 3,516 <0.01% new_market 1,982 <0.01% market_resolved 740 <0.01% PER PRODUCT joined merged boundary exception mkts class best_bid_ask 10,293,504 10,293,373 131 152 FULL book 736,858 736,280 578 198,640 FULL last_trade_price 61,501 61,500 1 1 FULL market_resolved 740 740 0 0 FULL new_market 1,982 1,982 0 2 FULL price_change 111,718,408 111,716,862 1,546 202 FULL tick_size_change 3,516 3,516 0 1 FULL ARRIVAL SKEW m rows won p50 p90 p99 max unmeasurable interpretation best_bid_ask g 10,266,094 1,194 80ms 146ms 1.1s 33.4s 0 transport_latency_assumed best_bid_ask h 10,290,416 243,705 19ms 43ms 400ms 45.7s 0 transport_latency_assumed best_bid_ask i 10,291,630 137,719 22ms 44ms 291ms 8.8s 0 transport_latency_assumed best_bid_ask k 10,291,832 755,423 14ms 36ms 233ms 46.5s 0 transport_latency_assumed best_bid_ask m 10,292,370 9,155,332 5ms 21ms 195ms 4.5s 0 transport_latency_assumed book g 393,395 226,504 5.1min 13.0h 41.0d 125.6d 0 book_staleness book h 410,114 210,937 4.3min 13.0h 41.0d 125.6d 0 book_staleness book i 132,847 8,051 35ms 1.1s 12.7h 107.1d 0 book_staleness book k 244,292 91,260 370ms 12.5h 37.8d 125.7d 0 book_staleness book m 252,657 199,528 1.6s 12.6h 37.8d 125.6d 0 book_staleness last_trade_price g 55,774 9 96ms 3.2s 18.7s 33.5s 0 transport_latency_assumed last_trade_price h 61,461 1,506 22ms 200ms 2.5s 37.1s 0 transport_latency_assumed last_trade_price i 61,409 848 29ms 310ms 2.5s 8.4s 0 transport_latency_assumed last_trade_price k 61,472 4,639 16ms 88ms 499ms 4.9s 0 transport_latency_assumed last_trade_price m 61,472 54,498 6ms 29ms 360ms 2.8s 0 transport_latency_assumed market_resolved g 730 1 87ms 648ms 52.2s 57.1s 0 transport_latency_assumed market_resolved h 730 16 21ms 233ms 38.7s 43.3s 0 transport_latency_assumed market_resolved i 730 9 30ms 375ms 33.6s 57.4s 0 transport_latency_assumed market_resolved k 730 52 17ms 196ms 37.1s 41.3s 0 transport_latency_assumed market_resolved m 730 662 6ms 14.2s 51.1s 55.4s 0 transport_latency_assumed new_market g 1,174 171 320ms 37.4s 1.9min 149.9d 0 transport_latency_assumed new_market h 1,174 216 171ms 35.9s 1.7min 149.9d 0 transport_latency_assumed new_market i 1,172 346 173ms 51.4s 2.0min 2.2min 0 transport_latency_assumed new_market k 1,174 224 149ms 22.6s 1.8min 149.9d 0 transport_latency_assumed new_market m 1,174 1,025 29ms 19.6s 2.0min 149.9d 0 transport_latency_assumed price_change g 109,530,288 12,950 82ms 309ms 11.1s 33.6s 0 transport_latency_assumed price_change h 111,683,142 2,833,728 20ms 61ms 652ms 45.7s 0 transport_latency_assumed price_change i 111,646,434 1,712,860 23ms 59ms 845ms 8.9s 0 transport_latency_assumed price_change k 111,676,726 8,371,066 15ms 47ms 291ms 46.5s 0 transport_latency_assumed price_change m 111,684,520 98,786,258 6ms 24ms 222ms 4.9s 0 transport_latency_assumed tick_size_change g 3,512 not meas. 79ms 118ms 713ms 8.4s 0 transport_latency_assumed tick_size_change h 3,516 93 19ms 45ms 479ms 2.7s 0 transport_latency_assumed tick_size_change i 3,516 8 22ms 46ms 255ms 2.8s 0 transport_latency_assumed tick_size_change k 3,516 230 14ms 35ms 325ms 3.5s 0 transport_latency_assumed tick_size_change m 3,516 3,185 5ms 17ms 147ms 657ms 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/13/2026-10-02T13.parquet sha256sum 2026-10-02T13.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.