forced-bridge-construction
$
npx mdskill add yogsoth-ai/de-anthropocentric-research-engine/forced-bridge-constructionForce 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.
SKILL.md
.github/skills/forced-bridge-constructionView on GitHub ↗
--- name: forced-bridge-construction description: Force connections between unrelated technologies. Deliberately construct bridges where none naturally exist to discover novel integration possibilities. execution: strategy used-by: cross-domain-discovery --- # 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 1. **Select endpoints**: Choose two unrelated technologies/domains via domain-divergence 2. **Identify abstraction levels**: For each endpoint, extract principles at multiple abstraction levels 3. **Construct bridge**: Use forced-connection SOP to build a path between endpoints 4. **Test bridge load**: Can the bridge carry a real solution concept? Use bridge-validation 5. **Iterate endpoints**: Try ≥4 different endpoint pairs 6. **Extract solutions**: From validated bridges, derive concrete solution ideas 7. **Synthesize**: Combine bridge-derived ideas into coherent proposals