Files
govoplan-tickets/AGENTS.md
T

33 lines
1.6 KiB
Markdown

# GovOPlaN Tickets Codex Guide
## Documentation Contract
- Treat documentation as part of every behavior change. Update this module's manifest-driven `DocumentationTopic` contributions for affected user and administrator behavior.
- Keep feature content here; `govoplan-docs` projects it without importing Tickets internals.
- Maintain a static user/admin baseline and run `/mnt/DATA/git/govoplan/tools/checks/check-manifest-shapes.py` after behavior or manifest changes.
## Scope
This repository owns the GovOPlaN Tickets domain module seed.
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
Use Gitea issues as the canonical backlog and state log. The shared workflow is installed under `.gitea/`, with labels in `docs/gitea-labels.json`.
Focused verification:
```bash
PYTHONPATH=src:/mnt/DATA/git/govoplan-core/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest discover -s tests
```