carlos / platform Public

docs: carlos commands assume no infra/box access (Paul's rule, 2026-08-08)

Recorded in CLAUDE.md as the design-side corollary of operate-via-API,
and folded into the carlos-deploy spec §6.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Paul Campbell 2 months ago c933ebdca09946911c70d96857c97d612ec10654 parent a02ebc6

2 files changed, +9 −1

diff --git a/CLAUDE.md b/CLAUDE.md

index 67bb9728e..75dbdc449 100644

--- a/CLAUDE.md

+++ b/CLAUDE.md

@@ -41,6 +41,12 @@ of working around it. Box-local-only counts as a gap too. (2026-08-06:

disk, so an agent went to Systems Manager to run it — the missing API-backed

remote form was the bug.)

+The design-side corollary (Paul, 2026-08-08): **every `carlos` command is

+designed for a user with no access to the underlying infra and no box

+commands.** The command alone must complete the job — no follow-up SSM

+session, AWS console visit, or on-box verb may be required for it to

+deliver or verify its result.

## Build & test

- `go build ./...`, `go vet ./...`, `go test ./... -count=1` — all clean, all

diff --git a/docs/superpowers/specs/2026-08-08-carlos-deploy-design.md b/docs/superpowers/specs/2026-08-08-carlos-deploy-design.md

index 6122f2550..743a54365 100644

--- a/docs/superpowers/specs/2026-08-08-carlos-deploy-design.md

+++ b/docs/superpowers/specs/2026-08-08-carlos-deploy-design.md

@@ -154,7 +154,9 @@ fix, and the instance-provisioning design's own recorded preference).

## 6. The verb: `carlos deploy`

Member CLI, console-API surface — no AWS access, per the operate-via-API

-rule. One command:

+rule and its design corollary (Paul, 2026-08-08): every `carlos` command

+assumes a user with no access to the underlying infra and no box commands;

+the command alone must complete and verify the job. One command:

```

carlos deploy [-target linux-arm64] [-channel <ch>] [-host <host>] [-timeout 120s]