Designed by Alex Greenshpun
System Architecture

AI Chief of Staff
Architecture

Multi-model, event-driven personal OS with proactive intelligence, layered security, and self-improving behavior.
Click any section for a plain-English explanation.

Command Interfaces

Entry Points

click to explain

Chat + AI Brain

Chat Platforms
WhatsApp Slack Telegram
AI Providers
Claude CLI Codex CLI Gemini CLI
In plain English

You can talk to Miss Chief through messaging apps or AI coding tools. Every message, regardless of where it comes from, flows through the same intelligence and safety pipeline. The system routes your request to the right AI model and responds in the same channel you used.

Defense in Depth

9-Layer Safety Shield

click to explain

Security Layers

1 Killswitch
2 Action Guard
3 Injection Scanner
4 Output Sanitizer
5 Unicode Safety
6 Security Profiles
7 Chat Isolation
8 Exfil Guard
9 Code Forensics
T0Silent Read
T1Auto + Log
T2Draft + Notify
T3Explicit OK
Every action passes through the guard before execution. Fail-closed: if the system cannot verify safety, it blocks.
Repo Forensics: 19-scanner security gate that audits code before it touches your machine
In plain English

Before the AI does anything, every action passes through 9 layers of security. A killswitch enforces hard limits on message rates and allowed hours. An injection scanner detects manipulation attempts. An output sanitizer strips secrets. Different security profiles apply depending on who the AI is talking to. Chat isolation prevents data leaking between conversations. Actions are classified into 4 approval tiers, from silent reads to explicit human approval.

Event-Driven Lifecycle

Lifecycle Hooks

click to explain

Session Timeline

SessionStart
UserPrompt
PostToolUse
PreCompact
SessionEnd

12+ hooks across the full lifecycle. Self-correcting: captures patterns, corrections, and context automatically at every stage.

In plain English

The system hooks into every phase of a conversation. When a session starts, it loads memory and personality. Before each message, it checks for triggers and loads relevant data. After tools run, it tracks changes. Before context compression, it snapshots critical data. When the session ends, it extracts a structured summary for future recall.

Core Systems

Data, Intelligence, Skills

click to explain Data Layer

15+ Integrations

WhatsApp R/W
Gmail R/W
Calendar Multi
Slack R/W
Telegram R/W
Google Drive
YouTube
Reddit
Web Search
CRM R/W
Fireflies
click to explain Intelligence Core

Memory + Intelligence

Three-Layer Memory

Session memory with semantic + temporal search, knowledge graph for entities and relations, semantic memory for learnings and habits.

Proactive Intelligence

Two-tier heartbeat: silent scan, narrative only on critical. Multi-agent monitoring with event-driven triggers.

Behavioral Corrections

Auto-extracts NEVER/ALWAYS rules. Model-agnostic across all providers. Nightly eval, fix, verify, keep or rollback.

Total Recall: proactive, persistent memory layer for AI agents
click to explain Capabilities

50+ Skills

Briefing & Orientation
Content Pipeline
Client Intelligence
Deep Research
System Health
Development
In plain English

The system connects to 15+ services to stay informed. It reads and writes WhatsApp, Gmail, Slack. It syncs calendars, pulls meeting transcripts, researches across YouTube, Reddit, and web search. All data synced in parallel before every briefing, so the AI reasons on fresh information.

In plain English

Three memory systems working together. Session memory remembers every conversation, searchable at 50:1 compression. A knowledge graph tracks people and projects. Semantic memory stores behavioral patterns. The corrections engine learns from mistakes and proposes permanent system changes when the same issue recurs.

In plain English

Skills are modular capabilities the AI can use. Morning and evening skills run daily briefings automatically. Content skills manage a publishing pipeline. Research skills dispatch multiple agents in parallel. Skills can be invoked manually, triggered by automation, or activated proactively when the AI detects they are needed.

Autonomous Systems

Heartbeat, Routing, Improvement

click to explain Multi-Agent Heartbeat

Silent Watchdogs

Ops
Content
Pipeline

Silent by default. Zero LLM on normal runs. Haiku-narrated alerts only when something genuinely matters.

click to explain Multi-Model Orchestration

Auto Failover

Claude Codex Gemini

Cost-aware routing. Output enforcement strips AI patterns before delivery. WhatsApp, Slack, Telegram, Email, Drive.

click to explain Overnight Improvement

Self-Improving Engine

Eval Pick Worst AI Fix Re-eval Keep/Roll

External model as judge. Budget-capped at 5 iterations. Rollback-safe.

In plain English

Three watchdogs running in the background. One monitors operations (urgent emails, calendar conflicts). Another watches the content pipeline (posting gaps, deadlines). A third tracks sales (invoices, payment signals). They stay silent unless something needs attention. No "all clear" noise, ever.

In plain English

The system uses multiple AI providers and automatically fails over between them. Cheap models handle triage and data collection. Full-powered models handle reasoning and synthesis. Before any response is sent, a validator strips AI-sounding patterns. The same behavioral corrections apply regardless of which provider generated the response.

In plain English

Every night, the system evaluates its own performance across system health, output quality, and interaction quality. It finds the worst-performing area, takes a snapshot, attempts a fix, then re-evaluates. If scores improved, the change stays. If not, it rolls back to the snapshot.

End-to-End Message Flow

Message Pipeline

click to explain

Incoming Message Flow

Message In Unicode Strip Injection Scan Security Profile AI Reasoning Output Sanitize Delivery
Echo loop prevention Cross-chat lockdown Rate limiting IPC token auth Fail-closed
In plain English

When a message arrives, it goes through a strict pipeline before the AI ever sees it. Invisible Unicode characters are stripped. A prompt injection scanner checks for manipulation. A security profile is selected based on who is talking. Only then does the AI process the message. Before the response goes out, an output sanitizer strips any exposed secrets, API keys, or file paths. If any step fails, the message is blocked.