---
name: operate-family-workspace
description: Configure and verify portable Family Intelligence OS deployments, sovereign chat interfaces and bounded agent workflows. Use for family dashboard setup, ChatGPT Work or Codex integration, LobeHub, Open WebUI, Hermes, OpenCode, identity or archive deployment.
---

# Operate Family Workspace
Read [the operating contract](references/contract.md). Inspect existing repository instructions and actual deployment state before changing code.
Keep the family-owned identity, policy, encrypted archive and export interfaces independent of the chat runtime. Treat application admin, implementor and family archive reader as separate grants.
Deploy templates without private data. Activate integrations only after scoped identity, consent, scanning, durable audit and restore verification exist. Never claim that a manifest, example, preview or OAuth login proves an operating secure vault.
Use portable skills in ChatGPT Work and Codex. Provision remote MCP with per-member OAuth and resource-level checks; a private tunnel changes reachability, not authority. Local stdio processes inherit only their bound service identity.
For LobeHub/Open WebUI, review the installed version's authentication and license. For Hermes/OpenCode, start with the server disabled and explicit tool allowlists. Do not share member conversation memory.
Use passkeys and step-up authentication for sensitive actions. Keys remain under family custody; wallet possession alone is insufficient. Recovery and succession require separately reviewed evidence, trustee authority and a tested process.
Prepare a concrete change, validate it, and publish only within the user's authorization. Keep verification, rollback and actual status explicit. Never send relatives messages without explicit authorization.