Treated vs. returned

There's a sentence the whole of this work rests on: you are not treated, you are returned. It sounds like a tagline. It's actually a description of method.

The difference

To be treated is to be a problem worked upon. Something is wrong; a technician applies a procedure; you leave, hopefully improved. It's the logic of most of the care we receive, and for plenty of things it's the right logic.

To be returned is different. Nothing about you is being corrected. The work isn't aimed at an outcome you'll measure in the mirror — it's aimed at bringing you back into contact with a body you may have been living slightly outside of.

Why presence, not outcome

When a session chases an outcome, the whole hour bends toward the end. You're somewhere ahead of yourself, waiting to see if it worked. The nervous system stays half-alert, half-braced.

When a session is built around presence, there's nowhere to get to. The only task is to be here, in this body, now. And it's precisely that — the having-arrived, the not-needing-to-perform — that lets the deep softening happen. The results people notice tend to come through the presence, not instead of it.

What it asks

It asks the practitioner to hold space without an agenda. And it asks you to do the quietly radical thing of receiving without earning — of letting two hours be for you, with no outcome owed.

Most people find that harder than they expect, and more nourishing than they imagined.