Evidence before ceremony
A decision becomes useful when a team can see what was evaluated, why it failed, and how to respond.
Our principles
Build the signal teams will keep listening to.
These ideas guide our APIs, analysis engines, documentation, community work, and the way we help organizations adopt architecture tests.
Native before uniform
Shared concepts should create coherence, not force every ecosystem into an API designed somewhere else.
Small rules before broad programs
Start with one important boundary. Expand only after the feedback proves precise enough to trust.
Explanation is part of correctness
A technically correct failure that nobody can understand is not yet a good developer tool.
Open work compounds
Source, examples, documentation, and design discussion let one ecosystem strengthen every other one.
Change is a first-class outcome
Architecture rules exist to support deliberate evolution, not to make yesterday’s structure permanent.
Principles in practice
See how the model becomes working software.
Walk through source extraction, dependency resolution, graph construction, fluent rules, and evaluation across Python and TypeScript.