BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//LatentShift//latentshift.ai schedule//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:LatentShift · Run the Dark Code: Why Your Agent's Error Handl
 ing Has Never Executed - and How to Run It on Purpose
X-WR-TIMEZONE:Europe/Istanbul
REFRESH-INTERVAL;VALUE=DURATION:PT12H
X-PUBLISHED-TTL:PT12H
BEGIN:VEVENT
UID:ed01-run-the-dark-code@latentshift.ai
DTSTAMP:20261007T125617Z
DTSTART:20261017T090500Z
DTEND:20261017T092500Z
SUMMARY:LatentShift · Run the Dark Code: Why Your Agent's Error Handling H
 as Never Executed - and How to Run It on Purpose · Cenk Kalpakoglu
DESCRIPTION:Short talk · 20 min · English\n\nCenk Kalpakoglu · Vice Pres
 ident\, AI R&D\, Invicti\n\nYour agent chains LLM calls\, tool subprocesse
 s\, RAG lookups\, and HTTP requests. You wrote error handling for every li
 nk in that chain: the retry after a 429\, the cleanup when a tool gets kil
 led\, the fallback when your vector DB returns garbage. This talk's thesis
  is uncomfortably simple: you wrote that code\, but you've never seen it r
 un\, and none of your current testing tools can run it.\n\nWhy? Because ag
 ent failures don't live at a single layer. An SSE response that cuts off m
 id-token lives in HTTP semantics. A tool subprocess that gets OOM-killed l
 ives at the stdio layer. An ENOSPC lives at the syscall layer. Unit tests 
 test the mock. Kubernetes-level chaos tools inject at the wrong layer enti
 rely. Agent failures live at the SDK/API boundary\, and that's exactly whe
 re fault injection has to happen.\n\nI'll demonstrate this live with two m
 echanisms: an HTTPS proxy with a per-run ephemeral CA that synthesizes ven
 dor-accurate 429s and stream truncations over a real TLS connection\, so t
 he SDK sees exactly what production would send it\, and eBPF kprobes that 
 rewrite syscall returns in the kernel\, so the target gets a real ECONNRES
 ET\, not a simulated one. The tool is open source (faultkit)\, but this is
  a methods talk\, not a tool pitch. In the live demo\, we inject the llm-a
 pi-degraded scenario into a real agent test suite and find two red tests t
 hat didn't exist yesterday: two production incidents that won't exist tomo
 rrow.\n\nBonus lesson: a resilience test that passes green without firing 
 a fault is more dangerous than one that fails red. That's the story of exi
 t code 3.\n\nOne memorable takeaway:\n\n"Your error paths are code too. Do
 n't let production be the first place they run! Run them on purpose\, toda
 y."\n\nhttps://latentshift.ai/schedule/run-the-dark-code/
LOCATION:Bağlarbaşı Kongre ve Kültür Merkezi\, Boğaziçi Salonu\, Sel
 ami Ali Mah.\, Gazi Cad. No:22\, 34664 Üsküdar\, İstanbul
GEO:41.024366;29.033571
URL:https://latentshift.ai/schedule/run-the-dark-code/
CATEGORIES:LatentShift,Short talk
STATUS:CONFIRMED
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER:-PT10M
DESCRIPTION:Starts in 10 minutes · Run the Dark Code: Why Your Agent's Err
 or Handling Has Never Executed - and How to Run It on Purpose
END:VALARM
END:VEVENT
END:VCALENDAR