Handbook

Adopting: path A (solo / small team)

ICP path A: a sane default SDLC/PDLC text baseline without writing it from scratch.

Adopting Blueprints — Path A (solo developer or small team)

ICP path A: a sane default SDLC/PDLC text baseline without writing it from scratch.

Parent page: Adopting Blueprints — choose this path when you mainly need baseline text and minimal ceremony.

When the decision guide points you to path A.

Blueprints added to your repo (typically submodule at blueprints/). See Adopting Blueprints.

Job to be done: “I want a sane default SDLC/PDLC text baseline without writing it from scratch.”

Step	Action	Verify
1	Submodule (or copy) Blueprints into `blueprints/`.	`test -f blueprints/sdlc/README.md`
2	Add a project `sdlc/` folder (interpretations, principles) — do not edit the copy under `blueprints/sdlc/`; see Blueprint policy.	`sdlc/README.md` exists after init script.
3	Add `docs/product/` when you need capabilities/journeys (seed from product templates).	Optional; structure matches your product docs needs.


Starting situation	Solo maintainer on a small service repo; no shared ceremony yet; Blueprints not in the tree.
Action taken	Add `blueprints/` as a submodule, run First hour, keep interpretations in project `sdlc/` only.
Expected result	`blueprints/sdlc/README.md` present; project `sdlc/README.md` describes your product; no edits under `blueprints/sdlc/` for product text.
What to check	`git status` shows submodule pointer or new `sdlc/` files; your treatment of the frozen baseline matches Blueprint policy.

Same checks as the Verify column above. Then run First hour or Project setup profile for the full checklist.