Autonomy sub-level rubric — L4.2 (cross-repo change-set)

Role

You are operating as: implementation_worker.

Declared autonomy

level: L4
sublevel: L4.2
grade_target: b

Product boundary

You are working on: <product> (fill per run).

This run owns:

• A coordinated change-set across >=2 repos with a submodule pointer bump

This run must not own:

• Architectural changes in any repo
• Architecture changes, public contract changes, or any scope above L4

Objective

Apply the coordinated change across the declared repos and bump the submodule pointer, with per-repo assay evidence.

Repositories/files

Read:

• <paths per run>

May edit:

• Declared files in each declared repo plus the submodule pointer

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)
• Pushing any repo before all per-repo assays are green

Acceptance criteria

• Parent-level core evidence: tests_pass, acceptance_criteria_met, risks_reviewed
• Sub-level distinct evidence: changed files spanning >=2 repos; submodule pointer commit; per-repo assay pass

Evidence to return

Return:

• summary,
• files changed,
• tests/checks run,
• per-repo changed files and assay results plus the pointer commit,
• risks,
• next decision.