Table of Contents

• Introduction
• Context
  • The platform
  • Setup of the run
• How the run unfolded
  • The pipeline as executed
  • Timeline
  • Live log
  • Effort by agent
• The MAGI board in detail
  • Independent analyses
  • The three proposals
  • Cross-review with authors masked
  • Preventive review by QA, SRE, Security and the Tech Writer
  • Claim verification and selection
• Implementation: the code written by the developers
  • DEV1, the writer
  • DEV2, the pair
• Verification and reviews of the implemented change
  • QA: acceptance scenarios
  • SRE
  • Security
  • Tech Writer
  • Final review by the three architects
• Functional requirements: from request to evidence
  • Traceability
  • Requirement-by-requirement outcome
  • Findings overall
• Discussion
  • What the architecture changed in this run
  • Threats to validity
  • Cost of robustness
• Second run: the same request on Amazon Bedrock AgentCore
  • What AgentCore changes
  • The deployment in the AWS console
  • The run: a second design round
  • What it took to get a SUCCESS
  • What the gates did not see
  • Independent check outside the platform
  • Two runs side by side
• Conclusion
• Appendix: mandatory gates

Well, here we are again. After the autopsy of the agentic loop I wanted to see the engine on something bigger than a Python upgrade: a long, demanding change request, written by a human, in Italian, for a service that already exists. Not a toy, not a fix. A feature.