Amazon Lost 6.3 Million Orders Because Nobody Reviewed the Code. Here's What Governance Actually Looks Like.

On March 5th, Amazon's North American marketplace saw a 99% drop in orders. 6.3 million orders gone. Not because of a hack. Not because of a natural disaster. Because someone pushed a production change without documentation or approval. Three days earlier, on March 2nd, their AI coding assistant Q gave an engineer inaccurate advice pulled from an outdated internal wiki. That change went live. 120,000 lost orders. 1.6 million website errors. Globally. Amazon's SVP of e-commerce stood up and said what everyone was thinking: "The availability of the site and related infrastructure has not been good recently." understatement of the quarter. They've now initiated a 90-day "code safety reset" across 335 Tier-1 systems. Senior engineers are now required to approve AI-assisted code changes before deployment. Directors and VPs have been instructed to audit all production code change activities within their organizations. Mandatory deep-dive meetings. Stricter documentation. "Controlled friction