Skip to content

docs(claude): E3 staging hibernation policy #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dndungu merged 1 commit into from
Apr 7, 2026
Merged

docs(claude): E3 staging hibernation policy #7

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,10 @@ Cross-repo planning and documentation lives in a dedicated git repo: `github.com

Work in this project is typically cross-repo. Always read/update the plan in the shared docs repo, not a per-repo copy. Commit docs changes via PR to `sirerun/docs` independently from code PRs.

## Staging Environment — HIBERNATED

`sire-staging.run` is temporarily hibernated (E3 in the shared docs/plan.md) to reduce cloud costs until funding closes. Do not deploy or test against staging. Tests target production using dedicated `qa+bot@sire.run` accounts in sandboxed workspaces. Hibernated (deleted): staging Cloud SQL, Redis, GKE. Preserved: secrets, Artifact Registry, DNS, KMS, IAM, Pulumi state. Revival: revert E3 gates and `pulumi up --stack staging`.

## No Manual DevOps — IaC + Release Pipeline Only

Production and staging are managed exclusively through IaC and the CI/CD release pipeline. Banned: `kubectl set/edit/scale/patch/delete` and `kubectl apply` against staging/prod, `gcloud secrets create/add/delete` and other imperative `gcloud` mutations, direct prod DB writes, hot-patching pods, re-tagging or force-pushing. Required path: edit IaC → PR → CI → rebase merge → tag release → deploy workflow → verify via workflow checks. Read-only diagnostics (`kubectl get/describe/logs`, `gcloud ... list/access`, `gh run view`) are fine. Agents: never run mutating commands against live infra; open a PR.
Expand Down
Loading