AP1.5c: Rekursive Projects fuer Mega-Programme ohne Stream-Typ.
Deploy Development / deploy (push) Successful in 53s
Test Suite / pytest-backend (push) Successful in 1m42s
Test Suite / lint-backend (push) Successful in 2s
Test Suite / compose-smoke (push) Has been skipped
Test Suite / k6 /api/health Baseline (push) Successful in 21s
Test Suite / playwright-smoke (push) Successful in 14s
Deploy Development / deploy (push) Successful in 53s
Test Suite / pytest-backend (push) Successful in 1m42s
Test Suite / lint-backend (push) Successful in 2s
Test Suite / compose-smoke (push) Has been skipped
Test Suite / k6 /api/health Baseline (push) Successful in 21s
Test Suite / playwright-smoke (push) Successful in 14s
parent_project_id und container_kind ermoeglichen verschachtelte Projektstruktur; Arbeitspakete bleiben an Blatt-Projekten gebunden. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
1 parent
6eeddfdc76
commit
4ca0a2c460
15 files changed
+947
-91
No files matched your search
@@ -82,10 +82,12 @@ Minimaler Fix erlaubt: Tab-Beschreibung / Breadcrumb „Gates“ statt implizit
|
||||
|
||||
```text
|
||||
✓ AP1.4b Gate-Checkliste Backend + Minimal-Detail-Route
|
||||
→ AP1.5 Project, Task, Ausführung als Ist-Kern (NÄCHSTES CODE-PAKET)
|
||||
→ AP1.5 Project, Task, Ausführung als Ist-Kern ✓
|
||||
→ AP1.5c Rekursive Projects (parent_project_id)
|
||||
→ AP1.5b IA/Begriffe: Gates vs. Ausführung, optionale Gate-Sicht
|
||||
→ AP1.6 Plan/Ist-Verknüpfung, Journey (Action/Backlog → Gate)
|
||||
⏸ AP1.4c Gate-UI (Modal, Checkliste-UX) — nach AP1.5
|
||||
→ AP1.6 Plan/Ist-Verknüpfung, Journey (Action/Backlog/Project → Gate)
|
||||
→ AP1.5d Rekursive Tasks (parent_task_id), Roll-up
|
||||
⏸ AP1.4c Gate-UI (Modal, Checkliste-UX) — nach AP1.6
|
||||
→ AP1.4d Graph Engine (Gate-Kanten only)
|
||||
→ AP1.4e Methodenprofile (generic_operating ohne Gate-Zwang)
|
||||
```
|
||||
@@ -101,9 +103,9 @@ Initiative (Vorhaben / Programm)
|
||||
│ ▲
|
||||
│ │ zahlt ein (Evidence, Zuordnung)
|
||||
│ │
|
||||
├── [optional] Project ← AP1.5
|
||||
├── [optional] Project* ← AP1.5c parent_project_id
|
||||
│ └── Action (Arbeitspaket) ← Ist — „Plan zwischen Gates“
|
||||
│ └── Task ← AP1.5 minimal
|
||||
│ └── Task* ← AP1.5d parent_task_id
|
||||
│
|
||||
├── Backlog → Commit → Action
|
||||
└── steering_context (Lifecycle, method_key) ← getrennt von Gate-Graph
|
||||
@@ -155,4 +157,4 @@ Initiative (Vorhaben / Programm)
|
||||
|
||||
---
|
||||
|
||||
*Referenz: `Kairo_Corrected_MVP_Roadmap_v0.2.md` (PO-Korrektur 2026-07-06), `Sprint1_AP1_5_Hierarchy_Assignment_v0.1.md`*
|
||||
*Referenz: `Kairo_Corrected_MVP_Roadmap_v0.2.md` (PO-Korrektur 2026-07-06), `ADP_Recursive_Containers_and_Execution_Granularity_v0.1.md`, `Sprint1_AP1_5_Hierarchy_Assignment_v0.1.md`*
|
||||
@@ -0,0 +1,198 @@
|
||||
# ADP — Rekursive Container & Ausführungs-Granularität v0.1
|
||||
|
||||
**Status:** PO-Freigabe (2026-07-06)
|
||||
**Stand:** 2026-07-06
|
||||
**Auslöser:** PO-Review — Mega-Programme vs. normale Vorhaben; Granularität für Mensch vs. Agent
|
||||
**Bezug:** `ADP_PO_Product_Layering_and_IA_Reset_v0.1.md`, Canonical OM v0.2, Target State §10–11
|
||||
|
||||
---
|
||||
|
||||
## Problem
|
||||
|
||||
Zwei verwandte Fragen ohne feste Extra-Typen (`Stream`, `Subtask`, …):
|
||||
|
||||
1. **Organisation:** Sehr große Programme brauchen optional **Project in Project**; normale Vorhaben nicht.
|
||||
2. **Ausführung:** Arbeitspakete und Aufgaben brauchen **methoden- und akteursabhängige Tiefe** — Menschen ~2–3 Untergliederungen, Agenten feiner.
|
||||
|
||||
Fest codierte Ebenen (`Stream`, `WorkPackage`, `Subtask` als eigene Typen) wären für kleine Vorhaben überdimensioniert und duplizieren semantisch **Project** bzw. **Task**.
|
||||
|
||||
---
|
||||
|
||||
## Betroffene Regeln
|
||||
|
||||
| Dokument | Regel |
|
||||
|----------|--------|
|
||||
| Canonical OM v0.2 §4 | Project optional; Action = Arbeitspaket; Task methodenabhängig |
|
||||
| Vision v0.2 §4 | Action ≠ atomare Aufgabe; Task-Hierarchie / WBS |
|
||||
| ADP Product Layering | Ist = Project → Action → Task; Gates orthogonal |
|
||||
| Target State §10–11 | Steuerbare Objekte inkl. `project`; `SteeringContext` mit `scope_type` |
|
||||
| Tenant Invariants | Kein paralleles Steering; Actor-first Assignments |
|
||||
|
||||
---
|
||||
|
||||
## Optionen (Struktur)
|
||||
|
||||
| Option | Kurz | Pro | Contra |
|
||||
|--------|------|-----|--------|
|
||||
| A | Feste Typen `Stream`, `Subtask` | Klare UI-Labels | Schema-Ballast; Doppelung zu Project/Task |
|
||||
| B | **Rekursion gleicher Typen** (`parent_*_id`) | Ein Modell für klein + groß | Baum-UI; Roll-up-Regeln nötig |
|
||||
| C | Unbegrenzte Rekursion + Steuerung pro Ebene | Maximale Flexibilität | Steuerungs-Explosion; MVP-Verzögerung |
|
||||
|
||||
---
|
||||
|
||||
## Entscheidung (PO-Freigabe 2026-07-06)
|
||||
|
||||
### 1. Organisations-Ebene: rekursives **Project**
|
||||
|
||||
- **`parent_project_id`** nullable auf `projects` (Adjacency List).
|
||||
- Gleiche Initiative; **Zyklen verboten**; **max. Tiefe 5** (hard block).
|
||||
- Optional **`container_kind`** (Registry/Label): `project`, `stream`, `phase`, `release` — **nur Anzeige/Methoden-Hint**, keine Sonderlogik pro Kind.
|
||||
- **Kein** eigener Typ `Stream`.
|
||||
|
||||
**Semantik nach Tiefe (UI, nicht Schema):**
|
||||
|
||||
| Tiefe | Typisches Label | Beispiel |
|
||||
|-------|-----------------|----------|
|
||||
| 0 | Projekt | „Kairo MVP“ |
|
||||
| 1 | Stream / Phase | „Backend“, „Kumite“ |
|
||||
| 2+ | Teilprojekt | „API-Schicht“ |
|
||||
|
||||
**Guardrails:**
|
||||
|
||||
- Actions bevorzugt an **Blatt-Projects** oder direkt an Initiative (Warnung bei Container mit Kindern).
|
||||
- Gates (`roadmap_item_id`) an jeder Project-Tiefe oder Initiative — Plan/Ist in AP1.6.
|
||||
|
||||
**Implementierung:** **AP1.5c** — Migration `014` o.ä.
|
||||
|
||||
---
|
||||
|
||||
### 2. Ausführungs-Ebene: rekursives **Task** (Haupthebel Granularität)
|
||||
|
||||
- **`parent_task_id`** nullable auf `tasks` — gleiche Tabelle, Zeiger auf weitere Instanz.
|
||||
- **Max. Tiefe Schema:** 10 (Agent/API).
|
||||
- **Max. Tiefe UI (Menschen):** 3 Ebenen (Task → Subtask → Sub-Subtask) — **Policy**, kein Schema-Limit.
|
||||
- Roll-up: Action `done` wenn Task-Baum erfüllt (Regeln in AP1.5d); Task `done` wenn alle Kinder `done` oder explizit ohne Kinder.
|
||||
|
||||
**Guardrails:**
|
||||
|
||||
- **Steuerung bleibt auf Action** (Assignment, Blocker, Evidence, Next Action für Menschen).
|
||||
- Kein `steering_context` pro Task-Ebene.
|
||||
- Agenten: Blatt-Tasks als Ausführungsschritte; tiefe Bäume in UI **aggregiert** anzeigen.
|
||||
|
||||
**Implementierung:** **AP1.5d** — **nach AP1.6** (Plan/Ist-Verknüpfung + Gate-Beitrag zuerst).
|
||||
|
||||
---
|
||||
|
||||
### 3. Action-Verschachtelung: **eingeschränkt**, nicht Default
|
||||
|
||||
- **`parent_action_id`** nur für **`wbs_driven`** (später), max. Tiefe **2**.
|
||||
- Nur **Root-Action** aus Backlog-Commit; Kind-Actions = strukturelle Teilpakete desselben Commits.
|
||||
- Default-Vorhaben: **eine Action + Task-Baum** — kein Action-Baum.
|
||||
|
||||
**Implementierung:** dokumentiert; Code **nicht** in AP1.5c/d — erst mit Methodenprofil / Structure Builder.
|
||||
|
||||
---
|
||||
|
||||
### 4. Steuerung: Vererbung, nicht Explosion
|
||||
|
||||
**Stufe 1 (MVP bis AP1.6+):**
|
||||
|
||||
```text
|
||||
Initiative = einziger Steering-Root (steering_context, heute implementiert)
|
||||
Project* = Struktur; erbt Initiative-Steuerung
|
||||
Action = operative Steuerungs-Anker für Menschen (Assignment, Blocker, Evidence)
|
||||
Task* = Ausführungsschritte; Roll-up, kein eigener Context
|
||||
```
|
||||
|
||||
**Stufe 2 (später, Mega-Programme):**
|
||||
|
||||
- Polymorpher `SteeringContext` (`scope_type`, `scope_id`) wie Target State.
|
||||
- Nur Projects mit `steering_root = true` oder explizitem Override — **nicht** jede Ebene.
|
||||
|
||||
---
|
||||
|
||||
## Schichtenmodell (Ziel)
|
||||
|
||||
```text
|
||||
Initiative ── steering_context (Pflicht)
|
||||
│
|
||||
├── [optional] Project* parent_project_id
|
||||
│ └── Project* …
|
||||
│ └── Action Commit-Grenze (Root aus Backlog)
|
||||
│ └── Task* parent_task_id
|
||||
│ └── Task* …
|
||||
│
|
||||
├── [optional] Gates (RoadmapItem) orthogonal
|
||||
└── Backlog → Commit → Action (Root)
|
||||
```
|
||||
|
||||
**Zwei orthogonale Dimensionen:**
|
||||
|
||||
| Dimension | Rekursion | Mensch-Tiefe | Agent-Tiefe |
|
||||
|-----------|-----------|--------------|-------------|
|
||||
| Project (Organisation) | ja | 0–2 typisch | — |
|
||||
| Action (Arbeitspaket) | selten (WBS) | 1 | 1–2 |
|
||||
| Task (Ausführung) | ja | 2–3 | bis 10 |
|
||||
|
||||
---
|
||||
|
||||
## Repriorisierung (verbindlich)
|
||||
|
||||
```text
|
||||
✓ AP1.5 Project, Task flach, Ausführung (0.14.0-ap1.5)
|
||||
→ AP1.5c parent_project_id, Baum-UI, container_kind optional
|
||||
→ AP1.6 Plan/Ist-Verknüpfung, Journey
|
||||
→ AP1.5d parent_task_id, Roll-up, UI-Tiefen-Policy
|
||||
⏸ AP1.4c Gate-UI — weiter eingefroren
|
||||
→ AP1.4d Gate-Graph
|
||||
→ AP1.7 Operational Actor Interface (unverändert)
|
||||
```
|
||||
|
||||
AP1.5b (IA-Begriffe) kann parallel zu AP1.5c.
|
||||
|
||||
---
|
||||
|
||||
## Konsequenzen
|
||||
|
||||
| Bereich | Konsequenz |
|
||||
|---------|------------|
|
||||
| Schema | Zwei Migrationen: Project-Baum, Task-Baum — getrennte APs |
|
||||
| UI | Baum/Outline statt nur flache Listen; Default collapsed ab Tiefe 2 |
|
||||
| API | Cycle-Detection; depth validation |
|
||||
| Tests | Klein (flach), Mega (Project-Tiefe 3), Agent (Task-Tiefe >3) |
|
||||
| Steering | Keine Änderung in AP1.5c/d außer Roll-up-Fortschritt |
|
||||
| Agent AP1.7 | Nutzt Task-Blätter; tiefe Zerlegung über AP1.5d |
|
||||
|
||||
---
|
||||
|
||||
## Risiko
|
||||
|
||||
| Risiko | Mitigation |
|
||||
|--------|------------|
|
||||
| UI-Overload durch Tiefe | UI soft cap 3 Tasks; Mega-Projects collapsed |
|
||||
| Redundante Pfade (Project + Action + Task alle tief) | Guardrails + PO-Dokumentation |
|
||||
| Commit-Modell bei nested Actions | Nested Actions erst WBS-Profil; Default flach |
|
||||
| Steuerungs-Explosion | Stufe 1: nur Initiative-Context |
|
||||
|
||||
---
|
||||
|
||||
## Rückbaubarkeit
|
||||
|
||||
- `parent_*_id` nullable — flache Nutzung bleibt Default.
|
||||
- `container_kind` optional — entfernbar ohne Schema-Bruch.
|
||||
- Polymorpher SteeringContext ist **Add-on**, kein Breaking Change für AP1.5c/d.
|
||||
|
||||
---
|
||||
|
||||
## Abnahme PO
|
||||
|
||||
- [x] Rekursives Project statt Stream-Typ
|
||||
- [x] Rekursives Task für Granularität (Mensch 2–3, Agent tiefer)
|
||||
- [x] Steering-Root = Initiative (Stufe 1)
|
||||
- [x] AP1.5c → AP1.6 → AP1.5d Reihenfolge
|
||||
- [x] Implementierung AP1.5c
|
||||
- [ ] Implementierung AP1.5d
|
||||
|
||||
---
|
||||
|
||||
*Referenz: `Kairo_Corrected_MVP_Roadmap_v0.2.md` (Update 2026-07-06), `ADP_PO_Product_Layering_and_IA_Reset_v0.1.md`*
|
||||
@@ -6,7 +6,8 @@
|
||||
**Ersetzt:** `Kairo_Corrected_MVP_Roadmap_v0.1.md`
|
||||
**Vision:** `Kairo_Vision_and_Product_Direction_v0.2.md`
|
||||
**Ist-Stand:** `Kairo_Implementation_Truth_Table_v0.1.md`
|
||||
**PO-ADP:** `ADP_PO_Product_Layering_and_IA_Reset_v0.1.md`
|
||||
**PO-ADP:** `ADP_PO_Product_Layering_and_IA_Reset_v0.1.md`
|
||||
**Container-ADP:** `ADP_Recursive_Containers_and_Execution_Granularity_v0.1.md`
|
||||
|
||||
---
|
||||
|
||||
@@ -28,8 +29,8 @@
|
||||
| Entscheidung | |
|
||||
|--------------|--|
|
||||
| AP1.4b Backend | ✓ behalten (Kriterien, Verify, Reopen) |
|
||||
| Gate-UI-Politur (Modal, Graph-Workflow) | ⏸ **eingefroren** bis AP1.5 |
|
||||
| Nächstes Code-Paket | **AP1.5** Hierarchie + Ausführung als Ist-Kern |
|
||||
| Gate-UI-Politur (Modal, Graph-Workflow) | ⏸ **eingefroren** bis AP1.6 |
|
||||
| Nächstes Code-Paket | **AP1.5c** rekursive Projects |
|
||||
| Tab „Plan“ | fachlich **Gates / Zielzustände** — Umbenennung AP1.5b |
|
||||
| Graph Engine AP1.4d | Gate-Kanten only — **kein** Lifecycle-Workflow |
|
||||
|
||||
@@ -37,6 +38,24 @@ Siehe `ADP_PO_Product_Layering_and_IA_Reset_v0.1.md`.
|
||||
|
||||
---
|
||||
|
||||
## 1.2 PO-Entscheidung 2026-07-06 — Rekursive Container & Task-Tiefe
|
||||
|
||||
**Auslöser:** Mega-Programme vs. normale Vorhaben; Granularität Mensch vs. Agent.
|
||||
|
||||
| Entscheidung | |
|
||||
|--------------|--|
|
||||
| Stream als eigener Typ | **Nein** — `Project` mit `parent_project_id` + optionalem `container_kind` |
|
||||
| Project in Project | **Ja** — AP1.5c |
|
||||
| Task → Subtask → … | **Ja** — `parent_task_id`; UI max. ~3 Ebenen; Schema tiefer für Agenten — AP1.5d |
|
||||
| Nested Actions | **Optional** später (`wbs_driven` only); nicht Default |
|
||||
| Steuerung pro Ebene | **Nein (Stufe 1)** — Initiative-Root; Action = Anker für Menschen |
|
||||
|
||||
Siehe `ADP_Recursive_Containers_and_Execution_Granularity_v0.1.md`.
|
||||
|
||||
**Reihenfolge:** AP1.5c → AP1.6 → AP1.5d
|
||||
|
||||
---
|
||||
|
||||
## 2. Phasenübersicht
|
||||
|
||||
```text
|
||||
@@ -47,11 +66,12 @@ Phase C Dokumentation Welle 1–2 ✓
|
||||
Phase D IA-Skeleton AP1.2 + AP1.2c ✓
|
||||
Phase E Steering AP1.2, AP1.3 ◐
|
||||
Phase F Gate-Backend AP1.4 + AP1.4b ✓ (Backend); UI minimal
|
||||
Phase G **Ist-Hierarchie AP1.5** ← **NÄCHSTES CODE**
|
||||
Phase H Plan/Ist-Verknüpfung AP1.6 geplant
|
||||
Phase I Gate-Graph AP1.4d–4e nach AP1.5
|
||||
Phase G Ist-Hierarchie AP1.5 ✓
|
||||
Phase G2 Rekursive Container AP1.5c–5d ✓ 5c / → 5d nach AP1.6
|
||||
Phase H Plan/Ist-Verknüpfung AP1.6 ← **NÄCHSTES CODE**
|
||||
Phase I Gate-Graph AP1.4d–4e nach AP1.6
|
||||
Phase J Portfolio & Kontext AP1.8 geplant
|
||||
Phase K Agent Interface AP1.7 geplant
|
||||
Phase K Agent Interface AP1.7 geplant (unverändert)
|
||||
Phase L Validation AP0.10d (laufend PO) parallel
|
||||
```
|
||||
|
||||
@@ -71,13 +91,15 @@ Phase L Validation AP0.10d (laufend PO) parallel
|
||||
| AP1.2c | 0.12.0-ap1.2c | IA-Skeleton |
|
||||
| AP1.4 | 0.13.0-ap1.4 | RoadmapItem / Gates Minimal |
|
||||
| AP1.4b | 0.13.1-ap1.4b | Gate-Checkliste Backend + Detail-Route |
|
||||
| AP1.5 | 0.14.0-ap1.5 | Project, Task flach, Ausführung-Tab |
|
||||
| DOC PO | 2026-07-06 | ADP Product Layering & IA-Reset |
|
||||
| DOC Container | 2026-07-06 | ADP Recursive Containers & Execution Granularity |
|
||||
|
||||
---
|
||||
|
||||
## 4. Nächste Pakete (verbindliche Reihenfolge — PO 2026-07-06)
|
||||
|
||||
### AP1.5 — Hierarchie & Ist-Ebene (**NÄCHSTES CODE-PAKET**)
|
||||
### AP1.5 — Hierarchie & Ist-Ebene ✓
|
||||
|
||||
**Ziel:** Operativer Plan zwischen Gates — Project, Task, Ausführung-Tab; Gates optional nutzbar.
|
||||
|
||||
@@ -94,6 +116,22 @@ Phase L Validation AP0.10d (laufend PO) parallel
|
||||
|
||||
---
|
||||
|
||||
### AP1.5c — Rekursive Projects ✓
|
||||
|
||||
**Ziel:** Project-Baum für Mega-Programme; normale Vorhaben unverändert flach.
|
||||
|
||||
| Scope | |
|
||||
|-------|--|
|
||||
| `parent_project_id`, Zyklen-Check, max. Tiefe 5 |
|
||||
| Optional `container_kind` (Label) |
|
||||
| Baum-UI in Ausführung; Actions nur an Blatt-Projects |
|
||||
| **Kein** eigener Steering-Context pro Project |
|
||||
|
||||
**ADP:** `ADP_Recursive_Containers_and_Execution_Granularity_v0.1.md`
|
||||
**Version:** `0.14.1-ap1.5c`
|
||||
|
||||
---
|
||||
|
||||
### AP1.5b — IA-Begriffe Gates vs. Ausführung
|
||||
|
||||
| Scope | |
|
||||
@@ -106,17 +144,35 @@ Phase L Validation AP0.10d (laufend PO) parallel
|
||||
|
||||
---
|
||||
|
||||
### AP1.6 — Plan/Ist-Verknüpfung & Journey
|
||||
### AP1.6 — Plan/Ist-Verknüpfung & Journey (**NÄCHSTES CODE-PAKET**)
|
||||
|
||||
Backlog/Action → RoadmapItem; Decision-Spur; Journey-Timeline.
|
||||
Backlog/Action/Project/Task → RoadmapItem; Decision-Spur; Journey-Timeline.
|
||||
|
||||
**Nach AP1.5** — Gates bekommen Bedeutung durch Ist-Bezug.
|
||||
**Nach AP1.5c** — Gates bekommen Bedeutung durch Ist-Bezug (auch auf Project-Ebenen).
|
||||
|
||||
**Version:** `0.15.0-ap1.6`
|
||||
|
||||
---
|
||||
|
||||
### AP1.4c — Gate-UI-Politur ⏸ (eingefroren bis AP1.5)
|
||||
### AP1.5d — Rekursive Tasks & Roll-up
|
||||
|
||||
**Ziel:** Task-Baum (`parent_task_id`); Mensch UI max. ~3 Ebenen; Agent tiefer.
|
||||
|
||||
| Scope | |
|
||||
|-------|--|
|
||||
| Migration `parent_task_id`, Cycle/Depth-Validation |
|
||||
| Roll-up Status Action ↔ Task-Baum |
|
||||
| Gate-Beitrag auf Blatt-Tasks (Fortsetzung AP1.6) |
|
||||
| UI: Outline, collapsed default ab Tiefe 2 |
|
||||
| **Kein** nested Action (Default) |
|
||||
|
||||
**ADP:** `ADP_Recursive_Containers_and_Execution_Granularity_v0.1.md`
|
||||
**Nach AP1.6**
|
||||
**Version:** `0.15.1-ap1.5d`
|
||||
|
||||
---
|
||||
|
||||
### AP1.4c — Gate-UI-Politur ⏸ (eingefroren bis AP1.6)
|
||||
|
||||
Modal Gate anlegen/bearbeiten; Checkliste-UX; Fortschritt in Liste.
|
||||
|
||||
@@ -134,7 +190,7 @@ Modal Gate anlegen/bearbeiten; Checkliste-UX; Fortschritt in Liste.
|
||||
| Deprecate `sequencing_mode` am Item |
|
||||
| Read Models: blocked, ready, fulfillment_ratio |
|
||||
|
||||
**Version:** `0.14.1-ap1.4d` (nach AP1.5)
|
||||
**Version:** `0.15.2-ap1.4d` (nach AP1.6)
|
||||
|
||||
---
|
||||
|
||||
@@ -204,7 +260,7 @@ Criteria, Waive/Defer, Reopen, Detail-Route. Version `0.13.1-ap1.4b`
|
||||
|
||||
| Thema | Bis wann |
|
||||
|-------|----------|
|
||||
| Gate-UI-Politur (Modal, Graph-Workflow) | **Nach AP1.5** (PO 2026-07-06) |
|
||||
| Gate-UI-Politur (Modal, Graph-Workflow) | **Nach AP1.6** (PO 2026-07-06) |
|
||||
| Prompt/KI/MCP produktiv | Ist-Hierarchie + Plan/Ist |
|
||||
| Method Designer UI | AP1.3+ |
|
||||
| Gantt / Kalender | nach Plan/Ist |
|
||||
@@ -230,12 +286,14 @@ MVP-nah wenn:
|
||||
0.12.0-ap1.2c ✓ IA-Skeleton
|
||||
0.13.0-ap1.4 ✓ RoadmapItem / Gates Backend
|
||||
0.13.1-ap1.4b ✓ Gate-Checkliste Backend
|
||||
0.14.0-ap1.5 → Hierarchie (Project, Task) — NÄCHSTES
|
||||
0.15.0-ap1.6 → Journey / Plan-Ist
|
||||
0.14.1-ap1.4d → Gate-Graph (nach AP1.5)
|
||||
0.14.0-ap1.5 ✓ Hierarchie (Project, Task flach)
|
||||
0.14.1-ap1.5c ✓ Rekursive Projects
|
||||
0.15.0-ap1.6 → Journey / Plan-Ist — NÄCHSTES
|
||||
0.15.1-ap1.5d → Rekursive Tasks / Roll-up
|
||||
0.15.2-ap1.4d → Gate-Graph
|
||||
0.16.0-ap1.7 → Agent Interface
|
||||
0.17.0-ap1.8 → Portfolio + Kontext
|
||||
```
|
||||
---
|
||||
|
||||
*Siehe auch: `ADP_PO_Product_Layering_and_IA_Reset_v0.1.md`, `Sprint1_AP1_5_Hierarchy_Assignment_v0.1.md`, `Kairo_MVP_Usability_Recovery_Plan_v0.2.md`*
|
||||
*Siehe auch: `ADP_Recursive_Containers_and_Execution_Granularity_v0.1.md`, `ADP_PO_Product_Layering_and_IA_Reset_v0.1.md`, `Sprint1_AP1_5_Hierarchy_Assignment_v0.1.md`, `Kairo_MVP_Usability_Recovery_Plan_v0.2.md`*
|
||||
@@ -1,7 +1,7 @@
|
||||
# Kairo — Implementation Truth Table v0.1
|
||||
|
||||
**Status:** living document — bei jedem AP aktualisieren
|
||||
**Stand:** 2026-07-06 (nach AP1.5)
|
||||
**Stand:** 2026-07-06 (nach AP1.5c)
|
||||
**Zweck:** Ehrliche Trennung von **implementiert**, **teilweise**, **nur API/Schema**, **nur Dokumentiert**
|
||||
|
||||
Verhindert, dass Zielbild-Dokumente als Ist-Stand gelesen werden.
|
||||
@@ -30,7 +30,7 @@ Verhindert, dass Zielbild-Dokumente als Ist-Stand gelesen werden.
|
||||
| Capabilities | ✓ | Keine Objekt-Sichtbarkeit |
|
||||
| Auth / Session | ✓ | |
|
||||
| Audit (Auth/Admin) | ◐ | Nicht für alle OM-Events |
|
||||
| Migrationen nummeriert | ✓ | Schema 013 |
|
||||
| Migrationen nummeriert | ✓ | Schema 014 |
|
||||
|
||||
---
|
||||
|
||||
@@ -39,7 +39,7 @@ Verhindert, dass Zielbild-Dokumente als Ist-Stand gelesen werden.
|
||||
| Element | Stand | Anmerkung |
|
||||
|---------|-------|-----------|
|
||||
| Initiative | ✓ | |
|
||||
| Project | ◐ | AP1.5 GUI + API |
|
||||
| Project | ◐ | AP1.5 + AP1.5c: Baum (`parent_project_id`), Blatt-Regel für Actions |
|
||||
| Action | ✓ | UI: Arbeitspaket (interim Maßnahme) |
|
||||
| ActionAssignment | ✓ | |
|
||||
| BacklogItem | ✓ | |
|
||||
|
||||
Reference in new issue
Block a user