Strategy: Assumption Constraint

SkillSecurity

Lets your agent rank which assumptions in an analysis are most fragile and assess their potential impact.

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 Strategy: Assumption Constraint skill

About this capability

Which assumptions are most fragile?, Vulnerability ranking + impact

What this skill tells your AI

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

Methodology

Systematic assumption vulnerability analysis:

  • Extraction: Surface all implicit and explicit assumptions
  • Scoring: Quantify vulnerability (confidence × evidence / testability)
  • Impact assessment: Blast radius × recovery cost
  • Prioritization: Vulnerability × Impact = Priority
  • Validation planning: Cheapest test that resolves uncertainty

Assumption categories:

CategoryExamples
TechnicalMethod convergence, architecture suitability
DataAvailability, quality, representativeness
ResourceSufficiency of compute, time, expertise
EnvironmentalTool stability, API access, policy
TheoreticalEffect existence, measurability, magnitude

Execution Flow

  1. Challenge Assumptions → call assumption-challenging SOP

    • Input: experiment plan, hypothesis
    • Output: assumption inventory with validity assessment
  2. Quantify Validation Cost → call resource-quantification SOP

    • Input: validation experiments for top assumptions
    • Output: cost to validate each assumption
  3. Rank Sensitivity → invoke sensitivity-ranking tactic

    • Determine which assumptions are most binding
  4. Report → synthesize vulnerability assessment

    • Top-5 fragile assumptions with validation paths
    • Binding assumption constraint identification

Budget Gate

ResourceBudgetNotes
Subagent calls≤52 SOPs + synthesis
Iterations≤2Re-rank if new assumptions surface
Output size≤3000 tokensRanked table + validation plan

Available Tactics

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

TacticWhen to use
sensitivity-rankingRank constraints by sensitivity — which ones most impact the outcome if they shift

Available SOPs

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

SOPWhen to use
assumption-challengingChallenge each assumption's validity — shared cross-repo SOP
resource-quantificationQuantify resource demand vs supply vs gap for each resource category

Signals

GitHub stars
481
Forks
37
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
assumption-constraint
Source
github.com/yogsoth-ai/de-anthropocentric-research-engine