Lars
01b3c594a1
All checks were successful
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>
1.6 KiB
1.6 KiB
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
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:
- Does it support the operational Program Director vision?
- Does it improve real initiative steering?
- Does it prevent a concrete refactoring trap?
- Is it a small verifiable slice?
- Are non-goals explicit?
If not, do not implement.