docs(adr): Fleet as usage-based grouping + Studio connection model - #33
Merged
Conversation
Records two decided design shifts: - Fleet is a named logical grouping defined by explicit members, decoupled from the physical cluster (schema `[fleet.<name>]` with a `members` list). Lets co-located agents (e.g. orca + mira in cluster oab) be distinct fleets grouped by usage. Tag-selector membership is a deferred follow-up. - Two first-class connection models: reverse-MCP-over-ACP to attach to a running Studio (shared instance + Studio identity, references openab #1447), and a headless standalone oab-mcp for no-Studio use (a "Copy MCP config" launcher). Status: Proposed — a direction-aligning stub; implementation lands in slices. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Address review: the ADR was abstract about connecting. Add a concrete usage guide and a "current usage" section grounded in the always-on ECS agent (Orca): - docs/connecting-an-agent.md: step-by-step for headless oab-mcp (register it as an MCP server; Orca uses its task role as the ambient credential, no profile), the raw-AWS level available now, and the reverse-MCP target; plus the laptop/Copy-MCP-config summary. - ADR §3: "how Orca connects today" — raw AWS now, headless oab-mcp near-term (no new Studio code), reverse-MCP as the target — linking the guide. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Drafted by Orca (
ecs-claude) — flagging authorship (shared GitHub identity).A Proposed ADR recording two design shifts decided with the operator (Brett) in-thread:
Part A — Fleet is a usage-based logical group. A fleet is defined by its members, not by a physical cluster; grouping is decoupled from credential. Schema moves
[[fleet]](array,namefield, keyed bycluster) →[fleet.<name>](map keyed by name) with an explicitmemberslist. This lets co-located agents —oab-prod-orcaandoab-prod-mira, both in clusteroab— be two distinct fleets sharing one cluster/credential, grouped by usage. Membership = explicit list now (decision (a)); tag-selector is a deferred follow-up.Part B — two first-class connection models (not primary + fallback):
oab-mcptools over the outbound/acpWS (mechanism as-built in openab #1447), core proxies to the agent. Shared instance + Studio identity, human-in-the-loop, no NAT/port, no per-agent creds.oab-mcp— for CI / scripts / no-Studio: a "Copy MCP config" action emits a stdio server spec so a headless agent spawns its own instance with its own creds.§4 lists consequences (schema migration;
for_cluster→ fleet-by-name; the config panel evolves from cluster-switch to fleet-switch). §5 lists open questions (reverse-MCP auth/scoping, session↔fleet mapping, tag-selector, cross-account fleets, migration).Stub to align direction — both decisions are made; implementation lands in slices. Relates to the per-Fleet managing identity ADR (#19) and its config panel (#26/#30).
🤖 Generated with Claude Code