Lars
753f178b0c
Some checks failed
Deploy Development / deploy (push) Successful in 48s
Test Suite / pytest-backend (push) Failing after 3m23s
Test Suite / k6 /api/health Baseline (push) Has been skipped
Test Suite / playwright-smoke (push) Has been skipped
Test Suite / lint-backend (push) Successful in 3s
Test Suite / compose-smoke (push) Has been skipped
Decision-Lock, Spec-D-Methoden und C1-Massstab-Vollspecs als Zielbild; Steering-Registry/Compat und Horizon-Tests an die Normierung anbinden. Implementierungsausreichendheit bleibt bewusst offen. Co-authored-by: Cursor <cursoragent@cursor.com>
4.5 KiB
4.5 KiB
M2 — Methoden: Kompatibilität & Code-Schuld
Status: erledigt (Dokumentation) — 2026-07-25
Voraussetzung: Kairo_Steering_Method_Kernel_v0.1.md
Spec-D: docs/architecture/methods/SPEC_D_*.md
Nächste Phase: Archetyp-Vollspecs
1. Dominanz (Kernel §3 / §8)
| Methode | Dominanz | Rolle |
|---|---|---|
sequential_dependency |
plan | primary |
program_delivery |
plan (+ Kind-Signale) | primary |
continuous_product |
plan (hybrid-light) | primary |
checklist_flow |
plan (dünn) | primary |
maturity_progression |
hybrid | primary |
recurring_control |
event (Cadence) | primary |
care_navigation |
hybrid | primary |
dispute_procedure |
event | primary |
agile_iteration |
plan-Slice | Komposition |
generic_operating |
plan (dünn) | primary Fallback |
queue_pull |
— | Legacy → ablösen durch checklist_flow |
chapter_based_progression |
— | Legacy → Content = A2 + Profil, keine eigene Methode nötig |
product_milestone_driven |
— | Legacy → migrieren zu program/product |
2. Kompatibilitätsmatrix Ziel (Archetyp × Methode)
| Archetyp | Default-Methode | Auch erlaubt | Komposition |
|---|---|---|---|
linear_project (A2) |
sequential_dependency |
— | agile_iteration |
program (B2a) |
program_delivery |
Kind-Methoden an Kindern | Agile nur an Kindern A2/B2b |
product (B2b) |
continuous_product |
— | agile_iteration |
maturity_journey (A1) |
maturity_progression |
— | — |
recurring_program (A3) |
recurring_control |
— | agile_iteration |
checklists (B1) |
checklist_flow |
— | — |
care (NEU) |
care_navigation |
— | — |
dispute_case (C1) |
dispute_procedure |
— | — |
generic |
generic_operating |
Übergang zu konkreter Methode | — |
content_project |
entfernt als Archetyp | Content → A2 | — |
Kind unter B2a: jeder Kind-Archetyp mit seiner Default-Methode (Hybrid Decision-Lock).
3. Ist-Code vs. Ziel
| Methode | Ist compatible_archetype_keys |
Ziel | Gap |
|---|---|---|---|
sequential_dependency |
* |
linear_project (+ Kind A2) |
zu weit |
program_delivery |
program |
program |
Strategy ≠ Nested/Impulse |
continuous_product |
product-like | product |
prüfen |
queue_pull |
* |
ersetzen durch checklist_flow + Checklisten-Archetyp |
Rename/neu |
agile_iteration |
*, composes_with product+program |
composes_with product + sequential + recurring (nicht Programm-Meta) | composes_with unvollständig |
care_navigation |
fehlt | care |
neu |
checklist_flow |
fehlt | checklists | neu |
chapter_based_* |
content_project |
deprecated | entfernen/umwidmen |
maturity / recurring / dispute |
ok eng | ok | Strategie-Tiefe |
4. Code-Schuld (Implementierung später — priorisiert)
| Prio | Schuld | Bezug |
|---|---|---|
| P0 | program_delivery: Impulse + Nested; Child-NA getrennt |
SPEC_D_program_delivery |
| P0 | Registry: care_navigation + Archetyp initiative.care |
Decision-Lock |
| P0 | checklist_flow + Archetyp initiative.checklists; Nested Tiefe 3 + Roll-up; Multi-Listen |
SPEC_B1_checklists / Spec-D |
| P1 | sequential_dependency compat auf A2 einschränken |
Matrix §2 |
| P1 | agile_iteration.composes_with → continuous_product, sequential_dependency, recurring_control |
Spec Agile |
| P1 | Dual-Auslöser Event-Pfad in Strategies (C1/Care) | Kernel §3 |
| P2 | Legacy chapter_based_progression / content_project Seed |
Decision-Lock |
| P2 | Spec-D Dominanz-Feld redaktionell in alle Dateien | Kernel §8 |
| P3 | Stubs → volle Strategien (recurring, dispute, …) | Spec-D |
Kein Code in M2 — nur Verbindlichkeit für spätere APs.
5. Implementierungsreife Methoden (ehrlich)
| Reife | Methoden |
|---|---|
| Fachlich bau-bar (Verhalten klar, Code teils da) | sequential_dependency, continuous_product, agile_iteration (Komposition), maturity_progression |
| Fachlich klar, Code weit weg | program_delivery (Umbau), checklist_flow, care_navigation |
| Spec-D gehärtet, Code teils Stub | recurring_control, dispute_procedure, maturity_progression, continuous_product, generic_operating |
Assignment-DoD für Code-APs: Kernel-Schlitze + Spec-D + diese Matrix — keine Page-Ifs.
6. Freigabe
- Matrix Ziel §2
- Code-Schuld §4
- Weiter mit Archetyp-Vollspecs