Sena Mira has a voice for difficult conversations.
It is not a different voice from her regular voice. That is the thing people do not understand about it when they first encounter it, the expectation being that someone skilled at managing distress would have a specific register they deploy, a softer pitch or a slower cadence or the particular warmth of someone turning the professional dial toward compassionate. Sena's difficult conversation voice is the same as her ordinary voice. The same pace, the same clarity, the same quality of attention that makes the person on the other end of the call feel that they are the only thing she is currently thinking about, which when she is in a call is true, because Sena Mira does not divide her attention and she does not perform presence. She is either present or she is not and when she is on a call she is entirely there, which is both her greatest professional asset and the reason she has needed to be careful about how many hours of calls she schedules in a single day.
Today she has been careful. Today she has scheduled eleven.
The first call began at seven forty-five with a manufacturing client based in the New Singapore vertical whose automated quality control systems rely on visual differentiation between acceptable product and reject product, and the differentiation had been calibrated, historically, against a color range that included black as its lower bound. The null-percept was not black. The null-percept was not registering in the calibration system as black. The calibration system was consequently failing to reject product it should reject and passing product it should fail and the client's quality assurance manager, a precise woman named Hana Yun who communicated exclusively in short declarative sentences, wanted to know when this would be fixed and what liability Helix Collective was prepared to accept for the product that had already passed through the compromised system.
Sena listened to Hana Yun for four minutes without interrupting, which was the right thing to do not because Hana Yun needed to finish a thought but because Hana Yun needed to say the thing aloud to someone who was genuinely receiving it, and Sena was genuinely receiving it, and this was audible in the quality of her silence.
Then Sena said that she understood the situation completely and that she wanted to address both parts of Hana Yun's concern, the technical resolution and the liability question, and that she was going to be direct about both because directness was more useful than reassurance in a situation like this one.
She said that the technical resolution was in active development, that Helix's lead interface architect was working through the remediation queue systematically with a priority weighting toward systems with operational safety implications, and that the quality control system's calibration dependency placed it in that category. She said she would have a timeline from the technical team within twenty-four hours and that the timeline would be honest rather than optimistic.
She said that on the liability question, Helix Collective's position was that the Lost Black was an external event outside the reasonable scope of any interface design contract, that no interface specification written before Event Zero could have anticipated or accommodated a change to the fundamental perceptual conditions under which the interface operated, and that Helix was therefore not in a position to accept liability for outputs produced under those changed conditions. She said this clearly and without apology, because apologizing for a position you are prepared to defend wastes the other person's time.
Hana Yun said that was what she expected Helix to say.
Sena said she understood and that she would send the formal position in writing along with the technical timeline, and that if Hana Yun wanted to discuss the liability question further her recommendation would be to wait until the technical resolution was in place because a conversation about responsibility is more productive when the problem it is about has been solved.
There was a pause. Then Hana Yun said that was a reasonable approach. Then the call ended.
Sena made a note in her client file, opened the next brief, and moved on.
This is the texture of her days. This is, in the most functional sense, what she is for, the person who sits between the technical reality and the human experience of it and makes sure that the distance between those two things does not become a gap that something falls into. She has been doing this for nine years. She is very good at it. She does not always love it and she does not always hate it and she has never been able to decide whether the inability to feel strongly about the work itself is a professional virtue or a personal warning sign, and she has decided not to decide, because deciding would require caring about the question more than she currently does.
The second call was a research facility on the Lunar Administrative Zone. The third was the orbital freight platform, for which she was able to provide a technical update because Elian had sent her the saturation gradient specification overnight and she had read it at six in the morning with the coffee she makes before any call day, sitting at the narrow desk in her temporary accommodation at Site 7-North, working through the technical logic with the specific attention of someone who needs to understand a thing well enough to explain it to someone who needs to understand it well enough to decide whether to trust it.
She trusted it. She told the freight platform's operations director that she trusted it and why, in language that was technical enough to be credible and accessible enough to be useful, and the operations director said he would review the specification with his technical team and come back with questions. She said that was exactly the right approach.
The fourth call was the one she had been thinking about since yesterday evening when it appeared in her schedule.
The hospital administrator's name was Dr. Priya Okafor and she had the particular composure of someone who manages a large institution and has learned to present the institution's face to external parties regardless of what is happening behind it. The institution's face, in this call, was calm. What was happening behind it was audible in the specific way Dr. Okafor chose her words, the slight over-precision of someone selecting language carefully enough that the selection itself communicated something.
Dr. Okafor said that she wanted to discuss the current status of the surgical systems remediation, which Sena had indicated in yesterday's brief would have a technical update within two days. She said she was calling because the situation at the hospital had developed since the brief was sent. She said three had become five.
Sena said she understood. She asked Dr. Okafor to tell her about the two additional suspensions.
Dr. Okafor said the first was a spinal procedure that the lead surgeon had halted during the preparatory phase, before the incision, when she became uncertain about the depth-indicator readings in the augmented overlay. She said the second was a cardiac procedure that proceeded to the intervention phase before the surgical team flagged a discrepancy between the overlay depth readings and their physical assessment of the field, and that the procedure had been completed successfully using physical assessment alone with the overlay disabled, and that no patient harm had occurred.
Sena said she was glad no patient harm had occurred.
Dr. Okafor said that no patient harm had occurred yet and that she wanted to be clear that yet was the operative word in that sentence, and that she was not saying this to be adversarial but because she was responsible for a facility in which people's lives depended on the reliability of tools that were currently not reliable, and the clarity of that responsibility did not allow her to soften the language.
Sena said that the clarity was appropriate and that she would not ask Dr. Okafor to soften anything. She said that she wanted to tell her two things and that she wanted to tell them in a specific order. She said the first thing was technical and the second thing was a question.
Dr. Okafor said go ahead.
Sena said that Helix's lead interface architect had completed a technical solution for the surgical overlay depth communication system. She said the solution had been developed and tested over the previous day and a half and that it had been reviewed by her personally and that she had read the full technical specification and the test documentation and was prepared to characterize it, in her non-technical assessment, as the most careful piece of remediation work she had seen produced under pressure in nine years of client management. She said the architect's recommendation was a two-week monitored pilot with non-critical procedures before full deployment, and that this recommendation was not a hedge or a delay tactic but a genuine professional judgment that any change to a surgical environment warranted a monitored period regardless of the developer's confidence level.
She said the second thing was a question.
Dr. Okafor said she was listening.
Sena said she wanted to ask whether the hospital's surgical teams had been given any structured guidance on working with the null-percept overlay in its current state, or whether the individual surgeons were making their own decisions about when the overlay was usable and when to disable it. She asked this because the answer would determine what Helix could usefully provide in addition to the technical solution, which was documentation and protocol guidance for the transition period, something that would give the surgical teams a framework for their decisions rather than leaving each person to develop their own threshold for confidence in a novel perceptual environment.
There was a pause that was longer than the ones before it.
Dr. Okafor said that was a perceptive question. She said that the guidance had been informal. She said that she had not considered the documentation angle and that she would like to discuss it further once the pilot parameters were established.
Sena said she would send the pilot specification and the technical documentation by end of day and that she would include a proposed structure for the transition protocol alongside it. She said she looked forward to working through the pilot together.
The call ended. Sena sat for a moment with her hands flat on the desk, a thing she did sometimes after calls that had required the full weight of her attention, a brief physical grounding before the next one.
She thought about what Elian had said about the surgical overlay solution. She had read the specification at six in the morning and she had understood most of it and the parts she had not understood she had understood well enough to know they were right, which was a different kind of understanding but a real one. She thought about the twelfth variation and the luminosity offset and the way he had written in the specification that the null-percept's threshold quality was serving as a feature rather than a liability in the mixed-light camera feed environment.
A feature rather than a liability.
She wrote this phrase in the small notebook she keeps beside her call desk, not because she has a specific use for it yet but because phrases that reconfigure a problem rather than describe it are worth keeping. She had started the notebook the day after Event Zero and it had twelve pages of entries now, most of them technical observations from Elian's remediation work filtered through the client conversations where she had seen those observations land on people who needed them.
The notebook was becoming something. She was not sure what yet.
The fifth call was a building systems management client whose automated lighting infrastructure across seventeen commercial properties had calibrated its after-hours dimming protocols against a target darkness value that no longer existed. The buildings were not going dark enough at night. They were stopping at the null-percept, which was as dark as the system could make them, and the null-percept read to the human eye as not fully dark, and the building managers were receiving complaints from tenants who felt that their spaces did not feel secure in the way that properly dark spaces feel secure. This was, in the hierarchy of Lost Black consequences, not a safety-critical issue. It was a comfort issue, which was the category of issue that was hardest to explain to clients because comfort issues feel less urgent than they are. A person who does not feel secure in their building at night is not in danger, usually, but the feeling of insecurity has its own costs and its own cascade and Sena was aware of this and made sure the call treated it with the weight it deserved.
She spent the sixth call managing a client who had heard about the liability position she had communicated to Hana Yun and wanted to discuss it, aggressively, which she handled without matching the aggression because matching aggression in a business context is almost always less effective than receiving it calmly and redirecting it toward the question of what both parties actually need.
What the client actually needed was to feel that Helix was taking responsibility for something. Not legal responsibility. Moral responsibility. The responsibility of a company that built a thing that stopped working correctly to engage seriously with the experience of the people who depended on it. Sena told them that Helix was taking exactly that responsibility and she described the remediation program in enough detail that the description itself was evidence of the seriousness, and by the end of the call the client's posture had shifted from adversarial to collaborative without either of them having to acknowledge that the shift had occurred.
She ate lunch at her desk between the seventh and eighth calls. Something from the dispenser, the same thing she had ordered twice this week, chosen for the same reason Elian chose his meals, which is that choosing requires a decision and decisions are finite.
She thought about this as she ate. The two of them making the same choice for the same reason without having discussed it, both of them rationing the same resource in the same way because the work was consuming the capacity for small choices along with everything else. She found this both reassuring and slightly funny, the parallel economies of people under the same kind of pressure. She considered mentioning it to him and decided not to because mentioning it would require explaining why she had noticed and explaining why she had noticed would require more words than the observation was worth.
The eighth call was the one she had been least prepared for.
The client was a small architecture firm based in New Cascadia, not a critical infrastructure client, not a safety-sensitive deployment, a visual design firm that used Helix's spatial modeling interface to present design concepts to clients in immersive three-dimensional environments. The firm's managing partner, a man named Theo Vance who had been a Helix client for four years and who had always communicated with Sena in the easy register of someone who regarded the relationship as a partnership rather than a vendor arrangement, called not to discuss the technical issue but to ask something else.
He said that he had been using the null-percept in his design work for a week now, not because he had been remediated but because he had been experimenting with it, trying to understand what it could do rather than focusing on what it could no longer do, and he wanted to tell her something.
Sena said she was listening.
He said that the null-percept was doing something in his spatial models that black had not done. He said that when he used black in the depth field of a spatial model it communicated finality, the space ended there and there was nothing beyond it and the viewer's imagination stopped at the boundary. He said that when he used the null-percept in the same position it communicated something different. The space did not end there. The viewer's imagination did not stop. The null-percept read as the limit of what was shown rather than the limit of what existed, and this was making his design presentations different in a way he was still working out how to describe, more open, more suggestive of possibility, less like a complete object and more like a view into something larger than the model.
He said he did not know if this was useful information or if it was just him talking about his own creative process, which he acknowledged was not what she was there for.
Sena said it was useful information. She said it more directly than she usually said things in client calls because the directness was warranted and because Theo Vance would receive it correctly. She asked if she could share it with the technical team.
He said of course and asked if the technical team would know what to do with it.
She said she thought one member of the technical team would know exactly what to do with it.
After the call she opened her notebook and wrote what Theo Vance had said in his words rather than hers, as precisely as she could reconstruct them, because his words were more accurate than any paraphrase she could produce. Then she opened a message to Elian.
She wrote that she had a client observation she thought he would want to read. She attached the notebook entry. She said she was not sending it as a technical brief or a client request. She said she was sending it because she thought it was about the same thing he had been writing about in his investigation file, the thing he had told her in the note attached to the surgical specification, that the null-percept was not a wound and was not a healing but something that did not have a word yet.
She said she thought Theo Vance might have found part of the word.
She sent it. Then she closed her notebook and opened the brief for the ninth call.
Outside her window Site 7-North hummed its construction hum, the sound of a settlement that had not yet decided what it was, the infrastructure breathing in the thin Martian air. The sky above was the butterscotch amber it always was in the middle of the day, and the shadows at the base of the structures outside were the null-percept, and she looked at them for a moment with the attention of someone who is trying to see something clearly rather than just see it.
The null-percept at the base of the structures did not look like the end of the light. It looked like the place where the light stopped knowing what was there.
She thought that was not nothing. She thought that was possibly quite a lot.
She opened the ninth call.
Her voice was the same as it always was.
She was entirely there.