| name | ablation-brainstorm |
| description | Remove components one by one, observe system changes to reveal hidden dependencies and generate ideas from structural gaps. |
| execution | strategy |
| dependencies | {"sops":["ablation-execution","dependency-identification","enumeration-synthesis"],"tactics":["coverage-analysis"]} |
Ablation Brainstorm
Systematically remove components from a system one by one, observe what changes, and use the resulting insights to generate novel ideas.
State Ledger
| Resource | Target | Current | % |
|---|
| web-search | 20 | 0 | 0% |
| web-research | 5 | 0 | 0% |
| paper-overview | 20 | 0 | 0% |
| paper-search | 12 | 0 | 0% |
| paper-research | 5 | 0 | 0% |
HARD-GATE
Cannot exit strategy until ≥80% of each budget line is consumed OR yield targets are met with justification for remaining budget.
Available Tactics
| Tactic | Role |
|---|
| coverage-analysis | Ensure all components are ablated |
| evaluation-filtering | Score and filter ablation-derived ideas |
Available SOPs
| SOP | Role |
|---|
| ablation-execution | Remove components one by one, record responses |
| dependency-identification | Extract dependency graph from ablation results |
| enumeration-synthesis | Synthesize ablation insights into idea report |
Execution Guidance
- Decompose: List all components of the target system
- Ablate: Run ablation-execution — remove each component, record effects
- Analyze: Run dependency-identification to find critical dependencies
- Ideate: For each critical dependency, ask "what if this were replaced/eliminated/redesigned?"
- Filter: Apply evaluation-filtering to rank generated ideas
- Synthesize: Produce structured report via enumeration-synthesis
Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use |
|---|
| coverage-analysis | Systematic coverage evaluation pipeline — benchmark inventory, method-problem crossing, and intersection evaluation to map explored vs unexplored solution space. |
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use |
|---|
| ablation-execution | Remove components one by one from a system, record the response/impact of each removal. |
| dependency-identification | Identify critical dependencies from ablation results, producing a dependency graph and highlighting critical components. |
| enumeration-synthesis | Synthesize all systematic enumeration outputs into a structured idea report with prioritized recommendations. |