Skip to main content

Run a code-change goal

A code-change goal implements or modifies production code. It is goal_type: IMPLEMENTATION_PHASE (or similar) and is dispatched under BUILDER role.

When to use​

  • Adding a new module or feature.
  • Modifying an existing module.
  • Bounded refactors that don't cross frozen surfaces.

Steps​

  1. Create a new branch.
  2. Copy an existing IMP-style contract (goals/ASF50_IMP_11_IMPLEMENTATION_001/GOAL_RECORD.yaml).
  3. Update all required fields.
  4. Commit the goal contract.
  5. Run goal-run.ps1 -GoalId <NEW_GOAL_ID> -RuntimeRoot … -DryRun.
  6. Inspect the JSON.
  7. Implement the bounded scope. Stay inside allowed_paths.
  8. Run the test suite (pytest).
  9. Commit the implementation.
  10. Push the branch.
  11. Open the PR.
  12. STOP at the GitHub review boundary.

Special considerations​

  • A code-change goal may require INDEPENDENT_AUDIT_HIGH. Two-root provenance is required: dispatch worktree + audit worktree pinned at audit_subject_sha.
  • The audit worktree must be created before the dispatch.
  • The orchestrator will detect any drift between the two and refuse to dispatch the auditor.