Files

T

stefan c696b8c50e feat(db): add regulation-as-data tables for license height and horse age matrices

- Introduced `license_height_matrix` for mapping minimum license requirements to jump heights (ÖTO § 231).
- Added `horse_min_age_matrix` for defining minimum horse ages by discipline, height, or level (ÖTO § 103, FEI GR Art. 136).
- Populated both tables with ÖTO 2026 and FEI-compliant seed data.
- Updated Flyway V008 to remove incorrect `RD4` entry and annotated corrected enum references.
- Created Flyway V009 for introducing the new tables and their seeds.
- Aligned documentation, validation rules, and roadmaps for backend implementation handover.

Signed-off-by: Stefan Mogeritsch <stefan.mo.co@gmail.com>

2026-04-03 11:10:45 +02:00

_archive

Migrate frontend navigation to V3: archive Navigation V2, implement updated screen-tree and back-stack rules, and adapt documentation for startable MVP flow.

2026-04-02 20:09:26 +02:00

01_Architecture

docs: add ADR-0022 for LAN-Sync protocol implementation

2026-04-03 09:45:55 +02:00

02_Guides

Migrate frontend navigation to V3: archive Navigation V2, implement updated screen-tree and back-stack rules, and adapt documentation for startable MVP flow.

2026-04-02 20:09:26 +02:00

03_Domain

feat(db): add regulation-as-data tables for license height and horse age matrices

2026-04-03 11:10:45 +02:00

04_Agents

feat(db): add regulation-as-data tables for license height and horse age matrices

2026-04-03 11:10:45 +02:00

05_Backend

Remove deprecated isAuthenticated logic from PingViewModel and related UI components

2026-03-17 00:18:02 +01:00

06_Frontend

Mark sprint tasks A-1 and parts of B-1 through B-3 as complete. Finalize design inventory, add Editier-Formulare guidelines, Bewerb creation workflow with Abteilungs-Logik, and Veranstaltungs-Kassa wireframes to documentation.

2026-04-03 00:39:59 +02:00

07_Infrastructure

chore: archive outdated architecture and roadmap documents, normalize documentation structure and metadata

2026-03-15 20:00:51 +01:00

90_Reports

docs(reports): add comprehensive status and recommendation reports for key roles

2026-04-02 11:15:38 +02:00

99_Journal

feat(db): add regulation-as-data tables for license height and horse age matrices

2026-04-03 11:10:45 +02:00

BilderSuDo

docs: add UI screenshots for SuDo documentation

2026-01-26 14:35:26 +01:00

Bin

chore: archive outdated architecture and roadmap documents, normalize documentation structure and metadata

2026-03-15 20:00:51 +01:00

Neumarkt2026

feat(horses-service): remove legacy configuration and repository classes

2026-03-23 13:47:04 +01:00

OePS

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

ScreenShots

feat(pferde-feature): introduce Pferde management module with screens, ViewModel, and domain models

2026-03-31 12:20:03 +02:00

temp

Finalize domain model: define event → tournament → class → division hierarchy, multi-tournament account structures, and event-wide cashbox aggregation logic. Add division types and update glossary tasks.

2026-04-02 17:53:49 +02:00

README.md

docs: update README with Zora architecture and roadmap links, add .keep file

2026-03-05 11:34:40 +01:00

README.md

📚 Projektdokumentation "Meldestelle"

Willkommen im "Gehirn" des Projekts. Dieses Verzeichnis ist die Single Source of Truth.

📂 Struktur

🏗️ Core

01_Architecture: Der Masterplan. ADRs, Roadmaps und C4-Modelle.
- Start hier: MASTER_ROADMAP.md
02_Guides: Guides für neue Entwickler (Setup, Guidelines).
03_Domain: Fachlichkeit (Turnierregeln, Entities).

🛠️ Tech Stack

05_Backend: Spring Boot Services, API-Specs, DB-Schema.
06_Frontend: Kotlin Multiplatform, Compose UI, State Management.
07_Infrastructure: Docker, Keycloak, CI/CD, Zora-Architektur.
- Referenz: Zora_System_Architektur.md

🤖 Process

04_Agents: Playbooks für unsere KI-Mitarbeiter.
90_Reports: Statusberichte und Meilenstein-Analysen.
99_Journal: Tägliche Session-Logs.

📝 Regeln für die Dokumentation

Docs-as-Code: Doku liegt beim Code und wird im selben PR aktualisiert.

Frontmatter: Jede Markdown-Datei muss einen YAML-Header haben:

---
type: [ADR, Guide, Reference, Report, Journal]
status: [DRAFT, ACTIVE, DEPRECATED, ARCHIVED]
owner: [Rolle]
---

Archivierung: Lösche nichts. Verschiebe veraltetes Wissen in _archive Ordner oder markiere es als ARCHIVED.

README.md

📚 Projektdokumentation "Meldestelle"

📂 Struktur

🏗️ Core

🛠️ Tech Stack

🤖 Process

📝 Regeln für die Dokumentation

🚀 Quick Links