Conductr

Development read as a score rather than a loop. Three processes run as independent voices: Orchestrate turns issues into merged PRs, Idle cycles round robin through coverage, security, architecture and performance and files issues where they slip, and Playtesting sits a human down with a prototype and comes back with new questions. Drawn as a flowchart they look like one machine, and you start reasoning about what triggers what and who is waiting on whom. Drawn as drum notation — instruments stacked vertically, time running to the right — nothing triggers anything. They are voices that happen to line up. The shift that buys you is scheduling, and the shapes are different. Orchestrate ticks every half hour, right round the clock. Idle runs all day too, but in investigations of an hour or two, depending on how far a check has to dig. Playtesting is the long one, and the only voice that needs a person awake. You don't schedule a loop. You score a day. None of it is specific to code: any project with recurring work has these voices — something pushing the work forward, something quietly checking it, and something that needs a person in the room.

• GitHub
• Elevator pitch
• Pocket zine