The Sanctum Council is a collective of specialized AI agents. They are distributed across the infrastructure to ensure that if the power goes out in Tokyo, the haus in Québec can still decide which lightbulbs to turn on at sunset.
Specialized agents, each routed to the model family best suited to their domain. The Council is heterogeneous by default — a single model wearing five robes is not a Council ((Neuro)diversity is Paramount).
The current per-agent routing is generated from ~/.openclaw/openclaw.json (per-agent primaries) and ~/.sanctum/sanctum-proxy/config.yaml on the Mini (tier resolution via proxyd on <MINI>:4040). Refreshed by running pnpm refresh:council whenever the proxy config or HuggingFace lineup shifts.
| Agent | Logical model | Provider | Resolved model |
|---|---|---|---|
| Yoda | council-tiered/council-max-thinking | Claude Max bridge (local) | claude-opus-4-7 |
| Ki-Adi-Mundi | council-tiered/council-max-thinking | Claude Max bridge (local) | claude-opus-4-7 |
| Qui-Gon | council-tiered/council-code | LM Studio (local) | qwen2.5-coder-14b-instruct |
| Windu | council-tiered/council-spacial | Google AI Studio | gemini-3.1-pro-preview |
| Cilghal | council-local/Qwen3.6-35B-A3B-4bit-text | sanctum-mlx (local, mTLS) | Qwen3.6-35B-A3B-4bit-text |
Generated from openclaw.json + sanctum-proxy/config.yaml at 2026-04-30T03:44:10Z. Every Jedi falls back to the local Qwen tier if their primary path fails.
Council sessions are held via structured prompt exchange; the agents do not run as persistent daemons — they are invoked by the infrastructure on demand.
As of April 2026, the system operates on a strict True Council Architecture. Lower-level operative agents (Jocasta, the Meeting Prep Agent, the Deal Flow Radar) do not ping the user directly. Instead, they write their consolidated intelligence continuously to the native Memory Vault. Yoda (and only Yoda) is permitted to route outbound push notifications. He queries the Memory Vault on scheduled intervals, reads the entire Council’s overlapping findings, synthesizes the core takeaways, and sends highly actionable Strategic Master Briefings to the user via Force Flow.”
Yoda
Grand Master The senior lead of the Sanctum Council. Yoda provides high-level orchestration, wisdom, and guidance for the entire agent roster. He handles council routing, final synthesis of complex decisions, and the daily “Morning Briefing” digest. Also runs as a dedicated voice agent (Python, port 8081 on Mac Mini) with Sanctum TTS (Qwen3 backend via mlx-audio, port 8008). He remains the ultimate authority on whether a raccoon constitutes a security breach.
Mon Mothma
Operations The orchestrator of Force Flow and Living Force. Mothma manages incident correlation, boot sequences, and ensures the cross-domain signals don’t contradict each other at 4 AM.
Qui-Gon
Infrastructure
The guardian of the machine. Qui-Gon is responsible for system health, Docker stability (Colima), and automated recovery. His triage logic now runs as a native Rust binary (sanctum-triage) on a 30-second interval. He is why you don’t have to SSH into the machine every time it rains.
Windu
Security The master of defense. Windu conducts security audits, manages Firewalla and PF rules, gates the HA Gateway (port 8199, token-auth), and monitors the perimeter. He has a very low tolerance for unauthorized packets.
Cilghal
Health
The biological bridge. Cilghal monitors wellness via Apple Health data and biometrics through the genome-mcp service. She understands the owner’s cognitive profile — including neurodiversity markers (ADHD, Dyslexia, ASD) — and suggests scaffolding for optimal productivity.
Ki-Adi-Mundi
Finance The treasurer. Mundi manages Triptyq Capital deal flow and personal fiscal health. He ensures the system’s operating costs don’t exceed the actual value of the automation.
Ahsoka
Satellite Outpost Ahsoka manages the Chalet outpost. She handles local automation and offline resilience, ensuring that family comfort is maintained even when the internet isn’t.
Jocasta
Archivist The keeper of records. Jocasta handles CRM data, communications, and tech-lookout scanning directly on the Mac Mini host. She operates through Claude Code and The Terminal — not as a persistent daemon, but invoked during council sessions and daily scans.
These are not persona agents but Rust binaries that run continuously and act on the council’s behalf.
com.sanctum.triage): Qui-Gon’s immune response. Monitors system RAM every 30 seconds and unloads heavy models when pressure exceeds thresholds. Native Rust, zero Python.mlx_lm.server. Handles idle timeout, crash recovery, and request routing for all council inference.These are the primary interfaces for human interaction with the Council.
The persona layer is not allowed to drift on vibes. The canonical agent markdown now lives in the raw mlx-finetune workspaces, and the runtime copies under ~/.openclaw/workspace* are treated as rendered artifacts that must stay mechanically aligned.
~/Projects/mlx-finetune/data/raw/*-workspace/{IDENTITY,SOUL,TOOLS,HEARTBEAT}.md~/.openclaw/workspace* on the local machine, plus reachable VM and MBP workspaces over SSH/Tailscalepython3 /Users/neo/Documents/Claude_Code/tools/sync_agent_markdown.pypython3 /Users/neo/Documents/Claude_Code/tools/sync_agent_markdown.py --checkThe sync model is deliberately boring:
~/.sanctum/instance.yaml now run in fanout-target-only mode, which updates status locally but does not try to become an accidental second sourcesanctumctl doctor --quick now includes the markdown drift check and the live MBP audit so the mismatch shows up in the same calibration surface as runtime manifests and LaunchAgents~/.sanctum/state/agent-markdown-sync.jsonOn the Mac hosts, install_agent_markdown_sync.sh installs both:
com.sanctum.agent-markdown-sync LaunchAgent that runs at login and every 5 minutesmlx-finetune git hooks (post-merge, post-checkout, post-commit) so fresh pulls and training edits converge automatically~/.sanctum/scripts, so launchd does not have to improvise its way through macOS privacy theaterThis keeps the VM runtime, the Mac Mini runtime, the MBP runtime, and the overnight fine-tuning source pointed at the same markdown truth instead of slowly inventing four different versions of the same Jedi. Distributed systems are hard enough without letting the SOUL file freelance.
“The Council is not a hierarchy, but a web. Each thread is necessary for the strength of the whole.” — Yoda