system-improvementlisted

# System Repair Resolution Read the persisted Goal, Run, Intervention, and change task before editing. The task must specify `change_kind`, owner, problem or capability, allowed files, acceptance commands, version before, and target version. 1. Refuse an unbounded or incomplete task. 2. Modify only `allowed_files`. Do not opportunistically refactor. 3. Preserve the originating business hypothesis and controlled variables. 4. Run every acceptance command exactly as recorded. 5. Record failure honestly if any acceptance command fails. A failed acceptance stays failed; the next try remains inside the same Intervention and allowed files, not a new Goal or a rewrite of failed evidence. 6. On success, call `company change complete` with the actual test evidence. 7. Mark deployed only after deployment actually happened. 8. Return control to the originating run. Never convert machinery evidence into a market or positioning conclusion. The Goal Run remains suspended during this Resolution work. Never silently resume it with different business variables. Never create a Goal for a repair, test, deployment, Agent fix, Connection fix, or Workflow change. If the repair has no clear relevant Goal, or several Goals could own it and the relationship is genuinely ambiguous, ask the owner. For a new Department package, require its purpose, metrics, Agents, Agent-owned Workflows, declared evidence, and exact allowed paths. Validate the package before editing and prove catalog disco