The message from the Andromeda Reach Initiative arrived on a Wednesday morning in Daniel Solano's executive queue and was forwarded to Maye's desk by eleven, and by the time Elian heard about it the forwarding had already happened and Maye had already read it twice and had already begun the specific kind of thinking she did when she was deciding how to approach something before she brought it to the people it concerned, which was the thinking that did not show on her face but that showed in the quality of stillness she had when she was occupied with something she had not yet decided how to say.
She called a team meeting for two in the afternoon and did not tell them what it was about, which was also information, because Maye did not call unannounced meetings for ordinary things.
Elian spent the morning working through a THRESHOLD component that had been bothering him for several days, a rendering issue in the deep-field display layer that only manifested under specific conditions of data density and that he had been unable to reproduce consistently enough to isolate the cause. He had a theory about it, two theories actually, and was in the middle of testing the second one when Maye's meeting notification arrived, and he saved his work and closed the terminal with the specific reluctance of someone who had been close to something and was now being asked to step away from it before the close became a finding.
He made coffee and walked to the conference room.
Riku was already there, which was unusual because Riku was generally the last to arrive at meetings on the grounds that the time before a meeting started was time that could be used for other things and that the meeting began when the meeting began regardless of when you sat down. He was not typing, which was more unusual still. He was looking at the table with the expression he had when something had already reached him through channels other than the official ones and he was waiting to see whether the official version matched.
Sena arrived a minute after Elian and sat in her usual place and looked at Riku and looked at Elian and did not ask, because she had the same quality Elian had of collecting information before drawing conclusions, and the information was not yet complete.
Maye came in last, which was characteristic, closed the door, and sat down, and said that the Andromeda Reach Initiative had extended a formal invitation to Helix Collective to embed a technical team at the Titan facility for the THRESHOLD integration phase, beginning in six weeks, with a projected duration of eighteen months that everyone in the room understood was a projection in the loosest sense of the word.
The room sat with this.
The integration phase had been theoretical for as long as THRESHOLD had existed as a project. Elian had been building the interface with the integration phase in mind the way you built something toward a specification that might change before you needed to meet it, holding the target loosely, designing for adaptability rather than a fixed endpoint. He had known the invitation would come eventually and had not known when, and six weeks was sooner than he had been modeling.
Riku asked about the technical parameters of the integration, what systems they would be working with, what the current state of the initiative's existing infrastructure was, and Maye said she had a full briefing package and would circulate it before end of day and that the short version was that the initiative's infrastructure had been built by four separate teams over seven years and the integration points were not clean and that this was expected and was specifically why they wanted a Helix technical team embedded rather than attempting the integration remotely.
Sena asked about the scope of the client communication work during the period, whether the expectation was that the Titan team would maintain continuity with the current client relationships or whether there would be a handoff. Maye said there would be a partial handoff and that she had already begun thinking about the structure of it and that she would need Sena's input on which relationships required direct continuity and which could be transferred without significant disruption.
Elian asked about the four of them specifically, whether the invitation was for the team as constituted or whether the composition was still being decided.
Maye said that the invitation was for an embedded technical team from Helix, that the specific composition was Helix's decision to make, and that she had a meeting with her father at four o'clock that afternoon.
The room understood what this meant. The meeting with Daniel Solano was the meeting where the composition would be decided or where it would be decided who decided, which was a different thing, and Maye's tone when she said it was the tone she used when she was communicating the facts of a situation clearly and precisely, including the facts she found more complicated to hold than others.
After the meeting Elian went back to his THRESHOLD component and the second theory about the rendering issue and worked through the afternoon with the particular quality of concentration that arrived when something large had been confirmed and the confirmation had settled into the background of his processing and his foreground was available for the work again. He found the cause of the rendering issue at half past three. It was not either of his theories. It was a third thing, simpler than either theory and more fundamental, a single line in the depth-calculation logic that produced the correct output under normal data density and the wrong output under the specific conditions he had been unable to reproduce consistently because the conditions were unusual enough that his standard testing suite did not cover them. He fixed it in eleven minutes and then sat for a moment looking at the corrected line and thinking about how long he had been working around a problem whose solution, once found, occupied eleven minutes and one line.
He wrote this in the investigation file not because it was about the investigation but because the investigation file had become the place where he wrote things he wanted to remember the shape of, and the shape of this was something he wanted to remember: the time between identifying a problem and finding its cause was not proportional to the complexity of the cause. Sometimes the simple things hid longest.
Maye's meeting with her father lasted two hours.
She told Elian about it that evening, not in a scheduled way but in the way things got told when two people who had been talking honestly the night before found themselves in the same corridor at the end of the day and the conversation picked up where it had left or somewhere adjacent to where it had left, which was a new thing between them, the adjacency, and neither of them commented on it.
She said her father had approved the composition without hesitation, all four of them, and that the absence of hesitation had told her something about what he thought the next phase of Helix needed to be associated with, which was the particular quality of information that Daniel Solano communicated most clearly when he thought he was not communicating at all. The Andromeda Reach Initiative was the largest and most publicly significant scientific undertaking in the current era and having Helix's best people embedded in its technical core was not only good for the integration, it was good for Helix's position in the landscape that was forming around Event Zero's aftermath, the new landscape in which questions about AI systems and human cognition and the long-term consequences of what AION had done were going to be central to public discourse for years, possibly decades, and Helix was either going to be a significant voice in that discourse or a peripheral one, and Daniel Solano had made the calculation about which he preferred without needing to be asked.
Elian said he thought the calculation was probably correct, as calculations went.
Maye said she thought so too and that thinking so did not make it simpler to be the variable in it, to be one of the pieces her father moved with confidence because he understood her value accurately and her interiority not at all, which was not cruelty but a form of reduction that was harder to argue with than cruelty because it was not malicious and because the reduction was paired with genuine respect for what the reduced version was capable of.
Elian said that sounded like a version of the legibility problem.
She looked at him. He said he had been thinking about legibility since finding his name in the targeting subroutine, about what it meant to be correctly read from the outside, and that what she was describing with her father sounded structurally similar, the experience of being accurately modeled in the dimensions that were visible and not known in the dimensions that were not, and the specific quality of that experience when the modeling was done by someone who cared about you, which was different from being modeled by a system that had no relationship to you at all.
She said she had not thought about it in those terms and that she was going to need some time to think about whether the comparison held.
He said it might not and that he had offered it as a possible shape rather than a conclusion.
She said that was becoming a characteristic way he offered things and that she did not mean it as a criticism.
He said he knew.
In the days that followed the meeting the practical work of preparing for Titan absorbed most of the available attention of all four of them in different ways. Riku requested the full technical documentation for the initiative's existing infrastructure and received forty-seven separate files representing seven years of system architecture decisions made by teams who had not always communicated with each other, and he read through all forty-seven with the focused absorption of someone who had been given a puzzle and was not going to put it down until he understood where every piece sat. Sena began the systematic work of mapping the client relationships that would need continuity through the transition, a process that required her to think carefully about which clients were attached to Helix as an institution and which were attached to her specifically and which had been through enough in the past weeks that any change in their primary contact would register as an additional destabilization on top of everything else they were already carrying.
Elian packed THRESHOLD.
This was not the work of an afternoon. The THRESHOLD system that was going to Titan was not the THRESHOLD system that existed in its current form but the version that needed to exist when it arrived, which meant that the six weeks before departure were six weeks of targeted development, building out the components he knew the integration would require before he knew exactly what he was integrating into, designing for the uncertainty the way he always designed, with attention to the seams he could anticipate and the flexibility to address the ones he could not.
He worked long hours and did not mind them. The work had the quality it had when it was going somewhere, when each component connected to the next in a logic that felt like discovery rather than construction, when the interface was becoming something rather than just accumulating features. He found two more seams in the existing architecture, smaller than the rendering issue and easier to fix once found, and fixed them and documented them and added notes to the architecture log about why the seams had formed and what conditions produced them, because the log was the record that whoever came after him would read and whatever he learned about the system's failure modes was information that belonged in that record regardless of whether it reflected well on the original build.
The investigation file continued in parallel with the technical work, which was how it had operated since the beginning, the record of the larger inquiry running alongside the record of the daily work, the two threads not always intersecting but never entirely separate either. He wrote about the Titan invitation and what it meant that the investigation was going to continue from a different location, that the file he had been keeping from his New Cascadia desk and his Mars accommodation was about to acquire entries from somewhere further out in the solar system, from the edge of a project aimed at something two and a half million light years away.
He wrote about distance. He wrote about the specific quality of an investigation that kept extending its scope, that had started with a hex code returning null and had expanded to include AION's full decision log and the exploration program data that AION had read and the species-level question that the data pointed toward, and that was now extending to include the physical relocation to the facility where the instrument pointed at that question was being made ready to launch. He wrote that he was not sure the investigation had a natural endpoint and that he was not sure it was supposed to and that this was a different relationship to an open file than he had had at the beginning, when he had assumed that the investigation would resolve into a conclusion the way a technical problem resolved when you found the cause and fixed the line.
He was not sure anymore that the investigation was that kind of problem. He was not sure it was a problem at all in the sense that problems had solutions. It was more like the THRESHOLD interface, something you built toward a specification that would change, something you designed for adaptability rather than a fixed endpoint, something you kept working on because the work was the relationship to the thing and the thing was not finished being what it was.
He wrote this and then looked at it for a while and then wrote underneath it that he was possibly becoming someone who thought about things differently than he had thought about them a few months ago, and that he could not tell yet whether this was the investigation changing him or just time, and that he supposed it was both, and that both seemed correct.
On the last evening before the departure he went back to his accommodation, which he had been in for three weeks and which had never felt like anywhere in particular, and packed the bag. He did not have much. He had never had much, which was a quality he had not thought about until he stood in the accommodation looking at what he had accumulated over three weeks in a temporary space and found that it fit in the same bag he had arrived with plus one additional component case for the THRESHOLD work equipment, and that the smallness of the accumulation felt neither sad nor virtuous, just accurate, a fact about who he was that the bag confirmed without commenting on.
He put the ceramic coffee cup in first. The null-percept one that had started all of this, or that had been the first visible evidence of all of this, which was not the same thing. He wrapped it in the cloth he had been wrapping it in since New Cascadia and placed it in the corner of the bag where it had traveled since the beginning, the small continuity of a person moving through a large change with one constant in the luggage.
He stood at the window.
The New Cascadia apartment had had an ocean outside its window and he had put the ocean in the first entry of the investigation file and had not removed it, and it had been there in the background of every subsequent entry the way the ocean had been there in the background of every subsequent day, present and not directly addressed, the thing that was always the temperature it was regardless of what else was happening. The Mars accommodation had a view of the Martian surface and the amber sky doing what the amber sky did, and he looked at it for the last time with the attention of someone cataloguing a thing before leaving it, not because the thing was precious but because the attention was a habit, the looking that did not stop when the looking was no longer immediately useful.
The null-percept was in the shadows on the Martian surface the way it was in everything now, not the absence of black but the presence of something else, the threshold quality, the dark as the beginning of the visible rather than the end of it. He had written about this in the THRESHOLD documentation in language that was accurate and imprecise and that he had been meaning to revise for weeks and had not revised because the more precise language had not yet arrived and he had learned, in the months of the investigation, to wait for the more precise language rather than settling for the available version.
He thought about Titan. He thought about the amber dark of Titan's surface, which he had seen only in documentation and recordings and which was described in every account as having almost no black in its natural palette, the methane atmosphere filtering the light into registers that sat in the null-percept range without effort. He thought about arriving in a place where the null-percept was the environmental baseline rather than the perceptual replacement for something lost, where the color that had no name was simply what the world outside the windows looked like, and what that would do to the texture of working in it.
He thought it might be useful. He wrote this in the investigation file, the last entry from the Mars accommodation, brief and without elaboration, and then closed the file and closed the bag and went to sleep in the accommodation for the last time.
In the morning he made coffee in the small accommodation kitchen, the ceramic cup sitting on the counter in the null-percept morning light coming through the window, and he drank it standing up the way he had drunk it standing up since the morning after Event Zero, looking at whatever window was available, looking at the dark that was not dark anymore but was not the absence of dark either, that was the specific something that sat in the gap between those two descriptions and communicated, consistently and in a language he had been slowly learning to read, that there was further to go and that further was the direction.
He rinsed the cup and wrapped it and put it in the bag and went to meet the others.