Chapter 9
Chapter Nine
The access denial came without warning.
Angus had logged into the interstate case reference system—the same database he’d used for a decade to cross-check records between jurisdictions. Routine. Automatic. The kind of action that required no thought because he had been performing it hundreds of times before.
He entered his credentials. The system accepted them. The loading screen appeared, then:
Authorization Unavailable
Access scope cannot be verified. Please contact your administrator.
No red text. No warning sound. Just a gray dialog box with neutral language and a button labeled “OK.”
Angus clicked it. The system returned to the login screen.
He tried again, entering his credentials more carefully this time, making sure every character was correct. Same result. The system accepted his login but denied access to the database itself.
Scout lifted his head from where he had been sleeping near the table, sensing something wrong in the quality of Angus’s stillness.
Angus opened a different system—the national missing persons database. Same credentials, same login process he’d used for years. This time the loading screen appeared and held for longer than usual, as if the system were checking something beyond routine authentication.
Then:
Access Currently Restricted
For assistance, please contact your department administrator.
Angus closed his laptop and sat in the quiet of his kitchen. Morning light filtered through the windows. Coffee cooled in his mug. Outside, Weyport continued its ordinary rhythm—garbage trucks making rounds, neighbors leaving for work, the town operating according to schedule and routine.
Inside, Sheriff Angus Reid had just been locked out of databases he’d accessed daily for a decade.
He pulled out his phone and opened the same systems through his mobile browser.
The missing persons database loaded partially—public-facing information appeared, but the detailed case files he’d always been able to view were grayed out, inaccessible.
The interstate reference system wouldn’t load at all beyond the login screen.
Then he tried his personal laptop—the one not issued by the department. The one connected through his home internet, paid for with his own money, carrying no official credentials.
Public databases loaded normally. Vital records searches worked. General information appeared without issue. Everything a civilian could access remained accessible.
Everything that required law enforcement credentials was closed.
Angus had been locked out. Not everywhere. Not completely. Just from the systems that marked him as someone with authority, with clearance, with the right to access details civilians couldn’t.
Someone had restricted his access without suspending it. They had created a barrier disguised as a technical issue, quietly restricting what he could see while preserving just enough access to avoid drawing attention.
Scout stood and nudged his elbow, the collie’s way of checking in. Unbothered by gray dialog boxes and bureaucratic language.
Angus pulled up his department email on the personal laptop. Civilian access only, but email should still work. His inbox loaded normally—routine messages, department updates, notifications that had accumulated during his leave. Nothing unusual.
Except that, filed automatically in his administrative folder, was a notice he hadn’t received but that had apparently been issued:
SUBJECT: Administrative Access Alignment
The email had no sender—just “System Administrator” in the From field. No timestamp beyond the date it was filed. No signature. Just text:
Your network access profile is currently undergoing routine administrative alignment to ensure proper authorization scope during your approved leave period.
This process is automated and requires no action on your part.
Access levels will be restored in accordance with standard protocols upon your return to active duty.
For questions regarding this adjustment, please contact your department’s IT coordinator
.
Angus read it twice. Then a third time.
At the bottom of the notice, beneath the standard footer language, was a reference code Angus didn’t recognize.
It wasn’t an error code. It looked like an internal classification tag.
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.
The system was responding to his searches. To patterns in his database access. To queries that suggested he was following trails someone didn’t want followed.
And the system had responded by closing doors. Quietly. Efficiently. Through administrative processes that involved no human decision, no oversight review, and no real opportunity to appeal without triggering questions about why routine alignment required explanation.
Angus closed the laptop and sat in his kitchen with Scout’s steady breathing the only sound.
Ordinary morning. Ordinary town. Ordinary life continuing while Sheriff Angus Reid sat at his kitchen table and understood that he was not ordinary. He’d been classified.
Not as grieving. Not as curious. Not as a brother searching for truth about his missing sibling.
As a risk.
Someone had made that classification. Had implemented it through systems that generated no alerts, raised no red flags, offered no obvious sign that anything had changed. Just quiet restrictions designed to stop his investigation without explanation.
Except they wouldn’t stop him. They would slow him. Would force him to work differently, more carefully, without the tools he’d relied on for two decades. But the truth didn’t change simply because access to official databases was restricted.
Logan’s death certificate was still fabricated. J. Brennan still didn’t exist. Sandra Hammond had still confirmed the pattern before retracting it. The evidence remained, locked in Angus’s files, documented in his notes, real regardless of whether official systems permitted further searches.
Angus added one final line to his journal entry:
They’re not warning me. They’re containing me.
The distinction mattered. Warnings suggested he could still choose differently, still step back, still accept what he had been told and move on.
Containment suggested that choice was no longer available.
That he’d crossed into territory where the system needed to manage his access, limit his reach, and ensure he couldn’t continue gathering evidence through official channels.
Which meant he’d found something worth containing. Something dangerous enough that quiet restrictions were necessary. Something that required institutional response beyond simple warnings and administrative courtesy.
They don’t contain people who are wrong.
They contain people who are close.
Scout stood and stretched, ready for his morning walk, completely unbothered by restricted databases or administrative notices. His routine remained unchanged—breakfast, walk, the simple rhythms of canine life that required no access credentials, authorizations.
Angus looked at his closed laptop.
He wouldn’t call IT. Wouldn’t ask about alignment, protocols, or when his access might be restored. Wouldn’t start a conversation that forced him to explain why routine administrative processes concerned him.
He would work differently now. With what he already had. With resources that required no credentials. With evidence hidden in locked files, coded notes, and the places where truth existed independent of any system.
The investigation hadn’t stopped. It had just moved further underground.
Where the only restriction was Angus’s willingness to continue despite everything the system was doing to make him stop.
And he would continue. Carefully. Quietly. Alone.
Because they’d classified him as a risk.
Which meant he was finally asking the right questions.