The relay tower logs the crossing without ceremony. Branch 12 reads 81% at 4:13 AM Saturday. It read 79% at 4:13 PM Friday, when he was watching. At some point between those two readings (overnight, while he slept) the branch crossed 80%, and the tower recorded that crossing in its batch log the same way it records everything: timestamp, branch identifier, signal strength, processing flags. The tower does not know that 80% is a threshold. Its batch log format does not have a field for significance: RLY-12|08:13|0.81|OK|NO-FLAGS. It does not know that Marcus has been checking the readouts twice a day for eleven weeks, or that he has been explaining Branch 12's progress to three different working groups, or that the September 17 agenda has an item specifically dedicated to documenting what Branch 12 has been doing. The tower processes. That is the complete description of what it does.
He sits at the desk with the readout on the screen. 81%. The number does not feel like anything. He expected to feel something when Branch 12 crossed 80%, some small confirmation, the thing you feel when a project moves from provisional to substantiated. That feeling has not arrived, or arrived so quietly that it already passed. What he has instead is the number, and the log, and the knowledge that the tower made this crossing without anyone watching.
This is, he thinks, probably how most thresholds are crossed.
The September 3 letter is in the outbox. He wrote it Thursday, reviewed it Friday, and has not opened it again since. The letter goes to Deacon Mira at the sub-registry board and to the two working group leads, not to announce a result, because the result is not his to announce, but to provide the documentation that the September 17 agenda item requires. What the letter says is this: Branch 12 has been processing at consistent rates since July. The signal behavior has been stable enough to characterize. The attached readouts represent eleven weeks of twice-daily observations. The working groups have reviewed this data and have prepared their assessment. The September 17 agenda item 3 will present the working group assessment and recommendation. The sub-registry board will determine whether to initiate a formal naming review.
He did not write: I believe Branch 12 should be named.
He did not write: the data is clear enough that delay is institutional caution, not genuine uncertainty.
He did not write that because it is not his determination to make. This is the distinction he worked out in Wednesday's session and confirmed in Thursday's afternoon revision and added to the September 17 agenda as a two-sub-bullet clarification. Working groups document and recommend. Registry boards name. The authority lives in the jurisdiction, not in the evidence. He has the evidence. The board has the authority. The letter is the bridge between them, and the bridge does not have opinions.
The vocabulary page is in the second drawer. Seven words. He started it in March, the week the first working group reviewed the preliminary data and told him the data was interesting but not yet characterizable. The first word was characterizable, because he had not known that word was the threshold until the working group used it and he felt the gap between what the data showed and what the institutional vocabulary could process. He wrote the word down that evening. Not a complaint. A record of the interval.
Word two was substantiated, which is different from characterized, which is different from verified, which is different from confirmed. Each of those differences matters to a registry board even if they are invisible to the data itself. He added substantiated in April. He added causal attribution in May as a two-word entry, which felt like cheating but the two words do different work than either word alone. In June he added attribution threshold: the point at which a pattern is strong enough that failing to name it becomes its own kind of institutional decision. By June he had five entries. The page is not a glossary. It is not a complaint. It is a record of the places where he has had to wait for language to catch up to what he was observing. The relay tower has no such page. It logs what it logs.
The seventh word is provisional.
He added it Friday evening, after Branch 12 read 79% and before he went to sleep. Provisional is what you call something that is known but not yet officially named. Not because it is uncertain, but because the institutional structure that would make it official has not yet acted. Branch 12's behavior has been clear to him since July. It has been clear to the working groups since August. What is provisional is not the knowledge. What is provisional is the name. The relay tower processes at 81% this morning without knowing it is called Branch 12. Branch 12 is what the working groups have been calling it. If the sub-registry board initiates a formal naming review after September 17 and the review concludes, and the board votes, and the name is ratified, then Branch 12 will have a name in the registry. The name will be what the board decides. It may not be Branch 12.
He has not told Annika what he thinks the name should be.
He has not told Annika anything for eighteen days. He sent her two notes in that silence: one in the first week, one ten days ago. The notes were not asking for anything specific. The first said that the working group review had gone well and that he had the readout documentation she asked about in June. The second said that the September 17 agenda was finalized. He did not say: I am thinking about what you said in May. He did not say: the vocabulary page has seven words now. He has not said these things because Annika does not answer notes when she is in her writing period, and he has known this about her for four years, and the silence is not a problem.
He checks the note timestamps anyway. It is 4:13 AM, eighteen days since her last reply. The first note arrived; the second note arrived. He knows this because neither bounced. That is the complete information. He does not know whether she has read the notes. He does not know whether she is three months into something that might become a paper or three weeks into something she will abandon by October. He knows that she is not a person who confirms receipt when she is working. He knows that he sent the notes and that they arrived. Everything else is outside his information.
The relay tower does not know Annika exists. The tower does not know that the note Marcus sent ten days ago mentioned the September 17 agenda, or that the agenda has a two-sub-bullet clarification that started as a conversation about naming authority that he has been having with Annika since the spring. She was the first person who pointed out that the distinction he was struggling to articulate, the distinction between the working group's authority to assess and the board's authority to name, was a jurisdictional question, not an evidentiary one. He had been treating it as a problem with his argument. She said: the argument is fine. The argument doesn't have authority. That is a different thing. He added jurisdictional to the vocabulary page and then removed it because the word was too ordinary to need recording. The distinction itself is what he needed. He has the distinction now. He wrote it into the agenda in two sub-bullets.
The tower logs Branch 12 at 81% at 4:13 AM Saturday. It will log another reading at the next cycle. The crossing of 80% is in the batch log, timestamped, unflagged. The tower does not distinguish milestone crossings from ordinary readings. All readings are ordinary readings. The tower processes.
He thinks about the word provisional as a description of his current situation and finds it more accurate than he expected when he wrote it down.
What he knows: Branch 12 has been crossing thresholds all week, and each crossing has been recorded, and the documentation is complete, and the letter is ready, and the September 17 agenda item is settled. What is provisional: the name, the formal record, the institutional acknowledgment of what he and the working groups have been observing since July. He is in the interval between the knowledge and the name. He has been in this interval for eleven weeks. On September 17 the interval may end. Or it may extend, because naming reviews take time, because the board has its own timeline, because the sub-registry board's calendar does not organize itself around his eleven weeks of twice-daily readings. Institutions move in their own rhythms the way relay towers process in their own cycles: continuously, without announcement, according to their own logic.
He is not impatient with this. He made his peace with it somewhere around the fifth word on the vocabulary page.
The desk faces east. The window shows the first faint differentiation between sky and not-sky that precedes dawn without being dawn. He knows that in an hour it will be light. He knows that Branch 12 will read higher (the morning cycle tends to run clearer than the overnight, and that the tower will log that too, and that the September 3 letter will go out on Tuesday whether or not Branch 12 reads 82% by then. The threshold that matters is not 80%. The threshold that matters is the one the sub-registry board decides is sufficient for a formal naming review, and he does not know what number that is, because the board has not published that threshold. They may not have one. Naming reviews may be initiated on qualitative grounds. He has asked this question to three people and gotten three different answers.
This is also, he thinks, what the vocabulary page is for. The places where the institutional language has not yet decided what it means. Not a critique of the institution. A record of a real interval. The interval between the relay tower logging 81% and the sub-registry board issuing a formal naming determination is not a failure. It is just time. It has a texture. He has been living in that texture for eleven weeks and he has been writing down the words that mark its edges.
Branch 12 at 81%. The tower on its early cycle. Six days to September 3. Seventeen days to September 17. The vocabulary page with seven words. The letter ready in the outbox. Annika somewhere in her silence. The window showing the not-yet-light.
He does not add an eighth word. He does not open the letter. He does not send another note.
What he does: closes the readout screen. Goes to the kitchen. Puts water on. Waits for the kettle, which heats at its own pace and does not know it is Saturday. When the water is ready, he makes coffee. He brings the coffee back to the desk. The readout screen is dark. He does not turn it back on.
There is a specific quality to a Saturday morning when you are waiting for something that will not happen until Tuesday. Not anxiety. Marcus has been anxious before, and this is not that. It is more like the quality of a document that is finished but not yet sent. Complete in itself. Waiting for the day that is the right day for it to leave.
He sits with the coffee. The kettle has finished its work and does not know this. Outside, the relay tower processes its early cycle, and Branch 12 reads 81%, and the batch log adds another timestamp, and none of that has anything to do with coffee or Saturday or the particular quality of light before dawn when you have slept, and know what day it is, and are in no particular hurry.
The letter is ready. The agenda is set. The vocabulary page has seven words. This is enough for now.