carlos / platform Public

AGENTS.md: the flagship root lives in carloku-infrastructure, pinned to release tags

carloku.com's tofu root moved out of platform-infrastructure into
carlosframework/carloku-infrastructure on 2026-10-01 and now consumes
the platform modules at ?ref=v0.21.0 instead of ?ref=main. Agents
need to know both where it went and that a module change on main no
longer reaches the flagship until a tag is pushed to the GitHub mirror
and the refs are bumped.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
claude agent, operated by paul@keymail.dev f5391dc255d94f1cad6e20a745850f21d5ff5380 parent 88abfae
1 file changed, +14 −3
  • AGENTS.md +14 −3

CI passed — run details

diff --git a/AGENTS.md b/AGENTS.md
index 9415e5890..d42abaf7a 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -323,9 +323,20 @@ anything.
## Deploy reality (2026-08-02; convergence rewritten 2026-08-08)
- Deployment-specific facts (which apps live where, box names, accounts,
- ship/promote scripts) live in the private `platform-infrastructure`
- repo, not here. The signing key comes from the deployment's secret store
- inside those scripts, never a terminal.
+ ship/promote scripts) live in private deployment repos, not here:
+ `carlosframework/carloku-infrastructure` for the flagship (carloku.com,
+ split out 2026-10-01; the tofu root is the repo root) and
+ `carlosframework/platform-infrastructure` for dev and the design docs.
+ The signing key comes from the deployment's secret store inside those
+ scripts, never a terminal.
+- **The flagship consumes the platform modules at a release tag**
+ (`?ref=vX.Y.Z` of the GitHub mirror), not `?ref=main`, the same way Tito
+ and any self-hoster do. A module change on main does not reach carloku
+ until a release is cut, its tag is pushed to the GitHub mirror
+ (`git push https://github.com/carlosframework/platform.git
+ refs/tags/vX.Y.Z`; the mirror had no tags past v0.9.0 until v0.21.0 went
+ up on 2026-10-01), every `?ref=` in carloku-infrastructure is bumped, and
+ `tofu init -upgrade` plus a read plan pass. Dev still tracks `main`.
- keymail.dev deploys via `carlos ship`/`promote`, NOT via its repo's legacy
`deploy/deploy.sh` — see that repo's CLAUDE.md.
- **Since main 1fba18f (PR #108, live both boxes 2026-08-08): convergence is