​Blown Context, Broken Code: The Real Bottleneck in AI Software Delivery

​A conversation on why more AI doesn't mean more output—and how to engineer the missing layer of the stack.

​Join CTOs, VPs and Engineering leaders for a private sit-down dinner at Osha Thai in San Francisco. We'll discuss one of the biggest challenges in modern software development: building reliable AI-powered engineering teams through better context engineering.

​About the Event

​AI coding tools produce plausible-looking code in seconds, and almost none of it knows your hidden dependencies, your team's conventions, or the business rules it's meant to serve. That gap is where the money goes: ballooning inference costs, fragile output, and code that quietly drifts from what the business asked for.

​The truth is AI is only as good as what it can see. Context—the live understanding of a system's architecture, dependencies, conventions, and recent changes—isn't a nice-to-have. It's the foundation under every correct decision an AI makes, and no model can save you when it's wrong.

​We're gathering builders, operators, and product leaders in San Francisco to skip the hype and talk honestly about the hardest problem in scaling AI-powered software: Context Engineering. Featuring a live walkthrough of Forge (softwareforge.ai), built on a simple premise—context isn't something you manage after the fact, it is the architecture.

​What We'll Cover

• ​The Attention Tax: Why overloading AI models with disorganized code degrades quality and triggers extreme token variance.

• ​Avoiding the Recontexting Tax: How starting every agent session from zero compounds into massive wasted spend across an org.

• ​Managing System Drift: Strategies to version-control business intent so evolving requirements don't break downstream code.

• ​The Context Blueprint: How to capture, structure, and preserve context through agent handoffs so no lifecycle step starts cold.

​What to Expect

• ​No Slides: Just high-signal, peer-to-peer technical problem solving.

• ​Come Prepared: Two tactical discussion questions sent in advance (takes 5 minutes).

• ​Chatham House Rules: What's said in the room stays in the room.

​Seats are strictly limited to maintain a high-signal room. Please register using your company email.