Handbook

L2.2 — Cross-file defect fix

Status: Demonstrated — retro-tagged L2.2b (Blueprints Example 3, L2-broken-link-and-nested; the failing-test-before evidence now required was not recorded at the time)

Updated

Sub-level at a glance
Parent level L2 — Change-set
Autonomous unit Cross-file defect fix
Distinct assay evidence Pre-existing failing test recorded, turns green; ≥2 files
Grade today b (retro-tag)

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 (L2 — Change-set) apply unchanged. Declaring this sub-level adds the distinct check:

  • Pre-existing failing test recorded before the fix and turned green by it, across ≥2 distinct changed files

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-l2-2.md — workcell-skeleton prompt declaring this sub-level, its evidence-to-return shape, and human gates.

Worked case

Field Value
Repo forge-dark-factory PoC — lenses-production-l2 campaign
Goal Fix README broken link and nested.md TODO placeholder in one change-set
Evidence produced runs/campaigns/lenses-production-l2/L2-broken-link-and-nested/run-*/{machine,human}/ — 2 patch units, README.md + docs/guide/nested.md
Assay pass rationale Core L2: ≥2 distinct changed files. Retro-tagged L2.2b: run predates failing_test_before recording; strict L2.2 _check_sublevel now requires failing_test_before non-empty — without it → L2.2 evidence: pre-existing failing test not recorded before the fix