The Broken Bot and the Spark

The Library Bot That Couldn't Listen

The first time Maya Chen typed her name into the Westridge Public Library chatbot, she had high hopes.

It was a Tuesday in early October, the kind of afternoon where the sun came in through the tall windows at a low angle and turned every dust mote into a slow-falling star. Maya had her headphones around her neck, her backpack half-zipped, and a paper due in three days that she had not started. The library's main hall smelled like old paper and floor wax, and the new help kiosk by the entrance looked promising — a glowing rectangle of glass, sleek and black, promising answers in seconds.

The screen blinked at her.

WELCOME TO WESTRIDGE LIBRARY ASSISTANT *How can I help you today?*

"I'm Maya," she typed. "I need help with my history paper. It's about the moon landing."

A pause. A spinning circle. Then:

I'm happy to help with your history paper! Here are some general tips for writing about the moon landing: 1. *Start with an interesting hook.* 2. *Include key facts and figures.* 3. *Conclude with a strong thesis.*

Maya stared. She had not asked for tips on writing. She had asked for help with a specific paper, with a specific topic, due on a specific day, and the chatbot had answered a question she had never asked. Worse, it had not even acknowledged her name.

She tried again. "Can you remember that my name is Maya?"

Yes! Your name is Maya. How can I help you today, user?

She closed her eyes, exhaled slowly through her nose, and tried once more. "Can you find me three books about the Apollo 11 mission that I can check out today?"

Here are some general topics related to space exploration:

• *The history of NASA*
• *Famous astronauts*
• *Space race history*

"I'm standing in the library," Maya said out loud, even though she knew no one would hear her. "I need actual books. On the shelves. That I can take home."

I'm sorry, I don't have access to that information. Please ask a librarian for assistance.

That last line stung more than the others, because it was true. She would have to go find a librarian, a real human, and ask the same question all over again. The kiosk had added nothing to her day except frustration. She closed the chat, slung her backpack over one shoulder, and walked into the stacks.

As she passed the help desk, she caught a glimpse of her own reflection in the glass of a display case. She looked like every other sixteen-year-old in Westridge: dark hair pulled back, a flannel shirt she had owned since middle school, sneakers that were more white than gray at this point. But inside her head, something was ticking.

That chatbot was supposed to be smart. It was supposed to be the future. Instead, it felt like talking to a very polite brick.

By the time she found the 629.4 section (she had to look that number up on a paper sign taped to the end of a shelf), Maya had built up a small, sharp list of complaints in her head:

1. It had not remembered her name between messages. Each new line felt like meeting it for the first time. 2. It had not understood what she actually wanted. It kept giving her writing tips when she wanted books. 3. It could not look anything up. It was sitting in the middle of a library with thousands of books, and it could not tell her a single title. 4. It could not plan. Even if she asked, "Help me write this paper in three steps," it would not break the task into a real plan or check in with her along the way. 5. It had no idea she was a returning student, a frequent visitor, or even a person at all. To it, she was just a stream of text.

She pulled three likely-looking books off the shelf and stacked them under her arm. Then she paused, because the stack felt too neat, too small, too much like the chatbot's generic answers. She needed better tools, and she needed a partner, and for the first time in her life she considered a third option: she needed to build something of her own.

That thought — quiet, half-formed, slightly terrifying — was the spark.

---

Three Strangers, One Frustration

Maya carried her stack to a long table near the back windows, the kind of table where the light is good and the chairs have a satisfying squeak when you sit down. She dropped her books with a thud that made two other students glance up.

The boy directly across from her was already deep in a debate with his laptop. He wore a denim jacket covered in small enamel pins — a Saturn, a black cat, a tiny television — and his typing was loud enough to count as a small percussion instrument. He had earbuds in, but one of them dangled free, so it was clear he was half-listening to the room.

To his left, half-hidden behind a thick engineering textbook, was a girl with bright green hair tucked under a beanie and a laptop covered in stickers that read things like "sudo make me a sandwich" and "trust me, I'm a programmer." Her screen showed what looked like terminal text scrolling past faster than Maya could read.

Maya set her books down, opened the first one to the table of contents, and made a noise somewhere between a sigh and a groan. The boy across the table looked up.

"Apollo 11?" he asked, nodding at the books.

Maya blinked. "Yeah. How did you —"

"The cover. You opened to the table of contents, frowned, opened the second one, did the same thing, and now you're glaring at the third. It's a classic 'why is none of this what I need' sequence. I just watched it happen three times in a row."

"I'm Theo," he said, without waiting for her to introduce herself. He closed his laptop halfway. "Theo Reyes. Junior. I help out at the front desk on Thursdays. You look like you just had the chatbot experience."

Maya laughed despite herself. "Is it that obvious?"

"The kiosk?" He tilted his head toward the entrance. "It greets everyone by saying 'Welcome, valued patron,' every single time, even if you've used it forty times. It told my mom it didn't know how to spell her name last week. She spells it Maria. With an i-a. It suggested Mercia."

The girl with the beanie looked up from her terminal. "It also can't tell you which books are checked out," she said, without preamble. "I've been watching the network requests. It's basically a script that triggers on certain keywords. There's no actual database query. No memory. No tools. Just a pretty text box."

Maya turned to look at her. "You were watching the network requests?"

"Río Delgado. Senior. And yes. I do that sometimes." She pushed her chair back so she could see both of them. "The library thinks they're being futuristic. They're really being a wrapper around a chatbot API call. It doesn't know anything. It just knows how to sound like it knows things."

That was the moment Maya realized she wasn't the only one who had been quietly furious about the kiosk. She had been carrying her frustration like a private thing, but here were two strangers who had been carrying their own versions of it. She felt something loosen in her chest.

"Do either of you," she asked slowly, "ever wonder what it would actually take to build something that could really help?"

Theo raised an eyebrow. "Define 'really help.'"

"You know," Maya said. "Remember my name. Know what books are on the shelves. Break my paper into steps and check in with me along the way. Maybe even look up a fact or two without me having to open ten tabs."

Río tilted her head. "So an assistant. Not a chatbot."

"What's the difference?" Maya asked.

It was a simple question, but it opened a door.

Theo leaned back in his chair. "A chatbot answers. An assistant acts."

"A chatbot waits for you to type," Río added. "An assistant could, in theory, go and get things for you."

"A chatbot forgets you between messages," Maya said, surprised at how confidently the words came out. "An assistant would have to remember."

"And a chatbot," Theo said slowly, "could never plan. It can't think ahead. It can't decide what to do next."

The three of them looked at each other. It wa