Keep the method.
Save a sequence of steps, not a mysterious one-click shortcut.
03 / WORKFLOWS
When something works,
preserve it.
Turn a useful procedure into something you can inspect, refine, and use again. Workflows are in build; explore the interaction below.
FocusMirror / Workflow conceptIllustrative data
A PROCESS YOU CAN KEEP
Research to recommendation
Workflow versionExample versions
v.03 adds a review checkpoint before the draft is considered complete.
PERMISSION BOUNDARY
Read selected notes. Create a draft. Never publish.
In development. These versions and their steps are example data.
Change it with intent.
Review versions and understand what changed before using the new procedure.
Keep permissions separate.
A saved workflow is not permission to connect accounts, send messages, or publish.
WORKFLOW ANATOMY
A reusable process should stay understandable.
The workflow direction is designed around editability and provenance. Reuse should make the method easier to inspect—not hide it behind a one-click action.
NAMEWhat is this procedure for?
A human-readable purpose and expected outcome.
STEPSWhat happens, in what order?
Explicit checkpoints that can be rearranged or rewritten.
VERSIONWhat changed since last time?
A visible history instead of an opaque prompt that quietly drifts.
SCOPEWhat information and tools can it use?
Permissions remain separate from the workflow itself.
REVIEWWhat did you keep, change, or reject?
Human judgment remains part of the operating loop.
REUSABLE BY DESIGNNext time,
Next time,
start further along.
The direction is a work system that preserves useful structure—not one that quietly expands its own access.
Your perspective comes first.WHEN REPETITION BECOMES A CANDIDATEPreserve first.
Preserve first.
Automate deliberately.
Workflows describe the procedure. Future automations add an explicit, scoped decision about whether it should run.
Explore automationsSee your work a little more clearly.
Start with the foundation. Explore what comes next.