The Sage
Log in
See the demo
For therapists practicing parts work
Your notes remember the session. They don't remember the thread.
A year in, a client is a system of dozens of parts — each one somewhere in its own process. Some found and not yet approached. Some witnessed halfway. Some unburdened with work still open. The Sage holds that whole record per client and hands it back assembled, before each session — so the work reaches completion instead of drifting.
Both demos are fictional and fully explorable. Nothing to sign up for.
The problem
The work is profound. The tracking is impossible.
You already have a system. It already fails.
A follow-up box at the bottom of every note, dutifully filled in. And still the thread from session 28 never comes back around. The problem was never diligence — it's that nothing indexes a year of notes by part.
Threads drop mid-process
A protector finally gives permission, an exile gets halfway witnessed — then a crisis takes the next four sessions, and the unburdening never comes. Nobody chose to drop it. It just fell.
The parts blur between clients
Tuesday's inner critic, Wednesday's inner critic — different people, different origins, the same name in your notes. By client thirty, whole inner families are riding on your memory alone.
Progress is invisible from inside it
The client asks whether this is working. You know it is — but they're so far in the thick of it they can't feel the distance traveled, and the evidence is scattered across a year of notes nobody can hold at once.
"None of this means you're a bad therapist. It means you're doing depth work with a filing system built for symptom checklists."
What it caught
The best argument for this is a thing nobody was looking for.
Every part carries its own history of being approached. When that history is held in one place, patterns surface that no one can see from inside a weekly hour. This is a flag from the fictional demo record — the shape is exactly what the tool produces:
High
The Perfect Daughter has been reached for six times and never finished
Contacted in sessions 4, 7, 11, 14, 19 and 23. On five of those six occasions a
protector stepped forward and the hour went there instead — each one a reasonable clinical choice in
the moment. Seen together, the pattern is a core exile that has never been witnessed through to
unburdening, while the parts around it keep getting the attention.
Drawn from
Session 4711141923
A flag is a proposal, never a conclusion. You confirm it, correct it, or set
it aside — and your correction is recorded beside the original rather than quietly replacing
it, so the record shows what the system thought and what you decided.
The therapist seat
Built around the session loop, not a list of features.
Before the session — prep, assembled
Where the work stands, what to check first, what moved since last time, and what's
queued. Every line is written from the record and linked back to the session it came from, so you
can open the source in one click instead of trusting a summary.
See a prep sheet →
In the session — the parts map and the Web
Every part a profile: manager, firefighter or exile — what it
protects or carries, where it came from, who it's polarized with, and every session it appeared
in. The Web shows how they hold each other, Self at the center. Search by name or by concept, for
the parts a client described but never named — those get a provisional name, marked as
provisional until you say otherwise.
Flags for what memory can't hold
Dropped threads, parts approached repeatedly but never finished, drift between what
happened and what got written down — surfaced with severity and sources. The system flags; you
judge; your corrections stay on the record.
After the session — notes, and your methods captured
Write the session note and the record updates around it. The techniques you
actually used get captured into a methods library as you go — including the ones you invented
mid-session and would otherwise forget by Friday. It holds what you practice, not a
generic catalog of modalities you aren't trained in.
The family, drawn properly
A genogram in standard notation — the relationships, the cut-offs, the households,
the people who aren't relatives but shaped the system anyway. Editable from either seat, so the
client can correct their own family without a support ticket.
Between sessions, without the phone tag
A shared workspace per client: check-ins, homework with visible progress, and your
notes back to them — dated and sourced. Async by design, so nobody is on call.
The client seat
Engagement between sessions — in service of the work, never instead of it.
A client who can see their own system arrives differently. The point is not to hand them a self-guided protocol; it's that the week between sessions stops being a gap in the record. Everything here is a window onto the work you're already doing together.
Becoming
A short weekly reflection on what's actually changing for them, written from the
sessions rather than from a template — alongside a running record of the moments something moved.
For a client deep in the thick of it, this is often the first evidence they've traveled at all.
Their goals, in their own words
Not a form. The things they said out loud over months, kept verbatim — each linked
to the sessions where it actually moved. When they ask whether this is working, the answer is a
dated list rather than reassurance.
A journal that stays theirs
Private by default. The client chooses what to publish to you and what to keep —
and can take it back. Their raw material never becomes your dataset, which is exactly why they
write honestly in it.
Check-ins, homework, and their own parts map
A check-in before session if the week was hard. Homework with visible progress.
The same parts map and Web you see, from their side — so the language you use in session is
language they already have.
Why the vocabulary matters
The vocabulary isn't a skin. It's the data model.
Roles, correctly
Managers work ahead of time; firefighters react once pain breaks
through. Both are protectors — same aim, different timing — and they roll up as such.
Exiles are what they protect. Self is not a part, and is never filed as one.
A status ladder that matches the work
Found → In Process → Unburdened. Because a part can be
unburdened and still have work left, Follow-Up is a flag on an unburdened part rather than a
fifth rung — the exile flow ends on a follow-up contract, so the record does too.
Sequence respected
Protectors are met first and permission precedes access. Polarizations are tracked
and shown, never resolved on your behalf. Nothing in the system routes anyone toward an exile.
Where the lines are
The constraints are the design, not the disclaimer.
Therapist-gated by construction
This is not a self-guided app and there is no route through it that walks someone
toward an exile alone. A client's seat is a window onto work held by a clinician. For anyone whose
exiles are genuinely dangerous, that gate is the whole point.
It proposes; you decide
Every flag, every inference, every suggested focus is a proposal routed to you.
Corrections are recorded alongside the original rather than overwriting it — including when the
system got a part's identity wrong, which is precisely the failure worth keeping visible.
The raw material stays with the client
Transcripts and private journals live on the client's side. What reaches the portal
is a published surface they control. Nobody's pain becomes a dataset, and nothing here is used to
train anything.
What it is not, plainly
Not HIPAA-certified — it's in active development with a single practicing therapist
and one client, and is not yet appropriate for a general caseload. Not a diagnostic tool. Not a
replacement for your EHR, your billing, or your clinical judgment.
Where it came from
Built inside the work, not in a product lab.
A client built it for his own therapy
Not a founder with a market thesis — a client a year into deep parts work, trying to hold
38 sessions and 25 parts in his head between Tuesdays and failing. The first version existed
because the alternative was continuing to lose threads that mattered.
His therapist's reaction became the roadmap
Thirty years in practice, meticulous notes, a follow-up box at the bottom of every
one — and the same problem. His response to seeing it was "I want this now, I want it with all
my clients", followed immediately by the harder question of what would have to be true before
it belonged anywhere near a general caseload. That question is the roadmap.
The center light is Self. The roots are the parts beneath. The branches and the leaves are the fruits of the work done below.
See it with your own eyes
Three invented clients. One real tool.
Dr
Start here: the therapist seat
One practice, three clients
Switch between three fictional clients and watch the whole record change with
them. Look at the clinical flags first — that's where the case for this is clearest — then
the prep sheet, then the Web.
Open the therapist demo →
MC
Maya Chen
Burnout & boundaries
A manager built on perfectionism, and a mother relationship renegotiated at a
workable pace. Look at Becoming — the weekly reflection written from the sessions.
Her record →
MW
Marcus Webb
Addiction & trauma
Drinking met as a firefighter rather than a defect, and a twenty-year-old exile
approached at its own pace. Look at the Web — the protectors standing around one wound.
His record →
PN
Priya Nair
A controlling parent & a wounded faith
An inner critic carrying her mother's voice, and a faith reclaimed from the way it
was used against her. Look at the goals — each one linked to where it moved.
Her record →
Questions you're right to ask
Including the uncomfortable ones.
Doesn't this encourage uncertified therapists to work with exiles?
It's designed to do the opposite. The Sage doesn't teach a protocol, doesn't
instruct anyone to approach a part, and doesn't give a client a route to their own exiles. It keeps
a record of work a clinician is already doing and makes the unfinished parts of it visible. If
anything, seeing that a core exile has been approached six times without completion is an argument
for more care, not less.
Is my clients' data used to train anything?
No. Each record exists for exactly two people: the client and you. Nothing is
aggregated, sold, or used for training. The client's raw transcripts and private journal never
leave their side — the portal holds only the surface they choose to publish.
Is it HIPAA compliant?
Not yet, and we'd rather say so than imply otherwise. It's currently in active
development with one practicing therapist and one client, both participating knowingly. Compliance
work comes before it touches a general caseload — which is also why there's nothing to sign up for
on this page.
Does this replace my clinical notes or my EHR?
No. The Sage is a companion for the depth work itself — the parts, the arcs, the
threads. Your legal documentation and billing stay wherever they live today.
What modality is this for?
Parts-based depth work. The vocabulary is the working kind rather than a simplified
stand-in — managers and firefighters as protectors, exiles, burdens and unburdening, Self at the
center — and the record follows how that work actually proceeds. It fits adjacent parts approaches too, and it adapts to how
you practice: your techniques become its methods library, not the other way around.
Is it AI making clinical decisions?
No. It flags patterns and asks questions; it never diagnoses, treats, or decides.
Every inference is a proposal routed to the clinician, and when a correction is made it's kept
beside the original rather than replacing it — so the record shows both what the system thought and
what you concluded.
What does it cost?
Nothing, and there's nothing to buy. It isn't open for sign-ups. This page exists so
the work can be looked at properly, not to collect anyone's email.