118 lines
4.6 KiB
Markdown
118 lines
4.6 KiB
Markdown
|
# Jinkendo Kairo
|
|||
|
|
## Steuerungsmethoden — Fachlicher Kern & Contract v0.1 (M1 reframed)
|
|||
|
|
|
|||
|
|
**Status:** Entwurf — Phase M1 **umgebogen** (Kern zuerst, nicht Spec-Formular)
|
|||
|
|
**Stand:** 2026-07-25
|
|||
|
|
**Programm:** `Kairo_Steering_Method_Normalization_Program_v0.1.md`
|
|||
|
|
**Nordstern:** `Kairo_Target_Architecture_Method_Driven_Adaptive_Steering_Core_v0.1.md`
|
|||
|
|
**Prinzipien:** `Kairo_Method_Design_Principles_v0.1.md`
|
|||
|
|
**Technik:** `ADP_AP2_4_Steering_Elements_and_Method_Contract_v0.1.md`
|
|||
|
|
**Archetypen:** `Kairo_Archetype_Decision_Lock_Interview_2026-07-25.md`
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## 0. Kurskorrektur
|
|||
|
|
|
|||
|
|
**Verworfen als Einstieg:** 10 Spec-Felder + Primitive-Stichliste (zu früh, MVP-verkürzt).
|
|||
|
|
|
|||
|
|
**Neuer M1-Pfad:**
|
|||
|
|
|
|||
|
|
```text
|
|||
|
|
1) Methodenkern (invariant) — Steuerungszyklus, Lifecycle, Core vs Methode
|
|||
|
|
2) Extension Points — Hooks, Strategies, Builder, Policies
|
|||
|
|
3) Gemeinsame Primitive / Read Models
|
|||
|
|
4) Methoden-Deltas (Besonderheiten)
|
|||
|
|
5) Archetyp × Methode
|
|||
|
|
6) Spec-Template (abgeleitet)
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
Spec-Tiefe = holistisch. Implementierungstiefe später MVP.
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## 1. Methodenkern — Arbeitsstand
|
|||
|
|
|
|||
|
|
### 1.1 Leitfrage (unverändert)
|
|||
|
|
|
|||
|
|
> Welcher nächste Schritt bringt ein Vorhaben aktuell am wirkungsvollsten voran — und warum?
|
|||
|
|
|
|||
|
|
### 1.2 Steuerungszyklus (Kandidat — aus Target Architecture)
|
|||
|
|
|
|||
|
|
```text
|
|||
|
|
intake → method_selection → structure_setup → planning → action_selection
|
|||
|
|
→ assignment → waiting → result_intake → validation → review
|
|||
|
|
→ adaptation → closure
|
|||
|
|
```
|
|||
|
|
|
|||
|
|
| Schritt | Core (invariant) | Methode (Extension) |
|
|||
|
|
|---------|------------------|---------------------|
|
|||
|
|
| intake | SteeringContext, Ziel/Scope | zusätzliche Hooks |
|
|||
|
|
| method_selection | Registry, Kompatibilität zu Archetyp | Domain-Filter, Default |
|
|||
|
|
| structure_setup | Hook-Dispatch, Builder-Interface | welche Structure Builder |
|
|||
|
|
| planning | Transition, Audit | DoD/Plan-Dichte-Policy |
|
|||
|
|
| action_selection | Signal-/NextAction-Orchestrierung | Next-Action-Strategy |
|
|||
|
|
| assignment | Actor-Validierung, Assignment-Service | Assignment-Strategy |
|
|||
|
|
| waiting | Wartezustand (Runtime später) | Waiting/Reminder/Escalation |
|
|||
|
|
| result_intake | Ergebnis entgegennehmen | Intake-Strategy |
|
|||
|
|
| validation | Evidence/DoD-Checks anstoßen | Evidence-Policy |
|
|||
|
|
| review | Review-Objekt | Review-Strategy |
|
|||
|
|
| adaptation | Replan-Hooks | Structure-/Method-Adjustment |
|
|||
|
|
| closure | Closure-Policy aufrufen | ob/wann Closure sinnvoll |
|
|||
|
|
|
|||
|
|
**Regel (Kandidat):** Methode darf Schritte **auslassen/spezialisieren**, nicht Tenant/Actor/Capability/OM-Kern umgehen.
|
|||
|
|
|
|||
|
|
**Analyse:** `M1_Lifecycle_Fit_Analysis_Archetypes_v0.1.md` — Lifecycle allein **nicht hinreichend**; siehe §5 dort (Kern-Anker A–G).
|
|||
|
|
|
|||
|
|
*(PO-Bestätigung: Interview M1.1 — reframed nach Analyse)*
|
|||
|
|
|
|||
|
|
### 1.3 Core vs. Methode vs. Archetyp (Kandidat)
|
|||
|
|
|
|||
|
|
| | Core | Methode | Archetyp |
|
|||
|
|
|--|------|---------|----------|
|
|||
|
|
| Rolle | Orchestrierung, Invarianten, Registries | Steuerungsverhalten | Natur/Horizont/UI-Hülle/OM-Fähigkeiten |
|
|||
|
|
| Persistenz | OM + SteeringContext | nutzt OM, keine Parallelwelt | `archetype_key`, ui_profile, om_capabilities |
|
|||
|
|
| UI Verhalten Work/Control | Element-Registry auflösen | `steering_elements`, `ui_features` | Nav/Routen/Outline |
|
|||
|
|
| Next Action | Engine ruft Strategy | liefert Strategy | begrenzt über om_capabilities |
|
|||
|
|
|
|||
|
|
### 1.4 Extension Points (Kandidat — Pflicht vs. optional)
|
|||
|
|
|
|||
|
|
| Extension | Pflicht primary? | Bemerkung |
|
|||
|
|
|-----------|------------------|-----------|
|
|||
|
|
| `next_action_strategy` | **ja** | Kern der Leitfrage |
|
|||
|
|
| `attention` / signal rules | **ja** (min. leer explizit) | Portfolio + Vorhaben |
|
|||
|
|
| `compatible_archetype_keys` + `data_slices` | **ja** | AP2.4 |
|
|||
|
|
| `steering_elements` | **ja** (min. `next_action_primary`) | AP2.4 |
|
|||
|
|
| `lifecycle_steps` aktiv/skip | **ja** | welche Schritte gelten |
|
|||
|
|
| Structure Builder | empfohlen | sonst manuelle Struktur |
|
|||
|
|
| assignment / waiting / reminder / escalation | optional | Default-Core |
|
|||
|
|
| evidence / review / closure policy | optional bis nötig | |
|
|||
|
|
| Hook-Bindings über Standard-Slugs | empfohlen | stabil versioniert |
|
|||
|
|
| `agile_iteration` als modifier | nur Komposition | kein primary Ersatz |
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## 2. Primitive — später (nach Kern)
|
|||
|
|
|
|||
|
|
Arbeitsliste unverändert als Kandidaten; Definition **nach** M1.1–M1.3.
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## 3. Spec-Formular (10 Punkte) — später
|
|||
|
|
|
|||
|
|
Wird **abgeleitet** aus Kern + Extensions — nicht Einstieg.
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
## 4. Interview-Log
|
|||
|
|
|
|||
|
|
| ID | Thema | Entscheidung |
|
|||
|
|
|----|-------|--------------|
|
|||
|
|
| — | Kurskorrektur Kern zuerst | ✓ A (2026-07-25) |
|
|||
|
|
| — | Lifecycle allein hinreichend? | ✗ Analyse — Anker nötig |
|
|||
|
|
| M1-Pfad | Hybrid A1 | ✓ (2026-07-25): Kandidat-Kern → Tiefe D → Freeze |
|
|||
|
|
| Prozess | | `M1_Hybrid_Path_and_Depth_D_v0.1.md` |
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
*Living document.*
|