Ship the standalone Go aos composed-container launcher #637

New issue

Closed

opened 2026-07-23 09:47:47 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-23 09:47:47 +00:00

Member

Goal

Ship a Ward-free aos CLI that launches the AOS dev-base image as a composed agent while keeping agent-compose as the identity compiler.

Command contract

aos --role engineer acompose -- codex

The launcher always bind-mounts the current working directory as the writable workspace. It infers the harness layout from the command after --, composes the requested role from the AOS provider snapshot in the image, projects the bundle into the container HOME, and execs the harness.

Substrate boundary

AOS owns the reusable runtime substrate primitive because AOS already owns the dev-base image, the public substrate roster, and the baked mirror seeds. The launcher hydrates fresh read-only /substrate/<name> reference trees through a shared mirror-cache volume. Ward keeps governance: fresh target clones, repo grants, credentials, reservations, reaping, and landing policy.

Acceptance

The CLI is Go and installs as aos.
CWD is always mounted read-write under /workspace and becomes the container workdir.
The image includes aos, agent-compose, the AOS provider snapshot, and its substrate seed manifest.
acompose verifies and home-projects a role bundle before exec.
No Ward command, config, bootstrap, authority, or lifecycle participates in the launch path.
Unit tests cover Docker argv, role requests, harness inference, substrate hydration, and failure behavior.
A local container smoke test proves CWD, /substrate, and composed HOME load points.
Documentation specifies a future release pipeline matching agent-compose binaries, checksums, Homebrew, Scoop, and Forgejo automation. The pipeline itself remains a follow-up slice.

## Goal Ship a Ward-free `aos` CLI that launches the AOS dev-base image as a composed agent while keeping agent-compose as the identity compiler. ## Command contract `aos --role engineer acompose -- codex` The launcher always bind-mounts the current working directory as the writable workspace. It infers the harness layout from the command after `--`, composes the requested role from the AOS provider snapshot in the image, projects the bundle into the container HOME, and execs the harness. ## Substrate boundary AOS owns the reusable runtime substrate primitive because AOS already owns the dev-base image, the public substrate roster, and the baked mirror seeds. The launcher hydrates fresh read-only `/substrate/<name>` reference trees through a shared mirror-cache volume. Ward keeps governance: fresh target clones, repo grants, credentials, reservations, reaping, and landing policy. ## Acceptance * The CLI is Go and installs as `aos`. * CWD is always mounted read-write under `/workspace` and becomes the container workdir. * The image includes `aos`, `agent-compose`, the AOS provider snapshot, and its substrate seed manifest. * `acompose` verifies and home-projects a role bundle before exec. * No Ward command, config, bootstrap, authority, or lifecycle participates in the launch path. * Unit tests cover Docker argv, role requests, harness inference, substrate hydration, and failure behavior. * A local container smoke test proves CWD, `/substrate`, and composed HOME load points. * Documentation specifies a future release pipeline matching agent-compose binaries, checksums, Homebrew, Scoop, and Forgejo automation. The pipeline itself remains a follow-up slice.

coilyco-ops referenced this issue

2026-07-23 10:06:44 +00:00

Publish the Go aos CLI through Forgejo, Homebrew, and Scoop #639

coilyco-ops referenced this issue from coilyco-flight-deck/ward

2026-07-23 10:06:51 +00:00

Consume the released AOS substrate primitive in Ward containers #1533

coilyco-ops referenced this issue from a commit

2026-07-23 10:09:18 +00:00

feat: ship standalone composed-container launcher (closes #637)

coilyco-ops closed this issue

2026-07-23 10:09:18 +00:00

coilyco-ops referenced this issue