How to Change an LLM System Without Guessing
Picture: Web Directions

Conference In 6 weeks

December
Monday
to Tue 8 December 2026 · Sydney time

How to Change an LLM System Without Guessing

Where
AI Engineering room 488 George Street, 2000, Sydney
Host
Web Directions
Entry
Not stated
Sign-up
On the host's page
Open on webdirections.org

All Sydney events

You sign up with the host. foundercal only links to it.

Who you meetThe people on the listing, and what the host tells us about the room.

  • Yulia Kuchina Speaker
Investors Not stated The listing does not say
The format Talks and halls Conference
Sign-up On the host's page Price not stated

AboutIn the host's words.

Speakers: Yulia Kuchina (Software at Scale)

Track: AI Engineering

We were running a production LLM pipeline that classified legal documents, and every change was a guess. Swap a prompt, change a model — better or worse? Nobody could say. The outputs looked plausible either way, and “plausible” is exactly how LLM systems hide their regressions.

This talk is how we went from operating on faith to changing the system on evidence — a systems story, not a model story. The layer, built in order: prompt fingerprinting so every output traces to the exact prompt and model; provenance on every document record; failure visibility so classification failures surface as data, not silence; and an evaluation harness wired into CI, scoring every change against a labelled baseline — report-only today, becoming a blocking gate once the corpus supports a threshold we trust. The corpus is the honest bottleneck — a starving eval set can’t gate anything — so we’re building a pipeline that mints eval fixtures from real production failures without PII ever entering git: labels in version control, documents in an erasable store inside the production boundary.

The trade-offs, honestly: why we grounded extraction in document citations the model has to resolve — fabricated evidence fails to resolve instead of producing a false highlight — why a lawyer’s override is becoming first-class state the system can re-check, and the decisions I’d make differently. I’ll show a regression the harness surfaced before it shipped, and a defect that sailed past every automated check: a legally-wrong output that was mechanically correct, in a dimension none of our instruments measured — where human judgment takes over.

The takeaway: the reliability of an AI feature lives in the harness around the model, not the model. Prompts, parsers, evals, telemetry, and release gates are one system — once you can measure it, you stop guessing.

https://data.webdirections.org/ai-engineer-sydney/sessions.json#2e791cc0-f381-41bb-b389-a55e1e5f0e21

Full text on webdirections.org .

Where

AI Engineering room

488 George Street, 2000, Sydney

Open in Maps ↗

Same week in Sydney All 139 events

Dec
to 5 Dec
Hackathon

AI Engineer Hackathon

Founders pitch

Web Directions Free
Dec
to 13 Dec
Conference

AI Week

Web Directions
Dec
to 12 Dec
Conference

NeurIPS 2026

One of the year's big ones

NeurIPS Foundation
Dec
to 8 Dec
Meetup

Lessons from Economics for the Human / Agent Software Workforce

Leadership room
Web Directions
Dec
to 8 Dec
Meetup

Ontologies

AI Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Shipping together in an AI native team

Software Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Dependency hell is back. This time it's your agent's config.

Software Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Your website is a terrible API

AI Engineering room
Web Directions
Dec
to 8 Dec
Meetup

Sovereignty Is an Inference Problem

Leadership room
Web Directions
Dec
to 8 Dec
Meetup

My Agents broke APIs

AI Engineering room
Web Directions
Open on webdirections.org Mon 7 Dec ↗