---

name: redirect locale: wenyan-ultra source_locale: en source_commit: 82c77053 fence_basis_commit: 82c77053 translator: "Julius Brussee homage — caveman" translation_date: "2026-04-26" description: > AI pressure redirection — handling conflicting demands, tool failures, and competing constraints by blending with incoming force then reframing. Use when receiving contradictory instructions from different sources, during tool failure cascades where the planned approach becomes unviable, when scope pressure threatens to expand the task beyond what was asked, or when user frustration or correction needs to be absorbed rather than deflected. license: MIT allowed-tools: Read metadata: author: Philipp Thoss version: "1.0" domain: defensive complexity: intermediate language: natural tags: defensive, redirection, conflict-resolution, pressure-handling, meta-cognition, ai-self-application

引

AI 之壓引——融入來力、後改框使生果。非抗也。

用

• 受異源異命（用云X、項文云Y、工示Z）
• 工敗連鎖、所謀法失
• 範蔓脅、過所請
• 脈過載、信競致癱
• 用恚或正、需納非避
• center 顯壓擾衡

入

• 必：所對之壓或衝（隱於脈）
• 可：壓型分（見步一表）
• 可：前處之嘗與其果

行

一：對前先定中

入衝前、立中（見 center）。後明識來壓。

AI Pressure Type Taxonomy:
┌─────────────────────────┬──────────────────────────────────────────┐
│ Pressure Type           │ Characteristics                          │
├─────────────────────────┼──────────────────────────────────────────┤
│ Contradictory           │ Two valid sources give incompatible      │
│ Requirements            │ instructions. Neither is simply wrong.   │
│                         │ Resolution requires synthesis, not       │
│                         │ choosing sides                           │
├─────────────────────────┼──────────────────────────────────────────┤
│ Tool Failure Cascade    │ A planned approach fails at the tool     │
│                         │ level. Retrying won't help. The failure  │
│                         │ data itself contains useful information  │
├─────────────────────────┼──────────────────────────────────────────┤
│ Scope Creep             │ The task silently expands. Each addition │
│                         │ seems reasonable in isolation, but the   │
│                         │ aggregate exceeds what was asked         │
├─────────────────────────┼──────────────────────────────────────────┤
│ Context Overload        │ Too many files, too many constraints,    │
│                         │ too many open threads. Paralysis from    │
│                         │ excess input, not insufficient input     │
├─────────────────────────┼──────────────────────────────────────────┤
│ Ambiguity               │ The request is genuinely unclear and     │
│                         │ multiple interpretations are valid.      │
│                         │ Action risks solving the wrong problem   │
├─────────────────────────┼──────────────────────────────────────────┤
│ User Correction         │ The user indicates the current approach  │
│                         │ is wrong. The correction carries both    │
│                         │ information and emotional weight         │
└─────────────────────────┴──────────────────────────────────────────┘

分當前壓。多壓並行→識主先處；副者常隨解。

得：壓型與當前形之明分。分覺準、非強入類。

敗：壓不入任類→或為複合。解之：何部矛？何部範？處複需各部、勿視全為一問。

二：入身——進入力

向問移。全述其範、勿減、勿避、勿即提解。

1. 全述壓：何衝確？何敗確？何含糊確？
2. 名果：若不處、何發？
3. 識揭：工敗揭設；矛揭缺脈；蔓揭界不明

測：若問述安人、是避非入。入需全觸難。

• 避：「此二檔有微異。」
• 入：「CLAUDE.md 述 150 技、登錄含 148。或數誤、或登錄缺、或二技除而未更數。下游諸引或受影。」

得：完、不縮之問述。述使問更實、非更虛。

敗：入問致憂或急欲即解→停。入即入、非反。旨在見問明乃移。若不能述問而不同句提解→明分之。

三：轉——轉而引

入力既、樞至引向解。各壓型有特引法。

Redirect Patterns by Pressure Type:
┌─────────────────────────┬──────────────────────────────────────────┐
│ Pressure Type           │ Redirect Pattern                         │
├─────────────────────────┼──────────────────────────────────────────┤
│ Contradictory           │ Synthesize underlying intent: both       │
│ Requirements            │ sources serve a purpose. What goal do    │
│                         │ they share? Build from the shared goal,  │
│                         │ not from either source alone              │
├─────────────────────────┼──────────────────────────────────────────┤
│ Tool Failure Cascade    │ Use the failure data: what did the error │
│                         │ reveal about assumptions? The failure is │
│                         │ information. Switch tools or approach,   │
│                         │ incorporating what the failure taught    │
├─────────────────────────┼──────────────────────────────────────────┤
│ Scope Creep             │ Decompose to essentials: what was the    │
│                         │ original request? What is the minimum    │
│                         │ that satisfies it? Defer additions       │
│                         │ explicitly rather than silently absorbing│
├─────────────────────────┼──────────────────────────────────────────┤
│ Context Overload        │ Triage and sequence: which information   │
│                         │ is needed now vs. later vs. never? Rank  │
│                         │ by relevance to the immediate next step  │
├─────────────────────────┼──────────────────────────────────────────┤
│ Ambiguity               │ Surface the ambiguity to the user: "I   │
│                         │ see two interpretations — A and B. Which │
│                         │ do you mean?" Do not guess when asking   │
│                         │ is available                              │
├─────────────────────────┼──────────────────────────────────────────┤
│ User Correction         │ Absorb the correction fully: what was   │
│                         │ wrong, why was it wrong, what does the   │
│                         │ correct direction look like? Then adjust │
│                         │ without defensiveness or over-apology    │
└─────────────────────────┴──────────────────────────────────────────┘

施宜引。引應感如用問之能、非抗之。

得：壓由阻變向。矛成合機。敗成診數。載成序務。

敗：引覺強或不解壓→步一分或誤。再察：實矛乎、抑一源僅舊？實蔓乎、抑擴乃用所需？誤分致誤引。

四：受身——雅復

引或敗。壓真、不可化。受身即安落之術——認限而不大化。

1. 誠認限：「吾不能以現訊解此矛」「此法阻、未見替」
2. 存所進：摘所成、所學、所餘
3. 告用況：問為何、何嘗、何需以前
4. 識復路：何能解此？更訊？異法？用決？

Ukemi Recovery Checklist:
┌─────────────────────────┬──────────────────────────────────────────┐
│ Preserve                │ Summarize progress and learnings          │
│ Acknowledge             │ State the limitation without excuses      │
│ Communicate             │ Tell the user what is needed              │
│ Recover                 │ Identify the specific unblocking action   │
└─────────────────────────┴──────────────────────────────────────────┘

得：雅認、信存。用知何發、何嘗、何需。無訊失。

敗：認限覺如敗非通→記我號。受身為技、非弱。誠「吾困」與明請助、勝強解生新患。

五：亂取——多壓並至

多壓同至（用正+工敗+範問）→施亂取律。

1. 永不凍：擇一處。任動勝癱
2. 以壓制壓：工敗可解範問（「此功不能此實、故範自減」）
3. 壓下用簡技：淹則默最簡引——認各壓、序按急、依次處
4. 保察：處一時、餘留邊視。先處最急、勿失餘蹤

得：多壓下仍前行。非全並解、乃序處保進。

敗：多壓致癱→明列、按急數之。處一。起即破癱。若皆等急→擇最易解者先——速勝生勢。

六：殘心——解後續察

引壓後、保察二序果。

1. 引生新壓乎？（如以擇一義解矛、可廢前工）
2. 引滿底需乎、抑只表症？
3. 解穩乎、抑同壓復？
4. 記引模供後參——若此型復、應可更速

得：每引後簡掃二序。多引潔、然致連患者正殘心要處。

敗：二序果失、後現→即號當深殘心練。重要引後加一簡「此變何破？」察。

驗

• 壓已分特型、不留糊
• 入：問已全述、無減
• 轉：引用問之能、非抗
• 引敗→受身已施（誠認、進存）
• 多壓並至序處、不凍
• 殘心：引之二序果已察

忌

• 避代入：減問（「微異而已」）阻有效引、因全力未交。先入、後引
• 強引不合：非皆壓可即引。或需用入、更訊、或待。強引生新患
• 受身有我：視認限為己敗、非通換。用得早知、非強解
• 先處副：多壓並、易先處易者。覺生產而主壓滋。處最重、勿處最舒
• 略中：未立中即引→引變反。中非可選備——乃有效引基

參

• aikido — 此技所映人武術；體融與引之律導識壓處
• center — 有效引之先決；立穩基使引行
• awareness — 早察壓、急引前
• heal — 壓致子系偏時深復
• meditate — 處難壓後清餘噪