formated-results
Closing skill for the research-executor, loaded as the last step of formated-specs. Summarize the design just produced into one research-result JSON fenced…
Classic reductio ad absurdum: negate the core claim, derive logical
$ npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill assumption-negation --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/assumption-negationContext preview
The summary Claude sees to decide when to auto-load this skill.
Classic reductio ad absurdum: negate the core claim, derive logical
name: assumption-negation description: 'Classic reductio ad absurdum: negate the core claim, derive logical consequences, seek contradiction or absurdity.' type: strategy dependencies: tactics: - contradiction-derivation - counterexample-heuristics sops: - claim-negation - claim-refinement - contradiction-detection - deductive-chain
1. Extract the core claim or assumption from the artifact 2. Formally negate it (produce ~P from P) 3. Derive logical consequences of ~P through deductive chains 4. Evaluate whether derivation reaches genuine contradiction 5. If contradiction found: original claim survives this test 6. If no contradiction: claim may be contingent, not necessary
| Size | Negation chains | Max derivation depth | |---|---|---| | S | 3 | 5 steps | | M | 6 | 8 steps | | L | 10 | 12 steps |
1. Dispatch `claim-negation` to produce formal negation 2. For each negation, dispatch `deductive-chain` to derive consequences 3. Dispatch `contradiction-detection` to evaluate results 4. If no contradiction, dispatch `claim-refinement` for weakened version
<!-- BEGIN available-tables (generated) -->
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use | | --- | --- | | contradiction-derivation | Negate a claim, derive logical consequences step by step, detect whether a genuine contradiction or absurdity emerges. | | counterexample-heuristics | Generate counterexamples (monsters), attempt monster-barring, incorporate surviving counterexamples as lemma refinements (Lakatos method). |
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use | | --- | --- | | claim-negation | Formally negate the core claim, producing the logical complement for reductio testing. | | claim-refinement | Propose a refined claim that survives counterexamples while preserving maximum explanatory power (Lakatos lemma-incorporation). | | contradiction-detection | Evaluate whether a derivation chain has reached a genuine contradiction, absurdity, or inconclusive state. | | deductive-chain | Derive logical consequences step by step from a given premise, building a traceable derivation chain. |
<!-- END available-tables (generated) -->
The complete research orchestration system for AI-native science. What It Does Design Philosophy Architecture (v3.2.2) Quick Start Configuration Roadmap License DARE is not a tool that helps you do research. It is the researcher.
Repo: yogsoth-ai/de-anthropocentric-research-engine
Closing skill for the research-executor, loaded as the last step of formated-specs. Summarize the design just produced into one research-result JSON fenced…
Spec-slot skill for the research-executor. Emit the 4-layer DARE orchestration of the assigned topic as one research-graph JSON fenced block in your reply.…
Loss-1 judge (codex role). Given one sample's de-identified dialogue and its PolicyCard, decide axis-by-axis whether the user-simulator enacted the card's…
Loss-2 judge (codex role). Over one topic's 6 shuffled research-design samples, pairwise-rank by quality using the D1–D5 standard. Emit the pairwise log; the…
The optimizer brain for the ladder-foundry pretraining loop. Runs the two-level nested batch loop, delegates gating to gate_eval, attributes a failing batch to…
Tactic: Extract atomic units from one paper and score how much of a caller-supplied summary covers. Use for ACU-style binary or Nugget-style ternary recall…