ae73904ad5
CI / detect-changes (pull_request) Successful in 7s
CI / branch-name (pull_request) Successful in 1s
CI / guardrail-integrity (pull_request) Successful in 5s
CI / secret-scan (pull_request) Successful in 5s
CI / dep-audit (pull_request) Failing after 55s
CI / sbom-scan (pull_request) Failing after 1m0s
CI / build-sha-integrity (pull_request) Successful in 6s
CI / validate-canonical-controls (pull_request) Successful in 6s
CI / loc-budget (pull_request) Successful in 19s
CI / go-lint (pull_request) Successful in 41s
CI / python-lint (pull_request) Failing after 14s
CI / nodejs-lint (pull_request) Failing after 1m10s
CI / nodejs-build (pull_request) Successful in 3m3s
CI / test-go (pull_request) Successful in 59s
CI / iace-gt-coverage (pull_request) Successful in 17s
CI / test-python-backend (pull_request) Successful in 27s
CI / test-python-document-crawler (pull_request) Successful in 13s
CI / test-python-dsms-gateway (pull_request) Successful in 9s
The authority re-rank always ranked binding law above guidance, so a guideline could never be Top-1 even when the user explicitly asked "what does the EDPB / ENISA say?". Add a tightly-bounded override: only when the query carries an explicit guidance signal (EDPB / DSK / ENISA / BSI / Leitlinie / Guideline / Orientierungshilfe / Auslegung / empfiehlt / Empfehlung / sagt / laut) AND the guideline is semantically competitive with the best binding hit (>= best_binding - 0.05) does supervisory_guidance get a +0.25 boost that lets it overtake the binding norm. Obligation questions (no signal) are unchanged: binding stays #1. Gate verified on dev: - "Ab wann DSB-Pflicht?" -> Art. 37 DSGVO (binding) Top-1 - "Was empfiehlt der EDPB zum DSB?" -> EDPB guidance Top-1 - "Was sagt die ENISA zu Security Updates?" -> ENISA guidance Top-1 - "Welche Anforderungen an Security Updates?" -> Art. 13 CRA (binding) Top-1 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>