The Alpha’s Unwanted Wife

If Elara Refuses

The second family’s advocate opened the next session with a simulation rather than another archive exhibit.

He asked the clerk to run the proposed temporary arrangement through an ordinary corridor workflow.

The reviewer allowed it.

The screen generated the first form.

AUTHORIZING ACTOR.

The current leading family would be entered there.

The second form asked for the source behind the permit.

The current hearing order would be entered there.

A contractor notice followed.

Then an internal service log.

Then a later renewal request.

Each new document inherited information from the one before it.

The advocate stopped the simulation after six entries.

“Now search the file as if you are a reviewer five years from today.”

The analyst did.

Six separate documents appeared.

All showed the same family acting.

All cited the same temporary hearing order somewhere in their history.

Only the first two displayed the original hearing safeguards on the first page.

The later forms carried shortened references.

The advocate enlarged the search result.

“This is the problem.”

The reviewer asked him to continue.

He removed the original hearing packet from the visible search and left only the downstream administrative documents.

A later reader would see repeated exercise.

Repeated signatures.

Repeated approvals.

Repeated acceptance by contractors and departments.

The pattern looked increasingly settled even though every entry had descended from one temporary decision.

Elara watched the simulation build the kind of paper trail that had caused the corridor dispute in the first place.

The advocate did not claim any of the simulated documents would be false.

They would be accurate descriptions of actions actually taken.

That was precisely why they could become dangerous.

A lawful temporary act could generate a long history of lawful temporary acts.

Later, the history itself could be mistaken for independent proof.

The hearing clerk marked the issue.

SELF-REINFORCING ADMINISTRATIVE HISTORY.

The advocate opened the original draft again.

His objection was not that the leading family had failed to earn the current evidentiary position.

He expressly preserved the existing comparison.

His objection was that exercise created after the comparison could begin feeding back into the comparison.

The reviewer asked whether a disclaimer on every form would solve the problem.

The advocate requested another simulation.

The clerk added TEMPORARY — NO FINAL EFFECT to each generated document.

The search result still showed six acts by the same family.

The disclaimer reduced ambiguity.

It did not make the acts disappear.

The advocate pointed to the result.

“A future dispute can argue about the disclaimer. It cannot argue that the acts never happened.”

The reviewer left the simulation on the wall.

The project lead joined remotely and studied the forms.

He wanted movement on the corridor.

The simulation showed why movement itself could alter the future evidentiary landscape.

The clerk tested one more variable.

What if the temporary actor changed later?

The system generated a second family name on the seventh document while the first six remained intact.

The history then looked like an earlier period of one-family exercise followed by a later switch.

Nothing in that visual explained whether the first period had been temporary, mistaken, provisional, or merely superseded by new evidence.

The advocate let the example stand.

The reviewer entered a finding on the objection only.

PROPOSED TEMPORARY EXERCISE PRESENTS A RISK OF CREATING ADMINISTRATIVE HISTORY THAT MAY LATER BE MISREAD AS INDEPENDENT EVIDENCE.

No remedy followed.

The clerk did not edit the draft.

No new limitation was inserted.

No operative term changed.

The hearing had not reached those questions.

It had identified the defect the proposed arrangement had to answer before it could move forward.

Elara read the finding.

Her family’s current lead remained exactly where it had been before the simulation.

The second family remained exactly where it had been.

What changed was the burden on the proposed temporary solution.

It could no longer be judged only by whether the present evidence justified using it today.

The hearing also had to account for the history that use would manufacture tomorrow.

The reviewer closed the simulation and left the objection marked SUSTAINED FOR REDRAFTING.

The proposed arrangement returned to the clerk without a ruling.

The rival had not defeated the leading family.

He had prevented the leading family’s present advantage from becoming a machine that quietly enlarged itself.

The clerk reopened the temporary-use draft beneath the ruling from the simulation.

SELF-REINFORCING ADMINISTRATIVE HISTORY.

Elara went first to the service list. The corridor authorization and its directly linked access approval remained inside the proposed scope. The neighboring service-coordination function sat in a separate row because the family-specific evidence had never reached its code.

“Does Veyne want the third function restored?” the chair asked.

“No.”

The clerk removed the row from the operating template.

The next problem was the paperwork created by temporary exercise. The sample permit still named Elara as the acting source for the current period. The service log repeated her name. A renewal form inherited the same entry.

Elara tapped the source field.

“Put the case order beside my name on every one of them.”

The clerk changed the template. The case number appeared in the same line as the actor field, followed by TEMPORARY AUTHORIZATION UNDER ACTIVE CLAIMANT PROCEEDING.

The second family’s advocate leaned forward on his screen.

“And those records stay attached to that source when someone searches them later.”

Elara looked at the simulated five-year file. That was the weakness the prior version had exposed. Six records could look like six separate pieces of historical practice even though all six descended from one temporary order.

“Attach them.”

The chair directed the clerk to create a common source tag. Every permit, service entry, renewal, contractor instruction, and internal approval produced under the temporary arrangement would point back to the same case record.

A rule appeared beneath the tag.

ADMINISTRATIVE ACTS CREATED UNDER THIS ORDER RECORD PERFORMANCE UNDER THE ORDER. REPETITION OR DURATION DOES NOT ADD SUCCESSION WEIGHT.

The rival advocate asked that the language apply regardless of which family later occupied the temporary position.

The clerk stripped Veyne from the safeguard and made the rule claimant-neutral.

Elara accepted the change.

The project lead joined from the corridor and opened the excluded service-coordination row.

“That function is costing us another staffed shift every day.”

Elara pulled the evidence map beside it. Blackridge’s broader archive showed the neighboring code as Greyhaven-derived, but the claimant comparison had never tied that function to Veyne through the tested family-specific chain.

“Then the workaround stays until the record reaches it.”

The project lead looked away from the camera for a moment, then closed the row.

The reduced scope remained.

The second family’s advocate moved to access. Every administrative record created during temporary use would enter the shared case workspace at the same time for both claimants. His family could challenge a new source, a claimed expansion, or any operating record that appeared to outrun the order.

The chair added the same automatic reconsideration trigger already approved in the prior hearing. Materially changed lineage, continuity, supersession, or authentication evidence would return the temporary position to the tribunal while allowing either family to keep its current rights.

Elara read the complete set of controls.

Two functions.

One common source tag.

Shared access.

A standing review trigger.

No accumulation of new succession weight from repetition.

The field dashboard made the price visible. The corridor could gain a lawful source actor if the mechanism survived. The neighboring function remained on workaround. The second family would keep challenging Veyne while Elara exercised the temporary role.

The clerk ran the simulation again.

A permit appeared with Elara’s name and the case number side by side.

A contractor instruction inherited both.

The service log did the same.

Three months later, the mock renewal pulled its authority source directly from the case order instead of from the prior permit.

The advocate advanced the search five years.

The same series of Veyne actions appeared, but the results grouped under one temporary authority source. Opening any result exposed the active challenge notice and the original case basis.

The reviewer compared the new output with the earlier simulation.

A future reader could still see that Elara had acted. The file would also show why she had been allowed to act and where that permission ended.

The rival advocate preserved his objection to granting temporary power at all. He withdrew the specific objection that administrative repetition would automatically create fresh succession evidence.

The clerk marked that issue resolved.

Elara approved the revised language.

The redraft now gave Veyne a smaller operational reach than the first proposal and required every exercise of that reach to carry its temporary source with it.

That was the bargain she accepted.

If Veyne’s lead produced power before final succession, the power would remain answerable to the evidence that created it.

The next implementation review began with a single signature line still unresolved.

The clerk displayed the operating form that would travel with any corridor authorization issued under the temporary arrangement. Elara’s case number appeared in the source field exactly as Chapter 10’s redraft required. Beneath it, the administrative template proposed a second line:

BLACKRIDGE ALPHA RECOGNITION / CO-SIGNATURE.

The project lead explained why the line had been added. Contractors already understood Blackridge signatures. Internal systems knew how to route an Alpha-approved authorization. Adding Ronan’s recognition would let the first corridor permit move through existing workflows with less manual intervention.

Ronan read the form.

“Remove my signature. Route it some other way.”

The project lead looked up from the field connection, then opened the routing constraints.

Blackridge counsel opened the template notes. The co-signature had been framed as administrative confirmation rather than a grant of Greyhaven authority. In practice, every downstream system would place Ronan’s name beside Elara’s temporary authority source.

Elara felt the damaged bond tighten as the two names appeared together on the screen.

Ronan pointed to the source field.

“Her position comes from the claimant ruling. My office can acknowledge that the ruling exists. It cannot be written as the office that makes her position effective.”

The clerk separated the fields.

SOURCE AUTHORITY: ACTIVE CLAIMANT ORDER.

BLACKRIDGE IMPLEMENTATION NOTICE: RECEIVED.

The second line now recorded institutional notice instead of recognition.

Counsel tested the change against the existing workflow. A permit could still enter Blackridge systems if the administrative office confirmed receipt of the case order. The receipt would prove that Blackridge had been notified and had opened the necessary execution channel. It would carry no language suggesting that the Alpha had conferred the underlying Greyhaven capacity.

“Will you approve the receipt field?” the project lead asked.

“Yes. Receipt is ours. Her source is not.”

The clerk entered the distinction into the operating instructions.

The second family’s advocate requested access to the same notice trail. If Blackridge later claimed that its receipt transformed the temporary position into delegated Blackridge authority, the challenger needed the underlying forms available for review.

The chair granted the request under the shared-access rule already in force.

Elara studied the revised permit.

Her name appeared once, beside the temporary case authority.

Ronan’s office appeared in a different section, beside the system receiving the order.

The page no longer made their powers look like one combined grant.

The distinction cost another hour. Blackridge’s software required a manual override because the authority-source field usually expected an internal office code. The project lead showed the queue building while the systems team created a temporary external-source route.

Ronan authorized the work.

He could have put his name on the form and let the old system treat the problem as familiar.

Instead, Blackridge had to change its own machinery enough to recognize an authority source that sat outside the Alpha office.

The clerk ran a test authorization.

Elara’s case number entered first.

The system flagged the unfamiliar source.

A Blackridge administrator attached the receipt notice.

The flag changed from UNKNOWN AUTHORITY to EXTERNAL AUTHORITY — TEMPORARY CASE BASIS.

The permit advanced to the next internal screen.

No Alpha recognition field appeared.

The rival advocate inspected the audit trail. The same challenge notice that followed Elara’s temporary position remained attached. If the claimant evidence shifted, the source record would return to review while Blackridge’s receipt remained only a record of what it had processed at that time.

The chair saved the operating form.

Ronan’s refusal had made the workflow less convenient and more exact.

Blackridge would execute around a Greyhaven-derived temporary source rather than pretending the source had become Blackridge power through his signature.

Elara looked across the table at him.

The bond pulled hard enough to make the distance between their chairs feel deliberate.

Neither of them used it.

The clerk marked the co-signature proposal withdrawn and replaced it with the external-source receipt procedure.

The temporary mechanism survived its last implementation challenge.

If the ruling issued, Veyne could act inside the two tested functions on the strength of the claimant record itself. Blackridge would receive and execute the resulting instructions through its systems, with Ronan’s office serving as administrator of its own machinery rather than author of Elara’s Greyhaven position.