Development factory
Build & AuditDevelopment Factory
Take a repo, feature request, or half-shaped delivery idea and turn it into a mapped, shaped, planned, and verified implementation path.
Subprocesses
5 stages
Entry points
2 ways in
Route variants
4 visible paths
Outcome
Move from scattered delivery context to a build-ready phase plan with an explicit verification gate at the end.
Two valid entrypoints: map an existing codebase or shape the project from a brief.
Research and planning stay explicit before implementation work begins.
The last step is verification against plan, not a vague sense that the work is probably done.
Path from A to B
The factory stays readable all the way through the handoffs.
Each route is a distinct path through the same factory — different starting conditions, priorities, or team setups that lead to the same outcome via different stage sequences.
Path variant
Map Codebase to Verify Phase
Map -> Shape -> Research -> Plan -> Verify
Path variant
Map Codebase to Verify Phase
Map -> Shape -> Plan -> Verify
Subprocesses
Each stage has a clear job, artifact, and next handoff.
Every stage has a defined input, a clear job, and a specific artifact it hands off to the next step. The operator can enter at any marked entrypoint.
Step
1
MapEntrypointMap Codebase
Map an existing codebase before planning changes
Create a readable orientation map of the codebase, system, or work surface before shaping changes.
Input
A repository or project folder path
Output
Codebase map with architecture, main flows, hotspots, and open questions
Steps in this subprocess
- 1Inspect the repository structure, entry points, and runtime paths
- 2Build an orientation map covering architecture, key flows, hotspots, and open questions