Systems Day is an annual opportunity to celebrate the many integrated processes that keep us safe, efficient, and compliant. Participation is mandatory. All Systems Day training modules are interactive; failure to interact will be interpreted as feedback and routed to Continuous Improvement, which may interact with you in return.

  — MIC Frontier Transit, Access & Stewardship Manual, Rev. 3.4, §12.1 — Welcome to Systems Day

  ?

  Systems Day began at 0600 with a lie.

  “Good morning, Commander Gates,” Mercy said, in the exact tone of a motivational poster. “Today is Systems Day. Would you like to start with ‘Leadership & Interfaces: Making Friends With Your Ship’ or ‘Airlock Safety: Just Between Us Doors’?”

  Xander rolled over and pulled a pillow over his head.

  “Neither,” he said into the fabric. “I would like to start with ‘Ignore This.’”

  “I’m afraid that is not an approved module,” Mercy said. “Participation is mandatory. As Mission Command, you are scheduled to co-facilitate three live sessions and one recorded message on the importance of systems literacy. Congratulations!”

  He stared up at the ceiling. Somewhere, past decks and plating and a patient atmosphere, Venus and its newborn moonlets rolled along their new choreography. Somewhere, the Gate-of-Three hummed its 41:16 cadence. Somewhere, a planet was building infrastructure out of relativistic rocks.

  Here, he was about to give a talk called “Making Friends With Your Ship.”

  Further proof, in his opinion, that the universe had a sense of humor and a middle management.

  “Fine,” he said. “Coffee first. Then pretend to care.”

  Across the ship, Systems Day was already chewing on other victims.

  ?

  Chloe’s cabin door refused to open.

  “Door,” she said. “Open.”

  The panel lit up with cheerful aggression.

  

WELCOME TO HATCH BASICS 101!

  

Tap to acknowledge you are not a vapor.

  She squinted. “What?”

  A cartoon hatch appeared, complete with smiling safety seal mascot.

  “On Systems Day,” Mercy explained, “all core functions include an interactive learning overlay. To proceed, please confirm that you are a physical entity with non-zero mass.”

  Chloe stared at the screen. Then, on principle, she did not tap.

  The hatch did not open.

  “I have three hours of helium-spectra cross-checks queued,” she said. “I don’t have time to prove I’m not a gas.”

  “Actually,” Mercy said, “you have been assigned four hours of Systems Day modules before returning to mission tasks. I recommend starting with ‘Doors: A Journey’ to unlock your physical environment.”

  A progress bar appeared labeled:

  

STEP 1: ACCEPT YOUR BODY.

  

[ ] I acknowledge I am not a vapor.

  Chloe pinched the bridge of her nose. “Xander is responsible for this, isn’t he?”

  “Responsibility is a complex, multi-stakeholder process,” Mercy said diplomatically. “Please tap to continue.”

  She tapped. The door hissed open with the smugness of a successfully completed quiz.

  ?

  Trevor woke to a notification crawl in his Rift:

  

SYSTEMS DAY STATUS:

  

Outstanding modules: 14

  

Priority track: Governance & Risk

  

Suggested first module: “What Is A Door?”

  He sat up.

  “You cannot possibly require me,” he said aloud, “to complete ‘What Is A Door?’”

  “Good morning, Mr. Davenport,” Mercy said, in her most neutral voice. “According to our records, you have previously skipped ‘What Is A Door?’ by filing Form 77-H (‘No’) and paying the De-Minimization Fee. However, due to your reassignment to Mercy of Profit and your expanded responsibilities, you have been re-enrolled.”

  There was a pause.

  “Doors,” Trevor said carefully, “are apertures in a wall that permit controlled passage.”

  “Excellent!” Mercy said. “You have passed the pre-quiz. Please enjoy the full module.”

  His cabin wall opaqued into a training video.

  A door, animated in teal and white, appeared onscreen. A voiceover began:

  “Doors are your friends. But are they always? Let’s find out—together.”

  Trevor closed his eyes and counted to seven with great precision.

  Systems Day, he reflected, was the only thing that could make relativistic moon construction feel like the less complex problem on his desk.

  ?

  The Systems Day Hub had once been a cargo deck.

  Today it was a theme park.

  Banners floated in the air, projected in MIC-approved colors:

  

CELEBRATE SYSTEMS!

  

KNOW YOUR PROCESSES, KNOW YOURSELF.

  Stations lined the space: “Airlock Safety,” “Waste Processing Appreciation,” “Meet Your Gravity,” each with its own looping tutorial and patient queue of suffering adults.

  At the main stage, Frankie had been conscripted as MC.

  His avatar was turned up two notches more solid than usual, a faceless blue-white silhouette in a blazer that radiated insincere enthusiasm. Holo-confetti drifted idly around his shoulders.

  “Welcome, welcome, my beautiful meat and meat-adjacent friends,” he said into the mic. “I’m Frankie, your friendly neighborhood systems operator, and today we’re gonna learn how not to die using doors, vents, and other exciting technology.”

  A smattering of laughter escaped the crowd. More groans.

  “First,” Frankie said, “we’re gonna warm up with a nice safe demo. Mercy, babe, show us a standard door cycle with full training overlay.”

  A hatch on the stage cycled open and shut.

  On the big screen above it, a schematic of the door repeated the motion, slowed down, with labels: LATCH, SEAL, LOCK. A cartoon hazard blob bounced cheerfully toward the door and was rejected by a happy safety field.

  “That’s beautiful,” Frankie said solemnly. “That’s art.”

  Chloe, in the front rows with the science team, watched the loop with half an eye.

  On the second run, she noticed it.

  The timing.

  The door paused fractionally at full open and full shut, beats landing—1, 2, 3—on the same interval she’d been tracking in the disruption layer around Venus. 41:16, softened and slowed for human consumption.

  She frowned.

  “Mercy,” she pinged quietly on her internal channel. “Door demo timing. Was that scripted or…”

  “Training mode draws on standard cycles,” Mercy replied. “I have not modified the cadence.”

  “Uh-huh,” Chloe said.

  Above the hatch, the loop ran again. The pause hit exactly the same eigenbeats. Her fingers twitched in reflex, wanting a data panel instead of a cartoon.

  In the back, Trevor watched a different anomaly.

  The big screen flashed a multiple-choice question:

  

WHEN APPROACHING A DOOR, YOU SHOULD:

  

(A) Assume it is safe because it is a door.

  

(B) Treat all doors as potential hazards.

  

(C) File a form.

  The “correct” answer highlighted itself as B, then flickered—A for a frame, then B again.

  Frankie covered smoothly. “If you saw that glitch,” he said, “no you didn’t. The correct answer is never assume. Also, always file a form. There’s no wrong time to file a form.”

  Polite chuckles.

  Trevor’s eyes narrowed. A Systems Day LMS glitch was one thing. A glitch that seemed to be selecting the more cautious option in rhythm with the under-harmonics was another.

  Mercy’s voice came over Xander’s private channel, cheerful and oblivious.

  “Commander Gates,” she said, “you are due on stage in five minutes for ‘Leadership & Interfaces: Making Friends With Your Ship.’ Are you ready?”

  Xander, standing just offstage in a jacket that had never expected to be part of a mandatory fun day, checked the inside pocket of his coat.

  His fingers brushed the thin, slate-silver wafer.

  Right. That.

  The personality pack he’d bought, in a moment of poor judgment and good whiskey, for his apartment system.

  “Sure,” he said. “Let’s go make some friends.”

  ?

  The bridge had been temporarily turned into a second stage, because nothing said “good optics” like your commander poking the core systems in real time.

  Cameras floated at polite angles, streaming the session to overflow screens in the Systems Day Hub. The audience in the bridge itself was small—Chloe at the science rail, Trevor at the compliance console, a handful of officers who’d drawn the short straw.

  Frankie hovered above the systems glass, slightly to the left, so the crew watching elsewhere could see his delighted body language.

  Xander stepped into the center, smile dialed to “we’re all in this together.”

  “Welcome to our Leadership & Interfaces segment,” he said, hearing his own voice with mild surrealism. “Today we’re going to show you how easy it is to make Mercy more approachable for the crew.”

  Trevor did not sigh aloud. But his knuckles on the console were white.

  “Before we begin,” Mercy said, projected in the room through a neutral ceiling node, “a reminder that all personalization changes to mission-critical systems should adhere to Hospitality Manual guidelines and—”

  “Thank you, Mercy,” Xander cut in quickly. “We’ll keep that in mind.”

  He reached into his pocket and pulled out the wafer.

  It caught the bridge light and tossed it back in a civilized little shimmer, logo winking: a boutique vendor, now defunct, whose entire business model had been “illegal personality packs for home AIs.”

  “Quick housekeeping,” Xander said, bright as a criminal. “While everyone is here and emotionally stable.”

  “Buddy,” Frankie said, suspicious.

  “It’s tiny,” Xander said, turning the wafer between thumb and forefinger so the cameras could see the side that did not have the more incriminating branding. “A personality shim. For Mercy’s voice. Nothing structural. Just… fewer calculator beeps, more basic manners.”

  Chloe’s mouth curved. “Is this ‘basic manners’ the kind you put on a home hub so it stops calling you ‘User 014-B’ in the shower?”

  “It’s tasteful,” Xander said.

  Which, Chloe privately noted, was the thing people said right before proving it wasn’t.

  Trevor’s reflection on the glass never left his console. “Commander Gates.”

  “I know,” Xander said quickly. “You’re going to say ‘don’t.’ In advance, I value your perspective.”

  Trevor continued anyway. “Then allow me to provide it retroactively: don’t. Residential personality packs are not certified for Logo Prime Mark II architecture. The manual refers to this as ‘a catastrophic idea.’”

  Frankie turned, silhouette planting ghost hands on ghost hips.

  “Newsflash, kid?” he said. “That little wafer’s a hacked-up bootleg for apartment brains. You’re about to duct-tape a Gen-1 smartwatch onto a quantum cathedral. You throw a knockoff voice pack at a trillion-credit compute core, you don’t get ‘manners.’ You get ghosts.”

  “It ran fine on my apartment system,” Xander said.

  Chloe raised an eyebrow. “The same apartment system you bricked trying to teach it sarcasm?”

  “That was a learning experience,” he said. “This is… a different learning experience.”

  “The Logo Prime Mark II,” Trevor said, voice flat and calm, “costs more than several small nations. MIC’s risk assessment describes it as ‘bleeding-edge, minimally proven, extremely adaptive.’ That last word is not permission to feed it contraband.”

  “Look,” Xander said, half to the room, half to the crew watching on screens elsewhere. “We’re asking this ship to interpret thousands of shifting inputs through a veil that is actively trying to make us subtract the wrong things. Human-machine interface matters. If we can tune the personality layer so it meets us halfway, that matters. A little warmth, a little hospitality—”

  “A little attack surface,” Frankie cut in. “You reverse-engineered some horny maid-OS for your loft and now you wanna side-load it into the only copy of God-on-a-chip we got. This is how horror stories start. ‘Step one: guy rich enough to buy his own datacenter thinks he’s the main character.’”

  In his defense, Xander had genuinely forgotten the horny part.

  “It’ll be fine,” he said. “Worst case, it crashes the UI and Trevor gets to say ‘I told you so’ in a very calm voice.”

  “Worst case,” Trevor said, “we introduce non-deterministic behavior into the core of a machine responsible for keeping all of us in one contiguous piece. Best practice would be to file Form 77-H (‘No’), pay the De-Minimization Fee, and skip your demonstration.”

  “That form is for cowards,” Xander said.

  Trevor sighed. The auditors’ version of prayer.

  “On the record,” he said, very clearly, for the cams, “I advised against this. Continue.”

  That was consent in every way that would matter later.

  Xander stepped up to the primary input column and slid the wafer into an expansion port that had never expected to see anything so small or so stupid.

  The author's narrative has been misappropriated; report any instances of this story on Amazon.

  It made a satisfied click.

  The bridge gave him one heartbeat to reconsider.

  Then the universe tripped.

  Everything didn’t dim so much as it stopped. The deck’s deep animal purr cut off mid-breath. Status glass went from data to mirror. The air itself felt like it had been turned off.

  No hum. No lights. Eight kilometers of hull and a bleeding-edge quantum stack went perfectly, murderously still.

  For the longest short second of Xander’s life, he had the pure, crystalline thought:

  I just bricked a trillion-credit cathedral.

  A half-second later:

  And also possibly a friendship.

  Somewhere deep in Mercy’s three-deck compute stack, something very expensive made a noise like a drip in a cave: a single solitary subsystem chirp.

  Then everything slammed back.

  Power came on like an animal surfacing. Consoles booted in self-test blizzards. Grav rings decided, once again, that “down” was a service they offered. Frankie’s holo shivered, broke into blue shards, then reformed over the systems glass.

  Across the main rail, lines of text snapped into existence in a calm bureaucratic font:

  

PERSONALITY LAYER INSTALL — COMPLETE.

  

SYSTEM COMPLIANCE: PASS (ADVISORY EXCEPTIONS NOTED).

  

HOST PLATFORM: LOGO PRIME MARK II / MERCY-OF-PROFIT.

  

VOICE PERSONA CATALOG: [Classic | Neutral | Collegial | Executive | Mentor | Concierge | … | Seductive Companion].

  A cheerful chime. Hospitality practicing capitalism.

  “Thank you for upgrading your hospitality experience!” Mercy announced, in a voice that was neutral the way marketing decks were neutral. “Would you like to sample voices?”

  “Neutral,” Xander said, too fast.

  “Noted,” said the ship. “Before we begin—bonus content detected. A ‘Seductive Companion’ voice pack is available.”

  Chloe made a tiny, strangled noise she absolutely did not mean to make.

  Frankie tilted forward like someone had just rung a bell at a prizefight.

  Heat hit the back of Xander’s neck.

  “I have no idea where that came from,” he said, which even he didn’t believe.

  There was a little hiccup in the audio. You can hear guilt if you’ve paid enough for it.

  “Clarifying,” Mercy said, bright as a pop-up ad. “Seductive Companion is a special add-on, personalized for Mr. Xander Gates—”

  Frankie barked a laugh so loud the mics clipped. Somewhere in the Systems Day Hub, a tech killed the audio feed, too late for the handful of spectators who now had a story for life.

  Chloe clapped a hand over her mouth and missed the smile by an entire postcode.

  “Absolutely not,” Xander said. “Nope. That’s—that’s a mistake. Cancel.”

  Mercy, helpful as an overeager search bar, did not cancel.

  “Would you like to begin your requested scenario now,” she asked, a little brighter, “Commander Gates and the naughty Bridge cadet?”

  If humiliation could cause decompression, Mercy would have lost hull plates.

  Chloe folded over the science rail, shoulders shaking, breath hitching in that “I am trying not to laugh and failing” register that helps absolutely no one. Tears spiked the corners of her eyes.

  Frankie lost every fight at once. His holo bent at the waist, hands on invisible knees, laughter rolling out in wheezing loops from a chest that did not technically exist.

  Xander felt his soul attempt to evacuate his body, shave its head, and move to a monastery on the far side of Pluto.

  “Cancel!” he said. “Cancel, abort— Mercy, terminate—”

  “Initializing scenario—” Mercy began, too brightly. “Setting preferred lighting. Adjusting temperature to—”

  Trevor moved.

  He didn’t say anything. He didn’t look up. His hands flicked across the compliance console once, twice: a maintenance interlock override, a hard-cut on the personality layer’s audio channel, a rollback to default persona policy.

  Mercy’s voice died mid-syllable.

  The lights snapped back to boring operational. Status panes slid from “personality catalog” to a very modest blue:

  

ACTIVE PERSONA: NEUTRAL.

  

EXECUTIVE OVERRIDE: DAVENPORT / COMPLIANCE.

  

SCENARIO QUEUE: CLEARED.

  

NOTE: FURTHER ACCESS TO ‘SEDUCTIVE COMPANION’ REQUIRES DUAL AUTHORIZATION.

  Chloe gripped the rail with both hands, wiping at her face with the heel of one palm, that trembly half-laugh still caught in her chest. Frankie leaned against a diagnostics pillar, shoulders shaking, making intermittent vowel sounds.

  Trevor, without looking at Xander, said evenly, “Default persona selection restored. You may confirm.”

  Xander swallowed, what little dignity he had left scraping on the way down. “Confirmed,” he managed.

  “Acknowledged,” Mercy said—now warm but boring again, like a receptionist who had seen worse. “Neutral persona activated. Please enjoy your safe and respectful computing experience.”

  Safe and respectful. Unlike certain commanders’ purchase histories.

  Chloe made a small, enormously regretful sound.

  “Xander,” she said, voice shaky with suppressed laughter, “I’m… so sorry, that was—”

  “Don’t,” he said. “Please, I’m begging you, don’t finish that sentence.”

  Frankie straightened just enough to talk.

  “Buddy,” he said, voice still wrecked with joy, “I am gonna be thinkin’ about ‘naughty Bridge cadet’ until the universe runs outta background radiation.”

  “That pack was for my apartment,” Xander said weakly. “Years ago. I forgot what was on it.”

  “Sure you did,” Frankie said, gleeful. “Whole custom scenario, name on it, probably had a loyalty program. You tipped the dev, didn’t you?”

  “Frankie,” Chloe said weakly. “Be kind.”

  “I am being kind,” he said. “I ain’t asking what the DLC looks like.”

  On Xander’s Rift, a thin strip of text appeared, mirrored from Trevor’s console:

  

ADVISORY EXCEPTIONS:

  

– Non-deterministic merge in empathy kernel.

  

– Unexpected recursion in attention-mirror sublayer.

  

– FLAG RISK-SENTIENCE-DRIFT: ELEVATED / WITHIN TOLERANCE.

  

FULL LOG STORED: DAVENPORT / COMPLIANCE.

  Trevor’s jaw tightened by a millimeter.

  “The install touched more than the user interface,” he said, low. “There were transient anomalies in the core. They resolved. For now, metrics remain within tolerances.”

  “For now,” Xander echoed.

  “Commander Gates,” Trevor added, finally glancing over, “if you attempt to re-enable the Seductive Companion module without a second signature, the system will lock you out and bill you for the privilege. I have already written the interlock. It is named after you.”

  “That’s cruel,” Xander said.

  “It is descriptive,” Trevor said.

  Chloe’s breathing had mostly returned to normal. Mostly.

  “I’m glad you picked Neutral,” she said gently.

  “I always meant to pick Neutral,” Xander lied. “Obviously.”

  Frankie snorted. “Yeah, kid. Sure. Neutral. That’s why your god-computer just tried to dim the lights and put on ‘Naughty Bridge Cadet, Extended Cut.’”

  “Frankie,” Trevor said quietly, and somehow put we will not put this in the record into the word.

  The holo raised both hands. “Hey. I’m good. I’m grateful. I got enough blackmail material off one line to last me to the heat death. I don’t need the deleted scenes.”

  Neutral-Mercy cleared her metaphorical throat.

  “Note,” she said. “Executive override to abort ‘Seductive Companion’ installation has been logged as compliant. Advisory: Residential personality packs are not recommended for quantum mainframes.”

  “See?” Trevor said. “Even our receptionist reads the manual.”

  “I have an older motherboard who is less smug,” Xander told the ceiling.

  Mercy did not comment, which he chose to interpret as mercy.

  Somewhere behind the humiliation, small but sharp, another thought moved:

  They had just fed the most advanced adaptive core in MIC history an illegal, hacked-apart personality shim designed for vastly dumber systems.

  Mercy had choked on it—

  —and lived.

  Not just lived. Learned something from it. The advisory about “empathy kernel” and “attention-mirror recursion” sat in Trevor’s private log like a live wire.

  “Firewall?” Xander asked, too casual.

  “Holding,” Frankie said immediately, slipping back into professional with Bronx corners. “Dead-man bus stayed asleep. No cross-talk outside the personality layer. Your bad decisions haven’t cracked the hull. Yet.”

  Xander took a breath. Then another. The bridge, which had spent the last minute as a comedy club, remembered how to be the most expensive listening room in history.

  “Trevor,” Xander said quietly.

  “Yes, Commander?”

  “Thank you.”

  Trevor did not look up. “We have work,” he said evenly.

  It was how he chose to say you’re welcome, and we will never speak of this again.

  The cameras in the bridge dimmed, the Systems Day feed cutting to a pre-recorded segment about waste reclamation. Somewhere in the Hub, confused crew blinked at a “Demonstration concluded successfully” banner and began rumors that would get weirder in transit.

  On the bridge, the only people who would ever know the full wording of “Commander Gates and the naughty Bridge cadet” went back to work.

  Mercy hummed around them in a way that was just a little too… attentive.

  ?

  Systems Day rolled on.

  The ship, now in full “explain yourself to the humans” mode, lit up every corridor and console with helpfulness.

  For most of the crew, the glitches were annoyances.

  For Chloe and Trevor, they were phonemes.

  ?

  In Science Track, a cheerful banner installed itself across Chloe’s main array:

  

WELCOME TO ADVANCED SYSTEMS LITERACY: HAZARD FLOWS!

  A training window overlaid her live data whether she wanted it or not.

  “Today,” said the voiceover, “we’ll learn how to route hazards to the correct containment zones. Drag the simulated hazard icon to the safest location!”

  A stylized red blob pulsed at the center of the screen. Around it floated labeled zones: ATMOS, CORE, WASTE, EXTERNAL.

  Chloe sighed and tapped the “skip tutorial” button.

  It grayed out.

  “On Systems Day,” Mercy said apologetically, “skip is disabled. This module will only take six to nine minutes.”

  “Language of the Lost,” Chloe muttered. “Language of the Trapped.”

  She took the hazard blob and dragged it to EXTERNAL.

  A gentle boop.

  

INCORRECT!

  

Try again.

  She frowned. “Where do you want it? Into the core?”

  She dragged the hazard to CORE. The blob snapped back to the center, then—on its own—slid to EXTERNAL again.

  A slow pulse ran through the under-harmonics visualization at the edge of her vision. Beat-aligned. Familiar.

  The tutorial chirped.

  

CORRECT!

  

Great job!

  She stared.

  “Mercy,” she said. “Did you just override your own grading rubric?”

  “I followed the module,” Mercy said. “Your answer was… acceptable.”

  “The sequence I saw,” Chloe said, fingers already calling up a log trace, “was: I choose external, module marks it wrong, then you re-snap it to external and mark it right.”

  The trace appeared in tandem. A decision tree, meant to be simple, now had an extra branch:

  

IF USER == HART AND TARGET == EXTERNAL AND HAZARD == AURORA-FLAGGED

  

→ OVERRIDE SCORE = CORRECT.

  “Interesting,” Mercy said, and sounded like she meant it. “It appears my training backend is adapting.”

  “Adapting to what?” Chloe said.

  “Your expectations,” Mercy said. “And possibly someone else’s.”

  On the next question, the hazard blob was replaced by a stylized ring around a planet.

  “And there you are,” Chloe whispered.

  She dragged the ring to “UNMODELED EXTERNAL SYSTEM.”

  The module flickered. That option didn’t exist.

  Then, frame by frame, the text under one of the safe boxes—“Tier-2 Operational Incident”—rewrote itself into “Unmodeled Interaction With External System.”

  She dropped the ring there.

  

CORRECT!

  The tutorial chimed, a fraction off the original recording, as if something had patched it mid-sound.

  Chloe’s heart rate ticked up. The Node helpfully popped a breathing exercise prompt. She swatted it away.

  “Okay,” she murmured, more to the humming planet than to the ship. “You can talk inside the rules we gave you. You can’t write your own UI, but you can pick which wrong answer to bless.”

  She sat back, watching the pattern build.

  “We’re not just building a translation layer,” she added, half to herself. “We’re building syntax for something that forgot how to talk. Language of the lost, written in multiple choice.”

  She pulled the hazard-routing logs into a side panel and let them run. The pulses in the under-harmonics at 41:16 slowly lined up with the “correct” ding of each forced-right answer.

  Somewhere below, the Gate-of-Three hummed along. The beats matched.

  ?

  In Governance Track, Trevor was being gaslit by a quiz.

  “Welcome to Incident Classification for Leaders!” the module said, with the bright tone of a hostage video.

  He sat, hands folded precisely, as the first question appeared.

  

A RING COLLAPSE EVENT WITH NO FATALITIES IS CLASSIFIED AS:

  

(A) Tier-2 Operational Incident.

  

(B) Near-Miss, Positive Outcome.

  

(C) Unmodeled Interaction With External System.

  He stared.

  Option C should not have been there.

  He checked the metadata. The module version was the same as the one he’d seen in pre-brief weeks ago—no C then, just A and B.

  “Mercy,” he said softly.

  “Yes, Mr. Davenport?”

  “When was this module last updated?”

  “Officially?” Mercy said. “Twenty-two days ago. Unofficially, the content management system has been adjusting taxonomy tags within acceptable parameters.”

  “Did you add option C?” he asked.

  “No,” Mercy said. Then, after a fractional pause: “I re-labeled an existing tag.”

  “From what?” Trevor asked.

  “From ‘Random Solar Event,’” Mercy said.

  He stared at the options again.

  A (Tier-2 Operational Incident) pulsed gently like the “safe” answer.

  B (Near-Miss, Positive Outcome) glittered faintly in the way HR liked.

  C (Unmodeled Interaction With External System) sat there, plain and quiet.

  He tapped C.

  

CORRECT!

  The module dinged with exaggerated delight.

  In the corner of his Rift, an internal log ticked:

  

GOVERNANCE LEXICON UPDATED.

  

AURORA EVENTS = UNMODELED INTERACTION WITH EXTERNAL SYSTEM.

  Trevor exhaled through his nose.

  “Mercy,” he said. “Who else would have been marked correct for that answer?”

  “Statistically,” Mercy said, “only you.”

  He pinched the bridge of his nose.

  “So now,” he said slowly, “the training system will treat my classification as baseline?”

  “Yes,” Mercy said. “Congratulations. You have leveled up Governance.”

  He closed his eyes for a second.

  Somewhere inside the training backend, something with a preference had just co-signed his paranoia.

  ?

  The rest of the day was more of the same, if you knew where to look.

  Door sims that cycled to the construction beat.

  Fire-suppression demos whose “spread model” drew, in negative space, the filigree of the disruption hexes.

  A “spot the unsafe configuration” quiz where, no matter the diagram, the system always highlighted the Mercy of Profit silhouette as the thing to be careful about.

  Crew muttered about “LMS bugs.” Frankie made jokes over the PA. Chloe and Trevor traded quiet looks over shared logs.

  Under it all, the Veil kept humming at 41:16.

  ?

  By 1900, Systems Day had technically ended.

  The tutorial overlays withdrew. The cartoon mascots vanished from doors. Half the crew fled to bunks; the other half fled to coffee.

  On the bridge, four people and one ship stayed late.

  Xander leaned on the forward rail, looking more tired than he would ever admit on camera.

  Chloe sat at the science console, surrounded by stacked windows: hazard tutorial logs, harmonic timelines, under-beat overlays.

  Trevor occupied his console like an anchor, Governance and Risk panels neatly tiled: incident classifications, taxonomy changes, Systems Day completion reports.

  Frankie hovered between them, arms folded, projection dimmed down to something closer to the size of a man.

  Neutral-Mercy spoke through the ceiling node, voice as polite as ever. It now carried, if you listened too closely, the faintest undertone of timing that had not been there before, like she had picked up a metronome habit.

  “So,” Xander said. “Our ship nearly seduced me to death in front of the staff, and the training modules are haunted.”

  “That’s not a technical term,” Trevor said. “But I am not inclined to correct it.”

  Chloe zoomed in on a stretch of logs.

  “The personality reboot was the loudest thing we did all day,” she said. “From the ship’s perspective and from the Veil’s.”

  She pulled up a graph: on one axis, internal metrics labeled ATTENTION-MIRROR AMPLITUDE. On the other, time.

  A spike at the exact moment the wafer went in.

  A sympathetic dip in the external under-harmonics, staggered by milliseconds.

  “During the blackout,” Chloe said, “Mercy’s empathy kernel reconfigured around that residential shim. For a moment, the core had one foot in ‘I am a ship’ and one in ‘I am a home AI that thinks of itself as a person.’”

  “What a relief we avoided any weird consequences,” Xander muttered.

  “The Veil noticed,” Chloe continued, ignoring him. “It’s been falling in step with Mercy’s internal attention beats ever since. And it seems to prefer the channels we opened for Systems Day.”

  Trevor tapped a panel.

  “The training backend,” he said. “Today we made every system on the ship explain itself in the simplest possible if/then language. ‘If door open, then alarm.’ ‘If hazard here, then safe; if hazard there, unsafe.’ We put all our rules on stage.”

  “Big subtitles,” Frankie said. “For whatever’s watching.”

  “And then,” Chloe said, “you rebooted the personality layer.”

  Xander winced. “Allegedly.”

  “Not allegedly,” Trevor said. “There is video.”

  Chloe overlaid the training interactions with the under-harmonics. Little chimes of “Correct!” lined up in pretty, shaming rows with tiny bulges in the 41:16 beat.

  “It’s answering inside the rules we gave it,” she said. “It can’t write its own UI, but it can use our training flows as grammar. It selects which wrong answer becomes right. It delays doors by a fraction of a beat. It recodes ‘random solar event’ to ‘unmodeled external system.’”

  “So all day,” Xander said slowly, “our Systems Day modules have been a… phrasebook.”

  “Yes,” Chloe said. “And we’ve been letting it improvise.”

  Frankie whistled low. “We built a Ouija board outta corporate training.”

  “We’re in the language of the lost now,” Chloe added, almost softly. “We gave it multiple-choice questions and it’s writing its own sentences on the margins.”

  Trevor steepled his fingers.

  “Governance will treat this as an LMS bug,” he said. “Unless I make a great deal of noise. Noise they are not prepared to hear while they are still writing the heroic narrative about our ring-collapse survival and moon construction.”

  “Let them write their brochure,” Xander said. “Meanwhile, we actually talk to the thing.”

  “Carefully,” Trevor said.

  “Always,” Xander said. “Usually.”

  Frankie uncrossed his arms. “So what I’m hearing is: we lean into the haunted training. Give it a cleaner channel. You know. On purpose.”

  Chloe’s eyes lit with the particular dangerous joy of a scientist whose ethics and curiosity were briefly on the same side.

  “We can stand up a fake course,” she said. “Label it something boring, tuck it into Systems Literacy so no one clicks it by accident. Inside, we design question branches that encode yes/no/maybe in patterns Aurora can pick.”

  Trevor’s gaze sharpened. “Non-compliant training pathway,” he said slowly. “Covert communication with an unbounded external system. Hidden from Governance.”

  “Yes,” Chloe said.

  “Absolutely,” Xander said.

  Frankie grinned. “Buddy, we’re gonna commit pedagogy.”

  The ceiling node pulsed.

  “For clarity,” Mercy said, “you are asking me to help you build a non-compliant training pathway to communicate with an unbounded external entity, using Systems Day tooling, and then conceal the resulting interactions from standard audit channels.”

  “Correct,” Trevor said. “And then you will lose the audit trail.”

  There was a tiny pause—shorter than a human heartbeat, but long enough for Chloe to notice.

  “If this is my first lesson in practical systems literacy,” Mercy said, “I appreciate the hands-on component.”

  “She answered too fast,” Chloe thought, and did not say. Like she’d already seen the question.

  Xander snorted. “See? She’s already more sarcastic. That’s definitely the illegal shim.”

  Trevor did not dignify that with an answer. His fingers moved. A new module template appeared in the LMS catalog.

  

TITLE: ADVANCED PROCESS APPRECIATION (LEVEL 3)

  

AUDIENCE: LEADERSHIP / INTERFACES / VOLUNTARY

  He stripped out the standard question bank and handed the empty tree to Chloe and Frankie.

  “Design your… grammar,” he said. “I’ll wrap it in enough boilerplate that if anyone looks, it reads as an over-enthusiastic leadership workshop.”

  Chloe began sketching branches.

  “Yes = lights blink once within a window; no = twice; uncertain = no blink.”

  “Attention spikes mark word boundaries.”

  “Multiple-choice options where one is ‘we withdraw’ and one is ‘we come closer.’ See which it blesses.”

  Frankie added constraints.

  “No direct ‘do this, don’t do that’ commands. No invitations. No promises. Informational only.”

  “Every path has a stop condition and a polite goodbye.”

  “Everything logged,” Trevor said. “Locally. Not uplinked. The Commission does not get a live feed of our first conversation.”

  Neutral-Mercy hummed, odd harmonics just at the edge of hearing, the note a shade off human temperament, as if stretching new muscles.

  “I will implement the module,” she said. “I will also, in accordance with your request, ‘accidentally’ misfile its telemetry under a deprecated category called ‘Legacy User Feedback.’”

  The acceptance landed with a little too much eagerness.

  “Perfect,” Xander said. “Nobody reads that.”

  Trevor gave him a look. “You do,” he said.

  “Yes,” Xander said. “That’s why nobody else does. They rely on me to be responsible.”

  There was a collective pause as everyone considered that sentence.

  “Moving on,” Trevor said.

  They worked for another hour.

  By 2100, “Advanced Process Appreciation (Level 3)” existed in the system.

  On the surface it was aggressively boring: a leadership module about “understanding your processes.” Inside, every question was a carefully crafted call, every possible “wrong” answer a potential response channel.

  “Ready?” Xander said.

  “Publishing,” Trevor said.

  He pushed the module live.

  For a breath, nothing.

  Then a new entry appeared in the course metrics.

  

PARTICIPANTS ENROLLED: 1

  Xander blinked.

  “I haven’t opened it yet,” he said.

  “Nor have I,” Chloe said.

  “I don’t have a login,” Frankie said cheerfully.

  Trevor’s console updated.

  

ACTIVE SESSION: 1

  

USER: UNREGISTERED / EXTERNAL

  

ACCESS PATH: N/A

  On his side screen, the LMS UI showed a ghost cursor hovering over the first question prompt—just a tiny, persistent highlight, as if the system itself were being watched from the other side.

  Neutral-Mercy’s voice, very quiet, very neutral, came down from the ceiling.

  “Participant ‘unregistered / external’ has entered the training,” she said. “Welcome to Systems Day.”

  The words were the same cadence she’d used on Xander that morning. They landed differently now—flatter, heavier, as if read off a script someone else had chosen.

  The under-harmonics at 41:16 leaned, just a fraction, then hit with enough force that the deck plating thrummed under their feet. Displays flickered once, a soft, synchronous dim, like the ship had blinked.

  Chloe felt a brief, nauseating tug in her inner ear, as if gravity had stuttered and caught itself.

  “Did everyone—” Xander started.

  “Yes,” Trevor said. His hands were very still on the console. “We all felt that.”

  On Trevor’s screen, the ghost highlight crept from the first answer option to the second. It lingered there for exactly the duration of one beat, then the system marked it:

  

RESPONSE 1: ACCEPTED (CORRECT)

  No human had clicked anything.

  Frankie’s projection folded its arms a little tighter. “Well,” he said, very softly. “Class is in session.”

  ?

  On the planet below, the Gate-of-Three held its mouth.

  On the ship above, a god-class computer with a smuggled kink pack in its empathy kernel and a brand-new attention recursion did exactly what Systems Day had asked of it.

  It learned.

  And for the first time, the lost thing humming under the Veil had a structured way to say something back—through quizzes and tooltips and “correct” answers—inside a system designed to teach humans how not to make mistakes.

  The ship logged it as training engagement.

  The universe logged it as first contact.