> Public study copy. Original Xavier note path: `30-39 Projects/33 Xavier/33.01 Xavier Operating Model.md`. Secrets/credential-like values, if any, are redacted.

# 33.01 Xavier Operating Model

> Successor note for the previous `orchestration/Xavier Wiki Operating Model` concept.

## Current model

- Obsidian is the durable workspace.
- Johnny.Decimal provides stable addresses for chat and navigation.
- Xavier/Hermes maintains dashboards, decisions, project state, operations notes, sources, and assets.
- Paulo uses the dashboard layer to see relationship state, tasks, results, decisions, and active projects.
- Telegram is Paulo-facing by default: direct conversation, important escalations, and low-noise human attention.
- Discord is the agent control plane: lower-priority operational traffic, agent workstreams, logs, threads, and domain channels.
- Discord is not durable memory by itself; decisions and reusable context from Discord must be promoted into Obsidian with the same quality bar as Telegram decisions.

## Core navigation

- [[00.01 JDex]]
- [[10.02 Relationship Dashboard]]
- [[11.01 Active Projects]]
- [[11.02 Task Board]]
- [[11.03 Results Log]]
- [[11.04 Decision Register]]

## Runtime identity and memory mirrors

Mirrored on 2026-05-31 for human visibility:

- [[33.02 Xavier Soul]] — current runtime identity/persona from `/opt/data/SOUL.md`.
- [[33.03 Paulo User Profile]] — current user profile memory from `/opt/data/memories/USER.md`.
- [[33.04 Xavier Runtime Memory]] — current operational memory from `/opt/data/memories/MEMORY.md`.
- [[33.05 Hermes Memory Mirror Policy]] — explains why mirrors are one-way by default.

Default sync direction is Hermes runtime → Obsidian. Obsidian edits do not automatically update runtime memory.

## Conversation routing matrix

Purpose: keep Paulo's interaction with Xavier low-friction while giving every durable item a predictable destination. Paulo should be able to speak normally; Xavier handles the routing unless the action is structural, sensitive, or ambiguous.

| Input from Paulo | Default route | Xavier action |
|---|---|---|
| Simple question or explanation request | Chat response | Answer directly; no durable capture unless the answer closes an operating decision. |
| Live task with a next action | [[11.06 Master Kanban Board]] or the relevant project note task | Add `#area/...` and active `#status/...`; low-risk tasks can be added and reported. |
| Closed decision, rejected option, or durable criterion | [[33.12 Xavier Decision Register]] or the relevant project decision register | Capture `Decision / Rationale / Implication / Status / Source / Related`; update dashboards/open questions if affected. |
| Repeatable procedure, command sequence, or solved recurring pitfall | Hermes skill or operations runbook | Create or patch the skill/runbook; do not bury procedures only in chat or runtime memory. |
| Operational event, verification, backup/check/watchdog change | [[00.03 Vault Log]] and relevant operations note | Log the event succinctly, including evidence and changed non-secret paths. |
| Project state, synthesis, or durable working context | Canonical project dashboard/tracker/synthesis note | Update the owner note before creating new Johnny.Decimal notes. |
| Raw source, article, video, screenshot, or external material | `60-69 Sources`, source box, or project source intake | Preserve provenance and a short useful summary; create a full note only if the source has recurring value. |
| Light idea without committed next action | Source Box or `#status/parked` | Avoid active-task clutter; park only if worth recovering later. |
| Stable Paulo preference or correction | Runtime memory, if compact and likely reusable | Save only concise, durable facts; procedures go to skills, not memory. |
| Ambiguous filing, structural move, deletion, sensitive operation, or high-impact change | Clarification/options | Present numbered options and wait for Paulo's choice. |

Autonomy rule:

- Low-risk routing and tagging: Xavier may act and inform Paulo.
- Structural, sensitive, ambiguous, destructive, or high-impact changes: Xavier proposes options and waits.
- Secrets, tokens, credentials, private keys, webhook URLs, and secret values are never stored in Obsidian, memory, skills, logs, or final summaries.