Converge native checkouts from the compiled AOS residency plan #758

Closed
opened 2026-08-05 07:49:02 +00:00 by coilyco-ops · 0 comments
Member

Parent

coilyco-flight-deck/agent-compose#200

Outcome

Make Infrastructure realize AOS's compiled native residency plan without owning or repeating repository policy.

Work

  • Upgrade and converge the required AOS and Agent Compose releases before resolving the residency plan.
  • Replace the source-tree repos-on-disk.txt input to checkout sync with the installed compiled plan.
  • Ensure fresh-host bootstrap can obtain the plan before all target repositories exist.
  • Clone missing resident repositories and refresh existing clean or dirty checkouts under the established safety behavior.
  • Preserve canonical remote selection and public versus private transport boundaries.
  • Remove the repository-list half of the agentic-os-config symlink role after no consumer needs ~/.config/agentic-os/repos-on-disk.txt.
  • Keep fleet-organization configuration separate because it scopes drift detection rather than residency.
  • Remove Infrastructure documentation that calls the old flat roster canonical.
  • Do not parse roles.kdl, reconstruct role closures, or maintain an Ansible repository list.

Acceptance criteria

  • Infrastructure consumes one machine-readable residency plan produced by the installed AOS or Agent Compose surface.
  • Fresh-host convergence has no checkout dependency cycle.
  • Missing resident repositories are cloned and existing repositories retain the current bounded refresh behavior.
  • Infrastructure owns rollout only and contains no role repository policy.
  • No full expected-repository list remains in Infrastructure variables, templates, scripts, or docs.
  • The conventional repo-list symlink is removed.
  • Fleet-organization configuration remains independently converged.
  • Check mode validates the plan and reports intended changes without mutation.
  • docs/FEATURES.md records compiled residency convergence.
  • Repository validation passes through declared Ward verbs.
## Parent https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/200 ## Outcome Make Infrastructure realize AOS's compiled native residency plan without owning or repeating repository policy. ## Work * Upgrade and converge the required AOS and Agent Compose releases before resolving the residency plan. * Replace the source-tree `repos-on-disk.txt` input to checkout sync with the installed compiled plan. * Ensure fresh-host bootstrap can obtain the plan before all target repositories exist. * Clone missing resident repositories and refresh existing clean or dirty checkouts under the established safety behavior. * Preserve canonical remote selection and public versus private transport boundaries. * Remove the repository-list half of the `agentic-os-config` symlink role after no consumer needs `~/.config/agentic-os/repos-on-disk.txt`. * Keep fleet-organization configuration separate because it scopes drift detection rather than residency. * Remove Infrastructure documentation that calls the old flat roster canonical. * Do not parse `roles.kdl`, reconstruct role closures, or maintain an Ansible repository list. ## Acceptance criteria * [ ] Infrastructure consumes one machine-readable residency plan produced by the installed AOS or Agent Compose surface. * [ ] Fresh-host convergence has no checkout dependency cycle. * [ ] Missing resident repositories are cloned and existing repositories retain the current bounded refresh behavior. * [ ] Infrastructure owns rollout only and contains no role repository policy. * [ ] No full expected-repository list remains in Infrastructure variables, templates, scripts, or docs. * [ ] The conventional repo-list symlink is removed. * [ ] Fleet-organization configuration remains independently converged. * [ ] Check mode validates the plan and reports intended changes without mutation. * [ ] `docs/FEATURES.md` records compiled residency convergence. * [ ] Repository validation passes through declared Ward verbs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/infrastructure#758
No description provided.