Pinned core-install.yaml (sha256 1a87025d...c448) with a kustomize
resources patch for the four workloads. The unpatched pin diffs clean
against live; the resources patch is declared only, and its apply waits
on the founder in RAIL-EN-WP-0002-T02. SCOPE.md no longer says ArgoCD is
absent from railiance01.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
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>
