Syntropia
There's something clinical practice runs into that the textbooks never quite capture. It isn't a gap in knowledge, and it isn't inexperience. A diagnosis names a moment. What's happening in front of you in the room is a process, and it's moving.
Some patients improve, then relapse. Others change in ways nobody saw coming. Some stay stuck in the same place for years, no matter what you try, then move all at once, for no clear reason. The diagnostic category names all of this. It doesn't explain any of it.
That's Syntropia's starting point: what determines how someone evolves isn't the state they're in at any given moment. It's the logic organizing their experience over time. That logic has a direction, a speed, a way of responding to change. One word for it: a trajectory.
A trajectory is deeper than a clinical history, and simpler. It's how a person connects, anticipates, holds themselves together, or reorganizes when something pushes on them. That way of moving has structure. And structure can be observed, characterized, and worked with.
In the room, that opens up different questions.
How this patient is doing today, and how they've been moving. Which domains of functioning are compromised, and which direction they're moving in, at what speed. Whether treatment worked, and what actually changed in the trajectory.
These are questions you're already asking. Syntropia gives you a shared language for them, and a framework for working with the answers.
Syntropia picks up where diagnosis leaves off. The state's already been named. What's left is where it's headed, and why.
If you want to get straight into the model itself (the trajectory, accumulated history, receptive capacity, syntropic configurations), there's an introduction built to be read in one sitting.
Syntropia in 20 Minutes →Syntropia is under active development.
If what you just read raises a question, write to [email protected]