The clinician is the system.
The tech works inside it.
The industry builds AI / tech systems and puts a human in the loop. We build it the other way around: therapist workflows where the therapist drives as the decision-maker and AI / tech serves in the process, never over it.
Explore the Therapy AlignedTM Clinical Wiki — theories, modalities & frameworks →One posture, administrative to clinical.
A knowledge layer clinicians can edit, session workbooks that leave the client holding something real, documentation and planning assistants that give the hour back, and the clinical record to integrate it all. Different jobs — same rule: the clinician drives, the technology works underneath.
Therapy AlignedTM Clinical Wiki
A cross-disciplinary, open-source reference for clinicians — theories, modalities and frameworks, each with worked examples of how to carry it into a treatment plan.
- Community revisions from practice experience
- Semantic search across the full corpus
- Notebooks and a public library
Example output from development — Parts Mapper Workbook
In development
Adaptive Clinical Workbooks
AI-powered, therapist-driven tools for structured therapeutic work.
Unlike static worksheets, Adaptive Clinical Workbooks respond to what the clinician and client enter, helping them explore concepts, identify patterns, generate examples, and move through structured therapeutic exercises while keeping the clinician in control of the clinical process. Each one saves its work into the EHR you already run — no rip-and-replace.
- Parts Mapper Workbook — IFS-informed parts work
- Storyboarding Workbook — narrative arc building
- Window of Tolerance Workbook — regulation mapping
- Coping Menu Workbook — between-session regulation
Electronic Clinical Notebook (ECN)
Most records are built for the payer and handed to the clinician. The ECN is the inverse: a clinical notebook first — formulation, what happened, what the client took home — that earns its administrative keep on the way out. The ECN is part of the bigger vision.
- Clinical-first, not billing-first
- Session artifacts and notes in one continuous thread
- Controlled development on AWS infrastructure
SOAP Note Assistant
The administrative side of the same posture. The clinician brings the judgment — what was observed, what it means, what happens next — and the assistant carries the structure, so the note reads like the session actually went.
- Clinician-dictated, clinician-signed
- Structure and formatting handled underneath
- Nothing leaves the draft without a human decision
- Saves into the EHR you already run
Treatment Plan Assistant
Goals and objectives that come out of the clinical formulation rather than a dropdown. Drafting support that stays anchored to the theory the clinician is actually working from, with the Clinical Wiki underneath it.
- Formulation first, template second
- Theory-to-treatment-plan examples from the Wiki
- The clinician writes the plan; the tool holds the scaffolding
- Writes back into your existing EHR
Everything here is being developed toward HIPAA and 42 CFR Part 2 compliance.
Regarding AI…
Everyone is putting humans in the loop.
We put AI in it.
“We believe in creating AI-in-the-loop products. This flips the common human-in-the-loop for AI systems. In our vision, we are working on products that are human / therapist systems with AI in the loop.”
Andrew H. Kim, MSW, LCSW, LCADC — Chief Architect
Human-in-the-loop means the machine runs the process and a person checks its work. It is a safety valve bolted onto an automated system. It is also, in behavioral health, exactly backwards.
The therapeutic relationship is not a process waiting to be automated with a reviewer attached. It is the intervention. So we build the architecture the opposite way: the therapist is the system, the alliance is the operating logic, and AI is a component that runs inside it — drafting a frame, holding a thread, rendering something the client can look at — always under clinical judgment, never in front of it.
Practically, that changes what we ship. Therapist workflows with AI assisting and supporting therapist functions. No model deciding what matters. Every tool has a therapist’s hand on it and ends with something two people made together.
Our Chief Architect is developing the 5-Level AI-Integrated Psychotherapy Framework, set out in a public Open Science Framework project that maps how AI can enter a live psychotherapy session without compromising the alliance — positioning AI as a “third chair” in the room rather than a replacement for the two people already in it. Every level of that framework describes a way AI can sit inside the loop. None of them hand AI the loop.
What we are planning.
The knowledge layer
Clinical Wiki live and open to community revision, with semantic search, notebooks and a public library.
The tool suite
Both halves of the work — clinical workflows for the room (Parts Mapper Workbook, Storyboarding Workbook, Window of Tolerance Workbook, Coping Menu Workbook) and administrative workflows around it (the SOAP Note Assistant, the Treatment Plan Assistant). Each one is being built to sit on top of the EHR a practice already runs and save its work into that record, with zero data retention (ZDR) on our side.
Custom tools
Modality-specific tools designed alongside the clinicians who bring the theory — one framework at a time, built to the same posture as the rest of the suite.
Electronic Clinical Notebook
A clinical-first EHR with the tools and assistants already embedded. As part of the bigger vision, this moves EHRs from compliance-driven entries (progress notes, treatment plans, contact notes) to a clinically-driven notebook (parts map, genograms, narrative stories, coping menu). Built on HIPAA and 42 CFR Part 2 compliance architecture to protect your clients.
Stages reflect where work sits today — not a delivery commitment.
A clinician and an engineer, in the same room.
Meet the team holding up the thesis
Bring us the theory.
We’ll build the tool.
If you have a modality you teach, a framework you keep redrawing on paper, or a moment in session you wish you could hand the client — that is the conversation we want. Pilot access and custom-tool collaboration run through the same form.