architecture
Boundaries, ports and adapters, and the difference between an architecture written in a document and one a machine can check.
4 posts
Permissions are two problems, not one
Every authorization engine I've tried answers "can this user see this?" beautifully, and "what can this user see?" badly. That second question is where I keep getting stuck.
The cost of writing collapsed. The cost of checking didn't
Obrussa is an approach I'm trying right now: treating AI-assisted development as a system problem — explicit context, a blocking gate, durable state — because the bottleneck moved from producing code to verifying it.
Architecture as a standard, not a suggestion
Where AI-assisted coding actually fails isn't algorithms, it's architectural boundaries. So I stopped leaving structure to the model: hexagonal clean architecture on NestJS, with the dependency rule enforced on the import graph and a composition root that is the only place allowed to know every piece.
Veive: turning a blockchain account into something you can program
In 2024 I built a modular smart account protocol for the Koinos blockchain. The absence of the piece everyone else builds on turned out to produce a stronger authorization model than the one I was copying.