Era 01 — 1990s Early Internet

The One-Person Era

In the early days of the internet, a single person typically built an entire website. They defined what the product should do, wrote the front-end pages, coded the back-end logic, deployed it to a server, and fixed any issues themselves.

This was not because early engineers were exceptionally versatile, but because the problems were simple enough. A static page plus a few server-side scripts remained well within one person's cognitive capacity.

There was a toolset from that era called "the Web Trio" -- Dreamweaver for building pages, Flash for animation and interaction, Fireworks for image editing. The significance of this toolset was that it packaged all the complexity of Web development into a single product suite, enabling one person to take a website from visual design to launch without specializing in any single discipline.

This state came with an important byproduct: the feedback loop was closed. I wrote the code, I managed the server, I was the first to know when users had problems, and I was the one who fixed them. Like a cook who tastes his own dish before serving.

AGENTS.MD is the precipitate of the Double Diamond process. It translates the results of human judgment into machine-executable constraints, so automation no longer runs in the dark.

What Goes Into AGENTS.MD—The output of Double Diamond convergence -- the LLM's behavioral constitution

Artifacts & Quality — The Dual-Track Production Structure

Every Artifact Has a Corresponding Quality Check

In the AI-era engineering pipeline, production artifacts progress layer by layer -- from the top-level value proposition, all the way down through user scenarios, business rules, domain models, API contracts, integration boundaries, to the system as a whole and non-functional requirements. This process is not a one-way waterfall but bidirectional: discoveries at any layer can feed back up.

At the same time, each layer of artifact naturally corresponds to a type of test. This is not an afterthought quality check but a mirror of the artifact itself -- whatever the artifact defines, the test verifies. The whole structure forms a continuous, iterative closed loop.

Feedback Characteristics of Each Test Type —Ordered by feedback speed

Cybernetics · Harness Engineering

Why Cybernetics Is the Discipline You Must Master Today

Cybernetics, proposed by Norbert Wiener in 1948, studies how systems maintain a target state through feedback. Its core model is elegantly simple: set a reference value, use a sensor to perceive the actual state, compare the two to detect deviation, have an actuator execute corrective action, and repeat.

This theory matters today not because it is new, but because LLMs are the first technology to make the "actuator" intelligent enough -- it no longer executes only fixed rules but can understand context, assess the nature of deviations, and choose corrective strategies. A decision node that once required human intervention can now be handled autonomously by the LLM.

This is the essence of Harness Engineering: designing the entire engineering pipeline from requirements to deployment as a closed-loop control system. Tests are the sensors, the LLM is the regulator, CI/CD is the actuator, and the product value proposition is the setpoint. Any deviation -- a failed test, a type error, a contract mismatch -- does not need to wait for a human to discover it; the system perceives, corrects, and advances on its own.

The ultimate form of this pipeline is lights-out operation: the LLM works continuously for hours or longer, completing full cycles from code generation to test verification to automatic repair in an unattended state. While you sleep, the pipeline keeps running.

Without understanding cybernetics, all you can design is a semi-automated process that requires constant human oversight. With cybernetics, you can design a system that corrects itself.

Cybernetics Concepts Mapped to the Engineering Pipeline

Underlying Logic

A Cycle, but Not a Return to the Origin