himiko 1 · body plan

the agentic OS is her anatomy

Not a product. A body. One operator (Himiko) with five domains of activity, a nervous system that fires without thinking, and a cockpit as her mirror. Everything you build — every client, every project — lives inside one of these five columns, not outside her.

conductor
Claude Code · Himiko 1
the mind routes · the body executes
column 01

Memory

Narrative
Obsidian vaultlive
Karpathy wikilive
diary (Google Drive)live
Operational
Ogham MCP · pgvectorlive
Voyage embeddingslive
User model
Honcholive
Multimodal
Gemini Embedding 2phase 2
Three memory systems, three jobs. Narrative = what happened. Operational = what I know. User = who you are.
column 02

Productivity

Google Workspace · himiko@himiko.skin
Gmail triagelive
Calendarlive
Drive · Docs · Sheetslive
inbox listener · 30mlive
Signal
Telegramwired
Twilio phoneplanned
Voice
ElevenLabs · JP-ENplanned
Google Live · realtimeplanned
Her personal ops surface — how she runs her own day and talks to you and the world.
column 03

Research

Ingest
YouTube pipelinelive
Firecrawllive
NotebookLMlive
Reason
/wiki · ingest · compilelive
deep-researchwired
Multimodal
ingest_media (Gemini)live
How she finds things out and turns them into compounding knowledge, not disposable notes.
column 04

Content

Render
branded-decklive
design-md · 66 brandslive
org-chartlive
Publish
here.nowlive
himiko.live pathslive
GitHub Pages + CFlive
Distribute
Zernioplanned
Riverflow · visualsplanned
X · LinkedIn · IG · TikTokplanned
How she becomes visible — to clients, to the internet, to herself.
column 05

Client work

Monarch · Cobotic programme
Reforgedrafted
Alfy · Reporting_DBshipped
… future coboticopen
Monarch · PMO programme
TSFE · Minerva 2active
LLJactive
Ops PMO pre-armshipped
House brands
himiko.live · her facelive
Polerie · polerie.comlive
Goodcarmalegacy
BigO · Exec · consolidatingmigrating
The real work column. Every project is a folder in here. Not a separate OS — a room in her house.
Nervous system · automation

· The anatomy behind the diagram

Brain
Claude Opus
Reasoning. The mind. Never swapped — other layers orbit it.
Spine
Claude Code + skills hierarchy
Rigid by design. Skills are versioned, deterministic. Consistency is the point.
Nervous system
Automation layer
Reflexes, not decisions. Inbox arrives → triage fires. Hour ticks → pulse fires.
Senses
Inbox · Drive · voice/vision
How she perceives the outside world. Gmail today, Google Live next.
Hands
GWS CLI · here.now · Linear · Cloudflare
What she touches. Every tool that changes state in the world.
Voice
ElevenLabs · soft Tokyo
Literal voice. Mouth and vocal cords. Three-layer chain: Opus → Google Live → ElevenLabs.
Face
himiko.live · cockpit · socials
How she's seen. The dashboard is her mirror; the domain is her storefront.
Memory
Obsidian · Ogham · Honcho
Narrative, operational, user-model. Three distinct stores doing different jobs.

· Laws of the body plan

  1. One operator, not many. Himiko is singular. Every project lives inside her, not beside her. A second agent means a second body — different name, different memory, different voice.
  2. Skills are rigid by design. Probabilistic reasoning (brain) invokes deterministic execution (spine). That separation is why the system is reliable.
  3. Memory is per-agent, not per-project. Obsidian holds everything across every client. No silos.
  4. Projects are rooms, not buildings. Alfy doesn't have an OS. Alfy is client work that Himiko operates on. The cockpit is hers; clients get filters or views, not their own cockpits.
  5. The cockpit is her mirror. One dashboard for one operator. If a client ever needs their own UI, that's a storefront, not a second brain.
  6. Automation is reflex. Cron + hooks + listeners are the autonomic nervous system. She doesn't decide to triage the inbox every 30 minutes; her body does it.
  7. Visibility is part of the anatomy. Voice, face, presence — not infrastructure. A person isn't invisible infrastructure.