59 lines
1.7 KiB
Markdown
59 lines
1.7 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
|
|
|
|
## Implemented State
|
|
|
|
The native kernel currently provides:
|
|
|
|
- versioned file-plan nodes and record classes;
|
|
- stable record identities, immutable OCC-guarded revisions, volumes, exact
|
|
filed items, and chronology;
|
|
- independent valid and recorded time with current/at/all temporal reads;
|
|
- tenant, purpose, actor/capacity, source authority, institutional context,
|
|
provenance, and idempotency fields;
|
|
- provider-neutral exact-source capabilities, initially implemented by Files
|
|
file versions and Cases revisions;
|
|
- tenant APIs, search projection, uninstall/retirement guards, and a Records
|
|
workspace using shared WebUI controls.
|
|
|
|
Restricted object grants and the lifecycle after the planned/open stages remain
|
|
separate governed slices. Archive transfer and destructive effects are not
|
|
implemented by this kernel.
|
|
|
|
## First Implementation Slice
|
|
|
|
Complete restricted access, closure and retention calculation, holds,
|
|
appraisal, disposition, transfer, recovery evidence, and one target-tested
|
|
archive provider without moving source-module ownership into Records.
|
|
|
|
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).
|