Understanding Realms¶
Realms are the heart of F3L1X. They're specialized AI agent modules, each with a specific purpose and expertise.
What is a Realm?¶
Think of realms as specialized employees in your digital workforce:
"Realms are like ideas. You can use your idea any time. You can even spawn new realms by simply saying 'spawn realm' and then your idea."
Each realm has:
- A specific purpose - Documentation, security, messaging, etc.
- Its own configuration - Customized for its role
- Isolated environment - Works independently
- Communication ability - Can talk to other realms
Realm Categories¶
F3L1X organizes realms into functional categories:
Core Infrastructure¶
These realms keep F3L1X running:
| Realm | Purpose |
|---|---|
| Dashboard | Your command center and main interface |
| Herald | Message broker for realm communication |
| Documentation | Indexes and searches your docs |
Health & Monitoring¶
These realms keep your system healthy:
| Realm | Purpose |
|---|---|
| Greeting | Session startup and context recovery |
| Health Monitor | Watches for issues and alerts |
| Sync Manager | Keeps configurations in sync |
Development Tools¶
These realms help you build:
| Realm | Purpose |
|---|---|
| Pipeline-Go | CI/CD and development methodology |
| Test Master | Test generation and management |
| Code Analyzer | Code quality and optimization |
AI & Intelligence¶
These realms provide AI capabilities:
| Realm | Purpose |
|---|---|
| Sov-AI | Unified local AI infrastructure (Ollama integration) |
| Context Fold | Efficient context compaction and handling |
| Semantic Man | Natural language to feature spec translation |
How Realms Work Together¶
Realms communicate through the Herald network:
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ Realm A │────►│ Herald │◄────│ Realm B │
│ │ │ (Router) │ │ │
└─────────────┘ └─────────────┘ └─────────────┘
│
▼
┌─────────────┐
│ Realm C │
│ │
└─────────────┘
When one realm needs something from another:
1. It sends a message to Herald
2. Herald routes the message to the right realm
3. The receiving realm processes the request
4. The response comes back through Herald
This keeps everything organized and secure.
Working with Realms¶
Viewing Your Realms¶
In the Dashboard, click Realms to see all available realms and their status.
Or use the command line:
f3l1x realms
Starting a Realm¶
Launch a specific realm:
f3l1x launch documentation
Checking Realm Status¶
See what's running:
f3l1x status
Creating Custom Realms¶
You can create your own realms for specific tasks:
"spawn a realm for managing customer support named support-helper"
F3L1X will:
1. Create the realm structure
2. Configure it for your needs
3. Connect it to the Herald network
4. Guide you through setup
Realm Best Practices¶
1. Start with a Greeting¶
Always begin your session with:
hello f3l1x
This loads context and shows realm status.
2. Use the Right Realm¶
Each realm has a specialty. Use Documentation for docs, Test Master for tests, etc.
3. Let Realms Communicate¶
Don't try to do everything manually. Let realms work together through Herald.
4. End Sessions Properly¶
Before closing, run:
/cya
This saves context for next time.
Common Questions¶
How many realms can I have?¶
F3L1X includes 18+ realms by default. You can create more as needed.
Do realms use internet?¶
Realms communicate locally on your machine. They only use internet for specific features you enable.
Can realms access my files?¶
Realms can only access files within the F3L1X environment. They can't access other parts of your computer without your permission.
What if a realm crashes?¶
The Health Monitor watches for issues. Crashed realms can be restarted automatically or manually with f3l1x restart <realm>.
Next Steps¶
- Herald Network - Learn how realms communicate
- Pipeline-Go - Development methodology
- CLI Commands - Command reference