Another week passed in a quiet, rciful blur.
Willow threw herself into work with surgical precision, early mornings bleeding into late nights, coffee cooling beside her keyboard, and the steady rhythm of typing that felt more reliable than her own pulse. Her departnt was running on fus and adrenaline, pushing to finalize the healthcare inventory interface upgrade before shifting focus to the next major contract.
She had promised Malik that the rollout would be flawless before the Star Engineering proposal eting next week. That promise translated into long evenings, black coffee, and the soft hum of monitors long after most of the office had emptied. She did not resent the pace. Busyness was armor, and noise left no space for ghosts.
Her office reflected her discipline. A glass desk anchored the room, immaculate except for her laptop, a legal pad filled with deliberate handwriting, and a ceramic mug she kept forgetting to refill. Sunlight filtered through half drawn blinds and striped the walls in muted gold. Her dark hair was twisted into a low bun, precise but not severe. The sleeve of her white blouse was folded carefully to accommodate the structured cast on her arm, the matte black brace stark against pale fabric. She had adapted to typing one handed with ruthless efficiency, fingers moving quickly enough that most people forgot she was injured at all.
She liked control. Order. Predictability. Clean code. Clean outcos.
Her phone buzzed across the desk and interrupted the rhythm. She glanced down and stilled when she saw the na on the screen.
Zane Reyes.
The ssage preview glowed softly.
Zane: You’re impossible to reach. I’m starting to think you’re avoiding .
Her thumb hovered over the glass. She was not avoiding him. Not exactly. She was postponing him. Postponing felt safer than confronting whatever had shifted between them. She scrolled upward and saw several unread ssages and two missed calls from late at night. She rembered seeing them. She rembered turning the phone over instead of answering.
Guilt brushed against her calm but did not linger. Silence had not been cruelty. It had been containnt.
She typed back.
Willow: Not avoiding. Just busy. Deadlines are carnivorous this week.
The reply ca almost imdiately.
Zane: Carnivorous? Should I worry about the survival rate of your team?
Her mouth softened despite herself.
Willow: We’re fine. Mild casualties. The coffee machine didn’t make it.
Zane: Tragic. I’ll send flowers.
She stared at the screen longer than necessary. This was the problem. The ease. The quiet humor. The way he made tension feel negotiable. She turned the phone face down and forced her attention back to the monitor.
Logic. Structure. Code.
By Friday she had nearly convinced herself that the kiss and the electricity surrounding it were irrelevant variables. They had been shelved, categorized, filed away like archived data that no longer affected current operations.
A knock sounded lightly on the glass door before Malik stepped inside carrying two things: an espresso cup in one hand and a thick corporate folder in the other.
"You are not going to believe what IT did," he announced, closing the door behind him.
Willow did not look up imdiately. "Given that introduction, I probably will."
"They sent the QA reminder to the entire company. Not just dev. HR. Finance. Cleaning staff. Everyone is invited to tomorrow’s test run."
Her head lifted sharply. "Everyone?"
"Even the vending machine contractor," he said with exaggerated gravity. "He already RSVP’d yes."
She leaned back in her chair and exhaled slowly. "Perfect. A cross departntal symposium on code validation."
"If the system crashes, at least we will panic with witnesses," Malik replied.
A reluctant smile touched her lips. "You understand I am holding you personally responsible for this circus."
"I will bring popcorn," he said, setting the espresso down on her desk.
"Bring earplugs," she returned.
He laughed softly, then lifted the folder in his other hand. "Speaking of organized chaos. This is the Star Engineering brief. Hard copy. I figured you would want to review it before we confirm the technical alignnt eting."
He placed the folder on her desk, its cover embossed with the company insignia in understated silver.
Willow’s attention sharpened imdiately. "They sent full schematics?"
"Full access overview. Logistics managent overhaul. International vendor synchronization. Real ti supply mapping. They want a system built from scratch."
She slid the folder closer and opened it without hesitation. Schematic diagrams unfolded across the pages. Workflow projections layered over supplier chains. Risk assessnts flagged in red across multiple jurisdictions. The scale of it stirred sothing steady inside her. This was architecture disguised as logistics, a structural problem demanding elegance.
"Ambitious," she murmured.
"They are paying for ambitious," Malik replied. "Premium contract. They were not happy with their last outsourcing attempt. This ti they want it bulletproof."
She flipped through the pages thodically. "Good. Then they will get disciplined."
Malik watched her for a mont before nodding toward her cast. "Two weeks left?"
"If the scan is clean," she answered calmly. "Doctor says it is healing on schedule."
"Try not to redesign global infrastructure with one hand."
"I adapt," she replied without looking up.
"That is why this landed on your desk," he said. "Let know when you want to lock in the consultation confirmation. I will coordinate with their IT division."
"Early next week," she said. "I want to review their architecture assumptions first."
Malik left her office, pulling the door closed behind him.
The room settled back into its familiar hum. Willow studied the executive summary briefly, confirming scope and projected deadlines before moving deeper into the technical breakdown. Titles and signatures mattered less than systems. She was interested in frawork compatibility, migration risk, scalability under stress.
As she turned a page, an uninvited image flickered through her thoughts. Dark eyes. A level voice. The restrained stillness of soone who rarely moved without purpose.
Zane.
The association irritated her. It had nothing to do with this project. She straightened in her chair and forced her focus back to the docunt.
She opened a new email.
To: Star Engineering IT DepartntSubject: Consultation Confirmation and Technical Alignnt
Her tone was precise and neutral. She confird availability windows, outlined docuntation requirents, and proposed an initial architecture review session. Each sentence was deliberate and contained.
She pressed send and felt the quiet satisfaction of forward motion.
The folder remained open on her desk, several pages deep into supplier logistics and system migration flowcharts. The executive authorization page sat near the back of the packet, formatted in dense corporate structure that she had not yet reached.
Her phone remained face down beside her keyboard.
Outside the window, the city lights began to shimr into evening.
Across the city, in a different tower of glass and steel, Star Engineering’s internal system registered a confird consultation scheduling email from a senior project lead at a leading technology solutions firm. The ssage was automatically categorized under enterprise systems integration and routed to the corporate IT architecture team for coordination, where it joined a queue of high level external infrastructure engagents awaiting internal alignnt.
Inside her office, Willow returned to her code and her diagrams, unaware that the system she had just agreed to rebuild would soon intersect with the one variable she was still postponing.
User Comments
0 comments from readers