47 lines
1.2 KiB
Markdown
47 lines
1.2 KiB
Markdown
# Assets Domain Boundary
|
|
|
|
## Purpose
|
|
|
|
Asset lifecycle management for inventory, assignment, maintenance, warranties, inspections, loss and damage reports, depreciation references, and handover protocols.
|
|
|
|
## Owns
|
|
|
|
- asset lifecycle records
|
|
- assignment and handover facts
|
|
- maintenance and warranty references
|
|
- loss and damage reports
|
|
- inspection links
|
|
|
|
## Does Not Own
|
|
|
|
- bookable resource scheduling
|
|
- building-level facilities operations
|
|
- financial ledger postings
|
|
|
|
## Integration Candidates
|
|
|
|
- resources
|
|
- facilities
|
|
- procurement
|
|
- contracts
|
|
- inspections
|
|
- files
|
|
- records
|
|
|
|
## 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 asset identity, assignment, maintenance, warranty, and handover records before adding import and search workflows.
|