coilyco-flight-deck/agent-compose

Watch

Publish the roster artifact into the v1 cascade #19

New issue

Closed

opened 2026-07-22 23:19:43 +00:00 by coilyco-ops · 3 comments

coilyco-ops commented

2026-07-22 23:19:43 +00:00

Member

What to build

Per docs/integration.md (host tier): materialize the roster artifact under ~/.config/agent-compose/sources/personality/ where v1 (generate-agent-compose in agentic-os) already walks for sources, so the next compose run carries the dispatch table into every harness global load point. Zero v1 code changes.

Acceptance criteria

The roster verb (previous slice) targets the sources root; a v1 compose run picks the artifact up and the table lands in COMPOSED..md for each configured harness.
The seam rule holds: v2 writes only under sources/, never touches the load-point symlinks v1 owns.
The dormant-host decision is documented: this workstation's v1 is a static snapshot (per its agent-compose.yaml note), so the slice records whether Kai revives composer runs here or hand-appends once - HITL decision, one paragraph.
Fleet rollout is noted as infrastructure-owned; no Ansible changes in this repo.

Blocked by

Roster artifact slice.
HITL: the dormant-host decision above.

Execution type

AFK after the one HITL decision.

Filed by Claude Code from the #9 decomposition.

## What to build Per docs/integration.md (host tier): materialize the roster artifact under ~/.config/agent-compose/sources/personality/ where v1 (generate-agent-compose in agentic-os) already walks for sources, so the next compose run carries the dispatch table into every harness global load point. Zero v1 code changes. ## Acceptance criteria - [ ] The roster verb (previous slice) targets the sources root; a v1 compose run picks the artifact up and the table lands in COMPOSED.<harness>.md for each configured harness. - [ ] The seam rule holds: v2 writes only under sources/, never touches the load-point symlinks v1 owns. - [ ] The dormant-host decision is documented: this workstation's v1 is a static snapshot (per its agent-compose.yaml note), so the slice records whether Kai revives composer runs here or hand-appends once - HITL decision, one paragraph. - [ ] Fleet rollout is noted as infrastructure-owned; no Ansible changes in this repo. ## Blocked by - Roster artifact slice. - HITL: the dormant-host decision above. ## Execution type AFK after the one HITL decision. Filed by Claude Code from the #9 decomposition.

coilyco-ops referenced this issue

2026-07-22 23:20:18 +00:00

Migrate AOS composition and publish personal v0.1 #9

coilyco-ops referenced this issue

2026-07-23 00:04:14 +00:00

Absorb the v1 cascade composer #23

coilyco-ops referenced this issue

2026-07-23 00:14:36 +00:00

Absorb the v1 cascade composer #23

coilyco-ops commented

2026-07-23 00:14:40 +00:00

Author

Member

Blocker update: the HITL dormant-host decision this issue carried is dissolved by #23 - agent-compose cascade (v0.2.0) composes natively, so no Python revival or hand-append is needed on any host. What replaced it is smaller and different: this workstation's COMPOSED.* files carry hand edits (per the 2026-07-01 note in agent-compose.yaml), so before the first native cascade run here, those edits need reconciling back into source files or they will be regenerated away. That reconciliation is the remaining HITL step; after it, this issue is pure execution: run roster --out ~/.config/agent-compose/sources/personality, then agent-compose cascade.

Filed by Claude Code working the issue queue.

coilyco-ops commented

2026-07-23 00:17:43 +00:00

Author

Member

Reconciliation blocker verified empty. Diffed all three live COMPOSED files against a fresh sandbox cascade compose of the same config: zero on-disk-only lines - the 2026-07-01 'hand-edited snapshots' note is stale fear. The frozen files are pure compositions that fell behind their sources: a native cascade run would only add the banner, the TEMPORARY kapwing/mcp branch section (currently missing from the claude and opencode slices, present in the newer codex one - a live inconsistency), and the mount-eligibility manifest. Symlinks already correct.

This issue is now pure execution, no HITL remaining: agent-compose roster --out ~/.config/agent-compose/sources/personality , then agent-compose cascade.

Verified by Claude Code, read-only.

coilyco-ops commented

2026-07-23 00:23:47 +00:00

Author

Member

Executed live on Kai's workstation and verified by inspection.

agent-compose roster --out ~/.config/agent-compose/sources/personality rendered the artifact (dispatch table, three personality bodies from the public fixtures, claude @-import override); agent-compose cascade (v0.2.0, brew) composed it as the second source into all three COMPOSED slices and repointed nothing (links already correct).
Seam rule held: v2 wrote only under sources/; the cascade owns the load points.
The stale 2026-07-01 note in agent-compose.yaml is replaced with current guidance (edit sources, never outputs).
Five roles render 'pending (#10)' until the #21 sitting; re-running roster + cascade after #10 is the whole refresh story.
Fleet rollout remains infrastructure-owned, tracked with retirement in agentic-os#618.

Closed by Claude Code working the issue queue.

Executed live on Kai's workstation and verified by inspection. - agent-compose roster --out ~/.config/agent-compose/sources/personality rendered the artifact (dispatch table, three personality bodies from the public fixtures, claude @-import override); agent-compose cascade (v0.2.0, brew) composed it as the second source into all three COMPOSED slices and repointed nothing (links already correct). - Seam rule held: v2 wrote only under sources/; the cascade owns the load points. - The stale 2026-07-01 note in agent-compose.yaml is replaced with current guidance (edit sources, never outputs). - Five roles render 'pending (#10)' until the #21 sitting; re-running roster + cascade after #10 is the whole refresh story. - Fleet rollout remains infrastructure-owned, tracked with retirement in agentic-os#618. Closed by Claude Code working the issue queue.

coilyco-ops closed this issue

2026-07-23 00:23:48 +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/agent-compose#19

No description provided.

Rows
Columns