MIT
/open source
/C4 · DDD · governance
Architecture that lives here,
and holds whatever builds from it.
One model, drawn by you or by AI, that becomes the harness for the code.
Made for
- Architects who model the architecture rather than draw it: one graph, eight views, the decisions next to the boxes — and, for the first time, a reader that acts on the model. Open Studio →
- Vibe coders who build fast with agents and still want to know, a month later, what they have: the agent reads the model first, and the model keeps up with the code. Connect your agent →
- Business analysts who want requirements that stay attached to the architecture: needs, EARS requirements, scenarios, processes and states, linked to the systems that satisfy them. Needs, requirements, processes →
- Tech leads bringing agents into a team: one picture of the system for people and agents alike, with the decisions where everyone, and everything, reads them. Start a model →
- Teams cutting the cost of AI agents get the system as a model instead of re-reading the codebase every session: shorter context, fewer wrong turns, less code thrown away. See it on our own repo →
- Companies with AI to govern a harness for the agents: decisions, requirements and fitness functions as linked elements, CI that fails when the code drifts from them, concern packs for what you would forget. Explore the Hub →
Six ways teams use it, from a better drawing to a harness for the code →