coulomb/railiance-enablement
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record forge layer inheritance and the real reach of GitOps
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Decision d151d817 gives S4 the forge layer responsibility - runner placement,
registry retention, artifact lifecycle, package credentials - its first concrete
owned accountability.

The existing ArgoCD claim was verified and is accurate: ArgoCD is on CoulombCore
as an S2-managed addon. What was missing is that GitOps does not reach the live
cluster - ArgoCD is absent from railiance01, its Applications target CoulombCore
in-cluster, nothing on railiance01 is ArgoCD-managed, and the live workloads
deploy by Makefile. Two Applications are Degraded and one is OutOfSync/Missing.

Also states plainly that this layer's INTENT promises more than the repo
contains, and that the gap is open debt rather than description.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-12 00:04:53 +02:00
parent a2525a404c
commit f910c7c873
1 changed files with 21 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

28
SCOPE.md
View file

@ -74,13 +74,27 @@ services. S5 applications consume S4 templates and conventions, while
## Current State
- Status: emerging (ArgoCD deployed; no S4 workplans yet)
- Implementation: ArgoCD is deployed in the `argocd` namespace on COULOMBCORE
as a cluster addon managed from S2 for now; no S4-owned workplans yet
- Stability: n/a for S4-owned content; ArgoCD itself is operational
- Usage: ArgoCD available for GitOps deployments; formal S4 tooling work begins
after S3 baseline and should consume runner/registry capabilities from
`railiance-forge`
- Status: emerging — **now owns the forge layer responsibility** (decision
`d151d817`, 2026-08-11), which is S4's first concrete owned accountability;
still no S4-owned workplans
- Inherited from `railiance-forge`: runner placement and labels, registry
retention, artifact lifecycle, package credentials. The Forgejo **workload**
becomes `rapp-forgejo`; this layer takes the **layer** responsibility, because
it already declared the handoff contract for exactly those concerns
- Implementation: ArgoCD is deployed in the `argocd` namespace on CoulombCore as
a cluster addon managed from S2 — verified still true 2026-08-12
- **But GitOps does not reach the live cluster.** ArgoCD is not deployed on
`railiance01`, its Applications target CoulombCore in-cluster, and no
`railiance01` namespace is ArgoCD-managed. The live workloads deploy by
Makefile, outside GitOps. Whether to adopt, retire or relocate ArgoCD is
reopened — see `railiance-platform/ArchitectureBlueprint.md` §5.6
- Stability: n/a for S4-owned content; ArgoCD itself runs, but two of its
Applications are Degraded and one is OutOfSync/Missing
- Usage: formal S4 tooling work begins after S3 baseline and should consume
runner/registry capabilities from `railiance-forge` until that migration
completes
- Honest gap: this layer's `INTENT.md` promises considerably more than the repo
contains (25 commits, no workplans). Read that as open debt, not description
---