Attach composed agents to repo-free Ward collaboration clusters #851

New issue

Open

opened 2026-08-02 04:43:27 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-02 04:43:27 +00:00

Member

Outcome

Let AOS launch a composed role into an existing Ward collaboration cluster without requiring a repository target or a manually selected agent id.

AOS remains the owner of harness selection, role selection, current Agent Compose bundle production, read-only substrate input, and launcher UX. Ward remains the owner of the broker, cluster lifecycle, peer admission, and runtime isolation.

Required behavior

The AOS Ward adapter accepts an explicit Ward cluster id plus role and freeform work.
The adapter composes the current role bundle and passes it through Ward's provider-neutral staged-home boundary.
The current substrate is available read-only without treating any repository as the execution target.
The ordinary path does not expose or require an agent-id option.
Ward's broker-minted cluster and peer ids are shown in the launch result.
The adapter fails closed when the cluster does not exist, is unavailable, or rejects admission.
Existing repository-backed aosward launches remain compatible.
Agent Compose remains unchanged unless its existing bundle contract proves insufficient.

Acceptance criteria

From a non-repository directory, AOS can compose a role and attach it to a running broker-only cluster.
No repository reference, clone, or Forgejo credential is required.
The peer can exchange direct broker messages with another peer in the cluster.
A nested peer launched through the broker remains attached to the same cluster.
The CLI output names the cluster and broker-assigned peer id.
Dry-run output makes the cluster attach and absence of repository integration explicit.
Focused tests cover argument ordering, context handoff, failure behavior, and repository-backed compatibility.
CLI and Ward integration documentation show the repo-free collaboration flow.

Depends on

## Outcome Let AOS launch a composed role into an existing Ward collaboration cluster without requiring a repository target or a manually selected agent id. AOS remains the owner of harness selection, role selection, current Agent Compose bundle production, read-only substrate input, and launcher UX. Ward remains the owner of the broker, cluster lifecycle, peer admission, and runtime isolation. ## Required behavior * The AOS Ward adapter accepts an explicit Ward cluster id plus role and freeform work. * The adapter composes the current role bundle and passes it through Ward's provider-neutral staged-home boundary. * The current substrate is available read-only without treating any repository as the execution target. * The ordinary path does not expose or require an agent-id option. * Ward's broker-minted cluster and peer ids are shown in the launch result. * The adapter fails closed when the cluster does not exist, is unavailable, or rejects admission. * Existing repository-backed `aosward` launches remain compatible. * Agent Compose remains unchanged unless its existing bundle contract proves insufficient. ## Acceptance criteria * From a non-repository directory, AOS can compose a role and attach it to a running broker-only cluster. * No repository reference, clone, or Forgejo credential is required. * The peer can exchange direct broker messages with another peer in the cluster. * A nested peer launched through the broker remains attached to the same cluster. * The CLI output names the cluster and broker-assigned peer id. * Dry-run output makes the cluster attach and absence of repository integration explicit. * Focused tests cover argument ordering, context handoff, failure behavior, and repository-backed compatibility. * CLI and Ward integration documentation show the repo-free collaboration flow. ## Depends on * coilyco-flight-deck/ward#1592 * coilyco-flight-deck/ward#1635 * coilyco-flight-deck/ward#1636 * coilyco-flight-deck/ward#1637 ## Related * #825 * #810 * coilysiren/inbox#309 * coilysiren/inbox#310

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

2026-08-02 04:43:42 +00:00

Give each Ward collaboration cluster a harness-scoped stable identity #1592

coilyco-ops added the

priority

autonomy

headless

labels

2026-08-02 04:43:50 +00:00

coilyco-ops referenced this issue

2026-08-09 04:23:36 +00:00

docs(agents): claim-triggered front-load rule, and principal-scoped pronouns #980