Skip to content
kanade — 奏 kanade docs

Auto-iterate

Mission auto-iterate is the controlled loop between a mission, a Forge run, and a review verdict. It is meant for bounded work with clear halt conditions, not for open-ended background autonomy.

A healthy loop has four gates:

  1. Scope: the mission states the target and non-goals.
  2. Cost: the operator accepts that a Forge run will consume local time and provider quota.
  3. Review: the run returns evidence, not just a status label.
  4. Halt: failure, uncertainty, or a review-blocking change stops the loop.

Kanade can show recent verdicts and launch another run, but the operator should read the run evidence before continuing. Auto-iterate is useful when a mission has a repeatable quality bar: build, route smoke, accessibility check, visual baseline, release proof, or docs link audit.

For destructive or shared-state work, the confirmation step stays in place. Kanade does not silently deploy, push, delete, or rewrite release state because a mission happens to be active.