The six-week restriction ended on a Tuesday.
I didn't celebrate that. I noted it, confirmed the intercostal mobility had returned to functional range by testing it against the wall of the corridor — deliberate lateral compression, measuring where discomfort became pain and where pain became the structural kind — and updated the training schedule accordingly.
The boxing trainer didn't comment on my return to full sessions. He adjusted the program without being asked, starting me at seventy percent load and building from there. That professionalism was one of the reasons I'd chosen his gym over the three alternatives I'd originally mapped. He treated bodies the way I tried to treat systems — as things with operational parameters rather than things with feelings about those parameters.
I ran forty minutes on footwork and combinations. My cardio baseline had dropped. Three weeks of modified sessions and two weeks of near-complete inactivity had cost me conditioning I'd spent four months building. I noted the gap without frustration, because frustration didn't accelerate recovery, and rebuilt the numbers into the weekly schedule.
The man from the far corner was there.
Thursday schedule, I'd confirmed. It was Tuesday. That was new information — he'd added a session, or rotated his schedule, or the front desk contact had given me incomplete data. Any of those was possible. I updated the observation log in my head and kept working.
He didn't look at me. That was consistent with the previous sessions. He arrived, worked, and left without investing social energy in the room around him. That kind of trained inward focus had two common sources: professional discipline or personal habit shaped by an environment where awareness was survival. The two weren't mutually exclusive.
I filed it and kept moving.
The Meridian buyer's secondary representative had been patient.
Camie had managed the relationship through three check-in exchanges during my recovery period — nothing committal, nothing that advanced the job parameters, but enough contact to maintain signal without transmitting vulnerability. When she reported it to me during our first post-recovery operational meeting, she described her approach in terms of emotional temperature management, which was her language for what I would have called relationship maintenance under adverse conditions.
The description was less precise than I preferred. The execution had been correct.
"He's still interested," she said. "Maybe more interested, actually. The delay read as selective rather than unavailable."
"That's a functional outcome."
"I know it is." She paused. "I'm telling you because it was a judgment call I made without checking in. I want you to know I made it."
I looked at her across the table. The café was the second one we'd used — different district, same structural logic, corner seating with sightlines to both entrances and the service corridor.
Camie had developed a pattern I'd been watching develop since the coordination office job. She was becoming more operationally fluent. Not just executing tasks with the competence she'd shown from the start, but anticipating the framework logic behind the tasks and applying it to decisions I hadn't specified in advance.
That was valuable. It was also a shift in the dynamic I needed to track carefully.
An asset who understood the system could operate it. An asset who understood the system could also interrogate it.
"The call was correct," I said. "Log it in your contact record with the reasoning. I'll review the tone choices before the next meeting."
She nodded. Then, after a beat: "How are your ribs?"
"Functional."
"That's not what I asked."
I met her eyes. Camie had a specific quality when she asked personal questions — not intrusive, not warm exactly, more like someone checking a structural reading on something they cared about the stability of. It was different from social inquiry. It was almost operational.
"Recovered within normal parameters," I said.
The corner of her mouth moved. "That's still not what I asked."
"It's what I have."
She accepted that without pushing, which was one of the other reasons she was useful. She understood when a door was closed without needing it explained.
The Meridian buyer's new request came through his secondary representative four days later.
It wasn't a job request. It was a capability inquiry.
The specific phrasing, as Camie relayed it: *Does your operation have the capacity to access personnel files held within the Hero Public Safety Commission's municipal archive division?*
I read the relay note three times. Then I set it down and looked at the ceiling of the corridor for approximately two minutes.
The HPSC municipal archive division was not a coordination office. It was not a records department staffed by clerks operating on routine schedules with predictable shift patterns. It was a government institution with security tiering, access logging, credentialed entry requirements, and, in all likelihood, on-site hero or security Quirk presence.
The gap between what we'd done before and what this required wasn't incremental.
It was categorical.
The correct answer, from a pure risk-management standpoint, was no. We were not resourced for that target. The exposure-to-payout ratio hadn't been established, the access architecture didn't exist, and attempting to build it under a buyer's timeline rather than my own was exactly the kind of inverted priority structure that produced failures.
I knew what the correct answer was.
I also knew that the Meridian buyer wasn't asking out of casual curiosity. He was mapping our capability ceiling. The inquiry itself was a test of operational ambition, and the response I gave would determine whether he escalated the relationship or maintained us at the current tier.
I sat with that for the rest of the evening.
The next morning I ran the environmental control framework against the HPSC scenario for the first time.
Not as a plan. As an exercise. I wanted to see what the new framework produced when applied to a hard target, independent of whether we'd ever actually run the job.
The archive division's public-facing access points were documented. Municipal records, credentialing offices, public inquiry windows. Staff entry points were partially inferable from building permit filings and the district consolidation announcement that had been published eight months ago. I'd never mapped the building specifically, but I'd walked past it twice on unrelated routes and noted the basic structural layout from the outside.
The new framework asked a different set of questions than the old one.
Old framework: who is the target, when are they accessible, what information do they have.
New framework: what environment can I construct, who moves through it naturally, what stimulus conditions make the channel clean.
The HPSC building had a public-facing inquiry window. People moved through it with legitimate purpose. The staff who handled that window weren't senior archivists — they were mid-level administrative processors, the same category of person I'd successfully worked with in the coordination office jobs. Their access was partial, but partial access to a high-tier archive was categorically different from full access to a low-tier one.
The channel question: those administrative processors worked in a specific kind of cognitive environment. Repetitive, moderately boring, low autonomy, high procedural load. That was a clean channel. Low noise. Moderate fatigue. Exactly the conditions the revised model said were favorable.
I kept working through it.
By midday I had seven pages of preliminary architecture, none of it confirmed, all of it framed as hypothesis rather than plan.
At the bottom of the seventh page I wrote: *Not yet. But not impossible.*
That was the most forward-looking thing I'd written in six weeks.
I went back to the gym on Thursday.
He was there.
I'd spent the intervening days deciding how to open the observation into something more active. The challenge with a potential buffer asset was that the recruitment logic was inverted compared to normal asset development. With Toga, the leverage had been mutual — she had needs I could structure, I had resources she could use. With Camie, there had been a clear professional value proposition I could articulate in terms she'd recognize.
This man, whoever he was, I knew almost nothing about. I had a movement profile and a schedule pattern and a general read on his background from body language alone. That wasn't enough to build a recruitment approach. It was barely enough to justify continued observation.
Which meant the next step was information acquisition, not contact.
I approached the front desk after my session, towel over my shoulder, manufactured mild frustration on my face.
"I thought I recognized someone in there," I said to the attendant. "Used to work near my old district. Stocky guy, thirties, working the heavy bag in the corner — do you know his name? I don't want to bother him if I'm wrong."
It was the kind of request that was too mundane to be suspicious. People recognized people at gyms. It happened.
The attendant glanced toward the training floor. "Oh, that's Shiro. He's been a member here almost two years."
"Shiro," I repeated. "Doesn't ring a bell. Sorry, must be wrong."
I left with a first name and a two-year tenure.
Back in the corridor, I added it to the log.
*Shiro. Approx. 28–32. Two-year member. Movement profile: trained combatant, mixed background, non-sport orientation. Behavioral profile: inward focus, low social investment, no group affiliation observed. No Quirk activity observed during training sessions.*
That last point was interesting. Either his Quirk was passive, or he trained without it by habit or necessity, or he had no Quirk at all.
A person who trained without Quirk dependency in a post-War environment where Quirk use in self-defense had been progressively normalized was either principled, limited, or professional in a specific kind of way.
I didn't know which yet.
*Continue observation,* I wrote. *No contact until three more sessions minimum.*
Toga found me two days later at the secondary drop point — not for a job handoff, just presence, which was becoming a pattern I'd decided not to address directly because addressing it would make it more significant than it needed to be.
She sat against the wall and looked at the pages I had spread on the floor.
"New job?" she said.
"Architecture exercise."
"On what?"
I considered how much to share. Toga's operational information was compartmentalized by default — she knew what she needed for her current assignments and nothing about the broader structure unless withholding it created a risk I couldn't manage another way.
The HPSC scenario wasn't a current assignment. It wasn't even a confirmed job. But she was going to be part of whatever the next escalation looked like, which meant her read on it had some marginal utility.
"A harder target than we've run before," I said. "I'm mapping whether the framework scales."
She looked at the pages. Didn't touch them.
"Does it?"
"The architecture works conceptually. The access problem is the constraint."
She was quiet for a moment. Then: "You need someone on the inside."
"Ideally."
"Not me. I don't look right for that building."
"I know."
"Camie, maybe."
"Maybe." I paused. "There's a credentialing angle I haven't fully mapped."
Toga made a sound that wasn't quite agreement and wasn't quite disagreement. She was looking at the floor between us with the expression she had when she was working something through but didn't want to be seen working it through.
"What?" I said.
"Nothing yet." She stood up. "I'll tell you if it becomes something."
Toga Himiko knelt between my spread legs, her messy pink hair swinging as she bobbed her head with utter, sloppy abandon. Her mouth was stretched wide around the thick shaft, cheeks hollowed with desperate suction as drool spilled past her lips and dribbled down heavy balls.She gagged wetly around the base, throat convulsing, but didn't pull off—just kept swallowing, her nose buried in dark curls, breathing hard through her flared nostrils. The air reeked of musk and salt, her own arousal slick between her thighs where she'd shoved her skirt up, grinding against her own hand while she worked. Every time she lifted her head, a thick string of spit and pre-cum stretched from her chin to the swollen head before snapping back onto my stomach.
She finally pulled off with a loud, wet pop, gasping and grinning up with cum-smeared lips, tongue darting out to catch stray drops. "Mmm~ so tasty," she chirped, voice thick and breathless. She didn't waste time—immediately dove down again, sucking each heavy testicle into her mouth, laving them with her tongue like she was savoring candy. Her fingers dug intomt hips, nails biting in as she cleaned every ridge and vein with meticulous, hungry licks, saliva mixing with sweat and residual semen. Her eyes stayed locked upward, pupils blown wide with manic affection, cheeks flushed deep pink
But…
She left, which was characteristic. Toga processed things in private and reported conclusions rather than working through them aloud. It was a habit I understood and didn't push against.
I looked at the pages on the floor.
The framework was stress-testing well. The HPSC scenario was hard, but hard meant it required more architecture, not that the architecture was wrong. The buffer asset search was progressing at its own pace. Camie was operationally deepening in ways that increased the system's adaptive capacity even if they introduced dynamics that needed managing.
None of this was the system I'd had before Hando.
It was better. More honestly built. The failure had removed an assumption I couldn't afford to carry and replaced it with a question I was now actually working to answer.
I started a new page.
*HPSC — access architecture, phase one mapping.*
The forward momentum was quiet. It didn't announce itself. It didn't feel like anything in particular.
But it was there, in the same way a building is there once you've finished the load-bearing walls — not complete, not safe to occupy yet, but structurally present in a way that the open lot before it never was.
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