Skip to main content

Rethinking Infrastructure for AI

by Scott Miller

  • AIAgents
  • AIGovernance
  • DevOps
  • InfrastructureAutomation
  • PlatformEngineering
  • ResourceShell
  • SRE

We're spending enormous effort making AI models smarter.

But are we spending enough time thinking about the infrastructure we're asking them to operate?

Most infrastructure was designed for experienced humans sitting at terminals. Commands such as:

š˜“š˜ŗš˜“š˜µš˜¦š˜®š˜¤š˜µš˜­ š˜³š˜¦š˜“š˜µš˜¢š˜³š˜µ š˜Æš˜Øš˜Ŗš˜Æš˜¹

make sense because the engineer brings the missing context.

They understand the system, its dependencies, the risks, and what might happen next.

An AI agent gets the command.

It doesn't automatically get the operational understanding behind it.

That's why I believe the architecture needs to change.

Instead of:

š€šˆ → š’š”šžš„š„ → šˆš§šŸš«ššš¬š­š«š®šœš­š®š«šž

I think we need:

š€šˆ → š†šØšÆšžš«š§šžš šŽš©šžš«ššš­š¢šØš§ššš„ š‘š®š§š­š¢š¦šž → šˆš§šŸš«ššš¬š­š«š®šœš­š®š«šž

The AI determines š˜øš˜©š˜¢š˜µ should happen.

The runtime determines whether, and how, it can happen.

That runtime can provide things a shell command inherently doesn't:

• Structured resources and capabilities • Dependency context • Risk evaluation • Policy enforcement • Dry-run • Explain-before-execute • Approval boundaries • Auditability • Verified outcomes

Instead of teaching AI to generate every possible command, we can give it resources it can reason about.

Conceptually:

š˜“š˜·š˜¤://š˜¤š˜­š˜¢š˜Ŗš˜®š˜“-š˜¢š˜±š˜Ŗ š˜³š˜¦š˜“š˜µš˜¢š˜³š˜µ

The syntax isn't the important part.

The important part is that the runtime understands the resource and the requested operation before execution occurs.

And when the model doesn't cover an operation?

It should say š˜‚š—»š˜€š˜‚š—½š—½š—¼š—æš˜š—²š—± rather than silently giving the AI unrestricted shell access. Exceptions can still exist, but they should remain governed, scoped, and audited.

This is one of the ideas I've been exploring with the open-source š—„š—²š˜€š—¼š˜‚š—æš—°š—² š—¦š—µš—²š—¹š—¹ (š—æš—²š˜€š—µ) project.

I don't believe the future of AI operations is about giving increasingly intelligent agents increasingly powerful terminals.

I think it's about creating a stronger boundary between š—æš—²š—®š˜€š—¼š—»š—¶š—»š—“ š—®š—»š—± š—²š˜…š—²š—°š˜‚š˜š—¶š—¼š—».

AI can propose.

AI can investigate.

AI can plan.

But a governed runtime should decide what gets executed.

As AI moves from assistant to operator, do you think our existing infrastructure interfaces are ready or do we need to rethink the operational layer itself?

All blog posts

Have a problem like this in your own systems?

Tell us what you're building or what needs fixing. We'll help you work out what should be built, and the smallest useful first step.