breakpilot-compliance

Files

T

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

#59 (geschaerft, User): capabilities.json -> capability_registry_v1 (contract_version 1.0):
stabile `cap.*`-IDs (NIE umbenennen) + 5 Vertragsfelder (description/guidance_basis/
realizes_obligations/required_procedures/evidence_patterns), PRODUKTNEUTRAL (keine Features).
= stabiler API-Vertrag fuer die Product->Compliance-Schnittstelle (Feature->Capability,
Session 3 mappt read-only dagegen).
session_ownership_model_v1.md RESOLVED: Legal-Owner = Re-Ingest-Session (vergibt KEINE
obligation_id, nur citation_span->legal_basis) · 4. Session -> Quality & Validation (nur
Tests, KEINE Daten) · Compliance 2 Branches DAUERHAFT (A=Build, B=Runtime). 4-Bibliotheken-
Zielbild (Legal/Product/Capability/Evidence).

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

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

_core.py

Add obligation discovery pipeline tooling

2026-06-25 07:41:45 +02:00

advisor_proof.py

Extend advisor proof with procedure→evidence chain

2026-06-25 09:44:27 +02:00

classify_relationships.py

feat: cross-domain relationship discovery — Capability-Schicht-Entwurf (CRA P1)

2026-06-25 19:12:17 +02:00

cross_domain_pairs.py

feat: cross-domain relationship discovery — Capability-Schicht-Entwurf (CRA P1)