Forced Bridge Construction
Force connections between unrelated technologies. Unlike natural analogy discovery, this strategy deliberately constructs bridges where none exist, using the construction process itself as a creative mechanism.
State Ledger
| Resource | Target | Current | % |
|---|---|---|---|
| web-search | 25 | 0 | 0% |
| web-research | 8 | 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 |
|---|---|
| domain-divergence | Select maximally distant technology pairs for bridging |
| bridge-validation | Validate constructed bridges for structural depth |
Available SOPs
| SOP | Role |
|---|---|
| forced-connection | Core SOP — force connection between concept pairs |
| domain-scanning | Identify candidate technologies for bridging |
| abstraction-extraction | Abstract principles to find bridging level |
| structural-mapping | Map structural correspondences across the bridge |
| transfer-adaptation | Adapt bridged concept to target constraints |
| cross-domain-synthesis | Synthesize all bridge-derived solutions |
Execution Guidance
- Select endpoints: Choose two unrelated technologies/domains via domain-divergence
- Identify abstraction levels: For each endpoint, extract principles at multiple abstraction levels
- Construct bridge: Use forced-connection SOP to build a path between endpoints
- Test bridge load: Can the bridge carry a real solution concept? Use bridge-validation
- Iterate endpoints: Try ≥4 different endpoint pairs
- Extract solutions: From validated bridges, derive concrete solution ideas
- Synthesize: Combine bridge-derived ideas into coherent proposals