The inventory clerk's note was three lines long and should have meant nothing: a routing sheet referenced in a 1991 access log was missing from its expected folder, flagged, filed, forgotten for thirteen years.
Inez found it on a Friday, the kind of detail that only surfaces when someone is willing to read an index instead of trusting that everything indexed still exists where it's supposed to.
"It's probably nothing," she said, in the tone people use right before something turns out to be everything. "Clerical drift happens. Things get misfiled, re-filed, lost in a move."
"Then let's confirm it's nothing."
We spent most of that day in the stored personnel packets, working through boxes that had not been opened since whatever reorganization had put them there. Annual reviews, supervisory notes, the dense paper sediment of a career conducted mostly before anyone thought to put it on a screen.
Inez found the carbon copy tucked inside Della's 1991 annual review, out of sequence, stapled behind a page where no one would think to look unless they were looking specifically for it.
It documented an access concern — someone, name redacted at an earlier stage and not yet restored to us, had flagged irregular retrieval patterns tied to Della's credentials that year. And it documented the concern's closure, stamped and coded, as a training matter rather than a security matter.
I recognized the code before Inez finished reading the stamp aloud.
"That's an exception classification," I said. "I helped write the criteria for that code. Years before this, for a different purpose entirely — minor discrepancies, retraining situations, cases where the fix is a conversation and a refresher course, not an investigation."
"So someone used your framework to close out a flagged access concern involving a woman who turns out, thirteen years later, to have been actively compromised the entire time."
I sat with that longer than I wanted to admit in front of her.
"The framework wasn't built for this," I said. "It was built for genuinely minor things. If someone applied it here, to something that looked serious enough to generate a routing sheet in the first place, that's a misuse of what I designed. Not what I designed failing on its own terms."
"Does the distinction matter to the people this review is for?"
It was a fair question, and an uncomfortable one, and I didn't have a clean answer. "It matters to whether we're correcting a tool or burying a person who misused it. I'd like to know which before we write either sentence into a final report."
The approval signature on the carbon was there but faint, smudged enough from age or handling that neither of us could read it with confidence in the room's poor light.
"We need a clearer copy," Inez said. "And whoever signed that needs to explain, on record, why a flagged access concern involving a trusted intelligence officer got closed with a code meant for a late report or a mishandled badge."
I agreed, and meant it, though some part of me — the part that had spent twenty years building that classification system and defending it in budget meetings as proof the agency could handle its own small failures without heavy machinery — hoped quietly, uselessly, that whoever had signed it had simply misapplied a tool I'd built in good faith, rather than having had any reason at all to want the concern to disappear.
I did not yet know whose signature it was. I only knew that the carbon in my hands connected my own earlier work, directly and undeniably, to a warning that had been raised and then allowed to vanish, and that the review I had promised Nolan I would conduct honestly was now, unavoidably, a review of something I had helped make possible.