project-spine-rationalelisted

# Local rationale review **Goal:** help the user review `.project-spine/exports/rationale.md` before they share it through their normal channel. The public OSS CLI generates the file locally; it does not publish hosted rationale URLs. ## Prerequisites 1. Project compiled — `.project-spine/exports/rationale.md` exists. If not, switch to project-spine-kickoff. 2. Generated outputs are current — run `spine drift check` first if the user mentions stale instructions or changed inputs. ## Step 1 — inspect the rationale ```bash sed -n '1,220p' .project-spine/exports/rationale.md ``` Review the headings and content with the user. Do not paste the whole file into a public channel unless they explicitly ask. ## Step 2 — check client-safety Before the user shares the rationale, call out these sections: - **Risks** — may contain internal language that should be softened. - **Constraints** — may mention vendor costs, private process, or trade secrets. - **Warnings** — may reveal missing brief details or repo uncertainty. - **Assumptions** — should be phrased as assumptions, not promises. If anything needs changing, edit the upstream `brief.md` or design inputs and rerun `spine compile`. Do not hand-edit `rationale.md` unless the user accepts that drift will be reported later. ## Step 3 — prepare a shareable note If the file is safe, summarize it into a short client note: ```text Here is the Project Spine rationale generated from the current brief and repo. It captures goals,