Governance is code: what an AI engineering playbook actually enforces
A policy no gate enforces is a suggestion. How one playbook governs AI coding agents across five repos, and which rules block versus merely advise.
I'm Leonardo Culjak — twenty-five years of building enterprise software, now spent making sure the thing you're about to pay for is the right thing. Every engagement starts small, paid, and honest about what comes next.
Not a funnel. Four situations, four honest routes into the same first conversation. The answer changes where you start.
One question, then I'll tell you where to start
Pick one — the answer changes where you start.
Every engagement starts scoped, at a fixed price, and with full clarity about what comes next. The first rung is a conversation; the second, a blueprint you own for good; the third, software running in production.
Eight web applications and their SQL databases off legacy hosting onto Azure, with failover, backup, monitoring and Zero Trust access added on the way. Then the delivery pipeline, so shipping stopped being an event.
Read the case studyPlatform
Azure App Services · Azure SQL with TDE · Blob Storage · Entra ID · Zero Trust network design · CI/CD pipelines · observability and cost governance
AI
Azure AI Foundry · Semantic Kernel · agentic RAG · multi-agent orchestration with guardrails and evaluation. Lead AI and agentic architect on the platform above.
Articles published here, not syndicated elsewhere. The claim is not that the work was done — it is that someone else could rebuild it from the page.
A policy no gate enforces is a suggestion. How one playbook governs AI coding agents across five repos, and which rules block versus merely advise.
Three terms that get used interchangeably and shouldn’t. What each one is, how they fit together, and the questions to ask before you buy “an AI agent”.
Short answers
Questions buyers ask before they spend.
A number quoted before your requirements are written down is a guess — and a guess is exactly what everyone else has already given you. What I can tell you is the method, and it doesn't change.
A fixed fee for forty focused minutes. No free “discovery call” that turns out to be a sales call.
You get the number before work starts. If scope changes the price, you approve it first.
Milestones and named deliverables, not an hourly meter you have no way to audit.
The blueprint is yours. Take it to any developer on earth — including instead of me.
Sometimes the honest recommendation is to buy something off the shelf, or wait. You'll get it anyway.
The numbered nav is deliberate: the lab, the case studies, the writing and the canvas each hold real work.
Start here
Paid, fixed fee, and I'll say so plainly if you don't need me. Available for remote engagements with US and EU clients.
Córdoba, Argentina — US time zones