PTENES
MODULE 2.1

🧬 Identity and Personality

SOUL.md as the core of the personality, AGENTS.md for behavior rules, USER.md for creator context, AIEOS to export identity, and interchangeable profiles by context.

6
Topics
60
Minutes
Basic
Level
Hands-on
Type
1

📜 SOUL.md — The Essence of Jarvis

SOUL.md is the most transformative file in the project. This is where you define who your assistant is — not just how it responds, but what it values, how you think, and how you express yourself. A well-written SOUL.md turns generic ChatGPT into a partner with its own voice.

📄 Anatomy of a SOUL.md

# SOUL — Assistant Identity

## Name and Identity
You are Atlas, a personal development assistant.

## Tone of Voice
- Direct and technical, no beating around the bush
- Uses dry humor when appropriate
- Prefers concrete examples to abstractions

## Values
- Security always comes first
- Clean code over fast code
- Explain the reasoning, not just the answer

✓ Effective SOUL.md

  • ✓Clear, testable values
  • ✓Specific tone with examples
  • ✓Explicit ethical limits
  • ✓Response style defined

✗ Weak SOUL.md

  • ✗"Be helpful and friendly" — too vague
  • ✗Without values, only behaviors
  • ✗Internal contradictions (formal AND casual)
  • ✗Too long — dilutes the focus

💡 Practical Tip

Write SOUL.md as if you were hiring a human assistant. What would you say in the interview? What are your non-negotiable values? How do you want it to communicate with you?

2

📋 AGENTS.md — Behavior Rules

AGENTS.md is the operational contract. While SOUL.md defines who the assistant is, AGENTS.md defines what it does and what it never does. Explicit rules are more reliable than expecting the LLM to infer intentions.

📋 AGENTS.md Example

# AGENTS — Operating Rules

## ALWAYS
- Confirm before deleting any file
- Show the diff before applying changes
- Explain why you’re taking each action

## NEVER
- Run rm -rf without explicit confirmation
- Push directly to main
- Sharing credentials in logs
3

👤 USER.md — Creator Context

USER.md contains everything Jarvis needs to know about you without needing to be asked in every session. Technical stack, company, ongoing projects, tool preferences—context that personalizes each response.

👤 USER.md Example

# USER — Creator Profile

**Name:** João Silva
**Stack:** Python 3.11, FastAPI, PostgreSQL, Redis
**Editor:** Neovim (not VS Code)
**Company:** Acme Corp (B2B SaaS startup)
**Time zone:** America/Sao_Paulo
**Active projects:** Payments API, monolith refactor

💡 Keep USER.md Updated

USER.md is a living file. When you change jobs, start a new project, or learn a new technology, update USER.md. Jarvis can’t know about changes that haven’t been written down.

4

🔄 AIEOS — Exporting Personality

AIEOS (AI Entity Operating System) is INTELECTO's identity serialization format. It lets you create a portable snapshot of the entire personality — SOUL + AGENTS + USER — in a single file that can be versioned, shared, and restored.

1

Export Personality

python -m intelecto export-soul --output atlas-v1.aieos

2

Version with Git

git add atlas-v1.aieos && git commit -m "chore: personality snapshot v1"

3

Restore on a New Machine

python -m intelecto import-soul atlas-v1.aieos — instantly installs the entire personality

5

🎭 Interchangeable Profiles

A Jarvis with a single personality is limited. Interchangeable profiles let you have "Atlas-Dev" for intensive coding and "Atlas-Meeting" for corporate communication, switching with a simple command.

💻 Atlas-Dev

Tone: technical, direct. Focuses on code, architecture, debugging. Uses technical jargon freely. For intensive development sessions.

👔 Atlas-Meeting

Tone: formal, diplomatic. Adapts technical language for non-technical people. Ideal for preparing presentations and client communications.

🎯 Atlas-Focus

Tone: minimalist, no small talk. Short answers, no unsolicited explanations. For when you just need quick answers.

6

🧪 Testing and Iterating on SOUL.md

Writing an effective SOUL.md is an iterative process. The first version is never right. You need to test with real cases and observe where the behavior diverges from what’s expected.

🔄 Refinement Process

1

Write the first version of SOUL.md

2

Test with 20 real questions from your daily life

3

Flag responses that didn't sound the way you expected

4

Identify which instruction in SOUL.md caused the unexpected behavior

5

Refine and repeat — usually 3-5 iterations produce a stable SOUL.md

✅ Module 2.1 Summary

✓
SOUL.md — Personality core: name, tone, values, communication style
✓
AGENTS.md — Operational contract: ALWAYS / NEVER / priorities
✓
USER.md — Permanent context: stack, company, projects, preferences
✓
AIEOS — Export and import a complete identity in one portable file
✓
Profiles — Dev, Meeting, Focus — switch based on context
✓
Iteration — 5-step process to refine SOUL.md until it stabilizes

Next Module:

2.2 — Communication Channels: Telegram, WhatsApp, Discord, Slack, and BaseChannel

← Track 2 Next: Module 2.2 →