FIELD NOTES01
Your architecture rules deserve a linter
Use Go’s syntax tree to turn dependency direction, naming rules, and yesterday’s production bug into CI checks.
Essays, notebooks, and field notes connected by architecture.
Use Go’s syntax tree to turn dependency direction, naming rules, and yesterday’s production bug into CI checks.
Separate the three-year decisions from next month’s tuning knobs, and the document becomes much easier to trust.
Tool protocols and agent protocols solve different boundaries; the alphabet soup gets easier once the arrows are drawn.
Keep UI-shaped reads fast and domain-shaped writes honest, without deploying another service for sport.