Writing · Architecture Note

Large software architecture change across service boundaries

A project note on moving layers and tiers without losing the thread. · Published May 26, 2026

Originally published as a Substack note. Subscribe there for the latest essays, notes, and frontier work.

Large software architecture change of a project to move different layers and tiers around service boundaries.

Test driven so something sensible was on the other side.

This is a fun project so it just needed to work “good enough for me”. He’s the /goal usage report.

Goal usage report from the architecture refactor note
The /goal usage report from the architecture boundary change.

Why keep this note

Small project notes are often the receipts that matter later. This one captures the practical shape of a real architecture move: boundaries changed, tests carried the project through the churn, and the finish line stayed intentionally modest.

The important part is not that the refactor became perfect. It is that the change crossed layers and tiers without letting “architecture” become an excuse to stop shipping.