Epic: ship agent-compose v0.1 context bundles #1
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#1
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?
Program context
This is the agent-compose implementation epic from
coilysiren/inbox#216, the agent knowledge-base reset. Agent-compose becomes Kai's public personal assembly and delivery system between reusable AOS knowledge, embedded person policy, and Ward or native-harness consumers.Outcome
Ship a public, personal-first v0.1 that accepts explicit agent, role, personality, model-class, privacy-scope, and target-repo facts, resolves Kai's embedded public-safe person policy plus scoped overlays, and emits an immutable context bundle with a versioned manifest.
Ownership boundary
Agent-compose owns schema, resolution, compilation, materialization, caching, harness projection, diagnostics, and Kai's public-safe company and personality configuration. It does not own reusable AOS knowledge, private overlays, Ward authority policy, credentials, or infrastructure rollout.
Acceptance criteria
Blocked by
None - child slices establish their own dependency order.
Execution type
HITL at contract review points. Implementation slices should otherwise be AFK.
Child issue index
The v0.1 epic is decomposed into eight independently verifiable slices:
Milestone: v0.1 - context bundle foundation.
The dependency spine is
#2 -> #3 -> #4 -> #5 -> #6, with Ward integration branching after #3, diagnostics after #5, and #9 joining every delivery path.Repository baseline landed
The public trifecta and validation shell landed on canonical
mainin commit35e0da3(docs: establish repository shell).The baseline includes
README.md,AGENTS.md,docs/FEATURES.md, theCLAUDE.mdbridge, MITLICENSE,.ward/ward.yaml, the agentic-os pre-commit catalog, and its narrow managed-YAML comment exemption.ward exec testand the installed commit hooks both pass. The local checkout is clean and tracksorigin/main. Child issue #2 can begin from a validated, public-safe repository boundary.Product decision: chatty composition
Agent-compose resolution is a messy decision tree, and humans need to inspect it as a product surface rather than reverse-engineer debug logs. The v0.1 plan now treats explainability as first-class data.
--why, semantic bundle diffing, and health diagnostics.Chatty does not mean noisy. Interactive composition gets a bounded summary with drill-down. Unattended wrappers stay one-line on no-change, expand for changes or warnings, and show complete context on failure. Human explanation output never enters generated model instructions.
Personal-first v0.1 update
The v0.1 tracker now has a ninth child slice: #10 Embed Kai ten-seat company and personality catalog. It carries the roles, sixteen personalities, curated compatibility, operating-mode expression, and personality safety invariant specified in agentic-os#602.
The product contract in #1, #2, #3, #5, #8, and #9 now treats the embedded public-safe person source as first-class. Agent-compose owns organizational and personality context. Ward still owns executable role authority and permissions. AOS retains reusable knowledge and general skills.
The final migration issue is now #9 Migrate AOS composition and publish personal v0.1 and is blocked by #10. The repository positioning landed on
mainin7d7ba17.v0.1 acceptance audit
All autonomous acceptance work is complete.
b339ac4.9f7ec90retains only the reusable low-context provider decision.v0.33.0before the final evaluation-pack push. Upgrade behavior is documented in the contracts and integration guides.The full Ward, agent-compose, and AOS validation surfaces passed for the landed changes. The two remaining agent-compose tickets, #72 and #73, contain only human taste and behavior-scoring decisions. They do not represent unfinished v0.1 implementation.
The epic is complete.