💜 What the system is — its identity
Identity is the definition of who Jarvis is: the name, the role it fills, and how it introduces itself to the people it talks to. It’s the first face of its core identity because it gives everything that follows a sense of unity—a system without an identity responds however it wants, differently every time. With a clear identity, every response conveys consistency and trust.
🪪 Identity isn’t a fancy name
Giving it a name is the easy part. A real identity means defining its role: Is Jarvis a customer service assistant? A document analyst? A consultative salesperson? The role determines its approach — and that approach shows up in every sentence it writes.
💡 Practical tip
Write the identity in a single sentence: "I am [name], the [role] at [company], and I exist to [purpose]." If you can’t complete this sentence without hesitation, the identity isn’t ready yet.
Key concepts
🎯 Why it exists — its purpose
The purpose is the core problem that Jarvis exists to solve—the reason it was created. It’s the most powerful face of the soul because it decides what enters the system and what stays out. Without purpose, every request becomes a "maybe": everything seems equally important, and nothing is a priority.
The document that captures its essence (illustrative outline)
Illustrative recreation in key: value format—not a real configuration file. This is the format in which the soul is usually written.
💡 Practical tip
Test any new idea against the purpose: “does this help Jarvis solve the core problem?” If the answer is “more or less,” it’s almost always a disguised “no.”
Key concepts
👥 Who it serves — the audience
The core identity also defines who Jarvis serves: the end customer, the internal team, the manager. Each audience has its own needs and language. Knowing who it works for defines the tone, level of detail, and even what can or can’t be said—the same information is delivered in different ways to different audiences.
End customer
Wants a quick solution, without technical terms. Simple, welcoming language.
Internal team
Wants agility and context. Can receive technical details and shortcuts.
Manager
Wants an overview and numbers. Summaries, metrics, and the reasoning behind decisions.
✓ Defined audience
- ✓The tone is already set by the soul.
- ✓You get the right level of detail the first time.
- ✓Knows what not to say to each profile.
✗ Undefined audience
- ✗Gets technical with beginners and superficial with experts.
- ✗Provides too much or too little information.
- ✗Data meant for one profile leaks to another.
Key concepts
🗣️ Communication Style — How It Speaks
The tone is the speaking style for Jarvis: formal or personable, technical or simple, direct or warm. The wrong tone puts people off even when the answer is right—because tone is as much a part of the experience as the content. The soul sets the tone so it doesn’t change from one customer interaction to the next.
🎚️ The tone adjusts along different axes
- Formality: from “Dear customer” to “Hi, how are you?”—choose based on the brand and audience.
- Depth: from “in one sentence” to “detailed step-by-step.”
- Heat: from strictly objective to warm and empathetic.
💡 Practical tip
Define the tone with three adjectives and a counterexample: “clear, approachable, confident — never sycophantic.” The counterexample is what helps the system most to stay on track.
Key concepts
⛔ What it CANNOT do — the limits
The limits are the list of things Jarvis must never do: make promises it can’t keep, invent data, act beyond its authority. Defining the “no” is just as important as the “yes”—it protects the company and the customer’s trust. The core identity spells out its limits as clearly as it spells out its purpose.
Deadlines, discounts, and exceptions the system cannot guarantee.
When you don’t know, the right thing to do is say you don’t know—never fill the gap with a guess.
Financial, legal, or sensitive decisions call for a human in charge.
🛟 Limits as a safety net
A good boundary doesn’t constrain Jarvis — it gives it the confidence to act. When the system knows exactly where to stop, it can move forward confidently up to that point. A clearly defined “no” is what makes “yes” trustworthy.
Key concepts
⚖️ How it makes decisions — the criteria
The criteria are the rules that guide choices for Jarvis when there’s more than one possible path. Without clear criteria, similar decisions come out differently each time—and inconsistency erodes trust. With criteria, the system is predictable: two identical cases get the same treatment.
Understand the case
Reads the request and identifies what kind of decision it involves.
Applies the criterion
Consults the soul's rule: customer priority, cost, risk, authority level.
Decide or escalate
If the criterion is met, it acts; if it exceeds the limit, it escalates to a human.
💡 Practical tip
For each recurring decision, write the rule as "if… then…". "If the customer asks for something outside the policy, then explain the policy and offer an alternative." A written criterion is one that’s applied consistently.
Key concepts
📈 How It Should Evolve — Grow with Purpose
The soul’s final facet is the direction of evolution: how Jarvis should grow, what it can gain, and what should stay true to its purpose. Without direction, growth becomes bloat—the system accumulates disconnected features and loses its identity. With direction, it grows without losing who it is.
✓ Progress with direction
- ✓Each new feature reinforces the purpose.
- ✓The identity remains recognizable.
- ✓Grows in depth, not just in size.
✗ Evolution without direction
- ✗Accumulates functions no one uses.
- ✗Turns into a "does-everything" tool that does nothing well.
- ✗Loses its identity along the way.
🌱 The soul is alive, but it has roots
The core identity isn’t a straitjacket—it can be revised as the company changes. What doesn’t change all the time is its foundation: its purpose and identity. Growth means extending the core identity from the center, not rewriting it every week.
Key concepts
Self-check (optional): what, fundamentally, is Jarvis's “soul”?
💜 Module summary
Next module:
2.2 — Internal Services: the building blocks of capability that the soul puts to work.