audit_trace_budget

Plan & Execute

Verified planning loop + post-approval autonomous execution

When to use

  • You need a verified change plan before making edits
  • The plan requires user approval before execution
  • After approval, execution should continue autonomously

Two coupled loops

Loop A: Plan (before approval)

  1. Pick one unresolved plan claim. Files to change, tests to run, migration safety.
  2. Gather the smallest evidence. Repo excerpt, config, test output.
  3. Update Facts / Decisions / Assumptions.
  4. Audit. Run audit_trace_budget on plan claims.
  5. Repeat until all plan-critical claims are supported. Then ask for approval once.

Loop B: Execute (after approval)

  1. Choose the smallest next patch mapped to one plan step.
  2. Apply, test, store outputs.
  3. Record attempt with keep/revert decision.
  4. Audit changed claims. If tests fail, revert and return to Loop A.
  5. Repeat until all planned changes are implemented and verified.

Copy/paste prompt

Start a run. Gather evidence for the plan.
Produce Facts (cited), Decisions, and Assumptions.
Run audit_trace_budget on plan claims.
Ask for approval once all claims are supported.
After approval, implement patches one at a time, testing each.
Record every attempt. Revert failed patches.