Logo
ScienceStack
Table of Contents
Fetching ...
Sign In

The Kitchen Loop: User-Spec-Driven Development for a Self-Evolving Codebase

Yannick Roy

Abstract

Code production is now a commodity; the bottleneck is knowing what to build and proving it works. We present the Kitchen Loop, a framework for autonomous, self-evolving software built on a unified trust model: (1) a specification surface enumerating what the product claims to support; (2) 'As a User x 1000', where an LLM agent exercises that surface as a synthetic power user at 1,000x human cadence; (3) Unbeatable Tests, ground-truth verification the code author cannot fake; and (4) Drift Control, continuous quality measurement with automated pause gates. We validate across two production systems over 285+ iterations, producing 1,094+ merged pull requests with zero regressions detected by the regression oracle (methodology in Section 6.1). We observe emergent properties at scale: multi-iteration self-correction chains, autonomous infrastructure healing, and monotonically improving quality gates. The primitives are not new; our contribution is their composition into a production-tested system with the operational discipline that makes long-running autonomous evolution safe.

The Kitchen Loop: User-Spec-Driven Development for a Self-Evolving Codebase

Abstract

Code production is now a commodity; the bottleneck is knowing what to build and proving it works. We present the Kitchen Loop, a framework for autonomous, self-evolving software built on a unified trust model: (1) a specification surface enumerating what the product claims to support; (2) 'As a User x 1000', where an LLM agent exercises that surface as a synthetic power user at 1,000x human cadence; (3) Unbeatable Tests, ground-truth verification the code author cannot fake; and (4) Drift Control, continuous quality measurement with automated pause gates. We validate across two production systems over 285+ iterations, producing 1,094+ merged pull requests with zero regressions detected by the regression oracle (methodology in Section 6.1). We observe emergent properties at scale: multi-iteration self-correction chains, autonomous infrastructure healing, and monotonically improving quality gates. The primitives are not new; our contribution is their composition into a production-tested system with the operational discipline that makes long-running autonomous evolution safe.

Paper Structure

This paper contains 110 sections, 8 figures, 2 tables.

Table of Contents

  1. Core Contributions
  2. Executive Summary (TL;DR)
  3. The Post-Commodity Code Thesis
  4. Code Is No Longer the Hard Part
  5. The Turing Test for Code
  6. Related Work
  7. Autonomous Coding Agents
  8. Self-Improving and Self-Evolving Agents
  9. Long-Running and Looping Patterns
  10. Spec-Driven and Verification-Focused Approaches
  11. Vibe Coding and the QA Crisis
  12. Benchmark Contamination, Adoption, and Quality Evidence
  13. Multi-Agent Design Patterns
  14. Our Differentiation
  15. The "As a User x 1000" Method (AaU1000)
  16. ...and 95 more sections

Figures (8)

  • Figure 1: The Kitchen Loop: a six-phase autonomous improvement cycle.
  • Figure 2: The unified trust model: each iteration flows through the full verification stack before proceeding.
  • Figure 3: The Almanak SDK repository: a production DeFi strategy framework supporting 14 chains and 30+ protocol connectors.
  • Figure :
  • Figure :
  • ...and 3 more figures