Blog
Writing about delivery when part of the team is software.
What changes when agents do the work, what it costs, which decisions stay with people, and where Turnado sits next to the AI tools you already use.
Our European vision: sovereignty is a setting, not a stickerDigital sovereignty has become a logo on a website. We think it is a property of a configuration: where inference runs, who can be compelled to disclose, and whether a rule refuses a call or merely disapproves of it. This is what we are building in Europe, what we can point at in code today, and the three claims we deliberately do not make — including that our own process model has its own weights.
Bring your own coding agent: what an ops layer adds to Claude Code, Cursor and CopilotTurnado does not plug into your editor. It meets whatever writes your code at the four places that already produce evidence: the ticket, the branch, the pipeline and the model bill.Turnado vs Claude Code, Cursor and Copilot: what changes when a second person joinsAI coding assistants are excellent at writing code and were never built to run a delivery process. Here is exactly where the line sits, and why the two are complements rather than competitors.How to write a functional design an AI can decomposeYou do not have to write differently for machines — you have to write more precisely, which helps people too. Seven habits that turn a document into a backlog worth editing.Jira and Azure DevOps in the agent era: what a board needs when half the team is AITraditional issue trackers assume every actor is a person who can be reasoned with. Four assumptions break when agents do the work, and each one has a concrete fix.Measuring AI autonomy: five metrics that tell you whether your agents actually helpLines of code and “tasks completed” measure activity, not value. Five metrics that survive contact with reality, and the two vanity numbers to stop reporting.Human in the loop: which decisions must stay with people when agents do the workNot every approval deserves a human, and not every human approval is real. A test for deciding which decisions to keep, based on reversibility, accountability and evidence.GEO: how to get your product cited by ChatGPT, Claude and PerplexityGenerative engine optimisation is not SEO with new keywords. It is making your pages quotable: verifiable facts, answered questions, real URLs per page, and structure a machine can lift.What does an AI coding agent actually cost per user story?Model usage is the first line item in software delivery that varies per work item. How to budget it, where the cost hides, and the four ceilings worth having before you need them.EU-hosted AI for software teams: what “European” actually has to meanData residency, the AI Act and GDPR turn a marketing line into a set of concrete questions. Six of them, with the answer that makes a claim checkable instead of reassuring.The eighteen conditions an AI agent should never be able to skipGuardrails for agentic delivery, concretely: which conditions belong on which transition, why they must be calculated rather than judged, and how to tell a real guarantee from a convention.Vibe coding works alone and breaks in a team — here is exactly whereBuilding by conversation is genuinely fast for one person on one project. The three things that break when a colleague, a customer or a second month arrives, and what replaces them.What is AI-native DevOps? A working definitionAI-assisted development makes a developer faster. AI-native delivery puts agents on the board as actors with roles, permissions and a cost. This is the difference, with the five properties that mark the line.