A lean reference architecture for AI-assisted delivery teams

This is the real architecture pattern behind how EBM's own delivery teams work — not a theoretical enterprise diagram, a description of what a lean team actually needs.

Version control with mandatory review gates. AI-assisted code still goes through the same pull-request review as anything else. No exceptions, no "the AI already checked it."

A staging environment that mirrors production closely enough to trust. AI-generated changes get tested somewhere real before they touch customers — the gap between staging and prod is where AI-assisted mistakes actually cause damage.

Task-scoped AI access, not project-wide access. An assistant working on a billing fix shouldn't have standing access to the auth system. Scope access to the task, not the whole codebase, by default.

A rollback path that doesn't depend on remembering what changed. Feature flags or clean revert points, so an AI-assisted change that turns out wrong can be undone in minutes, not hours.

One human owner per change, always. Every AI-assisted change has a named person accountable for it shipping — the assistant helps, it doesn't own the outcome.

None of this requires enterprise tooling budgets. It requires discipline about the four or five guardrails above, applied consistently. That's the same architecture we bring to IT Services engagements.