GovOPlaN/govoplan-tickets
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: rename issue reporting module to tickets

Browse Source
This commit is contained in:
Albrecht Degering
2026-07-29 15:50:18 +02:00
parent a6db06630c
commit 129cad410c
14 changed files with 326 additions and 111 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
AGENTS.md
View File

@@ -1,16 +1,18 @@
# GovOPlaN Issue Reporting Codex Guide
# GovOPlaN Tickets Codex Guide
## Scope
This repository owns the GovOPlaN Issue Reporting platform module seed.
This repository owns the GovOPlaN Tickets domain module seed.
Public or internal problem reporting for broken infrastructure, damaged rooms, IT outages, safety issues, accessibility issues, triage, and routing.
Tickets are queue-oriented reports, requests, incidents, problems, and service
work. Formal administrative procedures remain owned by `govoplan-cases`.
## Boundaries
- Depend on kernel contracts from `govoplan-core` and access contracts from `govoplan-access`.
- Keep domain behavior in this module; expose integration through manifests, capabilities, API routes, events, typed DTOs, and documentation topics.
- Do not import internals from sibling feature modules. Use optional dependencies and capabilities for cross-module behavior.
- Escalation to a case creates a stable cross-module reference; never mutate a ticket into a case or copy a case's authoritative procedural state.
- Keep the seed non-invasive until runtime routes, persistence, and WebUI flows are intentionally designed.
## Local Workflow