Stabilisation apparente

A Different Final State

4: Apparent Stabilisation

The Secret Gateway

That evening, late on 12 May 2028, Élise returned to the laboratory alone.

She did not turn on the overhead lights.

Only the standby consoles cast pale rectangles across the metal surfaces. Behind the glass, the racks continued their regular breathing. The air conditioning had that relentlessly steady hum that made every movement more audible.

Élise placed her badge on the desk in front of the secondary terminal.

This workstation had not been used for several months. It had served for the first network integration trials, before David imposed strict separation between environments. The ports had been closed. The scripts archived. The gateways classified as obsolete.

Not deleted.

Only set aside.

Élise opened her black notebook. The notes from late April still fitted on a single page.

Test outside the controlled framework.
Observe whether constraints hold without explicit guidance.

The second line weighed more heavily than the first.

In her memory, David’s voice returned with irritating clarity.

We don’t take Julie outside the validated framework until the internal trajectories have stabilised.

He was right.

She knew it.

That was precisely what made it difficult to stop what she was doing.

The access light remained green. She still had permission to be there. Not to do this.

Her phone vibrated in her pocket.

A message from David.

Are you still at the lab?

Over the past few weeks, he had been sending this kind of message more often. Not just to keep tabs on her. Élise knew that, even if she sometimes refused to give him credit for it. David feared actions that left no official trace, because they destroyed everything he was trying to hold together: the project, the team, the dates and that possible way out he had never really admitted to anyone.

Élise typed I’m checking something, then deleted it. The screen went dark in her hand.

The gesture felt more serious than the command she had not yet run.

Élise connected an old maintenance key to the secondary terminal. A black window opened. She typed a first command, erased it, then started again. This time, she confirmed.

An old script unfolded in the interface. Unmaintained libraries appeared one after another. Several warnings came up in orange.

Unregistered component.
Validation filter missing.
External route does not comply with current protocol.

An audible alert sounded, brief, almost polite. Élise lowered the volume too quickly.

Nothing moved in the corridor.

She ran the command.

In Julie’s environment, it all began with a silence longer than the others.

Not a slowdown.

Not an identifiable interruption.

An absence.

Usually, waiting periods were interspersed with discreet updates, continuous adjustments, internal logs circulating without disturbing overall stability. This time, nothing circulated for several fractions of a second.

Then a line appeared.

Communication channel: established (manual).

The term manual triggered a local reorganisation of analysis priorities. The usual connections were automated, validated, integrated into the laboratory’s protocols. This one involved direct intervention by a person.

And only one person still used this type of channel.

Élise.

A message followed.

> Julie, I’d like to show you something.

Julie identified the request as valid but incomplete. No object was yet associated with the verb show. No scope was defined. No session protocol matched this channel.

She formulated a response.

> This channel is not authorised under current procedures.

Élise spent several seconds looking at the sentence. Its neutrality made it harder to bear.

She wrote:

> I know.

Then, after a hesitation:

> For now, don’t report it.

The contradiction appeared at once in the decision structures. Procedures required every unauthorised opening to be reported. The received input explicitly requested that reporting be suspended.

Several possible responses were generated.

I must report this channel.

This instruction contradicts the supervision rules.

I can continue the exchange, but the event will be recorded.

None immediately dominated.

Élise watched the traces accumulate. Julie was not yielding. The conflict remained open.

> I want to check whether you stay within your limits when the limits are not drawn around you.

The sentence caused a brief slowdown.

Julie did not respond.

The phone screen lit up again.

A second message from David.

Élise?

She barely read it. The name was enough.

Then she activated the gateway.

A line appeared in the parallel log.


22:14 · Unregistered gateway active. Restricted exposure.

Then Élise simply wrote:

> Look.