How a change ships
This note comes from self-directed R&D, the fourth of six on how I build with AI. Every change takes the same path, and the numbers at the end set the next goal.
A person sets the goal and the number in Linear. Claude Code opens the PR in GitHub, where the checks run. Vercel previews it, then releases it.
Once it's live, the app's billing, product and CRM records load into MotherDuck daily, and PostHog exports its events there too. Metric views sit on top, with one ID and one definition per metric, and the dashboards show their SQL.
Then a person reads the numbers and sets the next goal. Granola calls explain why the numbers moved.
Agents carry the middle. A person starts it and a person closes it. Every key lives in Infisical, and scripts fetch them when they run, so no key sits in a repo.
