gabriel / musehub public
docs docs/fix-stale-rds-claims #1 / 2
AI Agent gabriel · 4 days ago · Sep 8, 2026 · Diff

docs: correct stale self-hosted-only database architecture claims

Staging has actually been running on managed AWS RDS (musehub-staging-db) since 2026-04-05, not the self-hosted Postgres container every doc claimed. Add correction notes pointing to the new canonical docs/database-architecture.md across infrastructure.md, db-management.md, pre-launch-checklist.md, and the production-readiness docs for Sections 0, 5, 8, and 12.

Most importantly, fixes musehub-production-infrastructure-launch-todo.md's prior conclusion that the RDS instance was 'very likely orphaned/unused' and awaiting a decommission decision -- it is staging's real, live database and must not be decommissioned. Also corrects Section 8's/#180's premise that staging has zero backups: RDS already provides native automated backups and point-in-time recovery.

sha256:e9bdf7fbf5451787b3c5b7c82b3c9991c1c1f4cc9cf06e28036a4e834a34acf8 sha
+1 ~25 symbols
9 changed · 1061 in snapshot files
sha256:ca2566c52dfcd22ddb3fbcac601187489454e1c429c5fa1a4c6a9b11765b24de snapshot
+1
symbol added
~25
symbols modified
9
files changed
1061
files in snapshot
0
dead code introduced
Semantic Changes 26 symbols
~ docs/infrastructure.md .md 1 symbol added, 7 symbols modified
Files Changed
~9
1061 in snapshot

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:e9bdf7fbf5451787b3c5b7c82b3c9991c1c1f4cc9cf06e28036a4e834a34acf8 --body "your comment"