Consolidate four deployment guides into a single canonical DEPLOYMENT.md

[robertocarlous]

Summary

The docs/ directory contains four overlapping deployment documents:

• DEPLOYMENT.md
• DEPLOYMENT_GUIDE.md
• DEPLOYMENT_PRODUCTION.md
• PRODUCTION_DEPLOYMENT.md

This creates confusion about which guide is authoritative and leads to instructions getting out of sync.

Proposed Solution

1. Audit all four files for unique content not present in the others
2. Merge into a single docs/DEPLOYMENT.md with sections:
   • Local development (Docker Compose)
   • Staging (Docker)
   • Production (Kubernetes)
   • Environment variables reference
   • Rollback procedure
3. Delete the three redundant files
4. Update docs/DOCUMENTATION_INDEX.md and readme.md to point to the new file

Acceptance Criteria

• Single docs/DEPLOYMENT.md covers all environments
• Three redundant files removed
• No broken links in readme.md or other docs
• Markdown link check CI step passes

[Yusufolosun]

@Yusufolosun has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi Maintainer, Good day
Please can you entrust the implementation of this issue to me. I am a Full Stack Developer and I can deliver maintainable solution that align with your codebase

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Yusufolosun to this issue.

[MarcusDavidG]

@MarcusDavidG has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I can handle this issue and will like to work on it, Please assign thank you.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @MarcusDavidG to this issue.

[trustosaretin]

@trustosaretin has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would love to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @trustosaretin to this issue.

[drips-wave]

Congratulations, @trustosaretin! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @trustosaretin: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[grantfox-oss]

🦊 GrantFox — @trustosaretin has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #230)
2. Your PR will be reviewed by the Neurowealth maintainers

Good luck! Track your progress on GrantFox.

[trustosaretin]

I'd like to work on this issue.

The docs/ directory contains four overlapping deployment documents (DEPLOYMENT.md, DEPLOYMENT_GUIDE.md, DEPLOYMENT_PRODUCTION.md, PRODUCTION_DEPLOYMENT.md) which creates confusion about which guide is authoritative and leads to instructions getting out of sync. This fragmentation increases maintenance burden and risks providing inconsistent deployment information.

My approach

I will audit all four documents, extract unique content from each, and consolidate everything into a single canonical docs/DEPLOYMENT.md file. The consolidated document will be organized by environment type for easy navigation.

Implementation plan

1. Audit existing deployment documents

   • Read all four deployment files to identify unique content
   • Create a mapping of which information exists in which files
   • Identify any outdated or conflicting information between documents

2. Design consolidated structure

   • Create an outline for the new docs/DEPLOYMENT.md with clear sections:
     • Local development (Docker Compose)
     • Staging (Docker)
     • Production (Kubernetes)
     • Environment variables reference
     • Rollback procedure
   • Ensure logical flow from development to production

3. Consolidate content

   • Merge unique content from all four documents into the new structure
   • Resolve any conflicts or inconsistencies between documents
   • Ensure all critical deployment information is preserved

4. Update references and links

   • Update docs/DOCUMENTATION_INDEX.md to point to the new consolidated file
   • Update readme.md to reference the new deployment documentation
   • Fix any broken links that referenced the old files

5. Remove redundant files

   • Delete DEPLOYMENT_GUIDE.md, DEPLOYMENT_PRODUCTION.md, and PRODUCTION_DEPLOYMENT.md
   • Ensure no other documentation references these deleted files

6. Validate documentation quality

   • Run markdown link check to ensure no broken links
   • Review the consolidated document for clarity and completeness
   • Ensure all deployment scenarios are covered

Impact

• Eliminates confusion about which deployment guide is authoritative
• Reduces maintenance burden by having a single source of truth
• Ensures consistent deployment information across all environments
• Improves developer experience with clear, organized documentation
• Prevents documentation drift and keeps instructions synchronized

I'm ready to start immediately and can have a PR up within a reasonable timeline. Happy to adjust the plan if you have preferences on any of the details.