S4 Developer Enablement — CI/CD, platform templates
tegwick
f910c7c873
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> |
||
|---|---|---|
| .claude/rules | ||
| .forgejo/workflows | ||
| docs | ||
| registry | ||
| tools | ||
| workflows | ||
| workplans | ||
| .custodian-brief.md | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| SCOPE.md | ||