Files
breakpilot-compliance/backend-compliance/tests
Benjamin Admin d3ac33d53a
CI / build-sha-integrity (push) Failing after 4s
CI / validate-canonical-controls (push) Successful in 12s
CI / loc-budget (push) Successful in 15s
CI / go-lint (push) Has been skipped
CI / python-lint (push) Has been skipped
CI / detect-changes (push) Successful in 7s
CI / branch-name (push) Has been skipped
CI / guardrail-integrity (push) Has been skipped
CI / secret-scan (push) Has been skipped
CI / dep-audit (push) Has been skipped
CI / sbom-scan (push) Has been skipped
CI / nodejs-lint (push) Has been skipped
CI / nodejs-build (push) Has been skipped
CI / test-go (push) Has been skipped
CI / iace-gt-coverage (push) Has been skipped
CI / test-python-backend (push) Successful in 31s
CI / test-python-document-crawler (push) Has been skipped
CI / test-python-dsms-gateway (push) Has been skipped
feat(impressum): v3 — Layer-Architektur auf doc_check_controls (75 DB-MCs)
Sprint 1.12 Phase 1 (User-Vorgabe 2026-06-09):

Statt eigener 12 hartgepatchter Patterns nutzt der Impressum-Agent jetzt
die 75 echten Master-Controls aus compliance.doc_check_controls. Pipeline:

  Layer 0  — Regex-Boost (meine 12 Patterns aus mcs.py / regex_boost.py)
             → wenn Pattern hits, MC wird zu PASS überschrieben
  Layer 1  — Keyword-Match aus pass_criteria der 75 DB-MCs
             (rag_document_checker.check_document_with_controls)
  Layer 2  — BGE-M3 Embedding-Match (in rag_document_checker integriert)
  Layer 3  — Semantic-Validator (LLM) für übriggebliebene HIGH/MEDIUM
             + Auto-Learning-Pattern-Library

Output-Layer bleibt unverändert: Disclaimer-Linter + Rollup-Dedup +
Methodik-First-UI.

Neue Dateien:
  - impressum/v3_engine.py       — Pipeline-Orchestrator
  - impressum/regex_boost.py     — meine 12 Patterns + Boost-Mapping

Refactored:
  - impressum/agent.py           — komplett umgeschrieben, agent_version=3.0
                                    255 LOC (unter 500-Cap)

Tests: test_impressum_v3.py mit 10 neuen Tests, alle gruen. Mockt
run_v3_pipeline für offline-Lauf. Bestaetigt:
  - Layer-0 erkennt Tesla-typische Felder
  - Boost matched DB-MC nur bei ≥2 Keyword-Treffern in pass_criteria
  - 12 Pattern-Boost-Slots + N DB-MCs in coverage
  - Notes enthalten Telemetrie (v3-pipeline, Boost-Overrides)

Telemetrie wird in AgentOutput.notes ausgegeben, damit Frontend
sehen kann: 75 DB-MCs geprueft · 5 Pattern-Boosts · 3 Boost-Overrides.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-06-09 08:58:53 +02:00
..