Align app scope headings
This commit is contained in:
16
SCOPE.md
16
SCOPE.md
@@ -127,7 +127,7 @@ lessons into reusable S5 app release patterns.
|
||||
|
||||
---
|
||||
|
||||
## Current Implementation Surface
|
||||
## Current State
|
||||
|
||||
- Gitea is deployed and operational as the current forge. Its deploy-capable
|
||||
Helm/SOPS/manifests now live in `railiance-forge`; this repo keeps
|
||||
@@ -197,6 +197,20 @@ from that file.
|
||||
|
||||
---
|
||||
|
||||
## Terminology
|
||||
|
||||
- Preferred terms:
|
||||
S5 app release, application workload, app runbook, release values, deployment
|
||||
guardrail, smoke evidence.
|
||||
- Forge terms:
|
||||
source forge, registry, package registry, runner substrate, and artifact
|
||||
evidence belong to `railiance-forge`; this repo consumes those capabilities.
|
||||
- Potentially confusing terms:
|
||||
"deployment" here means app release deployment unless a command explicitly
|
||||
delegates to `railiance-forge` for current Gitea operation.
|
||||
|
||||
---
|
||||
|
||||
## Related / Overlapping
|
||||
|
||||
- `railiance-platform`: shared CNPG clusters, backup primitives, object storage,
|
||||
|
||||
Reference in New Issue
Block a user