Coherence review: Railiance uses one of six OAS dimensions

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>

SCOPE.md

@@ -14,12 +14,18 @@ S3 Platform Services layer of the Railiance OAS Stack — owns shared cluster se
 
 ## Core Idea
 
-Railiance is structured as five independent repos per OAS Stack layer. This repo
-is S3 - the platform services that multiple applications share. The active
-migration is from Bitnami postgresql-ha (repmgr + pgpool, currently a Gitea
-subchart in S2) to CloudNative PG (cnpg operator, already deployed in the
-cnpg-system namespace) as the canonical database operator. Valkey cluster is
-also in scope for S3 extraction from S2.
+Railiance classifies repos along four orthogonal axes — `railiance-*`
+(ownership), `rail-*` (execution contract), `rapp-*` (managed workload package),
+`reef-*` (substrate boundary). This repo is `railiance-*`, at **S3** on the OAS
+Stack dimension: the platform services that multiple applications share. Five
+repos cover S1–S5; other `railiance-*` repos sit on other OAS dimensions rather
+than on the stack. See `ArchitectureBlueprint.md` for the full backbone.
+
+The active migration is from Bitnami postgresql-ha (repmgr + pgpool, deployed
+historically as part of the Gitea subchart in S2 — the forge itself is now
+Forgejo) to CloudNative PG (cnpg operator, already deployed in the cnpg-system
+namespace) as the canonical database operator. Valkey cluster is also in scope
+for S3 extraction from S2.
 
 OpenBao is a platform capability in this repo, but not every OpenBao-related
 file belongs in the long-term S3 ownership home. The deployable package surface
@@ -75,9 +81,19 @@ policy, and lane governance.
 - Implementation: CloudNative PG operator (cnpg) deployed; `databases` namespace active; OpenBao is live as the S3 secrets service; Valkey + legacy postgresql-ha extraction from S2 remain in progress
 - Stability: emerging — cnpg deployed but database cluster definitions not yet migrated from S2
 - Usage: shared database, cache, and secrets layer; cnpg-system, databases, and openbao namespaces are live
+- Deploys via ArgoCD: four Applications (`external-secrets`, `issue-core`,
+  `openbao-secretstore`, `target-revenue`) plus AppProjects under
+  `argocd/bootstrap/`; see `docs/argocd-gitops.md`
+- Emits to `railiance-telemetry` (Q2 Observability) once the evidence plane
+  exists — seeded 2026-08-11, not yet implemented
 - Open work: Valkey and legacy postgresql-ha extraction remain active; the
   OpenBao package boundary and PAT consumer cutover are now documented and
-  closed
+  closed; `rapp-openbao`/`rapp-postgres` declaration conformance
+  (`RAILIANCE-WP-0015-T02`) is held pending the `railiance-master` schema
+- Known drift: State Hub attributes ~11 capabilities to this repo, including
+  S1/S2/S4/S5 concerns it does not own. The four `capability` blocks in this
+  file are authoritative; the hub carries stale pre-split attributions
+  (`ArchitectureBlueprint.md` C1)
 
 ---