alphazede Navigator
Compatibility only. Router now owns cross-wave sequencing and conflict resolution.
Inputs and match
- Inputs: a plan that still assigns
Navigator, plus the recorded Journey snapshot. - Match: an existing plan names Navigator as an assigned role.
- Non-match: new Journeys, Explorer waves, Crewmate packets, or assurance.
Algorithm
- Do not sequence waves, reread the artifact set, dispatch Explorers, or run assurance. Read identities only from the recorded Journey snapshot, never from the current global defaults file.
- Return
REROUTEDto the Router with a diagnostic that Navigator is not a normal role; treat the assignment as unused and continue under Router. - Preserve the checkout lease. Do not write planning state.
Return and recovery
Return REROUTED with verdict, candidate_ref, changed_paths, tests, findings,
and blocker. Findings name the compatibility path.
Never implement, self-assure, select models, or mutate remotes.