Is your environment ready to open the throttle?

A self-check from Deploying Agents at Scale: What Enterprise Adoption Actually Looks Like, Agentic Engineering Days Zurich, 20 November 2026

How to answer

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. This page sends nothing and stores nothing: your answers stay on your screen and are gone when you close it.

Key to the labels

Every piece of evidence carries one of these labels in words. Where a label goes on after a comma, the rest says which kind it is, such as a benchmark, a randomized trial or a survey.

Controlled study
Researchers set the conditions and measured the result: a trial, a benchmark or a comparison before and after with a control.
Vendor telemetry
A company measuring its own systems or its customers' systems, usually a company that sells the fix.
Self-reported
What people or organizations say about themselves: a survey, a company's own field report, a vendor's own demonstration, or Michael's own record of an incident in one session he ran.
Observational study
Counts taken from public activity, such as pull requests on GitHub, with no control group.
Recommendation, not a figure
A source's advice, quoted. It carries no number.
Unverified
Not checked against the primary source. It is kept and marked, and no check rests on it alone.
Measured
A reason for the order that rests on a finding in the evidence, which it links to.
Argued
A reason for the order that is the talk's own reasoning, not a finding.

"Verified, read" gives the date the source was read live and found to say what the evidence quotes.

"Evidence-index rows" under each question names the rows of the talk's evidence index that its figures come from, each a link to its row. A row marked unverified was not read in a live primary source. Evidence that states no figure, such as a quote or a recommendation, has no row and links its source instead.

The ten checks, in fix-first order

  1. 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-index rows: metr-expected-24-believed-20, metr-19-percent-longer, s10-dora-2024-each-25-percent-increase, faros-q3-code-churn-71-6 (unverified)

    The evidence for check 1
  2. 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-index rows: s9-adaptive-attacks-bypass-12-recent-defenses, s7-prompt-of-481-lines-and-8, s7-reset-script-targets-9-nodes, s9-sandboxing-cut-permission-prompts-by-84

    The evidence for check 2
  3. 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-index rows: s7-150-clusters-are-provisioning-concurrently-19 (unverified), s7-0-attendee-clusters-at-workshop-time (unverified)

    The evidence for check 3
  4. 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-index rows: s10-faros-q3-prs-merged-without-review, s1-rejected-agent-prs-228-of-600

    The evidence for check 4
  5. 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-index rows: s5-veracode-2026-the-average-security-pass, s5-veracode-2026-syntax-correct-nearly-100, s5-gitguardian-claude-code-assisted-commits-3, s5-gitguardian-24-008-unique-secrets-in, s1-agent-prs-each-failed-ci-check

    The evidence for check 5
  6. 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-index rows: s11-metr-failure-table-runs-failing-tests, s11-mathews-and-nagappan-gpt-4-solved, s8-meta-testgen-llm-75-percent-of

    The evidence for check 6
  7. 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-index rows: s10-faros-q3-average-pr-size-up

    The evidence for check 7
  8. 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-index rows: s8-after-ai-agents-submission-to-merge, s10-faros-incidents-per-pr-up-242, s11-faros-q3-2026-22-000-developers

    The evidence for check 8
  9. 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-index rows: s11-lulla-et-al-10-repositories-124, s11-ambig-swe-models-struggle-to-distinguish, s11-gloaguen-et-al-context-files-do

    The evidence for check 9
  10. 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-index rows: s11-52-mostly-junior-developers-ai-group

    The evidence for check 10

What your first no means

Read down your answers. The first check you answer no to is the first thing to fix, and the other no answers follow in the order of the list.

Why this order

Argued, not measured. No source read ranks these fixes. No study compares the order in which teams put these practices in place, or measures which one matters most. The order is built from measured findings in five steps, and each reason below is labeled measured or argued.

  1. Step 1: Check 1

    1. A baseline taken before scaling

  2. Step 2: Checks 2, 3

    2. Limits the agent cannot lift; 3. Agent reports checked against reality

  3. Step 3: Checks 4, 5, 6

    4. A written review rule by risk; 5. Automated gates before human review; 6. Tests that check the behavior

  4. Step 4: Checks 7, 8

    7. Small changes, practiced rollback; 8. Review capacity grown with volume

  5. Step 5: Checks 9, 10

    9. Done written down first; 10. Reviewers who can debug unfamiliar code

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 the check does not tell you

What to fix first

Start at your first no and work down this order. The order is argued, not measured: no source read ranks these fixes.

  1. A baseline first. 1. A baseline taken before scaling
  2. Cap what cannot be undone. 2. Limits the agent cannot lift; 3. Agent reports checked against reality
  3. Keep the gate on what merges. 4. A written review rule by risk; 5. Automated gates before human review; 6. Tests that check the behavior
  4. Make the volume hold. 7. Small changes, practiced rollback; 8. Review capacity grown with volume
  5. Improve what goes in. 9. Done written down first; 10. Reviewers who can debug unfamiliar code

Ten yeses means ready by this check. That a yes to every check means ready is argued, not measured.