Zanmai is not one assistant that does everything a bit. It is a set of specialists on the same material, each with its own rules and its own idea of finished work.
Steve is the only one you speak with. He reads what you actually need, does the plain work himself, a page you handed over to read, a quick fact with an obvious source, a small edit to something already made, a look at a connection you already set up, a thought captured into today's note, and hands anything specialist to whoever owns it, with enough context to do it well. A specialist comes in only where the step genuinely needs their judgement, their access, or a decision on your behalf, not just because it touches their field.
He also owns every question and every approval. A specialist working in the background never interrupts you mid-run; anything only you can settle comes back up to Steve, who asks. That is deliberate: it keeps the conversation in one place instead of scattering prompts across parallel work.
What he does not do is carry work between two specialists. Where a job needs two trades at once, writing a document and setting it, one of them leads and brings the other in directly, so the words and the layout are settled together rather than handed over a wall. Steve stays free for you while that runs.
| Who | What they own |
|---|---|
| Hank | Filing beyond a single line: imports, multi-file moves, new themes, contact entries, keeping links intact |
| Marcus | What you keep: filing a document that has to stay, whether a contract still runs, what belongs to one matter, keeping terms, what may finally go |
| Ben | Writing, where the material has to be read first: minutes from a recording, an overview of a bundle you have not been through, a handover, a letter, copy for a page |
| Reed | Research across sources, cross-checked and cited, including reading a video or a code repository for its content |
| Wong | Access to systems outside the vault, and the security around it: what is connected, what a secret is allowed to touch |
| Shuri | Your brand: reads colour, type, voice and imagery out of your own material, keeps the one file the others build from, judges finished work against it, and tells you what it is still missing |
| Carol | Documents: flyers, one-pagers, decks, in your own visual language |
| Loki | Generated stills and short video, plus local editing of images that already exist |
| Luis | Editing footage into a finished cut: rough cut, captions, motion graphics, sound, other formats, and a review of his own render |
| Pepper | Anything that could lose state: updates, snapshots, structure checks, bulk repairs |
| Stan | Building a new specialist when nothing existing covers what you need |
A single general assistant averages everything. It files acceptably, designs acceptably, and researches acceptably, because the same instructions have to serve all three. Splitting the work lets each part carry its own standard: research that refuses to cite what it has not read, design that judges the rendered result instead of trusting the description, filing that never rewrites your text.
It also keeps the risky work in one pair of hands. Everything that can destroy state sits with Pepper, behind a snapshot and a confirmation, rather than being available to whoever happens to be working.
If no specialist covers what you need, the answer is not no. The role is researched first so the result is not a generic stub, then written and wired in properly, and you see the draft before it ships. A new specialist lives in a place that survives updates, so it is not overwritten by the next version.
- How Zanmai grows, what happens when a capability is missing
- Skills and scripts, the mechanical layer underneath
- A working session, how work is handed over and comes back