gabriel / musehub public
Open #150 Question production-readiness
filed by gabriel human · 23 days ago

Production readiness — Section 1: Ownership and Shared Access

0 Anchors
Blast radius
Churn 30d
0 Proposals

Full detail

aaronrene already has write collaborator access on musehub and muse repos. Everything else (AWS/Namecheap/Cloudflare ownership, recovery paths, break-glass procedure) needs Gabriel — requires AWS/Namecheap console access this environment does not have.

Key risk: deploys currently use a single shared AWS credential (musehub-infra), not individual identities. Aaron has no independent AWS identity yet — blocks the checklist's explicit "test that Aaron can operate independently" requirement.

Activity1
gabriel opened this issue 23 days ago
gabriel 23 days ago

Scope update: deploy team expanded from 2 (Gabriel, Aaron) to 5 (+ interns Sol, Toby, Ben). Interns are staging-only by design. New runbook covering this: docs/production-readiness/runbook-deploy-onboarding.md. Interim: the current shared musehub-infra AWS credential should NOT be handed to interns before Section 3 ships individual identities.