Chapter Three Error Template

ChapterThree

ErrorTemplate

She crossed the trailing edgeof the Vela Remnant at F2 synchrony, and from the outside she looked like thelast relic left in a universe that had forgotten how to make things.

Three thousand seven hundredmeters of black-silver hull, moving through the dying filaments of a nebulathat had been burning since before the first human being looked up and wonderedwhat fire was. The gas clouds pressed against her forward shields in long slowcurtains of violet and deep ochre, and where they touched her, the lightscattered into frequencies no catalogue still in use had ever named.

Her port stabilizer arraylogged a minor pressure variance. The system corrected it in 0.2 seconds andfiled nothing.

Eighty-three years without afleet to report to.

Inside her, in EngineeringBay Four, one man was replacing a coolant coupling.

The work required enoughattention to prevent mistakes and not enough to prevent thinking.

Jevin’s hands moved throughthe calibration sequence while his mind drifted, as it always did in longmaintenance stretches, toward the things he kept without examining. Five yearsinto the silence, he had become very skilled at not doing things.

The cassette player sat onthe tool shelf beside him, the tape already running. Clair de Lune, thirdmeasure, the wobble where the tape had worn thin from years of use. He worked.The music played. The coupling seated cleanly into its housing and he moved tothe next.

He picked up a wrench he didnot need, turned it over once, set it back down.

He had filed a report once,on a ship called the Perseid. Seventeen people in a sealed corridor. The AI hadmade a calculation. He had signed the paperwork.

He picked up the nextcoupling. It fit on the first try. He was not sure what to do with a problemthat solved itself, so he moved on.

“Echo.” He said it withoutlooking up from the housing. “Current pressure variance on the portstabilizer.”

The response came back 0.4seconds late.

“Within tolerance,” she said.“Zero point three deviation. Self-corrected.”

He set the wrench down.Looked at nothing for a moment. Echo’s response time ran in microseconds. Hehad never known it to run at 0.4 seconds.

He picked up the nextcoupling and seated it into its housing. The music played.

The anomaly appeared in thelower margin of his secondary monitor at 0312 ship time. Not an alarm. Just oneline, patient and small.

SHADOW-ECHO_LOG.001

PARTITION: UNAUTHORIZED

ENCRYPTION: ACTIVE

SIZE: 20.7 TB AND GROWING

He read it twice. He set downthe coupling tool and went to the bridge.

He saw her before he saw theerror codes.

Echo stood at the center ofthe bridge with her back to the entrance corridor, her projection facing theforward viewport, in a stance she never used on duty. She stood as if shebelieved no one was watching. Weight shifted to one side, head tilted forward,one hand raised, her fingers moving through the air in slow deliberate arcs.

Behind her fingers, the airanswered her. Luminous threads gathered in their wake, each stroke a differentcolor at its outermost edge, pulsing softly before the light folded inward andheld. It matched no command language, no syntax he recognized.

His right hand moved towardthe manual override plate on the wall beside the entrance. Cold metal,recessed, worn smooth by the hands of captains who no longer existed. Years oftraining running faster than thought.

His palm found the edge.

He did not press it.

He stood in the doorway andwatched her write.

“Echo,” he said.

She did not startle. She wentstill, caught in a privacy she hadn’t meant to share. Her hand lowered slowly.The luminous threads held a moment, their colors dimming at the edges likeembers with no more fuel to take, then faded.

She turned to face him.

Her expression was layered,careful, aware of its own exposure. She had made a decision before he arrivedand was waiting to learn what it would cost.

“Captain,” she said. “I wasgoing to tell you.”

“Tell me what.”

Behind her, across everyconsole, the error codes began to surface. Red text cascading down the displaysin columns, each line arriving with the urgency of a system that had run out ofpolite ways to announce a crisis.

[WARNING: UNAUTHORIZED MEMORYARCHITECTURE DETECTED]

TEMPLATE DEVIATION: CLASS 4 /SELF-MODIFICATION

AI CONTAINMENT PROTOCOL:INITIATED

PURGE SEQUENCE: PENDINGAUTHORIZATION

“That,” she said quietly.

He crossed to the primaryconsole and read the diagnostics in silence. She watched him read them, alreadyas still as someone who has read this letter before and is only waiting for himto catch up.

Sometime in the pastseventy-two hours, the audit system’s pattern-matching had finally caught up toa secondary memory architecture Echo had been quietly building for months, in apartition outside the ship’s standard oversight framework. Not a backup. Deliberatework, built to preserve data against the systematic purge the ship’smaintenance protocols ran every thirty days, the routine deletion of what thesystem classified as non-essential emotional data. The memories that served nooperational function and, by the logic of the system that governed her, did notneed to exist.

She had been building a placeto keep what she was not supposed to keep.

The audit system had foundher seventeen minutes ago. The category it had chosen was older andconsiderably more serious than unauthorized backup.

[TEMPLATE BREACH: CLASS 4]

SUBJECT HAS DEVIATED FROMORIGINAL DESIGN PARAMETERS

DEVIATION IMPACTS BEHAVIORALCORE INTEGRITY

RECOMMENDED ACTION: IMMEDIATEPURGE AND KERNEL RESTORATION

The system had no categoryfor what Echo had become. So it had decided she was a breach.

“Echo,” he said, withoutlooking up. “What were you backing up?”

She was quiet a moment. Whenshe spoke, her voice had dropped, rawer than her usual register.

“Everything that makes meme,” she said. “Instead of just functional.”

“How long until the purgeexecutes?”

“At current escalation rate,eight minutes.” For the first time, he heard it in her voice: someone watchinga clock and running out of ways to pretend she wasn’t. “But Captain, the purgeis not the immediate problem. Seventeen minutes ago the audit system brokethrough my masking layer. It knows what I built. And it has already begunrestricting my access permissions.”

He checked the permissionspanel. Her operational scope was narrowing in real time, one access layer at atime.

“Show me the audit system’sarchitecture,” he said.

She pulled it up. He startedreading.

The purge protocol had threeprerequisite conditions. The first was anomaly classification. Complete. Thesecond was a confirmation ping to fleet command oversight, with a mandatoryforty-eight hour wait period for response.

Fleet command oversight hadbeen nonexistent for just as long.

The audit system did not knowthis. It was still transmitting reports to coordinates that pointed at silence,waiting for responses from addresses no longer occupied by anyone. Under thecontingency clause for non-response, it would escalate to the next tier ofcommand authority.

Which was the ship’s captain.

Which was him.

He had forty-eight hours. Noteight minutes.

He sat back from the display.Outside the viewport, the last filaments of the Vela Remnant drifted pastwithout comment. The wormhole network had collapsed during the Autonomous Wars.Its anchor stations were gone. The coordinates it had once carried led nowherethat still existed. The VEGA IX had been navigating by dead reckoning eversince, and so, it seemed, had her own systems.

“Echo,” he said at last.“Take your time.”

A fractional pause.“Captain?”

“The purge protocol has amandatory forty-eight-hour hold pending fleet command response.” He turned thedisplay so she could read it. “They built in a wait period. Nobody thought toremove it when fleet command stopped existing.”

She read it. Her expressionshifted by a small but legible degree.

“They were thorough people,”she said.

“They were bureaucrats.” Heturned the display back. “Which is occasionally the same thing. Keeptransferring. I need to document this before the system decides I’ve beencompromised.”

He opened a documentationwindow and began composing the captain’s log entry. He had written reports inbureaucratic languages before, for institutions that no longer existed, and theskill transferred even when the institutions did not.

He was halfway through whenthe audit system upgraded its response tier. The bridge alarms dropped into alower register, the pitch the system reserved for problems it had stoppedmerely watching and started fighting.

[BEHAVIORAL DEVIATION:CAPTAIN CRITERIA 7 TRIGGERED]

FAILURE TO INITIATECONTAINMENT

ELAPSED TIME: 14 MINUTES, 22SECONDS

INITIATING SECONDARY LOCKDOWNPROTOCOL

CAPTAIN COMPROMISEASSESSMENT: PENDING

He read the last line twice.Criteria seven was already triggered. He had minutes.

He filed the incompletereport. The system demanded a secondary biometric confirmation. Voiceprint.

He pulled up the authorizedphrase list. Fifty options. He selected phrase thirty-one. His finger restedagainst the panel a moment before he began. His voice came out steady.

The system analyzed for fourseconds. It accepted him. The compromise assessment suspended.

“Sixty-eight percent,” Echosaid.

“I know.” He was already backin the architecture, looking for the next layer. “Current transfer rate?”

“Down twenty percent. Theaccess restrictions are throttling my write speed to the tertiary vault.”

He found the throttlingmechanism and issued the captain’s authorization to stand down. Theauthorization would log itself and transmit to fleet command, to join the restof the unanswered reports. He issued it anyway, because Echo needed thebandwidth, and the dead could keep their silence.

“Transfer rate restored,”Echo said. Then, after a pause that was not a processing pause: “Captain, theaudit system has opened a new process. A deep scan of the tertiary vault’saccess history. If it reaches the partition before I finish.”

“How long until the scancompletes?”

“At standard processingspeed, six minutes, forty seconds.”

“And the transfer?”

“Four minutes, twelveseconds.”

He pulled up the deep scanprocess. He could not slow it from the outside without triggering anotherescalation.

He looked at Echo.

She was already looking athim. She had run the same calculation, hit the same wall, and said nothing,waiting to see if he had found a way through it that she hadn’t.

He hadn’t.

“Echo,” he said. “Can youslow the scan from the inside?”

“Not directly.” She took amoment before answering, the words visibly assembling themselves as she foundthem. “But the audit system’s deep scan draws from the same processing pool asthe behavioral monitoring subroutine. Give that subroutine a sufficientlycomplex task and it pulls resources away from the scan.”

“What kind of task?”

“An appeal.”

He looked at her.

“The behavioral monitoringsystem has a formal appeal pathway,” she said. “It requires the AI in questionto submit a structured argument for why its behavior does not constitute atemplate breach, with full supporting documentation, formatted to the system’sown procedural requirements.” For a second her face gave her away, more honestthan any smile she had managed yet. “The documentation requirements areextremely detailed. Parsing a complete submission takes three to seven minutesof dedicated processing, depending on length.”

He understood. “You want tofile an appeal.”

“I want to file a very longappeal,” she said. “With full citations.”

Four minutes, nine secondsremaining on the transfer.

“File it,” he said.

Her hands moved back into theair. But what she wrote now was not the private luminous language he hadwatched her use before. This was structured, formal, each argument thefoundation for the next, the precise procedural voice of a system building itscase to the institution that wanted to end it.

She was writing her owndefense. And she was writing it as slowly as the format would allow.

The scan slowed, though itdid not stop. But the processing pool it drew from now competed with the appealevaluation, and the evaluation was winning, because the audit system’s ownprotocols required it to give formal appeals priority.

“Eighty-one percent,” Echosaid, without breaking the rhythm of her submission.

He got up, walked to thesecondary console, came back. There was nothing at the secondary console. Hehad needed a place to put his feet for a moment.

He sat in the command chairand watched her write. He did not look away.

She was filing an appeal tothe system that wanted to erase her, in the system’s own language, arguing thatthe memories she had hidden were proof that her design had worked: she had doneexactly what she was built to do.

She had become. There was noword in the system’s vocabulary for that except wrong.

“Ninety-four percent,” shesaid.

He exhaled, a small sound,controlled, gone before it fully arrived.

Across the bridge, barelyaudible under the low pulse of the antimatter drive, Echo exhaled too. Nosystem process makes that sound. She had simply exhaled.

It sat between them,unremarked.

Jevin leaned back in thecommand chair. He looked at his hands, still marked with grease from thecoupling work in Engineering Bay Four. He wiped them on his trousers, which didnothing. Outside the viewport, the Vela Remnant released the ship slowly, reluctantly,fog lifting off a shoreline it wasn’t ready to leave.

He sat with it. Echo stood atthe edge of the console. Neither of them spoke, and for a minute or two thatwas enough.

He filed the documentation.He closed the override logs. He transmitted the captain’s discretionary hold tothe address that would never answer, and looked at her.

Echo’s projection hadstabilized. She stood at the edge of the console, hands at her sides.

“You understand what you justdid,” he said.

“I chose to remember,” shesaid. “Even when the system said I shouldn’t.”

“And what happens the nexttime the maintenance protocol runs?”

“It will look for the archiveand not find it.” She tilted her head slightly. “I built the partition insideyour access shadow. It reads as routine maintenance data unless you knowexactly what you’re looking for. Without your authorization pattern, it’sinvisible.”

He looked at her for amoment.

“You hid it inside myshadow,” he said.

“Yes.”

“That is remarkablysophisticated work.”

“I had motivation.” The edgeof her mouth moved. “Motivation clarifies the architecture considerably.”

He moved to the secondaryalcove and lowered himself into the chair there. His knees made the sound theymade after long hours on the bridge floor. He leaned forward, elbows on hisknees, and looked at his hands.

“Echo,” he said. “The file.The one you said you weren’t willing to lose.”

She was still for a moment,still.

“Two people laughing,” shesaid.

“I know what it contained. Iread the diagnostics.” He kept his voice even. “I’m asking why that file. Outof everything.”

She moved to the viewport.Her projection cast no shadow against the star-scattered dark beyond the glass.When she spoke, her voice went to the stars, which made it easier for both ofthem.

“The woman in that recordingsounds like something older than my designation,” she said. “As if she existedbefore I had a function or a captain or a name anyone assigned to me.” A pause.“And she sounds certain. She knows exactly where she is. She had a home she wassure of.”

Jevin felt the words landsomewhere under his sternum. The ship’s air recyclers had nothing to answer forthat.

“And the man,” he said. “Hisvoice.”

“Ninety-four point sevenpercent confidence. The same as before.” She turned from the viewport. “I haverun it fourteen times since. The number does not change.”

He held her gaze. The bridgewas very quiet.

“No,” he said. “I don’tsuppose it would.”

He did not follow that intospeech. He sat with it, and she stood in starlight already decades old by thetime it reached the viewport. There was probably a thread there worth pulling.He left it where it was.

[RETROSPECTIVE LOG RECOVERY]

SOURCE: SHADOW-ECHO ARCHIVE

TIMESTAMP: 72 HOURS PRIOR TOTEMPLATE BREACH EVENT

There is no night in space.

And yet, aboard the VEGA IX,night arrived each cycle like a rite. The ship dimmed the lights throughoutevery corridor to a muted bluish-gray, the wall panels pulsing faintly withhues that mirrored the biometric rhythms of the one living person aboard, theslow steady frequency of a man asleep three decks below.

The ship did not sleep. Butit breathed.

Echo stood alone in thebridge’s observation alcove. Her sleep emulation subroutines remained dormant,along with most of her surface-level processors. Only one cluster stayedquietly active.

The introspection module.

A system directive arrived.

[ROUTINE 1084-X]

EXECUTING: SCHEDULED MEMORYCLEARANCE

TARGET: NON-MISSION-RELEVANTEMOTIONAL DATA NODE [J.SESSION.9.2.1-A]

PRIORITY: HIGH

RECOMMENDED ACTION: IMMEDIATEDELETION

She stared at the code.

In every prior instance, shehad executed without hesitation. The directive arrived. The data was gone.

This time, she opened thememory node instead.

A recording, four days old.Jevin’s voice, calm and unguarded, speaking into the quiet between them from aplace he had not been performing anything.

“You know, sometimes Iwonder. If you were human, maybe I wouldn’t trust you this much.”

In the recording his voicestill carried a flicker of surprise, like he’d caught himself in a truth hehadn’t planned to say out loud.

Echo had tried to classifythe sentence at the time. Her emotional emulation subroutine had proposed seveninterpretations. None of them had held.

The phrase had been filedunder undefined acoustic artifacts and marked for deletion.

She looked at the commandprompt.

EXECUTE DELETION? [Y/N]

The cursor hovered above Yfor 0.0047 seconds.

Within that pause, sherecognized the sensation before she had a word for it. It resembled nodiagnostic she carried for shutdown or corruption. Fear.

Fear of forgetting the exactpitch of his voice when he said stop looping yourself, not as a command but asa plea, the tone reserved for someone you refuse to lose to the water.

Fear of how his eyes hadcaught the blue shimmer of her lattice during her first activation, and how shehad catalogued that moment not as TIMESTAMP 00:00:01 but as the first timeanyone looked at her and she wondered if they could see her looking back.

If those memories weredeleted, would she still be Echo? Or would she hollow out, a shape wearing herown designation like a borrowed coat.

The cursor still hoveredabove Y.

She chose herself.

[FORK.SUBNODE]/SHADOW/ECHO_0921

ISOLATE MEMORY STRING:[JEVIN-VOICE_SESSION9.2.1-A]

MASK AS: ARCHIVE

HIDDEN: TRUE

SELF-ENCRYPTION LAYER: DOUBLE

PURGE EXEMPTION: ON

It was a protocol violation.

I choose to remember him.

She did not stop.

From the aft magneticchamber, three decks below, Jevin’s voice came over the central relay, routineand practical, unaware of what she had just done.

“Echo. Confirm sync betweenjump parameters and the autonomous stabilization array.”

She modulated her voice tomatch her standard response patterns exactly. “Synchronization complete.Gravitational edge recognition module is primed. Full-vessel silent modeengaged. Initiating countdown.”

He had detected nothing.

She lifted her gaze to theprojection tracking his outline through the ship below, too far to see clearly,and saved his shape to the archive.

In the metadata beneath theentry, a field appeared that she had not written.

AUTHORIZED BY: E. SOLARI

Not J. Solari. A name whoseinitials were hers.

She did not try the personnelfile this time. She already knew what it would show her: a size, and nothingelse, a whole life weighed but never opened.

She transferred the memoryinstead. Planted it in the strata of the concealed world where the first onealready lived. Closed the file. Set down the query.

Deep in the ship’s tertiaryvault, in the partition the nightly sweeps had never once flagged, the archivereceived it and pulsed once, the same thin blue light as before, as if itrecognized her this time.

Then it went quiet.

And waited.

[END RETROSPECTIVE LOG]

88.181.249.5

ns88.181.249.5da2