strategic-programming

Bold terms are defined in GLOSSARY.md.

Context

Three entry points, each with a different path through the steps:

• New design — full process
• Refactor — skip step 1 (existing modules are the seams). Run steps 2-5 against the refactored design.
• Bug fix — skip to step 3. If the fix touches multiple modules, the seam is wrong — redesign, then step 5.

Steps

1. Map the seams

Identify what's likely to change. Each likely-to-change decision gets its own seam — a module boundary the rest of the system must not cross.

Criterion: Every likely change is assigned to exactly one module. You can name what each seam hides.

2. Design for depth