Skip to the story

A Sovereign Mercy reader extra

Mind the Gap

By Robert Wescott · October 2026 · Public · Non-canon · Revised October 15, 2026

An empty hospital visitor chair with a phone displaying linked boxes; a red line leads toward an office. Mind the Gap.
AI-generated illustration of an imagined setting.

The first time BRIDGE gave Helen back an hour, she spent it eating lunch outside. There was a bench behind the office where the smokers used to sit, before the company discovered that removing the bench was cheaper than helping them quit. Someone had brought it back. She ate a sandwich with both hands and watched a bird dismantle a cigarette filter. Her phone stayed in her bag.

During the daytime training weeks, before she returned to the night shift, a supplier had submitted a proposal for replacing the warehouse cooling system. Helen would normally have read the report, checked the attachments, and attended a meeting in which three people repeated the report while a fourth advanced the slides. BRIDGE showed her the proposal as a small arrangement of linked statements. The promised saving depended on lower electricity use; the lower electricity use depended on a temperature setting; the temperature setting exceeded the limit for two products they stored. She followed that branch to the original specification, checked the numbers, and rejected the proposal before anyone had booked a room.

She liked the language immediately. It took a little learning, mostly the discipline of keeping a claim separate from its evidence. Estimates carried their uncertainty with them. A familiar term could open into its definition. You could see two consequences beside each other instead of holding the first in your head while somebody explained the second. When she needed a sentence, she asked for one. The system did not complain that the answer was already in the document.

At home, she used it to compare electricity plans and discovered that the cheapest one was cheapest during the hours she was at work. Her mother used it to untangle a pension letter. They sat at the kitchen table following the branches until her mother found the date that determined her payment, then opened the source to make sure. She had worked in payroll for thirty years and approached any claim about simplified administration as though it were an envelope containing a dead mouse.

“This is actually useful,” she said, sounding almost offended.

For two weeks, Helen left work on time. She began cooking things that required chopping. On Thursday she phoned her mother without simultaneously sorting laundry. The company circulated a message thanking the pilot group for demonstrating the possibilities of human and machine collaboration. Helen selected AGREE. She had no reason not to.

The new workload arrived on Monday.

Her manager's explanation was unusually clear. BRIDGE had reduced the average time required to review a supplier proposal, so each reviewer could now handle more proposals. The calculation included the training period and the occasions when a person needed the full explanation. It was a careful calculation. Helen checked it twice, hoping to find the kind of concealed assumption that had saved her from the cooling system. There wasn't one. The company had measured the hour she recovered and assigned it to somebody else's purchase order.

By Friday, her queue was longer than it had been before the pilot. She understood each proposal faster, which allowed her to understand more of them before becoming tired. There was no field for the accumulating weight of deciding. The work portal counted completed reviews and elapsed time; when she opened a supporting document, a small clock appeared in the corner. Her manager told her it was informational. He had one too. His was attached to how quickly he resolved her delays.

Meetings became eight minutes long. The agenda arrived in advance as a map everyone was expected to have understood. During the third meeting, Helen asked what would happen to the night staff if the warehouse changed its delivery schedule. Her manager expanded the relevant branch and showed her that the staffing problem had already been identified. He looked relieved. They could move on.

“I know it's identified,” she said. “What are we going to do about it?”

He glanced at the timer. A second meeting had been arranged immediately after theirs, using the minutes the first meeting no longer required. He sent the question to a review queue and thanked her for raising it. BRIDGE preserved the exchange accurately. Helen could return to it whenever she wanted to see exactly how little had happened.

When her mother fell, the hospital's version was already installed. The admission instructions reached Helen in the parking garage: location, condition, immediate plan, uncertainty. She could see which questions had answers and which were still waiting for tests. She reached the ward frightened but informed, and for that she was grateful. Gratitude became difficult to separate from anger later. She could remember what the system had done for her even while somebody was using it to get rid of her.

The discharge consultation lasted four minutes. A doctor showed them a recovery map and opened the branches they asked about. Her mother needed help standing, someone available overnight, and a follow-up appointment. Helen understood all three. She also understood that she worked nights and her mother lived alone. By the time she explained this, the doctor's device was announcing the next consultation. He added a note and told them the discharge team would arrange the details.

An hour later, her mother was sitting on the edge of the bed with one shoe on. The nurse held the other in a plastic bag. A tablet on the wall showed HOME, surrounded by a green circle. Helen opened it and found a transport booking, a list of precautions, and a record stating that the family had understood the plan. They had. The plan was exceptionally easy to understand.

“Where is the person who's staying with her?” Helen asked.

The nurse opened the same branch Helen had opened. Beneath OVERNIGHT SUPPORT was FAMILY, linked to Helen's name. The doctor's note about her night shift appeared further down, marked for follow-up. The nurse read it and pressed her lips together. A trolley in the corridor kept catching its wheel on something. Each attempt to move it produced the same small knock.

“I can call the discharge coordinator,” she said.

Helen selected WAIT beside the transport booking. The tablet offered the next available review slot, tomorrow afternoon. She expanded the delay warning. The first explanation was longer. The second said the hospital could not guarantee that the bed would remain available. Her mother reached for her coat, then stopped, keeping her hand on the blanket as if she had forgotten what she intended to do with it.

BRIDGE had shown Helen the problem almost immediately. She was beginning to understand that this was the easy part.

She followed the overnight-support branch to its source. FAMILY had been imported from the emergency-contact field. Below it, a second link showed the required confirmation from the person providing care. That field was empty. Helen could see the entire chain: a name entered so the hospital could call her, reused as evidence that somebody would be home. She opened the empty confirmation and showed it to the nurse.

The nurse set the shoe bag down. “Leave that open.” She brought up a review form and attached the missing confirmation to it. Helen asked why her explanation hadn't been enough. The nurse kept typing. The ordinary review queue went to the discharge team, she said; a missing required field went to the ward supervisor, and the transport booking could be held while it was resolved. She turned the tablet so Helen could see the hold appear. Someone had given the nurse a way to stop the process, provided she could describe the problem in the form the process recognized.

The supervisor came twenty minutes later. Her mother stayed. By then Helen had missed the beginning of her shift, and the nurse had three unanswered calls on her device. None of them seemed to have acquired more time.

At eleven, Helen sat beside the bed while her mother slept. She used BRIDGE to explain her absence to her manager. He received the situation, its supporting record, and her requested adjustment within seconds. He approved it. Then he sent six reviews she could complete remotely. The message was considerate: no expectation of a full shift, only tasks suited to the available window. She could see why he had chosen them. That was another improvement. She no longer had to wonder how the work had found her.

She completed two. On the third, a supplier's estimate opened into a long explanation, and she caught herself resenting it. She wanted the answer to fit on the screen. Her mother moved in her sleep. Helen closed the proposal and watched her settle, ashamed of how quickly she had learned to hurry another person's uncertainty.

A feedback request arrived from the hospital. Had BRIDGE helped her understand the discharge plan? Yes. Had it helped identify a problem? Yes. Would she recommend it? She left that unanswered. The system thanked her for the completed responses and displayed a figure for the consultation time saved. She looked at the number, then at the chair she had occupied for most of the evening.

Her mother woke and asked whether she could stay a little longer. Helen put the phone away. There was nothing to expand in the question, no source to check. She took her mother's hand and said yes.

In her bag, the work portal marked her available window as underused.

The novel

Sovereign Mercy

Knowing what a decision means does not mean agreeing to it. Sovereign Mercy asks what protection is worth when someone else gets to choose.

Read a sample of Sovereign Mercy →

The sample is open to everyone. Full chapters are free after email verification and acceptance of the reader agreement. Newsletter signup is separate and optional.

Explore the idea

BRIDGE

The story imagines a notation that makes claims, evidence and permission easier to distinguish. These optional companions explain the proposal; neither is needed to read the story.

  • Language card — the essentials, one example and a printable reference.
  • Full companion — the grammar, boundaries and tests a real prototype would need.

Design proposal 0.3. No demonstrated speed or comprehension benefit.

Sources & Record

Source notes checked October 15, 2026. These references inform the design discussion; they do not validate BRIDGE or document the fictional events.

  1. Progressive disclosure

    Jakob Nielsen · Nielsen Norman Group · December 3, 2006

    Describes making secondary interface options available on request. This is a useful design precedent for expandable explanations, not evidence that a new notation increases human communication speed.

  2. Time to understand

    W3C · Understanding WCAG 2.2 · Timing Adjustable

    Explains the need to let users turn off, adjust, or extend many interface time limits, including accessibility considerations. BRIDGE’s proposed protection for reflection goes beyond this specific criterion.