Chosen By Ruin

Chapter 44 - The Reassignment Part 1

Maddox's POV

I send the fourth message to Dorne on Friday morning at nine-fifteen.

It is the fourth message in three weeks. The first message, three weeks ago, was a routine check-in — the kind of correspondence I have been sending Dorne for the past sixteen months, ever since I was old enough to be entrusted with the council-liaison portfolio. We exchange information. He gives me the small political readings of the Continental Pack Council from his vantage point as a council aide. I give him the Ironvale-side readings he is permitted to receive in exchange. It is a working relationship. It has been a working relationship for sixteen months. Until three weeks ago.

The first message: no response.

The second message, ten days ago, was a polite escalation — *Dorne, I have not heard from you, please confirm receipt.* No response.

The third message, last Tuesday, was framed as urgent — a request for a specific document Dorne has supplied four times in the last year, the kind of routine pull that should produce a response within forty-eight hours. No response.

The fourth message, this morning, is a test. I phrase it as if I am unaware that the previous three messages went unanswered. I open with the small social pleasantries Dorne and I have used since the beginning. I reference his daughter's wedding, which he mentioned in his last responsive message six weeks ago. I ask whether the wedding went well. I close with a soft request for an update on the council calendar — nothing urgent, nothing the absence of which would impair me, just an open door for him to walk through if he is in a position to walk through it.

I send the message at nine-fifteen.

I do not expect a response.

I am sending it to confirm the absence of response, not to elicit one. If Dorne is in a position to write back, the social-pleasantry framing gives him the easiest possible reentry. If he is not in a position, his silence on this message will be informative in a way the previous three silences could be argued away as workload-related, illness, family matters, the accumulating ordinary reasons a working political contact might fall behind on correspondence. The fourth message removes the ordinary reasons. The fourth message sits in his inbox and either gets answered, or does not, and the not-answered is an answer.

I close the message window. I move to the rest of my morning.

---

The morning is full of the work I have been doing for two months — containment, redirection, calibration. The council liaison meeting from Saturday produced three follow-up items I have been processing all week. The Halvard incident, which the pack has now collectively decided to call *the Tregaard spar* in the social register — a deliberate reframing I have been encouraging through a combination of quiet conversations and a refusal to dignify any other framing — has settled into pack memory as a notable but not catastrophic training-yard event. Halvard himself has done his part. He has continued his Thursday-bonfire-equivalent attendance at the small gatherings, has been seen at the community center, has not allowed his bruised pride to translate into a campaign of resentment. I respect him for it. I also note, with the small specific filing that has become my default register lately, that his discipline in absorbing the loss is a sign of a pack member whose loyalties to the Ashworth family run deep enough that he is willing to eat the public humiliation rather than weaponize it.

I file Halvard's discipline.

I move to the next item.

The next item is a request from a council subcommittee for documentation on Ironvale's integration of the Ashborne survivor cohort. The request arrived two weeks ago, framed as routine. It is not routine. Routine requests come with deadlines and standard format expectations. This request came with neither — an open-ended ask for *whatever Ironvale considers relevant for the council's review.* That phrasing is a fishing line. The subcommittee wants to see what we volunteer, in what order, with what emphasis. Whatever we send becomes the basis for whatever they ask next.

I have been working on the response with Rhett since the request landed.

The strategy is to provide more than they expected and less than they wanted. We are sending a thorough, technical, immaculately bureaucratic packet — the housing arrangements, the medical assessments, the integration timeline, the training-cohort placement, the food-resource calculations. Nothing about the survivors' family histories. Nothing about pre-Ashborne genealogy. Nothing that could be used to ask follow-up questions about specific bloodlines or lineage trees. The packet will look like a model integration report. It will give the subcommittee no purchase to ask the questions they actually want to ask.

This is the Rhett-and-Maddox specialty. We have been doing it for years. We are good at it.

The packet is due Monday. I review it again this morning. I make three small adjustments. I send the revised version to Rhett for final sign-off.

---

At eleven-thirty, I get up from my desk and walk to the administrative cafeteria, because I have a standing Friday lunch with Marguerite and her circle and because Marguerite is one of the best political readings I have access to.

Marguerite is fifty-two. She is the wife of a council advisory member — the same advisory member who routes documents from Dorne's level up to the actual council members. She has been in council circles for thirty years. She knows everyone who matters and several people who only think they matter. She has a dry sense of humor and a near-perfect read on which way the council winds are blowing on any given week, and she has been mentoring me, in an informal capacity, since I was sixteen.

I sit with her at the corner table. Two of her circle are with us — Yves, who I sat with at the bonfire on Saturday, and a council wife named Hester whose husband sits on the membership subcommittee. We have soup and bread and the small pleasantries the Friday lunch always opens with. I let the pleasantries run for ten minutes. I do not introduce my actual subject until Hester has left to take a call from her daughter and Marguerite and Yves are comfortable in their second cups of coffee.

Then I say, casually:

"Marguerite. Have you heard anything about Dorne lately."

Her face does the tiny thing her face does when I have asked her a question whose framing matters to her. The almost-imperceptible shift of attention from social to political. She does not change her posture. She picks up her coffee and she sips.

"Dorne," she says. "Council aide Dorne."

"Yes."

"What about him."

"He has gone quiet on me. Three weeks. I have sent four messages, the most recent this morning. Routine traffic. Things he has historically responded to within a day. The silence is not consistent with the relationship."

Marguerite considers. Yves is watching the conversation now with the polished neutrality of a council wife who has decided to listen but is not going to participate. Marguerite glances at Yves, briefly, and Yves gives her the small specific nod that means *yes, you can speak in front of me, I am safe in this conversation.*

Marguerite sets her coffee down.

"Dorne has been reassigned."

"To what."

"To the agricultural council subcommittee."

I absorb this. The agricultural subcommittee is — I will not say it is a backwater, but the agricultural subcommittee is a backwater. It is where council aides go when their handlers want them visible-but-irrelevant, when there is a reason to keep someone employed but no reason to keep them in the information flow. Dorne, three weeks ago, was a working contact for inter-pack liaison work. Today, he is reading hay-yield reports.

"When."

"Sometime in the last month. The reassignment was not announced. I learned about it because his replacement on his old portfolio reached out to my husband, asking for context on the Ironvale-side relationship, and the word *replacement* was the first I had heard of any change."

"His replacement is —"

"A wolf named Briar. New to the council aide pool. I do not know him. My husband does not know him. He is not a known quantity, which is itself the information."

I file this. *A wolf named Briar.* I do not know him either. I have not received any outreach from him. The portfolio that was Dorne's is — apparently — Briar's now. And nobody has informed me of the transition.

"Why."

Marguerite looks at me. Her face is the face she gets when she is considering whether to share something she has not decided yet whether she should share. The calculation is visible. She is weighing how much I have earned, weighing how much the question cost me to ask, weighing whether the answer she is considering is hers to give.

"I do not know why," she says. "But I can tell you this. Reassignments at that level do not happen without instruction. Someone above the aide pool — someone in the council itself, not the advisory layer — decided Dorne should not continue on his portfolio. The decision was not posted. It was executed quietly, by paperwork that did not cross my husband's desk, which is unusual because most paperwork at that level does cross my husband's desk."

"Someone is managing the information."

"Someone is managing the information."

"For my portfolio specifically, or broadly."

Marguerite picks up her coffee again. She does not answer immediately. Yves has not moved, has not contributed, and is studying her own cup with the particular still attention I have learned to recognize as a council wife receiving information she may need later.

"I cannot answer that specifically," Marguerite says. "I can tell you that I am aware of one other portfolio that has had unusual handling in the last month. I am not going to tell you which. I will tell you that the pattern, if you can call two data points a pattern, is consistent with a council member who is filtering inquiries through a controlled channel. Which means the question to ask is not *what happened to Dorne.* The question to ask is *whose channel is Briar.*"

She stops there. She has given me a piece. She is not going to give me more this lunch.

I do not press.

"Thank you, Marguerite."

"You are welcome, Maddox. Eat your bread."

I eat my bread.

---

I walk back to my office at twelve-forty-five with a piece of information I did not have at nine-fifteen.

Dorne has been reassigned. The reassignment came from above the aide pool. A new contact, Briar, has been placed on the portfolio without my being notified — which is itself a procedural anomaly, because the standard council courtesy is to introduce a new aide to their counterparts within the first week of the transition. Briar has not introduced himself. Three weeks of silence, followed by no replacement reaching out. Either Briar is incompetent, which is unlikely at the council level, or Briar has been instructed not to reach out yet, which is the more probable reading.

Whose channel is Briar.

I sit at my desk. I open the council membership roster I keep in my private files. I read the names. There are twenty-three council members across the regional Continental Pack Council. I have working relationships with twelve of them through their advisory layers. I have direct relationships with three. The other eight are wolves I know by reputation but have not had cause to contact directly.

The wolf who reassigned Dorne is one of the twenty-three.

The wolf who reassigned Dorne is, almost certainly, also the wolf who has been asking questions about Ashborne survivors' bloodlines through the indirect channels I have been tracking for two months.

I have been tracking the questions. The questions originate somewhere in the council. The questions filter down through aide-level channels to the inter-pack records offices, where they get logged as routine genealogical inquiries — because that is the form they take, on paper. *We are reviewing the Ashborne survivor cohort's family histories as part of a routine integration audit.* Routine integration audits do not require pre-attack genealogy. Routine integration audits do not specifically request the family lines of survivors over five generations back. The Ashborne queries have been doing exactly that.

Five generations back.

Pre-attack genealogy.

I have been filing this oddity for two months and I have not been able to identify the originating council member. The aide-level paperwork has been clean. The questions have been routed through procedural channels that do not name their sponsor. I have known the questions are happening. I have not known whose questions they are.

Dorne was the one wolf I could have asked.

Dorne has been reassigned.

The reassignment is not a coincidence.

---

I think for an hour at my desk.

The thinking produces a working hypothesis, which I do not write down — I write almost nothing down lately — but which I can articulate in my head at the level of a sentence I will be able to refine over the next several weeks.

*Someone in the council is asking specific genealogical questions about the Ashborne cohort's family lines, and that someone is quietly preventing me from identifying who they are.*

The next question is — why.

There are several possible answers. Most of them are political. The council periodically reviews integration arrangements, and a council member with a personal political stake in either supporting or opposing Ironvale's absorption of the Ashborne survivors might be looking for ammunition in either direction. The genealogical angle would be unusual but not unprecedented — sometimes integration challenges turn on whether the absorbed pack had blood relationships with hostile neighboring packs, whether long-buried family conflicts could destabilize the absorbing pack, whether bloodline-based political alliances might be activated against Ironvale by the survivor cohort.

These are normal political concerns.

The Ashborne queries do not feel like normal political concerns.

Normal political concerns work in a frame of three to five generations and are usually paired with concerns about the destination pack's stability, not the source pack's lineage. The Ashborne queries are looking back farther than political concerns require, and they are not paired with corresponding concerns about Ironvale. They are interested in what the Ashborne cohort *carried,* not what they bring to Ironvale's political balance.

What does *what they carried* mean.

I do not know.

The question sits on my desk in the form of paperwork and absences. It does not resolve.