• Sources: primary, primary, discussion, discussion
  • Summary: Swami Sivasubramanian writes that agents first fix each fidelity test until it passes against real AWS, then implement the emulator until it passes the same test. One group of agents finds gaps and files issues. Another writes tests, implements the fix and reviews it. Before a change reaches the public repository, CodePipeline runs the fidelity tests, several adversarial security agents review it, and deterministic checks block agents from editing code they should not touch. Simon Willison counts 29,684 commits in the project's first three weeks.
  • Why it matters: This is a first-party, mechanism-level account of a software factory in production at AWS. Its guardrails are specs verified against the real system and a merge gate built from agent reviewers.
  • Comments: Sivasubramanian says Kiro failed for four nights to rebuild a Paxos replication engine with no way to check its results, then finished in about two hours once it had a spec and a test environment.