Chapter 26
Abel received the consultancy call while standing in his kitchen with Leona’s last message unanswered.
The message was a photograph of three restaurant options and the words: None of you can be trusted to choose efficiently.
At ten twelve, it had been flirtation.
At ten nineteen, the project lead explained the lobby photograph, the route information, and the institute’s need for integrated exposure analysis. She disclosed a known personal conflict and asked whether Abel wished to enter formal review or decline immediately.
His first instinct was no.
Not because he feared professional discipline. Because accepting felt like consenting to erase warmth precisely when Leona was frightened.
That instinct was the reason he did not trust it.
“Who handles physical protection?” he asked.
“A separate team.”
“Will I advise Dr. Grant personally?”
“No personal security advice. Your scope is institute systems, family-data separation, vendor exposure, site vulnerabilities, reporting, and continuity. Recommendations go through me. She retains client decision authority as executive director.”
“Can you replace me?”
“Yes. Four to six days for comparable integrated capacity. We can split the role sooner among three people, but coordination risk rises.”
“And Kieran?”
“Separate choice. I cannot tell you his answer.”
Of course.
Abel requested the written conflict terms. The documents arrived from the consultancy, the institute’s counsel, and Simone Baptiste. They were severe in all the places severity mattered.
No romantic or sexual contact. No private communication.
No suggestive language, fantasy shorthand, or covert reassurance.
No unnecessary physical proximity. No monitoring outside the defined professional scope.
No access to Leona’s private Society records.
No discussion of future romance. Necessary communication only on preserved work channels.
Independent escort. Permanent recusal from any future Leona-specific assignment after this contract.
Abel read the terms twice.
He called Simone.
“What if I decline?”
“The relationship remains private and may continue, subject to any narrower conflict created by information you have already received. The consultancy finds someone else.”
“What if declining delays protection for her staff?”
“That is a professional factor, not romantic coercion. You decide whether your expertise is sufficiently necessary to accept. Do not make Leona responsible for your choice.”
“And if I accept?”
“The firewall activates when the contract does. No exception because the threat is frightening. Crisis increases leverage; it does not cleanse it.”
He paced the kitchen. His gait was uneven because he had not fully seated the prosthesis after showering. Ordinarily he would stop and adjust. Now agitation tried to turn discomfort into proof of urgency.
Abel sat.
He removed the prosthesis, checked the skin, and gave the decision the time it deserved.
His expertise could protect sixty-three employees, their families, and the institute’s continuity.
He would not guard Leona. He would not become the man at her door.
Independent people would handle physical safety.
His work would reduce the chance that vendor systems and public schedules exposed less visible staff.
Refusing solely to preserve private access would also make romance distort professional judgment.
He called the project lead.
“I accept the limited scope under three conditions. No direct personal advisory relationship. Independent close protection remains separate. My permanent recusal from Dr. Grant-specific work survives the contract.”
“Agreed.”
“And accessibility on site is handled through my stated requirements, not assumptions about where I should remain.”
“Of course.”
“Put the specific process in writing. ‘Of course’ is where memory goes to die.”
The revised terms arrived twenty minutes later.
At noon, the contract activated.
Abel watched the private message thread lock.
He had the absurd urge to send one word before the minute changed—Here—but the urge exposed the problem.
Here would have been a promise created by professional proximity, a private reassurance Leona could not separate from the man helping manage her danger.
He let the minute pass.
His first assignment was to acknowledge the project channel and request documents. He wrote to the shared list.
Dr. Grant and team,
Please provide the current vendor roster, event-access agreements, public schedule workflow, emergency-contact data map, incident-preservation procedure, continuity plan, and building access policy through the secure project repository.
Interviews will be scheduled by the project coordinator.
Do not email sensitive records directly.
Regards,
Abel C. Nwosu
He removed the sentence he wanted to add: I am sorry this is happening.
The apology would have been human and professionally ordinary in another context. Here, Leona could claim it as a private signal because she knew the voice beneath it.
Abel sent the clean version.
The cost landed immediately.
Warmth had always felt like the ethical alternative to cold authority.
Now he had to accept that warmth could also exploit access if directed privately through duty.
He could remain humane in meetings. He could respect choice.
He could build systems that preserved Leona’s voice.
He could not make any of those things courtship.
He opened a new document and titled it Institute Exposure Integration Map.
Then he began the work that had made the separation necessary.
The first files revealed why his scope mattered beyond Leona.
The institute’s event vendor had received emergency contacts in a master spreadsheet because an employee once combined travel and event fields for convenience.
The vendor passed parts of the file to registration subcontractors.
Most deleted it on schedule; one retained an export beyond the contract.
The exposure was not one evil choice. It was a chain of ordinary permissions no one had revisited.
Abel requested interviews with the people who used the system daily, including administrative assistants and event coordinators. Executive diagrams rarely showed the shortcuts that kept work moving.
The project coordinator asked whether he needed Leona’s personal travel file.
“No,” he said. “The close-protection team holds operational travel. I need the process that decides who receives an itinerary, not the itinerary itself.”
Refusing unnecessary access was part of the firewall, but it was also good risk practice. Data not acquired could not become temptation, dependency, or breach.
At six, Abel shut down the project workspace and called his own business manager. The assignment would require canceling a profitable workshop the following week.
“Do you want to decline?” she asked.
“No. Reschedule it and pay the venue change fee from my firm. Do not ask the new client to absorb it.”
“You are allowed to protect your income.”
“Yes. I am also choosing this assignment. Choice has cost.”
The answer reminded him that Leona held no financial leverage over his life. He could leave. He could refuse scope. The fact that he chose professional duty did not make him nobly trapped.
He prepared dinner, adjusted the prosthesis, and deliberately placed his personal phone in another room. The locked message thread could not be opened, but he did not need the physical habit of waiting beside it.
Tomorrow he would speak to Leona through a project lead.
Tonight he practiced existing where she could not receive him.
Before bed, Abel made a second document that would never enter the client file. It contained no private facts about Leona. It was a boundary map for himself.
Professional warmth available to everyone: explain reasoning, offer accessible choices, admit uncertainty, ask before assistance, notice unequal burden.
Private warmth unavailable during contract: messages, romantic memory, special reassurance, coded humor, future promises, touch, disclosure designed to make her care for him.
The first list prevented him from confusing the firewall with cruelty. The second prevented him from using kindness as a smuggling route.
He sent the framework to Simone without names.
She called the next morning. “Your categories are useful. The risk is that you will treat the lists as complete.”
“Meaning?”
“You cannot pre-classify every sentence. Context creates leverage. Ask who receives the warmth and what response the speaker hopes to cause.”
Abel leaned back from his desk. “If I praise a staff member’s analysis in a meeting?”
“Ordinary professional recognition.”
“If I praise Leona’s analysis in the same meeting?”
“Potentially ordinary. Would you say it if you had no romantic history? Would you say it in the same tone? Would the work benefit from naming it? Or do you want her to hear I still see you?”
The last question found its mark.
“I want her to hear that,” he said.
“Then you do not make the work carry it.”
Abel closed his eyes briefly. “Understood.”
The project coordinator joined his next call with an administrative assistant who managed event registrations.
She explained how emergency contacts had entered the vendor export: the institute once needed travel contacts for a retreat, and the temporary spreadsheet became the template for every event afterward.
“Was anyone assigned to delete the extra columns?” Abel asked.
“No. We were assigned to make registration faster.”
“Then the system produced what it rewarded. This is not an individual confession.”
Her shoulders lowered on screen.
Together they redesigned the workflow. The institute would collect only event-specific information, keep emergency contacts in a restricted system, and use time-limited vendor access.
Any exception required a named owner and deletion date.
The assistant asked for a stop-work rule if a senior person requested a full export at the last minute.
“Yes,” Abel said. “Put the authority with the person doing the export. Escalation goes to operations, not around you.”
That was professional warmth: changing a system so the least powerful person did not have to absorb everyone else’s urgency.
When the call ended, Abel did not wonder whether Leona would admire the work. He recorded the decision, assigned the owner, and moved to the next dependency.