GovOPlaN/govoplan
2
0
Fork 0
Code Issues 18 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

Prove reference journey compositions
Dependency Audit / dependency-audit (push) Successful in 1m45s
Details
Deployment Installer / deployment-installer (push) Successful in 6s
Details
Security Audit / security-audit (push) Successful in 11m16s
Details

Browse Source
This commit is contained in:
zemion
2026-08-06 12:42:20 +02:00
parent 8bdf7b5f7e
commit 69ba1037bf
9 changed files with 383 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/REFERENCE_JOURNEY_PROGRAM.md
+7 -5
View File
@@ -42,11 +42,13 @@ 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.
and archive-neutral package simulation. Forms Runtime, Cases, and Decisions
expose exact, permission-rechecked source revisions for explicit filing, and
all three contribute metadata-only native Search projections that can be
rebuilt from authoritative state. The executable fixtures prove those native
transitions without claiming archival custody. The journey still needs
resumable user handoffs, pinned-composition reconstruction evidence, and one
target-tested archive profile.
## Why this sequence