C² vs AWS AI-DLC: pilot versus approver at the gate

Of all the methods for building with AI agents, AWS AI-DLC is the closest structural peer to C² — and the sharpest contrast. Both are genuinely AI-native. Both are serious about structure. They diverge on two things that turn out to matter a lot: who's in the seat, and what happens to context. Here's the honest head-to-head.

Two AI-native methods, side by side

AI-DLC (AI-Driven Development Lifecycle) is AWS's methodology for building with agents. It runs work through a hierarchical, agent-agnostic pipeline with human approval at phase gates, replaces the two-week sprint with shorter, intense cycles it calls "bolts", and centres on AI-powered execution under human oversight. It's structured, enterprise-credible, and genuinely built for the agent era — you can read the AWS framing directly.

C² is a lighter, agent-agnostic method built on one idea: every project runs two systems — a codebase and a contextbase — and the contextbase is version-controlled context the agent reads before it acts and that compounds across sessions.

They agree on a surprising amount: AI does the execution, humans stay essential, context is structured rather than ad hoc, and the method shouldn't be locked to one vendor's model. The differences are in the two choices below — and they're telling.

Approver at gates vs pilot throughout

The first divergence is the human's role.

AI-DLC casts the human as an approver at phase gates. The pipeline runs a phase, you review and sign off, the pipeline proceeds. Your control is exercised at the boundaries — the gates between phases.

C² casts the human as a pilot directing throughout. Not signing off at checkpoints, but steering continuously — scoping the brief, making the architectural calls, owning the quality bar at every step, not just at gates.

Stuart Leo

AI-DLC asks you to approve the pipeline's output at the gate. C² asks you to fly the thing the whole way.

Neither is wrong, but they produce different experiences. Gate approval scales oversight across a big org with formal checkpoints. Piloting keeps a builder in the loop continuously, which fits a founder or a small team who want their hands on the controls.

Context as delivery vs context as investment

The second divergence is the one that compounds — literally.

AI-DLC treats context as delivery. Load the right rules and information, run the phase, move on. The context is consumed in service of the phase. It does its job and the pipeline advances.

C² treats context as investment. Every session writes down what was learned — decisions, gotchas, briefs — and commits it, so the next session starts from everything figured out so far. The context isn't consumed running a phase. It accrues. After fifty sessions, the contextbase is denser in real decisions than the code itself.

This is the deepest difference between the two. One uses context to run the pipeline. The other builds context as the durable asset, and the pipeline is how it gets built. If you believe the accumulated knowledge of a project is its real value, that's the C² bet.

Bolts vs the brief cascade

A smaller, practical contrast. AI-DLC reframes the sprint as the "bolt" — a short, intense cycle measured in hours or days. C² doesn't batch into cycles at all. Work flows through a cascade of briefs, session by session, continuously — the unit is the brief and the session, not a timeboxed bolt. Both reject the two-week sprint. They replace it with different shapes: AI-DLC with a faster cycle, C² with continuous flow.

Side by side

How to choose

• Choose AI-DLC if you want a structured pipeline with formal phase gates, enterprise governance, and you're working in the AWS tooling world.
• Choose C² if you want to stay in the driver's seat throughout, keep things light and agent-agnostic, and have your context compound into an asset you own — not consumed running a pipeline.

AI-DLC runs the pipeline and asks you to sign off. C² puts you in the seat and makes the context yours.

Start here: see how all the methodologies compare, the head-to-head with BMAD, or read the method.