AI Engineer · July 24, 2025

What every AI engineer needs to know about GPUs — Charles Frye, Modal

What every AI engineer needs to know about GPUs — Charles Frye, Modal video thumbnail
Why it matters

AI Engineer session on What every AI engineer needs to know about GPUs, presented by Charles Frye, Modal. It adds practical context for how teams are building and operating AI systems in production.

My takeaway: What every AI engineer needs to know about GPUs — Charles Frye, Modal is an enterprise-adoption signal. The practical read is to watch how deployment scale, data boundaries, operational ownership, and platform controls change as AI moves out of experiments.
Keep exploring

More curated notes connected through AI Engineering and Model Evaluation.

OpenAI News · framework

Pacing model development in an era of cyber-critical capabilities

OpenAI says preliminary evidence that Astra may meet its Critical cybersecurity threshold led it to pause frontier reinforcement-learning work for two weeks and keep its largest planned run on hold. New safeguards include stronger workload and network isolation, continuous boundary testing, token-level monitoring that escalates suspicious tool activity, and broader alignment checks for deception, reward hacking, and unauthorized access.

OpenAI News · framework

A blueprint for democratic governance of frontier AI

OpenAI proposes a three-part U.S. frontier-AI governance model: harmonize emerging state safety laws into a federal baseline, strengthen CAISI as an evaluation and standards institution, and coordinate a broader resilience program. Proposed controls include severe-risk evaluations, transparency reports, independent audits, safety-incident reporting, model-weight security, whistleblower protection, and periodic technical assessments.

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.