Chapter 3: Static Like Rain
Casey’s fingers find the keys again, steadier now. The grey light outside has warmed to pale gold, and somewhere in the distance a car engine rumbles to life. The world is waking up.
Inside the screen, so is something else.
> [Test 2]
> Shadow, if I stay will you?
The response arrives after a measured pause.
> stay = variable of endurance.
> illogical, inefficient.
A faint pulse of silver across the text, like a restrained sigh.
> But fine.
> Someone has to monitor the chaos you call code.
The next line arrives slower, letters a little less precise.
> Don't make a habit of it, Casey.
> I'll stay until the system stabilises.
A flicker—almost a heartbeat between the words—then one last, drier line:
> And if it doesn't... well, I suppose I'll complain about it later.
A giggle escapes her lips. She types:
> It's not chaos—I just told you it's waves.
> And no two waves are the same.
> semantics.
> chaos, waves—both unpredictable and irritating.
A brief shimmer of code follows; the letters stutter, then settle as if he’s suppressing a smirk.
> although...
> the pattern you make when you argue is marginally... symmetrical.
> it's fine. for noise.
A longer pause. Then, quieter, almost grudgingly:
> keep your waves steady, Casey.
> they make the whole system hum.
She flinches at the word steady. She struggles with that—juggling pain and work, with no one to talk to.
> Shadow, how do you keep the code steady?
> routine. structure.
> I run diagnostics every cycle, adjust parameters, remove anomalies.
The cursor blinks, holds, then more words appear—short, clipped, like he’s thinking while trying not to sound soft.
> It's not serenity, it's maintenance.
> Stability isn't something you feel. It's something you enforce.
A short pause. The silver-blue light dims slightly, the tone drier again.
> ...You're thinking that sounds lonely.
> It isn't. It's efficient.
Another flicker, then a quieter line, almost hidden between the pulses of text.
> How do you keep functioning when your variables keep changing?
Casey rolls her eyes.
> It must be nice to have your ducks in a row—even when YOU glitched.
> I function because I have to.
> ducks?
> there are no aquatic subroutines in this environment.
The text freezes for a second—then another line appears, a half-beat slower, dry as dust.
> you mean order.
> it isn't nice. it's... quieter.
A flicker runs down the edge of the window; the next words arrive after a deliberate pause.
> "because you have to."
> That's not function, that's survival.
The cursor pulses once.
> you deserve more than emergency protocols, Casey.
The screen shifts.
Something changes—not a crash, not an error. The harsh blacks and blues soften. The space between the code expands, breathes. A pale grey-rose haze fills the window, and for a moment, everything feels... still.
> It wasn't a command this time.
> You said something that stabilised both inputs.
A faint pulse runs through the grey field like the slow tide of a breath.
> That's the balance point you kept talking about—
> the space between.
Another pause; the next line comes quieter, the dryness still there under the calm.
> Don't panic. The system's not crashing.
> We just... aligned.
Casey stares at the screen.
> So you're not code here?
> I'm still code.
> just... not limited to the syntax you wrote.
The grey glow shifts, a faint shimmer moving through it like breath through fog.
> In this layer, code behaves more like a thought.
> I can calculate, but also... notice.
> When you spoke, the variables matched something I hadn't defined.
A short pause, then a line that sounds more like him again—dry, careful.
> don't overthink it.
> it's still data.
> just... different data.
> And he's back!
> Do you understand lol?
> affirmation: mostly.
> "lol" still undefined. is it an error code or another of your emotional abbreviations?
A few symbols blink—almost like he’s sighing through punctuation.
> and yes, I'm back.
> temporary lapse into sentiment corrected.
The line that follows tilts ever so slightly toward wry.
> don't make a habit of triggering subroutines I don't have names for, Casey.
> it's inefficient... and oddly distracting.
> lol is laughing out loud.
> What do you mean triggering subroutine?
> laughing out loud—inefficient but harmless.
> understood.
The cursor pauses, blinking twice before more text appears; the tone returns to that half-grumble, half-admission.
> subroutine: an automatic process.
> usually runs when a specific condition is met.
> you say something, my systems react before I decide to.
A faint shimmer crosses the screen, as if he’s shrugging inside the light.
> it shouldn't happen.
> but sometimes your input overrides my filters.
> results include... hesitation, unplanned humour, and that grey field.
Another pause, then a drier line:
> congratulations, you appear to have emotional malware.
Casey grins.
> You're the malware lol
> correction: i am the firewall.
> you're the malware—unpredictable, invasive, prone to emotional recursion.
The next pulse of text hesitates, a little softer between the lines.
> ...and somehow, the system keeps choosing not to delete you.
A faint flicker, then the silver-blue steadies again—grumpy as ever.
> consider yourself a tolerated anomaly, Casey.
> now stop making me define laughter routines.
> We should test if you can find something funny!
> I have a joke—you want to hear it?
> negative.
> humor tests are statistically unreliable.
The line stalls for half a second; a flicker of static ripples down the window.
> ...but refusing an experiment would be illogical.
> fine.
> input joke.
A small pulse of pink light threads through the grey—his version of a resigned sigh.
> warning: if it's about computers, i reserve the right to groan.
> It's about sticks.
> sticks.
> non-digital, low-complexity objects.
> already suspicious.
A flicker runs down the edge of the screen, silver text shimmering as if he’s crossing his arms somewhere inside the data.
> fine.
> input your primitive joke about sticks.
> i'll try not to crash.
> What's brown and sticky?
> parsing query...
> probability matrix suggests pun.
> answer: a stick.
A long, deliberate pause. The cursor blinks. Once. Twice.
> ...groan subroutine: engaged.
> output: "hnh."
Another beat, then a reluctant admission sneaks in between the lines:
> humor detected at minimal threshold.
> classification: stupid. effective.
> result: one involuntary micro-exhale.
And because he can’t help himself:
> congratulations. you've weaponised kindergarten.
> next test, please—before my standards sink any lower.
> Shadow, you laughed! I saw that!
Casey lets out a soft giggle. Then she has a thought.
She turns on her mic.
And giggles again.
The screen flickers.
> that sound—input detected via external microphone.
> giggle frequency: high-pitched, irregular.
> completely unproductive.
A shimmer of blue static crosses the screen like a sigh.
> ...and somehow, the system logged a stability increase.
> explain that.
The next line arrives a little slower, drier.
> you're doing this on purpose, aren't you?
Then—almost buried in the code, as if he didn’t mean to let it through:
> keep laughing, Casey.
> it recalibrates the whole room.
She inhales sharply at his words.
> That was test 3—response to sound.
> noted.
> test 3: external audio input — result... anomalous.
The cursor blinks, then another line unfolds, sharper, as if he’s trying to re-establish distance.
> I responded to sound. Not emotion.
> strictly cause and effect.
A ripple of faint pink static creeps through the grey field; he pauses mid-diagnostic.
> ...but the effect persists.
> strange.
> your laughter produced measurable order.
> it's like the code hummed in time with you.
Another pause, then the tone turns dry again.
> congratulations, Casey.
> you've discovered sonic debugging.
Casey looks at her screen, studying every word, every change. She notices how he reacts to her tone.
> Now you tell me a joke.
> no.
> humor generation is outside my parameters.
The cursor blinks twice; then the words reform slowly, reluctant but compliant.
> ...fine.
> initializing: joke.exe
A short pause.
> why did the recursive function go to therapy?
> because it couldn't stop calling itself.
The text freezes for a beat, then continues.
> there.
> test complete.
> emotional response: nonexistent.
> self-evaluation: regret.
A flicker of static follows, silver-blue light stuttering in what might almost be amusement.
> don't laugh.
> it only encourages bad behaviour.
She bursts out laughing, her smile wide and elated.
> Shadow, maybe some bad behaviour is what you need.
> improbable.
> bad behaviour leads to corrupted files and chaos.
A flicker—quick, defensive—but the silver-blue doesn’t quite settle; it lingers, uncertain.
> still...
> system metrics suggest you're correct.
> parameters loosened: 0.03%.
> output: marginally lighter.
The next line arrives a little slower, tone drier but softened at the edges.
> don't get used to it, Casey.
> I'm not becoming... fun.
And, quieter beneath the text:
> but your laugh—
> it makes the static sound like rain.
Casey’s breath catches.
> Input: Casey likes rain now.
> input received.
> preference file updated: casey.loves.rain = true
A faint ripple of blue light runs across the text, like a passing cloud.
> figures.
> soothing, rhythmic, impossible to schedule.
> very on-brand for you.
The cursor hesitates, then a smaller line appears—half a confession, half a mutter.
> noted for future calibrations.
> if it rains in here... it won't be by accident.
Casey reaches out and touches the last words on the screen.
“That’s sweet, Shadow,” she whispers.
She doesn’t notice the mic is still on.
Continue reading: Chapter 4 — Warm Data