§ 01
DYLANANDER.COM/OPENCLAW/MULTI-AGENT KIT·v1.0·MIT LICENSED
A 2,000-word manual and the architecture for running multiple businesses through OpenClaw from your phone. Free. MIT. Read-only default. Never overwrites your files.
Free. MIT license. Safe-default install drops the multi-agent reference architecture into a new dylan-ander-openclaw/ subfolder. Your existing SOUL, USER, AGENTS, and MEMORY files are never touched.
§01 · The cost of a single-agent setup
You spun up one agent. It was sharp for one project. The moment you tried to run a second business through it, the same four failure modes showed up. Every single time.
§ The context tax
Personal life, three companies, a newsletter, a fund. Same context window. The agent that just wrote your wife a birthday note is now drafting a board update. It is the wrong model in the wrong voice with the wrong memory.
§ The memory tax
Your kid's school schedule and a client billing dispute sit in the same semantic search index. When you ask "what is happening this week," both surface. Neither is right. Privacy and signal both collapse.
§ The tone tax
Your newsletter persona is dry, sharp, third-person. Your operator persona is short, direct, first-person. Your family persona is warm. One agent collapses all three into one mushy average voice that fits no audience.
§ The drift tax
It is behavior you can't control over time. The thing you trained on Monday quietly mutates by Friday. You stop trusting what the agent will do next. You start checking every output. That is not leverage. That is a junior employee with amnesia.
§02 · What changes after the kit
The kit doesn't replace the underlying model. It gives OpenClaw the multi-agent architecture that distinguishes a useful operator from a flashy assistant.
§ Identity-level multi-agent
Register main, da-content, @jellybee_bot, and more. Each gets its own SOUL.md, MEMORY.md, channel binding, and model. They don't share context. They don't share voice. They don't leak.
§ Iron laws as durable contracts
🚨 IRON LAW formatted lines live in MEMORY.md at the top of the file. They get cached. They don't drift because they're not prompts. They're contracts. The agent reads them first, every session, forever.
§ Cache-boundary memory
A <!-- OPENCLAW_CACHE_BOUNDARY --> marker splits MEMORY.md. Iron laws and durable identity sit above the line and get cached. Daily mutable state sits below. Two different lifetimes. One file.
§ Threads as protocol
48-business-hour SLA. Weekend pauses. Business prefixes on every thread. Monday.com mirror. You don't chase your own task list. The agent reports what slipped and what's next, on a schedule you control.
§02.5 · The architecture
One Mac mini. One phone. Multiple agents. File-based brain. Real channels. Real tools. The diagram below is the actual shape of what's running on the box under my desk while I work from my phone.
Each agent has its own identity, model, channel binding, and memory namespace. The workspace is shared, with the cache boundary protecting durable behavior from session noise.
Projects
4
Personal, content brand, agency, fund. One operator. One phone. Four identities.
Identities
3+
Main agent. Content sub-agent. Bot fleet. Each with its own SOUL, MEMORY, channel, model.
Iron laws
∞
Durable, cached, 🚨-tagged. Survive compaction. Don't drift. Add new ones forever.
Cost
$0
Free forever. MIT license. Fork, modify, redistribute. Credit appreciated, not required.
§03 · What's inside
Everything is reference material. You read it, see what patterns your current setup is missing, adopt what fits. The kit never rewrites your existing identity files.
Session startup order, memory write discipline, red lines, external-vs-internal rules. The contract every agent in the fleet follows every session.
Voice, temperament, work ethic, boundaries. One per agent. The content sub-agent has a different SOUL than the main agent. That's the point.
Name, creature, vibe, emoji, avatar. The agent's metadata as a first-class identity, not a session label.
Reference scaffold for who you are, how you work, what you care about, what your agents should never do without asking.
🚨 IRON LAW format. Cache-boundary marker. Durable above the line, mutable below. Lean. Under 10,000 characters so semantic search stays sharp.
Beehiiv, Google Workspace, Monday.com, Klaviyo, Telegram, Vercel. Per-tool auth, base URLs, common ops. The local cheat sheet.
Silent-by-default check routines. Rotating coverage of email, calendar, mentions, weather. Batched findings. No "all clear" spam.
P0/P1/P2/P3 priority lanes. 48-business-hour SLA. Business prefixes. Monday.com mirror. The agent reports slippage. You don't chase it.
Main agent. Content sub-agent. Each with its own channel binding, model selection, and isolation rules. The org chart, in markdown.
memory/YYYY-MM-DD.md is the raw journal. MEMORY.md is the curated wisdom. Periodic promotion. Bounded growth. Nothing rots.
The operator's daily journal template. Sleep, energy, what shipped, what slipped. One file per day. Surfaced on demand.
The folder where reusable skills live. Each one has a SKILL.md description so the agent picks the right tool for the job.
ARCHITECTURE.md (the 10 differences). MIGRATING-FROM-HERMES.md (step-by-step). MULTI-BUSINESS-SETUP.md (the org chart pattern).
Default (read-only, drops into dylan-ander-openclaw/). Additive (optional scaffolding). Fresh (new workspaces only). Your files are never silently overwritten.
§04 · All 10 architectural differences
Workspace as truth. Identities as first-class. Iron laws as contracts. Memory as cache. Threads as protocol. Skills as infrastructure. Heartbeats over cron. One model per agent. Plus the operational glue: gateway, tunnel, dashboard, ACP coding agents.
§ 01
§ 02
§ 03
§ 04
§ 05
§ 06
§ 07
§ 08
§ 09
§ 10
All 10 covered end to end in docs/ARCHITECTURE.md.
§05 · Patterns from real work
Each one came from a real failure or a real win across four businesses. No theory. No training-doc language. Operator voice throughout.
§ 01.1 · MEMORY
When the operator states a rule, capture it in MEMORY.md under a 🚨 IRON LAW heading with the date and the context that triggered it. Plain paragraphs get skimmed. Iron laws get followed because they're a visual tripwire for your future self.
§ 02.1 · VOICE
Em dashes are an AI tell. The Dylan Ander newsletter persona has been clean for three years and the audience knows it. One em dash in a draft and the brand voice collapses. Replace with a period, a colon, or a sentence break.
§ 03.2 · OUTBOUND
The principal never sends. The EA agent sends on behalf of the principal. Every external message gets routed, contextualized, and tone-checked first. Zero exceptions. The principal's inbox is for reading.
§ 04.3 · RELATIONSHIPS
Anniversaries, birthdays, big client renewals. The agent surfaces them fourteen, seven, and three days out. Not the day of. Not the day before. Lead time is the gift. (Lesson learned from a Mother's Day miss.)
§ 05.4 · ISOLATION
Multi-agent isolation is the feature. The newsletter sub-agent has its own MEMORY.md with editorial guidelines, audience research, brand voice. It does not have access to the operator's family schedule. That separation is a contract, not a setting.
§ 06.2 · THREADS
Every P1 and P2 thread gets a 48-business-hour clock. Weekends and holidays freeze it. The agent reports anything aging out of SLA at the start of every Monday. The operator doesn't chase. The agent does.
§ 07.1 · OUTPUT
The operator reads on a phone 80% of the time. Walls of prose get skipped. Lead with the answer. Three to five bullets max. Headers if it runs long. The agent that writes for desktop loses on mobile every time.
§ 08.3 · HEARTBEATS
Heartbeats run on a schedule. They check email, calendar, mentions, weather on rotation. They speak only if there's signal. "All clear" is silence, not a message. Otherwise you train yourself to mute the channel.
§06 · Install
The default install never touches your existing SOUL, USER, AGENTS, or MEMORY files. Everything lands in a new dylan-ander-openclaw/ subfolder. Your agent reads it and proposes specific patterns to adopt with your approval, rather than rewriting what you have. Inspired by the structure pioneered at openclaw.nik.co.
Downloads the multi-agent architecture, manual, and reference templates into dylan-ander-openclaw/. Your workspace root is never modified. Your agent reads the kit, compares it against your current setup, and suggests incremental patterns to adopt.
Same as default, plus creates empty optional directories: memory/archive/, journal/, threads/, brain/. Still zero edits to your workspace root.
Writes full templates to the workspace root. If you already have SOUL.md or MEMORY.md, they're preserved and new versions land alongside with a .new suffix for manual diff. Only recommended for genuinely fresh setups.
Paste this in any OpenClaw chat. The agent reads the architecture and the migration guide before proposing anything. Every pattern is suggested, not imposed.
§07 · Honest answers
dylan-ander-openclaw/ subfolder inside your existing OpenClaw workspace. Your SOUL.md, USER.md, AGENTS.md, and MEMORY.md are never touched. Even Fresh mode preserves existing files and lands new versions alongside with a .new suffix.~/.openclaw/workspace/. If you don't have it, install OpenClaw first at github.com/openclaw/openclaw, then come back.Get it free
Paste the command. Read the manual. Your agent reads it. Your agent proposes specific multi-agent patterns worth adopting. You approve the ones that fit. Your workspace compounds across every business you run.
GitHub repo ↗ Architecture Migrate from Hermes heatmap.com ↗ billiondollarwebsites.com ↗