feat(records): implement native eAkte vertical

docs/EAKTE_ARCHITECTURE.md

@@ -15,6 +15,28 @@ specialist procedure. It must not duplicate all document editing or storage.
 Implementation is tracked in
 [Records #1](https://git.add-ideas.de/GovOPlaN/govoplan-records/issues/1).
 
+## Implementation Status
+
+The native foundation is implemented through the work packages tracked by
+Records #2-#4:
+
+- versioned file plans and record classes;
+- stable records, immutable revisions, volumes, exact record items, and
+  chronology;
+- tenant isolation, optimistic concurrency, replay-safe writes, independent
+  valid/recorded time, purpose capture, institutional context, and search;
+- a full-height eAkte workspace with file plan, list, details, chronology,
+  temporal status, create/edit, and filing actions;
+- a provider-neutral Core filing contract with exact Files-version and
+  Cases-revision providers.
+
+The remaining delivery order is intentionally visible rather than implied:
+Records #5 owns closure, retention, holds, appraisal, and disposition; #6 owns
+recovery and signed evidence; #7 requires selection and target testing of an
+archive/xdomea provider; and #8 proves the reference journey. Restricted
+per-record access grants also remain a dedicated access-policy slice. No
+archive or destructive effect is currently claimed.
+
 ## Ownership Boundary
 
 Records owns:

docs/RECORDS_DOMAIN_BOUNDARY.md

@@ -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