Frame the rollout as capability uplift, not replacement

The prompt

Write a one-page framing of your agentic-coding rollout using AWS CAF's four phases — Envision, Align, Launch, Scale. Be explicit that this is a controlled capability uplift, not a replacement for existing architecture, security, operations, or engineering accountability.

Why it's built that way

The handbook is direct about the framing risk: introduce the platform as a controlled capability uplift, not as a replacement for architecture, security, operations, or engineering accountability — the same distinction that keeps a rollout from reading as a headcount threat.

What to do with the answer

Share the one-pager with whoever owns security and platform architecture before the pilot starts, not after.