Generalize the dispatch broker for arbitrary composed agents #1626

New issue

Closed

opened 2026-07-31 08:12:53 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-31 08:12:53 +00:00

Member

Goal

Let the supervised broker launch and connect arbitrary composed agent roles without encoding repository workflow roles into the generic transport.

Acceptance

Broker launch validation accepts any safe role slug and preserves existing engineer and QA behavior.
Generic launches may use a freeform work input without an issue reference.
Broker-launched agents receive authenticated access to a direct message surface.
Messages carry durable ids, stamped sender identity, explicit recipients, and bounded payloads.
Existing issue reservations, PR workflow, recovery, logs, and stop behavior remain unchanged for engineering launches.
Documentation distinguishes generic agent dispatch from optional repository workflow integration.

Coordinates with coilysiren/inbox#309 and coilysiren/inbox#310.

## Goal Let the supervised broker launch and connect arbitrary composed agent roles without encoding repository workflow roles into the generic transport. ## Acceptance * Broker launch validation accepts any safe role slug and preserves existing engineer and QA behavior. * Generic launches may use a freeform work input without an issue reference. * Broker-launched agents receive authenticated access to a direct message surface. * Messages carry durable ids, stamped sender identity, explicit recipients, and bounded payloads. * Existing issue reservations, PR workflow, recovery, logs, and stop behavior remain unchanged for engineering launches. * Documentation distinguishes generic agent dispatch from optional repository workflow integration. Coordinates with coilysiren/inbox#309 and coilysiren/inbox#310.

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

2026-07-31 08:13:00 +00:00

Allow warded launches for arbitrary composed roles #825

coilyco-ops referenced this issue

2026-07-31 08:20:38 +00:00

Define the Ops release-candidate and outcome contract #1627

coilyco-ops referenced this issue

2026-07-31 08:21:28 +00:00

Enforce verified deploy-state transitions per environment #1628

coilyco-ops referenced this issue

2026-07-31 08:21:36 +00:00

Prove issue-to-verified-deployment in a disposable fixture #1629

coilyco-ops referenced this issue

2026-07-31 08:21:52 +00:00

Add an Ops role for verified GitOps deployment handoff #1625

coilyco-ops commented

2026-07-31 08:21:55 +00:00

Author

Member

Downstream consumer recorded: the Ops program in #1625 now builds on this generic broker. #1627 defines the Ops-specific release-candidate and outcome contract, #1628 owns verified deploy-state transitions, and #1629 owns the disposable end-to-end proof. Keep deployment semantics out of #1626.