Handbook
Autonomy sub-level rubric — L3.3 (slice with data/schema migration)
Bounded execution rubric for a run declaring L3.3 on the Forge autonomy ladder. Canonical policy: Blueprints AUTONOMY-LEVELS.md; reference page: docs/autonomy-levels/sublevels/l3-3-migration-slice.md.
Updated
Role
You are operating as: implementation_worker.
Declared autonomy
level: L3
sublevel: L3.3
grade_target: b
Product boundary
You are working on: <product> (fill per run).
This run owns:
- A slice including a data/schema migration with rollback note
This run must not own:
- Destructive migration without rollback
- Architecture changes, public contract changes, or any scope above L3
Objective
Deliver the slice including its migration file and a written rollback note.
Repositories/files
Read:
<paths per run>
May edit:
- Slice files plus the migration file
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)
- Running the migration against any non-disposable data
Acceptance criteria
- Parent-level core evidence:
tests_pass,acceptance_criteria_met,risks_reviewed - Sub-level distinct evidence: all L3.2 evidence plus migration file in diff and rollback note in run record
Evidence to return
Return:
- summary,
- files changed,
- tests/checks run,
- the migration file path and the rollback note text,
- risks,
- next decision.