Consume agent-compose bundles from Ward #7

New issue

Closed

opened 2026-07-16 08:01:07 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-16 08:01:07 +00:00

Member

Parent

What to build

Complete the first cross-product integration with Ward. Ward supplies resolved agent, role, model-class, privacy-scope, and target-repo facts, then mounts the selected bundle read-only. Agent-compose consumes those facts without learning Ward permission rules, deployment credentials, or live-system authority.

Acceptance criteria

A narrow, versioned runtime-fact handoff is implemented and documented.
Ward treats the bundle tree as opaque and validates only the manifest protocol it consumes.
Engineer, QA, director, advisor, and ops fixtures resolve distinct profiles from explicit facts.
Sealed engineer and QA fixtures receive deployment precedent without live observation credentials.
Bundle trees mount read-only and exclude auth stores and mutable harness state.
Two concurrent Ward launches against different repos receive distinct correct bundles.
Protocol mismatch and missing-bundle failures stop before agent launch with actionable errors.
The companion Ward issue and compatibility tests link back to this issue.

Blocked by

Blocked by #2
Blocked by #3

Execution type

AFK after the shared contract review. Live deployment verification is not part of this slice.

## Parent #1 ## What to build Complete the first cross-product integration with Ward. Ward supplies resolved agent, role, model-class, privacy-scope, and target-repo facts, then mounts the selected bundle read-only. Agent-compose consumes those facts without learning Ward permission rules, deployment credentials, or live-system authority. ## Acceptance criteria - [ ] A narrow, versioned runtime-fact handoff is implemented and documented. - [ ] Ward treats the bundle tree as opaque and validates only the manifest protocol it consumes. - [ ] Engineer, QA, director, advisor, and ops fixtures resolve distinct profiles from explicit facts. - [ ] Sealed engineer and QA fixtures receive deployment precedent without live observation credentials. - [ ] Bundle trees mount read-only and exclude auth stores and mutable harness state. - [ ] Two concurrent Ward launches against different repos receive distinct correct bundles. - [ ] Protocol mismatch and missing-bundle failures stop before agent launch with actionable errors. - [ ] The companion Ward issue and compatibility tests link back to this issue. ## Blocked by - Blocked by #2 - Blocked by #3 ## Execution type AFK after the shared contract review. Live deployment verification is not part of this slice.

coilyco-ops added this to the v0.1 - context bundle foundation milestone

2026-07-16 08:01:07 +00:00

coilyco-ops referenced this issue

2026-07-16 08:02:28 +00:00

Migrate AOS composition and publish personal v0.1 #9

coilyco-ops referenced this issue

2026-07-16 08:02:58 +00:00

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

coilyco-ops referenced this issue

2026-07-22 21:53:45 +00:00

Freshen context at launch without races or recursion #6

coilyco-ops commented

2026-07-22 23:13:32 +00:00

Author

Member

Closing as superseded by #17.

Most of this issue predates two decisions that reshaped Ward integration:

The #13 contract review removed agent, model-class, privacy-scope, and target-repo from composition inputs, and dropped the versioned-protocol framing. The handoff is now a five-line compose request or a bundle path.
The launch-entrypoint design conversation (recorded across #5/#6 and the projection docs) landed on containers as the home of per-agent identity: personality loads at launch mechanically because the bundle projects into container-HOME, with hard isolation as a side effect. Ward is the container launcher, not the primary entrypoint.

Already shipped elsewhere: concurrent-launch isolation and convergence (#6, tested), credentials/mutable-state exclusion (bundle format invariant), actionable manifest validation errors (#3).

Still relevant and carried into the successor: read-only opaque mount, container-HOME projection at start, fail-closed pre-launch gate, the documented handoff, companion Ward issue, and the multi-role fixture matrix (blocked on #10 giving roles beyond engineer their personalities).

Closed by Claude Code on Kai's direction.

Closing as superseded by #17. Most of this issue predates two decisions that reshaped Ward integration: - The #13 contract review removed agent, model-class, privacy-scope, and target-repo from composition inputs, and dropped the versioned-protocol framing. The handoff is now a five-line compose request or a bundle path. - The launch-entrypoint design conversation (recorded across #5/#6 and the projection docs) landed on containers as the home of per-agent identity: personality loads at launch mechanically because the bundle projects into container-HOME, with hard isolation as a side effect. Ward is the container launcher, not the primary entrypoint. Already shipped elsewhere: concurrent-launch isolation and convergence (#6, tested), credentials/mutable-state exclusion (bundle format invariant), actionable manifest validation errors (#3). Still relevant and carried into the successor: read-only opaque mount, container-HOME projection at start, fail-closed pre-launch gate, the documented handoff, companion Ward issue, and the multi-role fixture matrix (blocked on #10 giving roles beyond engineer their personalities). Closed by Claude Code on Kai's direction.

coilyco-ops referenced this issue

2026-07-22 23:13:33 +00:00

Mount and home-project bundles in warded containers #17

coilyco-ops closed this issue

2026-07-22 23:13:35 +00:00