She called on a Sunday morning.
I was in the middle of a cost review monthly financial ledger spread across the table, every line annotated, nothing approximate when the secondary line buzzed. I looked at the number. Confirmed it. Set down my pen.
Three days since Thursday. Sunday morning meant she'd thought about it across the weekend and called before she could decide to wait longer. That was useful information. It meant the decision had required effort to hold off on, which meant interest was real rather than polite.
"She's not rejecting me after all that right?"
I let it ring four times before answering. Not because I was performing unavailability — I don't perform things that have no operational purpose — but because answering immediately on a secondary contact line signals that you've been waiting, and waiting is a form of need.
"Kuroda here," I said.
"It's Utsushimi." A beat. "From Thursday."
"I remember."
"Right." A short pause. "I wanted to ask a few more questions before I decided anything."
"Go ahead."
She had three questions.
The first was whether the consultancy work was exclusive — whether taking it on would require her to stop pursuing other options. I told her no. I didn't operate with exclusivity clauses at the early stage, and I had no interest in limiting someone's ability to function independently. That would defeat the purpose. She would be more useful, and more trustworthy, if she maintained her own agency.
She was quiet for a moment after that. Processing. Most people expect the answer to be yes — exclusivity is how insecure systems maintain control. The no landed with the weight of something unexpected.
The second question was about the information work. Not phrased that way — she said *the operational side of what you do* — but she'd been thinking since Thursday and had connected enough dots to understand that brand consulting wasn't the whole picture. I confirmed it without giving her specifics. I told her some of what I worked on involved information with restricted access, that the methodology was careful, and that I hadn't been arrested.
That last part made her laugh. Short, dry. The kind of laugh that isn't amused so much as recognizing something accurate.
"That's a low bar," she said.
"In the current city, it's not," I said.
The third question was simpler: what would she actually be doing.
I told her the truth in the frame she could receive it. She'd be providing field presence for jobs where I needed someone with hero-level conditioning, field experience, and operational flexibility. There might be elements involving her Quirk. All of it would be structured in advance. She would know the parameters before committing to any job.
"You keep using that word," she said.
"Which one?"
"Structured."
"I find that chaos is expensive," I said. "Structure is cheaper." Even though chaos is universal and no structure can ever be enough.
Another pause. Longer.
"Okay," she said. "I want a face-to-face before I commit to anything."
"Same café. Tuesday, eleven o'clock."
"Why do you always pick the location?"
"Because I've already assessed it," I said. "It saves time."
She didn't push back on that. Just said Tuesday was fine and ended the call.
I'm kinda bored with this process but i have to be cautious since I'm actually recruiting hero.
I sat with the phone for a moment after she hung up and looked at the financial ledger still spread across the table.
She'd called. She'd asked operational questions rather than personal ones — that meant she'd already moved past evaluating me as a person and was now evaluating the work. That was the correct sequence. Personal trust was a slow variable and an unreliable one. Professional trust built faster and held up better under pressure because it was grounded in demonstrated results rather than feeling.
I made a note in the ledger margin: *C. — second contact confirmed. Tuesday. Advance to operational discussion.*
Then I went back to the cost review.
The numbers needed finishing. Camie was a developing line item. She didn't belong in the ledger yet.
Tuesday.
I arrived fourteen minutes early this time
I ordered coffee. I opened the notebook. Wrote the session objectives in the margin of a clean page.
*1. Establish what she wants from this. Real version.*
*2. Demonstrate that structured work is in her interest, not just mine.*
*3. Do not over-explain. Let her fill the space.*
The third point was the hardest. I had a tendency, in meetings where stakes were medium-high, to over-fill silence with information because information felt like control. It wasn't. Silence gave the other person room to show me what they were actually thinking, which was worth more than anything I could tell them.
I closed the notebook when she walked in.
Same punctuality. Different jacket again — she changed her presentation each time, which might have been habit or might have been deliberate. Either way it told me she was paying attention to how she appeared. Not vanity. Something more functional than that. Like someone who'd learned that appearance was a variable worth managing.
We ordered. She wrapped both hands around her mug. Not cold — the café was warm enough. A grounding gesture. She was about to say something real.
"I looked into Meridian Creative," she said.
"And?"
"The address is real. The registry is clean. There's almost no online presence." She looked at me steadily. "Which is either very good operational security or a very thin cover."
"It's both," I said. "The cover needs to hold at a surface check. It doesn't need to hold at depth because nobody with the resources to go deeper has a reason to look. Yet."
"Yet," she repeated.
"I plan to be more visible eventually. Right now, low profile serves the work better."
She nodded slowly. "You planned this whole thing from underground corridors."
"I planned the structure. The specifics develop as resources develop."
"That's a patient way to operate."
"Patience isn't a virtue," I said. "It's a calculation. Acting before the conditions are right costs more than waiting."
She studied me for a moment. That assessing look, the one that had nothing behind it except attention.
"You really do think about everything in terms of cost," she said.
"Yes."
"Does that ever get exhausting?"
The question was genuine. Not a challenge — she was actually curious. I looked at it honestly before answering.
"Sometimes," I said. "But the alternative is making decisions on the basis of how I feel, and I've found that to be significantly more expensive in the long run."
Something shifted in her expression. Not sympathy. More like recognition — the particular look of someone who has arrived at a similar place by a different route.
"What happened?" she asked.
"Several things. Over several years." I met her eyes. "What happened to you?"
That was the pivot.
She hadn't expected me to redirect it. Most people ask a personal question because they want to give the answer — they're using the question as a door. I'd held the door open and stepped aside.
She was quiet for a moment. Then she talked.
Not everything. She wasn't ready for everything, and I wasn't asking for it. But she talked about the war's end — the way things had restructured around her before she'd had time to decide what she wanted the restructuring to look like. She talked about the agency she'd been with disbanding in the reorganization. About taking the relief corridor jobs because the work was real and everything else felt like it was made of paper. About having a Quirk that was genuinely useful and a skill set built over years and no infrastructure that was worth what it cost to maintain.
She didn't say *I'm stuck.* But that was the shape of it.
I listened without moving. Didn't nod excessively. Didn't offer the listening sounds that people use to signal sympathy — the small affirmations that feel supportive but actually interrupt the other person's thread. I just let her talk until she was done.
When she finished I said: "The infrastructure problem is solvable."
"By working with you."
"By building something that functions," I said. "I happen to be building it. That's a coincidence of timing, not a sales pitch."
She almost smiled. "You really hate pitching."
"I hate things that don't work," I said. "A pitch works on people who want to be sold something. You don't want to be sold something. You want a reason."
"And you're offering a reason."
"I'm offering the reality," I said. "The reason is yours to make."
I used the Quirk once during the conversation.
She'd been describing the corridor job — the same one from Thursday, but in more detail now, the texture of it rather than the outline. There was a moment where she talked about the moment the route coordinator's information proved false and she'd had to recalculate mid-operation, alone, with no support structure.
I felt the shape of what she needed to feel in that story. Not validation — she wasn't looking for praise. She needed to feel that the competence she'd demonstrated in that moment was *seen* as competence, not as improvisation. There's a difference. Improvisation is reactive. Competence is structural — it's what allows effective response when conditions break.
I guided her attention, below the surface, toward the words I'd already chosen: *that's not improvisation. That's what operational judgment looks like when the system underneath it holds.*
Then I said it out loud.
She looked at me.
"How did you—" She stopped. Started again. "That's exactly what it felt like. From the inside."
"I know what field judgment looks like," I said simply. "I've needed it."
She held my eyes for a moment too long for professional distance. Then looked down at her coffee.
The redirect had done what it needed to do. The spoken version confirmed it. She hadn't felt manipulated — she'd felt understood.
That was the distinction I kept returning to in my own notes on Quirk application. The difference between making someone feel something false and helping them recognize something true. The ethics of it were not clean. I knew that. I didn't pretend otherwise when I was alone with the notebook. But I kept the rule: never manufacture a feeling that has no grounding in reality. Only guide attention to what's already there.
She'd genuinely felt that her judgment had held. I'd only helped her locate it.
---
We stayed another hour.
By the end we'd covered: the kind of jobs I was currently working, the payment split structure I used with field assets, the protocol for pre-job briefings, and what I expected from someone operating on-site when something unplanned happened.
That last point she pushed back on.
"You want the person on-site to have final judgment," she said. "But you're clearly someone who likes control."
"I like correct decisions," I said. "The person with the most accurate information at the moment of decision is the person on-site. Overriding them from the outside introduces lag and degrades outcome quality. My wanting control doesn't change the logic."
She turned that over. "That's either very rational or a very elegant way to avoid responsibility."
"It's both," I said. "The outcome quality still lands on my ledger. I'm not avoiding responsibility. I'm distributing decision authority correctly."
She was quiet. Then: "I want to try one job. Low-stakes. See how the structure actually works before I commit to anything ongoing."
"That's the correct approach," I said. "I'd think less of the decision if you'd agreed without it."
"You'd think less of me."
"I'd think the decision was based on something other than judgment," I said. "Which would tell me something I'd have to factor in going forward."
She looked at me for a long moment.
"You're strange," she said. It wasn't unkind.
Outside, she paused on the pavement again. Same spot as Thursday. Like she processed things better when her feet were still.
"The trial job," she said. "When?"
"I'll have something in the next two weeks. Low operational complexity, controlled environment, clear parameters. I'll contact you through the same number."
"Okay." She shifted her weight slightly. "Can I ask you something that's not about the work?"
I waited.
"Do you have anyone?" she said
The question was unexpected enough that I didn't answer for a full two seconds. That was long for me.
"I have functional relationships," I said finally.
"That's not what I asked."
"I know," I said.
She looked at me. Didn't push it. Nodded once and said she'd wait to hear about the job.
I watched her walk away.
This time she was a full block gone before I turned and started back toward the underground.
I walked for eleven minutes before I realized I'd been thinking about her question instead of the operational summary.
I stopped in the middle of the street. Noted the drift. Filed it as irrelevant.
Then I walked home and wrote up the meeting notes.
*Asset status: conditionally engaged. Trial job required. Trust trajectory: developing. Risk level: low.*
I closed the notebook.
The question was still there, sitting in a corner of my processing where I hadn't told it to go.
I let it stay. For now. Then I turned off the light..
Visit My Patreon and read upto 10+ Advanced chapters in advance to support the story
My Pat reon:ht tps://patreon.com/eyestapler
Thanks for reading
