AI & ML
Agentic Behavior Engineering: A Design-by-Contract Methodology for Specifying, Verifying, and Governing Enterprise AI Agents
arXiv cs.SE0 views
arXiv:2611.05454v1 Announce Type: new Abstract: Enterprise teams that deploy large language model (LLM) agents inherit a maintenance problem that traditional testing does not address. The model is non-deterministic, but the larger risk is that most of what changes an agent's behavior (a retired model version, a revised policy, an upstream schema change, a prompt edit meant to fix one case) originates outside the owning team and is discovered as a production defect rather than caught as a regression. This paper presents Agentic Behavior Engineering (ABE), a platform-agnostic methodology that treats observable agent behavior, rather than the prompt or the model, as the version-controlled engineering artifact. ABE adapts Design by Contract to non-deterministic systems. A specification-only behavior contract with stable rule identifiers states what the agent must do, must not do, and when it must abstain for lack of evidence; a lightweight scenario library turns each rule into concrete situations; and every engineering artifact (tests, runtime policies, telemetry) references the contract in one direction only, so that specification and implementation can change independently without drifting apart. The method organizes the work into five responsibilities (Specify, Ground, Control, Verify, Observe), treats missing evidence and a verified negative as different things, enforces authority outside the model, gates releases on per-scenario pass^k reliability rather than aggregate accuracy, and classifies every production run against the contract so that each finding routes to the asset that must change. We illustrate the method with an executable capacity-allocation boundary suite and a constructed worked example of a product-review approval workflow.
Source:https://arxiv.org/abs/2611.05454PreviousLIBRA: Programmatic Induction of Executable Tool LibrariesNextHybrid LLM-Deterministic Pipelines for Enterprise-Scale Code Migration at Bloomberg
Related posts

Designing a Form That Asks for Birth Date, Time and Place (No Code, Just the Tricky Parts)
0dev.to UX
메타 Quest 2 OS 업데이트 종료, 약시 훈련 루틴에는 무슨 일이 생기나
0dev.to News
How to Put a Logo in a QR Code (and Make Sure It Still Scans)
0dev.to Design
Why Luxury Fine Jewelry Brands Are Ditching Physical Video Shoots for 3D CAD Commercials in 2026
0dev.to Design

How AI Is Changing Healthcare in 2026 - And Why Developers Should Pay Attention
0dev.to Productivity

When Should Singapore Healthcare Enterprises Hire AI Developers?
0dev.to Productivity