Claude Code Is Not Your Architect
Claude Code can accelerate software delivery, but it cannot replace architectural judgment. Once an AI coding agent can understand a repository, edit files, run commands, create pull requests, and interact with tools, the real question is no longer “Can it generate code?” The real question is, “Can we safely govern what is allowed to change, test, approve, deploy, and explain?”
This talk introduces a practical architecture and governance model for using Claude Code in real software teams. Participants will learn how to move beyond prompt-to-code experiments and build safer workflows that incorporate context, limits, architectural rules, human approval, delivery gates, and evidence trails.
AI coding agents are changing software delivery. Claude Code can help developers understand codebases, modify files, run commands, generate tests, support Git workflows, and accelerate pull request creation. That speed is powerful, but it also introduces a new architecture risk: generated code can look correct while hiding security gaps, weak tests, unsafe retries, broken authorization, poor observability, excessive cloud permissions, and fragile production behavior.
This talk introduces the role of the Claude Code Architect: not as a replacement for developers, but as the person who defines how agentic coding is safely used across repositories, teams, CI/CD pipelines, and cloud systems. We will cover project memory, CLAUDE.md, plan-first workflows, permission boundaries, sandboxing, MCP/tool governance, pull-request policies, secure code review, CI/CD gates, observability, and production-readiness checks.
The goal is simple: use Claude Code to move faster without surrendering architectural control.
Main audience promise
By the end of this talk, participants will understand how to safely introduce Claude Code into a real engineering workflow without creating fragile, insecure, unreviewable, or ungoverned production systems.
⸻
Why this talk matters now
AI coding is moving from simple autocomplete to agentic software delivery. The new generation of tools can inspect repositories, plan changes, edit files, run commands, participate in pull requests, and connect to external tools through protocols such as MCP. That means AI coding agents are becoming active participants in the SDLC.
This creates new questions for architects and senior developers:
- What context should the agent be allowed to see?
- What commands should it be allowed to run?
- What files should it never modify?
- What secrets and credentials must stay outside its reach?
- What changes require human approval?
- What CI/CD gates must block unsafe output?
- What evidence should be preserved for review and audit?
- When should generated code be rejected even if it compiles?
This talk answers those questions through a practical architecture framework.
⸻
Talk details
Primary focus
This talk is not a Claude Code tutorial. It is an architecture talk about safe autonomy in software delivery.
It focuses on:
- Claude Code as an engineering workflow actor
- Risks introduced by agentic coding
- Repository-level architecture standards
- Context and project memory
- CLAUDE.md as an architecture control surface
- Plan-first workflows
- Prompt-to-plan-to-diff discipline
- Human-in-the-loop approval
- MCP and external tool governance
- CI/CD safety gates
- Secure code review
- Cloud-readiness checks
- Evidence and auditability
- Production-readiness decisions
About Rohit Bhardwaj
Rohit Bhardwaj is a Director of Architecture working at Salesforce. Rohit has extensive experience architecting multi-tenant cloud-native solutions in Resilient Microservices Service-Oriented architectures using AWS Stack. In addition, Rohit has a proven ability in designing solutions and executing and delivering transformational programs that reduce costs and increase efficiencies.
As a trusted advisor, leader, and collaborator, Rohit applies problem resolution, analytical, and operational skills to all initiatives and develops strategic requirements and solution analysis through all stages of the project life cycle and product readiness to execution.
Rohit excels in designing scalable cloud microservice architectures using Spring Boot and Netflix OSS technologies using AWS and Google clouds. As a Security Ninja, Rohit looks for ways to resolve application security vulnerabilities using ethical hacking and threat modeling. Rohit is excited about architecting cloud technologies using Dockers, REDIS, NGINX, RightScale, RabbitMQ, Apigee, Azul Zing, Actuate BIRT reporting, Chef, Splunk, Rest-Assured, SoapUI, Dynatrace, and EnterpriseDB. In addition, Rohit has developed lambda architecture solutions using Apache Spark, Cassandra, and Camel for real-time analytics and integration projects.
Rohit has done MBA from Babson College in Corporate Entrepreneurship, Masters in Computer Science from Boston University and Harvard University. Rohit is a regular speaker at No Fluff Just Stuff, UberConf, RichWeb, GIDS, and other international conferences.
Rohit loves to connect on http://www.productivecloudinnovation.com.
http://linkedin.com/in/rohit-bhardwaj-cloud or using Twitter at rbhardwaj1.