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

docs(records): record lifecycle and endpoint coverage
Dependency Audit / dependency-audit (push) Successful in 1m38s
Details
Deployment Installer / deployment-installer (push) Successful in 6s
Details
Security Audit / security-audit (push) Successful in 10m32s
Details

Browse Source
This commit is contained in:
zemion
2026-08-06 05:36:29 +02:00
parent d6fdd7ddf5
commit 8bdf7b5f7e
3 changed files with 77 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/REFERENCE_JOURNEY_PROGRAM.md
+9
View File
@@ -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
docs/STRATEGY_STATUS.md
+1 -1
View File
@@ -84,7 +84,7 @@ reconciliation, publication/export, and guided handoff evidence.
| --- | --- | --- |
| No reference-ready product package | The platform cannot yet make a bounded supported-product claim | Complete one named target composition and evidence bundle |
| Human-work spine incomplete | Users still navigate modules and remember unfinished work | Task/work inbox, resumable guided journey, deadlines and handoffs |
| Records/eAkte shallow | Institutional memory and disposition remain fragmented | Native record lifecycle plus external DMS/archive overlay |
| Records/eAkte target integration incomplete | Native lifecycle, retention, holds, approval, recovery, and transfer simulation are implemented, but real custody is not proved | Target-test one archive/xdomea profile and complete the assisted reference journey |
| Cross-cutting governance adoption uneven | Historical and purpose-sensitive behavior varies by module | Enforced adoption declarations and route/query/effect migration |
| Explicit help/accessibility depth incomplete | German/reference and F1 association gates now pass, but generic fallback remains too common | High-risk German help content and browser/a11y matrix |
| Real federation absent | Cross-institution exchange remains connector-specific | Paired-instance signed exchange and reconciliation proof |