docs(records): record lifecycle and endpoint coverage

2026-08-06 05:36:29 +02:00
parent d6fdd7ddf5
commit 8bdf7b5f7e
3 changed files with 77 additions and 15 deletions
@@ -39,6 +39,15 @@ identify the journey it improves, or provide security, operability, recovery,
 accessibility, or usability evidence that those journeys require. Work that
 does neither stays in the backlog until a concrete consumer exists.

+The Records vertical now supplies the journey's native file plan, immutable
+record and item revisions, chronology, close/reopen, retention calculation,
+holds, appraisal, independent disposition approval, recovery-ledger evidence,
+and archive-neutral package simulation. The executable Records fixture proves
+those native transitions without claiming archival custody. The journey still
+needs Forms Runtime/Decisions filing, resumable user handoffs, search
+reconstruction in the pinned composition, and one target-tested archive
+profile.
+
 ## Why this sequence

 The sequence grows one connected product rather than advancing repositories in