Chapter 23

Chapter 23: Jealousy Escalates

Chapter 23: Jealousy Escalates

The fourth month of the project had a different quality from the first three.

Arjun noticed this in the way he noticed most things that mattered — not all at once, but gradually, through the accumulation of small evidence. The work was in its most demanding phase: decisions compounding, timelines converging, the construction schedule requiring the kind of sustained attention that left little room for the other things his mind had developed a habit of returning to.

He was managing this. He was good at managing things.

What he was less good at, he was discovering, was managing two separate categories of preoccupation simultaneously without one of them bleeding into the other.

The first category: a question, folded carefully and placed in a drawer marked *insufficient evidence.* Eighteen months plus nine months. Twenty-seven months. A calculation he had performed once and then declined to perform again, because performing it a second time would constitute something closer to a conclusion than he was willing to reach on the available information.

The second category: the work. Which was, on any given day, sufficient to occupy a person entirely.

By Monday morning of the fourth month, he had been maintaining this separation for approximately ten days. He considered this adequate. He was incorrect.

---

He needed to confirm a material decision with Nisha before the contractor placed the afternoon order.

This was straightforward. He had done it dozens of times — a brief exchange, two minutes, the kind of operational communication that the project required constantly. He walked to the twenty-eighth floor at ten-fifteen with the folder containing the specification and the expectation of a two-minute conversation.

She was not in her office.

The project assistant looked up from her desk. "She's in the shared workspace. End of the corridor — meeting with her studio partner."

Arjun walked to the end of the corridor.

The shared workspace was an open area with four large tables and good window light, used by the various teams when they needed room to spread out. At the far table: Nisha, and beside her — close enough that they were both looking at the same laptop screen — Rohan Mehta.

Arjun had seen him three times now. He had a clear picture: mid-thirties, the ease of someone who operated in creative environments and had made a successful peace with the informal register they required. He was pointing at something on the screen and talking, and Nisha was following his point with the tilted head she used when she was genuinely tracking an argument, and then she nodded and laughed — not the professional warmth she distributed in meetings, the other one, the one that meant she had found something actually funny.

Arjun stopped at the entrance to the workspace.

He stood there for what he would later estimate as four seconds and what had felt, from the inside, considerably longer.

He was aware of what he was doing. He was also aware that being aware of it was not, apparently, sufficient to stop it, which was a new development in his relationship with his own self-control.

He walked in.

"Nisha." His voice came out at the correct register — professional, unhurried, the tone of someone interrupting a meeting with a brief practical matter. "The Calcutta stone specification — I need confirmation before three."

She looked up. "Right — yes, the honed finish. I confirmed that with Suresh last week, it should be in the system."

"It's not showing as confirmed on the contractor's end."

"I'll send it again now." She was already reaching for her phone.

He was aware of Rohan Mehta looking at him with the polite attention of someone waiting to see if the interruption was going to require his participation. Arjun looked back at him with the neutral expression he brought to most situations and said, because it was the correct thing to say: "Sorry to interrupt."

"No problem," Rohan said, with the ease of someone who meant it.

Nisha sent the confirmation. Arjun verified it on his own phone. Two minutes, as projected. He thanked her and left.

In the corridor, he walked at his normal pace and looked at his phone and told himself the matter was resolved.

---

The site meeting on the tenth floor began at two.

It was a working session — the head contractor, two of his team leads, Nisha. The purpose was to review the progress on the corridor lighting installation and confirm the ceiling finish sequence for the next three weeks. Arjun attended because the tenth floor decisions had downstream implications for the eleventh and twelfth floor scheduling that he needed to understand directly.

At two-twenty, Rohan Mehta arrived.

Nisha had mentioned this in passing that morning — her studio partner was handling the supplier contract for the custom metalwork, and his presence at the session would allow the relevant questions to be answered in real time. This was logical. Arjun had registered it as logical when she mentioned it and he registered it as logical now.

Logical and also: present for the next two hours in the same room.

Arjun sat at the head of the construction table and ran the meeting the way he always ran meetings — with full attention, efficient movement through the agenda, the quality of focus that was both genuine and, today, requiring more active maintenance than usual.

The lighting installation questions were resolved. The ceiling finish sequence was confirmed. Rohan provided the metalwork supplier's delivery window, which answered a scheduling question that had been open for a week.

The meeting was productive. Everyone in it was doing their job well.

Arjun participated in all of this with eighty percent of his attention.

The remaining twenty percent was occupied with the specific awareness of two people on the other side of the table who had been working together long enough to have developed a vocabulary of small signals — the shorthand of shared history, the way Rohan caught a detail in Nisha's presentation before she finished stating it, the way she incorporated his amendment without a beat of hesitation, the complete ease of two people who knew each other's thinking.

At three forty-five, as the meeting was winding toward its conclusion, Rohan said something to Nisha in a low voice — not directed at the room, directed at her. She tilted her head slightly and her expression shifted in the way it shifted when she heard something that was both accurate and unexpected, and she laughed, quietly, the laugh that was not professional warmth.

Arjun was signing the session documentation when he wrote his name on the witness line instead of the approving authority line.

He noticed immediately. He drew a clean line through it, initialled the correction, and signed in the correct place.

The head contractor did not look up.

Arjun put the pen down with the care of someone setting it down deliberately rather than dropping it.

---

The room cleared gradually after the session ended — the contractor team first, then the two engineers, then Rohan, who gathered his materials with the easy efficiency of someone with somewhere to be and said goodbye to Nisha with the warmth of a person who did not need to perform warmth because it simply existed.

Nisha was gathering her own materials.

Arjun stayed.

"The phase four deliverables," he said. "Given the current timeline compression — can your studio guarantee the milestone dates?"

It was a legitimate question. The phase four timeline had been under pressure since the structural overrun, and the delivery capacity of a two-principal studio against a project of this scale was a real consideration. He had looked at the numbers. They were achievable but not comfortable.

All of this was true.

Nisha looked up from her bag. The look she gave him was the one she produced when she had received a question and was simultaneously processing its stated content and its actual content.

"Yes," she said.

One word. Then she held his gaze for a moment — the beat of someone deciding whether to leave it there.

"Is there anything else?" she said.

Three words. Carrying, underneath them, the weight of a woman who had been watching him for four months and had a reasonably complete picture of what was happening in this room.

He looked at her.

He had been telling himself, for the duration of the afternoon, that this was about project management. He was now in the position of having said the project management version of the question and received the project management answer, and the actual question was still in the room, unasked.

"Rohan Mehta knows you well," he said.

It came out the way things come out when you have stopped fighting their arrival — not angry, not accusing, simply the observation of a man who had been watching something all afternoon and had reached the limit of pretending he had not been.

Nisha looked at him.

The look lasted long enough for him to understand she was deciding what to give him.

"He's the only person who knows my whole story," she said.

Quiet. Not defensive — something more deliberate. The tone of a person offering a specific thing in place of a larger thing, giving him what he needed to hear rather than what he had asked.

She picked up her bag.

And left.

---

Arjun stood in the empty meeting room.

The construction floor was quiet now — the day's work done, the evening shift not yet arrived. Through the unfinished windows, the city was moving into its late afternoon, the light shifting from sharp to gold.

*He's the only person who knows my whole story.*

He turned the sentence over.

Not: he's just a colleague. Not: there's nothing between us. She had not said those things, which he noted, because she was precise in what she said and did not offer reassurance she had not chosen to offer. What she had said was something different: a statement about knowledge. About who held the complete version of her.

Rohan Mehta knew her whole story.

Arjun did not.

And the part of her story he did not know — the part he had been carrying in a folded drawer for ten days, the part that involved an eighteen-month-old who liked yellow and a calculation that added up to twenty-seven months — that part was, apparently, part of the whole.

He walked to the window.

The city below was doing its ordinary things, uninterested in the interior states of the people observing it from above.

He had spent two and a half years with a story about what had happened between them. A story in which she had left. A story in which the ending had been hers, and he had been left with the aftermath of it, and he had built his life accordingly.

That story had made sense. He had believed it completely.

But if the calculation was right — if the arithmetic of twenty-seven months meant what it appeared to mean — then the story had a chapter he had not been given. A chapter that existed, that had been lived, that had produced a child who painted everything yellow.

And if that chapter existed, what did that mean for the chapter he had believed was the ending?

He did not know.

He stood at the window until the light had finished its shift from gold to grey, and then he picked up his folder and took the stairs to the fortieth floor and sat at his desk and looked at the city for a long time.

The question had changed shape.

It was no longer just: *could she be.*

It was: *if she is — then what, exactly, happened two and a half years ago?*

He did not have an answer.

But the question, once it had taken that shape, was not something he could put back in the drawer.

He sat with it until midnight.

The city outside his window did not offer anything useful.

But it stayed with him, which was, he supposed, what cities did.

You've reached the end of this chapter

Chapter 23

Chapter 23: Jealousy Escalates

Chapter 23: Jealousy Escalates

The fourth month of the project had a different quality from the first three.

Arjun noticed this in the way he noticed most things that mattered — not all at once, but gradually, through the accumulation of small evidence. The work was in its most demanding phase: decisions compounding, timelines converging, the construction schedule requiring the kind of sustained attention that left little room for the other things his mind had developed a habit of returning to.

He was managing this. He was good at managing things.

What he was less good at, he was discovering, was managing two separate categories of preoccupation simultaneously without one of them bleeding into the other.

The first category: a question, folded carefully and placed in a drawer marked *insufficient evidence.* Eighteen months plus nine months. Twenty-seven months. A calculation he had performed once and then declined to perform again, because performing it a second time would constitute something closer to a conclusion than he was willing to reach on the available information.

The second category: the work. Which was, on any given day, sufficient to occupy a person entirely.

By Monday morning of the fourth month, he had been maintaining this separation for approximately ten days. He considered this adequate. He was incorrect.

---

He needed to confirm a material decision with Nisha before the contractor placed the afternoon order.

This was straightforward. He had done it dozens of times — a brief exchange, two minutes, the kind of operational communication that the project required constantly. He walked to the twenty-eighth floor at ten-fifteen with the folder containing the specification and the expectation of a two-minute conversation.

She was not in her office.

The project assistant looked up from her desk. "She's in the shared workspace. End of the corridor — meeting with her studio partner."

Arjun walked to the end of the corridor.

The shared workspace was an open area with four large tables and good window light, used by the various teams when they needed room to spread out. At the far table: Nisha, and beside her — close enough that they were both looking at the same laptop screen — Rohan Mehta.

Arjun had seen him three times now. He had a clear picture: mid-thirties, the ease of someone who operated in creative environments and had made a successful peace with the informal register they required. He was pointing at something on the screen and talking, and Nisha was following his point with the tilted head she used when she was genuinely tracking an argument, and then she nodded and laughed — not the professional warmth she distributed in meetings, the other one, the one that meant she had found something actually funny.

Arjun stopped at the entrance to the workspace.

He stood there for what he would later estimate as four seconds and what had felt, from the inside, considerably longer.

He was aware of what he was doing. He was also aware that being aware of it was not, apparently, sufficient to stop it, which was a new development in his relationship with his own self-control.

He walked in.

"Nisha." His voice came out at the correct register — professional, unhurried, the tone of someone interrupting a meeting with a brief practical matter. "The Calcutta stone specification — I need confirmation before three."

She looked up. "Right — yes, the honed finish. I confirmed that with Suresh last week, it should be in the system."

"It's not showing as confirmed on the contractor's end."

"I'll send it again now." She was already reaching for her phone.

He was aware of Rohan Mehta looking at him with the polite attention of someone waiting to see if the interruption was going to require his participation. Arjun looked back at him with the neutral expression he brought to most situations and said, because it was the correct thing to say: "Sorry to interrupt."

"No problem," Rohan said, with the ease of someone who meant it.

Nisha sent the confirmation. Arjun verified it on his own phone. Two minutes, as projected. He thanked her and left.

In the corridor, he walked at his normal pace and looked at his phone and told himself the matter was resolved.

---

The site meeting on the tenth floor began at two.

It was a working session — the head contractor, two of his team leads, Nisha. The purpose was to review the progress on the corridor lighting installation and confirm the ceiling finish sequence for the next three weeks. Arjun attended because the tenth floor decisions had downstream implications for the eleventh and twelfth floor scheduling that he needed to understand directly.

At two-twenty, Rohan Mehta arrived.

Nisha had mentioned this in passing that morning — her studio partner was handling the supplier contract for the custom metalwork, and his presence at the session would allow the relevant questions to be answered in real time. This was logical. Arjun had registered it as logical when she mentioned it and he registered it as logical now.

Logical and also: present for the next two hours in the same room.

Arjun sat at the head of the construction table and ran the meeting the way he always ran meetings — with full attention, efficient movement through the agenda, the quality of focus that was both genuine and, today, requiring more active maintenance than usual.

The lighting installation questions were resolved. The ceiling finish sequence was confirmed. Rohan provided the metalwork supplier's delivery window, which answered a scheduling question that had been open for a week.

The meeting was productive. Everyone in it was doing their job well.

Arjun participated in all of this with eighty percent of his attention.

The remaining twenty percent was occupied with the specific awareness of two people on the other side of the table who had been working together long enough to have developed a vocabulary of small signals — the shorthand of shared history, the way Rohan caught a detail in Nisha's presentation before she finished stating it, the way she incorporated his amendment without a beat of hesitation, the complete ease of two people who knew each other's thinking.

At three forty-five, as the meeting was winding toward its conclusion, Rohan said something to Nisha in a low voice — not directed at the room, directed at her. She tilted her head slightly and her expression shifted in the way it shifted when she heard something that was both accurate and unexpected, and she laughed, quietly, the laugh that was not professional warmth.

Arjun was signing the session documentation when he wrote his name on the witness line instead of the approving authority line.

He noticed immediately. He drew a clean line through it, initialled the correction, and signed in the correct place.

The head contractor did not look up.

Arjun put the pen down with the care of someone setting it down deliberately rather than dropping it.

---

The room cleared gradually after the session ended — the contractor team first, then the two engineers, then Rohan, who gathered his materials with the easy efficiency of someone with somewhere to be and said goodbye to Nisha with the warmth of a person who did not need to perform warmth because it simply existed.

Nisha was gathering her own materials.

Arjun stayed.

"The phase four deliverables," he said. "Given the current timeline compression — can your studio guarantee the milestone dates?"

It was a legitimate question. The phase four timeline had been under pressure since the structural overrun, and the delivery capacity of a two-principal studio against a project of this scale was a real consideration. He had looked at the numbers. They were achievable but not comfortable.

All of this was true.

Nisha looked up from her bag. The look she gave him was the one she produced when she had received a question and was simultaneously processing its stated content and its actual content.

"Yes," she said.

One word. Then she held his gaze for a moment — the beat of someone deciding whether to leave it there.

"Is there anything else?" she said.

Three words. Carrying, underneath them, the weight of a woman who had been watching him for four months and had a reasonably complete picture of what was happening in this room.

He looked at her.

He had been telling himself, for the duration of the afternoon, that this was about project management. He was now in the position of having said the project management version of the question and received the project management answer, and the actual question was still in the room, unasked.

"Rohan Mehta knows you well," he said.

It came out the way things come out when you have stopped fighting their arrival — not angry, not accusing, simply the observation of a man who had been watching something all afternoon and had reached the limit of pretending he had not been.

Nisha looked at him.

The look lasted long enough for him to understand she was deciding what to give him.

"He's the only person who knows my whole story," she said.

Quiet. Not defensive — something more deliberate. The tone of a person offering a specific thing in place of a larger thing, giving him what he needed to hear rather than what he had asked.

She picked up her bag.

And left.

---

Arjun stood in the empty meeting room.

The construction floor was quiet now — the day's work done, the evening shift not yet arrived. Through the unfinished windows, the city was moving into its late afternoon, the light shifting from sharp to gold.

*He's the only person who knows my whole story.*

He turned the sentence over.

Not: he's just a colleague. Not: there's nothing between us. She had not said those things, which he noted, because she was precise in what she said and did not offer reassurance she had not chosen to offer. What she had said was something different: a statement about knowledge. About who held the complete version of her.

Rohan Mehta knew her whole story.

Arjun did not.

And the part of her story he did not know — the part he had been carrying in a folded drawer for ten days, the part that involved an eighteen-month-old who liked yellow and a calculation that added up to twenty-seven months — that part was, apparently, part of the whole.

He walked to the window.

The city below was doing its ordinary things, uninterested in the interior states of the people observing it from above.

He had spent two and a half years with a story about what had happened between them. A story in which she had left. A story in which the ending had been hers, and he had been left with the aftermath of it, and he had built his life accordingly.

That story had made sense. He had believed it completely.

But if the calculation was right — if the arithmetic of twenty-seven months meant what it appeared to mean — then the story had a chapter he had not been given. A chapter that existed, that had been lived, that had produced a child who painted everything yellow.

And if that chapter existed, what did that mean for the chapter he had believed was the ending?

He did not know.

He stood at the window until the light had finished its shift from gold to grey, and then he picked up his folder and took the stairs to the fortieth floor and sat at his desk and looked at the city for a long time.

The question had changed shape.

It was no longer just: *could she be.*

It was: *if she is — then what, exactly, happened two and a half years ago?*

He did not have an answer.

But the question, once it had taken that shape, was not something he could put back in the drawer.

He sat with it until midnight.

The city outside his window did not offer anything useful.

But it stayed with him, which was, he supposed, what cities did.

You've reached the end of this chapter