criteria-interrogation
$
npx mdskill add yogsoth-ai/de-anthropocentric-research-engine/criteria-interrogation**Purpose:** Question whether the evaluation framework used during convergence was itself valid — exposing hidden biases in criteria selection, weighting, and boundary definitions that may have predetermined the outcome.
SKILL.md
.github/skills/criteria-interrogationView on GitHub ↗
---
name: criteria-interrogation
description: Challenge the evaluation criteria themselves using Assumption-based Planning, Critical Systems Heuristics, and Boundary Critique to ensure the framework is sound.
used-by: steel-manning
---
# Criteria Interrogation
**Purpose:** Question whether the evaluation framework used during convergence was itself valid — exposing hidden biases in criteria selection, weighting, and boundary definitions that may have predetermined the outcome.
**When to use:**
- When criteria were inherited rather than deliberately designed
- When different criteria would produce different winners
- When stakeholders disagree about what matters
- When the evaluation framework has not been challenged
## Budget
| Metric | Minimum |
|--------|---------|
| Criteria challenged | All criteria used in convergence |
| Alternative framings | >= 2 alternative criteria sets |
| Boundary questions | >= 5 (who benefits, who is excluded) |
## State Ledger
```yaml
criteria_under_review: []
challenges_raised: {}
alternative_framings: []
sensitivity_to_criteria_change: {}
verdict: null # CRITERIA_SOUND | CRITERIA_BIASED | REWEIGHT
```
## Available Tactics
| Tactic | When to Deploy |
|--------|---------------|
| assumption-excavation | Default — treat criteria as assumptions to challenge |
| multi-perspective-attack | When criteria privilege certain stakeholders |
## Available SOPs
- assumption-extraction — surface assumptions embedded in criteria
- assumption-challenge — challenge each criterion's validity
- conclusion-sensitivity — test if outcome changes with different criteria
- perspective-assignment — assign stakeholder perspectives to criteria
- perspective-attack — attack criteria from each perspective
## Execution Guidance
1. List all criteria used in convergence with their weights
2. For each criterion, apply assumption-extraction (why this criterion?)
3. Challenge each criterion's inclusion, exclusion, and weight
4. Test conclusion sensitivity: would different weights change the winner?
5. If winner changes under reasonable alternative weighting, verdict is REWEIGHT
## Output Format
```yaml
strategy: criteria-interrogation
criteria_reviewed: <count>
challenges:
- criterion: <name>
challenge: <argument>
severity: HIGH | MEDIUM | LOW
alternative: <proposed change>
sensitivity_result: ROBUST | FRAGILE
verdict: CRITERIA_SOUND | CRITERIA_BIASED | REWEIGHT
recommended_changes: []
```
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.