Kairo-Jinkendo/docs/product/Kairo_Implementation_Truth_Table_v0.1.md

Kairo — Implementation Truth Table v0.1

Status: living document — bei jedem AP aktualisieren
Stand: 2026-07-25 (AP2.3/AP2.4 Plugin-Architektur geliefert)
Zweck: Ehrliche Trennung von implementiert, teilweise, nur API/Schema, nur Dokumentiert

Verhindert, dass Zielbild-Dokumente als Ist-Stand gelesen werden.

Review: Kairo_Status_Review_and_Next_Steps_v0.1.md · Dogfooding: Kairo_Dogfooding_Mirror_Steering_v0.1.md

---

Legende

Symbol	Bedeutung
✓	Nutzbar im Alltag (GUI + API)
◐	Backend/API/Schema, GUI unzureichend oder falsch platziert
○	Nur Schema oder Stub
✗	Nicht vorhanden
📄	Nur in Architektur-Docs beschrieben

---

Foundation

Element	Stand	Anmerkung
Tenant / Membership	✓
User ≠ Actor	✓
Actor Directory	✓	human, agent, working_group, external_system
Capabilities	✓	Keine Objekt-Sichtbarkeit
Auth / Session	✓
Audit (Auth/Admin)	◐	Nicht für alle OM-Events
Migrationen nummeriert	✓	Schema bis 023 (action_execution_plan)

---

Operating Model — Persistenz

Element	Stand	Anmerkung
Initiative	✓	inkl. archetype_key, portfolio_rank
Project	◐	AP1.5 + AP1.5c: Baum, Blatt-Regel; archetype_key Mirror AP2.0b
Action	✓	Gate-Zuordnung AP1.6, due_at; sort_order / Deps AP1.16 geplant
ActionAssignment	✓
Action Dependencies (Execution-Graph)	◐	Migration 023, Engine AP1.16b; GUI AP1.16c offen
action_kind (planning/delivery)	◐	Migration 023, API AP1.16a
actions.sort_order	◐	Migration 023
BacklogItem	✓	Gate-Zuordnung AP1.6, sort_order
BacklogItem kinds (MVP)	◐	story/bug/issue AP2.2e — global, nicht profilgebunden
Backlog Epic-Hierarchie	✓	AP2.2f/h: Epic-Baum + P4 Roll-up Read Model (epic_rollup, Attention)
Dual Commit (Direct AP)	◐	ADP P1: Plan→Arbeit im Product-Outline (2026-07-26)
Profil-Vokabular Backlog	◐	AP2.2g: backlog_vocabulary + backlog_epic_hierarchy via effektive steering_elements
Blocker	✓	action_id optional
Milestone	◐	Legacy-Tabelle MVP-Brücke; RoadmapItem bevorzugt
Evidence	✓	roadmap_item_id, action_id; Gitea-Links in description (manuell)
Decision	✓
Review	✓	roadmap_item_id
RecurringElement	✓
Task (unter Action)	◐	AP1.5d: parent_task_id, Baum-API, Outline; Roll-up-UI ◐
Roadmap	◐	1 pro Initiative; Migration 010
RoadmapItem	◐	CRUD + Detail; Verify AP1.4b
RoadmapItem Dependencies	◐	requires/blocks/related; Graph AP1.4d — nur Gates
RoadmapItem Criteria	◐	Checkliste, waive/defer, Reopen AP1.4b/c
Plan-Ist-Verknüpfung	◐	Links, Kriterien, Journey AP1.6; Snapshots AP1.14
Plan-Snapshots	◐	Migration 021, Diff-View Kontrolle AP1.14
Entity Field System	◐	Migration 017, Seeds AP1.10b/AP2.0b
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)	◐	AP1.16d: Attention + Cockpit-Kacheln AP1.9c ✓
work_cycle / Sprint	✓	AP2.0f: RoadmapItem + actions.work_cycle_id; Kontrolle zeigt aktive Zeitbox

---

Steering

Element	Stand	Anmerkung
steering_contexts (009)	✓	Lifecycle, method_key
backend/steering/ lifecycle	✓
Signal Engine	◐	Regeln begrenzt; Cockpit-Kacheln AP1.9c ✓
Method Registry	◐	AP2.0a Stubs; AP2.4 erweiterter MethodDefinition-Vertrag
Archetyp-/Methoden-Katalog PO	✓	ADP v0.2 + MVP v0.3
NextActionCandidate	◐	API + Widget; reason_code AP2.0c/d; Strategien nutzen ready_actions (AP2.0d)
Portfolio-Priorität (Initiativen)	◐	AP1.8a: portfolio_rank, Reorder, Next-Action-Sort
Situativer Steuerungskontext (Next Action)	✗	📄 Vision §7.6; AP1.8b deferred
AttentionItem	◐
Initiative Steering Snapshot	✓	Actions + linked; Archetyp/Guidance AP2.0c
Operating Context API	✓	AP2.3a: GET …/operating-context, ui_profile_json Migration 027
Archetyp-/Methoden-Plugin-Architektur	✓	AP2.3 A–F + AP2.4; Operating Context, Slice-Loader, Route Gating
Steering Kernel Spine	◐	v0.2: Events + slot_map + continuous_product; A2 Abnahme ✓
Steuerungselement-Registry	✓	AP2.4: steering/elements/, FE steeringElementRegistry, Methoden-Vertrag
operating_phase	✗	entfernt AP1.2
signals (Snapshot)	✓	snapshot_signals.py
Graph Read Models (blocked/ready)	◐	AP1.4d/e; Join/OR AP1.15d deferred
Hook Orchestrator	✗	AP1.3 geplant
Structure Builder	✗	📄
DoD Engine	✗	📄
Gitea / Webhook Integration	✗	📄 Schicht 4; manuelle Evidence-Links Phase 1

---

UI / Information Architecture

Sicht	Stand	Anmerkung
PM Work Modes Shell	✓	AP1.9a: Cockpit, Work, Plan, Control + Redirects
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
Scope-Breadcrumb modus-sensitiv	◐	AP1.9b teilweise
Workspace (Legacy-Redirect)	✓	→ Cockpit
Initiative-Übersicht (Steuerung)	✓	AP1.2c / Control Status
Journey	◐	AP1.6b: Fokus-Gates, Kriterien read-only, Ist-Graph
Next-Action-Widget	✓	portfolio + initiative scope
Action Detail-Route	✓	/actions/:actionId
Action Detail-Seite	✓	ActionHubCard + TasksSection
Gate Detail-Seite	◐	/gates/:gateId; Checkliste AP1.4c
Gate Map (read-only)	✓	AP1.13a
Gate Dependencies pflegen	◐	AP1.13b Detail
Zielzustands-Designer	◐	AP1.15a–c; OR deferred
Plan-Outline	◐	AP1.12a–d: Baum, Modal, Reorder, Actions; AP-Kanten AP1.16c offen
Execution-Plan (AP-Graph)	◐	AP1.16c: Outline + Arbeit-Liste + Action-Detail
Profil-Modal (Archetyp/EFS)	◐	AP1.10c
Operating Profile Resolver (FE)	✓	AP2.3b/f + AP2.4: API-first; methodUiDefaults nur Legacy-Fallback
Route Gating (Modus-Routen)	✓	AP2.3d/f: OperatingRouteGate, MODE_ROUTE_GROUPS, renderModeRoutes
Modal-Bearbeitung (Gates/Profil)	◐	viele Sektionen noch Inline-CRUD
Admin-UI	✗
Team-Modus	✗	AP1.9f

---

Milestone / Gate — Soll vs. Ist

Gate-Anforderung (Vision)	Ist
DoD / prüfbare Kriterien	◐
Zieltermin	◐
Abhängigkeiten (Gates)	◐
Abhängigkeiten (Actions)	✗
parallel vs. sequenziell	◐
Plan-Graph vs. Ist-Overlay	◐
Zielzustands-Designer (Joint/Parallel)	◐
Plan-Revision / Graph-Historie	◐
Verify vor reached	◐
Reopen nach reached	◐
Decision bei moved	✗
Quality-Gate-Semantik	◐

---

Referenz-Archetypen End-to-End (MVP Stufe A)

Archetyp	Anlage+Kit	Struktur pflegen	Kontrolle	Op-API	Paket
A1 Reifegrad	◐ AP2.2a	◐	◐	◐	AP2.2c + AP2.0e
A2 Linear	◐ AP2.2a	◐	◐	◐	AP2.2b
B2b Product	◐ AP2.2a	◐	◐	◐	AP2.2d ✓
B3 Sprint-Profil	◐	◐	◐	◐	AP2.2d ✓
B2a Programm	◐ AP2.2a	◐	◐	◐	AP2.2e

---

Archetyp / MVP v0.3

Element	Stand	Anmerkung
Vier-Schichten-Modell dokumentiert	✓	ADP v0.2
Initiative-Archetypen Seeds	◐	AP2.0b
Default-Methode bei Anlage	◐	AP2.0b
Next-Action program_delivery	◐	Strategie registriert
Next-Action continuous_product	◐	Strategie registriert
maturity / sequential / queue / recurring Strategien	✓	AP2.0d; pytest + Deploy
Referenz-Ausprägungen (Kumite, Buch, Kairo)	◐	Code-Registry; Nutzer wählt bei Anlage
Archetyp Starter-Kits	◐	AP2.2a
MVP-Abnahfe Stufe A validiert	✗	AP2.1 nach AP2.2b–e
Operational Actor API	✓	AP1.7: /api/operational/ + Service Tokens
Actor Service Token	✓	AP1.7c; Tenant-scoped, capability-gebunden
MCP produktiv	✗	nach AP2.1 Go

---

Terminologie im UI

Vision	UI heute
Arbeitspaket	Maßnahme (interim)
Quality Gate	Zielzustand / Gate (teils „Meilenstein“ legacy)
Programm	Vorhaben
Plan	◐
Cockpit	✓

---

MVP-Nutzbarkeits-Bar (v0.3 §5) — Kurz

#	Kriterium	Stand
1	Anlegen Archetyp/Methode	◐
2	Struktur modellieren	◐
3	Ist committen	◐
4	Kontrolle begründet	◐
5	Journey	◐
6	Leitfrage ≤2 Min	◐
7	Cockpit Attention	◐

Details: Kairo_Status_Review_and_Next_Steps_v0.1.md §2.1

---

Dokumente vs. Realität

Risiko	Mitigation
Target State liest sich wie fertig	Truth Table + Vision v0.2
Completion Reports = Vision erreicht	Review-Doc + Dogfooding
Roadmap-Phasen veraltet	Roadmap v0.2 §2 aktualisiert 2026-07-11
Usability Recovery → InitiativeDetail	IA-first, Redirects AP1.9a

---

Nächste erwartete Truth-Table-Änderungen

AP	Erwartung
AP2.3/4	✓ Plugin-Architektur + Element-Registry (2026-07-25)
AP2.2a	Starter-Kits ◐→✓
ADP Backlog/Epic	P1–P4 ✓ (Roll-up AP2.2h) · P5 Agent-Tasks offen
AP2.2b–e	Referenz-Archetypen End-to-End ◐→✓
AP2.1	MVP-Abnahfe ✗→✓
AP1.7b	Op-API Parität

---

Aktualisieren bei: jedem Merge auf develop mit produktrelevantem AP.