conflict-resolution
$
npx mdskill add yogsoth-ai/de-anthropocentric-research-engine/conflict-resolutionResolves conflicting constraints using Evaporating Cloud and assumption challenging
- Identifies and resolves contradictions between mutually exclusive constraints
- Uses Evaporating Cloud, assumption-challenging SOPs, and Future Reality Tree projections
- Analyzes assumptions underlying conflicting demands to find invalid ones
- Delivers actionable injections that eliminate conflicts without unintended effects
SKILL.md
.github/skills/conflict-resolutionView on GitHub ↗
---
name: conflict-resolution
description: "How do constraints conflict with each other? — Evaporating Cloud + assumption challenging + injection to resolve constraint conflicts"
version: 1.0.0
category: experiment-execution
type: strategy
used-by: constraint-analysis
sops:
- core-conflict-extraction
- assumption-challenging
- future-reality-projection
tactics:
- constraint-breaking
---
# Strategy: Conflict Resolution
## Methodology
Based on Goldratt's Evaporating Cloud (EC) and injection methodology:
- **Surface the conflict**: Express opposing demands in EC format
- **Challenge assumptions**: Each EC arrow rests on assumptions — find the invalid one
- **Inject**: Propose an action that invalidates the false assumption
- **Project future**: Use Future Reality Tree to verify injection resolves the conflict without creating new UDEs
Evaporating Cloud structure:
```
B ←── D
↗ ↘ (conflict)
A
↘ ↗ (conflict)
C ←── D'
```
- A: Common objective both sides want
- B: Need that leads to wanting D
- C: Need that leads to wanting D'
- D and D': Mutually exclusive wants
## Execution Flow
1. **Extract Core Conflict** → call `core-conflict-extraction` SOP
- Input: identified constraints that oppose each other
- Output: Evaporating Cloud (A-B-C-D-D') with assumptions on each arrow
2. **Challenge Assumptions** → call `assumption-challenging` SOP
- Input: assumptions underlying each EC arrow
- Output: validity assessment, weakest assumptions identified
3. **Generate Injections** → synthesize from challenged assumptions
- For each invalid assumption, propose an injection (action that makes the conflict disappear)
4. **Project Future Reality** → call `future-reality-projection` SOP
- Input: proposed injections
- Output: Future Reality Tree showing resolved conflict + any new UDEs
5. **Validate Resolution** → invoke `constraint-breaking` tactic
- Orchestrate full resolution cycle
## Budget Gate
| Resource | Budget | Notes |
|----------|--------|-------|
| Subagent calls | ≤8 | 3 SOPs + injection generation + validation |
| Iterations | ≤3 | May need multiple injection attempts |
| Output size | ≤3000 tokens | EC + injection + FRT summary |
More from yogsoth-ai/de-anthropocentric-research-engine
- abductive-hypothesis-generationStrategy: 面对异常的最佳解释推理
- ablation-brainstormRemove components one by one, observe system changes to reveal hidden dependencies and generate ideas from structural gaps.
- ablation-component-mappingMap system architecture to ablatable units for ablation studies
- ablation-designDesign ablation studies to isolate component contributions in ML systems
- ablation-executionRemove components one by one from a system, record the response/impact of each removal.
- abp-vulnerability-classificationClassify assumptions on 2 axes — load-bearing (how much conclusion depends on it) × vulnerable (how likely to be false). Focuses attention on High-Load × High-Vulnerable quadrant.
- abstraction-extractionExtract abstract principles from concrete domain cases. Strips domain-specific details to reveal transferable mechanisms.
- abstraction-ladderPerform bisociation at multiple abstraction levels
- abstraction-ladderingMove between concrete and abstract framings — 3 levels up (Why?) and 3 levels down (How?) to find the most productive research level.
- abstraction-to-designAbstract biological principle to design principle. Bridge from biology to engineering.