The Alpha’s Unwanted Wife

Elara Veyne arrived at the corridor review with the day already compressed around the release window. The contractor had mobilized before dawn. Utility access was booked for early afternoon. At four, the hospital-route slot closed, and missing it would force the crews to stand down and return under a new traffic plan. The people around the table had come expecting a final check, a signature, and movement. Elara opened the release packet. The parcel chain was clean. The municipal signer matched the permit. Utility coordination had been acknowledged. The corridor authorization carried the Blackridge office seal everyone expected to see. She almost moved on. Then the citation beneath the authorization failed to open. Elara clicked it again. The system returned the same error: SOURCE ENTRY UNRESOLVED. She copied the citation number into the archive search and found the Blackridge directive attached to it. The directive named the office responsible for the corridor and the department charged with administering it. A second reference sat beneath that language. She opened that one. Another administrative instrument. The same pattern repeated. Office. Function. Custody. A reference backward. Elara leaned closer to the screen. “Get me the first instrument in this chain.” The records analyst shifted to the archive console. Around him, screens still showed contractor check-in, utility timing, and traffic-control coordination. The release looked finished everywhere except in the one place Elara could no longer ignore. The analyst found an older entry. It assigned the corridor function to a Blackridge department after a territorial consolidation. It named staff responsibilities and implementation limits. It did not identify the authority from which the corridor function had originally been derived. Elara traced the footnotes. One sent her to a maintenance directive. Another to a service-area schedule. A third to an obsolete numbering index. Each document explained who had done the work at a particular time. None reached the beginning. The project lead moved to her side of the table. “Is this a broken link?” Elara kept reading. “It’s more than one.” She opened the metadata panel. The corridor function had an authority-class code older than the department currently administering it. The code survived every reorganization in the chain. The source field attached to that code was empty. The analyst found another historical entry and sent it to her screen. Elara compared dates. The corridor function existed before the Blackridge directive that everyone had treated as its foundation. The directive had not created the power. It had assumed the power was already there. That distinction settled coldly in her attention. She asked the analyst to search by the authority-class code rather than the corridor name. A new result list appeared. Some entries were duplicates. Some were fragments. Several referenced departments that no longer existed. The oldest readable item carried the same code and the same absence where an originating instrument should have been identified. Someone near the wall checked the time. Elara did not. The schedule had been the center of the meeting when she entered. Now it sat at the edge of her awareness, important but unable to answer what was on the screen. The project lead studied the chain with her. “We know which office uses the authority and who administers the corridor.” Elara nodded once. His gaze stayed on the empty source field. Elara enlarged the chain so the analyst and operations staff could see the break without leaning over her shoulder. The structure was simple once stripped of all the files that had accumulated around it. A present office exercised a corridor function. That office relied on an older directive. The directive relied on an authority class. Nothing on the screen established where that authority class came from. Elara felt the room finally catch up. The analyst stopped typing. Operations stopped discussing crew timing. The project lead’s attention moved away from the release checklist and fixed on the missing source field. Elara rested one finger beside it. “This is the question,” she said. “Who gave anyone this power?” No one answered. They had names for the offices that used it. They had decades of files showing the corridor function passing from one department to another. They had dates, seals, signatures, schedules, and implementation instructions. They did not have the beginning. Elara looked at the authority-class code again. Until they found its source, every later document in the chain rested on an unanswered question. The analyst broke the silence by opening a second archive window. If the authority-class code had no originating instrument attached to it, the next best answer was the history of how Blackridge had used it. Elara watched him build a chronology from signatures, departmental orders, and corridor actions extending back through decades of administration. The first stack looked persuasive because it was so consistent. Blackridge officials had signed access approvals. Blackridge departments had funded maintenance. Blackridge counsel had defended the corridor in disputes. Successive offices had behaved as if the power belonged where everyone assumed it belonged. The project lead pointed to the dates. “That is not a temporary arrangement.” “No,” Elara said. “It is a long arrangement.” He waited for more. She gave him none until the analyst placed the oldest signature beside the newest. The names changed. The office titles changed. The seal changed twice. What did not appear was any instrument explaining why the first Blackridge signer possessed the corridor power to begin with. Elara moved the oldest approval into a separate pane. “Show me what this signer relied on.” The analyst traced the citation. It led to an administrative schedule adopted during territorial consolidation. “And that schedule?” Another citation. Another Blackridge document. Elara read the operative language carefully. It assigned duties. It recognized ongoing functions. It preserved service delivery. Useful language, all of it. None of it answered the question she had put on the table. She could feel the room resisting the distinction because the distinction was expensive. The project lead folded his arms. “If every office since consolidation treated the authority as Blackridge, what else would you call that?” “Practice.” The word landed without drama. Elara turned the display so the chain faced the room. “Practice tells us what people did. It does not tell us what they were entitled to do.” The records analyst enlarged the consolidation schedule. One clause referenced continuity of administration during transition. Another preserved existing service obligations. Neither assigned the underlying sovereign power. Operations shifted behind her. Someone checked the contractor clock again. Elara kept going. They pulled a later legal memorandum. It assumed Blackridge control but cited no source beyond the same consolidation papers. A dispute resolution from twelve years earlier treated the corridor office as competent without reaching the origin question because neither party had challenged it. A budget instrument funded the work. A municipal compact recognized the office. Each item made the history thicker. None made the beginning clearer. The analyst finally sat back. “We can prove uninterrupted Blackridge administration.” Elara nodded. “Put that in.” He began typing into the review summary. “And put in what we cannot prove.” His hands paused over the keyboard. The project lead looked at her. This time he did not argue. Elara dictated slowly enough that each clause could be challenged before it became permanent. “Blackridge has continuously administered the corridor authority class through multiple offices and reorganizations. The reviewed materials establish use, custody, and institutional continuity.” The analyst entered the sentence. Elara looked again at the blank source field. “The reviewed materials do not establish the originating sovereign basis for that authority or demonstrate that the underlying power passed to Blackridge with the administrative functions.” The analyst stopped typing for half a second, then finished. There it was. The distinction was no longer something Elara was insisting on across a table. It existed in the review summary where the next person, and the person after that, would have to confront it. The project lead read the paragraph twice. “So decades of signatures get us nothing?” “They get us exactly what they prove.” His jaw tightened. Elara understood the frustration. If accumulated practice could answer the question, the release would already be moving. But convenience did not turn one kind of evidence into another. She pointed to the first sentence. “This proves Blackridge administered the function.” Then to the second. “This says we still do not know whether Blackridge received the power underneath it.” The room did not soften around the answer. It became more precise. The analyst saved the amended summary. The new language appeared beside the release packet. The project lead read it, then stopped tapping his stylus against the table. The analyst left both sentences on screen. Elara watched the save confirmation settle onto the screen. Now the file itself refused the assumption that had carried the corridor for decades. Operations did not accept the amended summary as the end of the question. The moment the analyst saved it, the operations representative moved to the delegation tab and opened every authority route still available beneath the disputed class. The first belonged to the municipal office. The second sat with corridor administration. A third covered emergency access under existing delegated powers. Elara watched the list narrow. “If the source is missing, can the delegated office still act?” the project lead asked. The analyst looked to Elara. “Only if the delegation can stand without the source it claims to descend from.” They tested it. The municipal delegation referenced the corridor class directly. The corridor office delegation referenced the same class through the consolidation schedule. Emergency access relied on a standing Blackridge order that assumed the corridor authority was valid before the emergency provision could activate. Every route returned to the same blank field. The operations representative swore under his breath and brought up the contractor board. Two crews were already on standby. A utility isolation team had a ninety-minute window. Traffic control was staged for the hospital route, and the permit attached to that staging would expire before the next available slot. Numbers appeared beside each delay. Elara read them because refusing the authority did not make the cost imaginary. The project lead asked whether they could separate physical work from the corridor authorization and proceed only with tasks already covered elsewhere. That question had an answer. Elara and the analyst stripped the work plan down line by line. Survey activity could continue. Equipment could remain staged off corridor property. One utility preparation step belonged to an uncontested municipal permit and could proceed. The access crossing, however, depended on the disputed corridor power. So did the traffic-control activation tied to it. The project lead marked the surviving tasks. It was not enough to preserve the day. “Can we issue a conditional release?” he asked. Elara shook her head. “A condition cannot cure missing authority.” He stared at the schedule. She understood what he saw. Standby charges. A lost utility window. A hospital-route sequence that would have to be rebuilt around whatever opening came next. People would spend money because she had refused to let an old assumption stay invisible. She kept her hand on the table. “Change the release state,” she said. The analyst selected source authority unresolved and opened the confirmation screen. A warning filled the screen. The change would suspend the corridor release, notify operations, and remove the package from the authority of the local review team. Further action required escalation under the governance chain attached to the disputed class. The project lead read the warning over the analyst’s shoulder. “If you confirm that, we lose control of the timing.” Elara looked at the remaining green tasks on the work plan. “The authority failure already took the timing from us. Keep everything else moving. Only the disputed class stops.” The analyst confirmed. The release indicator changed from green to red. Messages began arriving almost immediately. Contractor coordination requested instructions. Utility scheduling flagged the missed isolation window. Traffic control asked whether to release the hospital-route slot. The project lead answered them one by one while Elara checked that the suspension had not spread beyond the exact authority class. It had not. The corridor crossing was stopped. The rest of the work remained live where another power supported it. The distinction did nothing to soften the cost. A crew supervisor called to confirm demobilization. The project lead muted the room while he answered, then returned with his jaw set harder than before. “The next utility opening is tomorrow afternoon.” Elara entered the update into the case notes. The project lead watched her enter the update and accused her of knowing the day would collapse this way. Elara looked up. “I knew delay was possible. I did not know the source would fail. Now that it has, pretending otherwise would only make today easier by making the record worse.” He turned away before answering. On the shared screen, the red release state gained a second line. ESCALATION REQUIRED. The local review controls disappeared. A new routing panel opened in their place, asking the analyst to forward the matter to the next authority level capable of addressing a sovereign-source defect. The room had begun the morning waiting for Elara to clear a corridor. Now the corridor was stopped, the cost was accumulating, and the question had moved beyond anyone at the table.