Implementations

One spec, several builds. Your Spec says what your project does. An implementation is one build of it:

• d2: your project's own apps, pages and rules, run by d2 and built by your designer. Every project has one: Impl-d2.
• code: a build on a stack (a TypeScript server, an iPhone app…), in a repository, by coders.
• builtin: d2 itself, on d2spec only.

Open it from Implementations. Each row is a topic, Impl-<name>: open it to read or edit its description, scope, stack, deploy and its coders' start prompt.

Add one with + New implementation (Executive and Conductor): describe it in your words, pick what it covers (all of the Spec, or some features and journeys), its kind and stack, where it lives and who builds it. Creating it makes its topic and docs, and gives your designer an item to plan its first tickets, which wait for your send.

Leads and follows. One build leads: a change is built there first. A follower builds the same change once the lead's is released, and you can cap how far behind it may fall. A build can also go in parallel.

From its row: Pause (its tickets wait, its coders take nothing new), Make lead, Retire.