- 2025 to now
- Designed, built, and operated
- Go, Kubernetes, and MCP
The problem
AI coding agents can produce more change in a day than a team can review in a week. Without structure, nobody can say what was changed, why, or whether it was checked, and the reasoning disappears when the session ends.
The approach
An AI-augmented delivery workflow
- Plan
- Build
- Test
- Review
- Record
Plan
Every piece of work is an item on a board, grouped into plans and projects, with a written description of what done means.
Test first
Tests come first: a failing test, then the change, then the full suite before anything is marked done.
Decide
Strategic choices are recorded as decisions with their context, evidence, alternatives, and success criteria. A decision is never edited; a new one supersedes it.
Run unattended
Unattended runs execute as Kubernetes jobs on their own branch and are handed back for review instead of merging themselves.
Promote
Changes move from development to staging on their own, and to production only as an explicit, separate step.
The outcome
- The same process runs the Visiting Objects platform and this site, so every change on them traces back to an item and a recorded reason.
- Months later, the question of why something was built a certain way has a written answer.