46 lines
1.2 KiB
Markdown
46 lines
1.2 KiB
Markdown
# Resources Domain Boundary
|
|
|
|
## Purpose
|
|
|
|
Shared resource inventory for rooms, vehicles, devices, counters, labs, booths, equipment, availability rules, maintenance blocks, capacities, and accessibility metadata.
|
|
|
|
## Owns
|
|
|
|
- resource inventory
|
|
- availability rules
|
|
- capacity and accessibility metadata
|
|
- maintenance blocks
|
|
- resource classification
|
|
|
|
## Does Not Own
|
|
|
|
- reservation workflow
|
|
- asset depreciation
|
|
- facility building operations
|
|
|
|
## Integration Candidates
|
|
|
|
- booking
|
|
- assets
|
|
- facilities
|
|
- calendar
|
|
- files
|
|
- workflow
|
|
|
|
## 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 the resource catalogue model and expose resource availability metadata for booking and facilities modules.
|