AI as Planner, Not Dictator

There is a meaningful difference between an AI that helps create a plan and an AI that acts. For most domains, the distinction is interesting. For infrastructure, the distinction is essential. Production systems do not have a generous error budget. When something goes wrong, the blast radius is real and the recovery is expensive. The mode of AI involvement matters as much as the capability of the AI itself.

A planner can reason about things that an actor cannot. It can model dependency order — what has to happen before what. It can reason about risk — which operations are reversible, which are not, which have side effects in other systems. It can propose rollback steps before a single change is made, so that if execution fails midway, the recovery path already exists. It can surface expected verification signals so that both humans and systems know what success looks like. Acting without planning skips all of that. It substitutes speed for understanding, and in production infrastructure, speed without understanding is how incidents start.

I want Nexplane to use AI to increase the quality of planning, not to replace it. That means using models to reason about what a change involves, what it might break, what it depends on, and what the recovery looks like — before any execution begins. That output becomes a structured artifact: something a human can review, something a system can verify against, something that captures intent rather than just commands. The plan is the thing. The execution is downstream of the plan.

This framing also preserves accountability, which matters more than it sounds. When an AI acts directly, it is genuinely unclear who is responsible for the outcome. When an AI produces a plan and a human approves it, accountability is clear. The human reviewed it. The human chose to proceed. The organization made a decision, not a black box. That clarity is not bureaucracy. It is how institutions are able to safely delegate hard work without losing the ability to audit and learn from it.

A well-designed AI planner does a few specific things. It makes the reasoning visible. It surfaces assumptions it is making. It tells you what it does not know. It presents alternatives when tradeoffs exist. It does not just produce a script — it produces a structured, reviewable artifact that a human can push back on, modify, or reject. What it does not do is act. Acting is a separate phase, with its own controls. The planner's job is to make the execution phase as safe as possible, not to collapse the two into one.

The goal is not to remove humans from responsibility. The goal is to give humans better plans so they can exercise responsibility more effectively. That is a different thing than automation. Automation replaces human judgment. Planning augments it. I think the infrastructure industry has spent a lot of time pursuing the former when the latter is where the real value is.