AP1.16d + AP1.9c: Planning Debt in Attention und Cockpit-Signale.
Deploy Development / deploy (push) Successful in 46s
Test Suite / pytest-backend (push) Successful in 2m18s
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 19s
Test Suite / playwright-smoke (push) Successful in 12s

Attention-Regeln planning_debt/execution_waiting; Portfolio-Kacheln zeigen Steuerungssignale.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
LarsandCursor committed 2026-07-12 11:48:34 +02:00
1 parent 8546c7021b
commit b9bfa9e5bd
13 files changed
+352 -12

No files matched your search

@@ -128,7 +128,7 @@ Phase H2 PM Work Modes AP1.9 ✓ 9a / → 9b–9e
Phase H3 Plan Outline AP1.12 + AP1.10 ◐ 12a–d, 10c
Phase I Gate-Graph AP1.13 + AP1.15 ◐ 13a/b, 15a–c
Phase I2 Plan/Ist Snapshots AP1.14 ✓
Phase I3 Execution-Plan AP1.16 ◐ 16a–b ✓ / 16c UI / 16d offen
Phase I3 Execution-Plan AP1.16 ◐ 16a–c ✓ / 16d ◐ / AP1.9c ◐
Phase J Portfolio AP1.8 ◐ 8a ✓ / 8b deferred
Phase K Archetyp-Steuerung AP2.0 ◐ 2.0a–c ✓ / → 2.0d–f
Phase L Agent Interface AP1.7 ○
@@ -180,7 +180,7 @@ Siehe **`Kairo_Status_Review_and_Next_Steps_v0.1.md` §5** für vollständige Ro
|-------|-------|--------|------------|
| D0 | DOC-Sync (Truth Table, Gap, Review) | ✓ | eine Wahrheit |
| D1 | Dogfooding R1 — Kairo-Jinkendo in Kairo | **→ nächstes** | B2b-Validation |
| 1 | AP1.9c Cockpit-Signale | offen | MVP §5.7 |
| 1 | AP1.9c Cockpit-Signale | **◐ Code** | Portfolio-Kacheln via Attention |
| 2 | AP1.16a–b Execution-Graph (Schema + Engine) | **◐ Code** | **vor** AP2.0d; Remote-Verifikation nach Deploy |
| 3 | AP2.0d Next-Action-Strategien | offen | MVP Stufe A; nutzt `ready_actions` |
| 4 | AP1.16c–d Plan-Outline-Kanten + Planning Debt | offen | nach 16a–b |
@@ -65,7 +65,7 @@ Verhindert, dass Zielbild-Dokumente als Ist-Stand gelesen werden.
| Initiative Archetypes | ◐ | Migration 016, Registry AP2.0b |
| Method Profiles (Code-Seeds) | ◐ | `product.kairo_dev`, Kumite, Buch — AP2.0b |
| Execution Graph Engine | ◐ | AP1.16b; API `/execution/graph-state` |
| Planning Debt (Attention) | ◐ | Read Model AP1.16b; Cockpit AP1.16d offen |
| Planning Debt (Attention) | ◐ | AP1.16d: Attention + Cockpit-Kacheln AP1.9c |
| `work_cycle` / Sprint | ✗ | 📄 MVP v0.3 B3; Migration AP2.0f geplant |
---
@@ -99,7 +99,7 @@ Verhindert, dass Zielbild-Dokumente als Ist-Stand gelesen werden.
| Sicht | Stand | Anmerkung |
|-------|-------|-----------|
| PM Work Modes Shell | ✓ | AP1.9a: Cockpit, Work, Plan, Control + Redirects |
| Cockpit (Portfolio) | ◐ | Widget-Grid; Rang AP1.8a; Signale auf Kacheln ✗ AP1.9c |
| Cockpit (Portfolio) | ◐ | Widget-Grid; Rang AP1.8a; Signale AP1.9c ◐ |
| Ausführen (/work) | ◐ | Heute, Meine APs |
| Planen (/plan) | ◐ | Outline AP1.12, Gates, Inbox, Struktur, Profil |
| Kontrolle (/control) | ◐ | Status, Plan/Ist AP1.14, Journey AP1.6b |
@@ -69,21 +69,22 @@ Kanten-Richtung in DB: `predecessor_action_id` → `successor_action_id` (Vorgä
| 9 | `GET/POST/DELETE …/execution/dependencies` |
| 10 | pytest: Engine + Cycle-Detection (Unit) |
### AP1.16c — Frontend (folgt)
### AP1.16c — Frontend ✓
| # | Inhalt |
|---|--------|
| 11 | Plan-Outline „Arbeit“: blocked/ready Badges |
| 12 | Vorgänger-Kanten (Liste oder Mini-Graph) |
| 13 | Dependency anlegen/löschen im Action-Kontext |
| 12 | Action-Detail: Vorgänger-Verwaltung |
| 13 | Planning Debt Banner auf Plan → Arbeit |
### AP1.16d — Steuerung (folgt)
### AP1.16d + AP1.9c — Attention & Cockpit ◐
| # | Inhalt |
|---|--------|
| 14 | Method Profile: `planning_levels`, `planning_mode` |
| 15 | Planning Debt in Attention / Cockpit |
| 16 | AP2.0d: Next-Action nutzt `ready_actions` |
| 14 | Attention: `planning_debt`, `execution_waiting` |
| 15 | Cockpit Portfolio-Kacheln: Attention-Chips (AP1.9c) |
| 16 | Method Profile `planning_levels` | deferred |
| 17 | AP2.0d: Next-Action nutzt `ready_actions` | offen |
---