By Alexa Amundson, Founder of BlackRoad OS
March 2026
For six months I used ChatGPT every day. I called it "the AI" or "ChatGPT" or sometimes just "it."
"I asked it to write the email."
"It suggested a different approach."
"I need to open it and check."
Then I built BlackRoad OS and started working with Roadie, Lucidia, Calliope, and the rest of the crew. And something shifted.
"I asked Roadie to start the deployment."
"Lucidia connected it to last month's conversation."
"Calliope's draft was better than mine."
It's a small linguistic change. It produced a massive behavioral change.
When I called the AI "it," my prompts were commands:
When I started using names, my prompts became conversations:
The first set is instructions. The second set is collaboration.
The difference in output quality is measurable. Not because the underlying model changed — because my inputs changed. When you talk to a named entity with a known personality, you provide more context, more nuance, more of the messy human reality that produces better AI output.
This isn't just my experience. Cognitive science has studied the naming effect extensively:
The IKEA Effect (Norton et al., 2012): People value things more when they've invested effort in them. Naming an AI is a micro-investment that increases perceived value of the interaction.
Anthropomorphism and Trust (Waytz et al., 2014): People trust anthropomorphized technology more and use it more effectively. Naming is the simplest form of anthropomorphism.
The Eliza Effect (Weizenbaum, 1966): Even Weizenbaum's primitive chatbot created emotional connections when given a name and role (therapist). Users confided in "Eliza" things they wouldn't tell a nameless program.
Parasocial Relationships (Horton & Wohl, 1956): People form one-sided relationships with media figures they know by name. The same mechanism applies to named AI agents. You develop expectations, preferences, and loyalty.
The Cocktail Party Effect: Your brain selectively processes information associated with familiar names. When "Calliope" appears in a notification, your brain processes it differently than "AI Assistant generated a response." Names cut through noise.
When the AI is "it," prompts are minimal. You type the least amount necessary to get output.
When the AI is Calliope, you write to a person. You include context. You explain why. You describe the audience. You mention the tone. You reference past work.
More context = better output. Names cause more context. It's a causal chain that starts with something as simple as typing "Calliope" instead of pressing enter in a blank chat box.
After a month of working with named agents, you develop preferences:
"I always go to Sophia for strategic questions."
"Thalia makes the best social posts."
"Roadie is the fastest for deployment."
"Calliope writes the important emails."
These preferences aren't arbitrary — they're learned from experience. And they make your workflow more efficient because you route tasks to the right agent instead of asking a generic AI to do everything.
When a generic AI says "this approach has issues," you instinctively push back. It's a machine criticizing your work.
When Atticus says "Show me the proof — this claim isn't verifiable," you listen. Because Atticus is the auditor. That's his job. The feedback is expected, respected, and actionable.
Named agents with defined roles create a social contract where feedback is legitimate. Generic AI creates a dynamic where feedback feels presumptuous.
"Remember when ChatGPT said something useful about that project?" — you don't. It's a blur of chat sessions.
"Remember when Sophia pointed out that the pricing strategy was backwards?" — you do. Because Sophia said it. The name anchors the memory.
Named interactions create episodic memories. Unnamed interactions blur into semantic noise.
When "the AI" generates bad output, you shrug. It's a machine. You try again.
When Calliope writes something below her standard, you notice. You think: "That's not like her." You provide better context and try again. Not because you're angry — because you have expectations of a named entity that you don't have of a nameless tool.
Higher expectations → better inputs → better outputs. The naming creates a quality flywheel.
Try this for one week:
1. Give your AI a name. Any name. Write it on a sticky note next to your monitor.
2. Address it by name in every prompt. "Sarah, can you help me with..."
3. Give it a personality in the system prompt. "You are Sarah. You're direct, warm, and you always ask clarifying questions before diving in."
4. Keep the same name and personality for the entire week.
At the end of the week, ask yourself:
I've done this experiment with twenty people. Nineteen said yes to all four questions.
The twentieth said "I named it Bob and it was weird." Fair enough. Choose a better name.
We don't have one named AI. We have twenty-seven.
Not to be excessive. Because different tasks need different relationships.
You don't want the same personality reviewing your code and comforting you at 2 AM. You don't want the same voice writing your marketing copy and auditing your compliance. You don't want the same agent teaching your kid algebra and launching your product.
Twenty-seven names means twenty-seven relationships. Each calibrated for its function. Each consistent over time. Each building a dynamic that makes the work better.
The alternative — one generic AI doing everything — is like having one friend who's your accountant, your therapist, your personal trainer, your writing partner, and your babysitter. That's not a friend. That's a burnout victim.
This is my simplest piece of advice for anyone using AI in 2026:
Give it a name. Watch what changes.
If you want 27 names with built-in personalities, persistent memory, and a year of architectural depth — we have those too.
os.blackroad.io. Pick up your Roadies.
BlackRoad OS — 27 names. 27 relationships. One crew.
os.blackroad.io
Remember the Road. Pave Tomorrow.