§1 The argument

60 years of process, built for the wrong failure modes

Code review, standups, and sprint ceremonies all exist because humans forget, tire, and protect their egos. Models do none of that. They fail in their own ways, and a lifecycle that never checks for those failures will pass them straight through.

DimensionSDLC (built for humans)ADLC (built for models)
Defends againstHuman failure: forgetfulness, ego, fatigueModel failure: premature satisfaction, sycophancy, context rot, reward hacking
The specA requirements document humans interpretTests are the spec, frozen as rails before the build starts
ReviewPeer code review: does a colleague approve?Prosecution: fresh reviewers charged with breaking the change, and findings must reproduce before the builder sees them
Unit of trustThe engineer who wrote itExplicit exit contracts: deterministic evidence plus human attestation
Audit trailCommit messages and ticket commentsgate-manifest: a verdict ledger auditors can read
Cost over timeProcess overhead compoundsFindings distill into deterministic defenses (P7), so the same failure is caught by a lint next time

Read the original essay ↗

§2 Implement

Run it against your own repository

curl -fsSL https://www.agenticlifecycle.ai/install.sh | sh

macOS and Linux, Node 18+. Then adlc init in your repository. Windows is not supported. Every install channel →

ADLC began as an essay series. Read the original theory at voodootikigod.com ↗MIT · @adlc on npmPrivacy