breakpilot-compliance

Files

T

Benjamin Admin aaacec087c feat: Ownership-Konflikt #1 RESOLVED (Capability = geteilter Knoten) + Reasoning#1 Re-Link

User-Entscheidung: Feature->Capability + Certificate->Capability = Session 3 (Domaene 3), NICHT
Compliance. Capability = GETEILTER Knoten: eingehende Kanten (Feature/Cert->Cap) = Domaene 3 ·
Knoten+IDs+ausgehende Kanten (Cap->Obligation/Procedure/Control/Evidence) = Domaene 2. Expliziter
Vertrag: „Domaene 2 besitzt NIE Wissen, welche Produkte/Zertifikate welche Capabilities brauchen."
+ Ownership-Tabelle in session_ownership_model_v1.md.
Reasoning#1 (Domaene 2, Registry-Kanonisierung): obligations/proposed_obligation_canonical_map.json
— 5 machine_* -> cra_machinery (re-link, Ziele validiert), 7 data_act_*/cra_* pending (Regulierung
nicht geschnitten). RE-LINK, kein Re-Mint.

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

2026-06-26 21:54:07 +02:00

capabilities.json

feat: Capability Registry v1 API-Vertrag (#59 ) + Ownership-Modell finalisiert

2026-06-26 10:35:49 +02:00

controls_for_obligation_mapping.json

feat(ucca): re-point NIST primary_implementation to CORE obligations (#6 )

2026-06-26 09:35:46 +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