This SDD root keeps durable planning context close to the code it describes. It stores prompts, approved plans, roadmap
material, and bead state in predictable paths so humans and agents can reference the same artifacts over time. The root
may be the checkout's sdd/ directory or a separate .sase/sdd/ store; run sase sdd path or read SASE_SDD_DIR from
agent environments to locate it.
plans/stores implementation plans. Eachplans/<YYYYMM>/prompts/subdirectory stores the original user prompts or expanded prompt snapshots that led to that month's plans. Plan files requiretier: talefor focused task plans ortier: epicfor larger multi-phase plans.research/stores exploratory findings, prior art, options, critiques, and recommendations that inform later work.beads/stores bead issue data for SDD-backed work tracking.
Prompt, plan, and research files are normally organized under a YYYYMM/ month directory relative to this root. For
example, a prompt at plans/202605/prompts/example.md pairs with plans/202605/example.md, while research lives at
research/202605/example.md. Prompt files should link to their generated plan-like artifact with frontmatter such as
plan: plans/202605/example.md; the plan-like artifact should link back with
prompt: plans/202605/prompts/example.md.
sase sdd listlists SDD markdown artifacts.sase sdd pathprints the effective SDD root; pass a kind such asresearchto print that child directory.sase sdd validatechecks frontmatter links between prompts and plan-like artifacts.sase sdd repair-linksinfers and repairs missing bidirectional links.sase plan searchsearches thesesdd/plans and the machine-local~/.sase/plans/archive by content.sase beadmanages SDD bead issues and epic work.
The canonical top-level directories are plans/, research/, and beads/. Prompt snapshots live under
plans/<YYYYMM>/prompts/. Historical top-level prompts/ and specs/ aliases remain readable during migration, but
new snapshots are written only to the nested layout.