Make AOS guarded and composed by default, ship aoscompose and aosward #828

New issue

Closed

opened 2026-07-31 09:09:01 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-31 09:09:01 +00:00

Member

Outcome

Every AOS agent launch includes composed role context and the standalone AOSguard surface.

Ship two convenience entry points:

aoscompose is the explicit easy spelling for a standalone composed-and-guarded AOS launch.
aosward launches the same composed-and-guarded surface through Ward.
Plain aos keeps the standalone composed-and-guarded default.

Compatibility

Preserve compatible argument parsing for existing launch callers.
Existing positive capability flags may remain accepted for compatibility, but no AOS agent-launch entry point silently omits composition or AOSguard.
A legacy or incompatible command shape that requests Ward without using the Ward-owned lifecycle fails closed and points to aosward.
Fold #810 fail-closed coverage into this launch-contract change or close #810 as superseded after equivalent acceptance is proven.

Acceptance

aos and aoscompose launch the standalone composed-and-guarded surface.
aosward launches the composed-and-guarded surface through Ward.
Invocation, compatibility, and fail-closed behavior have focused tests.
Release packaging ships both convenience commands.
Launcher documentation names the three canonical spellings and their lifecycle boundary.

## Outcome Every AOS agent launch includes composed role context and the standalone AOSguard surface. Ship two convenience entry points: * `aoscompose` is the explicit easy spelling for a standalone composed-and-guarded AOS launch. * `aosward` launches the same composed-and-guarded surface through Ward. * Plain `aos` keeps the standalone composed-and-guarded default. ## Compatibility * Preserve compatible argument parsing for existing launch callers. * Existing positive capability flags may remain accepted for compatibility, but no AOS agent-launch entry point silently omits composition or AOSguard. * A legacy or incompatible command shape that requests Ward without using the Ward-owned lifecycle fails closed and points to `aosward`. * Fold #810 fail-closed coverage into this launch-contract change or close #810 as superseded after equivalent acceptance is proven. ## Acceptance * `aos` and `aoscompose` launch the standalone composed-and-guarded surface. * `aosward` launches the composed-and-guarded surface through Ward. * Invocation, compatibility, and fail-closed behavior have focused tests. * Release packaging ships both convenience commands. * Launcher documentation names the three canonical spellings and their lifecycle boundary.

coilyco-ops referenced this issue from a commit

2026-07-31 09:17:54 +00:00

feat: guard and compose every AOS launch

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-31 09:18:06 +00:00

feat: guard and compose every AOS launch #829

coilyco-ops referenced this issue from a commit

2026-07-31 09:24:11 +00:00

feat: add the aoscomposed launch alias

coilyco-ops added the

priority

label

2026-07-31 09:45:39 +00:00

coilyco-ops changed title from ~~Make AOS guarded and composed by default and ship aosward~~ to Make AOS guarded and composed by default, ship aoscompose and aosward

2026-07-31 09:51:24 +00:00

coilyco-ops added the

autonomy

headless

label

2026-07-31 09:51:29 +00:00

coilyco-ops referenced this issue from a commit

2026-08-01 06:16:32 +00:00

fix: expose aoscomposed as a package alias (closes #828)

coilyco-ops referenced this issue from a commit

2026-08-01 06:18:23 +00:00

docs: keep launcher inventory at capability level (closes #828)