Emit mount-eligibility manifest from generate_agent_compose #222

New issue

Closed

opened 2026-06-16 01:58:47 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-06-16 01:58:47 +00:00

Owner

Part of epic #220

Emit a mount-eligibility manifest from `generate_agent_compose`

The rule for which repos a harness may mount (e.g. claude mounts everything, codex only flight-deck) is the same scope logic agentic_os.generators.generate_agent_compose already computes. ward must read that decision, not re-implement it, so there is a single source of truth and no drift.

Scope

Extend the agent-compose generator to emit a machine-readable mount-eligibility manifest: for harness H on this host, the set of mountable repos (resolved to ~/projects/<org>/<repo> paths).
Include the always-on default mount set in the manifest so ward mounts them regardless of task: coilyco-bridge/lore (agent knowledge), coilyco-flight-deck/agentic-os (aos - doctrine + the repo you edit the harness in), coilyco-bridge/agentic-os-kai (aosk - operating context). aosk has no impl ticket of its own but is a default mount.
Place it where ward can read it deterministically (alongside the existing ~/.config/agent-compose/ output - confirm path here).

Out of scope

ward's consumption of the manifest (ward, child of #220).
Image build (sibling aos ticket).

Notes

The eligibility decision becomes data produced by aos, read by ward at compose-generation time - the pre-flight step is a read, not new judgment in ward.
Reuse the existing per-host scope filtering (work-overlay SSM subdir, primary-org set) rather than a parallel allowlist.

Part of epic https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/issues/220 ## Emit a mount-eligibility manifest from `generate_agent_compose` The rule for which repos a harness may mount (e.g. claude mounts everything, codex only flight-deck) is the same scope logic `agentic_os.generators.generate_agent_compose` already computes. ward must **read** that decision, not re-implement it, so there is a single source of truth and no drift. ### Scope - Extend the agent-compose generator to emit a machine-readable **mount-eligibility manifest**: for harness H on this host, the set of mountable repos (resolved to `~/projects/<org>/<repo>` paths). - Include the **always-on default mount set** in the manifest so ward mounts them regardless of task: `coilyco-bridge/lore` (agent knowledge), `coilyco-flight-deck/agentic-os` (aos - doctrine + the repo you edit the harness in), `coilyco-bridge/agentic-os-kai` (aosk - operating context). aosk has no impl ticket of its own but is a default mount. - Place it where ward can read it deterministically (alongside the existing `~/.config/agent-compose/` output - confirm path here). ### Out of scope - ward's consumption of the manifest (ward, child of #220). - Image build (sibling aos ticket). ### Notes - The eligibility decision becomes **data produced by aos, read by ward at compose-generation time** - the pre-flight step is a read, not new judgment in ward. - Reuse the existing per-host scope filtering (work-overlay SSM subdir, primary-org set) rather than a parallel allowlist.

coilysiren referenced this issue

2026-06-16 01:59:04 +00:00

Epic: dockerized local dev harness (aos-published image, ward-driven devcontainer) #220

coilysiren added the

label

2026-06-17 07:04:28 +00:00

coilysiren added

headless

and removed

labels

2026-06-18 06:01:10 +00:00

coilysiren commented

2026-06-18 06:42:12 +00:00

Author

Owner

Goose triage - 2026-06-17

Tier: P3 (score 68) - Real backlog item with clear implementation path
Mode: headless - Clear task description, all access needed, single source of truth implementation.

_{Auto-generated by ward exec goose-triage (qwen3-coder:30b), edited in place on each run. Labels are the conclusion; this is the why.}

**Goose triage** - 2026-06-17 - **Tier:** `P3` (score 68) - Real backlog item with clear implementation path - **Mode:** `headless` - Clear task description, all access needed, single source of truth implementation. <sub>Auto-generated by `ward exec goose-triage` (qwen3-coder:30b), edited in place on each run. Labels are the conclusion; this is the why.</sub>

coilyco-ops commented

2026-06-18 08:11:24 +00:00

Member

🔒 Reserved by ward agent claude — container ward-agentic-os-issue-222-claude-414a5fdd on host kais-macbook-pro.local is carrying this issue (reserved 2026-06-18T08:11:23Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent claude` — container `ward-agentic-os-issue-222-claude-414a5fdd` on host `kais-macbook-pro.local` is carrying this issue (reserved 2026-06-18T08:11:23Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`

coilysiren referenced this issue from a commit

2026-06-18 08:25:21 +00:00

feat(agent-compose): emit mount-eligibility manifest (#222)

coilysiren closed this issue

2026-06-18 08:25:21 +00:00