ARTFEED — Contemporary Art Intelligence

Agent Safety as a Runtime Contract: A New Paradigm for AI Harness Design

ai-technology · 2026-08-13

A recent paper on arXiv (2608.11274) posits that ensuring AI safety for autonomous agents should occur during runtime through harnesses rather than through training. The authors argue that existing training techniques, such as RLHF, DPO, and Constitutional AI, are inherently inadequate for agents that can execute code, alter files, communicate, and adjust databases. They introduce a dual-runtime contract: a preventive aspect that restricts harmful actions via sandboxes, permission gates, output filters, and trajectory monitors, and an evidential aspect that mandates verifiable evidence of positive actions, linking task submissions to concrete proof like test runs, log captures, file diffs, and citation grounding. The paper supports its claims with four lines of public evidence, including a survey of 52 documented safety incidents involving AI agents and LLMs, as well as an audit of 31 uncontested false completions, with detailed protocols and data available in supplementary JSON files. This work signifies a notable shift in perspectives on AI agent safety, highlighting the runtime environment's critical role over training interventions.

Key facts

  • Paper: arXiv:2608.11274
  • Title: 'Agent Safety Should Be a Runtime Contract'
  • Argues training-based safety methods (RLHF, DPO, Constitutional AI) are insufficient for autonomous agents
  • Proposes runtime contract with preventive and evidential faces
  • Preventive face includes sandboxes, permission gates, output filters, trajectory monitors
  • Evidential face requires proof like test runs, log captures, file diffs, citation grounding
  • Based on survey of 52 AI-agent/LLM safety incidents
  • Includes false-completion audit with 31 non-contested cases
  • Data released in supplementary JSON files
  • Published on arXiv

Entities

Institutions

  • arXiv

Sources