A²D²Agentic Agile Driven Development

A²D² · Agentic Agile Driven Development · 智能体敏捷驱动开发

The next agile is agentic.

Rethinking software engineering for the age of agents.

Read the essay →Where we start ↓

Where we start

01 — 03

These three essays are where A²D² starts — a starting point, not the whole of it. They were originally written in Chinese. Below are English titles and abstracts, each linking to the Chinese original. For one continuous English reading, see the essay.

    • LLM constraints
    • Context engineering
    • Architecture

    Context First Principles: Deriving Engineering Architecture from the Physical Constraints of LLMs

    《Context 第一性原理:从大模型的物理约束推导工程架构》

    Most of what developers know about working with agents — write good prompts, keep context short, verify outputs, use several agents — is scattered experience, not theory. This essay starts from four core constraints: prompts make a model converge from a diffuse state toward one direction, at the cost of finite context (L0, a mental model); project knowledge exists for the model only through a finite context window (L1); inference is stateless (L2); and output is probabilistic, not logically guaranteed (L3). Bridge theorems derive selective loading, context decay and optimal session length, frequency-matched persistence, consequence-proportional verification, and attributed feedback. The result is an architecture — convergence engineering, layered knowledge built from self-contained units, tools as cross-cutting channels, session lifecycle management, a persistence stack, trust layers and feedback loops — and the tensions between the constraints.

    • Cybernetics
    • Spec-driven development
    • Harness engineering

    The System Description Problem: When the Bottleneck Shifts from the Execution Layer to the Description Layer

    《系统描述问题:当瓶颈从执行层转移到描述层》

    A human developer is a compensator: gaps in the input are filled with experience, questions and conversation. An LLM is a conditional amplifier: it fills gaps with the most common patterns in its training data, fluently and confidently, and you cannot see where it did so. Once the executor changes, input quality becomes the dominant constraint. Using the cybernetic framework of Jin Guantao’s Cybernetics and Scientific Methodology, the essay treats software development as shrinking a possibility space and maps four progressive control methods onto four stages of AI coding: vibe coding (random control), rule files (control with memory), spec-driven development (conjugate control) and harness engineering (negative feedback). It derives what specs must become — self-contained units layered by change frequency, single-source with lineage tracking — names the missing sensors at the spec layer, and redefines the human role as the two ends of conjugate control.

    • Cybernetics
    • Negative feedback
    • Robustness

    Countering Uncertainty with Structure: A Cybernetic Toolbox for LLM Engineering

    《用结构对抗不确定性:LLM 工程的控制论工具箱》

    A companion to the second essay. In 1927 Harold Black faced unstable vacuum-tube amplifiers and changed the system’s structure instead of the tubes: the precision of a closed-loop system depends mainly on its feedback channel, not its forward channel. The LLM is that imprecise tube. From this the essay states a meta-theorem — system precision is a function of structure — and its corollary: treat sensor infrastructure as a first-class investment. It then lays out six tools across five dimensions: redundancy and voting (space), cascade control (time), feedforward compensation and filtering (information), adaptive control (learning) and robust control (architecture), each mapped to LLM engineering, and extends “can deviations be detected?” into a five-question checklist. Most teams should start with feedback and feedforward.

When you cannot raise component precision, counter uncertainty with structure.

— Countering Uncertainty with Structure

Coming next

The next essay distinguishes conversation from task in how we communicate with LLMs — the distinction that leads to A²D²’s domain objects. Title to be announced.

Tooling

The tooling is the practical implementation of this methodology and will be released later.