forked from molecule-ai/molecule-core
ded10a0660
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) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| architecture.md | ||
| canary-release.md | ||
| database-schema.md | ||
| event-log.md | ||
| memory.md | ||
| molecule-technical-doc.md | ||
| org-api-keys.md | ||
| overview.md | ||
| partner-api-keys.md | ||
| provisioner.md | ||
| saas-prod-migration-2026-04-19.md | ||
| staging-environment.md | ||
| technology-choices.md | ||
| tenant-image-upgrades.md | ||
| wildcard-dns-proxy.md | ||
| workspace-tiers.md | ||