[{"data":1,"prerenderedAt":71},["Reactive",2],{"work-agentic-delivery-platform":3,"work-next-agentic-delivery-platform":68},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"title":8,"description":7,"kicker":9,"summary":10,"cover":11,"coverSmall":12,"coverAlt":13,"role":14,"where":15,"stack":16,"stats":21,"next":28,"order":29,"body":30,"_type":62,"_id":63,"_source":64,"_file":65,"_stem":66,"_extension":67},"/work/agentic-delivery-platform","work",false,"","Agentic delivery platform","Lead engineer · global travel company","Moving a Jira ticket to Agent Ready hands it to agents on Amazon Bedrock AgentCore, which take it through requirements, architecture, implementation and code review.","/3d/cover-agentic-platform.webp","/3d/cover-agentic-platform-640.webp","Clay model of a conveyor with four upright cards travelling along it, one of the tiles on the rail picked out in teal","Lead engineer","Global travel company",[17,18,19,20],"Amazon Bedrock AgentCore","Jira","GitLab","Python",[22,25],{"value":23,"label":24},"3 agents","Claude Code, Codex, Kiro, interchangeable",{"value":26,"label":27},"Per agent","token and cost tracking","alarm-framework",2,{"type":31,"children":32,"toc":60},"root",[33],{"type":34,"tag":35,"props":36,"children":38},"element","case-section",{"label":37},"Overview",[39,45,50,55],{"type":34,"tag":40,"props":41,"children":42},"p",{},[43],{"type":44,"value":10},"text",{"type":34,"tag":40,"props":46,"children":47},{},[48],{"type":44,"value":49},"The agents run on Amazon Bedrock AgentCore, with an orchestration layer in Python sitting between the platform and the tools. That layer is the part I would keep. Claude Code, Codex and Kiro are interchangeable behind it, so which agent does a stage is a configuration choice rather than a rewrite, and every call is logged and traced with its tokens and its cost attributed to the agent that made it.",{"type":34,"tag":40,"props":51,"children":52},{},[53],{"type":44,"value":54},"The handover is the ticket. Jira holds the state, and each stage writes its output back onto the ticket for the next one to read: requirements, then architecture, then implementation, then code review. Moving a ticket to Agent Ready starts the first stage. After that, GitLab webhooks trigger each round of development and review, so a push or a comment on the merge request is what wakes the next pass rather than a person chasing it. Discovery runs locally, with Kiro agents that apply the client's own product guidelines to the requirements before the work reaches the board.",{"type":34,"tag":40,"props":56,"children":57},{},[58],{"type":44,"value":59},"What changed for the team is where their work starts. A ticket that used to be picked up empty now arrives with requirements and a design attached, and comes back as a merge request to read rather than a branch to write. Reviewing is still a person's job, and it is more of the job than it used to be.",{"title":7,"searchDepth":29,"depth":29,"links":61},[],"markdown","content:work:agentic-delivery-platform.md","content","work/agentic-delivery-platform.md","work/agentic-delivery-platform","md",{"_path":69,"title":70},"/work/alarm-framework","Alarms for a whole AWS organisation",1789325965349]