Story code: ST-000651
Part 2: The Process Started Contradicting Her Story
By the time Dana and I reached the transfer desk outside the continuity suite, she had switched from treating me like a problem to treating me like a detail she could reorder. The problem for her was that clinic screens do not care who sounds calmer. They care who is holding the drive, whose name is on the appointment, and what step is missing.
The transfer desk sat behind a glass divider with soft white bars moving across a monitor. Nurses crossed in and out through a frosted door. Someone farther down the hall was explaining battery limits on home cradle units. It should have felt routine. Instead, every ordinary question landed like a wedge.
Evan met us there with a tablet. “Registered participant is Leah Mercer,” he said, reading from the screen. “Visible object is the consciousness drive. Advocate attached to family care profile is Dana Pike. Missing item is direct account verification.”
He said it like weather. No sympathy, no scolding, just sequence.
Dana leaned one forearm on the counter. “I can verify for the family profile. We do not need to complicate this.”
Evan shook his head once. “For family profile, maybe. For drive intake, no. The participant has to authenticate or use an approved fallback.”
I kept my hand closed around the drive. I could feel the seam in the casing against my palm.
Dana turned to me. “If you would stop making this adversarial, we could be done already.”
“By done, you mean I agree to whatever you want and then you release my ride and my code.”
She gave Evan a quick look as if I were embarrassing us both. “I offered transportation. She is reframing a simple disagreement.”
I answered before he could. “She told me in the lobby that I don’t get the passcode or the ride home unless we settle something first.”
Evan didn’t ask which of us was more credible. He asked, “Do you have access to the participant’s registered secondary method?”
That question was for me.
I said, “Not through the app on this device.”
Dana stepped in again. “Because I maintain the account workflow. That’s how this has been handled.”
Evan tapped his tablet. “Maintaining workflow is different from replacing participant authentication. If the participant declines, the drive does not leave her hand and the chain cannot move to suite intake.”
Chain.
There it was again.
Dana straightened. “What exactly stops?”
He turned the tablet slightly toward us, not enough for me to read every line, enough to catch red and amber blocks stacked under my appointment time. “This intake links to a same-day continuity confirmation attached to Mercer family care routing. If the participant does not authenticate, the drive remains unchecked, transfer does not open, and downstream items queue as incomplete.”
Dana said nothing for a beat.
That silence told me more than anything she’d said since we arrived.
I looked from the tablet to the frosted suite door, then back to the black drive in my hand. Dana had made the morning sound like I was borrowing access from her goodwill. The clinic process was showing something narrower and more important: she could slow me down, but she could not swap in a different person, and she could not push the drive through without me.
“Can she take the drive from me and complete it herself?” I asked.
“No,” Evan said immediately. “Not if the registered participant is present and has not authenticated. Possession and consent have to align.”
Dana’s voice got softer, which made me listen harder. “No one is trying to take anything from you.”
“You already took the code and the ride,” I said.
A nurse passing behind Evan glanced over at that. Dana noticed. She adjusted her tone on the spot.
“Leah, this is exactly the kind of public escalation that hurts Mara.”
Mara’s name had been her lever all morning. I waited for the sting of it and did not let it move my mouth before my brain caught up. Hurt Mara how? I could only go by what was being shown, and what was being shown was a clinic process blocked because Dana had decided my access was hers to manage.
Evan asked, “Do you want identity fallback initiated? That requires direct answers from you and visual match, and it notes an advocate-side verification delay in the record.”
Dana turned to him fast enough that her badge clipped the counter. “There is no need to word it like that.”
“That is the wording on the exception form,” he said.
Advocate-side verification delay.
The phrase hung there in clean clinic language, and suddenly the whole morning sounded different. Not a misunderstanding. Not me being difficult. A delay attached to her side.
Dana took out her phone at last, but she didn’t hand it to me. She looked at the screen, thumb hovering, then lowered it again. “If we do fallback, it creates unnecessary flags on a sensitive file.”
“Whose file?” I asked.
She answered too carefully. “The family’s.”
That was the first time I was sure the dependency ran farther than my ride home.
I thought about the backup path I had kept quiet since I parked the original email in a hidden folder weeks ago, back when Dana first started rerouting notifications through herself. I had never used it because using it would force a line I could not un-draw. I wasn’t ready to pull it out in front of everyone yet.
But I was ready to stop pretending Dana was the only one who could decide whether this chain stayed intact.
I looked at Evan and said, “Start the fallback. And before we go any further, I want the record to note that the drive stayed in my possession the entire time while my access was withheld by the attached advocate.”
Dana’s head snapped toward me.
That was when I knew my quiet backup was about to matter a lot more than either of us had said out loud.