A cast of personas

A single general-purpose assistant is a compromise. The voice that should write a careful historical summary is not the voice that should draft ad copy, and neither should be the one reviewing the other's work. Personas let you stop compromising.

A persona is a role, not a prompt preset

Each persona carries its own instructions, its own model, and its own set of permitted tools. That last part is what makes them genuinely different from each other: a research persona can browse and query archives, an editor can read and critique, and a publishing persona can put something live. None of them can do the others' jobs by accident.

Skills - your procedures, written once

A skill is a reusable procedure: how you run a competitive teardown, what your house fact-check actually checks, the shape a client brief has to take. Write it once and attach it to as many personas as should follow it. Editing the procedure updates every persona using it, which is the difference between a documented process and a paragraph pasted into six prompts.

One procedure ships with the house: how to use the decision tools well. Give the model the material and never a summary of it, threshold on its confidence rather than on the winner's probability, quote the figure, and say so plainly when no decision key is set. Attach it to any persona that holds the tools.

Short procedures can sit in the prompt permanently. Long ones attach on request: the persona sees a one-line summary of what the skill covers and fetches the full text only on the turns where it applies, so a thousand-word procedure costs almost nothing on the calls that do not need it.

Memory - and whose it is

A persona can be given memory, and it stays off until you switch it on. Two different things live there. Curated memories are the ones you write yourself: your house style, the things it must never claim, the names it should get right - received by everyone who talks to that persona. Remembered ones the persona writes itself while working: your name, what you are building, how you want answers written.

Those are private to the person they were learned from. A persona shared across your whole organization still keeps a separate set of notes for each colleague, and nobody sees anybody else's. Long notes work the way long skills do - a short version stays in the prompt and the detail is fetched only when it is wanted.

Voice and method, held steady

Because the instructions live with the persona rather than in whoever's message happened to start the conversation, the same persona produces recognizably the same work next week as it did today. That consistency is what makes a persona usable inside a scheduled routine - you are not re-explaining the job every run.

The platform ships with a working cast, so routines can be built the day you arrive. Editing one, or writing your own, is a form - instructions, model, tools, the skills it follows and the memory it keeps. Skills and memory are included from the Standard plan.