[Gardner Analytics Office, SoMa — Late March 2014, 2:23 PM]
Marcus had been on the job for three days and was already reorganizing the codebase. Not rewriting it — the code was sound — but restructuring the repository with the meticulous file organization of someone who'd spent two years in IT support and knew that chaos at the infrastructure level compounded into catastrophe at the application level. He'd created documentation directories, build scripts, and a testing framework that Sarah declared "annoyingly thorough."
Ethan was at his desk reviewing training configurations for the scaled model when his phone rang. Monica's name on the screen. He picked up.
"We have a problem." Her voice carried the particular tension of someone delivering bad news in a professional context — controlled, precise, devoid of the warmth that had characterized their last few conversations. "Can you come to our offices? This afternoon."
"What kind of problem?"
"Due diligence. Our analyst flagged something in your financials. I need you here to address it before it escalates."
"Flagged what?"
A pause. Monica's pauses were never empty — they were edited silences, the conversational equivalent of choosing which sentence to publish and which to cut.
"ChronoCloud," she said.
The word dropped through Ethan's chest like a stone through still water. He gripped the phone tighter. Across the office, Sarah glanced up from her monitor — she could read his body language after two months of proximity, and whatever she read made her stop typing.
"I'll be there in an hour."
"Make it forty minutes."
She hung up. Ethan set the phone face-down on the desk and stared at the whiteboard across the room. The Transformer architecture diagram was still drawn there in three colors — blue, red, green — from the marathon coding sessions with Sarah. Behind it, invisible to everyone in the room, the architecture lived in his mind with a clarity that had been sharpening since the first training run's success. The layers were crisper now, the attention heads more defined, the data flow visible at resolutions that would have blurred into static two months ago. Phase 2 was approaching — he could feel it at the edges, a shift in mental resolution like a camera lens finding focus.
None of which mattered if Raviga pulled the funding.
"What happened?" Sarah asked.
"Due diligence. They found ChronoCloud."
Sarah's expression flatlined — the particular blankness she wore when processing a threat. She'd been asking about ChronoCloud since the day she joined. She knew it was the weakest point in the story, the thread that, if pulled, would unravel everything. "How much did they find?"
"Don't know yet. I need to go to Palo Alto."
"What are you going to tell them?"
"Whatever keeps the money flowing."
He grabbed the North Face jacket and the messenger bag — the strap was down to its last few braided fibers, a physical metaphor for the thinning margin between his cover story and exposure. The Honda Civic started on the third try, the engine complaining about the cold before catching. The gas gauge showed half a tank — a luxury he'd stopped thinking about since the funding arrived.
---
[Raviga Capital, Conference Room B — 3:05 PM]
The analyst's name was Kevin Torres. Late twenties, wire-rimmed glasses, the particular posture of a junior employee who'd found something his superiors hadn't and was vibrating with the combined energy of vindication and terror. He sat at the conference table with a laptop open to a spreadsheet, a stack of printed invoices, and the expression of a bloodhound that had treed its quarry.
Monica sat across from him. Linda Chao occupied the head of the table, her MIT ring catching the light as she folded her hands.
"Mr. Gardner," Linda said. "Thank you for coming on short notice. Kevin has raised some questions about your cloud infrastructure expenses that we'd like to address before we finalize the quarterly reporting framework."
Ethan sat down. The chair was leather, comfortable, designed for meetings that lasted hours. He didn't plan to be in it that long.
"What are the questions?"
Kevin adjusted his glasses and turned his laptop screen toward the table. "I've been reviewing the financial records submitted as part of the due diligence package. Specifically, the cloud computing invoices. You're using a provider called ChronoCloud for your GPU training runs."
"That's correct."
"ChronoCloud doesn't appear in any cloud provider registry — AWS, Azure, Google Cloud, IBM, Rackspace, none of them. It's not listed on any industry directory. The company has no website, no public-facing documentation, no LinkedIn presence, and no record of incorporation in any state or country that I've been able to identify."
Kevin paused. The silence in the conference room was the kind that existed in courtrooms and operating theaters — weighted, expectant, calibrated for consequence.
"Additionally," Kevin continued, "the hardware specifications listed on your invoices describe GPU models that don't correspond to any commercially available product. 'V100-equivalent' — there is no V100. NVIDIA's current flagship is the K80, released last November. The specifications on your invoices suggest hardware performance metrics approximately five to seven times faster than anything on the market."
Another pause. Kevin's eyes were bright behind the wire-rimmed glasses. He'd done his homework.
"My assessment is that either your cloud provider is fraudulently billing you for hardware that doesn't exist, or the invoices have been fabricated to inflate reported expenses. Either scenario represents a material concern for the partnership."
Linda looked at Ethan. Monica looked at the table.
The room waited.
Ethan had rehearsed versions of this conversation since the day he'd first logged into ChronoCloud's interface. The excuse had to be plausible, technical, and boring enough that non-engineers would stop asking questions while being sophisticated enough that engineers like Kevin wouldn't immediately spot holes.
"ChronoCloud is a proprietary research partnership," Ethan said. "They're a hardware R&D firm — not a commercial cloud provider. They develop experimental GPU architectures for academic and private research partnerships under NDA. The hardware specifications on the invoices reflect pre-release silicon that isn't publicly available."
"Which hardware firm?"
"I can't disclose that under the terms of our agreement."
"An NDA that prevents you from naming your cloud provider is unusual."
"The hardware is experimental. Pre-release. Their competitive advantage depends on secrecy. Companies like NVIDIA and AMD would reverse-engineer their architecture within months of disclosure."
Kevin's fingers drummed on the table edge. "I'd like to verify the NDA."
"The NDA itself is confidential."
A dangerous moment. Kevin's skepticism was hardening into something less polite. Linda's expression was neutral but attentive — she was evaluating not just the answer but the way it was being delivered. The body language. The steadiness of voice. The tells.
Monica spoke for the first time. "I've seen the training results produced on this hardware. Whatever the source, the output is real. The model generates text at a quality level that's inconsistent with anything achievable on currently available commercial GPUs. The hardware performance is genuine."
"That's not what I'm questioning," Kevin said. "I'm questioning the provenance—"
"Kevin." Linda's voice was quiet but final — the tone of a senior partner who'd decided the conversation had reached its productive limit. "The technology demonstration we reviewed during the partner meeting was conducted on this hardware. The output quality is not in dispute. The question is whether the cloud infrastructure arrangement represents a material risk to the investment."
She looked at Ethan. "Does it?"
"No. The partnership is stable. The billing is transparent. The hardware performs as specified."
"Can you provide documentation of the NDA's existence — redacted if necessary — for our files?"
Ethan's mind raced. A redacted NDA. He'd need to fabricate one — or find a way to produce documentation for an agreement that didn't exist with a company that operated outside the normal parameters of time and commerce. Sarah could help. A convincing legal template, properly formatted, with enough redaction to be plausible and enough content to satisfy a filing requirement.
"I can provide a redacted version within the week."
Linda nodded. Turned to Kevin. "File the concern. Note the CEO's response and the pending documentation. We'll revisit if the redacted NDA raises additional questions."
Kevin's expression said he wasn't satisfied. But Kevin was an analyst, and Linda was a partner, and in the hierarchy of Raviga Capital, partners overruled analysts the way gravity overruled opinion.
The meeting ended. Handshakes. Kevin gathered his printouts with the careful precision of someone who planned to keep looking. Linda left first. Monica walked Ethan to the elevator.
In the hallway, outside the conference room's glass walls, she turned to him. Her coffee cup — she'd been holding it through the entire meeting without drinking — trembled slightly in her grip. The tremor was small. Visible only because Ethan was looking for it.
"That was close," she said.
"I know."
"I vouched for you in that room. Again. My credibility is directly linked to your company now. If that NDA doesn't exist—"
"I'll provide the document."
"Ethan." She set the coffee cup on a side table. Freed both hands. "I have a pattern file. You know this. The file gets thicker every week. Today's entry is going to be substantial."
"Monica—"
"I'm not asking for an explanation. Not today. I'm telling you that Kevin Torres is going to keep looking, and eventually he's going to find something that a partner meeting can't dismiss. Be ready for that."
The elevator arrived. Ethan stepped in. Monica stayed in the hallway, framed by the closing doors, her coffee still sitting on the side table, growing cold.
Author's Note / Promotion: Your Reviews and Power Stones are the best way to show support. They help me know what you're enjoying and bring in new readers! You don't have to. Get instant access to more content by supporting me on Patreon. I have three options so you can pick how far ahead you want to be: 🪙 Silver Tier ($6): Read 10 chapters ahead of the public site. 👑 Gold Tier ($9): Get 15-20 chapters ahead of the public site. 💎 Platinum Tier ($15): The ultimate experience. Get new chapters the second I finish them . No waiting for weekly drops, just pure, instant access. Your support helps me write more . 👉 Find it all at patreon.com/fanficwriter1