Describe an operation, get a linked set of processes

One flow or a whole system

The model is told to decide scope from the brief. A narrow flow becomes exactly one document. An operation with clearly separable stages — a business process end to end, a department, a product lifecycle — becomes a set of two to six linked processes. The first document is the main flow: the entry point an operator starts from, which calls the sub-processes with .do (run it, then continue) or hands off with .go (jump and stop) rather than inlining their steps. Each document must stand alone with four to fifteen concrete steps, its own decisions and failure paths; no stubs. Names are short noun phrases in the language of the brief.

How the set is checked

The reply comes back as documents separated by “=== PROCESS: name ===” markers. Runic splits them and checks every .do and .go target against the names that were actually emitted. If any reference points nowhere, the model gets one correction pass with the exact list of broken references and the instruction to fix only those — rename to an emitted process, or emit the missing one. The corrected set replaces the draft only if it has at least as many documents and no broken links left.

Then every document goes through the same self-repair used everywhere Runic generates a process: parse it, run the structural audit, and if it scores above zero hand the report back for one bounded fix that is kept only when it scores better. This runs on Claude Opus 5 with room for a six-process system.

Landing in your workspace

Emitted names are made unique against the documents you already have (“Payment Check 2” if you had one), and every .do and .go inside the set is rewritten to the final names so nothing breaks on the rename. Sub-processes are created with their full text; the main flow is created and types itself in while the diagram draws. In the sidebar the sub-processes nest under the main flow, because a process with exactly one caller nests under it; one called from two places stays top-level with a reference-count badge. A structural check runs on the main flow, the chat opens, and the agent starts asking its clarifying questions.

What you see while it works

The “Create with AI” dialog narrates real stages rather than a spinner: Reading your brief… Mapping the processes… Drafting the steps… Adding decisions and failure paths… Wiring the linked processes… Checking the structure… Placing the boxes… Runic generates first and creates documents second, so a failed create never leaves an empty document behind, and your existing documents are untouched.

Limits

Ten generations an hour per account, the first 2,000 characters of the brief, and a signed-in session. Sequence diagrams generate as a single document; the system split is for processes. A single generated process is named from the first 44 characters of your brief. Once billing is switched on, a Free workspace holds 10 processes, and every document in a generated set counts toward that.

How to use it

1. 1
   Click ✨ in the sidebar

   Next to the Processes heading. Its tooltip reads “Create process with AI — describe it, Runic writes the first draft”. The sequence list has its own ✨.
2. 2
   Describe the operation

   Write it in plain words in the dialog. For a system, describe the stages and who owns them — the placeholder example is “employee requests vacation; manager approves or rejects; HR records it…”.
3. 3
   Press ⌘/Ctrl + Enter or click Create

   Watch the stages in the dialog. Esc closes it only while nothing is running.
4. 4
   Read the main flow

   It opens and types in. The sub-processes appear nested under it in the sidebar; ⌘/Ctrl-click any .do or .go line to jump into one.
5. 5
   Check and answer

   A structural check, if anything was found, lands in the chat, followed by the agent’s open questions about the draft.

Commands & shortcuts

Tips

• Mention the owners: “sales qualifies, finance checks credit, warehouse ships” gives the model the seams to split on.
• Write the brief in the language you want the processes in; names and steps follow the brief’s language.
• If you wanted one flat flow and got a system, say so in the brief: “a single process for …”.
• Each sub-process is a normal document: open it, edit it, extract from it, and the links keep working.
• The draft is the happy path by design — answer the questions that follow to add the unhappy one.

Questions