Handbook

L4.2 — Cross-repo change-set

Status: Defined (vision gates)

Updated

Sub-level at a glance
Parent level L4 — Feature/component
Autonomous unit Cross-repo change-set with submodule bump
Distinct assay evidence ≥2 repos; submodule pointer commit; per-repo assay pass
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:

  • Changed files spanning ≥2 repos, a submodule pointer commit, and a per-repo assay pass

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.

L4.2 has wider span than L4.1 but lower architectural risk — sub-levels within a level are peer variants ordered by typical adoption, not strictly increasing risk.

Prompt pack

Execution rubric (repo path, nav-hidden): prompts/autonomy/sublevel-l4-2.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 cross-repo campaign run exists.

Field Value
Repo forge-platform-website + forge-platform submodule (hypothetical)
Goal Bump forge-platform submodule pointer after autonomy docs change, with per-repo assay pass
Evidence produced Pattern: runs/campaigns/<campaign>/<item>/run-*/machine/ with changed files spanning ≥2 repo prefixes and submodule_pointer_commit: true
Assay pass rationale L4.2 _check_sublevel: _repo_prefixes(changed_files) length ≥2; submodule_pointer_commit recorded
Assay fail example Single-repo change → L4.2 evidence: changed files span 1 repo prefix(es), need >=2; no pointer commit → L4.2 evidence: submodule pointer commit not recorded