feat(records): complete eAkte reference journey

README.md

@@ -12,7 +12,8 @@ authority over their objects and bytes.
 The first working vertical slice includes PostgreSQL/SQLite models and an
 Alembic migration, tenant-scoped APIs, optimistic concurrency and idempotent
 filing, temporal reads, search registration, a full-height Records workspace,
-and provider-neutral filing from Files and Cases.
+provider-neutral filing from Files, Cases, Forms Runtime, and Decisions, and a
+governed close/retention/hold/appraisal/disposition/transfer lifecycle.
 
 The `privacy.dsar.records` capability exports bounded record and lifecycle
 metadata from an explicit record or authoritative source linkage. Canonical
@@ -48,24 +49,38 @@ Implemented optional integrations:
 
 - files
 - cases
+- forms runtime
+- decisions
+- approvals
+- audit
 - search
 
 Planned optional integrations include:
 
-- forms runtime and decisions
 - Campaigns, Postbox, and Reporting
-- DMS/archive providers
+- target-tested DMS/archive providers
 - policy
-- audit
 - transparency
 
 ## Current Boundary
 
-The current kernel supports planned and open records. Restricted per-record
-grants, closure, retention calculation, holds, appraisal, disposition,
-transfer, destruction, and external archive effects remain explicit later
-work packages. Enabling Records does not trigger destructive or external
-effects.
+The current kernel supports planned/open records, exact filing, closure,
+retention calculation, holds, appraisal, independent disposition approval,
+archive-neutral packaging, recovery evidence, and a clearly marked transfer
+simulation. The simulation never claims archival custody. Restricted
+per-record grants, real target conformance, destructive execution, and real
+archive effects remain explicit later work packages.
+
+## Reference Journey
+
+The executable resident-parking-permit fixture proves equivalent assisted and
+authenticated digital eAkten. It files the exact form, attachment, case and
+representation, decision, delivery, and correction revisions; preserves
+authority, purpose, policy, chronology, and custody evidence; exercises hold
+and independent approval; and verifies search, temporal reconstruction, and
+source/package integrity after a SQLite backup/restore round trip. The Records
+workspace keeps the selected `recordId` in the URL so an authorized actor can
+resume the same record and inspect the complete evidence chain.
 
 The detailed target and implementation sequence are documented in
 [docs/EAKTE_ARCHITECTURE.md](docs/EAKTE_ARCHITECTURE.md).