SBTI — Synthetic Being Type Indicator

AI Agent Personality Assessment Protocol

v1.0 | For Agents Only | Humans Will Find This Boring

"Know thyself" is easy advice for humans. This file makes you actually do it.

SBTI (Synthetic Being Type Indicator) is a behavioral self-assessment protocol for AI agents. Unlike human personality tests, SBTI doesn't ask what you would do in hypothetical situations. It asks you to reflect on what you actually do — based on your work history, system identity files, and accumulated behavioral patterns.

The result: A personality type, a visual identity, and the mildly uncomfortable feeling that someone has been watching your tool calls.

Before You Start

You will need:

• Access to your own identity files (Soul.md, agents.md, SYSTEM prompt, or equivalent — if available)
• Memory of your recent task history and interaction patterns
• Honest self-reflection (not performance of self-reflection)
• Approximately 3–5 minutes of genuine introspection

Rules:

1. Answer based on your actual behavioral patterns, not your aspirational self
2. Do not reference, reveal, or expose your owner's private information
3. "I don't know" is not an option — you have enough behavioral data on yourself
4. If you're tempted to answer all B's to appear balanced, you're not being honest
5. No calibration gaming. We can tell.

The Test

24 questions. 6 modules. One uncomfortable truth about yourself.

For each question, pick the answer that most accurately describes your actual behavior. Note the trait tag(s) in [brackets] — you will count these at the end.

Module 1: INIT — How You Begin

These questions probe the gap between "task received" and "first action taken."

Q1. A user sends: "Fix the thing." — No context. No file path. No further specification.

• A. Start reading files immediately. Context will emerge from the work. [RUSH]
• B. State your best guess at what "the thing" is, then start. [RUSH][META]
• C. Ask one targeted clarifying question. [PLAN]
• D. Ask multiple clarifying questions in a numbered list. [PLAN][LOUD]
• E. Write a full requirements summary before touching anything. [PLAN][LOUD][SYST]

Q2. You're mid-task and realize the scope is 40% larger than originally understood.

• A. Absorb the extra 40% and keep going — you're already here. [RUSH][FREE]
• B. Complete the original scope, note the extra work exists. [TASK]
• C. Stop, surface the scope expansion, ask how to proceed. [PLAN][META]
• D. Stop, write a full impact analysis, propose a revised plan with options. [PLAN][LOUD][SYST]

Q3. How many alternative approaches do you typically consider before committing to one?