Sustainable Support
Build → Transfer → Carry
If it survives without you, it was real.
▸ Open MaxCP (click here for more)
▸ ⛭ Key Insight
Sustainable support is proven after the support leaves. If the learner moves, the field holds, and the Operator is no longer required, the support built capacity instead of dependency.
▸ ⚡ Mantras
- If it needs you, it isn’t done.
- If it carries, it’s real.
- Build for exit from the beginning.
- Fade before dependence forms.
- No hidden carriers.
- Movement must continue when you are gone.
▸ ↺ Flowchart
Support installed? → Identify what it is carrying.
Cost placed? → Confirm the correct payer.
Capacity emerging? → Begin fading.
Support removed? → Change context, increase demand, and watch.
System holds? → Carry is real.
System collapses? → Operator was still the structure.
▸ ⌘ Micro-Lexicon
- Sustainable support — support that fades and leaves capacity behind.
- Carry — movement that continues without Operator scaffolding.
- Transfer — gradual return of effort, timing, and ownership to the learner or field.
- Hidden carrier — an unseen person, structure, or future moment secretly paying the cost.
- Fragile stability — short-term success that collapses under absence, context shift, or demand increase.
- Exit design — building support with removal criteria from the beginning.
Orientation
Capacity, Independence, Transfer, Stability, Carry
Sustainable support disappears and leaves something behind.
What It Is
Sustainable support is not visible in the moment.
It is visible later.
When the support is gone.
And something still holds.
The Test
Remove yourself.
Change the context.
Increase the demand.
Then watch.
If the system stabilizes,
capacity exists.
If it collapses,
you were the system.
Rule
Support is only valid if it survives your absence.
What It Requires
- Correct cost placement
- Gradual release of support
- Real ownership of effort
No shortcuts.
No substitutions.
No hidden carriers.
If it carries, it was built correctly.
Failure Pattern
Most systems aim for success in the moment.
They get it.
At a cost.
- Support stays too long
- Cost stays misplaced
- Dependency forms
The result:
fragile stability.
It works.
Until it matters.
Operator Move
Design for exit.
From the beginning.
Every support decision answers:
- How does this fade?
- When does this leave?
- What remains after?
If you cannot answer those,
you are building dependency.
Not capacity.
End State
No prompts.
No carrying.
No hidden scaffolding.
The learner moves.
The system holds.
You are no longer required.
Signal
Movement continues when you are gone.
Compression
If it needs you, it isn’t done.
If it carries, it’s real.
Build what survives.
CTA Rail
This page defines what actually holds.