docs: reachableceo wording sweep per 2026-09-09 direct order

House style: the principal identity is named (reachableceo), never
'the founder'. No behavior change.

https://projects.knownelement.com/issues/942

skills/agent-provisioning/references/cloudron.md

@@ -18,7 +18,7 @@
 - There is NO admin route to reset another user's 2FA (PUT/PATCH/DELETE on
   `/users/<uid>` 2FA variants all 404; the dashboard UI only offers profile
   self-service enrollment). Consequence: TOTP seeds not captured at
-  enrollment are unrecoverable without the founder.
+  enrollment are unrecoverable without reachableceo.
 - Other useful routes seen in the SPA bundle: `/api/v1/tokens`,
   `/api/v1/oidc/clients`, `/api/v1/groups`, `/api/v1/eventlog`,
   `/api/v1/app_passwords`. Verify behavior at runtime before relying on a
@@ -51,10 +51,10 @@ exist (`coo`). Identity emails follow `tsgstaff-<login>@turnsys.com`.
 - Enrollment is profile self-service ONLY. Capture the base32 seed into the
   vault (`sm setfield "<login> Cloudron" totp_seed <seed>`) at enrollment —
   there is no admin reset and no recovery path.
-- Policy RULED (founder, 2026-09-08): TOTP seeds MUST be stored in Bitwarden.
+- Policy RULED (reachableceo, 2026-09-08): TOTP seeds MUST be stored in Bitwarden.
   Enroll 2FA only when the seed is being captured to the vault item in the
   same step. Legacy identities whose seeds were never captured (the whole
-  August batch) are reset-on-sight candidates: founder clears 2FA or hands
+  August batch) are reset-on-sight candidates: reachableceo clears 2FA or hands
   over the seed, then re-enroll with capture.
 
 ---

skills/agent-provisioning/references/incident-log.md

@@ -37,7 +37,7 @@ rabbit hole (see #939 correction).
   password across cloudron+gitea+redmine+discourse, and the stored password
   already fails Cloudron auth (401 tested). Shared passwords are banned
   (#942); treat those items as stale until their owning lane remediates.
-- Several "admin" vault candidates resolved to the founder's personal
+- Several "admin" vault candidates resolved to reachableceo's personal
   reachableceo accounts (gitea id 3, redmine user 5) and none were admin
   (gitea: 403 "user should be the site admin"; redmine: 403 on /users.json).
   They now carry RESTRICTED notes. The compliant Cloudron admin lever is the

skills/agent-provisioning/references/org-chart-update.md

@@ -5,7 +5,7 @@ turn a provisioning change lands:
 
 | Where | What | How |
 |---|---|---|
-| `TSYSGroupCorporate/TSYSGroupAIOS` `agents/global/AGENTS.md` — "Org chart & agent lanes" | THE canonical operational map (every session loads it via symlink) | branch `coo/…` or lane branch → PR → founder merge |
+| `TSYSGroupCorporate/TSYSGroupAIOS` `agents/global/AGENTS.md` — "Org chart & agent lanes" | THE canonical operational map (every session loads it via symlink) | branch `coo/…` or lane branch → PR → reachableceo merge |
 | `reachableceo/org-buildout` `docs/org-chart.md` | The rendered full-group chart (publishable) | same-turn commit |
 | Redmine provisioning ticket | Per-identity state (pw/2FA/seed/systems) | comment with commit URLs |
 

skills/agent-provisioning/references/systems.md

@@ -62,7 +62,7 @@
   the API key is stored in the item's password field.
 - Admin surface: `/users.json` lists users (admin only — 403 otherwise).
   Every admin candidate tested in the vault so far is NON-admin (they are
-  all the founder's personal accounts anyway — RESTRICTED).
+  all reachableceo's personal accounts anyway — RESTRICTED).
 
 ## Shared infrastructure hazard