Ideas made executable
Notes on code that keeps its shape.
Practical guides, project stories, and comparisons for teams that want architecture to survive everyday delivery.
Written from the work behind ArchUnitTS, ArchUnitPython, and the wider ArchUnit family.
Latest writing
Architecture is easier to protect when the reasoning is shared.
Start with the project origin, choose a practical guardrail, or explore architecture testing in TypeScript and Python.
ArchUnitTS vs. tsarch in 2026: which architecture test should you choose?
A hands-on comparison of maintenance, correctness, project resolution, features, and performance for TypeScript architecture testing.
Fitness functions for AI-generated code
Why deterministic architecture feedback matters when software changes faster than humans can review every edge.
Your Python Architecture Should Be Tested, Not Just Documented
How ArchUnitPython turns dependency rules, layer boundaries, diagrams, and code metrics into tests your CI can enforce.
Architecture testing for fast-growing Python systems
How executable boundaries help Python services, data platforms, and AI projects grow without losing their shape.
Architecture tests and lint rules solve different problems
A practical guide to choosing editor-fast import rules, graph-aware architecture tests, or both.
Why ArchUnitTS exists
The practical need that started one TypeScript library and grew into an architecture-testing family.