Benjamin Admin
b0435f9885
Schema-Papier statt capabilities.json (User-Entscheidung). Befund: die 8 SHARED_CAPABILITY- Cluster zerfallen in Typ-1 (technische Capabilities: mfa/tls/code_signing/session/anomaly) und Typ-2 (Sicherheitsziele: attack_surface_min/software_integrity = die #4-Gaps). Empfehlung Modell C: Capability = EINZIGE neue Klasse; Sicherheitsziele = CORE Legal Obligations (CORE/DOMAIN existiert bereits). Kanten-Graph (realized_by/specializes/...). guidance_basis gehört konzeptionell an die Capability. 4 Entscheidungen offen (User). #5b Materialisierung GEGATED auf Modell-Annahme — keine Daten verschoben. 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.