Tenant Launch Runbooks
Tenant launch projects coordinate launch work. Tenant runbooks and release evidence prove that the configured tenant flow is ready to ship.
Required Artifacts
| Artifact | Purpose |
|---|---|
project-brief.md | Launch scope, project URL, capabilities, channels, and high-level gates. |
launch-runbook.md | Step-by-step launch procedure, source refs, owners, hold criteria, and post-launch review. |
launch-checklist.md | L0-L9 phase checklist and gate checklist. |
release-evidence.md | Proof for config, content, docs, Flow Studio, permissions, integrations, smoke tests, and go/hold decisions. |
Current Launch Packs
| Launch | Project | Runbook | Evidence |
|---|---|---|---|
| FiestaGenius Event Submission MVP | Org project migration pending (old personal Project #5) | Runbook | Evidence |
| Mi Gente DMV Submission Tool MVP | Org project migration pending (old personal Project #6) | Runbook | Evidence |
| RugbyMonkey Community Events MVP | Org project migration pending (old personal Project #7) | Runbook | Evidence |
| GoLatinDance Operations Source Ingest Pilot | Org project migration pending (old personal Project #8) | Runbook | Evidence |
Gate Standard
Every launch needs evidence for:
- capability profile review
- website/content review or explicit not-applicable decision
- public FAQ/help review or explicit not-applicable decision
- operator/admin docs review or explicit not-applicable decision
- Flow Studio desktop and mobile walkthrough
- permission and visibility review
- public-safe demo data review
- integration smoke tests for enabled services
- rollback and support path
- go or hold decision