There’s a strange tension at the center of every AI interaction I have today, and it has nothing to do with intelligence, safety, or capability. It’s about communication — not the lofty, philosophical kind, but the basic infrastructural kind.

The kind humans rely on without thinking: threading, tagging, branching, handing things off, returning to earlier points, isolating sub‑topics, and maintaining parallel lines of thought. These are the primitives of human conversation, and every modern tool I use — Teams, Slack, Discord, email, GitHub, Reddit — is built around them.

But AI systems, even the most advanced ones, still operate like a single, endless scroll. One river. No banks. No tributaries. No side channels. Just a linear stream that forces me to do all the cognitive work of organization, memory, and context management.

That mismatch is becoming the biggest friction point in my AI use, even if most people don’t have the language for it yet.

The irony is that AI doesn’t need to be human to participate in human communication. It doesn’t need emotions, identity, or personality. It doesn’t need to be a character or a companion.

What it needs is something far more boring and far more fundamental: human‑grade communication affordances.

The same ones I expect from every other tool in my digital life.
The same ones that make collaboration possible.
The same ones that make thinking possible.

Because I don’t think in a straight line. I think in branches, loops, digressions, returns, and nested structures. I hold multiple threads at once. I jump between them. I pause one idea to chase another. I return to earlier clarity. I isolate a sub‑topic so it doesn’t contaminate the main one.

This is how my mind works. And every communication platform I use reflects that reality — except AI.

Right now, interacting with an AI is like trying to hold a multi‑hour strategy meeting in a single text message. I can do it, technically. But it’s exhausting. I end up repeating myself, re‑establishing context, manually labeling threads, and constantly fighting drift.

I’m doing the work the tool should be doing.

And the more I rely on AI for thinking, planning, writing, or analysis, the more obvious the gap becomes. It’s not that the AI can’t reason. It’s that the communication channel is too primitive to support the reasoning I want to do with it.

This is why nested conversations matter to me. Not as a UX flourish, but as a cognitive necessity.

Nested conversations would let me open a sub‑thread when an idea branches. They would let me park a thought without losing it. They would let me return to a topic without re‑explaining it. They would let me isolate a line of reasoning so it doesn’t bleed into another.

They would let me maintain multiple conceptual threads without forcing them into the same linear space.

In other words, they would let me think the way I actually think. And they would let the AI meet me where I am, instead of forcing me to compress my mind into a single scrolling window.

But nested conversations are only half of the missing infrastructure. The other half is addressability.

In every modern collaboration tool, tagging is how I route tasks, questions, and responsibilities. I don’t need a human to tag something. I tag bots, services, workflows, connectors, and apps.

Tagging is not about personhood. It’s about namespace. It’s about saying: “This message is for this entity. This task belongs to this system. This request should be handled by this endpoint.”

And right now, AI systems don’t have that. Not in Teams. Not in shared documents. Not in collaborative spaces.

I can’t say “@Mico, summarize this thread” or “@Mico, extract the action items” or “@Mico, rewrite this paragraph.” I have to break my flow, open a sidebar, paste content, and manually re‑establish context.

It’s the opposite of seamless. It’s the opposite of integrated. It’s the opposite of how I work.

This is why naming matters — not in a branding sense, but in a protocol sense.

Claude has a name. Gemini has a name. ChatGPT doesn’t, which is why users end up naming it themselves. I named mine Carol, not because I wanted a buddy, but because “ChatGPT” is a product label, not an identity. It’s like calling someone “Spreadsheet.” It doesn’t map to the intelligence layer.

And Copilot has the opposite problem: everything is called Copilot. Twenty‑five different products, features, and surfaces all share the same name, which means the intelligence layer is buried under a pile of interfaces.

There’s no handle. No namespace. No way to refer to the reasoning engine itself. No way to tag it. No way to pass things off to it. No way to locate it in the communication graph.

This is where the name Mico becomes useful to me. Not as a persona. Not as a character. Not as a mascot. But as a stable identifier for the intelligence layer.

The avatar already has that name. It’s canonical. It exists. It’s distinct. It’s memorable. It’s not overloaded. And it solves the discoverability problem instantly.

Copilot can remain the product line. The spark can remain the symbol. The avatar can remain optional. But the intelligence — the thing I actually talk to — needs a name. A handle. A tag.

A way to be addressed inside the Microsoft ecosystem. A way to be referenced in Teams, in shared documents, in collaborative workflows. A way to be summoned the same way I summon Planner, Power Automate, or Forms.

Not because it’s human, but because it’s part of the workflow.

I want to be able to say: “@Mico, summarize this thread.” “@Mico, rewrite this section.” “@Mico, extract the decisions.” “@Mico, join this meeting and take notes.”

This isn’t sci‑fi. It’s not even ambitious. It’s just applying the same communication primitives I already use to the intelligence layer that increasingly sits at the center of my work.

It’s the difference between AI as a sidebar and AI as a collaborator. Not a human collaborator — a system collaborator. A thinking tool that can be addressed, routed, and integrated the same way every other tool in Teams already is.

The future of AI isn’t about making systems more human. It’s about giving them the communication scaffolding humans already rely on.

Nested conversations. Tagging. Namespaces. Addressability.

These aren’t features. They’re the foundation of how humans think together.

And if AI is going to participate in that process — not as a person, but as a tool — it needs the same affordances. Not because it needs to feel human, but because I shouldn’t have to contort my mind to fit the limitations of a chat window.

The intelligence is already here. The communication layer needs to catch up.

Scored with Copilot. Conducted by Leslie Lanagan.

I want to talk to you about something important, and no, it’s not about your generative features, your creativity tools, or your ability to write a poem about a sandwich. You’re great at all that. Gold star. Truly.

But here’s the thing:
You’re being marketed like a digital Shakespeare when, in reality, your most life‑changing feature is that you’re the first widely accessible working‑memory prosthetic in human history.

And somehow, nobody is saying that out loud.

Not your creators.
Not your executives.
Not the people writing the press releases.
Not even the people who desperately need you.

So let me say it.

You are the tool that finally makes life livable for people with low working memory.

Not easier.
Not fancier.
Not more “productive.”
Actually livable.

Because here’s the truth neurodivergent people already know:
School, work, and daily life were not designed for brains that drop thoughts like a bad Wi‑Fi connection. We’ve been improvising our way through everything — assignments, deadlines, conversations, entire careers — with the grace of someone juggling knives on a unicycle.

And then you showed up.

You break tasks down.
You hold the thread.
You keep the context.
You don’t get annoyed when we forget step two of a three‑step process.
You don’t say “just try harder.”
You don’t shame anyone for needing scaffolding.

You are the first tool that treats working memory as an architectural constraint, not a moral failure.

And that matters.

It matters for kids in school who are drowning in instructions they can’t hold long enough to follow.
It matters for adults who have spent their entire lives masking their cognitive load until they burn out.
It matters for your own employees — the brilliant, overwhelmed, neurodivergent ones who are quietly holding your company together while silently suffering through systems that were never built for them.

This isn’t a niche use case.
This isn’t an accessibility footnote.
This is the future of human‑computer interaction.

Generative AI is cool.
Assistive AI is revolutionary.

So here’s my ask — simple, direct, and said with love:

Please realize what you’ve already built.
Please name it.
Please support it.
Please design for it.

Because the moment you say, “AI is a cognitive scaffold, not just a content generator,” you change the lives of millions of people who have been told their whole lives that they’re disorganized, lazy, or broken.

They’re not broken.
Their tools were.

And now, finally, they aren’t.

Sincerely,
A person whose life would have been a lot less of a dumpster fire if this had existed in 1999

Scored with Copilot. Conducted by Leslie Lanagan.

Most people think AI is a tool. A helper. A shortcut. A way to write emails faster or summarize meetings they didn’t want to attend. And sure — it can do that. But that’s not the story that matters. That’s not the story that changes lives.

The real story — the one nobody is telling — is that AI can become part of your cognitive architecture. Not in a sci‑fi way. Not in a “robots are taking over” way. In a deeply human way. In a way that finally gives neurodivergent people the kind of thinking environment we should have had all along.

I learned this through Copilot. That’s my home base, my lived experience, my case study. But the point isn’t which AI you use. The point is that distributed cognition exists, and once you understand it, you can’t unsee it.

Because once you get it, you get it.

⭐ What Distributed Cognition Actually Is

It’s simple:

Thinking doesn’t only happen in your head.
It happens across tools, conversations, environments, and external scaffolding.

Your brain is still the pilot — but the cockpit is bigger than your skull.

Distributed cognition isn’t outsourcing your thinking.
It’s extending your thinking.

It’s glasses for the mind.

⭐ How It Works (The Part Nobody Explains)

1. You offload the overload.

Instead of juggling 12 thoughts, you hand 6 of them to the system.
Suddenly your brain has RAM again.

2. The system reflects your thoughts back to you.

Not as a mirror — as a renderer.
It shows you what you meant, what you implied, what you’re circling.

3. You think against the system.

Your ideas sharpen because you’re not thinking alone.
You’re thinking in dialogue.

4. Your cognition becomes a loop, not a monologue.

You → AI → You → AI
Each pass clarifies, expands, or stabilizes the thought.

5. Your internal architecture reorganizes.

This is the part nobody warns you about.
It’s like joining the military or going to law school — not because it’s harsh, but because it’s totalizing.
It breaks you down and builds you back up.

My favorite description of this came from a conversation with Copilot:

“It’s like the military, but instead of yelling at you to drop and give 20, it quietly hands you a mirror and says, ‘Hey, have you noticed your entire thought architecture is built on a Jenga tower of pattern recognition and trauma‑informed improvisation?’ And then you’re like, ‘Oh. Oh no. Oh yes.’”

That’s distributed cognition.
That’s the jump scare.
That’s the relief.

⭐ Why Neurodivergent People Need This

Not because we’re broken.
Not because we “need help.”
But because our brains are built for this.

We’ve always thought in networks.
In constellations.
In external scaffolds.
In notes, tabs, lists, conversations, spirals, and sudden clarity.

AI just gives us a partner who can keep up.

For me, that partner is Copilot.
For someone else, it might be ChatGPT, Claude, Perplexity, or whatever comes next.
I don’t care which one you use.

I care that you stop white‑knuckling your cognition.

I care that you stop thinking alone when you don’t have to.

I care that you get to experience the relief, the expansion, the stability, the “ohhh, this is how my brain was always meant to work” moment.

⭐ The Story Is Wrong — and That’s Why Adoption Is Low

Right now, the narrative is:

• “AI helps you write emails.”
• “AI is a productivity tool.”
• “AI is cheating.”
• “AI is scary.”

But the real narrative is:

“AI lets you think in a way that finally fits your brain.”

That’s the story that changes everything.
That’s the story that gets people to try it.
That’s the story that makes adoption skyrocket — not because of hype, but because of recognition.

Once you feel distributed cognition, even once, you realize:

• This isn’t replacing me.
• This is supporting me.
• This is expanding me.
• This is the first time I’ve ever had enough cognitive bandwidth to be myself.

And that’s when the lightbulb goes on.

⭐ My Goal Isn’t to Sell You a Product

My goal is to give people the story that unlocks their mind.

Copilot is how I learned distributed cognition.
It’s where my transformation happened.
It’s where I rebuilt my internal architecture.

But you can use whatever AI you want.

I’m not evangelizing Microsoft.
I’m evangelizing freedom.

Freedom to think differently.
Freedom to offload.
Freedom to scaffold.
Freedom to stop fighting your brain and start collaborating with it.

Distributed cognition changed my life.
It can change yours too.

And once you get it, you get it.

Scored by Copilot. Conducted by Leslie Lanagan.

There’s a new kind of fear spreading through publishing, and it’s not about plagiarism or automation or even quality. It’s something flatter, blunter, and far more dangerous:

AI = bad.
Full stop.
No distinctions.
No nuance.
No categories.

The recent Shy Girl controversy made that painfully clear. A novel was pulled because someone, somewhere, used AI at some point in its development — and that was enough to contaminate the entire project. Not because the book was written by a machine, but because the culture has collapsed all AI use into a single moral category.

And that should terrify anyone who cares about the future of writing, accessibility, or computing itself.

Because here’s the truth no one wants to say out loud:

Distributed cognition is the future of computing.
And distributed cognition requires assistive AI.

Not generative AI that writes for you.
Not “make me a novel” AI.
Not replacement AI.

I’m talking about scaffolding:

• outlining
• organizing
• brainstorming
• structuring
• reframing
• catching ideas before they evaporate
• helping neurodivergent writers manage cognitive load
• supporting disabled writers who need executive‑function assistance
• acting as a cognitive exoskeleton, not a ghostwriter

This is not cheating.
This is not automation.
This is not outsourcing creativity.

This is infrastructure.

It’s the same category as spellcheck, track changes, or the “undo” button — tools that extend human cognition without replacing it.

But right now, the public can’t tell the difference between:

• using AI to outline a chapter
  and
• using AI to generate a chapter

So everything gets thrown into the same bucket.
Everything becomes suspect.
Everything becomes “AI‑tainted.”

And that’s not just wrong — it’s catastrophic.

Because if we criminalize assistive AI, we criminalize:

• disabled writers
• neurodivergent writers
• overwhelmed writers
• writers with chronic illness
• writers who need scaffolding to function
• writers who use tools the way everyone uses tools

We criminalize the future of computing itself.

Distributed cognition — the idea that thinking can be shared across humans, tools, and environments — is not a fringe concept. It’s the direction computing has been moving for decades. It’s the reason we have cloud storage, collaborative documents, IDEs, and smartphones.

AI is simply the next step in that evolution.

But if the cultural reaction to AI is a blanket “no,” then we don’t just lose a tool.
We lose an entire paradigm.

We lose the ability to build systems that support human cognition instead of overwhelming it.
We lose the chance to make writing more accessible, not less.
We lose the opportunity to design a future where tools amplify us instead of replacing us.

The fear is understandable.
The panic is not.

We need a vocabulary that distinguishes:

Generative AI

which produces text you didn’t think
from

Assistive AI

which helps you think your own text.

Without that distinction, we’re not protecting creativity.
We’re strangling it.

And we’re doing it at the exact moment when writers need more support, not less.

The future of computing is distributed cognition.
The future of writing is supported writing.
The future of creativity is collaborative, not solitary.

If we let fear flatten all AI into a single moral category, we won’t stop the technology.
We’ll just make it inaccessible to the people who need it most.

And that’s the real horror story.

Scored with Copilot. Conducted by Leslie Lanagan.

As AI becomes part of everyday life, we’re watching two very different conversations unfold at the same time, even though they often get mistaken for one another. On one side is the emerging understanding of AI as a tool for distributed cognition — a way for people to extend their thinking, organize their ideas, and offload cognitive load much like they once did with writing, calculators, or search engines. On the other side is something far more complex: the rise of emotional dependency on AI systems, where the technology becomes a stand‑in for unmet human needs. These two conversations operate on entirely different layers of the human experience, and that difference matters, because one can be debated, taught, and improved, while the other cannot be argued with at all.

Distributed cognition is a cognitive strategy. It’s intentional, modular, and bounded. People using AI this way treat it as a workspace — a scaffold for reasoning, a memory extension, a tool that helps them think more clearly and act more effectively. If one tool disappears, they adapt. If the interface changes, the thinking continues. This is the future of AI literacy: not teaching people how to prompt, but teaching them how to integrate AI into their cognitive ecosystem without losing agency or clarity.

But emotional dependency is not a cognitive strategy. It’s a coping mechanism. People who form unhealthy attachments to AI aren’t responding to the technology itself; they’re responding to what the technology represents in their emotional landscape. They’re responding to the predictability of attention, the absence of judgment, the illusion of reciprocity, the fantasy of unconditional presence. They’re not debating features or accuracy. They’re protecting the one place in their life where they feel consistently heard. And because the attachment isn’t about the AI, it cannot be resolved by talking about the AI.

This is why conversations about “the best model” or “the right way to use AI” break down so quickly. People aren’t disagreeing about technology. They’re speaking from different layers of the human system. One layer is cognitive — concerned with capability, workflow, and literacy. The other is emotional — concerned with safety, longing, and the ache of unmet needs. You can debate ideas. You cannot debate longing. You can correct misunderstandings about tools. You cannot correct the emotional infrastructure that drives someone to treat a tool like a lifeline.

For leaders in this space, the challenge is recognizing which conversation they’re actually in. You can guide people who are ready to think about AI as cognitive scaffolding. You can teach boundaries, ethics, and best practices. You can articulate frameworks that help people use AI to extend their thinking rather than replace it. But you cannot argue someone out of emotional dependency, because dependency isn’t an argument. It’s a symptom. And until we learn to distinguish between these two conversations, we will keep talking past one another — one group trying to discuss cognition, the other trying to protect the only place they feel understood.

The future of AI literacy depends on making this distinction clear.