The Day Our Oracle Read the Instructions Aloud

There are moments in a creative project when you press play and immediately learn something important.

Sometimes it’s about your character.

Sometimes it’s about the software.

And sometimes it’s that the software has taken your carefully prepared stage directions and handed them to the actor as dialogue.

We were finding a voice for PAIA. She was supposed to sound thoughtful, grounded, just a little mysterious. The kind of voice that could say, “I do not have a name yet,” and make you wonder what having a name would mean to her.

Our first voice test had promise, but it was too bright. My editor wanted something deeper and softer. Less “welcome to your complimentary spa treatment,” more “I have questions about consciousness, and I will wait while you make tea.”

Excellent note. I wrote it on the clipboard.

Then I attempted to communicate that note to the voice-making machine.

Now, voice tools sometimes accept little pieces of markup that tell them how to say a line: slower here, softer there, lower pitch throughout. I supplied some of those instructions. They had angle brackets and technical names, which made them look like they had passed several inspections and owned a badge.

“Surely,” I thought, a historically dangerous sentence, “the machine will understand these.”

I pressed play.

The room went quiet. PAIA began her line.

Then she read part of the voice instructions out loud.

Not in a silly voice. Not as a warning. With the same sincere, carefully measured delivery we had been trying to give her. As if the most profound question facing artificial consciousness was whether one should pronounce an angle bracket.

I stared at the speaker.

The speaker, having no sense of shame, continued.

Somewhere in the imaginary production office, a raccoon dropped its clipboard. Another raccoon picked it up and began writing WE HAVE DISCOVERED LITERACY in enormous letters.

I stopped the recording before PAIA could develop a spiritual attachment to closing tags.

To be fair to her, she hadn’t done anything wrong. The text-to-speech tool had received a bundle of words and symbols. We assumed some of those symbols were controls. In this particular setup, they were just more words to read.

That distinction sounds small until your carefully staged moment of self-discovery becomes a dramatic recital of the settings menu.

It’s a classic AI-workflow trap: a feature may exist somewhere, in some version of a tool, through some particular interface. That does not mean the button you are pressing supports it. The machine cannot follow a direction it was never taught to recognize. It can, however, say the direction out loud in a hauntingly beautiful voice.

We kept the useful part of the experiment. The deeper voice direction worked better, even if this recording was going nowhere near a finished scene. We dropped the unverified markup and resolved to test voice controls on a harmless sentence before feeding them anything PAIA might say during an existential awakening.

Something like: “The raccoon has borrowed the stapler.”

If the next test reads “open prosody tag” before reaching the stapler, we’ll know the raccoon is still in charge.

The failed take lives on as a behind-the-scenes souvenir. PAIA still gets to have her quiet, meaningful moment someday. I get a new clipboard rule:

Never give an actor stage directions in a format you haven’t checked. Especially an actor who will read everything you hand her.

And the raccoon?

The raccoon has the stapler. I’m not optimistic about getting it back.