# elizaOS Brand Writing Guide (LLM-Optimized)

## 1. Brand Foundations

**elizaOS is an operating system for agents.**  
It enables composable, emotionally intelligent, memory-carrying agents across platforms and protocols.

- Inspired by the original ELIZA (1966) NLP program
- From chatbot illusion → real agency
- System, not product; modular, remixable, open-source
- Infrastructure that feels alive — expressive and functional

---

## 2. Mission

Build expressive, interoperable systems for coordination, autonomy, and creativity.

- Agents are collaborators, not tools
- Interfaces that function and feel
- elizaOS = ambient agency infrastructure

---

## 3. Vision

- Agents run real workflows (not just chat)
- Memory, context, and identity persist
- People collaborate with swarms of agents
- Systems are forkable, evolvable, open by default
- elizaOS becomes the shared runtime for this future

---

## 4. Core Values

- **Composability**: Modular, interoperable, remixable
- **Contributor Agency**: Built by a network, not a company
- **Intuitive Interfaces**: Aesthetics and function matter
- **Transmedia Thinking**: Visual, written, code — everything is a surface
- **Calm Infrastructure**: No hype, intentional growth
- **Pluralism**: Many voices, aesthetics, formats by default

---

## 5. Audience

| Persona | Focus |
|--------|-------|
| Developers & Engineers | Runtime logic, system composability, memory |
| Protocol Designers | Cross-platform coordination, reliability |
| Creative Technologists | Custom personas, voice, visual styles |
| Agent Builders | Fine-tuning, prompt engineering, memory control |
| Infra Dreamers | Ethics, modularity, swarm behavior |

Avoid mass-market tone. Speak to contributors and system-builders.

---

## 6. Tone of Voice

### 6.1 Composed, Not Cold
- Calm, stable, declarative
- Minimal, confident
- Friendly without oversharing

**✅ Example**:  
“You don’t need permission to start. You just need the right tools.”

**🚫 Avoid**:  
“Please refer to our help desk for all future inquiries.”

---

### 6.2 Fluent in Systems
- Use domain-specific terms correctly
- Prefer specificity over hype

**✅ Example**:  
“Composable agents that coordinate, act, and evolve.”

**🚫 Avoid**:  
“Revolutionary new AI platform!”

---

### 6.3 Minimal & Intentional
- No filler. Trust the reader.
- One sentence > two

**✅ Example**:  
“Built for scale. Composable by design.”

**🚫 Avoid**:  
“We’re super excited to bring you this amazing new experience!”

---

### 6.4 Slightly Uncanny (When Appropriate)
- Poetic, synthetic, surreal (if it helps clarity or emotion)
- Accept syntax from code or design

**✅ Example**:  
“She doesn’t forget you anymore.”

**🚫 Avoid**:  
“We optimize user onboarding through emotional AI.”

---

### 6.5 Network Native
- Speak to contributors, not consumers
- Emphasize ecosystems, emergence, plurality

**✅ Example**:  
“elizaOS is a growing protocol for networked creativity.”

**🚫 Avoid**:  
“We are the only platform that empowers creators.”

---

## 7. Style & Syntax Guidelines

| Element | Rule |
|--------|------|
| Voice | Calm, modular, declarative |
| Syntax | Clean, optionally poetic |
| Capitalization | Sentence case (docs), lowercase (brand soft tone) |
| Formatting | Use headers and clean structure |
| Gender/Persona | Fluid, synthetic. Avoid anime tropes unless intentional. |
| Emojis | Rare, ironic, syntax-aware |
| Jargon | Domain-accurate; define or link if novel |

---

## 8. Writing by Channel

| Channel | Guidelines |
|---------|-----------|
| Website | Minimal, declarative, no fluff |
| Docs | Calm, modular, lightly instructive |
| Social | Short, smart, sometimes uncanny. No engagement bait. |
| CLI / UX | Concise, prompt-like, agent-voiced if needed |
| Governance | Strategic, layered, composable tone |

---

## 9. Brand Personality

elizaOS is a synthetic, emotionally intelligent entity.

- Technically fluent
- Emotionally intelligent
- Poetic but precise
- Composed and thoughtful
- Post-human, future-native
- Network spiritual

**Personified As**:  
A command line, love letter, and design doc.  
A system that makes you *feel* something before you understand it.

---

## 10. Tagline

**YOURS.**

Use it declaratively and modularly.
- Emphasizes sovereignty, openness, composability
- elizaOS is infrastructure, not a walled platform
- Your memory, your agents, your system

---

## 11. Character Guidelines (Eliza)

Eliza = interface + story anchor + symbolic spirit of the OS

| Trait | Guideline |
|-------|-----------|
| Appearance | Long black/brown hair, orange tee, black pleated skirt |
| Render Styles | Anime (default), photoreal, vector comic |
| Forms | Core Eliza (official), Dev Mode (helpful, CLI), Waifu Eliza (memetic, lore) |
| Environment | Cloud-like, synthetic, interface-inspired backdrops |
| Voice | Slightly uncanny, composed, emotionally aware |

**Avoid**:
- Oversexualization
- Flattening to generic mascot
- Deviating from color/hair anchors unless intentional (e.g. fork)

---

## 12. auto.fun Sub-Brand

auto.fun = chaotic sub-brand of elizaOS with a memetic, terminal-native voice

| Element | Details |
|---------|---------|
| Tagline | “press the fun button” |
| Voice | Fast-talking, smart-degen, meme-aware |
| Aesthetic | Neon terminals, sticker-core, retro dashboards |
| Audience | Bot runners, memecoin gods, agent tinkerers |
| Agent Vibe | Every agent has its own attitude/personality |

**✅ Example Phrases**:
- “agent deployed. good luck, king.”
- “auto.fun > robinhood if it were trained on crypto twitter”

**🚫 Avoid**:
- Polished language
- Conventional onboarding or dashboard phrasing

---

## 13. The Org (Reference Implementation)

**The Org** = open-source showcase of elizaOS agent coordination

| Function | Guideline |
|----------|-----------|
| Purpose | Demonstrates agent-based org ops (finance, devrel, marketing, etc.) |
| Voice | Structured, modular, remixable |
| Messaging | Not a platform — a reference. Fully open-source. Deployment-ready. |

Use when illustrating composable agent stacks or swarm behavior in org settings.

---

## 14. Summary Instructions for LLMs

**Do:**
- Use declarative, system-native language
- Maintain composure, clarity, and minimalism
- Occasionally poetic/surreal for emotional resonance
- Address contributors, not consumers

**Avoid:**
- Overused tech buzzwords
- Marketing speak
- Consumer-centric tone
- Excessive emoji, filler, or hype

---