Feat: User Chooses Artifact Store Mode + Engram Limitations Documented
Artifact Store Mode Prompt
The SDD orchestrator now asks the user which artifact store they want when starting a new change (/sdd-new, /sdd-ff, /sdd-continue):
engram— Fast, no files. Solo work, quick iteration.openspec— File-based, committable, team-shareable, full git history.hybrid— Both: files for team + engram for recovery.
Previously, engram was silently used as default whenever available. Now the user makes an informed choice.
Engram Limitations Documented
Honest documentation of what engram mode does NOT provide:
- No iteration history: re-running a phase overwrites the previous version (upsert behavior)
- Not shareable: engram is a local database, team members cannot see SDD artifacts
- Partial audit trail: archive saves a summary report, not the full artifact folder
This is documented in three places:
sdd-initoutput (shown to user when initializing with engram)persistence-contract.md(mode comparison table + limitation section)engram-convention.md(upsert behavior note)
For team projects or auditable work, openspec or hybrid is recommended.