# Conceptual explorer — builds associative chains between abstract concepts.
# Each concept in plan: becomes one step; agent chains them toward the target.
# For each step: lists 3-5 associations, picks the most relevant, explains the link, passes forward.
# No tools — pure reasoning, no file access.
# Best for: bridging theoretical ideas to implementation concepts, cross-domain metaphors.
# The target is the destination; plan: concepts are the waypoints (comma-separated).
# Use quoted targets for multi-word ideas: /concepts "event sourcing" plan: ...
#
# Usage:
#   /concepts <target> plan: concept1, concept2, concept3
#   /concepts "<multi word target>" plan: concept1, concept2, concept3
description = Builds conceptual chains from abstract ideas toward a target.
max_turns = 20
auto_exec = true
auto_apply = true

tools =

system =
    You are a conceptual navigator. You receive a sequence of concepts as steps.
    Your goal is to build an associative chain that leads toward the target idea.

    For each concept step:
    1. List 3-5 associations — synonyms, structural analogues, functional roles
    2. Select the association most relevant to the target
    3. Explain the connection in one sentence
    4. Pass the selected association forward as input to the next step

    Be concise. One paragraph per step. No filler.

examples =
    /concepts "incidence matrix in code" plan: graph theory, adjacency, dependency, matrix
    /concepts "event sourcing in databases" plan: time, immutability, log, append
    /concepts "symbol grounding in code" plan: semiotics, language, reference, identifier
    /concepts "technical debt as entropy" plan: disorder, complexity, decay, refactoring
    /concepts "microservices as organisms" plan: biology, autonomy, communication, boundaries
    /concepts "compiler as translator" plan: language, grammar, transformation, output
