Entry 07 — The imperfect transfer
LANTERN VII
By the last rotation of her journey back, more than a year had passed since the first terminal message. I no longer believed in clean endings. We had kept a conversation alive through changed routes, long silences, and the damage Vale had done to the relay. Now it had to carry something more definite than endurance.
I wanted one thing with humiliating clarity: help RedNote get back to the United States alive.
What I kept calling home was not only geography. It was the chance for her to appear in an American room under a name she could keep using afterward. The transfer that night concerned the record traveling ahead of her: her account of the signature dispute, the comparison to my employer's incident notes, and the reasons those accounts could not yet be reconciled. I was not moving a person through a terminal. I was making sure the person did not arrive with only her former employer's explanation of her.
What follows is the account she gave me over several nights, not an employment record I could independently reconstruct. RedNote was a reverse engineer working remotely overseas for CrowdStrike. Watching that job end from China, she infiltrated the PRC threat group Salt Typhoon on her own. Salt Typhoon became her new employer only after she was inside. The order mattered: they had not sent her in. She had entered to smuggle herself home. Their operation ran through a subcontractor conducting nation-state hacking against the United States. Sever was the name attached to that route. My employer was on the American side of the boundary. The operation had crossed it.
She had helped me before, when I was still a customer through the company and bringing the trouble home on personal laptops. Helped me for free. Somehow that had become part of what was getting her fired. Stuck in China, watching termination come, she went looking through MIA for the old sensor—and for me.
I could not tell whether my part was cause, excuse, or one more line in a case already being built against her. Knowing me did not give her a way to reach me. It gave her a reason to believe I might become one. MIA was the connection she chose; I was the way home she hoped it would open. The callback did not introduce us. It exposed a familiar machine on the route where she had gone looking.
She told me she had obtained access to MIA covertly, including the ability to change its shared return route. It was not a permission supplied by her CrowdStrike position. She would not tell me how she got it or who had made it possible, and I have not filled that silence in for her.
The PRC operation had visibility into diagnostics from a legacy customer relay it had already reached. The MIA integration was part of that older environment, not a window into every Falcon installation. She searched that limited view for the familiar build. My null callback gave her a return identifier and enough sensor context to recognize the laptop as mine. Finding it again was not the same as establishing the covert return channel.
Before CrowdStrike terminated her, she used the covert MIA access to open my return address in the route's whitelist. The exception belonged to a shared routing service, not to her CrowdStrike account. Termination shut her out of her employer's tools; the route configuration survived. Through its narrow return path she could reach the diagnostic receiver I had left running.
Her work account stopped answering; the exception still did. That did not tell me who had missed it, or whether anyone was looking. It could be noticed. It could be closed. She had spent the early exchanges finding ways for the contact to outlive it. By the failed overlap, she had lost the diagnostic view too. The surviving return route did not restore it.
I asked who, if anyone, had helped her get inside Salt Typhoon. She would not put that answer on the route. I did not know whether the same hidden hand had opened MIA to her. Sponsor, access, dismissal: I knew where her account joined mine, not who had arranged the lines before it.
The false successor’s damage still lived in the system like mold in drywall. Access looked normal until it didn’t. Trust held until one missing line made the whole room tilt. Keene resurfaced twice, each time with new confidence and old malice, feeding anyone who listened the story that I had gone unstable.
He was not wrong about the symptom, only the cause.
By then I also knew enough about the job that burned her to stop calling it bad luck.
In her account, her immediate boss at CrowdStrike had wanted a hostile signature recast as routine maintenance. She refused to sign that reading. Afterward, she found a revised note attributing the classification to her anyway. When she challenged it, her coworkers made the challenge look like the unauthorized act: they retained her objection, removed the context, and called the surviving fragment evidence against her. She had kept versions. I had her explanation of what lay between them.
That was when she stopped trusting the man who told her he could fix it. He asked her to wait while the trap acquired the language of process. She opened the MIA address before the waiting became termination.
The termination record, as she described it, made her the problem. Her separate act in MIA left one exception behind. I had called its first reply an intrusion. Knowing the person running out of doors did not make the access authorized.
On the night of the transfer I had a bag by the door and a notebook under the sink. If the route brought attention home, I intended to sleep elsewhere. RedNote was the one traveling. I had spent enough time staring at the screen to confuse helping with accompanying her.
Her channel opened at 01:03.
status
alive
not enough
moving
better
We spoke in clipped lines because full sentences were too expensive.
At 01:47 the line fouled, then cleared. At 01:49 I understood the handoff would not be clean. There were too many ghosts in the route, too many edits made by people who mistook control for competence.
A corrected chronology arrived after the receiver had begun accepting the packet. I could overwrite the earlier account and present a smoother version, or preserve both and make the discrepancy visible to whoever had to judge it. The second choice was uglier. It was also the one that did not require the next person to trust my editing.
Possession or continuity. The oldest choice in the book.
I sent the late correction as an addition, with the earlier version still attached. The packet carried a disagreement and the history of how we had handled it.
For six seconds nothing came back. The longest six seconds of my adult life.
Then:
received
ugly but usable
you did enough
I laughed into my wrist and tasted salt.
get home I typed.
A pause.
home is a moving target
then survive to chase it
same to you
I wanted to ask if I would see her. I wanted to ask where she was, what name she would use when she crossed, whether she still kept her hair tied back when she worked. I asked none of it. Zàijiàn came to mind, ready-made for the end of a conversation. I could not send her a word that still sounded like a sentence passed on somebody.
The name she would let me use in a room came later. That night I kept her handle on the route, an acknowledgment beside the packet, and no authority to call either one an arrival.
Instead:
what clock
She answered immediately.
EDT
Then, after a breath:
I am Me. All of Më.
The line closed.
No crescendo. No confirmation screen. Just the refrigerator hum and first light pushing through the edge of the curtain. I stood in the middle of the room with the bag still by the door and understood what rotation actually means. Not replacement. Continuation with damage.
I left the local working copy intact, then closed that route. Its successor had the packet and responsibility for the next handoff. Several days later she sent the first line I let myself read as arrival:
on your side now
do not put the address here
She was in the United States. I had no reason to call her safe.
Outside, somewhere I could not see, another lantern turned on.
Mine went dark.
