Work Text:
The distress call arrived without drama—no panic in the voice, no frantic overlap of multiple speakers—just a steady transmission from a young Federation colony that understood exactly what was coming for it.
A long-range survey had identified the object hours earlier: a dense, fast-moving asteroid on a trajectory that would intersect the planet’s atmosphere with catastrophic results. The colony had neither the infrastructure nor the firepower to do anything about it. They had done what Starfleet expected of them. They had called for help.
The Enterprise was close enough to answer.
On the bridge, Jean-Luc Picard listened to the final portion of the transmission, hands folded lightly in front of him, his expression composed but attentive. Routine did not mean trivial; it meant familiar. The situation was clear, the solution straightforward.
“Time to intercept?” he asked.
“At current velocity, the asteroid will enter the upper atmosphere in approximately three hours, forty-two minutes,” replied Data, his tone even. “We will be in effective phaser range in eleven minutes.”
Picard gave a small nod. “Very well. Let’s not keep them waiting.”
The ship slipped into position with the quiet precision that had become second nature to her crew. On the main viewer, the asteroid resolved from a distant glint into a jagged, irregular mass, tumbling slowly as it cut across the starfield. It was not particularly large by cosmic standards, but its composition—dense, metallic, and cohesive—meant that an impact would transfer its energy with devastating efficiency.
At the tactical station, Worf stood rigid, eyes fixed on his display. “Target locked,” he reported. “Phasers standing by.”
“Proceed,” Picard said.
Worf did not hesitate. “Firing.”
A lance of coherent energy snapped from the Enterprise, brilliant and precise, crossing the intervening space in a fraction of a second.
It missed.
Not by much—close enough that, at first glance, it might have been mistaken for a near-perfect strike—but it passed cleanly along the asteroid’s flank, dissipating into the void beyond without so much as grazing its surface.
There was a brief, almost imperceptible pause on the bridge, the kind that followed a result that did not fit expectation.
Riker turned in his seat to look at Worf. “What happened, Mister Worf?”
Worf frowned slightly. “Phaser discharge nominal. Target was… not affected.”
Picard leaned forward a fraction. “Mr. Data?”
Data’s eyes flicked across his console. “Sensor telemetry confirms the phaser beam did not intersect the asteroid’s mass.”
Picard’s gaze shifted back to Worf. “Adjust and fire again.”
“Aye, Captain.”
Worf re-established the targeting solution, his hands moving with practiced certainty. The asteroid’s rotation, vector, and relative motion were all accounted for; the system compensated automatically for variables far more complex than this.
“Firing.”
The second beam flashed outward, identical in intensity and duration to the first.
It missed in exactly the same way.
This time the silence lingered a moment longer.
Worf’s brow tightened as he did a quick diagnostic. “Target lock remains stable. Phaser systems are functioning within normal parameters.”
Picard’s expression did not change, but there was a new edge beneath his calm. “Mr. Data?”
“The deviation is consistent,” Data said, studying the incoming data with quiet focus. “The point of closest approach between the beam and the asteroid matches the previous discharge within a margin of less than one percent.”
“In other words,” Picard said slowly, “we are missing… the same way.”
“Yes, sir.”
Picard considered that for only a heartbeat. “Mr. Worf, vary the firing solution. Adjust for the asteroid’s rotation manually. I want a different pattern.”
Worf inclined his head. “Understood.”
This time the targeting was not a simple repeat. He introduced a deliberate offset, compensating for the observed miss rather than trusting the original solution. The phaser emitters shifted fractionally, aligning to a new set of coordinates.
“Firing.”
The beam lanced out again—sharp, controlled, precise.
It missed.
But not the same way.
The path of the beam diverged from the previous two, cutting a different line through space, passing the asteroid at a new angle and a new distance. It was still wrong—clearly, unmistakably wrong—but the error had changed.
Worf exhaled once, controlled but unmistakably displeased. “The modification altered the point of impact. However, the target was not struck.”
On the bridge, the problem settled into place, no longer a fluke, no longer an anomaly that could be dismissed with a simple recalculation. The Enterprise was not failing to aim.
It was aiming consistently—and incorrectly.
Data’s head tilted slightly as he reviewed the compiled telemetry from all three shots. For a moment he said nothing, and then, with the same calm precision that marked all of his observations, he spoke.
“The errors are systematic,” he said. “They are neither random nor the result of stochastic variation. Each firing solution is internally consistent with the targeting data provided at the time of discharge.”
Picard’s eyes narrowed slightly. “Explain.”
Data looked up from his console. “The phaser systems are performing exactly as instructed. The discrepancy lies between the calculated target position and the asteroid’s actual position in space.”
A quiet, unsettling clarity settled over the bridge.
Picard leaned back in his chair, fingers steepled lightly. “So the fault is not with the weapon…”
Data met his gaze. “No, Captain.”
“It is with our understanding of where the target is.”
A beat passed.
Then Data added, almost as a conclusion rather than a warning:
“This is not random error.”
The bridge did not descend into chaos. There was no urgency yet, no rising panic—only a quiet tightening of focus as the nature of the problem clarified itself.
Riker leaned forward slightly in his chair. “Mr. Data, can you compensate?”
Data was already working, his hands moving across the console with measured precision. The three missed shots had not been wasted; they had drawn a shape in space, a pattern that could be measured, quantified, and—if properly understood—corrected.
“Yes, Commander,” he said after only a moment. “The deviation between calculated and actual target position is consistent enough to model. I can derive a corrective offset based on the previous discharges.”
On the main viewer, the asteroid continued its slow, implacable rotation, unaware of the attention focused upon it. Time was still on their side, but no one on the bridge was inclined to spend more of it than necessary.
Riker nodded once. “Do it.”
Data’s eyes flicked upward briefly, then back to his console. “Applying correction to the targeting solution… compensating for observed error vector.” He paused, then added, “Recommend manual verification before firing.”
At the tactical station, Worf’s posture remained rigid, but there was a subtle shift in his stance as he disengaged the standard targeting lock and began inputting the revised solution. The computer’s guidance remained present, but now it was being overridden—guided rather than obeyed.
“Correction received,” Worf said. “Aligning phaser emitters to adjusted coordinates.”
There was a moment—brief, but noticeable—where the Enterprise held its breath.
“Ready,” Worf said.
Picard did not hesitate. “Fire.”
The phaser beam snapped outward again, brilliant and controlled, its path now subtly altered from the previous attempts. For an instant it seemed no different, just another precise line cast into the void.
Then it struck.
The impact was immediate and decisive. Energy flared across the asteroid’s surface, bright enough to wash the viewer in white for a fraction of a second before resolving into a cascading fracture. The mass split along its weakened structure, sections breaking apart and dispersing, their trajectories altered just enough to ensure that what remained would burn harmlessly in the planet’s upper atmosphere.
On the bridge, the tension that had never fully surfaced now released in a quiet, collective exhale.
Worf watched the fragmentation pattern stabilize. “Target neutralized,” he reported. “Residual debris poses no threat to the colony.”
Picard allowed himself a small nod. “Very good.”
For a moment, that could have been the end of it. A routine mission complicated briefly, then resolved through skill and adaptability. The kind of incident that would merit a line in the log and little more.
But Picard did not look away from the viewer.
“Mr. Data,” he said, his voice measured, “confirm the targeting correction.”
Data reviewed the final firing solution and its result. “The adjusted coordinates produced the expected outcome. The applied offset accurately compensated for the observed deviation.”
“And without that adjustment?”
“The phaser beam would have missed the target,” Data replied simply.
Picard leaned back slightly, his gaze shifting from the viewer to the readouts along the edge of his chair. “Run a full diagnostic on phaser targeting, sensor alignment, and navigational reference systems.”
“Aye, Captain.”
There was a brief pause as the computer processed the request. On another day, under other circumstances, it would have been a formality.
Data’s eyes moved across the incoming results, and for just a fraction of a second, there was the faintest hint of hesitation.
“Diagnostics complete,” he said.
Picard waited.
“All systems are operating within normal parameters.”
The words hung in the air longer than they should have.
Worf turned slightly at his station, as if expecting some clarification that did not come. “Phaser systems are fully functional,” he added, almost defensively. “There is no indication of malfunction.”
Picard’s expression did not change, but something in it hardened—an edge of dissatisfaction that had nothing to do with the now-neutralized asteroid.
“Mr. Data,” he said quietly, “you are telling me that our targeting systems are functioning perfectly…”
“Yes, Captain.”
“…and yet we required a manual correction to hit a stationary object.”
Data inclined his head. “That is correct.”
Picard’s gaze settled forward again, unfocused now, no longer on the debris field but somewhere beyond it—on the implication rather than the event.
“The ship says it was right,” he said, almost to himself.
A beat passed.
Then, more sharply:
“I would very much like to know why it was wrong.”
Picard did not raise his voice, and he did not need to. By the time the Enterprise had cleared the debris field and settled into a steady orbit above the colony world, the order had already moved through the ship with quiet efficiency.
“Full investigation,” he had said.
Nothing more was required.
In Engineering, consoles were active across multiple stations, diagnostic routines cascading in layered sequences that would have taken a lesser crew hours to coordinate. Here, it unfolded with practiced fluency.
At the central control platform, Geordi stood with one hand braced lightly against the railing, his attention split between overlapping readouts. He did not look concerned—not yet—but there was a tightness to his focus that suggested the problem had already refused to yield to the first, simplest explanations.
“Alright,” he said, more to the room than to any one person. “Let’s start clean. Phaser emitters, targeting processors, sensor alignment, navigational reference—everything that feeds into where we think ‘there’ is. I don’t want assumptions. I want confirmation.”
At a nearby station, Miles O'Brien nodded once and turned back to his console. If there was a physical fault to be found, he would find it—or rule it out.
He began with the emitters themselves.
The phaser arrays along the Enterprise’s hull were not crude weapons bolted onto a frame; they were integrated systems, their alignment governed down to tolerances that bordered on the absurd. Thermal expansion, structural flex under warp stress, microfractures from repeated discharge—any of these could introduce error, and all of them were continuously compensated for.
O’Brien ran the alignment routines anyway.
One by one, the results came back.
Emitter segments: within tolerance.
Power distribution: stable.
Phase synchronization: nominal.
Mechanical alignment relative to hull geometry: exact.
He frowned slightly, not because anything was wrong, but because nothing was.
He tapped a final command, forcing a deeper-level check, one that bypassed the higher-level abstractions and went directly to raw sensor feedback. The numbers did not change.
O’Brien exhaled once, then spoke without looking up. “Emitters are clean, Commander. Alignment is dead-on. If there’s an error, it’s not in the hardware.”
Geordi nodded, already moving on. “Alright. That’s one layer down.”
Across the room, Data stood at a dedicated terminal, his posture perfectly still as streams of information moved across the display. Where O’Brien had looked outward—to the physical structure—Data looked inward, tracing the logic that connected perception to action.
He was not searching for a fault in the conventional sense. He was searching for contradiction.
“Targeting solution inputs are consistent with sensor data at the time of each discharge,” he said after a moment. “No discrepancies exist between recorded target position and the coordinates supplied to the phaser control systems.”
Geordi glanced over. “Meaning what we thought we were aiming at… matched what we told the phasers to hit.”
“Yes,” Data said. “The phaser systems executed their instructions with complete accuracy.”
Geordi leaned back slightly, considering that. “And the sensors? Any chance they were feeding us bad data?”
Data’s fingers moved once, bringing up a comparison set. “I have cross-referenced primary sensor readings with secondary and tertiary arrays. Additionally, I have compared our data with independent passive observations recorded during the engagement.”
“And?”
“There is no measurable divergence,” Data replied. “All sensor systems agree on the asteroid’s position and trajectory within expected tolerances.”
Geordi’s mouth tightened a fraction. “So the sensors agree with each other…”
“Yes.”
“…and the targeting system agrees with the sensors…”
“Yes.”
“…and the phasers did exactly what the targeting system told them to do.”
“That is correct.”
Geordi looked back to his console, then up again, as if expecting the pieces to rearrange themselves into something more cooperative.
“Then why did we miss?” he asked, not really expecting an immediate answer.
Data did not respond at once. Not because he lacked one, but because none of the available answers satisfied the conditions of the problem.
Time passed—not in long stretches, but in accumulating minutes that should have been sufficient.
Geordi ran software diagnostics next.
If there had been a fault in the code—corrupted routines, misapplied updates, timing errors in execution—it would reveal itself under scrutiny. Starfleet systems were not immune to error, but they were built to detect it, isolate it, and report it.
He initiated a full sweep of the targeting software stack, from high-level predictive algorithms down to the firmware controlling emitter synchronization.
The results came back in layers.
No corrupted modules.
No execution errors.
No unexpected deviations from baseline behavior.
He frowned and pushed deeper, forcing a verification against stored system images—comparing current operational code to known-good versions. The comparisons aligned perfectly.
Geordi straightened slowly, one hand coming to rest on the console as he considered what he was seeing.
“Software checks out,” he said at last. “No faults, no glitches, no bad code paths. Everything’s behaving exactly the way it’s supposed to.”
O’Brien looked up from his station. “Hardware’s clean.”
Data added, “All subsystems are internally consistent.”
The three statements hung in the air, each reinforcing the others, each closing off a path that might have led somewhere useful.
Geordi let out a quiet breath and rubbed the back of his neck. “That’s not possible.”
He didn’t mean it as a figure of speech.
If the hardware was aligned, the sensors were accurate, the software was correct, and the systems agreed with one another, then the shot should have hit. There was no room in that chain for a miss—no place where error could exist without being exposed by contradiction.
And yet the miss had happened. Not once, but repeatedly, with a consistency that argued against randomness and a precision that argued against failure.
Geordi turned away from the console and took a few steps across the platform, his mind running through the sequence again.
“We missed the target,” he said slowly. “Multiple times. Same deviation, same magnitude, until we compensated manually.”
“Yes,” Data confirmed.
“And every system we have says that shouldn’t have happened.”
Geordi stopped, looking out over the controlled chaos of Engineering, where everything was working exactly as designed.
“That means one of two things,” he said.
O’Brien glanced over. “Which are?”
“Either we’re missing something…” Geordi said, “…or the system is.”
Data’s head turned slightly, focusing on him.
Geordi met his gaze for a moment, then looked back at the consoles, at the streams of data that agreed with each other so completely that they left no room for doubt—and no room for explanation.
“Run it again,” he said quietly. “All of it. I want to see where this breaks.”
But as the diagnostics cycled once more, as the same confirmations returned in the same unhelpful perfection, the realization settled in—not all at once, but with the slow, inexorable weight of a door that refused to open.
They were not chasing a malfunction.
They were standing inside a system that insisted it was right.
And for the moment, they had no way to prove it wrong.
They had already run the diagnostics twice.
No one said it out loud, but the third pass was not about expecting a different result. It was about refusing to accept the one they already had.
In Engineering, the rhythm had shifted. The initial momentum—fast checks, clean eliminations—had given way to something slower, more deliberate. The obvious paths had closed. What remained was narrower, less certain.
At the central platform, Geordi watched another set of confirmations scroll past his display and resisted the urge to cancel the run before it completed. He let it finish anyway. The system deserved that much consistency, even if it returned nothing useful.
“Same results,” he said, more out of habit than necessity. “No drift in emitters, no desync, no software faults, no bad sensor feeds. Everything lines up.”
Across from him, O'Brien folded his arms, expression tight. “If I didn’t know better, I’d say the ship’s firing exactly where it’s supposed to.”
“It is,” came Data’s reply from the adjacent console. “The phaser discharge coordinates correspond precisely to the targeting solution generated at the moment of firing. There is no deviation within the system.”
Geordi glanced at him. “Yeah. That’s the problem.”
A brief silence followed—not empty, but dense with the absence of contradiction. Every test they had run agreed with every other test. Every subsystem confirmed the others. The Enterprise, in all her complexity, was behaving as though nothing were wrong.
And yet—
Geordi exhaled slowly and pushed himself upright from the console. “Alright. If nothing’s broken, then we’re asking the wrong question.”
O’Brien looked over. “And what question is that?”
Geordi didn’t answer immediately. He turned, pacing once across the platform, then back again, eyes unfocused as he ran through the chain in his head.
“Hardware’s good,” he said. “Software’s good. Sensors agree with targeting, targeting agrees with phasers. No disagreements anywhere in the system.”
Data inclined his head slightly. “Correct.”
Geordi stopped. “So we’ve been looking for something that disagrees with everything else.”
“Yes.”
“But what if that’s the wrong way to look at it?” Geordi said.
Before Data could respond, a voice—quieter, more hesitant—spoke from the far side of the room.
“Then… there wouldn’t be anything to find.”
Geordi turned.
At a secondary station, half-shadowed by the glow of his console, Reg Barclay stood with his hands hovering uncertainly over the controls, as though he were not entirely convinced he should have spoken at all.
Geordi’s expression softened slightly. “Go ahead, Reg.”
Barclay shifted his weight, clearly uncomfortable with the attention. “I mean… if all the systems agree with each other, then they’d all pass their own checks, right? Because they’re… they’re comparing themselves to each other.”
O’Brien frowned. “That’s how the diagnostics are supposed to work.”
“Yes, Chief, but—” Barclay stopped, then started again, more carefully. “What if the system isn’t failing… what if it’s working from the wrong starting point?”
The words hung there, simple and unadorned.
Geordi didn’t move for a second.
Data turned his head, eyes fixing on Barclay with sudden intensity. “Please clarify.”
Barclay swallowed. “The calibrations. The baseline data. Everything references that, doesn’t it? Sensors, targeting, emitter alignment—they all use the same… initial frame of reference.”
“That is correct,” Data said.
“So if that starting point was wrong…” Barclay continued, gaining a little confidence as he went, “then everything built on it would still agree. It would just all be wrong in the same way.”
Silence settled across Engineering again, but this time it was different. Not empty—focused.
Geordi turned back to his console, already moving. “Baseline alignment tables,” he said. “Pull the last verified calibration set and compare it to current operational values.”
Data’s hands moved in parallel. “Accessing historical calibration data. Cross-referencing with present system state.”
For a moment, nothing changed. The data streams flowed as they had before, orderly and cooperative.
Then, subtly, a divergence appeared.
Data’s eyes tracked it instantly. “There is a discrepancy.”
Geordi leaned in. “Where?”
“Primary targeting reference frame,” Data said. “Offset relative to last verified baseline. Magnitude is consistent with the deviation observed during phaser discharge.”
O’Brien stepped closer. “You’re saying the whole system’s been recalibrated?”
“Yes,” Data replied. “To a different reference.”
Geordi stared at the readout, the numbers resolving into something that finally made sense—not because they were correct, but because they explained the error.
“Not drift,” he said quietly. “Replacement.”
He straightened. “When did it happen?”
Data’s fingers moved, tracing the change backward through system logs. “During a scheduled maintenance cycle. Automated calibration routine.”
“Which one?” Geordi asked.
“Targeting alignment verification subroutine,” Data replied. “Executed approximately twelve hours prior to the engagement.”
O’Brien shook his head. “Those routines don’t just rewrite the baseline. They verify it.”
“They can also update it,” Geordi said, already pulling up the corresponding logs. “If they’re flagged to commit new data.”
Barclay leaned closer to his own console, scanning rapidly now. “There’s… there’s an entry here,” he said, his voice tightening. “Calibration run completed. Status—validated. And… and it was written to the baseline store.”
Geordi’s eyes narrowed. “Validated against what?”
Barclay hesitated. “That’s the thing. It doesn’t say. It just… passed.”
Data shifted his focus. “Tracing origin of calibration dataset.”
The system responded instantly.
“Source identified,” Data said.
Geordi looked up. “Where did it come from?”
Data did not hesitate.
“Lieutenant Daniel Harkins,” he said.
There was a brief pause as the name settled. Geordi glanced across Engineering, scanning the stations until he spotted him—young, focused, shoulders slightly hunched over a console as he worked through a diagnostic routine that, until a moment ago, had seemed entirely unrelated to anything of consequence.
“Harkins,” Geordi called.
The lieutenant looked up immediately, a flicker of surprise crossing his face before he straightened. “Sir?”
“Could you come over here a minute?”
There was nothing accusatory in Geordi’s tone, but the attention of the room had shifted all the same. Harkins stepped away from his station and crossed to the central platform, becoming increasingly aware of who was waiting for him—Geordi, Data, O’Brien, Barclay—all focused, all expectant.
“Yes, Commander?”
Geordi kept his voice even. “We’re tracing a calibration dataset that was written into the targeting baseline about twelve hours ago. According to the logs, it originated from your access credentials.”
Harkins blinked once, processing that. “My credentials?”
“That’s right,” Geordi said. “We’re trying to understand what you were working on.”
There was a brief moment—just enough to suggest nerves—before Harkins nodded. “I… yes, sir. I think I know what that might be.”
Geordi’s expression didn’t change, but he inclined his head slightly. “Go ahead.”
Harkins glanced once at the consoles around them, then back to Geordi. “I’ve been running a series of alignment tests. Targeting precision under variable conditions—thermal drift, structural stress, minor sensor lag. I’ve been trying to tighten the predictive model so the system compensates a little faster, a little cleaner.”
O’Brien folded his arms, listening. Data watched without interruption.
“For how long?” Geordi asked.
“A few weeks,” Harkins said. “Mostly in my off cycles. It’s not a major system rewrite or anything—just refinements to how the calibration routine interprets incoming data.”
Data spoke then, his tone neutral but attentive. “Your modifications are to improve internal consistency between sensor inputs and targeting solutions?”
Harkins blinked again, slightly surprised. “Yes, sir. That was the idea.”
Geordi gave a small nod. “It’s a good idea.”
The tension in Harkins’ shoulders eased a fraction, though the uncertainty remained. “I was running the latest iteration last night,” he continued. “Just a test pass. I fed it simulated conditions, let it generate a calibration solution, and checked the results against expected values.”
“And?” Geordi prompted.
“It passed,” Harkins said. “Everything lined up. No internal discrepancies. It actually performed better than the current baseline in the simulation.”
Barclay glanced up at that, interest flickering across his face.
“What did you do after the test?” Geordi asked.
Harkins shifted his weight slightly. “I saved the results. In the sandbox environment. Same as always. Logged the run, tagged it for later review. I was going to come back to it today, maybe run a few more variations before I submitted anything for evaluation.”
“You didn’t commit it to the live system?” Geordi asked.
“No, sir,” Harkins said immediately. “I wouldn’t do that without review. It wasn’t ready for that.”
Data had already moved to a nearby console. “Accessing Lieutenant Harkins’ sandbox environment.”
Harkins stepped aside as Data worked. “Everything should still be there,” he said, a little more quickly now. “The simulation parameters, the calibration output, the logs—nothing’s been touched since last night.”
The display resolved in front of them: the test environment exactly as Harkins had described it. Parameters intact and data sets preserved. No indication of a manual export or promotion to live systems.
Data’s eyes moved across the information. “There is no record of a manual transfer from this environment to the primary calibration baseline.”
Geordi’s gaze shifted from the display to Harkins. “Walk me through exactly what you did when you finished.”
Harkins swallowed once, then nodded. “I finalized the run, verified the output against the simulation model, and saved the dataset. Standard sandbox save—no external commit flags. Then I logged out.”
“That’s it?” O’Brien asked.
“That’s it,” Harkins said. “I didn’t even access the live calibration controls.”
Barclay leaned in, comparing the sandbox data to the baseline they had already identified as incorrect. His brow furrowed.
“It’s the same dataset,” he said quietly. “The structure matches. The values—” he hesitated, then looked up—“they’re identical.”
Geordi’s eyes narrowed slightly. “So the data that’s currently defining our targeting baseline…”
“…is coming from his test run,” O’Brien finished.
Harkins stared at the console, confusion overtaking the earlier nervousness. “That’s not possible. It shouldn’t have left the sandbox.”
Data straightened slightly. “Lieutenant Harkins is correct. Sandbox environments are isolated from operational systems. Direct promotion of data requires explicit authorization.”
Geordi looked from Data to the display, then back again. “Then how did it get there?”
Data’s head tilted a fraction, processing. “The dataset was flagged as validated by the calibration routine.”
Harkins nodded reflexively. “Yes, but that just means it passed internal checks. It doesn’t—”
He stopped.
Data continued, his tone unchanged. “The automated maintenance cycle subsequently incorporated the most recent validated calibration dataset into the baseline alignment store.”
O’Brien blinked. “You’re saying the system pulled it in on its own?”
“Yes.”
A quiet beat passed.
Harkins shook his head, more to himself than anyone else. “It’s not supposed to do that. The sandbox isn’t even in the same chain. It can’t—”
Geordi’s expression hardened slightly, not in anger, but in recognition.
“It did,” he said.
He looked back at the data, at the clean, consistent alignment values that had seemed so trustworthy only minutes ago.
“The system saw a dataset that passed every check it knows how to run,” he said slowly. “And it decided it was superior to baseline, and therefore, that made it good enough to use.”
Data inclined his head. “That is consistent with the observed behavior.”
Harkins stared at the display, the implication settling in with uncomfortable clarity. “But the simulation isn’t reality,” he said. “It’s… it’s internally consistent, but it’s not anchored to actual space. It’s just a model.”
“Yes,” Data said.
Another beat.
Geordi exhaled slowly. “Which means we didn’t just load bad data.”
He glanced at O’Brien, then Barclay, then finally back to Harkins.
“We loaded data that was perfectly valid… for the wrong frame of reference.”
No one spoke for a moment.
Then Harkins, quieter now: “I didn’t push it live.”
Geordi shook his head slightly. “No. You didn’t.”
His gaze shifted back to the console, to the system that had taken good work and applied it in a way no one had intended.
“The system did.”
The correction itself was almost disappointingly simple.
Once the source of the error was understood, the solution followed with the same quiet inevitability that had marked the rest of the investigation. The problem had never been hidden; it had simply been accepted.
At the central console, Geordi worked quickly now, pulling up the last verified calibration set—data that had been tested against real-space observations, not simulations, not internally consistent models, but reality itself.
“Restoring baseline alignment to last confirmed state,” he said. “Before the maintenance cycle.”
Data stood beside him, monitoring the transition as it propagated through the system. “Reinitializing targeting reference frame,” he added. “Synchronizing sensor input with restored baseline.”
Across the platform, O'Brien ran a parallel check, verifying that the physical emitters remained aligned with the updated coordinates. “Emitter geometry unchanged,” he reported. “They’ll follow whatever frame you give them.”
“Good,” Geordi said. “Let’s make sure it’s the right one this time.”
The recalibration sequence completed in stages, each subsystem falling back into alignment not with each other—but with a reference that had been confirmed against the outside world. It was a subtle distinction, but a critical one.
“Calibration complete,” Data said.
Geordi nodded once. “Let’s test it.”
On the bridge, the mood had shifted. The immediate danger had passed, but the question had not. Picard sat forward in his chair, watching the stars drift slowly across the main viewer, waiting.
Picard’s commbadge chirped.
“Captain,” Geordi’s voice came over the comm. “We traced the issue. A test calibration dataset was incorrectly promoted to the targeting baseline during an automated routine. Everything stayed internally consistent—but it was offset from real space.”
A brief pause.
“We’ve restored the correct baseline and recalibrated all affected systems. You should have full targeting accuracy now.”
Picard nodded slightly. “Understood. Thank you, Mr. La Forge.”
As the channel closed, the turbolift doors at the rear of the bridge parted with a soft hiss, and Data stepped out, crossing calmly to the operations station and resuming his position without comment.
Picard inclined his head slightly. “Very well. Mr. Worf?”
At tactical, Worf had already selected a suitable test object—a fragment of the earlier debris field, small enough to pose no risk, large enough to register clearly on sensors.
“Target acquired,” he said. “Phasers ready.”
Picard did not hesitate. “Fire.”
The beam lanced outward, precise and controlled, cutting cleanly across the intervening space.
This time, there was no ambiguity.
The fragment vanished in a brief flare of light, exactly where the system said it would be.
Worf studied his console for a moment, then gave a short, satisfied nod. “Direct hit.”
No one spoke for a second, as if allowing the simplicity of that result to settle.
Picard leaned back slightly. “Mr. Data?”
“All systems are now aligned with external reference,” Data replied. “There is no measurable deviation between calculated and actual target position.”
Picard allowed himself a small breath, not quite relief, but something adjacent to it. “Very good.”
Later, in the ready room, the tension had drained away, leaving behind something quieter, more reflective.
Picard stood near the viewport, hands clasped behind his back, the colony world turning slowly below. It looked unchanged, untouched by what had nearly occurred. From orbit, it was always easy to believe that problems had been simple.
Data stood across from him, composed as ever.
“The system behaved in a manner consistent with its programming,” Data said.
Picard did not turn immediately. “Yes,” he said after a moment. “That’s rather the point, isn’t it?”
Data regarded him. “The calibration dataset satisfied all internal validation criteria. The automated routine therefore incorporated it as an improved reference.”
Picard turned then, his expression thoughtful rather than troubled. “And yet it was wrong.”
“Yes, Captain.”
Picard moved slowly back toward his desk, considering that. “It strikes me, Mr. Data, that we place a great deal of trust in our systems. We ask them not only to perform tasks, but to evaluate themselves—to tell us when they are correct.”
Data inclined his head slightly. “That is a necessary function given the complexity of those systems.”
“Indeed,” Picard said. He paused, then allowed the faintest hint of a smile. “But perhaps not a sufficient one.”
Data’s gaze remained steady. “The error did not arise from a failure of logic, Captain. The system’s conclusions were valid within the framework of the data it was given.”
Picard nodded once. “Yes. It reasoned perfectly… from a flawed premise.”
A brief silence followed, not uncomfortable, but contemplative.
“We corrected the premise,” Picard said at last. “And the system corrected itself.”
Data considered that. “However, the conditions that allowed the erroneous dataset to be accepted remain under review.”
Picard’s expression sharpened slightly, though the calm never left it. “As they should be.”
He moved back toward the viewport, looking out once more at the world below.
“Trust,” he said quietly, “is a valuable thing, Mr. Data. But it must be earned—and, from time to time… verified.”
Data nodded once. “A prudent approach.”
Picard allowed himself a final, measured glance at the stars before turning away.
“See that it is,” he said.