Migrate AOS composition and publish personal v0.1 #9
Labels
No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agent-compose#9
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Parent
#1
What to build
Move the live composition engine and Kai's company/personality configuration out of agentic-os, migrate existing YAML-era sources and load points to the reviewed KDL and bundle contracts, and publish the first independently installable personal agent-compose release. Leave AOS as content and policy, not a second implementation.
Acceptance criteria
context-levelconcept is replaced by the reviewed model-class and profile schema.Blocked by
Execution type
HITL for migration cutover and release approval. Preparation and tests are AFK.
Migrate AOS composition and publish agent-compose v0.1to Migrate AOS composition and publish personal v0.1Closing as superseded, per docs/integration.md (
4207b4a) and the decomposition it defines.The premise of this issue - migrating AOS composition into this repo - predates the v1/v2 seam design. Nothing moves out of v1 in v0.1: v1 (generate-agent-compose in agentic-os) keeps global doctrine, the load-point symlinks, and the mount-eligibility manifest ward reads. The v0.1 'migration' is additive and now tracked as:
Retirement of v1, and inheritance of its mount-eligibility obligation, is explicitly deferred to a future contract.
Closed by Claude Code on Kai's direction from the planning discussion.