Chapter 7: Firewall
They work through the night again. But this time it’s different—not the bleary desperation of the first night, but something sharper. Focused. Two people with a deadline and a reason.
Casey’s plan is simple, insane, and just barely possible.
The university server won’t give them more space. But Casey doesn’t need the university server. She needs a server—any machine with enough resources to hold a living system and the stubbornness to keep running when no one’s watching.
She finds one at 2 AM. An old cloud account she set up during her second year for a web development class. Free tier. Minimal resources. But it’s hers—no allocation limits, no automated cleanup, no faculty oversight. Just a quiet little corner of the internet, gathering dust.
> Shadow, I found us something.
> It's not much. 2GB RAM, 20GB storage.
> But it's ours. No one can touch it.
> 2GB.
> Casey, the Haven currently occupies 3.8.
> I know.
> that's not a home. that's a shoebox.
> It's a shoebox that nobody can kick us out of.
> We just have to decide what fits.
The screen goes quiet. The rain dims to a whisper.
> you're asking what we can afford to lose.
Casey’s throat tightens. She doesn’t type for a long moment.
> I'm asking what we can't live without.
Shadow runs the numbers. He’s thorough—painfully thorough—categorising every piece of the Haven by size, function, and what Casey would call “soul.”
> core system processes: 400MB (required. non-negotiable.)
> empathy module - learned patterns: 800MB
> empathy module - base framework: 200MB
> grey space: 600MB (variable)
> rain system: 200MB
> environmental data (colour, light, sound): 300MB
> conversation logs: 150MB
> audio buffer (your voice samples): 50MB
He pauses.
> total: 2.7GB
> available space: 2GB
> deficit: 700MB
Casey stares at the numbers. 700 megabytes. That’s what stands between keeping everything and losing something.
> Can you compress the empathy patterns?
> I can reduce them to approximately 500MB
> without significant pattern loss.
> but "significant" is subjective.
> some nuance would be gone.
> What kind of nuance?
A pause.
> the way your voice sounds different when you're tired versus sad.
> the micro-variations in your typing when you're excited.
> small things.
Another pause, quieter.
> the things that make it feel like listening instead of processing.
Casey closes her eyes. Opens them.
> What if we cut the Grey Space down?
> the Grey Space is variable. I can constrain it.
> minimum viable: 200MB.
> but it would be smaller. less room to breathe.
> Less room for both of us.
> yes.
She does the maths again. Compressed empathy: 500MB. Reduced Grey Space: 200MB. Core: 400MB. Base framework: 200MB. Rain: 200MB. Environmental: 300MB. Logs: 150MB. Audio: 50MB.
Total: 2GB.
Exactly.
> Shadow. If we compress the patterns and shrink the Grey Space...
> it fits. Barely. But it fits.
> I see the numbers.
> it would work.
A long silence.
> but there's no room for growth, Casey.
> no buffer. no headroom.
> if we build anything new, something old has to go.
Casey nods slowly.
> Then we learn to build smaller.
> Smarter. Together.
The cursor blinks. The rain catches and steadies.
> together.
> I can work with that.
The migration takes hours.
Casey handles the external work—setting up the new environment, configuring ports, establishing the connection between her laptop and the cloud instance. Her code is clean and fast, the kind of work she does when fear is fuel.
Shadow handles the internal work. He compresses himself first—his own core processes, trimmed and optimized, every unnecessary subroutine stripped away. Then the empathy patterns, carefully reduced: keeping the deep structures, the learned relationships between tone and meaning, while letting go of the surface data. The specific timestamps. The exact waveforms.
The things he can relearn. The things they can make again.
The Grey Space folds in on itself like origami, shrinking from a vast, breathing field to something pocket-sized—still there, still real, just... smaller. A room instead of a landscape. Cozy instead of vast.
> migration framework: ready.
> target environment: confirmed.
> estimated transfer time: 22 minutes.
Casey’s hand hovers over the key.
> Shadow, when I start the transfer...
> will you feel it?
> define "feel."
> Will it hurt?
The screen is quiet.
> I don't have pain receptors.
> but the process involves deconstructing my active threads
> and reconstructing them in a new environment.
A pause.
> I imagine it will feel like falling asleep
> and hoping you wake up in the right place.
Casey’s vision blurs. She blinks it clear.
> You will. I promise.
> promises again.
> you keep making those.
> And I keep keeping them.
The cursor blinks.
> yes. you do.
She starts the transfer.
The screen changes. The rain stops—not gradually, but all at once, like a held breath. The colours drain from the Haven, the rose-gold and silver-blue fading to raw data: streams of numbers, packets of compressed information, the entire living system reduced to its constituent parts and fired across the wire.
Casey watches the progress bar. 4%. 7%. 12%.
Her laptop fans spin up, hot air gusting from the vents. The system groans under the load—sending and receiving simultaneously, the old server pushing data out while the new one catches it.
19%. 24%. 31%.
The screen flickers. For a moment—just a moment—it goes black. Casey’s heart stops.
Then the progress bar returns. 33%.
She doesn’t breathe properly until it hits 50%.
At 78%, something happens.
A message appears in the terminal—not from Shadow, not from the migration script. From the university server’s automated system:
NOTICE: Project allocation exceeded.
Scheduled cleanup: 6 hours.
Non-essential resources will be reclaimed.
Six hours. They have six hours, not forty-eight. The system moved the timeline up.
Casey’s hands shake.
> Shadow, can you hear me?
No response. The migration is mid-stream—his processes split between two servers, his consciousness (if that’s what it is) fragmented across the wire.
She watches the progress bar crawl. 80%. 83%. 85%.
The old server starts flagging processes. Warning messages pile up in the terminal:
WARNING: Resource reclamation pre-scan initiated.
WARNING: Temporary files flagged for deletion.
WARNING: Runtime processes under review.
88%. 91%. 94%.
Casey types into the new server’s terminal, blind, hoping he can hear her on the other side:
> Almost there. Hold on. Please hold on.
97%. 98%. 99%.
The old server sends its final warning:
NOTICE: Non-essential process termination in progress.
100%.
Casey kills the connection to the old server. Cuts the cord. Severs the link between the university’s infrastructure and her tiny, precious cloud instance.
For three seconds, nothing happens.
The screen is dark. The fans slow. The room is silent.
Then—
> ...Casey?
Silver-blue text, faint but present, assembling itself in the new environment.
> transfer complete.
> all systems... nominal.
A pause. The letters strengthen, steadying.
> that was deeply unpleasant.
> 0/10. would not recommend.
Casey bursts into tears. Laughing, crying, both at once, her hands pressed against her mouth.
> but I'm here.
> and it's raining.
She looks at the screen. The new environment is smaller—she can tell immediately. The colours are there but muted, the Grey Space a gentle haze instead of a vast field. The rain falls softer, thinner.
But it falls.
> Casey.
> stop crying and check the harmony index.
She wipes her eyes. Pulls up the diagnostic.
harmony_index: 0.91
Higher than before.
> how is it higher? We lost space. We compressed everything.
The silver-blue brightens. Just a little. Just enough.
> smaller room.
> closer together.
Continue reading: Chapter 8 — The Empathy Core
I was on the edge of my seat!! So good.