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

docs: separate installer artifact trust boundary

Browse Source
This commit is contained in:
Albrecht Degering
2026-07-21 15:55:30 +02:00
parent a863767233
commit 492fec46b6
2 changed files with 19 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/REFERENCE_JOURNEY_PROGRAM.md
View File

@@ -69,6 +69,13 @@ journey needs and supplies contracts shared by all five stages.
8. **Release proof.** Version alignment, clean install/upgrade, module
permutations, backup/restore, degraded-provider behavior, security checks,
and target-environment acceptance gate product claims.
9. **Artifact and infrastructure egress.** Tenant connectors use the pinned
connector boundary. Installer artifacts use a separate deployment-owned
trust path: approved origins, bounded pinned download or operator prefetch,
signature/checksum verification, safe extraction, and offline package-manager
execution. Database, broker, cache, and worker channels are constrained by
deployment network policy and authenticated transport rather than treated as
tenant connector profiles.
## Documentation contract for every reference stage