48 lines
1.2 KiB
Markdown
48 lines
1.2 KiB
Markdown
# Helpdesk Domain Boundary
|
|
|
|
## Purpose
|
|
|
|
Internal service desk workflows for IT, facilities, HR, finance, procurement, access requests, assignment, escalation, and resolution tracking.
|
|
|
|
## Owns
|
|
|
|
- internal support tickets
|
|
- service categories
|
|
- assignment and escalation state
|
|
- resolution records
|
|
- SLA-facing timestamps
|
|
|
|
## Does Not Own
|
|
|
|
- public issue intake forms
|
|
- domain case adjudication
|
|
- asset inventory
|
|
|
|
## Integration Candidates
|
|
|
|
- issue-reporting
|
|
- assets
|
|
- facilities
|
|
- mail
|
|
- notifications
|
|
- workflow
|
|
- files
|
|
- tasks
|
|
|
|
## Seed State
|
|
|
|
The current repository state is intentionally small:
|
|
|
|
- module manifest and entry point
|
|
- tenant-level permission definitions
|
|
- manager and viewer role templates
|
|
- documentation topic describing the module boundary
|
|
- Gitea issue workflow templates
|
|
- manifest contract test
|
|
|
|
No runtime API, database model, migration, WebUI route, or navigation item is registered yet. The first implementation slice should preserve the boundary above and only add user-visible surfaces once the workflow model is clear.
|
|
|
|
## First Implementation Slice
|
|
|
|
Create service ticket types, status flow, assignee ownership, and linking hooks for issue-reporting, assets, and facilities.
|