Skip to content
kanade — 奏 kanade docs

Mission Control

Mission Control stores goal-shaped work in Kanade. A mission is not a chat message and not a Forge run by itself. It is a local record with title, slug, state, persona or preferred model, action plan, and evidence of recent work.

The mission pages let an operator:

  • create a scoped mission,
  • review status and progress,
  • copy a brief for a lane,
  • bind a Forge hero or preferred model,
  • inspect recent Forge runs,
  • archive a finished or abandoned mission.

The route stays local-first. Kanade can launch a bounded Forge run when the bridge is configured, but Forge remains the engine that owns planning, implementation, and review worktrees. Kanade stores the mission and displays the relay state.

Good mission shape

Section titled “Good mission shape”

A good mission is narrower than a product roadmap and wider than a single edit. “Repair docs IA for v0.5.0” is a mission. “Make Kanade better” is not. Keep the scope tight enough that halt conditions and proof can be named before launch.