AI Agent Engineering Practice
Learn to build, validate and improve Agent systems, from specs, code and tests to incident analysis.
A passing local test does not establish final delivery; engineering observations do not certify financial research quality. Each article retains its actual evidence and unverified boundaries. Links marked “Chinese original” lead to articles without a published English edition.
IN THIS CATEGORY22 articles
Counts include articles in this category only; related reading is listed separately.
Tags · match all selected
01 / 02
Specs, Evidence and Engineering Memory
From specifications to execution evidence and durable project history.
- AI Coding Quality Panorama: Taking Responsibility for the Whole Project When AI Writes Most of the Code
- Agent Engineering Suite: Connecting Requirements to Release
- When Tests Outgrow the Code: Helping Docs, Code, and Tests Evolve Together
- Does the Code Really Support the Article? An Evidence Contract for Technical Writing
- Spec-Driven Agent Development: From Requirements to Trustworthy Delivery
- Evidence and Trustworthy Acceptance in Agent Development
- Why We Split a Large Weekly Review Spec into Three Phases
- Engineering Knowledge: Context, Memory and Retirement
02 / 02
Real Validation and Task Convergence
Testing runtime protocols, tracing, specialist handoffs and research quality beyond local green checks.
- Start with a Report You Can Read Back: Open ETF Agent v0.1
- Agent Evaluation Panorama: From Green Tests to Real Task Value
- Agent Evaluation Identity: Can Results Survive Model Failover?
- Building Agent Evaluation Sets Across Development and Acceptance
- How Do We Know the Main Agent Actually Used a Specialist’s Findings?
- How a null Broke an Agent Tool Call: A Streaming Compatibility Case
- RAG Recall Looks Great. Why Doesn’t That Prove the Agent Found the Right Financial Evidence?
- Why Did One Subagent Change Hold Up Our Work for an Entire Day?
- From Bug-Fix Loops to Task Convergence
- Why a Small ETF Investment Assistant Became an Engineering Problem
- The Expensive Part of AI Coding Is Deciding What Deserves Verification
- RAG: Revocation and Historical Replay
- Controlled Refresh for Stale Data
- Run Budget and Constraint Governance