51 lines
1.4 KiB
Markdown
51 lines
1.4 KiB
Markdown
# Records Domain Boundary
|
|
|
|
## Purpose
|
|
|
|
Records management for file plans, records classification, retention schedules, disposal holds, and archive handoff.
|
|
|
|
## Owns
|
|
|
|
- file plans
|
|
- records classification
|
|
- retention schedule application
|
|
- disposal holds
|
|
- archive handoff state
|
|
- legal record identity
|
|
|
|
## Does Not Own
|
|
|
|
- document binary storage
|
|
- DMS editing workflows
|
|
- generic privacy policy engine
|
|
|
|
## Integration Candidates
|
|
|
|
- files
|
|
- dms
|
|
- docs
|
|
- policy
|
|
- audit
|
|
- transparency
|
|
|
|
## 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 record class, file plan node, retention schedule, disposal hold, archive transfer, and source document links.
|
|
|
|
The complete native/external boundary, temporal and purpose-aware record model,
|
|
disposition lifecycle, German public-sector provider profiles, and staged
|
|
implementation are specified in [eAkte Architecture](EAKTE_ARCHITECTURE.md).
|