Strategy folder pattern
Strategy folder pattern
How a strategy level is laid out in this repo. Agreed 2026-11-20 with the SoR long-term and 2027 levels as the first two cases.
One folder per level, under its organisation (e.g. sor/long-term/, sor/near-term/). Don't mix levels in one document.
| File | What it is | When it appears |
|---|---|---|
README.md | Short pointer: what the level is, its status, links to the files below. No content of its own. | Always |
<scope>-brief.md | The brief: SCQ (situation, complication, question), criteria, issue tree, inputs, the prompt used. The input to the LTP. | First |
<scope>-ltp.md | Readable LTP write-up: goal tree, current reality, conflict clouds (ASCII), future reality, actions, open questions. | During the LTP |
<scope>.ltp.yaml | LTP state (reasoncommons schema); validator views go in .<scope>.ltp/ | During the LTP |
<scope>-strategy.md | The output: a one-pager, opening with a one-paragraph summary and five bullets, then the page; key detail (actions, briefs for the level below) can follow under "Detail". | At the end |
| Supporting pages | Named for what they are (e.g. engagement-ladder.md), for a piece of reasoning worth sharing on its own. | As needed |
inputs/ | Research and source material, dated where useful (2026-11-growth-research.md). | As needed |
<scope> names the organisation and level so a file makes sense on its own, in a link or a search result: sor-long-term, sor-2027. A year names a one-year level.
Raw inputs (transcripts, dictated comments) go in the repo's raw/ as YYYY-MM-DD-slug.md, not in the level folder. Finalised public strategy goes to life-itself/tao.