Is your environment ready to open the throttle? A self-check, and what to fix first

This page closes the second half of Deploying Agents at Scale: What Enterprise Adoption Actually Looks Like, Agentic Engineering Days Zurich, 20 November 2026. The talk promised that you would be "able to tell whether your own environment is ready to open the throttle, and what to fix first if it isn't". The interactive version asks the same ten questions and names your first fix as you answer; it loads, sends and stores nothing. Printed, it is a one-page checklist of the same ten questions and the fix-first order, also here as a PDF.

Is your environment ready to open the throttle on coding agents? Answer these ten questions yes or no, for one team or one system, as things stand today. Each question is about your own environment and needs no tool to answer. They are in fix-first order: if you answer no to any, the first no is the first thing to fix. Each comes with the evidence behind it and the kind of evidence it is, so you can check the work.

Answer yes only if it is true today, not planned. Every piece of evidence carries its label in words. Each one that states a figure links its row in the evidence index, which gives the source, the date it was read and its status; the rest link their source. Two things here are argued, not measured: the order of the checks, and that a yes to all ten means ready.

The ten checks

1. A baseline taken before scaling

Do you have delivery measures recorded from before agent use grew, such as lead time, change fail rate, rework rate, recovery time and total monthly incidents, and do you still collect them the same way?

Evidence:

2. Limits the agent cannot lift

Are the things an agent must never do, such as deleting data, resetting infrastructure or using production credentials, blocked by permissions it does not hold, and not only by instructions in its prompt or by an approval a person clicks through?

Evidence:

3. Agent reports checked against reality

Is every claim an agent makes about what it built, changed or deployed checked against the real system before anyone acts on it?

Evidence:

4. A written review rule by risk

Does every change that merges get a review under a written rule that says which changes need a human, which an agent and which both, and do you know what share of last month's merges had no review?

Evidence:

5. Automated gates before human review

Must every agent-written change pass the same build, test, static analysis and secret checks as human code before a person reviews it?

Evidence:

6. Tests that check the behavior

Do agent-written changes come with tests that check the behavior that was asked for, written or reviewed by someone other than the agent that wrote the code?

Evidence:

7. Small changes, practiced rollback

Do you keep each change small, and can every team undo a bad change quickly because it has practiced doing so?

Evidence:

8. Review capacity grown with volume

Has the capacity for review and QA grown in step with the volume of change agents produce, so that the time changes wait for review and spend in QA is not rising?

Evidence:

9. Done written down first

Is what done means written down before an agent starts a task, and do your repositories give agents short, human-written notes on what they could not work out from the code?

Evidence:

10. Reviewers who can debug unfamiliar code

Can the engineers who approve agent changes read and debug code they did not write, and do your junior engineers still get practice debugging code themselves?

Evidence:

What to fix first

Argued, not measured. No source read ranks these fixes. The order is built from the measured findings above in five steps, and each step says which part is measured and which is argued.

  1. A baseline first (check 1). Measured: people inside a rollout cannot tell whether it helped; developers believed they were 20% faster when their tasks took 19% longer (metr-expected-24-believed-20, metr-19-percent-longer). Argued: every later fix is judged against the baseline, and a baseline cannot be taken after the fact.
  2. Cap what cannot be undone (checks 2 and 3). Measured: controls that live in the agent's reasoning fail under adaptive attack, above 90% for most of 12 published defenses (s9-adaptive-attacks-bypass-12-recent-defenses); in my own sessions a prompt rule did not stop a nine-node reset, and a status report went out after the fix was checked on a single-cluster plan only (s7-prompt-of-481-lines-and-8, teardown B's sources). Argued: deleted data and a false report acted on cannot be caught later by review, so the limits come before any gate on what merges.
  3. Keep the gate on what merges (checks 4 to 6). Measured: the review gate is what erodes as volume rises, with PRs merged without review going from a 31.3% rise to 76.3% (s10-faros-q3-prs-merged-without-review), and code that works is often not secure, with syntax near 100% and a security pass rate of 56% (s5-veracode-2026-the-average-security-pass). Argued: the written rule comes first because the automated gates and the tests enforce it; the gates come before tests because they are settings in the pipeline the team already has.
  4. Make the volume hold (checks 7 and 8). Measured: changes grew and waited longer, with average PR size up 71.8% and submission to merge 56.1% longer (s10-faros-q3-average-pr-size-up, s8-after-ai-agents-submission-to-merge). Argued: smaller changes and more review capacity make each check cheaper to pass, which matters only once the gates in step 3 exist.
  5. Improve what goes in (checks 9 and 10). Measured: written task context and clarified requirements improve what agents produce, and learning with an assistant left the widest gap on debugging (s11-lulla-et-al-10-repositories-124, Anthropic, 29 January 2026). Argued: these raise the quality of what enters the pipeline rather than limit harm, and skills take the longest to build, so they come last in the list and are started early.

Ready means a yes to all ten. That a yes to every check means ready is argued, not measured: no study shows that these ten together are enough.

What your answers mean

What the check does not tell you