26  Code Generation and Repair Loop

27 Code Generation and Repair Loop

Working seal: stack://code-generation-and-repair-loop/DBD637DB96

Enter: Use when an AI system is helping write or modify software and generation should stay tied to execution evidence.

27.1 Related Runes

• 1088 diff {Forge} - A visible account of what changed between one state and another. Good diffs make review local; bad diffs turn truth into fog.
• 1146 benchmark - A performance claim forced to meet measurement. Benchmarks are where speed rhetoric either cashes out or dies.
• 1172 invariant - A law that must remain true while the rest of the system is allowed to move. If you cannot say the invariant, you probably do not yet understand the change.
• 1180 observability - Enough internal evidence exists that you can infer what the system is doing from the outside. Not logs alone: legible state under pressure.
• 1485 reproducible - Can be rebuilt or rerun and yield the same result again.

27.2 Related Spell Templates and References

• Test Generation
• Bug Diagnosis From Logs
• Safe Refactoring
• Stack Grammar
• Failure Modes
• Canon Map | Step | Spell | Artifact | Advance when | | —- | ——– | ————————————————————– | —————————————————- | | 1 | Specify | Precise task statement, constraints, interfaces, and non-goals | The target is testable | | 2 | Draft | Smallest plausible implementation or patch | The code compiles in principle and names assumptions | | 3 | Run | Build, test, lint, or type-check output | Actual failures are captured verbatim | | 4 | Diagnose | Likely cause and repair surface | The diagnosis uses only emitted evidence | | 5 | Repair | Smallest diff addressing the diagnosed cause | The patch is explicit | | 6 | Verify | Check results and residual risk | Checks pass or residual risk is clearly bounded |

27.3 Loop or Recursion

{
  "steps": [
    3,
    4,
    5,
    6
  ],
  "until": "Checks pass, error surface stabilizes without progress, or attempt budget is exhausted"
}

27.4 On Fail

Escalate with spec, code diff, failing output, diagnostic notes, and unresolved assumptions.

27.5 Why It Works

It separates invention from judgment and binds repair to execution evidence.