# Amazon — From prototype to production: Engineering agents with Agent DLC

- Company: Amazon (amazon.com)
- Announced: 2026-11-12T15:38:47+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://aws.amazon.com/blogs/machine-learning/from-prototype-to-production-engineering-agents-with-agent-dlc/
- Record: https://forck.live/items/35327-from-prototype-to-production-engineering-agents-with-agent-dlc
- Subject: Bedrock / Nova

Amazon's guide introduces the Agent Development Lifecycle (Agent DLC), a lifecycle with two loops and one explicit standard for judging every change to an AI agent before release. The post argues that conventional unit tests and CI/CD are necessary but not sufficient for agents, because agents are non-deterministic, because prompt, tool, retrieval or memory changes alter behavior in ways text review cannot reveal, and because model endpoints, knowledge bases and external APIs can change independently of the repository. It presents a measured reference implementation, an internal HR policy assistant answering questions over a document knowledge base, and states the results are not a customer outcome or a benchmark result. In the first evaluation round, chunk-level source precision was 1.00 for all three golden questions, while fact-level precision was 0.59, 0.53 and 0.09, so a release gate using chunk-level precision alone would have accepted all three answers. After a prompt-only change that added three constraints, the first question improved substantially and the third got worse, which the evaluation traced to a knowledge-coverage problem: the corpus lacked a dedicated sick-leave policy document. The accompanying AWS Samples repository includes infrastructure deployment, the HR agent, custom evaluators, and scripts for baseline evaluation and prompt-change re-evaluation, and the post notes scores can vary across runs and repository versions.

## Evidence

Verbatim from https://aws.amazon.com/blogs/machine-learning/from-prototype-to-production-engineering-agents-with-agent-dlc/:

> Over the past year, AI agents have moved from exploration into engineering. Enterprise teams are shipping large language model (LLM) systems that call tools, orchestrate APIs, and answer questions over internal knowledge.
> 
> A successful demo can show what an agent is capable of. Before release, the team needs to answer a further question: “ Is this agent ready for production? ” The person responsible for that decision needs evidence that the agent meets the agreed requirements.
> 
> To make that decision consistently, teams need a repeatable, affordable way to assess the agent’s current behavior and whether the latest change has improved it.
> 
> In traditional software development, teams answer these questions with unit tests, continuous integration and continuous delivery (CI/CD), and passing builds. Those mechanisms are necessary but not sufficient for agents, for three reasons, each requiring additional checks. This post explains these three properties and presents a measured case where an aggregate metric hides a coverage problem. It then introduces the Agent Development Lifecycle (Agent DLC): one lifecycle, two loops, and a single explicit standard for judging every change.

---

Record: https://forck.live/items/35327-from-prototype-to-production-engineering-agents-with-agent-dlc
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
