Launch and manage broker-only collaboration clusters #1635

New issue

Closed

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

coilyco-ops commented

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

Member

Outcome

Expose a public Ward lifecycle that starts an empty collaboration cluster with only the supervised dispatch broker. A director or initial peer must not be required.

This is the rendezvous surface for composed agents that attach later. It productizes the broker-only path that Ward's current Compose machinery already uses internally.

Boundary

Ward owns the broker process, authentication token, isolation, Compose project, durable journal, and lifecycle.
Launching the cluster does not require a repository, issue reference, Forgejo credential, role, or initial agent.
The cluster identity follows #1592.
Repository workflows remain an optional higher-level integration.

Acceptance criteria

An operator can launch a broker-only cluster from a directory that is not a Git checkout.
Launch starts the broker service and no director or peer service.
Ward mints and prints the cluster id.
List, status, logs, and stop can target the cluster id without a repository reference.
The broker survives terminal detachment under the existing supervised restart policy.
The launch does not request or project Forgejo credentials.
Starting or stopping one cluster cannot affect another cluster.
Automated tests cover broker-only rendering, startup planning, lookup, cleanup, and the absence of a director.
The public broker documentation and feature inventory describe the new lifecycle.

## Outcome Expose a public Ward lifecycle that starts an empty collaboration cluster with only the supervised dispatch broker. A director or initial peer must not be required. This is the rendezvous surface for composed agents that attach later. It productizes the broker-only path that Ward's current Compose machinery already uses internally. ## Boundary * Ward owns the broker process, authentication token, isolation, Compose project, durable journal, and lifecycle. * Launching the cluster does not require a repository, issue reference, Forgejo credential, role, or initial agent. * The cluster identity follows #1592. * Repository workflows remain an optional higher-level integration. ## Acceptance criteria * An operator can launch a broker-only cluster from a directory that is not a Git checkout. * Launch starts the broker service and no director or peer service. * Ward mints and prints the cluster id. * List, status, logs, and stop can target the cluster id without a repository reference. * The broker survives terminal detachment under the existing supervised restart policy. * The launch does not request or project Forgejo credentials. * Starting or stopping one cluster cannot affect another cluster. * Automated tests cover broker-only rendering, startup planning, lookup, cleanup, and the absence of a director. * The public broker documentation and feature inventory describe the new lifecycle. ## Related * #1592 * #1626 * coilysiren/inbox#309 * coilysiren/inbox#310

coilyco-ops referenced this issue

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

Run generic broker peers without a repository target #1636

coilyco-ops referenced this issue from coilyco-flight-deck/agentic-os

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

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

coilyco-ops referenced this issue

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