Transactional Support
Route → Load → Release
Support is not what you give. It is where the cost goes.
▸ Open MaxCP (click here for more)
▸ ⛭ Key Insight
Transactional Support is cost routing, not niceness. The move is clean only when access increases, the correct payer carries the cost, and future capacity becomes easier instead of heavier.
▸ ⚡ Mantras
- Support is a transaction.
- Cost always moves.
- No hidden subsidy.
- Access without capacity creates debt.
- If no one appears to be paying, you missed it.
- The learner moves more over time, not less.
▸ ↺ Flowchart
Need to support? → Locate the cost.
Cost located? → Identify the current payer.
Payer incorrect? → Reroute before adding help.
Move selected? → Use the smallest viable support.
After movement? → Re-read who is carrying now.
Learner carries more over time? → Fade clean.
▸ ⌘ Micro-Lexicon
- Transactional Support — support understood as cost movement, not generosity.
- Cost routing — deciding where the burden lands and whether that placement is correct.
- Correct payer — the person or structure that can carry the cost without distortion.
- Hidden subsidy — invisible payment by an Agent, Operator, peer, future system, or future-you.
- Distorted transaction — visible task completion purchased through invisible dependency.
- Clean fade — exit only when the loop holds without Operator carry.
Orientation
Routing, Load Distribution, Access, Initiation, Capacity
Support is a transaction. Cost moves. Someone pays.
What Transactional Support Is
Transactional Support is not helping.
It is logistics.
You are not giving support.
You are deciding:
who carries what.
The Transaction
Every move creates a transaction:
- Access is increased
- Cost is redistributed
Nothing is free.
If the learner does less,
someone else is doing more.
If no one appears to be paying,
you missed it.
Clean Transactions
A clean transaction does three things:
- Creates access
- Maintains correct cost placement
- Builds future capacity
Signal
The learner moves more over time, not less.
The system becomes lighter.
Not heavier.
Distorted Transactions
This is where systems lie to themselves.
- Prompting replaces initiation
- Support replaces effort
- Presence replaces agency
The task gets done.
The system degrades.
Pattern
Visible success. Invisible dependency.
It works.
Until you leave.
Routing Errors
Most failure is not refusal.
It is bad routing.
- Cost assigned to the weakest agent
- Cost absorbed by the most capable adult
- Cost avoided entirely (temporary illusion)
This creates:
- fragile systems
- learned helplessness
- operator burnout
Rule
Incorrect cost placement guarantees future failure.
Operator Move
Before acting:
- Where is the cost now?
- Where should it be?
- What happens if I move it?
Then route deliberately.
Not reactively.
Not emotionally.
Not under urgency.
You are not solving the moment.
You are designing the system.
Compression
Support is a transaction.
Cost always moves.
If you don’t control it, the system will distort.
CTA Rail
This page turns support into a system instead of a reaction.