# DevOps Salesforce with AI — Practical Manual of Adoption > Markdown (GEO/AEO) version of . Author: **Mauricio Yokoyama Issei** · en-BR · Published: 2026-04-10 · Updated: 2026-08-24. ## In short Putting an AI agent to write code in a shared org Salesforce is only safe in four layers: **foundation**, **architecture**, **methodology** and **governance**. There are nine sections, in order — each one depends on the previous one. - **Foundation** — VS Code, Salesforce CLI and JDK 21 in the right order; then IA connected to live org by an MCP Server, not just to files. - **Architecture** — Flosum Cloud Agent translates metadata into Git in both directions; Delta Deployment, Overwrite Protection and Smart Merge protect the target org. - **Methodology** — Spec-Driven Development: You write WHO and WHY. Impact Matrix and Acting Limits cut rework and wasted computing. - **Governance** — the repository is the long-term memory of the AI: knowledge-base, AGENTS.md, playbooks and skill versions. ## Frequently Asked Questions **Where to start to use AI in Salesforce development?** In the order of installation: VS Code, Salesforce CLI and Salesforce Extension Pack and then JDK 21 — installing Java before the rest is the most common cause of broken environment. Then authenticate the org with "sf org web login" and connect an MCP Salesforce Server, for AI to consult real metadata instead of just reading static files. **When to use Claude Code and when to use Devin?** Claude Code for interactive work in the editor: pair programming, diff review with each change, ambiguous refactoring and architectural exploration. Devin for well-defined ticket that can run alone in sandbox and come back as Pull Request — repetitive batch tasks, delegated by Slack or Jira. **What is Flosum Cloud Agent for?** It's a Node service. js hosted out of the org that translates in both directions between the Salesforce Metadata API and the Git protocol. It is he who makes the org readable as a common Git repository — the format for which Claude Code and Devin were optimized. **How to prevent AI from hallucinating paths or breaking a shared org?** Three Layer Locks: a repository in Salesforce DX source format (force-app/main/default), a spec with Impact Matrix and Acting Limits before opening the agent session, and deploy protected by Overwrite Protection and Smart Merge on the Flosum pipeline. **What is Spec-Driven Development in practice?** It is to stop writing the HOW and start writing the WHO and WHY: a short spec with business context, observable objective, impact matrix, scope limits and verifiable acceptance criteria. Vague scope makes the agent explore, test hypotheses and rework — which costs human time and computing. *© 2026 Mauritius Yokoyama Issei. Citable content with assignment (fair use educational).*