Strategy: Assumption Constraint
SkillSecurityWhich assumptions are most fragile? — Vulnerability ranking + impact
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Strategy: Assumption Constraint skill
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:
| Category | Examples |
|---|---|
| Technical | Method convergence, architecture suitability |
| Data | Availability, quality, representativeness |
| Resource | Sufficiency of compute, time, expertise |
| Environmental | Tool stability, API access, policy |
| Theoretical | Effect existence, measurability, magnitude |
Execution Flow
-
Challenge Assumptions → call
assumption-challengingSOP- Input: experiment plan, hypothesis
- Output: assumption inventory with validity assessment
-
Quantify Validation Cost → call
resource-quantificationSOP- Input: validation experiments for top assumptions
- Output: cost to validate each assumption
-
Rank Sensitivity → invoke
sensitivity-rankingtactic- Determine which assumptions are most binding
-
Report → synthesize vulnerability assessment
- Top-5 fragile assumptions with validation paths
- Binding assumption constraint identification
Budget Gate
| Resource | Budget | Notes |
|---|---|---|
| Subagent calls | ≤5 | 2 SOPs + synthesis |
| Iterations | ≤2 | Re-rank if new assumptions surface |
| Output size | ≤3000 tokens | Ranked table + validation plan |
Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use |
|---|---|
| sensitivity-ranking | Rank 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.
| SOP | When to use |
|---|---|
| assumption-challenging | Challenge each assumption's validity — shared cross-repo SOP |
| resource-quantification | Quantify resource demand vs supply vs gap for each resource category |
Signals
- GitHub stars
- 469
- Forks
- 37
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
assumption-constraint- Source
- github.com/yogsoth-ai/de-anthropocentric-research-engine