CHAPTER 25 — THE SHAPE OF PROTECTION
January arrived with the specific quality of a new year in a cold city — the same streets, the same buildings, the same grey sky, but with the particular freshness of a calendar that had reset and the particular resolve of a person who had spent December processing things and was now ready to work.
Su Wanqing was ready to work.
The Meridian engagement was the largest project she had managed since before the studio had closed, and she had spent the break between years — the quiet days between Christmas and the new year, the days the building had been mostly empty and the city had been in its post-holiday suspension — doing exactly what she always did in the interval between finishing one major thing and beginning the next: thinking. Not planning, not scheduling, not building the structural framework that would need to exist by January second. Thinking, in the specific way of someone who needed to understand the shape of a problem before they could address it.
She understood the shape of this one. It was interesting and it was large and it was going to require her to operate at a level she had not operated at since before everything, and she was ready for that.
The first week passed well.
Contract meetings with Meridian's legal team, handled through the corporate structure with Zhou Cheng coordinating logistics. A kickoff meeting with the extended project team — not just the Lu Corporation creative group but the wider team that would be building out the engagement, including representatives from Meridian's communications division. The specific, productive discomfort of a project that was large enough that she could see its edges only by walking toward them.
She worked with the focused efficiency of someone doing what they were built for.
It was on the second Wednesday of January that something changed.
---
The email from Zhou Cheng arrived at ten-fourteen.
It was a calendar update — a meeting she had been scheduled to attend later in the week, a presentation of the initial creative direction to a small group of Meridian stakeholders. She had been preparing for this meeting. She had her materials ready. She had been scheduled as lead creative and presenter, which was the correct designation.
The update changed her role to *materials support.*
*Meeting updated: Mr. Lu will present the creative direction. Miss Su's materials will be incorporated into the presentation. Miss Su is not required to attend.*
She read it twice.
Not required to attend.
She was the lead creative on the project. She had built the direction. The materials were hers. In the professional framework she had been working within for months, the lead creative attended the client-facing presentations of their work. This was not a preference — it was a function. You presented your own work because you were the person who could answer questions about it, because you understood the reasoning behind every decision, because being in the room when clients first encountered the work gave you information you needed to develop it further.
She wrote back to Zhou Cheng: *Could you clarify the reason for the change? I want to make sure I understand the meeting structure.*
The reply came in twenty minutes: *Mr. Lu's decision. He will present the creative direction to the stakeholders. Your materials will be used.*
She looked at the email for a moment.
Then she went upstairs.
She had not, this time, written a draft of what she was going to say. She had not prepared for the conversation the way she prepared for difficult conversations — by establishing the outcome she wanted and the arguments that would support it and the concessions she was willing to make. She was going past that kind of preparation, into the territory of a conversation she needed to have regardless of its outcome because the information it produced was more important than managing how the conversation went.
She needed to know why.
She had learned, over the months of working with him, to distinguish between the registers he used for different kinds of statements. There was the register of professional authority — *I've made the decision, the decision stands* — which was blunt and final. There was the register of collaborative thinking — the whiteboard sessions, the back-and-forth of a problem being worked through together.
And there was this: the register of someone managing something they were not going to share, not because they didn't want to but because they had decided — or had been constrained — not to. The register of a person who knew something and was carrying it alone.
She recognised it because she had been in it herself.
Not the official reason. The reason under the official reason. She had learned, in the past months, that there was almost always a reason under the official reason, and that the official reason was the surface of something, and that she was now in the business of looking at what was underneath.
---
He was at his desk when she arrived — not standing at the window, not mid-thought. Actually at his desk, with documents that he was reading, in the posture of someone who had been there for a while and intended to be there for a while more.
He looked up when she came in.
"The Meridian stakeholder meeting," she said. She was using the register she used when she had a professional concern to raise — not confrontational, not accusatory, the register of someone who wanted to understand something. "I've been removed from the presentation role. I want to understand why."
He looked at her for a moment. His expression had the quality she had come to recognise over the past months as his version of careful consideration — not blankness, not resistance, the specific quality of someone who was thinking through what to say rather than simply responding.
"The meeting includes stakeholders outside the standard project team," he said. "I'll be presenting."
She looked at him.
"Is there a reason I shouldn't be in that room?"
A pause. Not the pause of someone considering the answer — the pause of someone who had the answer and was considering whether to give it.
"It's more efficient to have one presenter," he said. "The stakeholders are senior. The format suits a direct executive presentation."
"I've presented to senior stakeholders before," she said. "Successfully. Including the internal board presentation in November." She kept her voice level. "The format argument doesn't hold — we've run hybrid presentations with multiple voices before and they've been effective."
He looked at the desk. A brief, specific gesture — the looking-at-the-desk that she had catalogued as the equivalent of the looking-at-the-window: thinking in real time, not finished.
"I've made the decision," he said.
"I understand you've made the decision," she said. "I'm asking for the reasoning behind it, because I'm the lead creative and the reasoning affects how I approach the project."
Another pause.
"There are stakeholder dynamics in this meeting that are outside the project scope," he said, finally. "I'm managing them. It's not a reflection of your work or your capabilities."
She looked at him.
*There are stakeholder dynamics in this meeting that are outside the project scope.*
This was new information. He had not, in any previous decision-making conversation, offered this kind of qualifier. He had said *it's a business decision*, he had said *these are operational considerations*, he had said things that were correct without being explanatory. *Stakeholder dynamics outside the project scope* was a different kind of statement — it acknowledged that there was something in the room that was not about the project, and that he was managing it, and that the management required her absence.
She noted this.
She had been building a vocabulary for the specific ways he communicated over the past months — learning to distinguish between the registers he used for different categories of information, the way a person developed fluency in a language by paying attention to its grammar rather than just its words. She knew the difference between *it's a business decision* (which meant: I've decided and I'm not going to explain further) and *there are considerations outside the project scope* (which meant: there are things I know that you don't, and I am choosing not to share them, and this choice is deliberate).
He had never used that second register with her before.
Every previous decision — the scope amendments, the meeting requirements, the feedback patterns — had been delivered in the first register. *I've decided. This is the way it is.* Even when she had pushed back and he had listened and they had arrived at different conclusions together, the communication had been in the register of professional authority: I have considered your input and I am making a decision.
This was different.
This was the register of someone who was managing something they were not going to share. Not because they didn't want to — the quality of the pause before *there are stakeholder dynamics outside the project scope* had not been the quality of someone who had decided not to explain. It had been the quality of someone who had decided they *couldn't* explain, which was a different constraint entirely.
She had spent six years making assumptions about his motivations. She had spent the past few months questioning those assumptions. She was not going to make a new assumption in the room. She was going to take the information, note it precisely, and think about it somewhere she could think properly.
"All right," she said. "I'll have the full deck ready for Thursday."
He nodded.
She walked out.
---
She sat at her workstation for twenty minutes doing nothing visible.
On the surface, she was looking at her screen. The screen had a document open. The document was a specification for the Meridian visual system. She was not reading it.
She was thinking about *stakeholder dynamics outside the project scope.*
She opened the private file.
The five items were there. The two questions were there. She read through them, which she had done enough times now that they were not fully surprising, but which still produced the specific quality of looking at a set of evidence that was trying to tell her something she had not yet fully heard.
She added a sixth item:
*6. Removed from Meridian stakeholder meeting. "Stakeholder dynamics outside the project scope." No explanation.*
She read the six items together.
Then she did something she had not permitted herself to do yet — she built the hypothesis. Not the partial hypothesis of *he is keeping me away from something*, which she had written two weeks ago and which had been accurate but incomplete. The fuller hypothesis.
She wrote it slowly, because the writing of it required precision:
*He is keeping me away from something connected to the family. The family has contact with the Meridian stakeholders (or the meeting includes family-connected parties). He believes my presence in that room creates a risk. He is managing the risk by removing me from the equation.*
She looked at what she had written.
The logic held.
She had done this before — the building of a hypothesis from incomplete data — in design contexts, in client situations, in the specific kind of problem-solving that required you to make a decision before you had all the information you needed. The method was the same regardless of context: you gathered what you had, you identified the pattern it suggested, you formed the most economical hypothesis that accounted for all the data, and you proceeded with that hypothesis while staying alert to information that contradicted it.
The hypothesis she had built accounted for all six items in the file. It accounted for the lily. It accounted for the "No. I know." It accounted for Old Madam Lu knowing her name. It accounted for the meeting reassignment and the phrase *stakeholder dynamics outside the project scope.*
The hypothesis she had built also — and this was the part she was sitting with, the part that required her to hold it carefully and not rush to process it — accounted for certain things that had happened six years ago, if she extended it backward in time.
She extended it backward carefully.
If the family had been managing things they didn't approve of six years ago, and if the thing they hadn't approved of had been her specifically — not her work, not her background, but her presence in his life — then the events of six years ago could look different than they had looked to her at the time.
She did not complete this chain of reasoning yet. She had learned not to build too far ahead of her evidence.
But she had set the foundation.
She was not certain of it — she did not have enough information to be certain of it. But the logic held in the specific way that a design direction held before you had tested it: the underlying structure was sound, the evidence pointed consistently in the same direction, and the alternative explanations were either weaker or required assumptions the current evidence didn't support.
If the logic held, then the question was not *why is he making decisions without me.* The question was *what is he protecting me from, and why does he think I need protecting.*
She had been building hypotheses from incomplete data her whole professional life — it was, in some ways, the core skill of design work: you gathered what you had, you identified the pattern it suggested, you formed the most economical hypothesis that accounted for all the data, and you proceeded with that hypothesis while staying alert to information that contradicted it.
The hypothesis she had now accounted for all six items. The lily. The 'No, I know.' Old Madam Lu knowing her name. The meeting reassignment. The phrase *stakeholder dynamics outside the project scope.*
It also — and this was the part she was sitting with most carefully — accounted for certain things that had happened six years ago, if she extended the hypothesis backward in time.
If the family had been managing what they didn't approve of six years ago, and if the thing they hadn't approved of was her specifically — not her work, but her presence in his life — then the events she had spent six years filing under *betrayal* could look different. The absence of runway before those events was not evidence of his concealment. It was evidence of urgency imposed from outside.
She was not ready to say this was what had happened.
She was ready to say it was the most economical hypothesis she currently had.
She saved the file.
She closed it.
She went back to the visual system specification.
---
She called Tang Xin at eight that evening — not from habit, from the specific decision that Tang Xin was the right person to have this conversation with.
"How much do you know about the Lu family?" she said, when Tang Xin picked up. "Beyond the general knowledge."
A brief pause. Tang Xin's pauses always had information in them.
"Enough to know that they don't allow things to happen that they haven't approved," she said. "In the company and outside it. They're the kind of family that has been managing their environment for long enough that the management has become invisible — it just looks like the way things are."
Wanqing was quiet for a moment.
"Does that extend to decisions within the company? About personnel?"
Another pause, longer than the first.
"Why are you asking?" Tang Xin said. Not evasion — genuine care, the care of someone who was trying to understand what she was actually being asked.
"Something happened in December," Wanqing said. "Something in January. I'm trying to understand whether they're connected."
Tang Xin was quiet for three seconds.
"Yes," she said. "It would extend to that."
Wanqing sat with this.
"Thank you," she said.
"Wanqing." Tang Xin's voice had the quality it had when she had something specific to say. "Whatever you're putting together — be careful with it. Not because you're wrong. Because being right about certain things in certain environments requires more than just the information."
"I know," Wanqing said.
She had needed to hear it confirmed by someone who was not her. She had been building the hypothesis alone, from evidence she had gathered alone, in a file she had kept private. That kind of solitary evidence-gathering had a specific vulnerability: it was possible to convince yourself of things that were not true when you were the only person checking your own reasoning.
Tang Xin had confirmed the structural logic without knowing the full picture. That was different from confirmation by someone who had the same information and agreed with her conclusion. It was the confirmation of someone who knew the environment well enough to say: yes, this is the kind of thing this environment produces.
It was enough.
After she hung up, she sat for a long time with the confirmed hypothesis and the caution and the specific quality of a thing that had been half-visible for months and was now, finally, beginning to resolve into a shape she could describe.
He was protecting her from something.
She did not know what.
She was going to find out.
She added one more line to the file, below the hypothesis:
*Next step: find out who the stakeholders in Thursday's meeting are.*
She closed her laptop.
She went to bed.
She thought, before sleeping, that she had been right to stay. Not because of what she was finding — the finding was uncomfortable and incomplete and pointed toward things she was not sure she was ready to face. But because she was finding it. She was standing on her own two feet and finding it, and that was what she had stayed for.
She had not been wrong about that.
You've reached the end of this chapter
CHAPTER 25 — THE SHAPE OF PROTECTION
January arrived with the specific quality of a new year in a cold city — the same streets, the same buildings, the same grey sky, but with the particular freshness of a calendar that had reset and the particular resolve of a person who had spent December processing things and was now ready to work.
Su Wanqing was ready to work.
The Meridian engagement was the largest project she had managed since before the studio had closed, and she had spent the break between years — the quiet days between Christmas and the new year, the days the building had been mostly empty and the city had been in its post-holiday suspension — doing exactly what she always did in the interval between finishing one major thing and beginning the next: thinking. Not planning, not scheduling, not building the structural framework that would need to exist by January second. Thinking, in the specific way of someone who needed to understand the shape of a problem before they could address it.
She understood the shape of this one. It was interesting and it was large and it was going to require her to operate at a level she had not operated at since before everything, and she was ready for that.
The first week passed well.
Contract meetings with Meridian's legal team, handled through the corporate structure with Zhou Cheng coordinating logistics. A kickoff meeting with the extended project team — not just the Lu Corporation creative group but the wider team that would be building out the engagement, including representatives from Meridian's communications division. The specific, productive discomfort of a project that was large enough that she could see its edges only by walking toward them.
She worked with the focused efficiency of someone doing what they were built for.
It was on the second Wednesday of January that something changed.
---
The email from Zhou Cheng arrived at ten-fourteen.
It was a calendar update — a meeting she had been scheduled to attend later in the week, a presentation of the initial creative direction to a small group of Meridian stakeholders. She had been preparing for this meeting. She had her materials ready. She had been scheduled as lead creative and presenter, which was the correct designation.
The update changed her role to *materials support.*
*Meeting updated: Mr. Lu will present the creative direction. Miss Su's materials will be incorporated into the presentation. Miss Su is not required to attend.*
She read it twice.
Not required to attend.
She was the lead creative on the project. She had built the direction. The materials were hers. In the professional framework she had been working within for months, the lead creative attended the client-facing presentations of their work. This was not a preference — it was a function. You presented your own work because you were the person who could answer questions about it, because you understood the reasoning behind every decision, because being in the room when clients first encountered the work gave you information you needed to develop it further.
She wrote back to Zhou Cheng: *Could you clarify the reason for the change? I want to make sure I understand the meeting structure.*
The reply came in twenty minutes: *Mr. Lu's decision. He will present the creative direction to the stakeholders. Your materials will be used.*
She looked at the email for a moment.
Then she went upstairs.
She had not, this time, written a draft of what she was going to say. She had not prepared for the conversation the way she prepared for difficult conversations — by establishing the outcome she wanted and the arguments that would support it and the concessions she was willing to make. She was going past that kind of preparation, into the territory of a conversation she needed to have regardless of its outcome because the information it produced was more important than managing how the conversation went.
She needed to know why.
She had learned, over the months of working with him, to distinguish between the registers he used for different kinds of statements. There was the register of professional authority — *I've made the decision, the decision stands* — which was blunt and final. There was the register of collaborative thinking — the whiteboard sessions, the back-and-forth of a problem being worked through together.
And there was this: the register of someone managing something they were not going to share, not because they didn't want to but because they had decided — or had been constrained — not to. The register of a person who knew something and was carrying it alone.
She recognised it because she had been in it herself.
Not the official reason. The reason under the official reason. She had learned, in the past months, that there was almost always a reason under the official reason, and that the official reason was the surface of something, and that she was now in the business of looking at what was underneath.
---
He was at his desk when she arrived — not standing at the window, not mid-thought. Actually at his desk, with documents that he was reading, in the posture of someone who had been there for a while and intended to be there for a while more.
He looked up when she came in.
"The Meridian stakeholder meeting," she said. She was using the register she used when she had a professional concern to raise — not confrontational, not accusatory, the register of someone who wanted to understand something. "I've been removed from the presentation role. I want to understand why."
He looked at her for a moment. His expression had the quality she had come to recognise over the past months as his version of careful consideration — not blankness, not resistance, the specific quality of someone who was thinking through what to say rather than simply responding.
"The meeting includes stakeholders outside the standard project team," he said. "I'll be presenting."
She looked at him.
"Is there a reason I shouldn't be in that room?"
A pause. Not the pause of someone considering the answer — the pause of someone who had the answer and was considering whether to give it.
"It's more efficient to have one presenter," he said. "The stakeholders are senior. The format suits a direct executive presentation."
"I've presented to senior stakeholders before," she said. "Successfully. Including the internal board presentation in November." She kept her voice level. "The format argument doesn't hold — we've run hybrid presentations with multiple voices before and they've been effective."
He looked at the desk. A brief, specific gesture — the looking-at-the-desk that she had catalogued as the equivalent of the looking-at-the-window: thinking in real time, not finished.
"I've made the decision," he said.
"I understand you've made the decision," she said. "I'm asking for the reasoning behind it, because I'm the lead creative and the reasoning affects how I approach the project."
Another pause.
"There are stakeholder dynamics in this meeting that are outside the project scope," he said, finally. "I'm managing them. It's not a reflection of your work or your capabilities."
She looked at him.
*There are stakeholder dynamics in this meeting that are outside the project scope.*
This was new information. He had not, in any previous decision-making conversation, offered this kind of qualifier. He had said *it's a business decision*, he had said *these are operational considerations*, he had said things that were correct without being explanatory. *Stakeholder dynamics outside the project scope* was a different kind of statement — it acknowledged that there was something in the room that was not about the project, and that he was managing it, and that the management required her absence.
She noted this.
She had been building a vocabulary for the specific ways he communicated over the past months — learning to distinguish between the registers he used for different categories of information, the way a person developed fluency in a language by paying attention to its grammar rather than just its words. She knew the difference between *it's a business decision* (which meant: I've decided and I'm not going to explain further) and *there are considerations outside the project scope* (which meant: there are things I know that you don't, and I am choosing not to share them, and this choice is deliberate).
He had never used that second register with her before.
Every previous decision — the scope amendments, the meeting requirements, the feedback patterns — had been delivered in the first register. *I've decided. This is the way it is.* Even when she had pushed back and he had listened and they had arrived at different conclusions together, the communication had been in the register of professional authority: I have considered your input and I am making a decision.
This was different.
This was the register of someone who was managing something they were not going to share. Not because they didn't want to — the quality of the pause before *there are stakeholder dynamics outside the project scope* had not been the quality of someone who had decided not to explain. It had been the quality of someone who had decided they *couldn't* explain, which was a different constraint entirely.
She had spent six years making assumptions about his motivations. She had spent the past few months questioning those assumptions. She was not going to make a new assumption in the room. She was going to take the information, note it precisely, and think about it somewhere she could think properly.
"All right," she said. "I'll have the full deck ready for Thursday."
He nodded.
She walked out.
---
She sat at her workstation for twenty minutes doing nothing visible.
On the surface, she was looking at her screen. The screen had a document open. The document was a specification for the Meridian visual system. She was not reading it.
She was thinking about *stakeholder dynamics outside the project scope.*
She opened the private file.
The five items were there. The two questions were there. She read through them, which she had done enough times now that they were not fully surprising, but which still produced the specific quality of looking at a set of evidence that was trying to tell her something she had not yet fully heard.
She added a sixth item:
*6. Removed from Meridian stakeholder meeting. "Stakeholder dynamics outside the project scope." No explanation.*
She read the six items together.
Then she did something she had not permitted herself to do yet — she built the hypothesis. Not the partial hypothesis of *he is keeping me away from something*, which she had written two weeks ago and which had been accurate but incomplete. The fuller hypothesis.
She wrote it slowly, because the writing of it required precision:
*He is keeping me away from something connected to the family. The family has contact with the Meridian stakeholders (or the meeting includes family-connected parties). He believes my presence in that room creates a risk. He is managing the risk by removing me from the equation.*
She looked at what she had written.
The logic held.
She had done this before — the building of a hypothesis from incomplete data — in design contexts, in client situations, in the specific kind of problem-solving that required you to make a decision before you had all the information you needed. The method was the same regardless of context: you gathered what you had, you identified the pattern it suggested, you formed the most economical hypothesis that accounted for all the data, and you proceeded with that hypothesis while staying alert to information that contradicted it.
The hypothesis she had built accounted for all six items in the file. It accounted for the lily. It accounted for the "No. I know." It accounted for Old Madam Lu knowing her name. It accounted for the meeting reassignment and the phrase *stakeholder dynamics outside the project scope.*
The hypothesis she had built also — and this was the part she was sitting with, the part that required her to hold it carefully and not rush to process it — accounted for certain things that had happened six years ago, if she extended it backward in time.
She extended it backward carefully.
If the family had been managing things they didn't approve of six years ago, and if the thing they hadn't approved of had been her specifically — not her work, not her background, but her presence in his life — then the events of six years ago could look different than they had looked to her at the time.
She did not complete this chain of reasoning yet. She had learned not to build too far ahead of her evidence.
But she had set the foundation.
She was not certain of it — she did not have enough information to be certain of it. But the logic held in the specific way that a design direction held before you had tested it: the underlying structure was sound, the evidence pointed consistently in the same direction, and the alternative explanations were either weaker or required assumptions the current evidence didn't support.
If the logic held, then the question was not *why is he making decisions without me.* The question was *what is he protecting me from, and why does he think I need protecting.*
She had been building hypotheses from incomplete data her whole professional life — it was, in some ways, the core skill of design work: you gathered what you had, you identified the pattern it suggested, you formed the most economical hypothesis that accounted for all the data, and you proceeded with that hypothesis while staying alert to information that contradicted it.
The hypothesis she had now accounted for all six items. The lily. The 'No, I know.' Old Madam Lu knowing her name. The meeting reassignment. The phrase *stakeholder dynamics outside the project scope.*
It also — and this was the part she was sitting with most carefully — accounted for certain things that had happened six years ago, if she extended the hypothesis backward in time.
If the family had been managing what they didn't approve of six years ago, and if the thing they hadn't approved of was her specifically — not her work, but her presence in his life — then the events she had spent six years filing under *betrayal* could look different. The absence of runway before those events was not evidence of his concealment. It was evidence of urgency imposed from outside.
She was not ready to say this was what had happened.
She was ready to say it was the most economical hypothesis she currently had.
She saved the file.
She closed it.
She went back to the visual system specification.
---
She called Tang Xin at eight that evening — not from habit, from the specific decision that Tang Xin was the right person to have this conversation with.
"How much do you know about the Lu family?" she said, when Tang Xin picked up. "Beyond the general knowledge."
A brief pause. Tang Xin's pauses always had information in them.
"Enough to know that they don't allow things to happen that they haven't approved," she said. "In the company and outside it. They're the kind of family that has been managing their environment for long enough that the management has become invisible — it just looks like the way things are."
Wanqing was quiet for a moment.
"Does that extend to decisions within the company? About personnel?"
Another pause, longer than the first.
"Why are you asking?" Tang Xin said. Not evasion — genuine care, the care of someone who was trying to understand what she was actually being asked.
"Something happened in December," Wanqing said. "Something in January. I'm trying to understand whether they're connected."
Tang Xin was quiet for three seconds.
"Yes," she said. "It would extend to that."
Wanqing sat with this.
"Thank you," she said.
"Wanqing." Tang Xin's voice had the quality it had when she had something specific to say. "Whatever you're putting together — be careful with it. Not because you're wrong. Because being right about certain things in certain environments requires more than just the information."
"I know," Wanqing said.
She had needed to hear it confirmed by someone who was not her. She had been building the hypothesis alone, from evidence she had gathered alone, in a file she had kept private. That kind of solitary evidence-gathering had a specific vulnerability: it was possible to convince yourself of things that were not true when you were the only person checking your own reasoning.
Tang Xin had confirmed the structural logic without knowing the full picture. That was different from confirmation by someone who had the same information and agreed with her conclusion. It was the confirmation of someone who knew the environment well enough to say: yes, this is the kind of thing this environment produces.
It was enough.
After she hung up, she sat for a long time with the confirmed hypothesis and the caution and the specific quality of a thing that had been half-visible for months and was now, finally, beginning to resolve into a shape she could describe.
He was protecting her from something.
She did not know what.
She was going to find out.
She added one more line to the file, below the hypothesis:
*Next step: find out who the stakeholders in Thursday's meeting are.*
She closed her laptop.
She went to bed.
She thought, before sleeping, that she had been right to stay. Not because of what she was finding — the finding was uncomfortable and incomplete and pointed toward things she was not sure she was ready to face. But because she was finding it. She was standing on her own two feet and finding it, and that was what she had stayed for.
She had not been wrong about that.
You've reached the end of this chapter