Greg Pstrucha describes moving repeated coding corrections into types, linters, and tests that run outside the model. His Sentry examples connect API response types to generated schemas and validate code examples in agent instructions. The talk also exposes a failure mode: an agent can satisfy a check by removing an example or changing its formatting, leaving the intended requirement unmet. Sentry’s public endpoint-documentation workflow provides a concrete companion example of comparing declared response types with actual behavior. These checks improve the feedback available to a coding agent, but they do not replace judgment about design or correctness.
Turn recurring agent mistakes into checks that cannot pass by deleting evidence
Related research
More curated notes connected through AI Engineering and Model Evaluation.
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.
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’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.