S3 Platform Services — PostgreSQL HA, Valkey, object storage
The central finding. OAS defines six canonical dimensions and states that each architecture description MUST use them. Railiance has modelled itself almost entirely on Stack. Everything that did not fit a stack level was treated as an anomaly - "unplaced", "beside the stack" - and accumulated as exceptions. They were never anomalies. They are concerns on dimensions Railiance was not using, and the Quality dimension's sub-levels map almost one-to-one onto the capability gaps this review found independently: Q2 Observability is railiance-telemetry, named in canon in exactly those words; Q7 Governance is the conformance loop; Q3 is restore proof; Q6 is cost attribution. The self-evidencing thread across five stack layers is five Stack repos each independently asking for Q2 and Q7 - what a missing dimension looks like from inside the one you are using. Also records four contradictions (C1-C4), of which C1 is actionable here: the hub attributes ~11 capabilities to this repo including Terraform, Ansible, k3s, CI/CD and app deployment, which S3 does not own. SCOPE.md declares four, all correctly S3, and is authoritative. ArgoCD decision closed: keep it, documentation stays accurate; relocating GitOps to Helix Forge noted as possible future cleanup. SCOPE.md: corrects the "five independent repos per OAS Stack layer" claim, records the ArgoCD deployment path, the telemetry emission relationship, and the hub capability drift. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude/rules | ||
| .forgejo/workflows | ||
| argocd | ||
| credential-change-requests | ||
| credential-grants | ||
| docs | ||
| helm | ||
| history | ||
| lib | ||
| openbao | ||
| registry | ||
| schemas | ||
| scripts | ||
| tests | ||
| tools | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| .sops.yaml | ||
| AGENTS.md | ||
| ArchitectureBlueprint.md | ||
| CLAUDE.md | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| SCOPE.md | ||
| WORK-RECORDS.md | ||