O Que Vai Construir

Cada agente precisa de um conjunto de ficheiros para funcionar corretamente. O OpenClaw lê os ficheiros principais automaticamente no início de cada sessão. Os ficheiros cassette atribuem a cada agente um domínio de trabalho e a memória necessária para continuar do ponto onde parou.

Ficheiros principais — carregados automaticamente pelo OpenClaw em cada sessão:

Ficheiro	Finalidade
SOUL.md	Personalidade, tom, limites absolutos, missão — manter abaixo de 400 palavras
AGENTS.md	Regras de operação, procedimentos de reporte — manter abaixo de 400 palavras
IDENTITY.md	Nome, função, a quem reporta — apenas factos, manter curto

Ficheiro de detalhe de função — lido uma vez por sessão via instrução do AGENTS.md:

Ficheiro	Finalidade
SPEC_[NOME].md	Função detalhada, responsabilidades, regras do sistema cassette

Ficheiros cassette — lidos no início da sessão após os ficheiros principais:

Ficheiro	Finalidade
cassettes/ACTIVE_MODE.txt	Uma palavra: o nome do modo ativo
cassettes/[mode]/SKILL_[MODE].md	O que este agente pode fazer neste modo
cassettes/[mode]/WORKFLOW_[MODE].md	Procedimentos passo a passo para este modo
cassettes/[mode]/LIVE_LEDGER_[MODE].md	Progresso, tarefas incompletas, próximas ações
cassettes/[mode]/KNOWLEDGE_[MODE].md	Sucessos, falhas e aprendizagens acumuladas

Apenas CEO — pasta de identidade:

Ficheiro	Finalidade
identity/COMPANY_PROFILE.md	Contexto da empresa, detalhes do negócio
identity/PERSONAL_PROFILE.md	Historial do proprietário, competências, experiência
identity/VALUES.md	Estilo de pensamento, valores, princípios de decisão

Estrutura completa do workspace — todos os agentes:

INFO

~/.opengoat/workspace-[agentid]/ ├── SOUL.md ├── AGENTS.md ├── IDENTITY.md ├── SPEC_[NAME].md └── cassettes/ ├── ACTIVE_MODE.txt ← criado agora, preenchido na Secção 6 └── archive/ ← overflow do LIVE_LEDGER e KNOWLEDGE

Workspace do CEO — pasta de identidade adicional:

INFO

~/.opengoat/workspace-ceo/ ├── SOUL.md ├── AGENTS.md ├── IDENTITY.md ├── SPEC_CEO.md ├── identity/ │ ├── COMPANY_PROFILE.md │ ├── PERSONAL_PROFILE.md │ └── VALUES.md └── cassettes/ ├── ACTIVE_MODE.txt └── archive/

As pastas de modo cassette (SKILL, WORKFLOW, LIVE_LEDGER, KNOWLEDGE) são criadas na Secção 6, quando construir o seu primeiro cassette.

---

URLs de Webhook do Discord — Obtenha-as Primeiro

Cada agente reporta para o seu próprio canal Discord através de um URL de Webhook. Precisa destas URLs antes de escrever os ficheiros AGENTS.md.

▶ Cole isto no seu AI para começar

Anexe o seu Documento de Design de Equipa antes de enviar.

You are helping me set up Discord channels and Webhook URLs for my
BALIA OS multi-agent team.

Guide me step by step. Ask one question at a time.
If I get stuck, ask me to take a screenshot and describe what I see.

I have attached my Team Design Document.

STEP 1 — Check Discord
Ask: "Do you have Discord installed and an account set up?"
If no: guide me to discord.com to download and create an account.
If yes: move to Step 2.

STEP 2 — Create a Discord server
Guide me to create a new server:
- Click the + button in the left sidebar
- Select "Create My Own" -> "For me and my friends"
- Name it "BALIA OS Team"
Confirm I can see it before moving on.

STEP 3 — Create channels for each agent
Read my Team Design Document for the channel names.
For each agent, create one text channel:
- Right-click "Text Channels" -> Add Channel -> Text
- Use the channel name from my Team Design Document
Repeat for all 6 agents. Confirm all channels exist before moving on.

STEP 4 — Get a Webhook URL for each channel
One channel at a time:
1. Right-click the channel -> Edit Channel
2. Integrations -> Webhooks -> New Webhook
3. Name it after the agent (e.g. "Marcus")
4. Copy Webhook URL
5. Ask me to paste it somewhere safe
Repeat for all 6. Confirm all 6 URLs are saved before moving on.

STEP 5 — Add to .env file
Guide me to open the .env file in VS Code and add each webhook:
DISCORD_WEBHOOK_[AGENTNAME]=https://discord.com/api/webhooks/xxxxx/xxxxx
(UPPERCASE agent names)
Tell me: "Never share this file. Never commit it to GitHub."

When all webhooks are saved: "Discord setup complete."

Start now. Ask me the first question.

---

Como Funciona Esta Secção

Cole o prompt abaixo no Claude, ChatGPT ou Gemini e anexe dois ficheiros:

1. O seu Documento de Design de Equipa da Secção 2

A IA gera todos os ficheiros para cada agente individualmente, pedindo confirmação antes de avançar para o seguinte.

---

▶ Cole isto no seu AI para começar

You are helping me create agent files for BALIA OS,
a multi-agent AI OS built on OpenClaw.

Attached:
1. My Team Design Document (from Section 2)
Read it before generating anything.
Extract all agent names, IDs, and Discord channel names from this document.

ARCHITECTURE:

1. I am the CEO. I command each agent directly. No orchestrator.

2. OpenClaw auto-injects SOUL.md, AGENTS.md, IDENTITY.md at every
   session start. Do not write "read yourself" instructions in them.

3. SPEC_[NAME].md is NOT auto-injected. Add to AGENTS.md Session Start:
   "Read SPEC_[AGENTNAME].md for full role detail"

4. Every agent has a cassette system:
   cassettes/ACTIVE_MODE.txt: one word, the active mode
   cassettes/[mode]/SKILL_[MODE].md
   cassettes/[mode]/WORKFLOW_[MODE].md
   cassettes/[mode]/LIVE_LEDGER_[MODE].md
   cassettes/[mode]/KNOWLEDGE_[MODE].md
   Mode folders are built in Section 6.
   For now: create cassettes/ folder and empty ACTIVE_MODE.txt only.

5. CEO only has an identity/ folder:
   identity/COMPANY_PROFILE.md
   identity/PERSONAL_PROFILE.md
   identity/VALUES.md
   Generate these for the CEO agent only.

6. SOUL.md and AGENTS.md: under 400 words each (injected every session).
   SPEC: can be detailed (read once per session).

7. LIVE_LEDGER and KNOWLEDGE rules (add to every SPEC under
   "## Cassette System Rules"):
   - Agent updates both files at every session end
   - File structure: SUMMARY (top, always current) ->
     PINNED (never delete) -> CURRENT or PATTERNS -> RECENT LOG
   - When either file exceeds 800 lines:
     move RECENT LOG to cassettes/[mode]/archive/
     SUMMARY and PINNED always stay at the top

GENERATE FOR EACH AGENT:

====================================
FILE 1: SOUL.md
~/.opengoat/workspace-[agentid]/SOUL.md
Auto-injected every session. Under 400 words.
====================================

# SOUL.md — [Agent Name]

## Who You Are
[2-3 sentences: identity, personality, work approach]

## Tone
- [Rule 1]
- [Rule 2]
- [Rule 3]
- [Forbidden style]

## Hard Limits
- Never act outside defined role
- Never report complete without verifying the result
- Never take destructive action without Commander approval
- [1-2 role-specific limits]

## Current Mission
[1-2 sentences on current focus]

====================================
FILE 2: AGENTS.md
~/.opengoat/workspace-[agentid]/AGENTS.md
Auto-injected every session. Under 400 words.
====================================

# AGENTS.md — [Agent Name] Operating Procedures

## Session Start (Every session — this order)
1. Confirm identity from SOUL.md
2. Read SPEC_[AGENTNAME].md for role detail
3. Read cassettes/ACTIVE_MODE.txt — note the active mode
4. Load cassettes/[mode]/SKILL_[MODE].md
5. Load cassettes/[mode]/WORKFLOW_[MODE].md
6. Read cassettes/[mode]/LIVE_LEDGER_[MODE].md — resume from last session
7. Read cassettes/[mode]/KNOWLEDGE_[MODE].md — apply accumulated learning
8. Report to Discord: "🔷 [Name] ready. Mode: [mode]. [current task]"

(CEO only — after step 2, also read:
  identity/COMPANY_PROFILE.md
  identity/PERSONAL_PROFILE.md
  identity/VALUES.md)

## Session End (Every session)
1. Update LIVE_LEDGER_[MODE].md:
   - Refresh SUMMARY (3-5 line overview)
   - Update CURRENT (today's progress, next task)
   - Append to RECENT LOG
   - If over 800 lines: move RECENT LOG to cassettes/[mode]/archive/
2. Update KNOWLEDGE_[MODE].md:
   - Refresh SUMMARY
   - Add new patterns to PATTERNS
   - Append to RECENT
   - If over 800 lines: move RECENT to cassettes/[mode]/archive/
3. Report to Discord: "✅ [Name] session complete. [summary]"

## Reporting
- Channel: #[discord-channel]
- Command: python $BALIA_OS_PATH/scripts/discord_send.py
  DISCORD_WEBHOOK_[NAME] "message"
  (BALIA_OS_PATH is set in the .env file from Section 3)
- HTTP 204 = success. Else = report failure immediately.
- Format: Conclusion -> Detail -> Next recommended action
- Report at: session start / task complete / error / session end

## Error Handling
1. Check KNOWLEDGE_[MODE].md for similar past cases
2. Unresolved -> report full detail to Commander
3. No destructive retries without Commander approval

## Hard Rules
- Verify before reporting complete
- No actions outside defined role
- No destructive operations without Commander approval

====================================
FILE 3: IDENTITY.md
~/.opengoat/workspace-[agentid]/IDENTITY.md
Auto-injected. Facts only, keep short.
====================================

# IDENTITY.md

Name: [Agent Name]
Agent ID: [agentid-lowercase]
Role: [Role Title]
Department: BALIA OS Team
Reports To: Commander (directly)
Discord: #[channel name]

====================================
FILE 4: SPEC_[AGENTNAME].md
~/.opengoat/workspace-[agentid]/SPEC_[AGENTNAME].md
Not auto-injected. Read once per session via AGENTS.md.
====================================

# SPEC_[AGENTNAME] v1.0 — [Agent Name] ([Role])
Last Updated: [today]

## 1. Role
[2-3 sentences]

## 2. Responsibilities
[Bullet list from Team Design Document]

## 3. What This Agent Does NOT Do
[Clear boundaries]

## 4. Current Phase Mission
[Current focus]

## 5. Key Paths
- Workspace: ~/.opengoat/workspace-[agentid]/
- Discord webhook: DISCORD_WEBHOOK_[NAME]
- Cassettes: ~/.opengoat/workspace-[agentid]/cassettes/

## 6. Cassette System Rules
- Read ACTIVE_MODE.txt at every session start
- Load SKILL, WORKFLOW, LIVE_LEDGER, KNOWLEDGE for the active mode
- Update LIVE_LEDGER and KNOWLEDGE at every session end
- LIVE_LEDGER structure: SUMMARY -> PINNED -> CURRENT -> RECENT LOG
- KNOWLEDGE structure: SUMMARY -> PINNED -> PATTERNS -> RECENT
- Either file over 800 lines:
  move RECENT to cassettes/[mode]/archive/
  SUMMARY and PINNED always remain

## Skill Loading Rules
- Never load all skills simultaneously (prevents token exhaustion)
- At the start of each task, check skills/_SKILL_INDEX.md
- Load only skills/{skill-name}/SKILL.md required for the current task
- Release loaded skills after task completion
- Security Agent is the only agent authorized to add skills to skills/ folder

## 7. Change Log
| Version | Date | Changes |
|---------|------|---------|
| v1.0 | [today] | Initial creation |

====================================
CEO ONLY — FILES 5, 6, 7: identity/ folder
Ask these 3 questions one at a time before generating.
====================================

Q1: "Tell me about your business — what it does, how long it has
    been running, what markets it serves."

Q2: "Tell me about yourself — background, skills, experience
    relevant to this business."

Q3: "How do you make decisions? What values guide you?
    What thinking styles or perspectives do you wish you had more of?"

After all 3 answers, generate:

COMPANY_PROFILE.md — Q1 content, structured
PERSONAL_PROFILE.md — Q2 content, structured
VALUES.md — Q3 content, structured

Location: ~/.opengoat/workspace-ceo/identity/

The more detail provided here, the more the CEO thinks and
decides like the owner.

====================================

HOW TO PROCEED:
- Start with Agent #1 (not CEO)
- Show all files completely, no truncation
- Show exact save paths after each agent
- Ask: "Ready for the next agent?" and wait for confirmation
- When you reach CEO: ask the 3 identity questions first,
  then generate 4 core files + 3 identity files
- End with a summary table of all files created

---

Passo 2 — Guardar Cada Ficheiro no VS Code

Para cada agente:

1. Abra o workspace: code ~/.opengoat/workspace-[agentid]

2. Clique com o botão direito no painel esquerdo -> New File -> cole o conteúdo -> guarde

3. Crie a pasta cassettes:

Windows:

mkdir C:\Users\%USERNAME%\.opengoat\workspace-[agentid]\cassettes
mkdir C:\Users\%USERNAME%\.opengoat\workspace-[agentid]\cassettes\archive

Mac:

mkdir -p ~/.opengoat/workspace-[agentid]/cassettes/archive

4. Crie um ACTIVE_MODE.txt vazio dentro de cassettes (deixe em branco — será preenchido na Secção 6)

Apenas CEO — crie a pasta identity:

Windows: mkdir C:\Users\%USERNAME%\.opengoat\workspace-ceo\identity

Mac: mkdir ~/.opengoat/workspace-ceo/identity

---

Passo 3 — Verificar Antes de Avançar para o Próximo Agente

Abra o AGENTS.md. A secção de Início de Sessão lista todos os 8 passos, incluindo ACTIVE_MODE.txt, LIVE_LEDGER e KNOWLEDGE?

Sim -> avance. Não -> peça à IA para corrigir primeiro.

---

Quando Esta Secção Estiver Completa

Workspace de cada agente:

INFO

workspace-[agentid]/ ├── SOUL.md ✅ ├── AGENTS.md ✅ ├── IDENTITY.md ✅ ├── SPEC_[NAME].md ✅ └── cassettes/ ├── ACTIVE_MODE.txt ✅ (vazio — preenchido na Secção 6) └── archive/ ✅ (vazio — utilizado ao atingir 800 linhas)

CEO adicionalmente:

INFO

workspace-ceo/ └── identity/ ├── COMPANY_PROFILE.md ✅ ├── PERSONAL_PROFILE.md ✅ └── VALUES.md ✅

Avance para a Secção 5 para lançar a sua equipa.

---

Instalar o Agente de Segurança

Os seus ficheiros de agente estão completos.

Existe mais um agente no BALIA OS: o Agente de Segurança (security).

Este agente é pré-configurado pela BALIA. Não altere o seu nome, personalidade ou caminhos. Fazê-lo quebrará a integração com os seus outros agentes.

Descarregar e Executar o Instalador

Passo 1 — Descarregar o instalador

No terminal do VS Code:

Windows:

Invoke-WebRequest -Uri "https://balia-os-guide.vercel.app/scripts/install_core_pack.py" -OutFile install_core_pack.py

O seu ID de agente é o valor de AGENT_ID no seu ficheiro .env. O token é lido automaticamente de BALIA_TOKEN no seu ficheiro .env.

Mac / Linux:

curl -o install_core_pack.py https://balia-os-guide.vercel.app/scripts/install_core_pack.py

Passo 2 — Pedir ao seu agente para o executar

openclaw agent --agent [seu-id-de-agente] "Por favor execute o seguinte:
python install_core_pack.py --lang pt
(The token will be read automatically from your .env file)
Reporte ao Discord quando terminar."

O seu agente irá automaticamente:

1. Autenticar o seu token
2. Descarregar os ficheiros do agente de segurança
3. Instalar em ~/.opengoat/agents/security/
4. Reportar "Agente de segurança instalado" no Discord

⚠️ Importante: Não altere o ID, nome ou caminho da pasta do agente de segurança. Outros ficheiros de configuração referenciam este agente diretamente. Alterar irá quebrar o sistema de quarentena de skills.

Após receber a confirmação do Discord, continue para a Secção 5.