History

StefanMoCoAt c483f4925d Introduce tournament structure management for Entries Service: - Add multi-layered entity support for `Turniere`, `Bewerbe`, and `Abteilungen` with tenant isolation. - Implement Flyway schema migrations with constraints, indices, and default values for `Turniere`. - Add Kotlin repositories and services for CRUD operations and validation across entities. - Ensure tenant-safe transactions and implement new exception handling for `LockedException` and `ValidationException`. - Provide REST APIs with controllers for managing lifecycle, hierarchy, and relationships between entities (`Turniere`, `Bewerbe`, and `Abteilungen`). - Update Spring configuration with dependency wiring for new services and repositories.		2026-04-03 00:06:38 +02:00
..
Journal	Add documentation and templates for Start-/Ergebnislisten v07: Introduce foundational templates, print styles and partials, and consolidate related session notes.	2026-03-30 22:55:51 +02:00
Logs	feat(horses-service): remove legacy configuration and repository classes	2026-03-23 13:47:04 +01:00
Playbooks	Audit and enhance playbook documentation: fix path inconsistencies, add missing "Abschluss" sections, standardize "Curator" frontmatter, and update Agent roles in README	2026-03-25 23:58:39 +01:00
Roadmaps	Introduce tournament structure management for Entries Service:	2026-04-03 00:06:38 +02:00
Sessions	feat(docs): add detailed session logs and initial architecture plan for Neumarkt 2026	2026-03-27 14:41:21 +01:00
README.md	Audit and enhance playbook documentation: fix path inconsistencies, add missing "Abschluss" sections, standardize "Curator" frontmatter, and update Agent roles in README	2026-03-25 23:58:39 +01:00
SessionLog_2026-03-30.md	docs(ROADMAP & SessionLog): add nightly roadmap and session log for 2026-03-30 updates	2026-03-30 17:14:52 +02:00

README.md

type	status	owner
Reference	ACTIVE	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/:

ADR (docs/01_Architecture/adr/) – Entscheidung/Optionen/Trade-offs (Status proposed ist erlaubt)
Reference (passender Bereich) – Fakten/Ist-Zustand/Inventar
How-to / Runbook (passender Bereich) – konkrete Schritte (Setup/Betrieb/Recovery)
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