Coding agents pay for your architecture in tokens
After my Claude Code community talk, many asked for the harness and architecture I'd built. I can't share SimCorp's code — so I distilled the ideas into Brokkr & Eitri, a public repo named for the dwarf brothers who forged Mjölnir while Loki tried to sabotage them. The right patron saints for architecture enforcement.
Same 80 features, built two ways: vertical slices with contract-only seams vs. an identical Clean Architecture twin. Single-feature task: ~1.6k tokens sliced vs ~5.3k layered. More importantly, sliced stays O(1) as the repo grows; layered grows O(n).
The problem with any architecture like this is that it's too easy to break. So everything that can be enforced at compile time is — Roslyn analyzers, a mutation-test canary that asserts the build fails on a violation, and a Claude Code hook that warns agents when they drift across a seam.