breakpilot-compliance

Files

T

Benjamin Admin f23ae32077 feat: MaschVO als erster Multi-Regulation-Run + Reuse-Metrik (Freeze haelt: 0 neue Klassen)

User-Reframe: nicht „naechste Regulierung", sondern erster MULTI-REGULATION-Reuse-Test.
- obligations/cra_machinery.json: 31 MaschVO-Obligations (25 LM = Anhang-III-Essential-Reqs
  rechtlich legit + 6 BP). Pipeline 2229->1096 micro->120 review-units->Opus. out_of_scope
  41 RU (AI-Act/DSGVO/Common-Criteria/Banking/...).
- obligations/machinery_reuse_metrics.json: ERSTE Reuse-KPI. **NEUE OBJEKTKLASSEN = 0**
  (Architektur-Freeze haelt gegen physische-Safety-Regulierung — empirisch). 39% Reuse / 61%
  net-new; Capability-Reuse 2 (Cyber-Safety-Bruecke: access_control_safety_functions->access,
  protection_against_corruption->integrity/tamper), Procedure-Reuse 6, Evidence-Reuse 2,
  CORE-Spezialisierung 2 (risk_assessment->update_risk_assessment, conformity->sbom_tech_doc).
- join_keys 95->126 (machinery 31). precluster.py: machinery-Scope.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-06-26 10:05:00 +02:00

capabilities.json

feat: #5b materialize capability layer (Modell C) — capabilities.json + cra_core.json

2026-06-26 00:54:23 +02:00

controls_for_obligation_mapping.json

fill: NIST primary_implementation -> obligation_id (Handoff #4 , jetzt 10/10)

2026-06-25 19:15:49 +02:00

cra_authentication.json

feat: #5b materialize capability layer (Modell C) — capabilities.json + cra_core.json

2026-06-26 00:54:23 +02:00

cra_core.json

feat: #5b materialize capability layer (Modell C) — capabilities.json + cra_core.json