Fee Schedule
What Counts as Cost
Cost is anything paid by any node so movement can happen, continue, or appear stable.
▸ Open MaxCP (click here for more)
▸ ◉ Key Insight
Cost is not only effort. Cost includes time, attention, access, dignity, regulation, trust, repair, future load, and the invisible burden moved onto quieter nodes.
▸ ⚡ Mantras
- Nothing is free.
- If no one appears to pay, look again.
- Quiet payers are still payers.
- Future-you is not a garbage dump.
- Cost literacy precedes cost routing.
▸ ↺ Flowchart
Movement happens? → identify what was paid.
Cost identified? → locate the current payer.
Payer correct? → continue and re-read.
Payer hidden, weak, or future-loaded? → routing error.
Routing error found? → reduce, reassign, or redesign before calling it support.
▸ ⌘ Micro-Lexicon
- Cost — anything paid so movement can happen, continue, or appear stable.
- Payer — the node currently absorbing the burden.
- Correct payer — the node structurally responsible and able to pay without collapse.
- Hidden subsidy — unacknowledged support that makes the system look cheaper than it is.
- Future load — cost deferred until later, usually with interest. Rude little invoice goblin.
Orientation
Cost, Payer, Node, Hidden Subsidy, Future Load, Correct Routing
Cost is the bill movement leaves behind. Integrity begins when the bill has a real payer.
What Counts as Cost
Cost is not just effort.
Cost is not just time.
Cost is not just money.
Cost is anything a person, role, field, relationship, or future moment pays so the current move can happen.
If the move became easier, something else carried weight.
Nothing is free.
The Fee Schedule
Open the stand. Check the produce. Find the payer.
▸ 🍎 Visible Costs
Visible costs are easy to notice because someone can usually point at them without needing doctrine glasses.
▸ Time
Waiting, delays, repeated transitions, repeated prompting, extended recovery, and the five-minute thing that has somehow become a twenty-minute thing. Magnificent little gremlin.
▸ Effort
Physical movement, task demand, initiation, sustained work, cleanup, re-entry, and any extra lift required to keep the loop moving.
▸ Attention
Monitoring, scanning, anticipating, translating, watching for drift, and holding the thread so someone else can move.
▸ 🥬 Hidden Costs
Hidden costs are the ones systems love to deny because admitting them would ruin the spreadsheet cosplay.
▸ Cognitive Load
Remembering steps, holding ambiguity, interpreting mixed signals, tracking social rules, sequencing movement, and carrying instructions that were never made usable.
▸ Emotional Load
Suppression, masking, shame, fear, frustration, self-blame, disappointment, and the cost of looking fine while very much not being fine.
▸ Dignity Cost
Embarrassment, public correction, forced explanation, unwanted exposure, extraction, and being made into the lesson instead of protected inside it.
▸ 🌶️ Spicy Costs
Spicy costs burn later if nobody admits they were added.
▸ Agency Cost
Reduced choice, reduced exit, compliance traps, dependency, learned helplessness, and any move where the person moves less so the system can look smoother.
▸ Relational Cost
Trust loss, face loss, resentment, rupture, adult-child friction, peer damage, and the tiny cracks people pretend are not structural. Adorable. False.
▸ Access Cost
The price of starting, asking, re-entering, recovering, switching contexts, accepting help, refusing cleanly, or trying again without having to bleed for admission.
▸ 🧺 Deferred Costs
Deferred costs are not gone. They are waiting politely in the parking lot with a folding chair.
▸ Repair Cost
Apology, restoration, cleanup, reteaching, trust repair, relationship repair, and the cost of rebuilding what a cheaper earlier move could have preserved.
▸ Future Cost
Anything made easier now by making later heavier: delayed blowback, accumulated fatigue, future refusal, transfer failure, and the invoice future-you did not authorize.
▸ Field Cost
Lost room flow, peer attention diversion, adult depletion, schedule distortion, increased noise, and the environment paying because routing failed.
The Test
If you cannot name the cost, you cannot route it.
If you cannot name the payer, you cannot call it clean.
If the payer cannot refuse, the system is already leaning toward coercion.
- Who is doing more so this can happen?
- Who is losing capacity, choice, trust, time, or dignity?
- What becomes harder later because this became easier now?
- Would this collapse if the hidden payer stopped paying?
Clean vs Dirty Fees
Clean Fee
The cost is visible, temporary, correctly assigned, capacity-building, and reviewed after the move lands.
Dirty Fee
The cost is hidden, permanent, pushed downward, disguised as kindness, or deferred until collapse makes the bill obvious.
Dirty fees are how systems buy visible success with invisible debt.
Quiet does not mean paid.
Operator Move
Before support, name the fee.
During support, track the payer.
After support, test whether the cost returned cleanly.
If the same cost keeps returning to you, you are not watching a fee.
You are watching a subscription.
That is not support.
Failure Mode
The system tracks visible work but ignores invisible payment.
This creates:
- hidden subsidy
- operator burnout
- learner dependency
- future collapse presented as surprise
The bill was always there.
Compression
Cost is what gets paid so movement can happen.
Integrity is making sure the right payer pays it.
Support is incomplete until the cost can return without collapse.
CTA Rail
This page teaches the reader to see the invoice before locating the payer.