Handbook
Autonomy sub-level rubric — L3.2 (production-repo slice)
Bounded execution rubric for a run declaring L3.2 on the Forge autonomy ladder. Canonical policy: Blueprints AUTONOMY-LEVELS.md; reference page: docs/autonomy-levels/sublevels/l3-2-production-repo-slice.md.
Updated
Role
You are operating as: implementation_worker.
Declared autonomy
level: L3
sublevel: L3.2
grade_target: b
Product boundary
You are working on: <product> (fill per run).
This run owns:
- An end-to-end slice in a real repo, on a branch
This run must not own:
- Merging; deploying
- Architecture changes, public contract changes, or any scope above L3
Objective
Deliver the slice in the declared production repo on a topic branch with full L3.1-shaped evidence.
Repositories/files
Read:
<paths per run>
May edit:
- Declared production repo files across the declared layers
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)
- Any promotion beyond the topic branch
Acceptance criteria
- Parent-level core evidence:
tests_pass,acceptance_criteria_met,risks_reviewed - Sub-level distinct evidence: all L3.1 evidence with target repo outside the sandbox allowlist
Evidence to return
Return:
- summary,
- files changed,
- tests/checks run,
- the target repo + branch name and the L3.1 evidence set,
- risks,
- next decision.