Lars
cc3129116a
Some checks failed
Test Suite / pytest-backend (push) Waiting to run
Test Suite / lint-backend (push) Waiting to run
Test Suite / compose-smoke (push) Waiting to run
Test Suite / k6 /api/health Baseline (push) Blocked by required conditions
Test Suite / playwright-smoke (push) Blocked by required conditions
Deploy Development / deploy (push) Has been cancelled
Co-authored-by: Cursor <cursoragent@cursor.com>
59 lines
2.3 KiB
Plaintext
59 lines
2.3 KiB
Plaintext
---
|
|
description: Kairo Sprint-0 Architektur-Leitplanken und Dokumentenpriorität
|
|
globs: backend/**,frontend/**,docs/**,.gitea/**
|
|
alwaysApply: true
|
|
---
|
|
|
|
# Kairo Architecture Rules
|
|
|
|
Du arbeitest an **Jinkendo Kairo** (Sprint 0). Kairo ist mandantenfähig und Actor-first.
|
|
|
|
## Kairo Product Reset
|
|
|
|
Before implementing new functionality, preserve the canonical operating model:
|
|
Initiative, Project optional, Milestone, BacklogItem, Action, Assignment, Blocker, Decision, Evidence, Review, RecurringElement, AttentionItem, NextActionCandidate.
|
|
|
|
Do not reduce Kairo to Initiative → Action.
|
|
Do not continue prompt/AI/workflow/MCP work before the operating model MVP is restored.
|
|
|
|
Führende Product-Dokumente: `docs/product/Kairo_Product_Definition_and_MVP_Reset_v0.1.md`, `Kairo_Canonical_Operating_Model_v0.1.md`, `Kairo_Corrected_MVP_Roadmap_v0.1.md`.
|
|
|
|
## Dokumentenpriorität bei Konflikten
|
|
|
|
1. `docs/product/Kairo_Product_Definition_and_MVP_Reset_v0.1.md`
|
|
2. `docs/product/Kairo_Canonical_Operating_Model_v0.1.md`
|
|
3. `docs/product/Kairo_Corrected_MVP_Roadmap_v0.1.md`
|
|
4. `docs/product/Jinkendo_Kairo_Product_Spec_v0.2.md`
|
|
5. `docs/architecture/Kairo_Current_State_Gap_Analysis_AP0.1_AP0.6b_v0.1.md`
|
|
6. `docs/architecture/CLAUDE_Product_Direction_Addendum_v0.1.md`
|
|
7. `docs/architecture/Kairo_Tenant_Invariants_v0.1.md`
|
|
8. `docs/architecture/Kairo_Sprint0_Principle_Gate_v0.1.md`
|
|
9. `docs/sprints/Jinkendo_Kairo_04_Sprint0_Foundation_v0.3.md`
|
|
10. `docs/reference/design-principles/alignment/*`
|
|
11. Mitai/Shinkan-Einzelprinzipien (nur Begründung, kein Scope)
|
|
|
|
## Reference design principles
|
|
|
|
Referenzmaterial:
|
|
|
|
- `docs/reference/design-principles/mitai/`
|
|
- `docs/reference/design-principles/shinkan/`
|
|
- `docs/reference/design-principles/alignment/`
|
|
|
|
Nicht automatisch Implementierungs-Scope. Übernahme nur via Principle Gate oder Architecture Decision.
|
|
|
|
## Harte Guardrails
|
|
|
|
- Kein Single-User ohne Tenant
|
|
- User ≠ Actor; Agenten sind Actors
|
|
- Auth, Capability, Feature, Governance trennen
|
|
- Keine hardcodierten Rechte, Prompts oder Fachkonfiguration
|
|
- Nummerierte SQL-Migrationen; kein ad-hoc DDL in Routern
|
|
- Keine Mitai-/Shinkan-Domänenlogik kopieren
|
|
- Kairo nicht auf Initiative → Action reduzieren
|
|
- Keine Prompt-/KI-/Workflow-/MCP-Erweiterung vor Operating-Model-MVP
|
|
|
|
## Abweichungen
|
|
|
|
Architecture Decision Proposal nach Vorlage in `docs/architecture/ARCHITECTURE_DECISION_PROPOSAL_TEMPLATE.md`.
|