Handbook

L4.1 — New component in a single repo

Status: Defined (vision gates)

Updated

Sub-level at a glance
Parent level L4 — Feature/component
Autonomous unit New component, single repo
Distinct assay evidence New module/dir + ADR draft + release-gate record
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 (L4 — Feature/component) apply unchanged. Declaring this sub-level adds the distinct check:

  • A new module/directory in the diff, an ADR draft, and a release-gate 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-l4-1.md — workcell-skeleton prompt declaring this sub-level, its evidence-to-return shape, and human gates.

Worked case

Hypothetical case — L4.x remains vision; no PoC or Platform enforcement run exists.

Field Value
Repo forge-platform (hypothetical)
Goal Introduce new autonomy-assessor module with ADR draft and release-gate record
Evidence produced Pattern: runs/campaigns/<campaign>/<item>/run-*/machine/ with new src/autonomy_assessor/ dir, adr_recorded: true, release_gate_recorded: true
Assay pass rationale L4.1 _check_sublevel: adr_recorded and release_gate_recorded both true
Assay fail example New module without ADR → L4.1 evidence: ADR draft not recorded; no release gate → L4.1 evidence: release-gate record missing