Exhibit A

Julian

The door had a lock I had set myself, and I used it. I stood at the window for a moment, looking at the darkened garden below: the same controlled quiet, even at night. I had told myself I was going to sleep.

I lasted as far as the chair.

The evidence file was open on my screen at eight forty-three, and I worked through two more entities with the disciplined focus I could always locate when everything else was unreliable, the part of my brain that turned distress into productivity as a matter of functional survival.

Entity thirty-eight. Entity thirty-nine. Both clean, or clean enough: the skimming pattern didn't appear in either, which was its own data point; absence of the pattern was as informative as its presence.

I was opening entity forty when the workstation's secondary email client flagged a message.

I had set up secure internal email access as part of the compliance system integration, standard practice. I needed to be able to receive documentation from Serena, from the accounting systems, and from the entity administrators. The address was new. I had used it for less than twelve hours. It was registered under a pseudonym within the secure system, accessible only to people with deep internal access to the organisation's communication infrastructure.

I looked at the flag.

One new message.

The sender field was blank, not absent: blank, which was the technical difference between an address that doesn't exist and one that has been scrubbed. The subject line was empty.

I opened it.

The body of the email was four words.

I read them once.

I read them twice.

I sat very still for a long time, long enough that the screen's automatic dimming engaged and the room went fractionally darker, and I reached out and touched the trackpad to bring the brightness back.

The four words were still there.

Dig deeper. You die.

And below them, in a separate line that had not been there in my first reading. It had appeared in the ten seconds between opening the email and reading it: generated dynamically, which meant someone was watching the moment of access in real time.

A fifth word.

Leave.

I stared at the screen.

My hands were flat on the desk.

Not shaking. I noted this from a slight remove. Hands steady. That was something. That was still something.

I looked at the five words on the screen and thought about all the things they confirmed.

Someone with deep internal access to the organisation's communication infrastructure. Someone who knew I had set up the email account today. Someone who was monitoring the system in real time. Someone who knew I had been in the evidence file at five-seventeen and knew, therefore, what I had found.

I opened a new document.

I typed the five words into it, with the timestamp, with the dynamic delivery notation, with the technical specifications of a blank sender field. I flagged it correctly in the evidence system, attached it to the Meridian Gap file and labelled it:

Exhibit A: Direct Threat, Day Two.

Then I sat back.

I thought about four words that were meant to stop me, delivered by someone who had spent fourteen months building an architecture designed to survive examination, and who had just demonstrated, by sending this email at all, that they were afraid.

You only threatened the person who was close enough to find you.

Dig deeper, the email said.

You die.

I looked at the whiteboard. At the name in the top corner of the " Investigate Further " column. At the line connecting it to Marcus Hale. At the timeline running along the bottom.

My small, precise handwriting. The kind Marcus had said looked like someone afraid to take up space.

I picked up the marker.

I added a new entry to the timeline.

Day 2: Subject aware of investigation. Direct threat issued via secure internal channel. Indicates real-time surveillance access.

I drew a line from it to Dorian Kells's name.

I capped the marker.

Then I reached for my phone. Not to call Alastor: not yet, not until I had more. I opened the encrypted notes application and typed one line to myself:

They tried to scare me. They used a channel that required deep internal access to reach me. They gave me evidence of their access, trying to take mine away.

I looked at the note.

Added a second line.

I have been afraid my whole life. It has never once stopped me from doing the work.

The workspace was quiet. The residence was settling into its engineered nighttime stillness. Somewhere below me, Alastor Vane was in his study or at his desk or standing at a window the way he stood at windows, with the quality of a man for whom thinking required space and silence.

I closed the email.

I opened entity forty.

I kept working.

And in the corner of the screen, the evidence file sat with its new exhibit: four words and a fifth that had arrived while someone watched. The timestamp marked the exact moment that whoever had built fourteen months of careful, patient, sophisticated deception had made their first mistake.

They had told me I was close.