feat(records): implement native eAkte vertical
This commit is contained in:
@@ -28,22 +28,30 @@ Records management for file plans, records classification, retention schedules,
|
||||
- audit
|
||||
- transparency
|
||||
|
||||
## Seed State
|
||||
## Implemented State
|
||||
|
||||
The current repository state is intentionally small:
|
||||
The native kernel currently provides:
|
||||
|
||||
- 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
|
||||
- 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.
|
||||
|
||||
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.
|
||||
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
|
||||
|
||||
Define record class, file plan node, retention schedule, disposal hold, archive transfer, and source document links.
|
||||
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
|
||||
|
||||
Reference in New Issue
Block a user