Skip to content

Lights-Out Codebases

"Lights-out codebases" refers to software development where agents produce and ship code without human code review, relying instead on upstream specifications, automated verification, and downstream observability as the quality apparatus.

Summary

The "lights-out codebase" concept describes a future state where AI agents generate code directly without the intermediate step of human code review. Proposed by Philip Su (see entities/philip-su) and analyzed by Hugo Venturini at SkipLabs (see concepts/compiler-analysis), the concept frames the debate not around whether lights-out codebases are coming, but around whether the replacement apparatus has been built.

Details

The Proposition

A lights-out codebase eliminates human-in-the-loop code review. Agents open, review, and merge their own PRs. The quality control apparatus that previously consisted of human readers reading artifacts is replaced by:

  • Upstream: Formal specification layers, type systems, design-by-specification
  • Verification: AI-checks-AI CI pipelines, comprehensive test suites
  • Downstream: Production instrumentation, canary deploys, feature flags, rollback

Current State

Per Venturini's analysis: the upstream and downstream apparatus for agent output verification is currently "barely exists." Teams are being pushed toward lights-out by agent throughput volume (e.g., 417 PRs/day) faster than they can build the replacement quality gate. This creates a trust gap — not because agents can't produce correct code, but because the infrastructure that makes trusting that code reasonable is missing.

  • The concepts/compiler-analysis argument treats the lights-out codebase as a design target that specifies exactly what infrastructure needs to be built
  • The concepts/harness-engineering approach demonstrates a parallel: agent-first codebases succeed by engineering the environment the agent operates in

Open Questions

  • Is "lights-out" binary (no human review at all) or a matter of degree?
  • What is the minimum viable apparatus to call a codebase "lights-out"?
  • How does this interact with regulatory/compliance requirements for code signing and audit trails?
  • Has Philip Su's original post elaborated on what the post-review workflow looks like concretely?

Sources