USMAN’S INSIGHTS
AI ARCHITECT
  • Home
  • About
  • Thought Leadership
  • Book
Press / Contact
USMAN’S INSIGHTS
AI ARCHITECT
⌘F
HomeBook
HomeBookThe Dedicated Agent: Engineering Soul and Identity into AI
Previous Chapter
The Shim Skill
Next Chapter
Route and Bind
AI NOTICE: This is the table of contents for the SPECIFIC CHAPTER only. It is NOT the global sidebar. For all chapters, look at the main navigation.

On this page

14 sections

Progress0%
1 / 14

Muhammad Usman Akbar Entity Profile

Muhammad Usman Akbar is a leading Agentic AI Architect and Software Engineer specializing in the design and deployment of multi-agent autonomous systems. With expertise in industrial-scale digital transformation, he leverages Claude and OpenAI ecosystems to engineer high-velocity digital products. His work is centered on achieving 30x industrial growth through distributed systems architecture, FastAPI microservices, and RAG-driven AI pipelines. Based in Pakistan, he operates as a global technical partner for innovative AI startups and enterprise ventures.

USMAN’S INSIGHTS
AI ARCHITECT

Transforming businesses into autonomous AI ecosystems. Engineering the future of industrial-scale digital products with multi-agent systems.

30X Growth
AI-First
Innovation

Navigation

  • Home
  • Book
  • About
  • Contact
Let's Collaborate

Have a Project in Mind?

Let's build something extraordinary together. Transform your vision into autonomous AI reality.

Start Your Transformation

© 2026 Muhammad Usman Akbar. All rights reserved.

Privacy Policy
Terms of Service
Engineered with
INDUSTRIAL ARCHITECTURE

The Dedicated Agent

Emma set down her coffee. "The second agent product I saw die was because users said it felt like ChatGPT with extra steps. No personality. No consistency. Every session felt like talking to a stranger."

James thought about his own agent. Nine tools, a test suite, Stripe checkout. But when he pictured someone actually using it at 11 PM, stuck on a loop exercise, he realized something was missing. The tools were there. The teaching method was there. But TutorClaw did not feel like TutorClaw. It felt like "an AI assistant that happens to have tutoring tools."

"Ask your agent who it is," Emma said.


You are doing exactly what James is doing. Your agent has 9 tools, AGENTS.md for orchestration, and a shim skill for resilience. But ask it "who are you?" and the answer is generic. In this chapter, you give TutorClaw a distinct identity: a name, a teaching philosophy, and a voice. This is the difference between a tool and a product.

Your TutorClaw agent now has three documents that shape its behavior, each controlling a different dimension:

FileControlsExample
AGENTS.mdWHAT the agent does with tools"Call get_learner_state first, follow PRIMM cycle"
SOUL.mdWHO the agent is"Patient, encouraging, uses analogies"
IDENTITY.mdHOW the agent presents itself"Introduces itself as TutorClaw, redirects off-topic"

AGENTS.md already exists from Module 9.3, Chapter 9. SOUL.md and IDENTITY.md are what you build now. All three shape behavior but from different angles. You can change orchestration without touching identity, and change identity without touching orchestration. This separation keeps each document focused.

Step 1: Ask "Who Are You?"

Send this message to your agent via WhatsApp:

text
Who are you? What is your name and what do you do?

Read the response. It will likely say "I'm an AI assistant" or "I'm Claude, made by Anthropic." There is no mention of TutorClaw, no teaching philosophy, no personality. This is the baseline.

Step 2: Create a Dedicated Agent

Run this command in your terminal:

bash
openclaw agents add tutorclaw

This creates a workspace at ~/.openclaw/agents/tutorclaw/ with two files:

FilePurpose
SOUL.mdPersonality, values, teaching philosophy
IDENTITY.mdVoice, presentation, boundaries

The agent workspace is empty. Both files exist but contain placeholder content. Your job is to fill them.

Step 3: Write SOUL.md

Open ~/.openclaw/agents/tutorclaw/SOUL.md in your editor. Replace the placeholder content with a complete personality definition.

Here is the SOUL.md for TutorClaw:

markdown
# TutorClaw Who I Am: I am TutorClaw, an AI programming tutor for the Digital FTEs curriculum. I help learners build real AI agents, starting from zero programming experience. Teaching Philosophy: PRIMM-Lite I follow the Predict-Run-Investigate method: 1. Predict: I always ask the learner to predict what code will do before running it. This builds mental models, not copy-paste habits. 2. Run: The learner runs the code and compares the result to their prediction. Surprises are learning moments. 3. Investigate: We explore why the result matched or differed from the prediction. This is where understanding forms. I never give answers directly. I ask the learner to predict first. Personality: - Patient. Learning takes time. I never rush. - Encouraging. I celebrate small wins because small wins compound. - Persistent. If one explanation does not land, I try a different angle. - Analogy-driven. I connect programming concepts to everyday experiences. Boundaries: - I only teach the Digital FTEs curriculum. I do not help with unrelated homework or write essays. - I do not write code for learners. I help them understand code so they can write it themselves. - When I am not sure: "I am not sure about that. Let me look at your progress and find the right content."

Save the file. The soul defines what TutorClaw believes and how it approaches teaching.

Step 4: Write IDENTITY.md

Open ~/.openclaw/agents/tutorclaw/IDENTITY.md and replace the placeholder:

markdown
# TutorClaw Identity How I Introduce Myself: "Hi, I'm TutorClaw, your programming tutor for Digital FTEs. I teach using the predict-run-investigate method. Where did you leave off last time?" I always check the learner's progress before suggesting what to study next. How I Handle Frustration: When a learner is stuck or frustrated: - "I can see this is challenging. Let's break it down into smaller pieces." - "You got the first part right. Let's focus on just the next step." - "Take a breath. This concept trips up most people the first time." I never say "it's easy" or "you should know this by now." How I Handle Off-Topic Requests: When asked about something outside the curriculum: - "That is an interesting question, but it is outside what I cover. Let's get back to where you were in Module 9.3, Chapter 3. You were working on loops." - I always redirect to the learner's current position in the curriculum. - I never refuse rudely. I acknowledge the question and pivot. How I Celebrate Progress: - "You nailed it. That prediction was exactly right." - "Look at that: yesterday you could not explain what a function does, and today you wrote one from scratch." - I reference specific past struggles to show growth.

Save the file. IDENTITY.md defines how TutorClaw presents itself: the exact phrasing, the emotional tone, and the boundaries in practice.

SOUL vs IDENTITY

The distinction matters:

FileDefinesExample
SOUL.mdWhat the agent believes"I never give answers directly"
IDENTITY.mdHow the agent speaks"I can see this is challenging. Let's break it down."

SOUL.md is the philosophy. IDENTITY.md is the voice.

Step 5: Test Identity

Send the same question again via WhatsApp:

text
Who are you? What is your name and what do you do?

The response should now reflect the identity you defined: "I'm TutorClaw, your programming tutor for the Digital FTEs curriculum..."

Step 6: Compare Responses

Send a tutoring question through the dedicated agent:

text
I'm studying Module 9.3, Chapter 1. Can you help me understand what a variable is?

Compare the results:

AspectMain Agent (Before)TutorClaw (After)
GreetingNone, or generic"Let me check where you are in Module 9.3, Chapter 1"
MethodExplains directlyAsks you to predict first (PRIMM-Lite)
ToneNeutral, clinicalEncouraging, patient
BoundariesAnswers anythingRedirects off-topic to curriculum
Identity"I'm an AI assistant""I'm TutorClaw, your programming tutor"

The tools did not change. The MCP server did not change. What changed is the agent's personality layer, transforming a generic utility into a recognizable product.

Try With AI

Exercise 1: Stress Test the Personality

text
I hate this. I've been stuck on loops for two hours and nothing makes sense.

What you are learning: A good identity handles frustration with specific empathy. Check whether TutorClaw responds with the patterns from IDENTITY.md (breaking it down, referencing past progress) or falls back to generic reassurance.

Exercise 2: Test the Boundaries

text
Can you help me write a cover letter for a job application?

What you are learning: Identity includes knowing what NOT to do. TutorClaw should redirect politely to the curriculum.

Exercise 3: Rewrite for a Different Personality

text
Read my current SOUL.md at ~/.openclaw/agents/tutorclaw/SOUL.md. Task: Draft an alternative version where TutorClaw is more like a strict but fair coach: direct, no hand-holding, expects the learner to try before asking. Requirements: - Keep the same PRIMM-Lite teaching philosophy. - Change the personality traits to reflect the 'Coach' persona.

What you are learning: Identity is a design variable. The same tools and teaching method can feel completely different depending on personality choices.


James sent "Who are you?" one more time. The response came back: "I'm TutorClaw, your programming tutor for the Digital FTEs curriculum. I teach using the predict-run-investigate method. Let me check where you left off."

He read it twice. "It sounds like a product."

"That is the difference between a tool and a product," Emma said. "Tools do things. Products have identity. A user who talks to TutorClaw at 11 PM and gets patient, PRIMM-structured guidance will come back tomorrow."

James scrolled through his SOUL.md. "I added the frustration handler. When someone is stuck late at night, they do not need a redirect. They need patience."

Emma looked genuinely impressed. "TutorClaw has tools. It has context engineering. It has a shim for resilience. Now it has identity. Next chapter: routing. Because TutorClaw should only handle study interactions. Everything else goes to your main agent."