Benjamin Admin
63fe2d496e
User-Antwort auf „wie verteilen wir die Arbeit": nach BESITZ der Datenmodelle, NICHT nach Regulierung. 3 Domaenen (Legal Knowledge / Compliance Execution / Product Knowledge), jede besitzt EIN Modell (andere read-only). 3 Vertraege: Legal->Compliance citation_span->legal_basis · Product->Compliance Feature->Capability (WICHTIGSTE Schnittstelle) · Compliance->Legal obligation_id->legal_basis. Product Knowledge Graph = naechster Meilenstein (Reasoning-Session umfokussieren, besitzt schon CanonicalProductRegulatoryProfile+Navigator). NIS2 verschoben. Offene Fragen: Legal-KG-Owner, IACE-4.-Session, Compliance-2-Branch-Split. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
docs-src
MkDocs-based internal documentation site — system architecture, data models, runbooks, API references.
Port: 8011 (container: bp-compliance-docs)
Stack: MkDocs + Material theme, served via nginx.
Build + serve locally
cd docs-src
pip install -r requirements.txt
mkdocs serve # http://localhost:8000
mkdocs build # static output to site/
Known debt (Phase 4)
index.mdis 9436 lines — will be split into per-topic pages with proper mkdocs nav. Target: no single markdown file >500 lines except explicit reference tables.