Failure Modes
Distort → Misapply → Collapse
Most refusal fails by becoming something else.
▸ Open MaxCP
▸ ◉ Key Insight
Failure modes imitate refusal at the surface while removing the actual gate: evaluation, selection, and stable boundary under pressure.
▸ ⚡ Mantras
- Refusal selects.
- Avoidance disappears.
- Aggression leaks.
- Control coerces.
- Collapse teaches pressure to keep pushing.
- When unclear, return to 吞.
▸ ↺ Flowchart
Pressure appears → return to 吞.
No evaluation? → avoidance, not refusal.
Escalation enters? → aggression, not refusal.
Others are forced? → control, not refusal.
Boundary changes under pressure? → collapse, not refusal.
Clean read + stable posture + valid cost → one 吐.
Then 浮 → 沉.
▸ ⌘ Micro-Lexicon
- Pseudo-refusal — any surface no that lacks clean selection.
- Avoidance — disappearance mistaken for boundary.
- Aggression — reaction mistaken for refusal.
- Control — outward force mistaken for inward gatekeeping.
- Collapse — delayed compliance after pressure outlasts clarity.
- 四勁 — internal posture that keeps refusal clean.
- 六勁 — external posture that keeps the boundary transmissible.
Orientation
Distortion, Misuse, Leak, Collapse, Correction
If refusal is unclear, it mutates into something else.
The Pattern
Refusal is simple.
Which makes it easy to distort.
When misapplied, it becomes:
- avoidance
- aggression
- control
- collapse
It can look correct.
But function incorrectly.
This is where lazy reading gets expensive.
The Costume Problem
Failure modes borrow refusal’s outfit.
They wear the jacket.
They do not carry the gate.
Clown Costume Test
If there is no clean evaluation, no actual selection, and no stable boundary under pressure, it is not refusal. It is a clown in a security vest.
The outfit is not the function.
▸ Avoidance (Passive Refusal)
▸ What it looks like
- silence
- withdrawal
- non-response
▸ What is actually happening
No evaluation occurred.
No decision was made.
This is disengagement.
The system receives fog, not constraint.
▸ Why it fails
Nothing was refused.
The system receives no constraint.
Without 吞, there is no valid refusal.
▸ Correction
Refusal is active.
It selects. It does not disappear.
▸ Aggression (Reactive Refusal)
▸ What it looks like
- pushing back
- arguing
- escalating tone
▸ What is actually happening
Reaction replaced evaluation.
This is not refusal.
This is participation in escalation.
The loop just put your name on the roster.
▸ Why it fails
It feeds the loop.
Dirty 吐 is still movement. The system counts it.
▸ Correction
Refusal does not fight.
It does not need to.
▸ Control (Misplaced Authority)
▸ What it looks like
- forcing outcomes
- imposing structure on others
- blocking without evaluation
▸ What is actually happening
Refusal applied outward instead of inward.
This is not refusal.
This is control.
The gate got pointed at the wrong person.
▸ Why it fails
It governs what others must do.
Refusal governs what enters the system.
If agency is removed, nəc̓aʔmat did not pass.
▸ Correction
Refusal governs what enters you.
Not what others must do.
▸ Collapse (Failure Under Pressure)
▸ What it looks like
- initial boundary → eventual compliance
- “fine, just this once”
▸ What is actually happening
Pressure outlasted clarity.
This is not refusal.
This is delayed compliance.
The system learned the timer exists.
▸ Why it fails
It teaches the system to push.
The next pressure event starts from that receipt.
▸ Correction
Refusal must hold at the same level under pressure.
If the boundary changes, return to 吞 and rebuild the read.
System Cost of Failure
Each failure mode creates distortion:
- Avoidance → no movement
- Aggression → escalation loops
- Control → resistance and backlash
- Collapse → unstable boundaries
All four:
break the system.
They either block 浮, corrupt 沉, or authorize a dirty 吐.
Operator Check
Before calling something refusal, ask:
- Was there evaluation?
- Was there selection?
- Is the boundary stable under pressure?
- Does agency remain intact?
- Can the loop return to 吞 cleanly?
If not:
It is something else.
Rule
Refusal is precise. Distortion is not.
Celery Check
If the move needs drama to feel real, the structure is already wobbling.
Clean refusal does not need fireworks.
It needs a clean read, stable posture, and a boundary that does not leak when poked.
Hold the gate.
Compression
Refusal selects.
If it doesn’t select, it isn’t refusal.
Clarity prevents distortion.
CTA Rail
This page protects refusal from misuse and closes the child branch cleanly.