Story code: ST-000764
Part 2: What He Could Name, He Could Not Run
The room did not move away from the contradiction. It moved closer. Cal Bennett stepped out from behind the status panel and held his phone up beside the wall feed, showing the access timeline in the memorial platform while the stream kept running over the family table. The log was plain enough for everyone in the room to read: Evan’s remote credentials had been granted to view the memorial, to add a tribute note, and to manage a few guest settings, but the actual repair actions had come from Maya’s backup account, the one tied to the VR memorial link and the only one that could restart the archive without dropping the room.
Evan tried to step around that by talking faster. He told the room he had coordinated the whole thing from out of state, that he had handled the archive layout, that he had made sure the memorial stayed accessible for relatives who were not coming in person. The problem was that each claim had a visible test attached to it, and every test landed on Maya’s side of the table. When the stream drifted again, he reached for the shared settings and the memorial banner froze. Maya reached over, used the admin path he did not know, and the banner cleared. When the tribute queue skipped a photo, he said the family link must be glitching. Maya pulled up the folder map, moved the file into the right line, and the next photo loaded clean.
Denise watched the two of them and said, “You keep talking like you built the room, but you’re not fixing anything in it.”
That line changed the way the relatives on the remote feed leaned in. Not because it was dramatic. Because it matched what they could see. The memorial platform kept exposing a gap between the person speaking for the work and the person actually doing it. Evan had the story. Maya had the steps. Cal had the log. The tribute archive, which he had claimed to organize, still used Maya’s recovery structure, the same one she had set up months earlier so the family could reconnect if anyone got locked out during the service.
Then the next failure hit in full view. Evan tried to demonstrate that he knew the system by opening the condolence wall from his end. The wrong folder loaded. The memorial feed flashed a missing permissions panel. The live tribute froze on a gray screen with the family name half-cut off. A couple of relatives gasped. One of the remote squares went dark. Cal looked at the panel, then at Maya, because she was already reaching for the backup path that only she could use.
She did not say anything about credit. She just typed, waited for the response timer, and repaired the session again.
Evan’s face stayed set, but his next move gave him away more than his speech did. He asked Maya, in front of everybody, to “just put the admin code in so we can keep going.” That was the first time his need showed up in the open. He could repeat the memorial’s story. He could not continue without the knowledge embedded in Maya’s process.
Maya looked at him across the family table and kept her voice low. “You told them you handled the link. Why are you asking me for the code?”
No one answered for him. The room stayed on the same quiet beat, with the tribute archive waiting and the stream still live, and Cal’s screen showing that the only repair route left belonged to Maya alone. The question now was simple enough for everyone to hear and sharp enough to change the room: if Evan needed Maya’s missing skill just to keep the memorial alive, what else had he been claiming that he could not actually do?