Benjamin Admin
d44f3672be
User decision (2026-06-28): provisional acceptance. Journey is now the preferred way of THINKING, but the persisted artifact stays "Transition Pattern" — NO rename, NO migration, NO runtime change. Per the Rule of Three, Journey becomes the official primary entity only after it proves itself on >=3 distinct transitions (1. ISO27001->CRA done, 2. ISO9001->MaschinenVO, 3. TISAX->CRA). Only then: rename to Journey, ratify ADR-011, derive renderers officially. Erst beweisen, dann kanonisieren — as with Master Controls/Capabilities. Also makes the two-axis separation durable (the most valuable finding): Atomic Requirement -> Capability -> Journey (transition axis) vs Capability -> Playbook (implementation axis). Journey belongs to the transition; Playbook stays capability-owned, referenced by any number of journeys. We do NOT force-unify. Non-runtime doc -> no deploy (ADR-001). 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.