Dael's response to the letter about the diagnostic gap came in seven days.
Seven days was faster than eleven. Junho noted the difference without drawing conclusions from it. Faster could mean he took the technical concern seriously. It could mean he wanted to close the window before it widened. The timing was ambiguous.
The letter itself was three paragraphs.
The first thanked Lord Ashmore for identifying the technical issue, expressed that this was precisely the kind of expert input the framework needed, and noted that Lord Dael had immediately shared the concern with his team.
The second said that his team had reviewed the diagnostic methodology section and agreed that it needed strengthening. However, given the timeline constraints of the consultation period, a comprehensive revision would require additional time — potentially two to three months beyond the current consultation window. Rather than delay the framework's adoption, Lord Dael proposed to address the diagnostic section in a formal addendum, to be developed in collaboration with Lord Ashmore and submitted within ninety days of framework adoption.
An addendum. After adoption.
The framework gets adopted without the critical technical step. Then, ninety days later, an addendum addresses the gap. Which means: the framework goes out to territories, they begin implementation, some of them dig channels in clay without a gravel subbase, the drainage fails, the addendum arrives explaining what they should have checked first.
The addendum is the fix applied after the harm has occurred.
The third paragraph expressed Lord Dael's continued appreciation for Lord Ashmore's collaboration and enthusiasm for the addendum process.
Junho read the letter twice. Then he set it flat on the desk and looked at it.
He didn't take the exit.
The exit was: revise the framework before adoption so it's complete. He declined the exit and offered a different path: adopt the framework as-is, fix it later.
He may have reasons for this that have nothing to do with bad faith. Two to three months of revision delay might genuinely cost something important in the Office's cycle. The addendum process might be standard practice for framework refinements.
Or he calculated that a framework adopted without the diagnostic step is a framework that demonstrates results in territories with the right soil profile, and demonstrates failure in territories without it, and the failures are attributed to implementation error rather than framework incompleteness, and either way the framework exists and is under his authority.
I can't know which.
I know what I have to do.
He went to find Sera.
She read the letter in thirty seconds.
'The consultation comment,' she said.
'Yes.'
'We file it.'
'Yes,' he said. 'But we need to get it right. Lenna needs to review the technical language. I need Mara to verify the soil profile description is accurate for conditions outside Ashmore — she's seen the eastern fields at Fenhold from Ryse's descriptions, she might have a sense of the profile.'
'You're going to ask Mara to contribute to the consultation comment?' Sera said.
'I'm going to ask her whether the diagnostic process I've described applies correctly to a variety of soil conditions or whether I've made it too specific to Ashmore,' Junho said. 'It's a technical question. She's the person who knows the answer.'
Sera was quiet for a moment.
'She's a farmer,' she said. 'The comment will be filed by Lord Ashmore of Ashmore Barony. Citing a farmer as a technical source—'
'I'm going to cite her name and her role,' Junho said. 'Mara Dunwick, agricultural manager of Ashmore east field, thirty years experience with the drainage conditions described. If the Agricultural Development Office has a problem with a woman who has farmed the same clay-over-gravel soil for thirty years serving as a technical reference, they should say so and explain why her three decades of direct observation count for less than my engineering background.'
Sera looked at him.
'That's going to make some people uncomfortable,' she said.
'Good,' Junho said. 'People who are uncomfortable with accurate attribution should be uncomfortable. That's information.'
* * *
Writing the consultation comment took two weeks.
Not because the technical content was unclear — the diagnostic step was specific and could be described precisely — but because the comment had to accomplish several things simultaneously, and making it do all of them without any one element undermining the others required more care than most documents he had written.
It had to be technically accurate. Any error in the technical description would give the Office grounds to dismiss the comment as the work of someone who didn't fully understand the subject. Lenna reviewed three drafts and made corrections to two of them — not errors of principle but errors of precision, the kind that mattered in official technical documents.
It had to be constructive rather than adversarial. A comment written as a complaint about credit was a political document. A comment written as a technical contribution was a professional one. The framing had to be: here is a gap in the framework's diagnostic methodology that will cause implementation failures in territories without the applicable soil conditions. Not: here is what Dael got wrong. Not: here is what belongs to Ashmore.
It had to establish the source of the knowledge without making the establishment of the source the primary purpose. He achieved this by including a detailed technical footnote: *The soil profile assessment methodology described in this comment was developed and validated at Ashmore Barony, Northern March, over eighteen months of implementation by Mara Dunwick (agricultural manager, thirty years experience in clay-loam soil management) and the undersigned. The methodology has been independently verified by Crown Surveyor Vane (Assessment reference: [record number]) and by Lenna Fen, Crown Road Office, Northern March Division.*
Three independent sources, one of them the Crown's own surveyor. The methodology is not my claim. It's a documented fact in multiple official records.
Dael can't remove that from the comment. The comment goes into the official record as submitted.
It had to be written in the register of someone who wanted the framework to succeed. Because he did want it to succeed. That part was not strategy — it was the truth. If the framework adopted the diagnostic step correctly, territories across the March would have better drainage and better harvests. He wanted that.
The genuine desire for the framework's success made the comment more credible than any political calculation could have.
When the draft was final, he took it to Mara.
She was at the east field, checking the stubborn rye's progress. She looked up when he approached with the parchment.
'Read this,' he said. 'The section describing the soil profile diagnostic. Tell me if it's accurate for conditions you've seen or heard about outside this field.'
She took the parchment. She read slowly, which was how she read technical material — not labored but thorough. She reached the relevant section and her pace slowed further.
'The creek bank exposure method,' she said. 'I've seen this work on two other fields I know. The Aldric family's south field — they had the same clay problem, and when Carra walked the creek bank near it she found the same transition you found here. They haven't acted on it yet.'
The Aldric family's south field. Carra found the same transition. Nobody acted on it.
'And the other?'
'A field in Crossfen that my cousin farms. She described it to me years ago — the same mud hole problem, and the creek bank near it exposed the same layers.' She paused. 'She said the lord's steward dismissed the observation because he said the field had always been that way and there was nothing to be done.'
Dismissed. Because 'there's nothing to be done' was the frame, and the frame didn't include 'check the creek bank for a gravel subbase.'
How many fields in how many territories have that same clay-over-gravel profile, sitting above drainage potential that nobody has accessed because nobody looked at the creek bank.
'So the methodology applies to at least two known cases outside Ashmore,' Junho said.
'Yes.' She handed back the parchment. 'The description is accurate. The step about pressing the soil with your thumb to feel the clay transition — I'd add one thing. The gravel layer sounds different when you strike the channel bottom with the spade. The clay makes a dull sound. The gravel makes a sharper click.' She tapped the parchment. 'That's how I always knew when we'd reached the right depth before we even looked at what was coming up.'
The sound of the spade changing.
Dull clay, sharp gravel. Auditory confirmation alongside visual confirmation. She's described a field test that I don't have in the document.
'Can I include that?' Junho said.
'You just wrote it down,' she said. She had noticed that he was writing while she spoke. She had not stopped speaking because of it. That was Mara — she said what was accurate and let it be used.
He added the note to the comment's diagnostic section. *Field indicator: strike the channel bottom with a spade. Clay produces a dull impact sound; the gravel subbase produces a sharper, resonant strike. Experienced practitioners use both visual assessment of material and auditory confirmation to verify subbase depth.*
*Experience of M. Dunwick, Ashmore Barony agricultural manager.*
He read it back to her.
She nodded. 'That's accurate.'
* * *
The comment was filed on day four hundred and eighty-nine.
Filed through the standard consultation process — a formal document submission to the Agricultural Development Office's review secretary, with copies to the March Commander's office and to Lord Colwick as the senior Northern March lord.
The cover letter was one paragraph: *Lord Ashmore of Ashmore Barony submits the attached technical comment during the formal consultation period for the proposed Territorial Agricultural Development Framework. The comment addresses a material gap in the framework's diagnostic methodology and includes a proposed addition that would allow accurate assessment of the framework's applicability in specific territorial soil conditions. Lord Ashmore supports the framework's adoption and submits this comment in the interest of its technical completeness.*
Sera had written the cover letter.
He had changed one word.
She had accepted it.
The comment itself was nine pages. Three pages of technical description, clearly structured. Four pages of field application notes, including Mara's observations and the two independent cases from her knowledge. One page of references, including Vane's assessment record and Lenna's professional endorsement. One page of proposed framework revision language — the exact text that could be inserted into the existing document to correct the gap.
He can adopt the proposed language verbatim or he can write his own version. Either way, the diagnostic step is in the record and its source is documented.
If he adopts it verbatim: the record shows the correction came from Ashmore.
If he rewrites it: the record shows the original description came from Ashmore, and the comparison between the two versions is visible to anyone who looks.
If he ignores it: the record shows a material technical gap was identified and not addressed, and any implementation failures in territories without the applicable soil conditions are traceable to a documented and unaddressed comment.
There are no paths forward from here that don't acknowledge Ashmore's contribution to the methodology.
That's not a victory. Dael still controls the framework. He still has the lead authorship and the Crown connection and the Agricultural Development Office relationship. But the documentation is now complete enough that history will be accurate about what happened.
History being accurate is not the same as getting what I asked for. But it's not nothing.
* * *
The consultation period ran six weeks. During those six weeks, Ashmore's operations continued.
The school building frame went up on day five hundred. Pol and Bett worked with Calder, the three of them in the professional rhythm of a team that had built together before and trusted each other's pace. The frame was up in three days, the walls going on in the week after, the shale tile roof starting in the second week.
Junho stayed out of the construction.
This was not passivity. It was the correct behavior — he had designed the building with Sera, the construction was Pol and Bett and Calder's domain, and inserting himself would have added delay without adding value. He checked dimensions at end of day, found nothing wrong, and went back to his other work.
His other work included three consultation comments from other territories.
Not about the framework — about drainage. Three lords had read Vane's assessment record or heard about Ashmore's approach through some path in the March network, and had written asking for technical guidance. A field in Brackton. A section of Caldewick near Lady Norn's western boundary. A territory in the Western March that he had never heard of, apparently referred by someone he also didn't know.
He answered all three. Specific, written assessments based on the descriptions they provided. Not site visits — he couldn't do site visits. But the diagnostic framework was now documented well enough that he could help people apply it from a description.
He told all three of them: look at the creek bank nearest the problem field. If you see a clay-over-gravel transition within seventy centimeters depth, the approach applies. If you don't see that transition, write back and describe what you see, and I'll tell you what the alternative options are.
Two of them wrote back with creek bank descriptions that confirmed the transition. He gave them the full diagnostic and installation guidance, with Mara's spade-sound note included.
The third wrote back saying they couldn't find any exposed creek bank section near the problem field. He told them to look for a road cut or a hillside exposure — anywhere the soil layers were naturally visible. He told them to look for the dark-to-light transition at depth, because the gravel was pale and the clay was grey-brown, and the transition was often visible even in poor conditions.
He did not hear back from the third territory for three weeks. Then a letter arrived saying they had found the transition in a road cut half a kilometer from the field, and they were beginning the channel work.
He added the three territories to his records. Not the operational log — a separate document he had started, which he called the drainage correspondence record. Cases with descriptions, diagnostic findings, recommended approaches, outcomes where he knew them.
This is becoming its own documentation. Case studies. The approach applied in different contexts with different results.
If the framework document gets adopted and the diagnostic step is included, this correspondence record is the evidence base for it. If the diagnostic step is excluded, this record is the independent documentation that it exists and works.
Either way, the record grows.
* * *
Ryse came back on day five hundred and seven, her fourth visit.
She was different from the first visit. Not less professional — more settled. The provisional quality of the first Thursday visit had resolved into something more confident. She knew the mill, she knew Wyll, she knew the operation. She arrived and went directly to the work without the orientation interval she had needed before.
She had also implemented the secondary drive mechanism at Fenhold's mill.
She told him about it at lunch — not a formal report, just describing what had happened. The bearing support she had added, the way she had checked it against the calculation he had corrected in her notebook. The first run.
'The grain mill worked,' she said. 'First session, sixty kilograms. The stone gap needed two adjustments to get the fineness right, but the mechanism ran without problems.'
She implemented it. With the corrected bearing design. And it worked.
'How did the tenants respond?' Junho said.
'Coser organized the first session,' she said. She said it with a small, direct satisfaction. 'I asked him about the cart trip, as you suggested. He told me about it for an hour. The trip was — it was everything you said it might be. I proposed the mill sessions, and I proposed keeping the annual collective trip as a social occasion rather than a logistics run. He could see both were better than neither.' She paused. 'He organized the first session himself. I didn't have to.'
She asked Coser about the trip. She learned what it was. She preserved what mattered. The mill sessions are running and the social institution is intact.
That's the transfer of method, not just solution. She understood the principle well enough to apply it in a context I hadn't specifically described.
'The eastern fields,' he said. 'The drainage.'
'We found the gravel transition at the creek bank,' she said. 'Lord Dael is — he approved the project. Ryse set the schedule.'
She had said 'Ryse' and then paused, realizing she had referred to herself in the third person.
She looked at him with a slight expression. Not embarrassment — more like an acknowledgment of a habit she'd developed in written reporting.
'You scheduled it,' Junho said.
'Yes.' She looked at her notebook. 'The channels start next week. I have the depth specifications from the diagnostic notes you wrote. I have Mara's spade-sound observation in my own notes — I wrote it down when she described it. I think I'll recognize the transition when I hear it.'
She has Mara's spade-sound note in her own notebook. She wrote it herself during a session here.
The knowledge is in Ryse's notebooks. Not in a framework document. In the handwritten notes of the person who will implement it.
That's the real transfer. Not the official documentation. The person who learned it here taking it somewhere and using it.
'You will,' Junho said.
She closed her notebook.
'The framework comment,' she said. 'I read it.'
He was still. He had not sent her a copy. The document was a public filing.
'It's a public document,' she said. 'During the consultation period, the comments are accessible.'
'Yes,' he said.
'The diagnostic section is correct,' she said. 'I know because I've done the assessment, and it describes what I found.' She looked at her notebook. 'And Mara Dunwick's name is in the footnote.'
'Yes.'
She was quiet for a moment.
'Lord Dael doesn't know I read it,' she said.
'You don't have to tell him,' Junho said.
'No,' she said. 'But I might anyway.'
She might tell him. Voluntarily. Because she thinks he should know that the technical content of the comment is accurate, from someone who has applied it.
That's not loyalty to me. That's her professional integrity. She would do it for the same reason she corrects herself in front of a twenty-one-year-old teacher — because accuracy matters more than position.
Dael has a very good estate manager.
He doesn't deserve her.
She'd disagree with that assessment. She's not someone who measures what people deserve. She measures what work is needed and does it.
'Thank you for coming,' Junho said. 'For all four Thursdays.'
'I'll come back,' she said. 'There are still things I haven't learned.'
'There are always things you haven't learned,' he said.
'Yes,' she said. 'That's why it's worth coming back.'
She left.
* * *
The Agricultural Development Office responded to the consultation comment on day five hundred and nineteen.
Not a rejection. Not an acceptance. An inquiry. The Office's technical review committee had reviewed the comment and had questions. Specifically: three technical questions about the soil profile diagnostic, and one administrative question about the nature of the collaborative relationship between Lord Ashmore and Lord Dael.
Technical questions from the review committee. They took the technical content seriously enough to ask questions.
The administrative question about the 'collaborative relationship' is the one I need to read carefully.
He read the administrative question.
It said: *The consultation comment submitted by Lord Ashmore references technical methodology described as originating at Ashmore Barony. The framework proposal references Lord Ashmore's territory as a demonstration site. The committee would find it useful to understand the nature of the relationship between the two submissions — specifically, whether the comment represents supplementary input to the framework proposal or a competing claim regarding the methodology's ownership.*
They're asking whether this is collaboration or dispute.
The framing of 'competing claim regarding the methodology's ownership' is — that's the framing I've been trying to avoid. The framing that makes this look like a credit dispute.
But they're asking directly. And the answer has to be direct.
He wrote the response to the administrative question himself. Not Sera — himself, because the content of it was specific to his own relationship with the work and no one else could write it accurately.
He wrote: *Lord Ashmore's consultation comment does not constitute a competing claim regarding methodology ownership. Methodologies cannot be owned; they can be practiced, documented, and attributed. The comment is a contribution to the framework's technical completeness — specifically, the inclusion of a diagnostic step that the comment demonstrates is necessary for correct implementation. The methodology originated in practice at Ashmore Barony over eighteen months; this is documented in the Crown survey record referenced in the comment. The relationship between the comment and the framework proposal is collaborative, in the sense that both aim to propagate effective territorial development practices across the March. The question of attribution is secondary to the question of technical accuracy. However, accurate attribution is not merely a credit matter — it allows practitioners who have questions about implementation to find the source of the methodology, which is Ashmore Barony and the individuals named in the comment's footnote.*
He read it back.
That's accurate. Every word of it.
Attribution allows practitioners to find the source. That's the practical argument for accurate attribution that has nothing to do with credit or ego. You attribute the methodology to Ashmore because if a territory has a question about implementation, they need to know where to ask.
The people who know the answers are at Ashmore. Not in a framework document. Not at the Agricultural Development Office. Here.
He showed it to Sera.
She read it. She set it down.
'No corrections,' she said.
'None?'
'It says what it needs to say. I don't have a word.'
That might be the first time she has found nothing to change.
Or it means the document is doing exactly what it should and she can see it.
* * *
Three days after filing the administrative response, something happened that Junho had not anticipated.
A letter arrived from Crane.
Not the administrative secretary. From Crane directly, in his own hand, on his own paper without the Galden Group seal.
It was four sentences.
*Lord Ashmore. I have been following the Agricultural Development Office consultation period as a registered trade observer, which gives me access to public filings. Your consultation comment and administrative response are notable for their technical precision and for the quality of the attribution argument in the response. For your information: the Office's technical review committee includes one member of the Crown Agricultural Advisory Board, which reports to the Crown Steward. The Crown Steward is not a friend of Lord Dael's family.*
The Crown Steward is not a friend of Dael's family.
Crane is telling me there's a political dimension I haven't seen.
The Agricultural Development Office has a link to the Crown Advisory Board. The Advisory Board reports to the Crown Steward. Dael's family connection is presumably to someone else in the Crown structure — not the Steward, someone adjacent or parallel.
If the Steward and Dael's connection are in different factions — or in competition — then a framework proposed through Dael's connection that attracts scrutiny from the Steward's committee is in a complicated political position.
Crane is telling me this without explaining it. Because explaining it would require him to describe Crown court politics in a letter, which he would not do. He's giving me the signal and leaving me to interpret it.
The interpretation is: my consultation comment, by raising a technical question that the Steward's committee is now reviewing, has inserted a complication into a political arrangement between factions I didn't know about.
That might help me. It might complicate things in ways that harm the framework's adoption. It might produce an outcome nobody intended.
Crane is a man who calculates. He sent four sentences. He did not send them idly.
He showed the letter to Sera.
She read it three times.
'He's telling you the Crown politics are more complicated than the March politics,' she said.
'Yes.'
'And that your comment has landed in the middle of something you didn't put it in the middle of.'
'Yes.'
'What do we do with this?'
What do we do with information about a political situation we can't fully see, that we didn't intend to enter, that might help or harm depending on factors we can't evaluate?
The answer is: nothing. We do nothing with it. We continue doing what we were doing, which is filing accurate technical contributions to a consultation process.
The Court politics are not my domain. The soil profile diagnostic is my domain. If the Court politics move in our direction, the comment is in the record. If they move against us, the comment is still in the record.
I don't have the knowledge to play the court game. I do have the knowledge to make the technical argument.
'We continue the technical work,' Junho said. 'The comment is filed. The drainage correspondence records are growing. The framework comment addresses the gap accurately. We can't influence the Court politics and we shouldn't try.'
'Reply to Crane?' Sera said.
'Thank him,' Junho said. 'Briefly. One paragraph. No analysis, no requests. Thank him for the information.'
'I'll write it.'
'One paragraph.'
'Yes,' she said.
* * *
On day five hundred and thirty-one, a letter arrived from the Agricultural Development Office.
It was addressed to Lord Ashmore and Lord Dael jointly.
The Office's technical review committee had completed its review of the framework proposal and the consultation comments. The committee had found that the diagnostic methodology gap identified in Lord Ashmore's comment was material — that is, the framework as filed would be inapplicable in a significant proportion of territories without the diagnostic step, and implementation without it risked adverse outcomes.
Accordingly, the committee recommended that the framework's adoption be deferred pending a revision that incorporated the diagnostic methodology. The committee further recommended that the revision be developed collaboratively between the framework's lead author and Lord Ashmore of Ashmore Barony, and submitted for a focused review within ninety days.
The committee had also reviewed the administrative response submitted by Lord Ashmore regarding the attribution question and noted that the practical argument — accurate attribution enables practitioners to find the source of the methodology — was well-founded. The committee recommended that the framework revision include a clear statement of the methodology's originating territory and primary practitioners.
Deferred.
The framework is deferred pending revision.
The revision must be collaborative. The attribution must include originating territory and primary practitioners.
That's — that's everything I asked for at the table. Not as I asked for it. Through the consultation process rather than through direct negotiation. But the outcome is the same.
The committee found the technical gap material. Not me asking for credit. The committee, independently, reviewing the technical content.
Lenna knew. She told me about the diagnostic gap and she told me to file the consultation comment. She's been in that building for fifteen years and she knew exactly what would happen when a material technical gap was identified in an official review process.
He read the letter a second time, more slowly.
The revision must be developed collaboratively. He cannot revise it without me, because the committee is requiring collaboration. He cannot exclude the attribution, because the committee is recommending it.
He could still maneuver around these recommendations. The committee recommends; it doesn't mandate. If Dael has sufficient influence at the Office, he might revise without full collaboration and submit something that technically satisfies the committee's requirements while maintaining the structure he filed.
But doing that now would be visible. The committee's recommendations are in the record. Any revision that doesn't honor them will be compared to them.
He set the letter down.
He was quiet for a long time.
Not processing the outcome — absorbing it. There was a difference.
He had spent forty days fighting a political battle with inadequate tools in unfamiliar terrain. He had lost the initial move — the first filing. He had made the correct response — the technical comment. He had been helped by people he hadn't asked for help from: Lenna, who gave him the technical angle; Crane, who gave him the court context; Ryse, who independently validated the diagnostic; Colwick, who warned him early.
I didn't win this. It was won by the accumulated weight of accurate work documented by people who know the substance.
That's how it should work. That's how I said it would work, in my previous life, when clients tried to run over subcontractors with bad-faith contract interpretations and I told the subcontractors: document everything, stay accurate, let the record do the work.
I gave myself the advice I give other people.
It worked.
He went to find Sera.
She was in the hall, reading the equivalent letter — the Office had sent both of them copies, as it was jointly addressed.
She looked up when he came in.
'Collaborative revision,' she said.
'Yes.'
'Primary practitioners named.'
'Yes.'
She was quiet for a moment.
'Mara's name will be in the framework,' she said.
'And Calder's,' he said.
She set the letter down. She looked at the wall — the operations documentation, now organized for external visitors as well as internal function.
'When Dael writes to propose the revision process,' she said, 'be careful about what you agree to. The committee's recommendation is in the record. But the revision itself will be drafted in negotiations between you and him. He's still better at those negotiations than you are.'
Still better at court-style negotiations than I am. Yes. That's accurate.
I know my floor. I know what I won't accept. I have the record.
And I'll bring Sera to the table.
'I know,' Junho said. 'But the terms I'll accept now are different from the terms I stated at the table in spring. The committee's recommendations are the new baseline. He has to work from there.'
'Yes,' Sera said. 'He does.'
She picked up her pen. She was already drafting the acknowledgment of receipt.
* * *
That evening, Junho took the letter to Mara.
She was in the east field at sunset, the light coming low and gold across the rye that was now well-established in the northwest section, the central section planted for seed, the southwest section's stubborn rye still shorter than the rest but present.
He gave her the letter.
She read it. She was a slow reader — she had learned from Wyll's evening sessions, and she read like someone who had come to literacy late and took nothing for granted. But she read it fully.
She came to the line: *originating territory and primary practitioners.*
She read that line twice.
'Primary practitioners,' she said.
'You and Calder,' Junho said. 'By name. In the framework document.'
She was quiet.
The field was quiet around her, the rye moving slightly in the evening air, the drainage channels invisible below the surface, doing their work.
'My father,' she said. He had heard this from her before, in different forms. The father who had correctly diagnosed the field's problem and been ignored. The father who had waited for a lord who would fix it and died without seeing it.
'If the framework works,' Junho said carefully, 'if the approach spreads across the March and other fields are drained and other families can plant what their soil wants to grow — your father's observation is part of that. He was right. The record will say that the approach was developed and validated here, at Ashmore, by the people who farmed this land.'
She was quiet for a long time.
'He didn't know about the gravel subbase,' she said.
'No,' Junho said. 'But he knew the field was drainable. He knew the problem was solvable. The specific solution required more information. You provided part of that information when you described the field to me on the first morning. The rest—'
'The rest we dug up,' she said.
'Yes.'
She folded the letter and handed it back to him.
'Good,' she said. She said it the way Junho used it — not a small word, a word that held more than its surface.
She went back to the field.
He stood at the edge for a moment.
Ping—!
―――――――――――――――――――――――――――
[ TERRITORY STATUS — DAY 531 ]
Agricultural Development Office outcome:
Framework: DEFERRED pending collaborative revision
Revision requirement: Joint authorship with Ashmore
Attribution requirement: Originating territory + primary practitioners named
What this means:
Mara Dunwick and Calder Voss named in the framework.
Ashmore cited as originating territory of the methodology.
Revision cannot proceed without Ashmore's participation.
What this does not mean:
Dael does not become less powerful. He still has the Crown connection.
He still initiates the revision. He still leads the framework process.
The revision negotiations will require continued vigilance.
The political conflict is not over.
The first phase has concluded with an acceptable outcome.
The revision phase begins.
Active projects (unchanged):
School building: Frame complete, walls 60%, completion Day 555 est.
East field: Planting complete, early season growth established
Mill: Operating normally, Year 2 production pace
Drainage correspondence: 3 active external cases, growing record
Dael's next move: Revision proposal letter (expected within 30 days)
Lesson noted: Stay accurate. Let the record do the work.
It did.
Territory Status: ESTABLISHED
Days since arrival: 531
―――――――――――――――――――――――――――
He closed the panel.
The rye moved in the field. The drainage channels worked in the soil below. The mill ran in the distance.
First phase concluded.
The revision phase begins.
He's better at court-style negotiations than I am. That's still true.
But I have Sera. And the record. And Ryse, who is implementing the methodology at Fenhold and will know if the revision produces something inaccurate. And Lenna, who reads official documents with the same eye she uses for structural specifications. And Colwick, who sent Harwell to warn me early.
And Mara, whose name is now in the record.
That's not nothing. That's the work of eighteen months, crystallized into a position that cannot be erased by a better negotiator.
He walked back to the hall.
There was a letter to write.
Not to Dael yet — to Harwell, with instructions to let Colwick know the outcome and to continue monitoring the Agricultural Development Office correspondence.
Then to Crane, one paragraph, as agreed.
Then to Lenna — not a thank you, because she wouldn't want a thank you. A question: *What is the standard process for co-developing a framework revision with the Agricultural Development Office? What should I know before the first revision meeting?*
Always: what should I know before I walk into the room.
He sat down. He picked up the charcoal stick.
Skrrk—
He kept writing.
—
[ End of Chapter 28 ]
~ To be continued ~
Wanna read ahead? The story is already completed with 63 chapters on Patreon. Go and finish the story before anyone else.
Join Patreon: patreon.com/MASKO73