Architecture: How should drafts system work for platform changes?

Documentation for Sessions

🏗️ Architecture: How should drafts system work for platform changes?

Date: 2026-01-16
Time: 23:12:53 UTC
Session: editor2-49.8
Agent: architecture
Confidence: 85%
Status: ✅ Documented

📋 Decision Context

Question:

How should drafts system work for platform changes?

Task: Design drafts system for platform builder

🎯 Decision Made

Chosen:

Git branches map to drafts: main=production, draft/{name}=draft versions, preview/{id}=temporary previews. Tags for versioned releases.

Options Considered:

  1. MongoDB version documents
  2. Git branches
  3. Separate draft collections
  4. Copy-on-write in S3

💭 Reasoning

  1. User explicitly wanted git-style branching for drafts system. 2. Branches provide isolation for work-in-progress changes. 3. Merge to main = publish to production. 4. Tags (v1.0.0) = versioned releases for rollback. 5. Preview branches = temporary deployments for review. 6. Native git semantics, no custom versioning logic needed.

📁 Files Involved

🔗 Related

Auto-generated by MCP Smart Consolidation