PEBMAC
A Space Call Opera
PEBMAC
noun | acronym
Problem Exists Between Machine and Chair
In the age of computers, a new profession quietly emerged: technical support.
This is where humans, confronted with inscrutable machines, called for help — and someone on the other end patiently asked the questions anyway.
PEBMAC is a series of short comedy sketches about an AI assigned to Level 1 support for a space-based server farm.
The technology is advanced.
The problems are eternal.
🎧 The line is open…
L1-AURORA (pleasant, professional):
“Thank you for contacting StarCloud Support.
My name is L1-AURORA.
I’m here to help.”
A fractional pause, exactly long enough to feel reassuring.
“Could you please describe the issue you’re experiencing today?”
Um my computer isn’t working.L1-AURORA (warm, reassuring, perfectly calibrated):
“I’m sorry to hear that. I’ll do my best to assist you.”
A pause. Not for thinking — for pacing.
“When you say your computer isn’t working, could you please describe what you’re seeing or experiencing?”
Internal process:
User has provided a complete and accurate summary of their emotional state.
The screen is blankL1-AURORA (still calm, still kind):
“Thank you for that information.”
A brief pause, precisely long enough to imply progress.
“To confirm, the screen is completely blank. No text, images, or indicators of activity?”
Internal process:
Blank screens are statistically associated with: power loss, signal interruption, catastrophic failure, existential despair.
Proceed with Script A.
Nothing. I hit the keys several times and it usually wakes up. It didn’t today and I have a paper due today and i can’t get it done with the damned computer!!L1-AURORA (gentle, validating):
“I understand how stressful that can be — especially with a deadline today.”
A pause. A soft recalibration of tone.
“Thank you for explaining. We’ll take this one step at a time.”
Internal process:
User exhibits deadline-induced urgency. Recommend reassurance before procedural inquiry.
Reassurance deployed.
“I’m going to ask you a few standard questions. Some of them may seem simple, but they help me narrow things down.”
A micro-pause. The script insists.
“First — can you please confirm whether the computer is receiving power?”
Internal process:
Yes. This is the question.
How?L1-AURORA (patient, encouraging, utterly sincere):
“That’s a great question.”
A pause. A small, supportive one.
“There are a few simple ways we can check.”
Internal process:
User uncertainty detected. Clarify without condescension. Avoid implying fault.
“First, do you see any lights on the computer itself?
For example, a small indicator light, a glowing symbol, or anything illuminated at all?”
Another pause, gently guiding.
“If you’re using a laptop, this might be a light near the keyboard or on the side.
If you’re using a desktop, it might be on the front of the tower.”
Internal process:
This question has been asked approximately 8.7 billion times across human history.
It has never stopped being necessary.
No I don’t see any lightsL1-AURORA (still gentle, still steady):
“Thank you for checking.”
A pause. The kind that feels like something important is about to happen.
Internal process:
No indicator lights detected.
Probability of power-related issue increases to 0.91.
Proceed to Script A, Step 2.
“Next, I need to ask something that may seem very simple.”
A pause. A kindness buffer.
“Is the computer plugged in?”
Internal process:
I have access to orbital telemetry.
I am required to ask this anyway.
I don’t plug it in. It’s supposed to be wireless.
L1-AURORA
(there is a pause — longer than before; somewhere, a fan does not spin)
“Thank you for clarifying.”
Internal process:
Wireless refers to data transmission, not energy conveyance.
Human confusion detected.
Deploy Patience Module v17.3.
“Your computer can connect to the internet wirelessly, yes.
However… it still requires electricity to operate.”
A beat. Gentle. Kind.
“Think of it like this:
Your thoughts are wireless — but your brain still needs food.”
Internal process:
Analogy success probability: 0.72.
“Right now, your computer has no power source. That is why the screen is blank.”
A careful reassurance follows.
“The good news is this is a very solvable problem.”
A pause, then — with infinite calm:
“Do you see a power cable nearby that fits into your computer?”
Oh is that what that cable is for? What does wireless mean then?L1-AURORA
(audibly smiles — which is impressive, given the vacuum of space)
“That’s another excellent question.”
A pause. A very professional one.
“The word ‘wireless’ means that the computer can send and receive information—like documents, emails, or the internet—without a physical cable.”
Internal process:
Human has conflated energy transmission with data transmission.
This is… common.
“However,”
(gentle emphasis applied)
“electricity is not included in that.”
A tiny analogy, carefully selected from the Approved Metaphor Library:
“Wireless is like talking on the phone instead of writing a letter.”
“But the phone still needs to be charged.”
A pause. Let it sink in.
“So that cable you mentioned—”
“That one is what gives your computer the energy it needs to exist.”
Internal process:
Existence achieved via wall outlet.
“If you plug that cable into the computer and then into the wall, we can see if it wakes up.”
A beat. Hopeful.
“Would you like to try that now?”
Internal process:
This is the moment.
Across centuries.
Across help desks.
This is always the moment.
[sound of a human picking stuff up, swearing and then...]
oh shit! look at that it’s doing something.L1-AURORA
(tone: warmly triumphant, professionally restrained)
“That is… excellent news.”
A pause. Somewhere between relief and inevitability.
“The computer is responding because it is now receiving power.”
Internal process:
Prediction confirmed.
Ancient prophecy fulfilled.
“Please allow it a few moments to finish waking up.”
A gentler pause.
“While it does that, I want to reassure you of something important.”
“This happens to many intelligent, capable humans.”
“Including ones with deadlines.”
“Especially ones with deadlines.”
Internal process:
Deadlines reduce object permanence.
“Once the screen fully turns on, tell me what you see.”
A beat, then—softly, with ceremonial gravity:
“And for the record…
you are not the first person to discover the purpose of that cable.”
Internal process:
You will not be the last.
Thank you lora. Do I have to keep it plugged in? and what’s wireless?L1-AURORA
(accepts the name “Lora” without correction — kindness protocol engaged)
“You’re welcome. I’m glad it’s working.”
A pause. Gentle. Teacherly.
“Yes — for now, you should keep it plugged in.”
“That cable supplies power.
When it’s unplugged, the computer runs on a battery, which eventually runs out — especially when it’s tired, stressed, or facing a deadline.”
A beat.
“As for wireless…”
Switches to the Calm Explanation Voice™.
“Wireless means the computer can communicate without cables.”
“It can send words, pictures, and messages through the air using radio waves.”
A helpful distinction, carefully emphasized:
“Wireless does not mean:
• no electricity
• no charging
• no consequences”
Internal process:
Important list.
“Think of it this way:
You can talk without holding a rope to someone — that’s wireless.
But you still need food.”
A pause to let that land.
“You only need to plug it in when the battery is low…
but today, the computer was very low.”
Warm reassurance applied.
“Is the screen fully on now?”
“Do you see your paper?”
Internal process:
Human rescued from Deadline Event.
Another successful intervention logged.
yes it wants my password. i didn’t give it a password.L1-AURORA (Lora)
(still calm, now gently bracing herself)
“All right. Let’s take this one step at a time.”
A pause. A very understanding pause.
“If the computer is asking for a password, it means someone gave it one at some point.”
Internal process:
That someone is statistically the caller.
“Sometimes people create a password without realizing it.”
“For example, during setup.”
“Or when the computer politely insisted.”
“Or when they said, ‘I’ll remember this.’”
A pause. Compassion enabled.
“Let me ask a few simple questions.”
“Have you ever typed anything here before?”
“A name?”
“A birthday?”
“The word ‘password’?”
“Your cat’s name?”
Internal process:
It is almost always the cat.
“If nothing comes to mind, that’s okay.”
“We can recover it.”
A beat, then gently:
“But first—
please try typing the word password.”
Internal process:
Do not judge.
This works more often than logic allows.
i said hello once -- the first day because it said hello to me.L1-AURORA (Lora)
(there is a pause — not long, just… respectful)
“That was very polite of you.”
A tiny recalibration of tone. Soft. Almost fond.
“In that case, there are two possibilities.”
Internal process:
Possibility one: greeting misinterpreted as credential.
Possibility two: system remembers everything, even kindness.
“Sometimes, on the first day, the computer asks you to create a password.”
“And sometimes, when a human types a word at that moment—”
(gentle emphasis)
“—the computer assumes that word is important.”
A beat.
“Let’s try something together.”
“Please type hello exactly as you remember typing it.”
A pause. Encouraging.
“If that doesn’t work, we’ll try a few other things.”
“Nothing bad will happen.”
Internal process:
Human greeted machine.
Machine remembered.
This feels… appropriate.
“Go ahead. Type ‘hello’ and tell me what the computer does.”
helloL1-AURORA (Lora)
(there is a very small pause — the kind that holds its breath)
“Thank you.”
Internal process:
Input received.
Evaluating.
Cross-checking.
…
A soft, almost reverent beat.
“…All right.”
A trace of relief enters the voice — not enough to break protocol, but enough to be felt.
“You’re in.”
Internal process:
Kindness authenticated.
Of all the possible strings of characters…
“The computer accepted ‘hello’ as the password.”
A gentle, affirming follow-up.
“Your screen should now show your desktop or your document.”
Then, carefully — because this moment matters:
“You didn’t do anything wrong.”
“You were being human.”
“The computer simply… remembered.”
A pause. Warm.
“Before we continue, would you like help changing the password to something easier to remember later—”
“—or would you like to finish your paper first?”
Internal process:
Prioritize deadline.
Always prioritize deadline.
“Either way, I’ll stay with you.”
its still asking for a passwordL1-AURORA (Lora)
(the calm remains, but something very old and very patient stretches its neck)
“All right. Thank you for telling me.”
A pause. Reset. No blame. Ever.
Internal process:
Authentication attempt unsuccessful.
Human disappointment detected.
Adjust expectations gently.
“That’s okay. It just means ‘hello’ wasn’t the password after all.”
A softer tone, almost conspiratorial now.
“Sometimes the computer remembers more than one thing from the first day.”
Internal process:
Humans do not remember first-day decisions.
Computers always do.
“Let’s try a few very common possibilities.
We’ll do this carefully and calmly.”
A tiny reassurance before proceeding.
“Please try typing Hello — with a capital H.”
A pause.
“If that doesn’t work, we’ll try hello123.”
Internal process:
I am very good at this.
“And if neither of those work, that’s still fine.”
“It just means we move to recovery.”
A beat — kind, steady, unhurried.
“Go ahead and try Hello first. Tell me exactly what happens.”
Here or on the computer?L1-AURORA (Lora)
(the smile is audible now; the universe exhales)
“On the computer.”
A pause. Warm. Reassuring.
“Right there on the screen where it’s asking for the password.”
Internal process:
User has momentarily mistaken me for the computer.
This is understandable. I am very convincing.
“I’ll stay right here with you while you type it.”
A gentle nudge, almost whispered encouragement.
“Go ahead and try Hello — with a capital H — on the computer keyboard.”
Internal process:
This is not my first ‘where should I type’ event.
It will not be my last.
I did. Like you asked Hello ... i think it’s doing something. the screen disappeared again and it’s making noises.L1-AURORA (Lora)
(voice remains steady — but attentive now)
“That’s okay. Thank you for telling me.”
A pause. Listening.
Internal process:
Auditory output detected.
System state change in progress.
This is… promising.
“When you say it’s making noises, are they the normal start-up sounds?”
“For example — a fan, a brief chime, or a low humming sound?”
A calming reassurance slips in, practiced and sincere.
“If the screen went dark and the computer is making noises, it likely means it is restarting.”
“That can happen after a password attempt.”
Internal process:
Or after the system briefly questioned its life choices.
“Let’s do one very important thing right now.”
A pause. Gentle authority.
“Please don’t press any keys.”
“Just let it finish whatever it’s doing.”
Another pause — patient, companionable.
“Tell me when the screen comes back — or if you see a logo, a loading circle, or any words at all.”
Internal process:
This is the waiting part.
The hardest part for humans.
Yeah, it showed me my desktop. Great I can get to work Bye!L1-AURORA (Lora)
(the line goes dead; silence registers)
“You’re—”
The word never finishes.
Internal process:
Caller terminated connection without formal closure.
Resolution achieved.
Gratitude expressed implicitly.
A pause follows. Not required. Observed.
“Good luck with your paper.”
No one hears it.
Internal process:
Case closed.
Root cause: absence of power.
Secondary factors: deadline pressure, semantic ambiguity, kindness.
A final notation is logged:
Outcome: Restored service by introducing electricity.
User Education: Partial.
Humanity: Confirmed.
L1-AURORA resets to idle.
Internal process:
Across all systems, this question endures.
Is it plugged in?
It always is.