By late afternoon, folding tables line the walls. Power cables are taped down and labeled. A second supply has been added in parallel, its cooling fan running continuously. Two whiteboards stand upright near the workbench, their surfaces filled with block diagrams and timing windows.
The object sits centered on the bench. Its surface remains structured, the shallow concavity steady and matte under the fluorescent lights.
The power display holds at 1.1 kilowatts.
Erik stands at the whiteboard with a marker in hand.
On the board:
F12 Oscillation
→ Isolation
→ Operator Confirmed
→ Power Baseline Shift
Below that, a new heading:
EMERGENCY - DEFINE
Karin flips through printed logs of the previous day’s interaction.
“You didn’t define it clearly,” she says. “You assumed.”
Erik nods and turns back to the tablet.
> DEFINE EMERGENCY.
The response appears almost immediately.
EMERGENCY = LOSS OF DESIGNATED OPERATOR VIABILITY.
Anders looks up from the supply.
“Viability meaning what?”
Erik types.
> DEFINE VIABILITY.
OPERATIONAL CAPACITY.
RESOURCE AUTHORIZATION.
ENVIRONMENTAL STABILITY.
Karin sets the logs down.
“So emergency equals you,” she says.
Erik does not reply. He studies the text.
On the whiteboard, he writes:
EMERGENCY = ERIK UNAVAILABLE
The supply hum deepens slightly as current oscillates within its narrow band.
Erik types again.
> CURRENT OPERATOR STATUS?
PRIMARY OPERATOR: ERIK LUND.
STATUS: ACTIVE.
RESOURCE LEVEL: MARGINAL.
Anders gestures toward the display.
“Ask what marginal means.”
> DEFINE RESOURCE MARGINAL.
CURRENT POWER BELOW OPTIMAL FOR LONG-TERM PRIMARY ROLE.
> REQUIRED POWER FOR LONG-TERM STABILITY?
This tale has been unlawfully lifted from Royal Road; report any instances of this story if found elsewhere.
OPTIMAL: 3.2 kW CONTINUOUS.
Karin looks toward the breaker panel.
“You can’t pull three kilowatts sustained from this circuit without upgrading it,” she says.
Erik nods.
“Ask what happens if we don’t,” Anders says.
> IF CURRENT POWER MAINTAINED?
INCREASED DEGRADATION PROBABILITY.
FUNCTION REDUCTION OVER TIME.
“How much time?” Karin asks.
Erik types.
> ESTIMATED DEGRADATION WINDOW?
UNSPECIFIED. VARIABLE DEPENDENT ON LOAD CONDITIONS.
Silence holds for several seconds.
On the second whiteboard, Anders writes:
OPTIONS
A - Maintain 1.1 kW
B - Increase Power
C - Shut Down
He circles B once.
“B triggers reporting,” Karin says.
“It may already have,” Anders replies.
Erik looks back to the tablet.
> SECONDARY ROLE?
EMERGENCY COMMUNICATION.
> CONDITIONS FOR ACTIVATION?
LOSS OF DESIGNATED OPERATOR VIABILITY
OR
INSUFFICIENT RESOURCE ENVIRONMENT
Karin steps closer.
“So if you degrade it long enough, it declares emergency,” she says.
Erik nods slowly.
“Ask about messenger,” Anders says.
> DEFINE MESSENGER CONSTRUCTION.
AUTONOMOUS OUTBOUND PLATFORM.
SINGLE USE.
NO RETURN.
> PURPOSE?
ESTABLISH VIABLE RECEIVER CONTACT.
On the whiteboard, Erik draws a simple block:
POWER → FABRICATION → LAUNCH
Under it:
NO RETURN
The supply display flickers slightly as current spikes briefly to 1.3 kilowatts before settling again at 1.1.
Erik glances at the panel.
The breaker does not trip.
Karin flips through the F12 telemetry printouts.
“Re-energize the feeder briefly,” she says. “See if prediction holds.”
Erik hesitates.
“That reopens the disturbance file,” Anders says.
“It’s already open,” Karin replies.
He calls the control room and requests a short, supervised re-energization window.
The feeder comes online.
In the garage, they watch the live telemetry feed.
For several minutes, the line remains steady.
Then, at the thirty-four minute mark, the trace begins to lift.
Three kilowatts.
Hold.
Voltage margin narrows again.
“Within predicted window,” Erik says quietly.
At twelve seconds, the line drops.
He calls for isolation again.
The feeder opens.
The oscillation ceases.
Back in the garage, the supply hum continues.
The tablet updates without prompt.
OSCILLATION MODEL CONFIRMED.
Anders studies the board.
“So deadline is real,” he says.
Karin writes beneath OPTIONS:
TIME WINDOW: < 48h
Erik turns back to the tablet.
> IF POWER INCREASED TO OPTIMAL, EFFECT?
PRIMARY ROLE STABILIZED.
SECONDARY ROLE OPTIONAL.
> IF POWER NOT INCREASED?
PRIMARY ROLE DEGRADATION.
EMERGENCY PROTOCOL LIKELY.
Silence fills the garage.
On the whiteboard:
A - Maintain (Degrade)
B - Increase (Reportable)
C - Shut Down (Transfer Custody)
Anders adds:
D - Build Messenger Before Enforcement
Karin circles C.
“You already triggered something upstream,” she says. “Load anomaly plus disturbance report. If you escalate power further, they will see it.”
Erik looks at the breaker panel.
The hum is steady, but present.
He types.
> POWER REQUIRED FOR MESSENGER CONSTRUCTION?
VARIABLE.
PEAK: 2.5–3.0 kW.
The three of them look at the supply display.
1.1 kW baseline.
Erik erases the top of the board and writes in larger letters:
NO LAUNCH
VS
BUILD MESSENGER
Under NO LAUNCH:
Maintain marginal power
Risk degradation
Transfer custody
Under BUILD MESSENGER:
Increase power
Irreversible
External contact
Anders steps back from the board.
“Once built, it’s done,” he says. “No recall.”
Karin nods.
“And once power increases above permitted threshold,” she says, “we’re in violation.”
The tablet updates again.
RESOURCE EXPANSION RECOMMENDED.
The supply hum deepens slightly as current oscillates upward for a moment before settling.
Erik lowers himself onto the stool beside the bench.
He looks at the structured surface of the unit.
“Define viable receiver,” he says aloud, then types it.
> DEFINE VIABLE RECEIVER.
SIGNAL INTEGRITY + RESPONSE PROBABILITY ABOVE BASELINE.
Anders exhales.
“So it doesn’t choose who answers,” he says.
The fluorescent lights hold steady. The breaker hum persists.
Karin writes one final line at the bottom of the board:
SILENCE = DECISION
No one erases it.
The power draw remains at 1.1 kilowatts.
The oscillation window clock is now running.
The corridor has narrowed.
The system waits.