The same good work, done reliably, without asking.

Hand it a job. It runs without being asked.

A workflow is a named recipe of stages, handled by your agents, producing things that land where they belong. It is not a flowchart and not a state machine — it reads like a recipe: first Scout gathers, then Drafter writes, then Editor reviews, then Presence hands it to you. Each step has someone who does it, something they need, something they produce, and something the next step picks up.

Think of it less like writing software and more like asking a team to do a piece of work. You name the work, you name the people, you say what each is responsible for, and you let them get on with it.

You set it up once — in conversation with 1Presence, or in the visual builder if you prefer. You name it, pick the trigger, arrange the stages, decide where the output lands and who else sees it.

It runs without you noticing — until it has something for you. Most of the time you simply find the result already in your vault. Sometimes a stage pauses and asks; you answer and it carries on. If something fails, a plain-language note arrives saying what went wrong and what it did about it.

The run timeline is the receipt. Every run leaves a trace — stages, durations, who did what, what they wrote, what they asked. Last Monday's brief and last December's are both five seconds away.

You adjust as you go. Swap an agent, tighten a stage, move a pause earlier, change the schedule, add a recipient. Workflows evolve with how you actually use them.

• Monday Morning Brief. Every Monday at 7am: what shipped, what is on fire, what is worth reading. Scout gathers, Drafter writes, Editor checks, Presence delivers it to your morning chat.
• Inbox Triage. Every weekday at 7am: sorts overnight email, archives the noise, surfaces what needs you, drafts replies to the routine ones.
• Pre-meeting Prep. Thirty minutes before any calendar event: a one-page brief with attendee context, prior threads, and notes from last time — waiting before you join.
• Friday Digest. Every Friday at 5pm: what shipped, what was decided, what is pending, what to mull over the weekend — with decisions quietly captured as you go.
• Content Repurposing. When a new post lands in your published folder: variants for each channel, drafted and staged for your review.

Workflows are not autonomous by default. They pause when they need to, fail with reasons, and ask for approval on anything that reaches the outside world. The first time a stage tries something consequential it has not been cleared for — sending an email, posting to a channel — it stops and asks, and remembers your answer for next time. Nothing material happens silently.

And they compose. One workflow can set up another — onboarding a new client can schedule the weekly check-in; logging a decision can schedule its own 90-day revisit. The work keeps paying off long after you set it up.

A routine is the simple case — one job, one agent, its own cadence. The inbox-keeper that checks your mail each morning; the dashboard that refreshes itself before you wake. A workflow is the fuller thing: several agents, ordered stages, typed handoffs. Most recurring work starts life as a routine, and grows into a workflow only when it earns the extra stages.

• Built by describing it. Say what should happen and when — "check my inbox each morning and flag what needs me" — and 1Presence shapes the routine in the conversation. No builder needed for the simple case.
• Scheduled only when you ask. Nothing is quietly armed. A routine gets a schedule when you give it one — until then it runs when you say run. When you do schedule it, you confirm the cadence, and you can pause or change it any time.
• It knows who it is for. A routine that runs for something — a brief for a client, a workup on a lead — asks you to pick the subject from a searchable list of your real records. Schedule it and you choose once; every run after that already knows.
• It picks up where it left off. A recurring job remembers when it last ran well and handles only what is new since — the emails that came in, the files that appeared — instead of starting over each time or missing what arrived while it was busy.
• Sweeps you can stop. When a routine works through a whole set — refreshing a card per client, say — you watch it move ("19 of 50") and can stop the sweep in one tap: the current item finishes, the rest are skipped, and everything already done keeps its result. In the history, a sweep folds into one tidy line you can open to see how each item fared.

Both routines and workflows leave the same honest trail. Every run keeps its plain summary, and one tap opens the full step-by-step transcript behind it — so work you were not watching is never a black box. And when any of them needs you, it appears in your inbox as a single card you can answer in a tap.