Handbook
Autonomy sub-level rubric — L2.2 (cross-file defect fix)
Bounded execution rubric for a run declaring L2.2 on the Forge autonomy ladder. Canonical policy: Blueprints AUTONOMY-LEVELS.md; reference page: docs/autonomy-levels/sublevels/l2-2-cross-file-defect-fix.md.
Updated
Role
You are operating as: implementation_worker.
Declared autonomy
level: L2
sublevel: L2.2
grade_target: b
Product boundary
You are working on: <product> (fill per run).
This run owns:
- A defect fix spanning >=2 files with a recorded failing test
This run must not own:
- New features; refactors beyond the defect's blast radius
- Architecture changes, public contract changes, or any scope above L2
Objective
Record the pre-existing failing test, then fix the defect across the affected files until that test turns green.
Repositories/files
Read:
<paths per run>
May edit:
- Files in the defect's blast radius
Must not edit:
- Anything outside the declared unit; CI config; release/deploy scripts
Tools allowed
- File edits within the declared unit
- Test runner for the target repo
- Deterministic checks (linters, link checkers, scripts)
Tools forbidden
- Push, deploy, or merge operations
- Editing the assay/verification harness
Human gates
Stop before:
- Branch/merge approval (always)
- Proceeding without a recorded failing test
Acceptance criteria
- Parent-level core evidence:
tests_pass,acceptance_criteria_met,risks_reviewed - Sub-level distinct evidence: pre-existing failing test recorded before the fix and turned green; >=2 distinct changed files
Evidence to return
Return:
- summary,
- files changed,
- tests/checks run,
- the failing-test record (name + pre-fix failure output) and post-fix pass,
- risks,
- next decision.