navigate

# Navigate A crafted goal runs many RPIs over one bead graph: the root epic holds frozen acceptance and each child bead is one experiment with one RPI. A running goal applies Navigate each wave to pick beads and write results back; a person can run [one pass](#one-pass-without-a-goal). It never edits acceptance, dispatches, judges or closes: Craft Goal owns the prompt and HOLD, [Plan](../plan/SKILL.md) shapes a bead, [Orchestrate](../orchestrate/SKILL.md) dispatches, RPI runs, [Validate](../validate/SKILL.md) judges. ## Speak the domain - **BDD:** each criterion is a Given/When/Then example with an observable result. Each bead names the example it moves; a bead that lacks one gets Plan first inside its RPI. A criterion with no observable result is an open decision for the caller, who can settle it with Interview: report it, never rewrite it. - **DDD:** the root epic defines each domain term once, in one line. Titles, examples, code and tests reuse that exact word. A synonym is a hygiene finding; [Domain](../domain/SKILL.md) settles disputes. - Write a bead as its title, then its id: `Redelivery test (ag-12)`. ## Bead graph contract Root epic: outcome, acceptance examples, non-goals, authority, domain terms. Child bead: the question and the criterion or uncertainty it serves; method, expected observation, falsifier, scope, non-goals; notes enough to resume after compaction; verdict, evidence refs, learning. Edges: `parent-child` for membership, `blocks` only ...