Navigation

Navigation turns an uncertain bearing into one owned, testable correction. The captain owns the voyage. A First Mate reads the instruments and hands over the next chart.

Choose Your Job

1. Run the Golden MEV Journey — turn goodwill into a zero-fee, beneficiary-verified experiment and reusable standard.
2. Make a first Playbook contribution — correct one teaching-to-action gap and leave proof for the next contributor.
3. Start Nav — turn one live decision into a session-only nav.v1 handoff.
4. Understand First Mate — learn the authority boundary between captain, agent, and retained state.
5. Navigate a decision — run Problem → Question → Decision and close with proof, review, and a kill signal.
6. Calibrate Value, Belief, and Control — align the setpoint, truth horizon, and feedback loop.
7. Use navigation instruments — read forks, obstacles, signs, and handoffs.

Contract

Nav asks for facts the captain owns: situation, evidence, the decision under consideration, value at stake, and constraints. It proposes a nine-field navigation artifact and steering contract. The captain rejects, revises, or explicitly confirms it.

Only explicit confirmation may emit one private receipt and schedule a review. Public doctrine stays here. Private decisions and mutable review state stay in Stackmates/drmg.

Context

• depends-on Navigation System — canonical Value, Belief, and Control architecture.
• applies-to Decision Making — deeper treatment for irreversible or compound decisions.
• contrasts-with AI Harness — generic agent software architecture, not Nav’s product identity.