version: 0.2.0
context: >
  Chain Templates beschreiben typische Konstellationen als Slots + erlaubte Rollen.
  Sie dienen der Analyse (Lücken, Pfade, Start-/Endpunkte), nicht zum automatischen Schreiben.
  Templates sind YAML-driven und werden von Obsidian-Plugin und Mindnet gemeinsam genutzt.

# -------------------------------------------------------------------
# DEFAULTS (optional, permissive):
# - Das Plugin kann Felder ignorieren, die es (noch) nicht nutzt.
# - Mindnet kann später dieselben Profile-Namen verwenden oder per Mapping adaptieren.
# -------------------------------------------------------------------
defaults:

  # Matching-Defaults (Plugin v0.4.x kann zumindest required_links/distinct_nodes nutzen)
  matching:
    distinct_nodes: true
    required_links: true
    max_candidate_nodes: 30
    max_matches_per_template: 1

  # Rollen-Defaults (Referenz auf chain_roles.yaml Rollen)
  roles:
    causal_ish: [causal, influences, enables_constraints]

  # Profile-Defaults: gleiche Templates, unterschiedliche Strenge in der Auswertung
  profiles:
    discovery:
      required_links: false
      min_slots_filled_for_gap_findings: 2
      min_score_for_gap_findings: 8
    decisioning:
      required_links: true
      min_slots_filled_for_gap_findings: 3
      min_score_for_gap_findings: 18

templates:

  # ================================================================
  # 1) Core: Trigger → Transformation → Outcome
  # ================================================================
  - name: "trigger_transformation_outcome"
    description: "Wendepunkt/Trigger → innere Veränderung (Insight/Value/Belief) → Ergebnis/Handlung."
    matching:
      # Template kann bei Bedarf vom Default abweichen
      required_links: true
      distinct_nodes: true
    slots:
      - id: trigger
        allowed_node_types: [experience, event, obstacle, risk, state]
      - id: transformation
        allowed_node_types: [insight, belief, value, principle, trait, skill, boundary]
      - id: outcome
        allowed_node_types: [decision, project, habit, goal]
    links:
      - from: trigger
        to: transformation
        allowed_edge_roles: [causal, influences, provenance]
      - from: transformation
        to: outcome
        allowed_edge_roles: [causal, influences, enables_constraints]

  # ================================================================
  # 2) Core: Decision Logic (Driver + Constraint → Decision → Outcome)
  # ================================================================
  - name: "decision_logic"
    description: "Wert/Prinzip/Motivation + Constraints → Entscheidung → Outcome/Projekt."
    slots:
      - id: driver
        allowed_node_types: [value, principle, motivation, need, goal]
      - id: constraint
        allowed_node_types: [risk, obstacle, state, boundary]
      - id: decision
        allowed_node_types: [decision, task]
      - id: outcome
        allowed_node_types: [project, habit, goal]
    links:
      - from: driver
        to: decision
        allowed_edge_roles: [influences, enables_constraints]
      - from: constraint
        to: decision
        allowed_edge_roles: [enables_constraints, influences]
      - from: decision
        to: outcome
        allowed_edge_roles: [causal, influences]

  # ================================================================
  # 3) Core: Learning Loop (Experience → Learning → Behavior → Feedback)
  # ================================================================
  - name: "loop_learning"
    description: "Wiederkehrendes Muster: Experience → Insight/Principle → Behavior/Decision → neue Experience."
    slots:
      - id: experience
        allowed_node_types: [experience, journal, event]
      - id: learning
        allowed_node_types: [insight, principle, value, belief, skill, trait]
      - id: behavior
        allowed_node_types: [habit, decision, task]
      - id: feedback
        allowed_node_types: [experience, journal, event, state]
    links:
      - from: experience
        to: learning
        allowed_edge_roles: [causal, provenance, influences]
      - from: learning
        to: behavior
        allowed_edge_roles: [influences, enables_constraints, causal]
      - from: behavior
        to: feedback
        allowed_edge_roles: [causal, influences]

  # ================================================================
  # 4) Core: Constraint → Adaptation/Regulation → Stabilization
  # ================================================================
  - name: "constraint_to_adaptation"
    description: "Begrenzung/Problem → Anpassung/Regulation → Stabilisierung (Prinzip/Wert/Habit/Projekt)."
    slots:
      - id: constraint
        allowed_node_types: [risk, obstacle, state, boundary]
      - id: adaptation
        allowed_node_types: [skill, trait, habit, boundary, insight, principle]
      - id: stabilization
        allowed_node_types: [principle, value, habit, project, goal]
    links:
      - from: constraint
        to: adaptation
        allowed_edge_roles: [causal, influences, enables_constraints, provenance]
      - from: adaptation
        to: stabilization
        allowed_edge_roles: [causal, influences, enables_constraints]

  # ================================================================
  # 5) Core: Person Influence (Person → Inner Model → Decision/Outcome)
  # ================================================================
  - name: "person_influence"
    description: "Person/Beziehungseinfluss → Belief/Insight/Skill/Trait → Entscheidung/Outcome."
    slots:
      - id: person
        allowed_node_types: [person]
      - id: internal_model
        allowed_node_types: [belief, insight, value, principle, skill, trait, boundary, bias]
      - id: outcome
        allowed_node_types: [decision, habit, project, goal]
    links:
      - from: person
        to: internal_model
        allowed_edge_roles: [influences, provenance, causal]
      - from: internal_model
        to: outcome
        allowed_edge_roles: [influences, enables_constraints, causal]

  # ================================================================
  # 6) Core: State → Trigger → Response → State/Outcome (empathy-ready)
  # ================================================================
  - name: "state_trigger_response"
    description: "Zustand → Auslöser → Reaktion/Verhalten → neuer Zustand/Outcome."
    slots:
      - id: state
        allowed_node_types: [state]
      - id: trigger
        allowed_node_types: [experience, event, obstacle, risk]
      - id: response
        allowed_node_types: [habit, decision, task]
      - id: next_state_or_outcome
        allowed_node_types: [state, goal, project, habit]
    links:
      - from: state
        to: trigger
        allowed_edge_roles: [influences, causal, provenance]
      - from: trigger
        to: response
        allowed_edge_roles: [causal, influences, enables_constraints]
      - from: response
        to: next_state_or_outcome
        allowed_edge_roles: [causal, influences]