Chapter 9 Names #2
His colleague Priya was standing behind him with a coffee in one hand and her laptop tucked beneath the other arm.
“Morning,” Elliot replied.
“You look suspiciously well-rested.”
Elliot smiled.
“Do I?”
“Either that or you’re hiding something.”
“I’m not.”
Priya studied him for a moment.
“You’re smiling.”
“I smile.”
“Not before nine in the morning.”
Elliot laughed.
The elevator doors opened.
“Maybe I’m changing.”
Priya stepped inside.
“That’s terrifying.”
Elliot followed her.
He didn’t mention Kai.
He couldn’t.
The metro had always been separate from work.
That separation felt more important now that their lives were becoming complicated.
When Elliot reached his desk, he opened his laptop and immediately found several messages waiting for him. Most were routine. A bug report. A request for a data pull. A meeting invitation.
Then he noticed an email from his department director.
New Project Assignment — Urban Mobility & Commercial Development Analysis
Elliot opened it.
The project involved a large-scale redevelopment initiative planned across several connected neighborhoods. His company had been contracted to provide data analysis and software modeling for the development group.
At first glance, it looked like exactly the kind of work Elliot handled regularly.
Transportation patterns.
Passenger volumes.
Commercial activity.
Population movement.
Property utilization.
Projected economic impact.
The goal was to build a predictive model that could estimate how the redevelopment would affect traffic, public transportation, business activity, and surrounding neighborhoods over the next several years.
Elliot leaned back in his chair.
It was a large project.
Important enough that senior management would be watching closely.
He opened the attached documentation.
There were spreadsheets, maps, property datasets, demographic reports, transportation statistics, and several preliminary planning documents.
Elliot began reading.
His technical mind shifted automatically into work mode.
He examined the data structure.
He identified missing fields.
He noted inconsistent property classifications.
He marked several areas where historical data would need to be cleaned before the model could produce reliable projections.
Within half an hour, the personal thoughts from the previous evening had been pushed aside.
This was familiar territory.
Numbers made sense.
Systems made sense.
People were complicated.
Data usually wasn’t.
At least, it wasn’t supposed to be.
Over the next several hours, Elliot worked through the datasets.
He mapped transportation patterns against commercial properties.
He compared passenger movement during morning and evening rush hours.
He studied projected changes in metro usage.
He analyzed neighborhood demographics and economic indicators.
One of the models predicted that redevelopment could significantly increase commercial activity in certain areas.
Another projected improved transportation efficiency.
The numbers looked promising.
Too promising, perhaps.
Elliot frowned at one of the projections.
He ran the calculation again.
The result was almost identical.
He made a note to investigate the underlying assumptions later.
For now, he continued.
Around lunchtime, he joined a project meeting.
A senior project manager presented the broader plan.
“We’re looking at a multi-phase redevelopment,” she explained. “The objective is to improve commercial utilization, transportation connectivity, and long-term economic growth.”
Elliot listened while scrolling through the maps on his laptop.
Several highlighted zones appeared on the screen.
One of them caught his attention.
He couldn’t immediately explain why.
The name looked familiar.
He zoomed in.
The neighborhood name appeared in several datasets.
He had seen it somewhere before.
Elliot frowned.
The meeting continued around him.
“We’ll need the first mobility model within three weeks.”
Three weeks.
Elliot typed a note.
Then he looked at the neighborhood name again.
Something about it bothered him.
He searched the internal database.
The result returned a list of commercial properties, transportation routes, and development targets.
He opened one of the property maps.
The area was close to the metro line he used every evening.
Elliot stared at the screen.
He knew the neighborhood.
He had passed through it countless times.
But that wasn’t why the name felt familiar.
He tried to remember where he had heard it.
Then his phone vibrated.
A message from Kai.
You surviving today?
Elliot smiled immediately.
He typed a response.
Barely. You?
The reply came a few seconds later.
Same.
Elliot looked at the message.
He smiled again.
Then he returned to the project.
The neighborhood name remained on the screen.
He didn’t yet understand why.
He didn’t know that the answer was sitting only a few metro stops away.
He didn’t know that the redevelopment map he was analyzing contained the very streets where Kai had grown up.
He didn’t know that the tattoo studio was somewhere inside the highlighted zone.
And he certainly didn’t know that the project he had just been assigned could eventually threaten the person who had become the most important part of his evenings.
For now, it was simply another project.
Another dataset.
Another deadline.
Another problem Elliot was expected to solve.
Across the city, Kai was dealing with a very different kind of problem.
He had barely opened the studio when someone from the neighborhood association arrived.
Kai recognized the expression immediately.
Bad news.
“What happened?”
The man placed a folder on the counter.
“They’ve moved the meeting forward.”
Kai’s shoulders tightened.
“To when?”
“Next week.”
“That soon?”
The man nodded.
“There are more representatives involved now. The development company has apparently submitted additional planning documents.”
Kai opened the folder.
Maps.
Property lists.
Preliminary proposals.
He scanned the pages.
His stomach tightened.
The discussions weren’t casual anymore.
They were becoming formal.
Serious.
Immediate.
“What are they asking for?”
“Several blocks.”
Kai’s eyes moved across the map.
His studio was there.
His father’s studio.
His home.
Everything he’d spent years protecting.
He closed the folder.
“They’re not getting it.”
The man looked at him.
“They may have more support than we expected.”
Kai’s jaw tightened.
“Then we’ll need more people.”
“You can’t fight them alone.”
“I know.”
The man left a few minutes later.
Kai remained behind the counter.
He looked through the front window.
The neighborhood looked exactly as it always had.
The café across the street.
The grocery store on the corner.
The old buildings lining the block.
People walking to work.
Nothing looked different.
But Kai knew something had changed.
The threat was no longer distant.
It was moving closer.
His phone vibrated.
He looked down.
A message from Elliot.
Still surviving.
Kai smiled.
He typed back.
Good. I need you alive for tonight’s train ride.
He sent it before reconsidering the wording.
A few seconds later, Elliot replied.
Wouldn’t miss it.
Kai stared at the message.
A strange warmth spread through him.
He had no idea what Elliot was working on.
Elliot had no idea what Kai was fighting.
Their lives still existed in separate worlds.
For another evening, the metro would bring those worlds together.
Neither man knew how close they were to colliding.
And neither understood that the next time Elliot opened the redevelopment data, the familiar neighborhood name would lead him directly toward Kai.
· ? ·