49 lines
1.1 KiB
Markdown
49 lines
1.1 KiB
Markdown
# Inspections Domain Boundary
|
|
|
|
## Purpose
|
|
|
|
Inspection workflows for site visits, checklists, findings, measures, deadlines, evidence, and re-inspections.
|
|
|
|
## Owns
|
|
|
|
- inspection plans
|
|
- site visits
|
|
- checklists
|
|
- findings
|
|
- corrective measures
|
|
- deadlines
|
|
- re-inspection links
|
|
|
|
## Does Not Own
|
|
|
|
- permit decision records
|
|
- facility master data
|
|
- document binary storage
|
|
|
|
## Integration Candidates
|
|
|
|
- permits
|
|
- facilities
|
|
- grants
|
|
- assets
|
|
- files
|
|
- forms-runtime
|
|
- 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
|
|
|
|
Define inspection type, visit, checklist, finding, measure, deadline, evidence, and re-inspection concepts.
|