Handbook

L3.3 — Slice with data/schema migration

Status: Defined

Updated

Sub-level at a glance
Parent level L3 — Use-case slice
Autonomous unit Slice including data/schema migration
Distinct assay evidence L3.2 evidence + migration file + rollback note
Grade today a

Canonical policy, grades a-d, and promotion criteria: Autonomy levels (Blueprints). Per-project scoring: Autonomy maturity framework (Blueprints).

Gates and evidence

All gates and core evidence of the parent level (L3 — Use-case slice) apply unchanged. Declaring this sub-level adds the distinct check:

  • All L3.2 evidence, plus a migration file in the diff and a rollback note in the run record

A run that fails the sub-level check may still be reported at the plain parent-level grain if the parent's evidence holds — sub-level claims are strictly additive.

Prompt pack

Execution rubric (repo path, nav-hidden): prompts/autonomy/sublevel-l3-3.md — workcell-skeleton prompt declaring this sub-level, its evidence-to-return shape, and human gates.

Worked case

Hypothetical case — no campaign run has declared L3.3 yet.

Field Value
Repo forge-lenses on a feature branch (hypothetical)
Goal Use-case slice adding a schema column with Alembic migration and documented rollback
Evidence produced Pattern: runs/campaigns/<campaign>/<item>/run-*/machine/ with migrations/001_add_scan_id.py in changed_files and rollback_note in run record
Assay pass rationale All L3.2 evidence plus L3.3 _check_sublevel: _is_migration_file match in changed_files; non-empty rollback_note
Assay fail example Slice without migration file → L3.3 evidence: no migration file in changed files; missing rollback → L3.3 evidence: rollback note missing from run record