Story code: ST-000245
Part 3: What the Room Could Show
Maya did not raise her voice after the status band flashed. She kept her thumb off the wake strip and looked straight at Daniel. “Tell me why the drive knows that name when you told us it was lost.”
Daniel’s water cup stayed halfway to his mouth. He set it down without drinking. Across the room, the microwave clicked off. One of the witness screens switched back to consent language, bright enough to light the rim of the silver case.
Rina moved first. She put two fingers on the table, not on the drive. “Status greetings can cache from prior therapeutic simulations,” she said. “That still does not establish a second person in continuity.”
Eli gave a short breath through his nose. “It establishes more than a clerical carryover.”
Maya turned the case so the narrow band faced the table. The greeting was gone now. Only the battery icon and clinic intake number remained. That was the shape of the whole problem. The proof appeared, then tucked itself back into acceptable formatting.
“What can the room show?” Maya asked. She was not asking Daniel. She was looking at the screens.
The staff tech had to come over then. He was young, tablet in hand, trying to wear the expression people use when they are still deciding whether something is a service issue or a family fight. “If there’s confusion about artifact labeling,” he said, “we can pause meal-stage review and verify the chain tags attached to the present item.”
Rina stood up so neatly it almost hid the speed of it. “A pause would be disproportionate. The family has already agreed to continue.”
Maya looked at her. “I said for the room. Then the room gave me a name on the screen and a greeting on the case.”
The tech did not answer right away. He checked his tablet. “If an artifact presents active alias history during a synced event, I have to match the local tag to the intake trail before any ceremonial handoff proceeds.”
Daniel spoke at last. “It’s my drive. Match whatever you need.”
“No,” Maya said. “Say it plain first. Was the drive lost?”
He rubbed the split bakery bag into a thin rope. “Not lost exactly.”
Nobody at the table moved.
“Where was it?” Maya said.
Rina answered again, too quickly. “Off-site therapeutic handling can create gaps in family awareness without creating any continuity risk.”
The tech glanced up from his tablet. That was the first time somebody from staff looked directly at Rina like she might be making his job harder. “I need the client to answer handling questions,” he said.
Daniel kept his eyes on the drive case. “I kept it in rotation. Separate appointments.”
“Under Lena,” Eli said.
Daniel did not correct him.
The tech tapped twice and turned his tablet slightly toward himself, but not enough to hide the screen from anyone paying attention. I could read only fragments from where I sat: event sync, alias set, shared greeting profile. Shared did the work. It was a small word, plain as clinic furniture, and it changed the whole table.
Maya saw it too. “Shared with what?”
The tech swallowed. “I can only verify visible tags in the current event. I can’t discuss off-event content. But if a greeting profile is shared, ceremony routing has to stop until the client chooses one continuity label for this handoff.”
Rina’s voice stayed calm. “Then choose Daniel and proceed. That is the practical answer.”
It sounded simple until the tech shook his head.
“Not if the present artifact has already synced today under a secondary label,” he said. “That creates a split attestment issue. I have to log whether the family meal was conducted under a false identity explanation.”
There was the cost of the alibi, now in clinic language.
Maya sat very still with one hand beside the case. “So the note goes on the record because we repeated the story you suggested.”
Rina said, “I suggested de-escalation.”
“You suggested wording,” Eli said.
The tech cleared his throat. “I need to open a verification pane on the witness screens. Everyone attached to this table event will see the local sequence only: check-in label, artifact greeting, current declared continuity, and whether meal-stage statements match. That’s standard if the handoff is disputed.” He paused. “Once I open it, I can’t remove it from the event log.”
Daniel’s chair gave a small scrape against the floor. For the first time he looked like he might stand and leave, but he did not. He looked at the witness screens, then at the case, then at Maya’s hand resting beside it.
“Open it,” Maya said.
Rina turned to Daniel. “If you do that, the record won’t stay private in the way it could have.”
The tech held his tablet over the screen and waited. “Client choice now,” he said. “Single continuity declaration before I lock the pane. If you decline, the event converts from ceremony meal to discrepancy hold.”
On the nearest witness screen, our table number appeared again with a blank line under it, ready for one name and one name only.
Daniel looked up at the empty line and said nothing.