You understand what the Identity Line is. You recognise the pattern. You know the problem isn't at the level of behaviour or mindset, it's below both of those, where the code was originally installed.
That understanding is real. It changes something. It is not, by itself, the change.
There are three ways to do this work. The right one depends on where you are, what you've already tried, and how much support you need to reach the level where the pattern actually lives.
The Diagnostic maps your specific architecture. It's the starting point for every path. After it, you choose how to proceed, self-directed, guided, or fully supported.
Not sure which path is right? That's what the strategy call is for. It's a genuine conversation, not a sales process.
The strategy call isn't a sales call. It's a genuine conversation about where you are, what's been running underneath it, and whether Identity Reset is the right next step for you specifically.
If it is, we'll work out which path makes sense. If it isn't, you'll leave with more clarity about your situation than you arrived with. Either way, the call is worth having.
The conversation is direct. It goes somewhere. And by the end of it, you'll know, clearly and without ambiguity, whether this is the right work at the right time for you.
The people who understand their patterns most clearly are often the same people who have been living inside them the longest.
Comprehension is not the lever. Working at the right level is. And the right level requires a starting point, a precise map of what your system has actually been running, before anything else can begin.
That's what the Diagnostic builds. Everything follows from it.
You already know what the pattern costs.
You already know the surface-level approaches don't reach it.
The only question is what you do with that.