Adversarial Stress Testing

SkillDev tools

'Campaign: Logical extreme and boundary testing via reductio ad absurdum

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Adversarial Stress Testing skill

What this skill tells your AI

The instructions your AI receives, as published by yogsoth-ai/de-anthropocentric-research-engine in skills/adversarial-stress-testing/SKILL.md and read by ahel’s review.

Core Question: Does this artifact collapse under logical limits and boundary conditions?

Methodology Sources

  • Lakatos (1976) — Proofs and Refutations: counterexample-driven refinement
  • Dutilh Novaes (2016) — Adversarial argumentation as dialogical practice
  • Clarke BVA — Boundary Value Analysis for systematic edge testing
  • Flyvbjerg (2006) — Critical case methodology: most-likely/least-likely selection
  • Popper (1959) — Falsificationism: seek conditions where claims break

Strategy Routing

Artifact TypePrimary StrategyRationale
claim, hypothesisassumption-negationDirect logical attack
gap, research-questionlakatos-heuristicsCounterexample refinement
idea, approachboundary-enumerationParameter space testing
experiment-designcritical-case-designDecisive test selection
any (synthesis)validity-envelope-mappingComprehensive envelope

Budget Table

ResourceSML
Negation derivation chains3610
Counterexamples/boundary cases51225
Parameter dimensions3610
Validity envelope dimensions246

Tactics

  • contradiction-derivation — Negate, derive, detect contradiction
  • boundary-probing — Map parameter space, test extremes, find breakpoints
  • counterexample-heuristics — Generate monsters, bar or incorporate

Context Management

  • Persist derivation chains and counterexamples across rounds
  • Track which negations produced genuine contradictions vs. benign outcomes
  • Accumulate validity envelope boundaries incrementally

Output

Produces AdversarialStressReport containing: identified breakpoints, validity envelope, surviving refined claims, and confidence assessment.

Available Strategies

Optional, no fixed order; the final leaf is always a sop.

StrategyWhen to use
assumption-negationClassic reductio ad absurdum: negate the core claim, derive logical consequences, seek contradiction or absurdity.
boundary-enumerationSystematic Boundary Value Analysis: identify parameter boundaries, test at and beyond limits, detect breakpoints.
critical-case-designFlyvbjerg critical case methodology: select most-likely and least-likely cases to maximize inferential power.
lakatos-heuristicsProofs and Refutations method: generate counterexamples, attempt monster-barring, incorporate surviving counterexamples as lemma refinements.
stress-test-validity-envelope-mappingMap the complete validity envelope of a claim across all relevant dimensions, synthesizing breakpoints into a bounded region.

Available Tactics

Optional, no fixed order; the final leaf is always a sop.

TacticWhen to use
boundary-probingMap parameter space, generate extreme values, test at boundaries, detect breakpoints, synthesize validity envelope.
contradiction-derivationNegate a claim, derive logical consequences step by step, detect whether a genuine contradiction or absurdity emerges.
counterexample-heuristicsGenerate counterexamples (monsters), attempt monster-barring, incorporate surviving counterexamples as lemma refinements (Lakatos method).

Available SOPs

Optional, no fixed order; the final leaf is always a sop.

SOPWhen to use
context-checkpointAppend research process and results to the current Phase's context file. Covers both process and results with genuine substance. Use this skill at plan-designated checkpoint points — typically after each strategy completes or at key decision nodes within a research Phase.
context-initCreate a new context file for a research Phase. Called once at Phase start to initialize the file that subsequent context-checkpoint calls will append to. Use this skill whenever a new research Phase begins and a fresh context file is needed.
mitigation-proposalProposes concrete mitigation strategies for identified weaknesses. Generates prevention, detection, and response measures with feasibility assessment.
stress-test-saturation-detectionDetermines whether validation has reached saturation — no new weaknesses or failure modes being discovered. Used by all 5 campaigns as termination signal.
verdict-synthesisSynthesizes findings from a completed campaign into typed verdict reports. Produces DebateVerdict, RedTeamReport, FailureAnticipationReport, CounterfactualMap, or AdversarialStressReport depending on campaign. Also supports cross-campaign StressTestSummary.
weakness-classificationClassifies discovered weaknesses into severity tiers (fatal/major/minor/cosmetic) with structured justification and exploitability assessment.

Signals

GitHub stars
469
Forks
37
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
adversarial-stress-testing
Source
github.com/yogsoth-ai/de-anthropocentric-research-engine