Epic: ship agent-compose v0.1 context bundles #1

Closed
opened 2026-07-16 07:59:12 +00:00 by coilyco-ops · 5 comments
Member

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

  • Versioned input and bundle contracts are documented and tested.
  • The default product embeds Kai's ten-seat company, sixteen personalities, and curated compatibility from #10.
  • Personal defaults are first-class product source, not a sample forced through a premature generic extension framework.
  • One command composes a deterministic bundle from public fixture sources.
  • Native harness and Ward consumers both use the same bundle contract.
  • Repo language and product capabilities select skills without Ward parsing AOS policy.
  • Every bundle retains a deterministic decision trace that explains inclusions, exclusions, fallbacks, and delivery choices.
  • Humans can inspect and diff that trace ergonomically without turning unattended startup into a wall of logs.
  • Concurrent launches cannot mutate or observe a partially written shared bundle.
  • Claude, Codex, Goose, and local Qwen/OpenCode compatibility is exercised.
  • The existing AOS composer migrates without leaving a second implementation.
  • Generated bundles and rendered references remain uncommitted.
  • A versioned v0.1 artifact and upgrade path are published.

Blocked by

None - child slices establish their own dependency order.

Execution type

HITL at contract review points. Implementation slices should otherwise be AFK.

## 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 - [ ] Versioned input and bundle contracts are documented and tested. - [ ] The default product embeds Kai's ten-seat company, sixteen personalities, and curated compatibility from #10. - [ ] Personal defaults are first-class product source, not a sample forced through a premature generic extension framework. - [ ] One command composes a deterministic bundle from public fixture sources. - [ ] Native harness and Ward consumers both use the same bundle contract. - [ ] Repo language and product capabilities select skills without Ward parsing AOS policy. - [ ] Every bundle retains a deterministic decision trace that explains inclusions, exclusions, fallbacks, and delivery choices. - [ ] Humans can inspect and diff that trace ergonomically without turning unattended startup into a wall of logs. - [ ] Concurrent launches cannot mutate or observe a partially written shared bundle. - [ ] Claude, Codex, Goose, and local Qwen/OpenCode compatibility is exercised. - [ ] The existing AOS composer migrates without leaving a second implementation. - [ ] Generated bundles and rendered references remain uncommitted. - [ ] A versioned v0.1 artifact and upgrade path are published. ## Blocked by None - child slices establish their own dependency order. ## Execution type HITL at contract review points. Implementation slices should otherwise be AFK.
Author
Member

Child issue index

The v0.1 epic is decomposed into eight independently verifiable slices:

  1. #2 Define the v0.1 input, policy, and bundle contracts - HITL contract review, starts now.
  2. #3 Compose one public profile into a deterministic bundle - first executable tracer, blocked by #2.
  3. #4 Resolve repo capabilities into selected skills - blocked by #3.
  4. #5 Deliver one bundle across native and compiled harness profiles - blocked by #3 and #4.
  5. #6 Freshen context at launch without races or recursion - blocked by #5.
  6. #7 Consume agent-compose bundles from Ward - blocked by #2 and #3, can proceed in parallel with later harness work.
  7. #8 Explain composition decisions and diagnose bundle health - blocked by #4 and #5.
  8. #9 Migrate AOS composition and publish agent-compose v0.1 - final cutover and release gate, blocked by #5 through #8.

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.

### Child issue index The v0.1 epic is decomposed into eight independently verifiable slices: 1. [#2 Define the v0.1 input, policy, and bundle contracts](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/2) - HITL contract review, starts now. 2. [#3 Compose one public profile into a deterministic bundle](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/3) - first executable tracer, blocked by #2. 3. [#4 Resolve repo capabilities into selected skills](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/4) - blocked by #3. 4. [#5 Deliver one bundle across native and compiled harness profiles](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/5) - blocked by #3 and #4. 5. [#6 Freshen context at launch without races or recursion](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/6) - blocked by #5. 6. [#7 Consume agent-compose bundles from Ward](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/7) - blocked by #2 and #3, can proceed in parallel with later harness work. 7. [#8 Explain composition decisions and diagnose bundle health](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/8) - blocked by #4 and #5. 8. [#9 Migrate AOS composition and publish agent-compose v0.1](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/9) - final cutover and release gate, blocked by #5 through #8. Milestone: [v0.1 - context bundle foundation](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/milestone/10). The dependency spine is `#2 -> #3 -> #4 -> #5 -> #6`, with Ward integration branching after #3, diagnostics after #5, and #9 joining every delivery path.
Author
Member

Repository baseline landed

The public trifecta and validation shell landed on canonical main in commit 35e0da3 (docs: establish repository shell).

The baseline includes README.md, AGENTS.md, docs/FEATURES.md, the CLAUDE.md bridge, MIT LICENSE, .ward/ward.yaml, the agentic-os pre-commit catalog, and its narrow managed-YAML comment exemption.

ward exec test and the installed commit hooks both pass. The local checkout is clean and tracks origin/main. Child issue #2 can begin from a validated, public-safe repository boundary.

### Repository baseline landed The public trifecta and validation shell landed on canonical `main` in commit `35e0da3` (`docs: establish repository shell`). The baseline includes `README.md`, `AGENTS.md`, `docs/FEATURES.md`, the `CLAUDE.md` bridge, MIT `LICENSE`, `.ward/ward.yaml`, the agentic-os pre-commit catalog, and its narrow managed-YAML comment exemption. `ward exec test` and the installed commit hooks both pass. The local checkout is clean and tracks `origin/main`. Child issue #2 can begin from a validated, public-safe repository boundary.
Author
Member

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.

  • #2 defines a deterministic decision-trace contract alongside the bundle manifest.
  • #3 emits and stores the trace from the first executable composer slice.
  • #8 Make composition decisions chatty and inspectable renders progressive human output, item-level --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.

### 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. * #2 defines a deterministic decision-trace contract alongside the bundle manifest. * #3 emits and stores the trace from the first executable composer slice. * [#8 Make composition decisions chatty and inspectable](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/8) renders progressive human output, item-level `--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.
Author
Member

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 main in 7d7ba17.

### Personal-first v0.1 update The v0.1 tracker now has a ninth child slice: [#10 Embed Kai ten-seat company and personality catalog](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/10). 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 `main` in `7d7ba17`.
Author
Member

v0.1 acceptance audit

All autonomous acceptance work is complete.

  • Contracts and deterministic composition landed through #2 and #3, with tested KDL, manifest, bundle, and trace contracts.
  • The embedded personal-first roster and personality catalog landed through #10 and the later person-source consolidation work.
  • Repo capabilities and model class select skills in agent-compose. AOS publishes provider decisions, while Ward does not parse AOS policy.
  • Native projection supports Claude, Codex, Goose, and OpenCode from the same immutable bundle contract.
  • Ward consumes that contract through a verified fixed read-only mount in Ward commit b339ac4.
  • Decision traces, human summaries, item-level explanations, diffs, and health diagnostics landed through #8.
  • Atomic materialization, warm refresh, and concurrent-launch coverage landed through #6 and subsequent stability fixes.
  • The former AOS composition implementation was absorbed and removed. AOS commit 9f7ec90 retains only the reusable low-context provider decision.
  • Generated bundles, projections, and person snapshots stay outside repositories.
  • Automated release publication is active, and versioned artifacts exist through v0.33.0 before 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.

## v0.1 acceptance audit All autonomous acceptance work is complete. * Contracts and deterministic composition landed through #2 and #3, with tested KDL, manifest, bundle, and trace contracts. * The embedded personal-first roster and personality catalog landed through #10 and the later person-source consolidation work. * Repo capabilities and model class select skills in agent-compose. AOS publishes provider decisions, while Ward does not parse AOS policy. * Native projection supports Claude, Codex, Goose, and OpenCode from the same immutable bundle contract. * Ward consumes that contract through a verified fixed read-only mount in Ward commit `b339ac4`. * Decision traces, human summaries, item-level explanations, diffs, and health diagnostics landed through #8. * Atomic materialization, warm refresh, and concurrent-launch coverage landed through #6 and subsequent stability fixes. * The former AOS composition implementation was absorbed and removed. AOS commit `9f7ec90` retains only the reusable low-context provider decision. * Generated bundles, projections, and person snapshots stay outside repositories. * Automated release publication is active, and versioned artifacts exist through `v0.33.0` before 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.
Sign in to join this conversation.
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#1
No description provided.