The Recall monitoring interface shows green across all channels when Marcus sits down for Session 7.
Green means the session is clean. Green means his neural oscillation patterns have stabilized into something the system can archive and verify. Green means behavioral compliance has been met and the court-mandated course can proceed toward its scheduled close date. I know what green means. I've been reading these monitors for three years, ever since I took the extraction technician job because I could recognize the labile window better than anyone who hadn't been through one.
I've also stopped believing green means what it says it means.
"What does the third attempt feel like now," I ask, "a week later?"
Marcus is quiet for longer than usual. The interface registers a theta-gamma dip — the pattern I've learned to associate with a person trying to find honest language for something the system doesn't have a category for. Not a gap. Not a deficit. Just a thing that doesn't map cleanly.
"Smaller," he says.
I write the word in my paper notebook. Not the session notes — those I type into the intake system, which syncs to the Recall compliance database, which is technically accessible to the supervising court officer if they file a review request. The notebook is paper because paper doesn't sync anywhere.
"Smaller how?" I ask.
He takes a moment. "Like it happened to a version of me that was further away from me than I thought it was."
The interface stays green. It has no indicator for this. There is no gamma-theta signature for the specific kind of grief that comes when you realize you are further from yourself than you expected. The system measures whether the memory is consolidated, not what consolidation cost.
I write: grief changed his geography.
After Session 7 I update his intake notes with a flag. Possible grief response conflated with performance evaluation. The flag exists in the system now, officially. I can be asked about it. I wrote it in the approved vocabulary — the language the compliance reviewers understand, the language that fits inside the boxes the Recall network built when it moved from clinical to infrastructure.
The margin note in my paper notebook says something different: grief changed his geography. That formulation belongs to a different order of observation than what I'm allowed to submit. It is soft. It is not operationalizable. It would not survive a training archive review.
I don't need it to survive a training archive review. I need it to survive until next week.
Seven active clients in Recall-mandated behavioral compliance sessions. I don't usually think about them as a group — case confidentiality makes that hard, legally — but after Session 7 I find myself doing the math anyway.
I know what each of them is working on in the language the intake system uses. And I know, separately, the thing underneath that language. The thing I write in the margin, in paper, in words that don't sync.
Marcus: grief for who he was inside an architecture he no longer trusts.
The woman who's been in the program eighteen months: a decision from 2030 that keeps reconsolidating wrong, keeps failing the consistency check, not because she misremembers it but because she doesn't recognize the person who made it.
The new cohort member, Lena: two cities in her episodic memory, one she left and one she landed in, the grief moving between them on a timeline the system tracks as displacement instability.
The man who came through the Detroit-Akron network in February: a question he asked before his Recall and never got back, and now he's not sure if the not-having-it-back is the Recall or just the ordinary erosion of certainty over time.
Four of seven holding the same gap. Not a symptom the intake system has a field for. Not a gap that shows on the compliance monitoring interface, which is green, green, green, green, because they are meeting their behavioral thresholds, because the Recall worked, because the court-mandated course is proceeding as scheduled.
I don't know what I'm going to do with this observation. I can flag one case. I can't file a finding that spans four clients without invoking a case review that would compromise individual confidentiality in ways I'm not willing to explain to a compliance officer at 2 PM on a Thursday.
I write, in the margin: four of seven.
Then I go home and try to sleep.
2 AM. The apartment is quiet in the way it gets when the building's system has cycled down — no hum, no thermostat tick, just the street sounds that filter up from the Corridor: a reconsolidation clinic van making its overnight pickup run, someone's door at the end of the hall.
I have been Reyna Torres for nine years. I have also been, for nine years, someone with fragments of donor template 19 in my episodic architecture: a taste for black coffee, a fear of dogs, a recurring dream about a house in Michigan I have never visited and whose address I know with more certainty than I know my own grandmother's birthday. I moved to Detroit because the dream felt like home. The Recall system would flag that sentence as clinically anomalous. It is also true.
I lie still and think about the four cases. Not analytically. Just — hold them. The way you hold a problem that doesn't have a workable frame yet, that you're waiting on.
The Recall system measures whether clients are meeting their compliance indicators. It does not measure what compliance is covering over. For Marcus it is grief. For the others — different words for the same underlying structure. The structure is: something got reorganized by the Recall, and the person is working around the reorganization rather than through it, and the behavioral indicators look fine because they are working around it very skillfully.
I can see this because I worked around my own reorganization for two years before I learned to name the donor fragments for what they were. The black coffee and the fear of dogs didn't feel like intrusions. They felt like me. The system that treated my contamination was not designed to help me figure out which parts of me were me. It was designed to achieve clinical stability, which it achieved. I am clinically stable. I also know things about how a person navigates their own labile architecture that aren't in any training curriculum I've been given.
The clinic hired me because I understood the extraction monitor better than any tech without contamination history. They didn't know they were also hiring someone who could read what the monitor doesn't show.
4 AM. I get up. I make tea because the donor fragments left me with a preference for black coffee and I've been refusing it for six months on principle, which means I drink tea.
I open my laptop. I create a new document.
I don't know what to put in it yet. I know it isn't a session note and it isn't a margin entry and it isn't a formal finding. It's something else — a third space, a document that doesn't belong to the system and doesn't belong to the paper notebook and doesn't get reviewed by anyone.
I name it. I type: WHAT THE RECALL SYSTEM CANNOT MEASURE.
Then I sit with the cursor blinking.
The Recall system measures behavioral compliance. It measures the consolidation stability of targeted memory traces. It measures the gamma-theta coupling that indicates a memory has moved from labile to archived. It measures whether a person is meeting the terms of their court-mandated treatment program and can be cleared for re-entry into the social and employment systems that require Recall compliance documentation.
It does not measure what compliance is covering over.
I write that sentence down. It takes up one line.
I think about Marcus, who is grieving who he was inside an architecture he no longer trusts — and who is, by every metric the system can track, doing well. His sessions are productive. His engagement is high. His compliance documentation will support a positive close-date recommendation. He will be cleared.
The grief will still be there. The system has no mechanism for flagging grief that looks like successful treatment. The grief hiding in a place the system can't see.
I write: For Marcus it is grief.
Third line. I save the document. Three lines. It is 4:17 in the morning and I don't know what the document is for yet. But it exists now. Somewhere that is only mine.
I close the laptop and go back to bed.
Three days later I open the document. Three lines. I haven't added anything.
I sit with it — the cursor blinking at the end of the third line, the same place I left it.
I think: the document exists because I needed somewhere to put the thing that doesn't have a system field. Not for any purpose I can define. Not as a precursor to a finding or a formal report or anything the clinic could use. Just — a place that is mine, outside the intake system and outside the paper notebook and outside the language of compliance documentation.
That is a thing the Recall system cannot measure. Not the four-of-seven pattern, not the specific griefs, not Marcus's theta-gamma dip when he says smaller. Those are data points. What the system cannot measure is the fact that I am sitting here with a three-line document at 7 AM and the document's existence means something to me that I couldn't fully articulate before I wrote it.
I think about the house in Michigan. The dream that isn't mine. The way I moved toward it for nine years before I understood what I was moving toward. The way the donor fragments taught me something the contamination treatment never intended to teach me: that the archive of a person isn't the same as the person, and the gap between them is where most of the actual living happens.
The Recall system is very good at the archive. It is not built for the gap.
I close the document. I don't add a fourth line. Not yet.
I open the intake system. I have two sessions today. I open the first client's file and read the most recent compliance report.
Green across all channels.
I write the word smaller in my paper notebook, next to the date, before I begin.