Ryse came back on Thursday, as promised.
She arrived in the morning with her notebook and without Lord Dael, which was the expected arrangement. She was polite, focused, and took up exactly as much space as she needed. Wyll showed her the grain mill operation — the gate management, the hopper rate, the tramming adjustment — with the patient explanatory clarity of someone who had been teaching for a year and had learned to read how much a person already knew before deciding what to say.
She knew more than he expected. Wyll recalibrated partway through and stopped explaining fundamentals and started discussing refinements, which was the right call.
Junho observed from the doorway for ten minutes, then left them to it.
When Ryse came to find him at midday, her notebook was full of new entries. She had specific questions — about the grain quality inspection process, about the milling fee structure, about how the tenant families had been organized into the weekly session schedule. Not the mechanism. The operation.
She's moved past the technical questions to the operational ones. She understands the mechanism. Now she's trying to understand how you make it work as a community service rather than just a piece of equipment.
'The weekly session,' she said. 'How did you establish the rotation? Eighteen families, one mill, one day per week.'
'Mara organized it,' Junho said. 'She knew which families had grain ready when, which ones had storage constraints, which ones needed priority for the early harvest. I gave her the operational parameters — how many sacks per session, how long each family's processing takes — and she built the schedule.'
'You didn't build the schedule,' Ryse said.
'I could have,' Junho said. 'It would have been less accurate.'
She wrote it down. Then: 'At Fenhold, when we establish grain milling — I have a good sense of the mechanism now, I think I can adapt it. The operational structure will be harder. The tenants at Fenhold have been managing around the broken mill for so long that they've built alternative arrangements. Reorganizing those arrangements will create friction.'
Reorganizing established workarounds. She's thought several steps ahead to the social problem that follows the technical solution.
'The alternative arrangements,' Junho said. 'Do you know what they are?'
'Some of them. The tenant head — a man named Coser — has organized a collective cart to Veldmark twice yearly. It takes two days and half the families contribute to the cart cost. It's worked for twenty years.'
'If you install a mill, you're eliminating Coser's organizational role,' Junho said. 'And you're eliminating the semi-annual social event that the cart trip has become. Both of those matter.'
Ryse looked at him. 'You're saying keep the collective cart trip.'
'I'm saying understand what the cart trip is before you replace it. If it's purely logistical, replace it. If it's also the occasion when three families who've had a difficult year spend two days talking and arrive back on better terms with each other — that's worth knowing about.'
She was quiet for a moment. Then she wrote something longer than usual.
'Ask Coser,' she said, to herself as much as to him. 'Not about the cart. About the trip.'
'Yes,' Junho said.
She closed the notebook.
'I'll come back,' she said. 'If that's acceptable. I learn more in half a day here than in a week of reading.'
'Come back,' Junho said. 'Bring your specific problems. We'll work through them.'
She left.
Wyll appeared at Junho's shoulder.
'She's good,' he said.
'Yes,' Junho said.
'She corrected herself twice during the session. Without being prompted.' Wyll paused. 'Most people don't do that. Most people wait to be corrected.'
She corrected herself. Twice. In front of a twenty-one-year-old teacher who had been operating the grain mill for four months.
That's a specific kind of capability — the ability to catch your own errors in real time and revise publicly without embarrassment. It's rare. It's also the capability that distinguishes someone who improves quickly from someone who improves slowly.
Whatever Dael is, Ryse is an asset. The question is whose asset.
* * *
Three weeks after Dael's visit, Harwell came back.
Not with a letter. In person, which told Junho before any words were spoken that the message was the kind that needed to be delivered face to face.
He arrived mid-morning and went straight to the hall's steward office, where Junho was working on the school building design revisions — Sera and he had been iterating on the window placement after she'd observed that the morning light would create glare on the instructional wall surface at certain hours.
Harwell sat. He did not begin with preamble.
'Lord Dael visited the Agricultural Development Office in Veldmark,' he said. 'Last week.'
'He said he would,' Junho said.
'Yes.' Harwell paused. 'He went further than that.'
Further than checking the process.
'Tell me,' Junho said.
'He filed a formal proposal,' Harwell said. 'With the Agricultural Development Office. A development framework for March territories. Based on what he observed at Ashmore.'
...
He went and filed a formal proposal. Not checked the process. Filed the proposal.
Without coming back to me first.
Without the co-authorship terms we discussed. Without the review right. Without confirming what the Office's process allowed.
He said he would check the process. He filed the proposal.
Junho was quiet for a long moment.
'What does the proposal contain?' he said. His voice was even.
'I don't have the full text,' Harwell said. 'I have a summary from a contact at the Office. The proposal describes a Crown-endorsed program for territorial agricultural development. It draws extensively on the Ashmore drainage and mill approach. It references Ashmore as a demonstration site.' He paused. 'The lead author is Lord Dael of Fenhold. Contributing credit: Lord Ashmore of Ashmore Barony.'
Contributing credit.
Not co-author. Contributing credit.
The exact downgrade I said I would not accept.
'Review right?' Junho said.
'The proposal doesn't mention a review right for Ashmore.'
'Originating territory credit?'
'Ashmore is referenced as a demonstration site. Not as the originating territory of the approach.'
'Mara and Calder's names?'
'Not in the summary. I don't know if they're in the full text.'
Everything I asked for. Nothing I asked for is in the document.
He sat across the table from me. He looked at me. He agreed to investigate the process. And then he filed the proposal with none of the terms I'd named.
That's not a misunderstanding. That's a decision.
Junho looked at the school building design on the table in front of him. The window placement he and Sera had been arguing about this morning. The question of where the morning light fell.
Get the specifics before reacting. Harwell has a summary, not the full text.
The summary might be incomplete. The full text might include the terms. The contact might have missed something.
Or the summary is accurate and Dael made a decision the moment he left Ashmore's gate.
'When was the proposal filed?' he said.
'Five days after his visit here,' Harwell said.
Five days.
He rode from Ashmore to Veldmark — two days — and filed the proposal three days after arriving. Which means he drafted it on the road. Or before the visit. He had the proposal ready before he sat across from me and listened to my terms.
He was not checking the process. He was making a courtesy visit to the territory that was going to be cited in his proposal. An advance notification, dressed as a consultation.
And I sat across from him and thought I was negotiating.
I wasn't negotiating. I was being managed.
He was quiet for a long time.
Harwell waited. He was good at waiting.
'Colwick,' Junho said finally. 'Does he know?'
'He received a copy of the proposal,' Harwell said. 'From Dael's office. As a courtesy.'
'What did he say?'
'He sent me here.' A pause. 'He said: tell Ashmore before he hears it from someone else.'
Colwick sent Harwell to warn me. That's the action of an ally honoring an alliance.
Good. I'll need it.
'What does the Agricultural Development Office's review process look like?' Junho said.
'Thirty days for initial review. If they approve the framework for development, there's a six-month consultation period before formal adoption. During the consultation period, comments from affected territories are accepted.' Harwell looked at his hands. 'The consultation period is the window.'
Six months. If I file a formal objection during the consultation period, it goes on the record. It has to be addressed. It can slow the process, potentially modify it, potentially block it.
But filing a formal objection to a program that my work inspired — a program that could genuinely benefit territories across the March — makes me look like someone who cares more about credit than outcomes.
Which is exactly how Dael would frame it if I object.
And he would frame it that way accurately. Because to someone watching from outside, that is what an objection looks like.
This is the trap. He's filed a proposal that does genuine good. Objecting to the credit terms makes me look petty. Not objecting means accepting terms I explicitly rejected.
He stood.
He went to the window of the steward's office and looked out at the territory.
The mill, running. The east field in early spring. The hall's courtyard.
Ping—!
―――――――――――――――――――――――――――
[ SYSTEM NOTE — THREAT ASSESSMENT ]
Lord Dael's Agricultural Development Office proposal — analysis:
What happened:
Proposal filed without agreed terms. 5 days post-visit.
Timeline indicates proposal was drafted before the visit.
Visit was a courtesy notification, not a genuine negotiation.
Current document status:
Lead author: Lord Dael of Fenhold
Contributing credit: Lord Ashmore (downgraded from co-author)
Ashmore as: 'demonstration site' (downgraded from 'originating territory')
Mara Dunwick, Calder Voss: NOT credited
Review right: NOT included
The trap:
Formal objection = looks petty (credit over outcomes)
No objection = accepts downgraded terms
Window: 6-month consultation period for comments
Leverage points:
→ Colwick (ally, received proposal, sent warning)
→ Crane (creditor, March observer, relationships)
→ Lenna Fen (Crown Road Office, technical credibility)
→ Ryse (estate manager, implementing at Fenhold, relationship separate)
→ The documentation (meeting summary, witnessed by Sera)
⚠ This is not a physical problem or a technical problem.
This is a political problem.
The tools for this problem are different from the tools you know best.
―――――――――――――――――――――――――――
The tools for this problem are different.
I've solved drainage problems with spades. Structural problems with calculations. Commercial problems with contracts. Political problems in the Assembly with prepared documents and corridor conversations.
This is different. This is someone with superior resources and connections who has made a move on a timeline that advantages him. He controls the bureaucratic process. He has the Crown relationship. He has the proposal already filed.
What do I have?
He turned from the window.
'Harwell,' he said. 'The full proposal document. Can you get it?'
'I can try,' Harwell said.
'Not the summary. The full text.'
'It's an official filing. It might be accessible through the March records office.'
'Find out what's accessible and what the process is.' He paused. 'And tell Colwick — formally, in writing — that I received his warning and am in his debt.'
'He won't want payment,' Harwell said.
'I know. Acknowledging the debt is the payment.' Junho sat back down. 'A relationship is maintained by acknowledging when it's been used. Even — especially — when the party doesn't expect acknowledgment.'
Harwell looked at him for a moment. Then he stood.
'I'll find the document,' he said. 'And I'll tell Colwick.'
He left.
Junho sat at the desk.
He did not move for several minutes.
* * *
Sera came in an hour later. She set a cup of tea on the desk without saying anything. She sat across from him.
She waited.
'He filed the proposal,' Junho said.
'I heard,' she said. She had been in the adjacent room when Harwell was there, managing correspondence, in the particular attentive stillness she used when she was present and listening without participating.
'None of the terms I asked for.'
'No.'
'And I can't straightforwardly object because objecting looks—'
'Like credit over outcomes,' she said. 'Yes. I know.'
He was quiet.
'Say it,' she said.
'I thought I was negotiating,' Junho said. 'I was being managed. He sat across from me and looked me in the eye and said he would check the process before making any moves, and he left and filed the proposal in five days.' He paused. 'I didn't see it.'
'You were watching carefully,' Sera said. 'You said so.'
'Not carefully enough.'
'Or he's better at this than you expected.' She looked at the wall. 'He's been at court. Not occasionally. His family has been at court for three generations. What he did is not unusual in a court environment — proposing something and citing the source as a contributor is standard practice. In court, that's how things work. The person with the access defines the frame; the people with the knowledge get credited.'
Standard practice in a court environment. He wasn't deceiving me by his own norms. He was operating normally. I was in a negotiation context; he was in a court-behavior context. We were in different frames and I didn't recognize it.
That's a different kind of mistake from missing the non-return valve. That was an incomplete design. This was an incomplete read of a person's operating mode.
'What do I do?' Junho said.
He asked it directly, because Sera was the person he asked when the question needed to be asked directly.
She was quiet for a moment.
'You have a written meeting summary,' she said. 'Witnessed. That establishes what terms you stated.'
'Yes.'
'You have the documentation of where the approach originated. The Crown survey records, the operational log, dated from month one. The timeline is clear.'
'Yes.'
'You have relationships that Dael doesn't have.' She looked at him. 'Not the same relationships. Different ones. Crane knows you. Lenna Fen knows you. Colwick is allied. Trenn owes you the revised formula's quality. These are not court connections. They're operational connections — people who have worked with you and can speak to the substance of what you do.'
Operational connections versus court connections.
He has people who can endorse him through institutional authority. I have people who can endorse me through direct knowledge of the work.
Those are different kinds of credibility. Neither is automatically superior to the other.
'And Ryse,' Junho said.
Sera looked at him.
'Ryse is implementing at Fenhold,' he said. 'If the approach works at Fenhold because she learned it correctly here — if the Fenhold results are good — that's evidence that the method's quality comes from the specific knowledge, not from Dael's framework document.'
'You're thinking several steps ahead,' Sera said.
'I'm thinking that if the consultation period is six months, and Ryse comes back here two or three more times, and she implements the eastern fields drainage correctly, and the results are visible by the time the consultation closes—'
'Then there's a working example that predates the framework,' Sera said. 'Which establishes the timeline of the knowledge independently of what the document says.'
'Yes.'
She looked at the wall. At the operations documentation.
'Write to Ryse,' she said. 'Directly. Tell her you're aware of the proposal. Tell her you want her to continue the technical exchange regardless of whatever the political situation between you and Dael becomes. Tell her the knowledge is separate from the credit question and you won't compromise her access to it.'
Write to Ryse directly. Separate the technical relationship from the political one. Keep the channel open.
If she understands that I'm not retaliating against her for Dael's move — and she will understand, because she's too perceptive not to — the technical exchange continues. The Fenhold implementation continues. The evidence accumulates.
'And then?' Junho said.
'And then you write to Dael,' Sera said. 'Not a formal objection. A letter. Formal in tone, calm in content. You reference the meeting summary. You note the discrepancy between what was discussed and what was filed. You do not accuse. You state the discrepancy as a fact and ask him to clarify whether the filed document reflects his final position or whether there's been an error.'
Give him the exit. If the discrepancy was genuine — if the proposal was drafted before the visit and he forgot to revise it — the exit of 'there's been an error' lets him correct it without admitting bad faith.
If there was no error, he'll say so. And then we know exactly where we stand.
Either way, the letter is on the record.
'A letter that looks like a courtesy inquiry,' Junho said.
'That is a courtesy inquiry,' Sera said. 'Every word in it should be exactly what it says it is. No hidden threat, no veiled accusation. A genuine question about a discrepancy.'
'And if he ignores it?'
'Then the letter sits on the record and the consultation process proceeds,' she said. 'And we file our own comment during the consultation period.'
'Which looks—'
'Which looks like a territorially affected lord providing technical input during a formal consultation period,' she said. 'Which is exactly what it is. The framing is in how you write the comment. Not a complaint about credit. A contribution to the framework's technical accuracy.' She paused. 'The things Dael's proposal likely gets wrong — because he doesn't have the operational detail — are the things you can correct in a comment. And those corrections, entered in the official record, establish the depth of your knowledge relative to his.'
Technical input during the consultation period. Not a fight over credit. A contribution to accuracy.
Which is also a demonstration, to everyone reviewing the document, of who actually understands the substance.
That's clever. That's better than I would have arrived at alone.
He looked at Sera.
She was watching him with the composed, direct expression of someone who had been thinking about this since Harwell walked through the door.
'You were already planning this,' he said.
'I was thinking,' she said. 'There's a difference.'
'Less of a difference for you than for most people,' he said.
She picked up her pen. 'Write the letter to Ryse first,' she said. 'I'll draft the letter to Dael while you do.'
* * *
The letters went out the same day.
The letter to Ryse was three paragraphs. It told her that Junho was aware of the proposal, that he had concerns he would address through appropriate channels, and that none of those concerns affected her access to the technical exchange. The invitation was open. Thursday was still her day if she wanted it.
The letter to Dael was four paragraphs. The first acknowledged the visit and expressed genuine appreciation for the interest in the approach. The second noted that a copy of their meeting summary — the document he and Sera had written and witnessed — was attached for Lord Dael's reference, in case it was useful as he developed the framework proposal. The third noted, without accusation, that the summary described several terms discussed during the meeting that appeared not to be reflected in the filed proposal as described to Lord Ashmore, and asked whether the filed document represented Lord Dael's final position or whether revisions were planned. The fourth closed with an expression of continuing goodwill and a note that Lord Ashmore looked forward to the formal consultation process.
Sera read both letters before they went.
'The letter to Dael,' she said. 'The second paragraph. Attaching the meeting summary as a reference — that's the weight-bearing component.'
'Yes,' Junho said.
'He'll know the moment he reads it that you documented the meeting immediately after, and that the documentation is witnessed, and that you are now providing him with a copy so that any claim of a misunderstanding has to grapple with the written record.'
'Yes.'
'He'll also know you haven't accused him of anything.'
'Not yet.'
She looked at him. 'Be careful with that last thought. If it shows in the letter—'
'It doesn't,' Junho said. 'I read it three times.'
She read it one more time.
'It doesn't,' she confirmed. She sealed it.
Thk.
* * *
Dael's reply came in eleven days.
Eleven days was itself information. Not three days, which would have suggested immediate response. Not thirty, which would have suggested deliberate delay. Eleven, which was the timing of someone who had read the letter carefully, thought carefully, and decided on a specific response.
The letter was three pages.
The first page was warm. It expressed Dael's continued appreciation for the visit, his ongoing admiration for what had been built at Ashmore, and his genuine intent for the framework to benefit territories across the March.
The second page was more careful. It explained that the proposal had been developed rapidly due to an upcoming deadline at the Agricultural Development Office — an annual review cycle that closed in thirty days. If the proposal missed the cycle, the earliest opportunity for submission would be the following year. The desire to make the deadline had unfortunately meant that some of the refinements discussed at Ashmore had not yet been incorporated. Lord Dael expressed regret for this and stated his full intention to incorporate Lord Ashmore's input during the consultation period.
An annual review cycle with a thirty-day deadline.
That's the explanation. File now or wait a year. The deadline created urgency that couldn't accommodate the agreed terms.
Plausible. Entirely plausible. Annual review cycles exist. Deadlines create pressure. People file incomplete proposals to make deadlines all the time.
Also: the proposal was drafted before the visit. Which means Dael knew about the deadline before he came to Ashmore. He chose to visit knowing he would file within the deadline window. He visited, heard the terms I asked for, and then filed without them.
Was the deadline the real reason, or was the deadline the available reason?
I can't know from here.
The third page addressed the specific terms.
The co-authorship question: the Agricultural Development Office's format did not accommodate co-authorship for proposals from multiple territories. The lead author designation reflected the submitting party, not the source of knowledge. However, Lord Dael proposed to add a formal acknowledgment section to the framework document specifically citing Ashmore as the originating territory of the core methodology.
The review right: the Office's process did not include formal review rights for cited territories during the proposal phase. However, Lord Dael proposed to add Lord Ashmore to the formal consultation notification list, ensuring that any technical input provided during the consultation period would be reviewed and considered.
The names: Lord Dael had already instructed his steward to revise the acknowledgments section to include Mara Dunwick, farmer of Ashmore, and Calder Voss, carpenter of Ashmore, as contributors to the methodology's practical development.
The letter closed: *I hope this addresses Lord Ashmore's concerns. I want this program to succeed, and I believe its success depends on maintaining the trust and participation of the territories that made it possible. I look forward to Lord Ashmore's participation in the consultation process.*
He's given me everything I asked for except co-authorship. Which isn't technically available through the Office's process.
He gave me the acknowledgment of originating territory. The names. The consultation notification. And an explanation of why the co-authorship isn't available.
If the explanation is true — if the Office's format genuinely doesn't accommodate co-authorship — then the best outcome available is what he's offering.
If the explanation is convenient — if the format is more flexible than he's claiming and the deadline was chosen rather than forced — then this is an elegant capitulation that gives me what's available while retaining what matters most: the lead authorship and the frame.
He set the letter down.
Sera had read it over his shoulder. She sat back.
'Mara's name,' she said. 'Calder's name. Those were the things that mattered most.'
'Yes,' Junho said.
'He gave them.'
'Yes.'
They were quiet.
'What do we do?' he said.
'We verify,' she said. 'The Agricultural Development Office's format. Whether co-authorship is genuinely unavailable or whether that's a claim.' She looked at the letter. 'Lenna Fen is at the Crown Road Office. The Road Office and the Agricultural Development Office are in the same building in Veldmark. She would know.'
Lenna. Who ran the numbers on the bridge specification before the meeting. Who cross-references Crown surveys. Who has been in that building for fifteen years.
She'll know whether co-authorship is structurally unavailable or conveniently unavailable.
'Write to her,' Junho said.
'I'll write to her,' Sera said.
* * *
While waiting for Lenna's reply, life continued.
This was the thing about the real world that distinguished it from the problems Junho was more naturally suited to: structural problems waited to be solved. Political problems continued to move while you worked on them, and while you were working on them, everything else continued too.
The school building groundbreaking happened on day four hundred and fifty-one, on a mild late-spring morning. Sera had organized it, Hendry had staked the foundation lines, and Pol and Bett had arrived from Harren three days prior — Lord Colwick had renewed their posting for a second season, a courtesy Junho had not asked for and which meant something.
The foundation was a single day's work for Hendry and Ott. The frame would start next week.
Mara had begun spring planting on the east field's recovered sections. The northwest and central sections went in on schedule; the southwest section, most affected by the flood sediment, she planted at sixty percent density with a variety she called 'stubborn rye,' a shorter-stemmed grain she said was more tolerant of imperfect soil conditions.
'My grandmother saved that seed in bad years,' she said. 'It doesn't produce as much but it produces regardless.'
Stubborn rye. Adapted to adversity. A seed variety passed down through bad years specifically for this situation.
The knowledge at Ashmore runs deeper than anything I brought. It runs through Mara's seed bags and Hendry's mortar and Brin's thatch technique and Carra's road-building memory and Tomas's rock classification and forty years of Pell's records.
I brought a framework. They had the content. I keep needing to remember that.
The grain mill ran its Thursday sessions. Ryse came back twice during the month, each time with specific problems from Fenhold, each time leaving with clearer understanding.
She had not mentioned Dael's proposal in either visit. Neither had Junho. The technical exchange continued, as agreed, separate from the political situation. This separation was maintained by mutual unspoken consent — both of them understood that the channel was too valuable to let the political situation close it.
Ryse was, Junho was coming to understand, not Dael's proxy. She was a professional with her own judgment who happened to work in Dael's household. Those were different things.
* * *
Lenna's reply came on day four hundred and sixty-three.
It was precise, as her responses always were. Three paragraphs.
The first: the Agricultural Development Office's standard format did not include co-authorship provisions for proposals from individual territories. This was accurate. The format assigned a lead proposing party and provided acknowledgment sections for other contributors.
The second: the acknowledgment section was not limited in what it could contain. There was no format restriction preventing a detailed acknowledgment that credited Ashmore as the originating territory or named specific individuals. Whether such acknowledgments were 'co-authorship' in any meaningful sense was a matter of framing, not format.
The third: Lenna noted, without being asked, that she had reviewed the filed proposal as a matter of professional interest. The technical content relating to drainage methodology was accurate in its description of outcomes but incomplete in its description of diagnostic approach. Specifically: the proposal described the herringbone channel system as the solution but did not describe the soil profile assessment method that identified the gravel subbase — which was the critical step that determined whether the drainage approach was applicable. A drainage system installed in clay without a gravel subbase would not perform the same way.
She wrote: *Lord Ashmore will understand the technical significance of this omission. An approach described without its diagnostic prerequisite is an approach that will fail in cases where the prerequisite is not met. If the framework is to be used across the March, the diagnostic methodology must be included. I would suggest that the consultation period comment from Ashmore address this specific technical gap.*
The diagnostic prerequisite.
The soil profile assessment. The creek bank examination. The identification of the gravel subbase. The step that determines whether the drainage approach applies at all.
Dael's proposal describes what to do. It doesn't describe how to know whether to do it.
If territories implement the drainage system without checking the soil profile first, they'll dig channels into clay without a draining subbase, the channels will fill with water and hold it, and the drainage will be worse than no channels at all.
Lenna is right. This is a real technical gap. Not a credit complaint. An accuracy problem that will cause genuine harm if not corrected.
He read the letter twice.
Then he read it a third time.
The trap disappeared.
I've been trying to figure out how to object to the credit terms without looking petty. But that framing was wrong.
I'm not objecting to the credit terms. I'm correcting a technical error that will cause the framework to fail in application.
Those are completely different things. One is a complaint. The other is a contribution.
A technical expert who says 'your drainage guide is missing a critical step and territories that follow it without that step will make their drainage worse' is doing exactly what a technical expert should do. That's not pettiness. That's the job.
He went to find Sera.
He showed her the letter.
She read it. She looked up.
'The diagnostic step,' she said.
'The whole approach depends on identifying the gravel subbase before you start digging,' Junho said. 'Without that step, you dig the channels and the water has nowhere to go and you've made things worse. The proposal doesn't include it.'
'Dael may not have understood that it was a separate step,' Sera said carefully. 'He watched the field. He saw the drainage channels. He may have assumed the soil profile assessment was part of the digging process rather than a prerequisite to it.'
'He may have,' Junho said. 'Or he may have omitted it deliberately, because if the diagnostic step is the critical knowledge, the framework isn't complete without Ashmore's input. And an incomplete framework that he controls is better for his position than a complete one where the completion requires me.'
Or both. Unconscious incompleteness that serves conscious interests. The most dangerous kind of error, because it's genuinely difficult to characterize as bad faith.
'Does it matter which?' Sera said.
'No,' Junho said. 'The comment during consultation addresses the technical gap. It doesn't speculate about intent. It describes the missing step precisely and explains why it's necessary. That's the comment.'
'Yes,' Sera said.
'And the comment is significant. Not a marginal correction. The correction of a fundamental gap in the framework's applicability. If the Agricultural Development Office's reviewers understand the technical implications, the comment will require a substantial revision before the framework is adopted.'
'Requiring Dael to come back to you for the content of that revision,' Sera said.
'Or to acknowledge in the revision that the diagnostic methodology originated at Ashmore,' Junho said. 'Which puts the originating territory credit back in the document, not in the acknowledgment section but in the method description itself.'
That's the move.
Not a fight about credit. A correction of a technical gap that puts the critical knowledge, and its source, in the body of the framework.
He can't remove it. If he removes the diagnostic step from the revision, the framework is still wrong. If he includes it, he has to credit where it came from because it's in the main text, not the acknowledgments.
It's not a perfect position. He controls the document. He can write the diagnostic step description in a way that minimizes Ashmore's contribution. But each revision makes the timeline of knowledge clearer.
And if the framework goes to implementation and the territories follow the drainage approach without the diagnostic step — which they will, because the diagnostic step isn't in the current document — and the drainage fails in territories without a gravel subbase—
Then the framework is a documented failure. And the documented failure's origin will be clearly identifiable in the record.
None of this is good. The failure of the framework is bad for territories that need help. The best outcome is that the diagnostic step gets correctly included and the framework works.
I need to write a comment that fixes the framework. Not because it helps my position, though it does. Because it's the right thing. And those happen to be the same action.
'I'll write the comment,' he said.
'I'll help,' Sera said.
'Yes,' he said. 'And Lenna should review the technical language before we submit it.'
'I'll write to her.'
'One more thing,' he said.
Sera looked at him.
'Write to Dael as well,' Junho said. 'Before the comment is filed. Tell him we've identified a technical gap and we want to give him the opportunity to address it in a revision before the consultation comment period, so the framework goes into consultation in its strongest form.'
Sera looked at him for a long moment.
'You're giving him another exit,' she said.
'Yes,' Junho said. 'If he takes it and revises the framework correctly, the outcome is good. The framework works. Territories benefit.'
'And if he doesn't?'
'Then the consultation comment is on the record,' Junho said. 'And the record is clear.'
She was quiet for a moment.
'You keep giving him exits,' she said. 'Even after he filed without the agreed terms.'
'Yes,' Junho said.
'Why?'
Because the exits are not generosity. They're methodology.
Every exit I give him that he doesn't take makes the record clearer. Every opportunity to correct that he doesn't take narrows the space for 'misunderstanding.'
And every exit I give him that he does take produces a better outcome for the territories that need this framework.
I don't know if he's acting in bad faith or just in court-norms. In either case, the right move is to keep giving him the opportunity to do the right thing.
Not because he deserves it. Because the record is cleaner if he refuses it than if I don't offer it.
'Because the best outcome is that the framework works correctly,' Junho said. 'And the second-best outcome is that the record shows clearly who had the knowledge and who provided the exit that wasn't taken.'
Sera looked at him.
'That's cold,' she said.
'It's accurate,' he said.
She picked up her pen.
'I'll write the letter to Dael,' she said. 'You write the technical comment. We review each other's work.'
'One word each,' he said.
'Probably more this time,' she said.
* * *
That evening, Junho walked the east field.
It was a habit now — the evening walk, when the day's work had settled into the log and tomorrow's work was not yet urgent enough to occupy the mind. He walked and thought about things that were not quite problems yet and were not quite plans yet.
The stubborn rye in the southwest section was small but present — thin green shoots, shorter than the ones in the northwest, but alive. Mara had been right about it. It was producing, in imperfect conditions, what it had been bred over generations to produce.
Stubborn rye. Adapted to adversity.
I need to be the stubborn rye for the next few months.
Not aggressive. Not dramatic. Just present and producing, in conditions that aren't ideal, doing the work that needs doing regardless of whether the conditions cooperate.
He reached the northeast corner — the corner that had been last to drain, last to plant, last to establish. The full-density planting here was the strongest in the field. The soil in this section had been affected least by the flood because it was farthest from the outlet, and the recovery had been fullest.
The things that were last are sometimes the strongest. Because they had more time.
I've been building here for over a year. Dael has been in the framework process for three weeks. The knowledge is mine — not because I claimed it but because I built it, day by day, in the soil and the timber and the gears and the people.
Documentation is the record of that. The operational log, the letters, the meeting summary, Lenna's technical review, Ryse's notebooks with the corrections in her own hand.
He can write the framework. He cannot write the record of how the knowledge was built.
The two moons were rising. The large pale one leading, the red crescent following.
They had been rising over this field since before he arrived. They would be rising over it long after whatever happened with Dael was resolved.
The field didn't care about the framework process. The rye didn't care. The drainage channels didn't care. They kept doing what they did.
I should take a lesson from that.
He walked back to the hall.
He had letters to write.
—
[ End of Chapter 27 ]
~ 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