feat(programs): Operational Knowledge — the transition is the unit + Transition Coverage KPI

Customers don't buy "EMV domain"; they buy "we have ISO 9001, help us with the CRA". The sellable
unit of knowledge is the TRANSITION (from -> to), not the law and not the capability. This reframes
the backlog from "model EMV next" to "the top demanded transitions". No new runtime framework (ADR-010).

- knowledge/programs/transitions.yaml: the Operational Knowledge backlog — the ~20-30 actually demanded
  transitions (of ~N*(N-1) possible) with priority. ISO27001->CRA, ISO9001->CRA, ISO9001->MaschinenVO
  (all 5-star), IEC62443->CRA, TISAX->CRA, ISO27001/IEC62443->NIS2, ISO14001->Umweltrecht.
- Transition Coverage KPI (reference suite, computed-not-stored): per transition a status DERIVED from
  the transition-pattern corpus (reviewed/validated/proven -> Gold, draft -> 🟡, none -> ⚪). Honest
  current state: ISO27001->CRA ✅ reviewed, ISO9001->CRA 🟡 draft, rest ⚪. Highest-priority gap =
  ISO9001->MaschinenVO (the next Track-B work) — a far stronger product indicator than "EMV 30% modelled".
- Three knowledge layers documented: Regulatory -> Operational (transitions/playbooks/deltas, the
  biggest differentiator) -> Verification (Vision V2). A domain is a TRANSITION PROGRAM with two tracks:
  Track A breadth (model sources, @Legal-KG/@Execution) + Track B product (transitions/playbooks/RTS
  per source, @Reasoning).
- ADR-010: the transition is the unit of knowledge; Transition Coverage KPI; three layers; two tracks.

10 program/transition-contract tests, check-loc 0. Knowledge data + ADR + reference harness =
non-runtime -> no deploy (ADR-001). No new module, no runtime change.

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

backend-compliance/knowledge/programs/README.md

@@ -56,3 +56,38 @@ playbooks · passed reference scenarios · consciously declared corpus gaps. Ren
 
 The work shifts decisively from software development to knowledge production; the competitive
 advantage now comes from the quality and breadth of the modelled domains.
+
+## The unit of knowledge is the TRANSITION, not the law (Operational Knowledge)
+
+Customers never ask „what's in the CRA?". They ask **„I have ISO 9001 — what do I still need for the
+CRA?"**. The sellable unit is therefore the **transition** (`from → to`), not a single law and not a
+single capability. `knowledge/programs/transitions.yaml` is the **Operational Knowledge backlog**: the
+~20–30 transitions that are actually demanded (out of the ~N·(N−1) theoretically possible), with a
+priority. Nobody buys „EMV domain"; they buy „ISO 9001 → CRA".
+
+## Three knowledge layers
+
+```
+Regulatory Knowledge  (laws · standards · guidelines)
+        ↓
+Operational Knowledge (transition patterns · playbooks · capability deltas)  ← biggest differentiator
+        ↓
+Verification Knowledge (source code · SBOM · docs · architecture · processes)  ← Vision V2 / Req. Verification
+```
+
+The middle layer is where we answer not just *what* is required, but *how a company gets there from its
+current maturity*. That is the strongest moat.
+
+## Transition Coverage — a second, stronger KPI
+
+Besides per-domain maturity, the reference suite reports **Transition Coverage**: per top-transition a
+status DERIVED from the transition-pattern corpus (`reviewed/validated/proven → ✅`, `draft → 🟡`,
+`none → ⚪`). „ISO 9001 → MaschinenVO ⭐⭐⭐⭐⭐ but ⚪" is a far stronger product indicator than „EMV 30 %".
+
+## A domain is a TRANSITION PROGRAM with two parallel tracks
+
+- **Track A — breadth:** model the domain's remaining requirement sources (EMV, RED, IEC 62443, NIS2 …)
+  so the corpus grows. (Stage 2–3, @Legal-KG / @Execution.)
+- **Track B — product:** for each newly modelled source, immediately produce the top transition
+  patterns + playbooks + reference scenarios → knowledge customers buy and consultants use. (Stage 4–6,
+  @Reasoning.) Track B turns breadth into product value continuously.

backend-compliance/knowledge/programs/transitions.yaml

@@ -0,0 +1,22 @@
+# Operational Knowledge backlog — the TRANSITION is the unit of knowledge, not the law.
+# Customers buy „we have ISO 9001, help us with the CRA", not „EMV domain". This is the Operational
+# layer (the differentiator). Status per transition is DERIVED from the transition_patterns corpus by
+# the reference suite (reviewed/validated/proven -> Gold ✅, draft -> 🟡, none -> ⚪) — computed-not-stored.
+
+id: BACKLOG-transitions-v1
+note: >
+  Drei Wissensebenen: Regulatory (Gesetze/Normen/Leitlinien) → OPERATIONAL (diese Transitionen +
+  Playbooks + Capability-Deltas — der größte Differenzierer) → Verification (Code/SBOM/Doku/Architektur/
+  Prozesse, vgl. Vision V2). Diese Liste ist die Operational-Ebene und der eigentliche Verkaufs-Backlog.
+
+# Theoretisch entstehen aus N Requirement Sources ~N*(N-1) Übergänge; praktisch werden nur ~20-30
+# regelmäßig nachgefragt. Diese hier sind die meistnachgefragten (Priorität 1-5 Sterne).
+transitions:
+  - {from: ISO27001, to: CRA, priority: 5, domains: [industrial_automation]}
+  - {from: ISO9001, to: CRA, priority: 5, domains: [industrial_automation]}
+  - {from: ISO9001, to: MaschinenVO, priority: 5, domains: [industrial_automation]}
+  - {from: IEC62443, to: CRA, priority: 4, domains: [industrial_automation, energy]}
+  - {from: TISAX, to: CRA, priority: 4, domains: [automotive, industrial_automation]}
+  - {from: ISO27001, to: NIS2, priority: 4, domains: [industrial_automation, energy]}
+  - {from: IEC62443, to: NIS2, priority: 4, domains: [industrial_automation, energy]}
+  - {from: ISO14001, to: Umweltrecht, priority: 3, domains: [environmental]}