Boundary Analysis
Probe where methods fail — validity envelopes, robustness, failure modes, scaling limits.
Design Philosophy
This campaign is a strategy book — CC reads, internalizes, and autonomously constructs an approach. The SKILL.md files are textbooks, not scripts.
Strategy Routing
| Signal |
Strategy |
| Valid conditions, applicability range, multi-axis variation, degradation curves |
→ validity-envelope-mapping |
| Cross-method consistency, multi-model convergence, Wimsatt robustness |
→ robustness-testing |
| System boundaries, inclusion/exclusion, CSH critique |
→ boundary-critique |
| Failure modes, boundary inputs, distribution shift, adversarial |
→ failure-mode-analysis |
| Scaling limits, scaling law, behavioral phase transitions, capacity |
→ scaling-frontier |
Available Tactics
- multi-model-convergence — Wimsatt-style cross-validation
- systematic-perturbation — multi-axis validity probing
- failure-mode-cataloging — systematic failure taxonomy
Available SOPs
Import (5): web-search, web-research, paper-overview, paper-search, paper-research
Subagent (11): assumption-enumeration, alternative-model-generation, convergence-assessment, fragility-flagging, variation-axis-definition, controlled-perturbation, validity-envelope-construction, edge-case-generation, failure-clustering, scaling-regime-detection, boundary-synthesis
Shared (1): evidence-synthesis
Context Management
context-checkpoint after each strategy completes.
Available Strategies
Optional, no fixed order; the final leaf is always a sop.
| Strategy |
When to use |
| boundary-critique |
Apply CSH boundary critique — what is included/excluded, who benefits/is harmed, what expertise is privileged/marginalized. Identifies opportunities at the boundaries. |
| deep-insight-validity-envelope-mapping |
Map multi-dimensional validity envelopes — define variation axes, perturb systematically, measure degradation, construct boundary surface. |
| failure-mode-analysis |
Systematically catalog failure modes — generate edge cases, observe failures, cluster by mechanism, identify triggers and frequency. |
| robustness-testing |
Test conclusion robustness via multi-model convergence — enumerate assumptions, generate alternatives, compare results, flag fragile conclusions. |
| scaling-frontier |
Analyze behavior across scales — detect regime changes, identify capacity limits, fit scaling laws within regimes. |
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP |
When to use |
| boundary-synthesis |
Compile all boundary analysis products into a coherent report — validity envelopes, robustness results, failure catalogs, scaling maps, safe operating conditions. |
| context-checkpoint |
Append research process and results to the current Phase's context file. Each append MUST contain >=500 lines of markdown covering both process and results. Use this skill at plan-designated checkpoint points — typically after each strategy completes or at key decision nodes within a research Phase. |
| context-init |
Create 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. |
1---2name: boundary-analysis-23description: Boundary Analysis Campaign — probe where methods fail, map validity envelopes, test robustness, catalog failure modes, detect scaling limits. 5 strategies, 3 tactics, 11 subagent SOPs.4---56# Boundary Analysis78Probe where methods fail — validity envelopes, robustness, failure modes, scaling limits.910## Design Philosophy1112This campaign is a strategy book — CC reads, internalizes, and autonomously constructs an approach. The SKILL.md files are textbooks, not scripts.1314## Strategy Routing1516| Signal | Strategy |17|--------|----------|18| Valid conditions, applicability range, multi-axis variation, degradation curves | → validity-envelope-mapping |19| Cross-method consistency, multi-model convergence, Wimsatt robustness | → robustness-testing |20| System boundaries, inclusion/exclusion, CSH critique | → boundary-critique |21| Failure modes, boundary inputs, distribution shift, adversarial | → failure-mode-analysis |22| Scaling limits, scaling law, behavioral phase transitions, capacity | → scaling-frontier |2324## Available Tactics2526- multi-model-convergence — Wimsatt-style cross-validation27- systematic-perturbation — multi-axis validity probing28- failure-mode-cataloging — systematic failure taxonomy2930## Available SOPs3132**Import (5):** web-search, web-research, paper-overview, paper-search, paper-research3334**Subagent (11):** assumption-enumeration, alternative-model-generation, convergence-assessment, fragility-flagging, variation-axis-definition, controlled-perturbation, validity-envelope-construction, edge-case-generation, failure-clustering, scaling-regime-detection, boundary-synthesis3536**Shared (1):** evidence-synthesis3738## Context Management3940context-checkpoint after each strategy completes.4142<!-- BEGIN available-tables (generated) -->4344## Available Strategies4546Optional, no fixed order; the final leaf is always a sop.4748| Strategy | When to use |49| --- | --- |50| boundary-critique | Apply CSH boundary critique — what is included/excluded, who benefits/is harmed, what expertise is privileged/marginalized. Identifies opportunities at the boundaries. |51| deep-insight-validity-envelope-mapping | Map multi-dimensional validity envelopes — define variation axes, perturb systematically, measure degradation, construct boundary surface. |52| failure-mode-analysis | Systematically catalog failure modes — generate edge cases, observe failures, cluster by mechanism, identify triggers and frequency. |53| robustness-testing | Test conclusion robustness via multi-model convergence — enumerate assumptions, generate alternatives, compare results, flag fragile conclusions. |54| scaling-frontier | Analyze behavior across scales — detect regime changes, identify capacity limits, fit scaling laws within regimes. |5556## Available SOPs5758Optional, no fixed order; the final leaf is always a sop.5960| SOP | When to use |61| --- | --- |62| boundary-synthesis | Compile all boundary analysis products into a coherent report — validity envelopes, robustness results, failure catalogs, scaling maps, safe operating conditions. |63| context-checkpoint | Append research process and results to the current Phase's context file. Each append MUST contain >=500 lines of markdown covering both process and results. Use this skill at plan-designated checkpoint points — typically after each strategy completes or at key decision nodes within a research Phase. |64| context-init | Create 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. |6566<!-- END available-tables (generated) -->
yogsoth-ai