Page 27 of Logan’s Way

Routine administrative alignment.

Authorization scope adjustment.

Standard protocols.

Every word had been carefully chosen. Every phrase technically accurate. Nothing that could be called punitive or disciplinary. Nothing that suggested wrongdoing or investigation or concern.

Just a neutral explanation for the restriction of his access, filed in his administrative folder where it would wait—patient, official—ready to justify the limitations he’d discovered.

Except Angus had never received alignment notices before. He’d never had his authorization scope adjusted, nor encountered standard protocols that locked him out of systems he used daily.

This wasn’t routine. It wasn’t automated. And it wasn’t administrative housekeeping during an employee’s absence.

This was response. Targeted. Specific. Implemented by someone with enough authority to modify access profiles and generate official-sounding notices that would satisfy casual inquiry without revealing actual intent.

Someone had noticed the databases Angus was accessing, had tracked the records he viewed, the queries he ran, the files he cross-referenced. And someone had decided those patterns warranted restriction.

Not suspension. Not an investigation. Just quiet containment—limiting what he could see while maintaining the appearance of normal administrative procedure.

Scout settled onto his bed with a quiet huff, content now that Angus’s attention had returned to what he could understand—presence, steadiness, the patient rhythm of sitting together in familiar space.

Angus looked at the email again. At the language that said everything without saying anything. At the notice that had been filed without being sent, explaining restrictions that hadn’t been announced.

This was how the system protected itself—not through confrontation or accusation, but through procedure. Through administrative language that couldn’t be challenged without escalating to questions like, “Why are you concerned about routine alignment?” and “What makes you think this is anything other than standard protocol?”

The State Oversight call had been a warning—a suggestion to stop before things became complicated. That had been personal—a human voice making a human suggestion that Angus could acknowledge and theoretically heed.

This was different. This was the system itself responding. No human voice. No opportunity for conversation. Just automated restriction, implemented through channels that looked procedural but accomplished something specific: limiting Angus’s ability to continue investigating through official databases.

He closed the email and stared at the screen. The notice would remain in his administrative folder, waiting to explain the access restrictions if anyone asked. Creating a paper trail that suggested nothing unusual, nothing targeted, just routine adjustments during an employee’s leave period.

Except Angus had been on leave for two weeks before the restrictions appeared. Two weeks of normal access, routine database use, standard logins that worked exactly as they always had.

The restrictions hadn’t begun when his leave started. They came after specific inquiries. After accessing specific records. After someone noticed what he was looking at and decided he shouldn’t be allowed to look anymore.

They don’t restrict people poking around in the wrong places.

They restrict people getting close to what they’re not supposed to find.

He thought about the Hammond retraction. About the phone call that had come within an hour of her confirming what he’d suspected. About the precise timing that suggested active monitoring, not periodic review.

And now this: access restrictions dressed up as administrative alignment. Limitations implemented through automated systems that left no fingerprints, no responsible parties, no one to question or confront.

Just bureaucratic language and closed doors and the quiet, efficient machinery of institutional suppression.

Angus pulled out the notebook where he documented everything in coded shorthand, shorthand that resembled personal reflection more than investigative notes. He wrote:

Database access restricted. Administrative notice filed. Language suggests routine—timing suggests response.

Then, after a pause:

Not accused. Not suspended. Contained.

He underlined that last word twice.

Contained. That was the right term. Not stopped. Not prevented. Just limited in scope, restricted in reach, quietly classified as someone who needed boundaries without being told why.

The system wasn’t asking questions or investigating whether Angus had done something wrong. It wasn’t concerned with procedure or protocol or whether his actions violated policy.