Every slice of the Alderline CRM travelled the same ring: idea, scope, details, build, test, deploy, and back with what was learned. See it three ways. As a ring. As a Linear board that plays six weeks in a minute. As one issue traced from a café's question to a release note.
The lifecycle is the contract between the agents. Each stage has an owner, a Linear state, a way in and a way out. Bellows moves an issue forward only when the exit rule is met. It moves an issue back only when Gauge files a defect. Priya sits at the gates and nowhere else.
The dates are the fact sheet's: kickoff 3 Aug, live to Sam 4 Sep, ALD-42 deployed 15 Sep, today 21 Sep. The order of the slices inside each week is illustrative. A card that jumps from In Test back to In Progress is a defect. A card with Priya's avatar is waiting on a gate.
Idea to deploy and round again. Why the stages exist and who owns each one.
Read the chapter → ⚙Chapter 11 · BellowsThe dispatcher that moves the cards, asks the gates and writes the telemetry the dashboard reads.
Read the chapter → ▤The dashboardHow much each agent worked, what it did, and what the crew learned along the way.
Open the dashboard →