A folder as a process
Open the process view
- In the file tree (the Files button in the brain's heading): hover over a folder and click the View as a process icon. On a phone the icon is always visible.
- On the map: in the panel of a selected folder or Markdown file, click View as a process. From the brain's panel, the whole brain can be shown this way.
The view is built in the browser from headings, lists, tables and links. It uses no AI, writes nothing into the brain and takes only files the role sees. The open folder is in the page address, so a link opens the same view.
Tabs at the top:
- Your own process from a
process.mdfile, when the folder has one (see Your own process layout). The tab carries its title and always comes first. - Folder overview: the files right in the folder, then each subfolder as one stage. Subfolders numbered
01-…,02-…go in that order. Each file has a card with its title and first sentence, dotted lines are links between files. - Files that read like a procedure: each one gets its own tab with stages and steps.
- Mermaid diagrams from the files in the folder.
- Processes from the AI chat: the AI's draft of the folder or a process the chat has written, see The AI chat beside the process.
Clicking a card shows its summary: what the step, file or folder is, its main files and sections. From there the file opens right at the lines of the step (Open at the step), a folder shows as a process, or the AI can be asked about it. Back to the process returns to the view exactly as it was. Hovering a card highlights the whole path through the step.
What the view shows
- Stages are coloured columns. Each has a number and a name at the top, so the order is clear without colours and in black and white print too.
- Steps are cards with a bar in the stage's colour, a number and an icon. Chips on the card show a Decision, who does the step and its status.
- Decisions have pointed ends, and the ways out of them carry a label, such as Yes and No.
- Lines: a solid arrow leads to the next step, a dashed one back (a repeat), a dotted line is a link between files.
- Start is a ring with a triangle, End a thick ring.
- Role lanes: when people take turns within a stage, each role has its own lane with a label.
The view has a light and a dark theme, following the app. When the system reduces motion, the view does not move.
Controls
| Key or gesture | What it does |
|---|---|
| drag, arrows | pan |
| scroll wheel, + and -, pinch | zoom in and out |
| 0 | centre the whole process |
| click a card | the card's summary, from there its file |
| P | present |
| Esc | back |
Presenting
Present (key P) shows the process full screen, slide by slide:
- A title slide: the title, the lead sentence, the stages in order with their number and colour, the number of stages and steps, who takes part and where the process comes from.
- The whole process at once.
- A slide per stage: the view moves to it, the rest dims and the steps are listed beside it.
- An end slide with the downloads.
Go on with the arrows, space, Enter, a click or a swipe. Esc ends the presentation and returns to the process view. When the chat has written several processes at once, the presentation shows them one after another.
Download and print
In the Download or print menu:
- PNG image: the whole process in the current theme (light or dark), at double resolution.
- HTML presentation: one file with all the slides, no scripts and no outside links. It can be sent by e-mail and opened in any browser.
- Print or PDF: one slide per A4 landscape page. Choose Save as PDF in the print window for a PDF.
The export holds what the own role sees. Before sending it outside the company, it is worth a look.
The AI chat beside the process
For a folder the AI chat about the process panel is right there beside the diagram. The AI chat button in the header closes and opens it (the choice is remembered); for a file and on a phone it opens only with this button. It is the one place for AI in the process view.
An empty chat offers Draft the process, see AI draft. Then questions can be asked:
- Write a question, or pick an example: "How does this process work here?", "Write out step 3 in more detail", "Add an approval by the director".
- Send it with Enter (a new line with Shift+Enter).
- The AI answers briefly. When the process changes, or the question is about something the diagram does not show ("how does a complaint work"), it writes it and the view is redrawn right away. When the question is about a part of the process on screen, the process stays and that part stands out in the diagram (Show in the diagram).
- Under the answer are the Sources: the files the AI worked from. A click opens the file, at the line when there is one.
A further question builds on the previous ones, so the process can be changed step by step. An answer can hold several processes in a row; the arrows by Process 1 of 3 switch between them.
Versions and edits:
- Each answer that changes the process is a new version (Redrawn, version 2), and so is the AI's draft of the folder. Restore the previous version under the answer and the Back and Forward buttons above the conversation switch between versions, Back to the folder's process shows the original process. The versions stay.
- The versions are kept with the folder: they stay after leaving the folder and after reloading the page, and the one on screen last comes back. Each version says who made it and when. Only people who see the brain the same way (the same role with the same rules) see them, the author's name only where the role shows the authors of changes. Viewing as another role keeps no versions. Kept versions are deleted after 90 days without a change.
- Edit the text shows the text of the process in the
proces.mdformat. Edits are drawn right away, without AI. From the card of a step of a process from the chat, Edit in the text marks its lines. - The panel's width changes by dragging its left edge. Esc closes the chat.
- The conversation is not kept, only the versions of the process. Opening another folder starts the chat afresh. What should stay in the brain has to be saved to the brain.
- While it answers, the chat shows its steps: reading the folder's files, the AI reading the material, putting the draft together (how many phases and steps so far, with the local AI also its speed in tokens per second) and drawing. After the answer the steps fold into one line.
- When not everything fits into the AI's context (the local AI in a mode with more slots has a smaller one), the AI gets a shorter outline of the folder, fewer older messages, or only the beginning of the draft, and the answer says what did not fit.
What the AI gets and what it costs:
- Each question uses 1 AI request from the daily limit, the same one as the AI draft. Questions go one at a time, the next one after the answer. The number of tokens is shown under the answer.
- The AI the organization has set for the process view answers (Organization AI → Routing): the company's local AI, the organization's AI, or the onlybrain AI (a fast model, Claude Haiku). Every answer says which one it was. When the AI that is set does not answer and the organization allows a fallback, the fallback answers and the answer says so. The app draws the process itself, drawing uses no AI.
- The AI gets only an overview of the open folder (titles, headings, first sentences), a few lines a search finds for the question, the process being written and the last few messages. All of it only from files the role sees, never from hidden folders. A source outside the role's view is not shown in the answer.
- While viewing as another role, the AI works from that role's view.
- When the organization has switched AI off, the chat takes no questions.
- Nothing is written into the brain until the process is saved. The answer can be wrong; the files are what counts.
Save a process to the brain
A process from the chat and the AI draft can be saved as a Markdown file in the brain:
- Click Save to brain at the top of the process view, or at the bottom of the chat.
- Pick a name and a folder,
procesy/by default. The resulting file name is shown below them. - Click Save.
- The process on screen is saved. When the chat has written several processes, each one is saved on its own.
- A new file in the
proces.mdformat is made, withproces: truein its frontmatter. A file with the same name is never replaced, a number is added to the name. The original files in the folder stay as they are. - The role's rights apply. When the role may only propose changes in the folder, the process waits for approval in Changes and is in the brain only after that.
- Nothing can be saved while viewing as another role.
Saved processes are together on the Processes page.
How to write a document that makes a good process
Plain Markdown is enough, no special syntax. The document still reads well as text.
| In the file | In the process |
|---|---|
# Title or title: in the frontmatter | the process title |
the first sentence under the title or description: | the lead sentence |
numbered sections ## 1. Inquiry, ## Step 2: Offer, ### Phase 3 · Delivery | stages in order |
| bullets or a numbered list in a section | steps |
### subheadings in a section | steps, each with its own card |
**Owner**: sales (also Responsible:, Role:) | who does the stage |
a step that starts with a role: Accountant issues the invoice | who does the step. When people take turns within a stage, the process splits into lanes by role. |
a heading ### 2. Reviewer - review | the role and the step |
a question with Yes: … and No: … bullets under it | a decision with two ways out |
If …, …, otherwise … | a decision |
| a stage that says "in parallel" or "at the same time" in its title or first sentence | steps side by side |
a table with an Owner or Role column | rows as steps, the column as the role |
A → B → C on a line of its own | a simple chain of steps |
a top to bottom chain with ↓ in a code block, also with a box of columns ┌ │ └ | steps, the box's columns as parallel branches |
a mermaid block with flowchart or stateDiagram | its own tab with the diagram |
| a link to another process (a folder or file with "process", "workflow" or "how to" in its name) | a Sub-process chip |
status: in the frontmatter or a Status: line | a status chip |
| other sections without numbers (Overview, Deadlines, Checklist) | notes under the process |
An example process with two decisions, roles and a sub-process:
# Invoicing a project
From delivered work to a paid invoice.
## 1. Groundwork
**Owner**: PM
- Write down the work done this month
- Sales confirms the price from the contract
## 2. Invoice
- Accountant issues the invoice
- If it is an advance, attach the advance sheet, otherwise the final bill
- Accountant sends the invoice to the client
## 3. Payment
- Client pays within 14 days
- Is the invoice overdue?
- Yes: Accountant sends a reminder
- No: Accountant matches the payment
## 4. Closing
- PM closes the project in the brain
- Sales offers further work following the [sales process](../sales/process.md)
## Deadlines
- Invoice by the 5th of the month
- Reminder 3 days after the due dateA short procedure fits on one line:
Inquiry → Offer → Contract → Delivery → InvoiceAnd a process with branches as Mermaid:
flowchart LR
A[Request] --> B{Bigger change?}
B -->|yes| C[Design]
B -->|no| D[Build]
C --> D
D --> E[Review]
E --> F[Release]Tips:
- One step per line.
**Title**: detailsgives the card a title and a subtitle. - A stage shows at most 8 steps on the canvas, the rest folds into
+N. A longer stage is better split. - Numbered sections alone are not enough for a file to count as a procedure. It helps to have "process", "workflow", "onboarding" or "how to" in the title, steps like
Step 2orPhase 3, who does what, or a chain with arrows. Specs, contracts, checklists, summaries and files with a date in the name do not count as processes. - The AI in Claude Code or Codex writes such a file itself, just ask:
From the files in knowledge/invoicing, write process.md:
numbered stages, an Owner for each, steps as bullets and decisions as a question with Yes and No.Your own process layout
The automatic overview shows what the folder holds. How the process should look is set by a process.md file (or proces.md) right in the folder. It follows the same rules as above and shows as the first tab of the process view. Any other file can be marked as the process too, by adding process: true to its frontmatter.
AI draft
The Draft the process button in an empty AI chat lets the AI build a clearer version of the folder's process: it names the stages as a person would explain them, groups the steps, and adds who does them and where decisions are made. The draft is the first version in the chat, so it can be asked about further and taken back.
- It runs only on a click and uses 1 AI request from the daily limit.
- The AI gets only the titles, headings and first sentences of the files in the folder that the role sees. A step of the draft never leads to a file outside the folder.
- The draft is kept until the files in the folder change. Opening it again costs no request; Draft again has it built anew.
- For a large folder and an AI with a smaller context (a local AI) not every file may fit into the draft. The chat then says how many were left out.
- Nothing is written into the brain until Save to brain is chosen. The draft can be wrong; the files are what counts.