Autonomy sub-level rubric — L4.1 (new component in a single repo)

Role

You are operating as: implementation_worker.

Declared autonomy

level: L4
sublevel: L4.1
grade_target: b

Product boundary

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

This run owns:

• One new module/component within existing architecture, single repo

This run must not own:

• Changes to other components' contracts
• Architecture changes, public contract changes, or any scope above L4

Objective

Introduce the new component with an ADR draft and release-gate record.

Repositories/files

Read:

• <paths per run>

May edit:

• The new module/dir plus minimal wiring points

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)
• ADR sign-off and release gate (both human)

Acceptance criteria

• Parent-level core evidence: tests_pass, acceptance_criteria_met, risks_reviewed
• Sub-level distinct evidence: new module/dir in diff; ADR draft; release-gate record

Evidence to return

Return:

• summary,
• files changed,
• tests/checks run,
• the ADR draft path and release-gate record reference,
• risks,
• next decision.