31 lines
1.2 KiB
Markdown
31 lines
1.2 KiB
Markdown
# AIOS Autonomous Release Campaign v1
|
|
|
|
This control plane changes the Owner interaction model from per-transaction
|
|
approval to one durable, revocable campaign policy delegation.
|
|
|
|
The single bootstrap confirmation creates:
|
|
1. a narrow task-writer grant for the control-plane implementation branch; and
|
|
2. a root-owned campaign authorization in PENDING_CONTROL_PLANE_MERGE state.
|
|
|
|
After the protected control-plane PR merges, machine activation may move that
|
|
same receipt to ACTIVE only when:
|
|
- the merged main is a descendant of the campaign lineage anchor;
|
|
- the campaign modules and tests are present in merged main;
|
|
- the campaign receipt digest is valid;
|
|
- no revocation exists;
|
|
- global AIOS_GITOPS_WRITES_ENABLED remains false.
|
|
|
|
Once ACTIVE, routine engineering, protected PRs, exact release binding
|
|
acceptance, tag publication, deployment, Registry/Baseline finalization and
|
|
recoverable failure handling no longer ask the Owner for another interaction.
|
|
|
|
Manual Owner review remains mandatory only for:
|
|
- formal same-name tag conflict;
|
|
- force-push requirement;
|
|
- published history rewrite;
|
|
- non-fast-forward main divergence;
|
|
- private signing material exposure;
|
|
- repository identity conflict;
|
|
- campaign revocation;
|
|
- operation outside campaign scope.
|