Decide blueprint 5.6 (adopt ArgoCD) and plan phase B adoption on railiance01.

Records the founder's 2026-09-21 decision, read-only diff evidence for the
four Applications, and RPF-WP-0044 (one founder go-ahead per app). Nothing
applied.

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

docs/argocd-gitops.md

@@ -48,7 +48,9 @@ through git.
 What this means for platform review in this repository:
 
 - A merge to `argocd/applications/` is a live production change. Once the
-  commit is on `main`, `railiance-apps-root` syncs it with prune and self-heal.
+  commit is on `main`, `railiance-apps-root` syncs it with prune and self-heal
+  (today on coulombcore; on railiance01 only after RPF-WP-0044 applies the
+  bootstrap).
   Treat the merge as the `APPROVED` gate, not as a draft.
 - A new Application for a workload that is already running is an **adoption**.
   Follow the adoption steps in `workplans/RPF-WP-0043-policy-nexus-argocd-onboarding.md`:
@@ -63,29 +65,23 @@ Application here. Until 2026-12-21 its changes keep `activation=APPROVED` by
 founder plan approval, and each one is recorded as production-tier.
 Onboarding is due by 2026-12-21 (RPF-WP-0043).
 
-**Not verified: that ArgoCD syncs on railiance01.** This repository does not
-show it, and some records point the other way:
+**ArgoCD on railiance01: installed, not yet reconciling anything
+(2026-09-21).** The custodian's read-only check found no ArgoCD on
+railiance01 (namespace and CRDs NotFound; RPF-WP-0043-T01 evidence). The
+founder then decided ArchitectureBlueprint §5.6 as option 1, adopt properly,
+and Argo CD Core v3.5.3 was installed there (phase A). As of this record it
+has 0 AppProjects, 0 Applications and 0 repository Secrets: the bootstrap in
+`argocd/bootstrap/` is **not applied**, so `railiance-apps-root` does not yet
+sync anything on railiance01. The records calling the controller "coulombcore
+ArgoCD" were right about the past; coulombcore's ArgoCD still reads
+`argocd/applications/` until phase C retires it.
 
-- The only record of ArgoCD's health is the RPF-WP-0022 inbox evidence from
-  2026-06: "installed and healthy on `railiance01`", with zero Applications.
-  That is from before the 2026-07-02 naming correction. Until then, "railiance01
-  cluster" often meant coulombcore.
-- The later records in this file and in
-  `argocd/platform-addons/openbao-secretstore/kustomization.yaml` name the
-  ArgoCD that runs these Applications "coulombcore ArgoCD". They say the
-  railiance01 stores are "not managed by coulombcore ArgoCD".
-- Every Application uses `destination.server: https://kubernetes.default.svc`,
-  so it reconciles whichever cluster ArgoCD itself runs in.
-- No evidence file in this repository records a sync of `railiance-apps-root`
-  on railiance01 (92.205.62.239).
-
-Confirming it takes an attended **read-only** check against railiance01, not
-coulombcore: check the node IP, the `argocd` namespace, and the `railiance-apps-root`
-sync and health status, for example `make argocd-status` with a kubeconfig whose
-server is verified to be 92.205.62.239. Record the result as evidence. If ArgoCD
-is not running there, the production row has no working path on railiance01
-yet. Installing ArgoCD belongs to the cluster layer and needs its own go-ahead
-from the founder. This is RPF-WP-0043-T01.
+**Do not apply the bootstrap as committed.** The root app and all four
+children declare `automated` sync with prune and self-heal, so applying it
+would adopt all four live workloads at once. Phase B (`RPF-WP-0044`) first
+neutralises automated sync, then adopts one application at a time, each with
+its own founder go-ahead. Read-only diff evidence:
+`docs/evidence/argocd-phase-b-adoption-diff-2026-09-21.json`.
 
 ## Bootstrap Layout