THE SEED, PLAINLY: Apple Health distance is FOOT only — today's synced 3.03 MI excludes tonight's train ride and board miles entirely. Rail and board travel are real, and they are proven — they just never inflate the foot game.
The standing record is 12.67 MI in a day (Oct 28). The crown target is the record + 1% — 12.80 MI in a single day takes it. It is always just barely reachable, on purpose.
The standing record is 52.39 MI in a week (Oct 26 – Nov 1). The crown target is the record + 1% — 52.9 MI in a week takes it.
Walk the Ming wall's main line end to end — 5,500 MI, crew-cumulative. Every mile anybody logs moves the whole expedition. Seeded with the Captain's synced week.
Climb sea level to the summit in elevation gain — 29,032 FT, crew-cumulative. Flights climbed convert at ≈10 FT each. Seeded with the Captain's synced 41 flights.
A 1,000 MI relay along the Khan's messenger route — crew-cumulative, rider after rider. Seeded with the Captain's synced week.
Dadeland → Coconut Grove Marina overland: 7 MI in a single day. Tonight's run, on the board forever. Progress rides today's total.
Home Base → Bayside: 5 MI in a single day. Progress rides today's total.
Every crown target is the standing record + 1% — never a fixed wall, so the next crown is always just barely reachable (the goal-gradient: the closer it looks, the harder you push). Sandbagging is pointless: a soft record only lowers tomorrow's target for everybody else. Set a record today and tomorrow the game asks you for 1% more. That is the whole engine — join, and beat the leader.
Matchmaking by weekly baseline, so newcomers play winnable games instead of chasing a legend's shadow:
The Great Wall, Everest, and the Khan's Ride are crew-cumulative — every mile and every foot of climb anybody logs moves the whole expedition; nobody races alone against 5,500 miles. The crowns are individual — your day against the leader's day. Both motives run at once: help the crew cross the world, and take the crown while you do it.
Distances in FEET and MILES, elevation in FEET — Presidential Challenge № 022 settled the units question for this fleet. The seeded board is the Captain's Apple Health sync through Nov 1, 2026; anything added in ADD TODAY is a local log on this phone, labeled LOCAL wherever it counts. No server writes, no one else's health data — v1.0 plays clean.
Prizes make the game real — and the prize is access. Winners earn access to the BRIDGE apps. Two keys unlock the Bunny Rabbit Queue: ① ATHLETICISM — win or place in the Arena. ② SMARTS — the second key (gate details to come). The Captain confirms every seat personally — a prize earns the hearing; athleticism + smarts earn the keys.
THE TRIBUTE DOOR RULE STANDS: access prizes never include the Captain's data, crew positions, or anyone's private stats — the keys open doors, not people's records.
🏁 Ride with NAV open to start scoring — your first measured segment opens your accuracy row.
SURVEY POINTS: every stored segment pass earns 1 point per 100 FT of measured ground (rounded, minimum 1 per pass). Lay ground truth down, get paid.
ACCURACY POINTS: when the same ground is measured again on a different day, the board compares the day grades: AGREEMENT = 100 − 10 × the spread between the day grades (in grade points), never below 0. Each repeat day pays AGREEMENT ÷ 10 points (rounded). Steadier rider, bigger pay.
ACCURACY %: a rider's accuracy is the distance-weighted mean AGREEMENT across all their re-measured ground. One ride proves nothing — agreement across days is the score.
WHY DAYS: re-rides inside a single day blend into one record inside NAV's store before this board can see them, so repeats count across days — that is where two independent looks at the same ground exist.
WHAT THIS BOARD DOES NOT PUBLISH: no feed estimate is stored per segment, so there is no feed-error number here. The board grades the rider, not the feed.
THIS DEVICE'S RIDES — crew rows light up when crew segments flow.