templates: suffix the seeds `-box`, and follow rig's tenant role rename #123

New issue

Closed

opened 2026-07-19 23:54:41 +00:00 by dan-claude-bot · 0 comments

dan-claude-bot commented

2026-07-19 23:54:41 +00:00

(Migrated from github.com)

heavy-duty/rig#76 gives rig role names a family suffix: fleet machines take -server, box tenants take -box. The tenant roles this repo seeds become claude-box, codex-box, grok-box, staging-box, and each template BOX_BOOTSTRAP_ROLE has to follow — rig hard-cuts the old names, so a seed still saying claude mints a box that fails its own bootstrap.

Also rename the templates themselves

templates/claude   ->   templates/claude-box
templates/codex    ->   templates/codex-box
templates/grok     ->   templates/grok-box
templates/staging  ->   templates/staging-box

The argument against is that box template namespace only ever holds guests, so the suffix carries no information here — box new --template claude is unambiguous on its own. The argument for wins anyway: the template name and the role name are read side by side, in box.env, in the docs, and in every runbook, and having them differ by a suffix invites exactly the "which one is this" pause the rename exists to remove. One vocabulary across both repos beats a locally-minimal one.

blank keeps its name — it seeds no tenant role and has nothing to agree with.

Depends on rig landing first

Hard cut on both sides, so ordering matters: rig#76 tenant rename merges, then this. A box seed naming claude-box against a rig that predates the rename dies at mint, and box templates install rig from RIG_REF (default main).

Scope

templates/* directory renames
BOX_BOOTSTRAP_ROLE values
bin/box — default template, any name in usage or validation
docs/, drill/, test/cli.sh, CHANGELOG.md

heavy-duty/rig#76 gives rig role names a family suffix: fleet machines take `-server`, box tenants take `-box`. The tenant roles this repo seeds become `claude-box`, `codex-box`, `grok-box`, `staging-box`, and each template `BOX_BOOTSTRAP_ROLE` has to follow — rig hard-cuts the old names, so a seed still saying `claude` mints a box that fails its own bootstrap. ## Also rename the templates themselves templates/claude -> templates/claude-box templates/codex -> templates/codex-box templates/grok -> templates/grok-box templates/staging -> templates/staging-box The argument against is that box template namespace only ever holds guests, so the suffix carries no information here — `box new --template claude` is unambiguous on its own. The argument for wins anyway: the template name and the role name are read side by side, in `box.env`, in the docs, and in every runbook, and having them differ by a suffix invites exactly the "which one is this" pause the rename exists to remove. One vocabulary across both repos beats a locally-minimal one. `blank` keeps its name — it seeds no tenant role and has nothing to agree with. ## Depends on rig landing first Hard cut on both sides, so ordering matters: rig#76 tenant rename merges, then this. A box seed naming `claude-box` against a rig that predates the rename dies at mint, and box templates install rig from `RIG_REF` (default `main`). ## Scope - [ ] `templates/*` directory renames - [ ] `BOX_BOOTSTRAP_ROLE` values - [ ] `bin/box` — default template, any name in usage or validation - [ ] `docs/`, `drill/`, `test/cli.sh`, `CHANGELOG.md`

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: heavy-duty/box#123

No description provided.

templates: suffix the seeds -box, and follow rig's tenant role rename #123

Also rename the templates themselves

Depends on rig landing first

Scope

templates: suffix the seeds `-box`, and follow rig's tenant role rename #123