Skip to content

docs(adr): agent deployment — template/skills bundles → provider-tagged provisioning - #63

Merged
brettchien merged 2 commits into
mainfrom
docs/adr-agent-deployment-templates
Aug 16, 2026
Merged

docs(adr): agent deployment — template/skills bundles → provider-tagged provisioning#63
brettchien merged 2 commits into
mainfrom
docs/adr-agent-deployment-templates

Conversation

@brettchien

Copy link
Copy Markdown
Contributor

Direction ADR for the deployment vision we aligned on in-thread (2026-08-15).

The idea

Studio should stand up agents, not just observe them. Grounded on three facts:

  • An agent = a prebuilt image tag + a plain-file bundle (config.toml + persona + .claude/skills). Nothing in an agent's identity needs compiling.
  • Compilation is CI/CD, never the deploy path — Studio consumes an image tag.
  • The runtime isn't always ECS — k8s is on the roadmap, so deploy is provider-tagged from the start.

Decision (summary)

  • Studio holds a template/skills library; composes a per-agent bundle (template ⊕ overlay, last-writer-wins).
  • Provision via a provider-tagged RuntimeDriver: pick an image tag + push the bundle to the runtime's file carrier (S3 state for ECS via pre_seed, ConfigMap/volume for k8s) + apply the workload. The driver is the only layer that knows S3-vs-ConfigMap.
  • Credential/region binding reuses the hermetic, provider-tagged approach from feat(desktop): provider-tagged, hermetic oab-mcp target (backend) #60; desired state records into the Fleet Store (ADR: Fleet Store & Control-Plane State Ownership #18) when it lands.

Boundaries

Status: Proposed (draft) — direction alignment; open questions in §6 (bundle transport, template storage, skills-by-reference, image/file boundary).

🤖 Generated with Claude Code

brettchien and others added 2 commits August 15, 2026 23:42
…ed provisioning

Studio stands up agents (not just observes): an agent = a prebuilt image tag +
a plain-file bundle (config.toml + persona + skills). Studio holds a
template/skills library, composes a per-agent bundle (template ⊕ overlay), and
provisions it via a provider-tagged driver — pick an image tag + push the bundle
to the runtime's file carrier (S3 state for ECS, ConfigMap/volume for k8s) +
apply the workload. No build in the deploy path (compilation is CI/CD). Defers
#49 Part D (remote editing of a running agent's files). Relates to #18 (desired
state) and #60 (provider-tagged hermetic target).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Direction greenlit by Brett (2026-08-16). Slices 1&2 (template/skills
library + compose; ECS provision) to follow.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@brettchien
brettchien merged commit 3982f87 into main Aug 16, 2026
1 check passed
@brettchien
brettchien deleted the docs/adr-agent-deployment-templates branch August 16, 2026 06:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant