Chapter 4: What Tanner Doesn't Hide
The name on the complaint was Travis Tanner.
I sat in Document Review Room 3 with the filing spread across the table in front of me — seventy-two pages of aggressive litigation posturing wrapped in the formal language of a federal complaint. Day eleven at Pearson Hardman, and I was reading the work of someone the show had treated as Harvey's mirror: brilliant, ruthless, and fundamentally uninterested in playing fair.
The Ledger turned before I finished the first paragraph.
Synthesis. Ninety seconds.
Tanner's strategy assembled itself in my mind like a blueprint viewed from above. The complaint wasn't about winning at trial — Tanner never intended to reach trial. His filing structure was designed for a specific purpose: discovery overload. He'd crafted the allegations to require extensive document production, buried the actual legal argument beneath procedural requirements, and structured his requests to maximize the time and cost required to respond. The goal was settlement. Exhaust the defense team, drive up costs, extract a number before the real fight started.
[CASE FILE OMNISCIENCE: Tanner v. Kerrigan Industries — TACTICAL SYNTHESIS COMPLETE]
[WARNING: Two facts in synthesis may reflect user interpretation bias. External verification recommended.]
The corruption flags appeared in my awareness like asterisks on a document I couldn't quite read. Two facts wrong. I scanned the synthesis, looking for the weak points — and found them, I thought, in two inconsistencies within Tanner's own filing. A paragraph reference that didn't quite match the exhibit tab. A timeline detail that contradicted an earlier claim.
"His errors," I told myself. "Not mine."
I pulled out my legal pad and started writing. The synthesis was solid. Tanner's playbook was visible in every structural choice he'd made — the discovery requests, the interrogatory categories, the document production demands. He was good. He was also predictable, if you knew where to look.
The Ledger settled. Ninety seconds, complete. I kept writing.
Gregory found me at 4:30 PM.
"Calder. Tanner memo. Two pages. My desk by six."
He was gone before I could respond, already moving to his next task. I looked at my legal pad — twelve pages of notes, cross-references, tactical observations. Two pages would require compression.
I started writing.
The memo took shape quickly. Tanner's discovery strategy, summarized. His preference for volume over precision, identified. The timeline pressure he was attempting to create, mapped. I kept the language clinical — no recommendations, no suggestions for response, just the pattern as I'd read it.
Two pages. Single-spaced. Routed to Gregory's inbox at 5:47 PM.
I went back to the document review room and kept reading.
Day twelve. The response came at 9:15 AM.
Not from Gregory. From Harvey's assistant — Donna — via the firm's internal messaging system. A calendar invite: Tanner Response Team, Strategy Meeting, Conference Room A, 2:00 PM. Attendees: Harvey Specter, Gregory Sloane, two senior associates I didn't recognize, and at the bottom of the list, Ethan Calder.
I stared at the invite for three seconds.
Harvey had read the memo. Harvey had made no comment on the memo. Harvey had not thanked me for the memo or acknowledged that it contained anything useful.
What Harvey had done was put my name on the Tanner team email chain.
I'd watched enough of the show to understand the grammar. Harvey didn't praise associates verbally — he deployed them. If you were useful, you stayed in the rotation. If you weren't, you disappeared back into the associate pool and never heard from him again.
The calendar invite was, in Harvey's language, approval.
[SOCIAL PATTERN RECOGNITION: Harvey Specter — approval registered through assignment, not acknowledgment]
I closed the system message without dwelling on it. The meeting was in four hours. I had work to do.
The Tanner team meeting lasted ninety-three minutes. Harvey dominated the room — he always would, that was the point — but his attention moved across the participants with the precision of someone who was constantly evaluating talent.
I spoke twice. Both times in response to direct questions about the discovery timeline. Both times with information drawn directly from my synthesis, stripped of context that would make the source suspicious.
Harvey's eyes landed on me briefly after the second response. The assessment was quick and clinical: useful tool, continue deployment.
I noted this and filed it. The Ledger pressed against my sternum, recording something I couldn't read.
The human moment came at lunch.
I was eating at my desk — a sandwich from the deli two blocks east, purchased during the fifteen-minute window between the team meeting and the next document review session — with the Tanner file open in front of me. The complaint. The discovery requests. The timeline demands.
I took a bite of the sandwich and realized I was interested.
Not in the system's read. Not in the tactical advantage Omniscience provided. I was interested in Tanner himself — in the specific architecture of his strategy, in the way his intelligence shaped his approach to litigation. He was an adversary worth respecting, even as I worked to dismantle him.
"This is what it's supposed to feel like," I thought. "The work itself. Not the meta-knowledge. Not the Ledger. The actual practice of law."
The sandwich was good. The puzzle was better. I kept reading.
Territory Claim 1 sent a faint signal at 4:00 PM.
Not a crisis — a billing question, minor, the kind of thing that surfaced when clients reviewed their monthly statements. Warren Folcroft had noticed an inconsistency between projected and actual hours on a subsidiary matter.
I felt the signal as a pull on my attention, a gentle redirection of focus that I couldn't quite ignore. The Territory Claim had registered Folcroft's concern before I received the formal inquiry, and the sensation was strange — like remembering something I hadn't been told yet.
I handled it in the footnotes. A clarifying memo, three paragraphs, explaining the variance and projecting adjusted costs. The kind of client service that nobody tracked but everyone appreciated.
The signal faded. Folcroft's concern was resolved. I went back to Tanner.
Day twelve ended with an email.
Harvey's name appeared above mine on the Tanner team thread, which was the correct order. Senior partner, then associates, in descending hierarchy. Nothing unusual about that.
The question was how long the order stayed correct.
I closed my laptop and gathered my things. The Ledger pressed against my sternum — synthesis residue, Exposure Debt at baseline, Territory Claim humming at the edge of attention. Four Omniscience activations in twelve days. Eight corrupted facts accepted, location unknown.
"External verification recommended."
I'd verify tomorrow. I always told myself I'd verify tomorrow.
The elevator carried me down to the lobby, and I walked into the Manhattan evening with Tanner's strategy mapped in my mind and Harvey's approval logged in my professional account. The trajectory was correct. The order was holding.
The question was whether the order would hold when the corrupted facts surfaced.
Get Early Access to New Chapters
Thank you for reading. For those who want to skip the wait, my Patreon is currently 21 chapters ahead of the public sites.
Schedule: 7 new chapters released every 10 days.
Benefit: Gain a significant lead of 7 to 21 chapters depending on your tier.
Support the project and start reading the next arc now: Patreon.com/IsekaiStories