Handbook
Advanced customization
Where safe customization lives in a consumer repository — without treating blueprints/ as an editable scratchpad.
Advanced customization (consumer view)
What it is
Where safe customization lives in a consumer repository — without treating blueprints/ as an editable scratchpad.
When to use it
Use this page when you have baseline adoption working (Project setup checklist) and need project-specific process, tooling, or docs beyond the frozen submodule.
Prerequisites
- First hour or equivalent layout in place.
- Familiarity with Blueprint policy (frozen baseline vs project space).
Steps
Principles
blueprints/— Frozen baseline; changes only per Blueprint policy (upstream bumps, deliberate exceptions).- Project
sdlc/— Your interpretations, principles, and links into the baseline — created byinit-sdlc-workspace.shand owned by the product repo. docs/— Requirements, roadmaps, product docs; structure can follow your org. For a full consuming-repo doc tree template, seesdlc/DOCUMENTATION-STRUCTURE.mdon GitHub (maintainer-oriented layout reference).forge/— Forge config, logs paths, Versona usage — seeded by forge-init and edited for your project.
Extension points (examples)
| Need | Where to work |
|---|---|
| Custom SDLC wording for this product | Project sdlc/ Markdown; link to blueprints/sdlc/ where useful. |
| Cursor rules and tasklets | .cursor/ and scripts under blueprints/.../forge/setup/ invoked from your repo root; generated files in .cursor/rules/. |
| CI that checks blueprint presence | Your pipeline YAML at repo root; call test -f blueprints/sdlc/README.md or run upstream check scripts. |
| Extra methodology reading | Consume selectively from blueprints/sdlc/methodologies/ — do not fork the whole tree unless policy requires it. |
How to verify success
- A newcomer can still follow first hour without undoing your customizations.
- Submodule updates do not routinely conflict with files you own under
sdlc/,docs/,forge/.