From ded10a0660959afa77c63dbfaf2769302d6c0daa Mon Sep 17 00:00:00 2001 From: Hongming Wang Date: Wed, 22 Apr 2026 14:03:27 -0700 Subject: [PATCH] docs(canary-release): flag as aspirational; link to current state MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The canary-release.md doc describes the pipeline as if the fleet is running — referring to AWS account 004947743811 and a configured MoleculeStagingProvisioner role. Reality as of 2026-04-22: no canary tenants are provisioned, the 3 GH Actions secrets are empty, and canary-verify.yml has failed 7/7 times in a row. Added a top-of-doc ⚠️ state note that: 1. Clarifies this is intended design, not deployed reality. 2. Notes the AWS account ID is historical / unverified. 3. Explains that merges currently rely on manual promote-latest. 4. Cross-links to molecule-controlplane/docs/canary-tenants.md for the Phase 1 work that's shipped, the Phase 2 stand-up plan, and the "should we even do this now?" decision framework. 5. Asks whoever lands Phase 2 to reconcile the two docs. No behaviour change — doc-only. Co-Authored-By: Claude Opus 4.7 (1M context) --- docs/architecture/canary-release.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/architecture/canary-release.md b/docs/architecture/canary-release.md index eb795eda..61eaeeda 100644 --- a/docs/architecture/canary-release.md +++ b/docs/architecture/canary-release.md @@ -2,6 +2,12 @@ How a workspace-server code change reaches the prod tenant fleet — and how to stop it if something's wrong. +> **⚠️ State note (2026-04-22):** this doc describes the **intended design**. As of this write, the canary fleet described below is **not actually running** — no canary tenants are provisioned, `CANARY_TENANT_URLS` / `CANARY_ADMIN_TOKENS` / `CANARY_CP_SHARED_SECRET` are empty in repo secrets, and `canary-verify.yml` fails every run. The AWS account `004947743811` referenced in "Canary fleet" below predates this repo's history and hasn't been verified in-session. +> +> Current merges gate on manual `promote-latest.yml` dispatches, not canary. See [molecule-controlplane/docs/canary-tenants.md](https://github.com/Molecule-AI/molecule-controlplane/blob/main/docs/canary-tenants.md) for the Phase 1 code work that's already shipped + the Phase 2 plan for actually standing up the fleet + a "should we even do this now?" decision framework. +> +> When Phase 2 lands, delete this note and reconcile the two docs. + ## The loop ```