Commit graph

7 commits

Author SHA1 Message Date
f910c7c873 Record forge layer inheritance and the real reach of GitOps
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
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>
2026-08-12 00:04:53 +02:00
b34d08c358 Reference forge runner contract 2026-06-05 16:16:42 +02:00
b6712300c6 Clarify enablement forge handoffs 2026-06-05 15:43:13 +02:00
edf7bb5e86 Scope update from repo-scoping refactor 2026-05-01 12:34:31 +02:00
77ff1a1fcf updated Scope 2026-03-27 14:09:54 +01:00
1e35876ec4 Updated scope 2026-03-20 23:43:55 +01:00
2f0e0cbedb docs: add SCOPE.md for rapid orientation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-17 23:11:38 +01:00