AI Engineer · Event date June 29, 2026 - July 2, 2026

AI Engineer World's Fair - JUNE 29 - JULY 2, 2026 • SAN FRANCISCO, CA

Why it matters
June 29, 2026 - July 2, 2026
Event archive

AI Engineer runs the most viewed technical conferences in AI for engineers, with over 10M+ views of our talks online. We are back in SF for the 4th year in a row! This is the one place you can meet with every major frontier lab, leading AI clouds, and AI native/transformed companies — from disruptive AI startups to Fortune 500 AI leaders, and every notable building block in the LLM OS ecosystem.

My takeaway: AI Engineer World's Fair - JUNE 29 - JULY 2, 2026 • SAN FRANCISCO, CA is an event signal. The practical read is to track where researchers, vendors, and operators are putting attention before those themes become standard enterprise guidance.
Keep exploring

More curated notes connected through AI Engineering and Model Evaluation.

OpenAI News · framework

OpenAI’s Frontier Governance Framework

OpenAI's 22-page Frontier Governance Framework maps its frontier-model processes to California's Transparency in Frontier AI Act and the EU AI Act's general-purpose AI code. It documents lifecycle risk assessment, cyber-offense and other risk tiers, mitigation and residual-risk decisions, critical-incident handling, security risk management, model reporting, external review, responsibility allocation, and change control.

OWASP GenAI Security Project · guide

OWASP Top 10 for Agentic Applications for 2026

OWASP's community guide organizes agentic-system risk into ten categories, including goal hijacking, tool misuse, identity and privilege abuse, memory poisoning, insecure inter-agent communication, cascading failures, and rogue-agent behavior. It provides a shared taxonomy and mitigation starting point rather than a certification checklist or evidence that a deployed system is secure.

OECD.AI Wonk · guide

A five-step roadmap to closing the AI evaluation gap

The roadmap addresses evaluation results that overstate real-world performance or fail to transfer across deployment contexts. Its five steps balance standardized and local tests, evaluate throughout the lifecycle, build qualified assurance and communication capacity, tailor tests to each value-chain actor and technology, and use a coordinated, trusted process for updating methods.