AP0.R1: Product Reset Dokumente ins Repository aufgenommen
Deploy Development / deploy (push) Successful in 43s
Test Suite / pytest-backend (push) Successful in 43s
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 18s
Test Suite / playwright-smoke (push) Successful in 11s
Deploy Development / deploy (push) Successful in 43s
Test Suite / pytest-backend (push) Successful in 43s
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 18s
Test Suite / playwright-smoke (push) Successful in 11s
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
1 parent
cc3129116a
commit
01b3c594a1
5 files changed
+1295
No files matched your search
@@ -0,0 +1,94 @@
|
||||
# CLAUDE.md Addendum
|
||||
## Kairo Product Direction Reset v0.1
|
||||
|
||||
Dieses Addendum ist in `CLAUDE.md` aufzunehmen oder dort zu referenzieren.
|
||||
|
||||
---
|
||||
|
||||
## Current Product Direction
|
||||
|
||||
Kairo is not a task list.
|
||||
|
||||
Kairo is the operational Program Director of the Jinkendo product family.
|
||||
|
||||
The central question is:
|
||||
|
||||
> Which next step moves an initiative forward most effectively now?
|
||||
|
||||
---
|
||||
|
||||
## Do not reduce Kairo to
|
||||
|
||||
```text
|
||||
Initiative
|
||||
→ Action
|
||||
```
|
||||
|
||||
This is only the first technical slice.
|
||||
|
||||
The canonical operating model includes:
|
||||
|
||||
- Initiative
|
||||
- Project optional
|
||||
- Milestone
|
||||
- BacklogItem
|
||||
- Action
|
||||
- Assignment to Actor
|
||||
- Blocker
|
||||
- Decision
|
||||
- Evidence
|
||||
- Review
|
||||
- RecurringElement
|
||||
- AttentionItem
|
||||
- NextActionCandidate
|
||||
|
||||
---
|
||||
|
||||
## Current implementation state
|
||||
|
||||
Valid but incomplete:
|
||||
|
||||
- Tenant
|
||||
- Actor
|
||||
- TenantContext
|
||||
- Capabilities
|
||||
- Entitlements
|
||||
- Initiative
|
||||
- Action
|
||||
- Assignment
|
||||
- Workspace UX
|
||||
|
||||
Missing MVP-critical concepts:
|
||||
|
||||
- Data Layer
|
||||
- Actor Directory
|
||||
- Tenant Invariants
|
||||
- Backlog
|
||||
- Blocker
|
||||
- Milestone
|
||||
- Evidence
|
||||
- Review
|
||||
- Recurrence
|
||||
- Attention / Next Action
|
||||
|
||||
---
|
||||
|
||||
## Implementation rule
|
||||
|
||||
Do not continue foundation work unless it directly supports MVP usability or prevents a documented refactoring trap.
|
||||
|
||||
Do not continue prompt/AI/workflow/MCP work until the operating model MVP is restored.
|
||||
|
||||
---
|
||||
|
||||
## Gate for new tasks
|
||||
|
||||
Every new task must answer:
|
||||
|
||||
1. Does it support the operational Program Director vision?
|
||||
2. Does it improve real initiative steering?
|
||||
3. Does it prevent a concrete refactoring trap?
|
||||
4. Is it a small verifiable slice?
|
||||
5. Are non-goals explicit?
|
||||
|
||||
If not, do not implement.
|
||||
@@ -0,0 +1,210 @@
|
||||
# Jinkendo Kairo
|
||||
## Current State & Gap Analysis AP0.1–AP0.6b v0.1
|
||||
|
||||
Status: Arbeitsstand / Reset-Grundlage
|
||||
Stand: 2026-07-05
|
||||
|
||||
---
|
||||
|
||||
## 1. Zweck
|
||||
|
||||
Dieses Dokument ordnet den aktuellen Implementierungsstand gegen das kanonische Kairo Operating Model ein.
|
||||
|
||||
---
|
||||
|
||||
## 2. Aktueller Stand
|
||||
|
||||
### AP0.1 / AP0.1b
|
||||
|
||||
Technische Runtime:
|
||||
|
||||
- Deployment
|
||||
- Docker
|
||||
- FastAPI
|
||||
- PostgreSQL
|
||||
- Migration Runner
|
||||
- Health
|
||||
- Tests
|
||||
|
||||
Bewertung: gültig.
|
||||
|
||||
### AP0.2
|
||||
|
||||
Auth, Identity, Tenant und Actor:
|
||||
|
||||
- User
|
||||
- Sessions
|
||||
- Login/Logout
|
||||
- Tenant
|
||||
- Membership
|
||||
- Actor
|
||||
- TenantContext
|
||||
- Bootstrap
|
||||
- Audit bei Auth
|
||||
|
||||
Bewertung: gültig und zentral.
|
||||
|
||||
### AP0.3
|
||||
|
||||
Capability / Rights Registry:
|
||||
|
||||
- Capabilities
|
||||
- Grants
|
||||
- TenantContext.capabilities
|
||||
- require_capability
|
||||
- Entitlements Snapshot
|
||||
|
||||
Bewertung: gültig und zentral.
|
||||
|
||||
### AP0.4
|
||||
|
||||
Prompt / Feature / Config Registry:
|
||||
|
||||
- Feature Registry
|
||||
- PromptDefinition/Version/Step
|
||||
- Placeholder
|
||||
- Config
|
||||
- Single Render
|
||||
|
||||
Bewertung: technisch brauchbar, aber aktuell eingefroren. Nicht weiter ausbauen, bis MVP-Fachkern trägt.
|
||||
|
||||
### AP0.5
|
||||
|
||||
Minimaler Vorhaben-/Maßnahmen-Slice:
|
||||
|
||||
- Initiatives
|
||||
- Actions
|
||||
- Assignments
|
||||
- Status
|
||||
- Priority
|
||||
- Meine offenen Maßnahmen
|
||||
- Audit
|
||||
- Tests
|
||||
|
||||
Bewertung: gültiger technischer Start, aber zu flach als Kairo-MVP.
|
||||
|
||||
### AP0.6 / AP0.6b
|
||||
|
||||
Workspace UX / PWA Remediation:
|
||||
|
||||
- Jinkendo Look & Feel
|
||||
- App Shell
|
||||
- PWA-Grundlagen
|
||||
- responsive Desktop/Mobile
|
||||
- Widget/View Registry
|
||||
- Workspace/Vorhaben/Meine Maßnahmen
|
||||
|
||||
Bewertung: gültig und notwendig für Produktprüfung.
|
||||
|
||||
---
|
||||
|
||||
## 3. Gap-Matrix
|
||||
|
||||
| Konzept | Status | Bewertung |
|
||||
|---|---:|---|
|
||||
| Tenant | implementiert | gültig |
|
||||
| Actor | implementiert | Directory fehlt |
|
||||
| TenantContext | implementiert | gültig |
|
||||
| Capabilities | implementiert | gültig |
|
||||
| Initiative | implementiert | Status ggf. um draft ergänzen |
|
||||
| Action | implementiert | Status ggf. um ready/review_required ergänzen |
|
||||
| ActionAssignment | implementiert | ActorSelect braucht echtes Directory |
|
||||
| Project | fehlt | optional, aber Modell muss vorbereitet werden |
|
||||
| Milestone | fehlt | MVP-relevant minimal |
|
||||
| BacklogItem | fehlt | MVP-relevant |
|
||||
| Blocker | fehlt | MVP-relevant |
|
||||
| Evidence | fehlt | MVP-relevant minimal |
|
||||
| Decision | fehlt | MVP-relevant minimal |
|
||||
| Review | fehlt | MVP-relevant minimal |
|
||||
| RecurringElement | fehlt | MVP-relevant vorbereiten |
|
||||
| NextActionCandidate | fehlt | MVP-kritisches Read Model |
|
||||
| AttentionItem | fehlt | MVP-kritisches Read Model |
|
||||
| Data Layer | fehlt | Umbaufalle |
|
||||
| Tenant Invariants Doc | fehlt | Umbaufalle |
|
||||
| Actor Directory | fehlt | Actor-first nicht vollständig |
|
||||
| Prompt Workflow | vorbereitet | nicht MVP-kritisch |
|
||||
| MCP | fehlt | später |
|
||||
| KI-Priorisierung | fehlt | später |
|
||||
|
||||
---
|
||||
|
||||
## 4. Was bleibt gültig?
|
||||
|
||||
Gültig bleiben:
|
||||
|
||||
- technische Runtime
|
||||
- Auth
|
||||
- Tenant
|
||||
- Actor
|
||||
- Capability Registry
|
||||
- Entitlements
|
||||
- Prompt Kernel als eingefrorene Vorleistung
|
||||
- Initiative/Action als erster Slice
|
||||
- Jinkendo Workspace UX
|
||||
- Widget/View Registry
|
||||
|
||||
---
|
||||
|
||||
## 5. Was muss korrigiert werden?
|
||||
|
||||
Korrigiert werden muss die implizite Produktlinie.
|
||||
|
||||
Die aktuelle UI und API dürfen nicht den Eindruck erzeugen:
|
||||
|
||||
```text
|
||||
Kairo = Vorhaben + Aufgaben
|
||||
```
|
||||
|
||||
Kairo muss sichtbar werden als:
|
||||
|
||||
```text
|
||||
Kairo = operative Steuerung von Vorhaben
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 6. Zwingende nächste Grundlagen
|
||||
|
||||
Vor weiterem Fachausbau:
|
||||
|
||||
1. Tenant Invariants
|
||||
2. Actor Directory
|
||||
3. Data Layer Minimum
|
||||
4. Attention/Next-Action Read Model
|
||||
5. Operating Model Extension I
|
||||
|
||||
---
|
||||
|
||||
## 7. Nächste Implementierungsvorschläge
|
||||
|
||||
### AP0.7 — Tenant Hardening, Actor Directory & Data Layer Minimum
|
||||
|
||||
Klein halten, aber zwingend.
|
||||
|
||||
### AP0.8 — Operating Model Extension I
|
||||
|
||||
BacklogItem, Blocker, Milestone minimal, Attention Items.
|
||||
|
||||
### AP0.9 — Operating Model Extension II
|
||||
|
||||
Evidence, Decision, Review, RecurringElement minimal.
|
||||
|
||||
---
|
||||
|
||||
## 8. Risiko, wenn wir nicht korrigieren
|
||||
|
||||
Ohne Korrektur wird Kairo:
|
||||
|
||||
- eine bessere To-do-Liste
|
||||
- ein generischer Workspace
|
||||
- technisch überfundiert
|
||||
- fachlich zu flach
|
||||
- später schwer auf Program Director umzubauen
|
||||
|
||||
---
|
||||
|
||||
## 9. Empfehlung
|
||||
|
||||
Keine weitere Prompt-/Foundation-/Admin-Arbeit starten.
|
||||
|
||||
Erst kanonisches Operating Model und Data Layer wieder in die Implementierungsroadmap bringen.
|
||||
Reference in new issue
Block a user