---
type: "query"
date: "2026-06-10T06:42:14.745783+00:00"
question: "How does the DiGA Lyra requirement (REQ-LYRA) reach its implementation across community boundaries?"
contributor: "graphify"
source_nodes: ["REQ-LYRA Lyra KI-Coach & Krisen-Behandlung", "Lyra Modi (SOS-Crisis-Mode / Coach-Casual-Mode)", "SAFETY-REQ-LLM-001 Krisenreferenz-Pflicht", "R-LYRA-01 verpasste Krise/Suizidalität", "lyraResponse.ts", "sosConstants.ts"]
---

# Q: How does the DiGA Lyra requirement (REQ-LYRA) reach its implementation across community boundaries?

## Answer

Expanded from original query via graph vocab to tokens: [lyra, diga, requirements, req, crisis, krise, krisen, sos, coach, persona, groq, haiku]. Substring BFS anchored on the i18n 'coach' locale key and was swamped by locale strings, so traced surgically via graph.json instead. FINDING: REQ-LYRA sits in a tight, fully-connected 155-node DiGA regulatory spine — references the 57-REQ requirements index, R-LYRA-01 top risk (verpasste Krise/Suizidalitaet S4), SAFETY-REQ-LLM-001 Krisenreferenz-Pflicht (recall 100%), the datenschutz audit (Groq/Schrems-II/ZDR), Zweckbestimmung (ICD-10 F63.0), and the ops Lyra Persona doc (SOS-Crisis vs Coach-Casual modes, Forbidden Vocabulary). BUT there is NO PATH from this spine to the actual code: lyra.tsx, lyraResponse.ts, sosConstants.ts, and backend lyra routes form a SEPARATE connected island. The doc/regulatory layer (LLM-extracted) and the code layer (AST-extracted) are structurally disconnected — the requirement-to-code traceability edges do not exist in the graph. This mirrors a node that literally appears inside the spine: 'Fehlende Traceability-Matrix (Tests<->Anforderungen<->Risiken)'. The spine even names crisis-filter.ts in a doc node without an edge to the code file.

## Source Nodes

- REQ-LYRA Lyra KI-Coach & Krisen-Behandlung
- Lyra Modi (SOS-Crisis-Mode / Coach-Casual-Mode)
- SAFETY-REQ-LLM-001 Krisenreferenz-Pflicht
- R-LYRA-01 verpasste Krise/Suizidalität
- lyraResponse.ts
- sosConstants.ts