concept-build
Concept build
Goal
Implement a confirmed concept model, or provide the requested implementation plan.
Run only on explicit $concept-build invocation. Use the specifications,
application purpose, scenarios, and confirmed project conventions as input.
Principles
Default to a modular monolith with independently built and tested modules, assembled by server into one process. Business calls follow api, composition, then concept interfaces. Keep public assembly factories separate from business interfaces.
Use ports and adapters. Add Clean layers when domain and application responsibilities need separation. Do not add empty layers or forwarding wrappers. Honor existing confirmed conventions and scoped migrations.
Preserve concept contracts, permissions, correlation, failures, and exclusions. Keep concept, action, and parameter meanings consistent across specifications, code, and logs. Leave model gaps open.