48 lines
1.2 KiB
Markdown
48 lines
1.2 KiB
Markdown
# Facilities Domain Boundary
|
|
|
|
## Purpose
|
|
|
|
Facilities management for buildings, rooms, maintenance, cleaning, keys, access zones, recurring inspections, occupancy, defects, and service contractors.
|
|
|
|
## Owns
|
|
|
|
- building and room operations
|
|
- maintenance and cleaning schedules
|
|
- key and access-zone facts
|
|
- occupancy metadata
|
|
- defect records
|
|
- contractor references
|
|
|
|
## Does Not Own
|
|
|
|
- generic bookable resource slots
|
|
- asset accounting lifecycle
|
|
- public issue intake
|
|
|
|
## Integration Candidates
|
|
|
|
- resources
|
|
- assets
|
|
- inspections
|
|
- contracts
|
|
- procurement
|
|
- booking
|
|
- files
|
|
|
|
## 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 building, room, maintenance block, defect, contractor, and inspection link concepts with clear resource and asset boundaries.
|