causal-necessity-testing
$
npx mdskill add yogsoth-ai/de-anthropocentric-research-engine/causal-necessity-testingPNS evaluation: for each causal claim, determine whether the cause is necessary, sufficient, both, or neither.
SKILL.md
.github/skills/causal-necessity-testingView on GitHub ↗
--- name: causal-necessity-testing description: "Tactic: Extract causal claims, evaluate probability of necessity (PN) and sufficiency (PS) for each, classify into necessity-sufficiency quadrants." type: tactic used-by: [counterfactual-probing] strategies: [necessity-sufficiency, structural-counterfactual, thought-experiment] --- # Causal Necessity Testing Tactic PNS evaluation: for each causal claim, determine whether the cause is necessary, sufficient, both, or neither. ## Orchestration 1. **causal-claim-extraction** extracts all X→Y causal claims from the artifact 2. **necessity-evaluation** asks: if X had NOT occurred, would Y still hold? (PN) 3. **sufficiency-evaluation** asks: if X occurred in isolation, would Y follow? (PS) 4. Classify each claim into quadrant: - PN high + PS high → INUS condition (load-bearing) - PN high + PS low → necessary but not sufficient - PN low + PS high → sufficient but redundant - PN low + PS low → spurious or decorative 5. **load-bearing-identification** synthesizes quadrant assignments ## Scoring - PN and PS scored 0.0–1.0 (probability estimates) - Threshold for "high": >= 0.7 - Threshold for "low": < 0.3 - Middle range (0.3–0.7): uncertain, flag for deeper investigation ## Subagents Dispatched - causal-claim-extraction (claim identification) - necessity-evaluation (PN scoring per claim) - sufficiency-evaluation (PS scoring per claim) - load-bearing-identification (quadrant synthesis) ## Termination Conditions - All extracted claims evaluated within budget - Early termination if INUS condition found and budget is S - All claims score PN < 0.3 (no necessary factors found — conclusion may be overdetermined)
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.