Andrew Orobator’s publisher notes describe a feature-flag cleanup workflow that screens code complexity and experiment state before asking a coding agent to generate a patch. Skills preserve recurring decisions, work logs carry session history, and CI supplies evidence for human review. His safeguard example shows why a commit hook can miss a separate file-writing path and why an agent must not invent its own bypass exception. Seven reported green-CI pull requests demonstrate a small screened workflow, not general reliability.
Coding-agent maintenance: preserve decisions and enforce the actual action boundary
Related research
More curated notes connected through AI Engineering and Agent Security.
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.
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.