Rework the Compliance Advisor header ("Diese Antwort stuetzt sich auf")
to describe the EVIDENCE rather than the documents: binding
Rechtsgrundlagen split from Leitlinien (soft-law guidance), a
per-regulation breakdown, plus Abbildungen, Fussnoten and Evidence Units.
No fabricated trust score — objective counts only.
- bindingness is a canonical Legal-KG fact (APEX rule): added an optional
EvidenceUnit.bindingness contract seam; the FE renders the split from it
and degrades to a neutral per-regulation breakdown when it is absent
(SDK/RAG asked via board to populate it in /retrieve).
- evidence-grouping.ts: pure, tested grouping/counting model.
- route.ts: optional `audience` field (tonality) kept out of the retrieval
question; answers lead with a "Kurz gesagt" summary, structured by theme.
- E2E + unit tests updated for the evidence framing.
Not deployed.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Per the "always write E2E" rule: drives the floating advisor widget end-to-end against a
stubbed /api/sdk/compliance-advisor/chat with contract fixtures — clarify (L1 + context
chips), answer ([n] citation + evidence pane), and clarify->pick-context->scoped-answer.
No backend needed (route interception). Runs on CI/macmini (Next app on :3002); validated
here via tsc + `playwright --list` (3 tests discovered). check-loc 0.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Benjamin Admin