Architecture: Where should session documentation files be stored?

Documentation for Sessions

🏗️ Architecture: Where should session documentation files be stored?

Date: 2026-01-22
Time: 19:22:16 UTC
Session: editor2-58.13
Agent: backend
Confidence: 92%
Status: ✅ Documented


📋 Decision Context

Question:

Where should session documentation files be stored?

Task: Document the dual-storage architecture for session documentation


🎯 Decision Made

Chosen:

Both locally AND synced to MongoDB

Options Considered:

  1. Only in MongoDB (docs-database)
  2. Only locally in docs/english/sessions/
  3. Both locally AND synced to MongoDB

💭 Reasoning

Local docs serve multiple purposes: (1) Source of truth during development - files are created/edited locally first; (2) docs-angular app reads from local files during development; (3) Git version control preserves history; (4) Offline access for developers. MongoDB sync provides: (1) Production searchability in docs-angular; (2) Cross-referencing with decisions via docUrl field; (3) Fast full-text search. The sync script (sync-session-docs-to-mongodb.js) pushes local docs to docs-database, making them searchable in production while preserving local development workflow.


📁 Files Involved


🔗 Related


Auto-generated by MCP Smart Consolidation