Two Projects, One Man
1302 Words
Alicia realised it during a meeting that wasn’t supposed to matter.
It was a routine Helix check‑in, low stakes, low visibility, a loose collection of updates delivered by people who expected little more than polite acknowledgment. She sat at the edge of the table, laptop open, posture softened, her presence deliberately reduced to fit the role she was playing.
Training Content Developer.
Invisible. Peripheral. Safe.
The facilitator droned on about completion percentages and user readiness metrics. Alicia listened with half her attention, fingers annotating a document she’d already internalised, mind running parallel calculations the way it always did.
Then the door opened.
Nate walked in.
Not late. Not rushed. Just… present.
He took the empty chair across from her without ceremony, set his notebook down, and glanced up at the screen as if he’d been there all along. No introductions followed. No one thought it necessary. He belonged here now, apparently, as seamlessly as he had belonged on Orion.
Alicia felt it immediately, the shift. Subtle, but unmistakable. Like a hairline fracture in a structure that had been load‑bearing for years.
Two projects.
One man.
She kept her eyes on her screen, her expression unchanged, but internally the architecture of her day rearranged itself. This was no longer theoretical. No longer a future risk. Nate was not a shared resource on paper. He was a shared witness in practice.
He spoke halfway through the meeting.
Not to assert dominance. Not to redirect the agenda. Just to ask a question that cut cleanly through the noise.
“How are we aligning the training scenarios with the revised migration logic?” he asked. “The assumptions changed last week.”
The facilitator hesitated. Someone else answered vaguely.
Alicia typed.
She did not look up.
“I can take that offline,” she said calmly, voice measured, unremarkable. “I’ve already adjusted the content to account for the changes.”
Nate’s gaze flicked to her.
Just once.
It wasn’t surprise that registered there. It was recognition. The same quiet, unsettling kind she’d felt in the Orion meeting earlier that day, like two independent data points suddenly resolving into a pattern.
“Good,” he said. “That’ll save us trouble later.”
The meeting moved on.
Alicia did not relax.
Afterward, she packed up quickly, slipping back to her desk before the facilitator could think to ask follow‑up questions. She sat, opened her laptop, and grounded herself in the familiar rhythm of work. Task. Focus. Deliver.
Still, she felt him before she heard him.
“You switch well,” Nate said, stopping beside her desk.
She didn’t look up. “Switch?”
“Contexts,” he clarified. “Orion this morning. Helix now. Different cadence. Different expectations.” He paused. “Same outcome.”
Alicia kept typing. “That’s consulting.”
He smiled faintly. “That’s talent.”
She stopped.
Just for a moment.
Then resumed.
“Was there something you needed?” she asked, tone cool, professional, deliberately flat.
“Just confirming you’ll join the data review tomorrow,” he said. “Both projects.”
Her fingers slowed.
“Yes,” she replied. “I’ll be there.”
“Great.” He hesitated, then added, “You don’t mind the overlap?”
Alicia looked up then, meeting his gaze squarely.
“I manage overlaps for a living.”
He held her eyes for a beat longer than necessary, as if weighing the answer.
“I’ll see you tomorrow,” he said, and walked away.
Alicia sat very still.
This was not how it was supposed to work.
Her system relied on separation. On clean lines. On controlled intersections that never lingered long enough to invite scrutiny. Orion and Helix were meant to exist in parallel, connected only by her, by versions of herself no one ever thought to compare.
Nate collapsed that distance simply by existing in both spaces with equal ease.
She opened her calendar and scanned the next two weeks.
He was everywhere.
Steering committees. Data checkpoints. Training alignment sessions. Workshops she usually attended anonymously. Forums where she led.
She closed the calendar.
At lunch, she took refuge in an unused meeting room, sandwich untouched, eyes unfocused as she replayed the morning’s interactions. Not with anxiety, panic was inefficient, but with precision.
What did he know?
He knew she was competent. That was unavoidable.
He knew she shifted roles. That was common enough in consulting.
What he did not know, and could not know, if she was careful, was how deliberate the shift was. How engineered. How essential.
Still.
Patterns were his domain.
And Alicia had built her life on the assumption that no one would ever think to look for them.
Her phone buzzed.
Natalie: You’re quiet. That’s never a good sign.
Alicia typed, then erased, then typed again.
Alicia: HR has deployed Nate across both projects.
Three dots appeared immediately.
Natalie: Oh.
Then-
Natalie: Oh, this just got interesting.
Alicia exhaled through her nose.
Alicia: It’s a structural risk.
Natalie: It’s a narrative gift.
Alicia: This is not a story.
Natalie: Everything is a story. You just prefer yours without witnesses.
Alicia didn’t reply.
She spent the afternoon doing what she always did when control was threatened.
She tightened it.
Her responses to Nate became clipped. Efficient. Minimal. She avoided unnecessary proximity, declined optional discussions, redirected questions to group forums instead of private conversations. Where warmth might have softened an exchange, she introduced distance instead.
Strategic rudeness, Natalie would have called it.
Alicia thought of it as risk mitigation.
By the end of the day, she’d succeeded in one respect: Nate no longer lingered at her desk. He stopped asking follow‑up questions. He observed from farther away.
But she had failed in another.
He noticed.
At the final meeting of the day, an Orion wrap‑up that ran ten minutes over, Nate stayed behind as others filtered out. Alicia was packing up when he spoke.
“You don’t like overlap,” he said, not accusing. Observing.
“I don’t like inefficiency,” she replied.
“Same thing, sometimes.”
She closed her laptop. “Is there a concern?”
He leaned back against the table, arms loosely crossed. “Only that you’re working very hard not to be seen.”
The words landed cleanly. No edge. No challenge.
Just truth.
Alicia met his gaze, her expression unreadable.
“Visibility is contextual,” she said. “I suggest you focus on data.”
A flicker of something, amusement, perhaps, passed over his face.
“I always do,” he said. “That’s how I know when something doesn’t add up.”
She held his gaze for a moment longer than necessary, then stepped past him.
“Goodnight, Nate.”
“Goodnight, Alicia.”
At home, the routine faltered.
Not enough to collapse, never that, but enough to register. She aligned her shoes twice. Reset the kitchen counter after already resetting it. Stood by the window longer than usual, watching the city fall into its predictable patterns.
Two projects.
One man.
The problem was not that Nate might discover who she was.
The problem was that he might discover how she was.
That her invisibility was not an accident, but a choice.
That her power did not announce itself because she had learned, the hard way, what happened when it did.
Alicia turned away from the window and prepared for bed, movements precise, controlled.
Tomorrow, she would adjust.
She always did.
But as she slid beneath the sheets, the quiet of the apartment pressing in around her, she acknowledged something she could not yet solve.
Nathaniel Cole was not a variable she could isolate.
He was a constant now.
And constants, she knew, had a way of forcing systems to reveal their limits.
- Writer
- chap_listContents
- likeADD