StefanMoCoAt
a72953cea7
Some checks failed
Build and Publish Docker Images / build-and-push (., backend/infrastructure/gateway/Dockerfile, api-gateway, api-gateway) (push) Successful in 8m24s
Build and Publish Docker Images / build-and-push (., backend/services/ping/Dockerfile, ping-service, ping-service) (push) Successful in 7m17s
Build and Publish Docker Images / build-and-push (., config/docker/caddy/web-app/Dockerfile, web-app, web-app) (push) Failing after 2m49s
Build and Publish Docker Images / build-and-push (., config/docker/keycloak/Dockerfile, keycloak, keycloak) (push) Successful in 1m57s
50 lines
2.3 KiB
Markdown
50 lines
2.3 KiB
Markdown
---
|
||
type: Reference
|
||
status: ACTIVE
|
||
owner: Lead Architect
|
||
---
|
||
# Agent Operating Model (AOM)
|
||
|
||
Dieses Verzeichnis definiert, **wie** KI-Unterstützung im Projekt eingesetzt wird:
|
||
Rollen/Playbooks, Ablageorte und der minimale Prozess, damit Wissen nicht verloren geht.
|
||
|
||
## Governance (Konfliktregel)
|
||
|
||
* **Single Source of Truth:** `docs/`
|
||
* **Tooling/Automatisierung:** `.junie/` (Scripts, Checks, optional Archiv – keine zweite „Wahrheit“)
|
||
* **Personas-Übersicht:** `AGENTS.md` (Repo-Root)
|
||
|
||
Wenn Aussagen in `.junie/*` und `docs/*` widersprechen, gilt **`docs/*`**.
|
||
|
||
## Artefakt-Vertrag (Anti-Wissensverlust)
|
||
|
||
Jede KI-Session endet mit **genau einem** Artefakt in `docs/`:
|
||
|
||
1. **ADR** (`docs/01_Architecture/adr/`) – Entscheidung/Optionen/Trade-offs (Status `proposed` ist erlaubt)
|
||
2. **Reference** (passender Bereich) – Fakten/Ist-Zustand/Inventar
|
||
3. **How-to / Runbook** (passender Bereich) – konkrete Schritte (Setup/Betrieb/Recovery)
|
||
4. **Journal Entry** (`docs/99_Journal/`) – Kurzprotokoll, wenn nichts „fertig“ wird
|
||
|
||
## Tool-Rollen (keine Doppelarbeit)
|
||
|
||
* **Junie (IDE-nah):** Code/Repo-Wahrheit (Dateien, konkrete Implementierung, Refactors)
|
||
* **Gemini (parallel/extern):** Variantenraum (Optionen, Argumentation, Formulierungen, Gegenentwurf)
|
||
|
||
„Wahr“ wird es erst, wenn es im passenden `docs/*` Artefakt verankert ist.
|
||
|
||
## Playbooks
|
||
|
||
| Playbook | Rolle | Typ |
|
||
|----------|-------|-----|
|
||
| `Playbooks/Architect.md` | 🏗️ Lead Architect | Strategie, Planung, Build-System |
|
||
| `Playbooks/BackendDeveloper.md` | 👷 Backend Developer | Spring Boot, Kotlin, DDD |
|
||
| `Playbooks/Curator.md` | 🧹 Curator | Dokumentation, Wissensmanagement |
|
||
| `Playbooks/DevOpsEngineer.md` | 🐧 DevOps Engineer | Docker, CI/CD, Infrastruktur |
|
||
| `Playbooks/DomainExpert.md` | 📋 Domain Expert | Fachlichkeit, Regelwerke, Gherkin |
|
||
| `Playbooks/FrontendExpert.md` | 🎨 Frontend Expert | KMP, Compose, Offline-First |
|
||
| `Playbooks/Gemini.md` | 🤖 Gemini (extern) | Konzeptarbeit, Optionen, ADR-Formulierung |
|
||
| `Playbooks/Junie.md` | 🤖 Junie (IDE) | Repo-nahe Arbeit, Code, Implementierung |
|
||
| `Playbooks/QASpecialist.md` | 🧐 QA Specialist | Teststrategie, Edge-Cases |
|
||
| `Playbooks/RulebookExpert.md` | 📜 ÖTO/FEI Rulebook Expert | Regelwerks-Compliance, Validierung |
|
||
| `Playbooks/UIUXDesigner.md` | 🖌️ UI/UX Designer | High-Density Design, Wireframes |
|