Epic: converge and verify the agent knowledge fleet #953

New issue

Open

opened 2026-08-27 03:24:51 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-27 03:24:51 +00:00

Owner

Parent

#216

Owning repos

infrastructure owns fleet convergence. agent-compose, ward, agentic-os, and agentic-os-kai own the artifacts and contracts that infrastructure installs.

Outcome

Every supported host, harness, role, and model class receives the intended knowledge sources through one reproducible rollout, with compatibility evidence and rollback instead of hand-populated root files.

What to build

Install released agent-compose through the normal fleet convergence path.
Install or shadow the supported launch wrappers for Ward, warded roles, Claude, Codex, Goose, and local-model harnesses.
Converge public AOS sources, personal AOSK overlays, embedded person config, and repo capability declarations from their canonical owners.
Wire Ward's read-only context-bundle mount without teaching Ansible or Ward to interpret composed policy.
Cover root-native Codex and Claude, warded engineer / QA / director roles, Goose, Qwen / OpenCode, WSL / Windows, and supported Linux hosts.
Apply model-class density so frontier and local models receive the intended instruction depth and personality balance.
Mount the full AOS catalog first-class where the role and privacy scope allow it.
Verify concurrent multi-repo runs select the right repo declarations and never leak another repo's bundle.
Retain a last-known-good bundle and a documented rollback path.
Make rollout a consequence of landed source changes through the established push-triggered automation.
Record a compatibility matrix with evidence for every supported surface.
Keep infrastructure declarative. It installs canonical outputs and does not duplicate composition policy.

Acceptance criteria

A fresh supported host converges agent-compose, launch wrappers, sources, and mounts without manual root-file population.
Existing supported hosts converge idempotently.
Root-native, warded, Goose, Qwen / OpenCode, and WSL / Windows scenarios pass the compatibility matrix.
Frontier and local model sessions receive visibly different, intentional context density.
Kai's person config appears only on personal surfaces.
Public and work surfaces receive only public-safe sources.
All intended AOS skills are first-class discoverable without injecting their full bodies into every prompt.
Concurrent repo sessions select correct bundles with no cross-repo contamination.
Rollback restores the last-known-good composition after a failed rollout.
No deployment or composition policy is reimplemented in Ansible.
Fleet verification includes role-boundary evidence from #219 and source coverage from #220 through #224.

Blocked by

Execution type

AFK for convergence code and non-live compatibility fixtures. Human-in-the-loop for live fleet rollout, host verification, and rollback acceptance.

## Parent #216 ## Owning repos infrastructure owns fleet convergence. agent-compose, ward, agentic-os, and agentic-os-kai own the artifacts and contracts that infrastructure installs. ## Outcome Every supported host, harness, role, and model class receives the intended knowledge sources through one reproducible rollout, with compatibility evidence and rollback instead of hand-populated root files. ## What to build * Install released agent-compose through the normal fleet convergence path. * Install or shadow the supported launch wrappers for Ward, warded roles, Claude, Codex, Goose, and local-model harnesses. * Converge public AOS sources, personal AOSK overlays, embedded person config, and repo capability declarations from their canonical owners. * Wire Ward's read-only context-bundle mount without teaching Ansible or Ward to interpret composed policy. * Cover root-native Codex and Claude, warded engineer / QA / director roles, Goose, Qwen / OpenCode, WSL / Windows, and supported Linux hosts. * Apply model-class density so frontier and local models receive the intended instruction depth and personality balance. * Mount the full AOS catalog first-class where the role and privacy scope allow it. * Verify concurrent multi-repo runs select the right repo declarations and never leak another repo's bundle. * Retain a last-known-good bundle and a documented rollback path. * Make rollout a consequence of landed source changes through the established push-triggered automation. * Record a compatibility matrix with evidence for every supported surface. * Keep infrastructure declarative. It installs canonical outputs and does not duplicate composition policy. ## Acceptance criteria * A fresh supported host converges agent-compose, launch wrappers, sources, and mounts without manual root-file population. * Existing supported hosts converge idempotently. * Root-native, warded, Goose, Qwen / OpenCode, and WSL / Windows scenarios pass the compatibility matrix. * Frontier and local model sessions receive visibly different, intentional context density. * Kai's person config appears only on personal surfaces. * Public and work surfaces receive only public-safe sources. * All intended AOS skills are first-class discoverable without injecting their full bodies into every prompt. * Concurrent repo sessions select correct bundles with no cross-repo contamination. * Rollback restores the last-known-good composition after a failed rollout. * No deployment or composition policy is reimplemented in Ansible. * Fleet verification includes role-boundary evidence from #219 and source coverage from #220 through #224. ## Blocked by * #219 * #220 * #221 * #222 * #223 * #224 * https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/9 ## Execution type AFK for convergence code and non-live compatibility fixtures. Human-in-the-loop for live fleet rollout, host verification, and rollback acceptance.

coilyco-ops added this to the CD and rollout milestone

2026-08-29 06:10:05 +00:00

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#953

No description provided.

Rows
Columns