AI can act, within limits

It can open pages Diting has adapted, filter, drill down and run actions you allow. Permissions and audit follow it.

Permission boundaryDiting
RoleCan seeCan do
On-callAll pagesRead only
OperatorHosts and clustersBatch run
AdminEverythingRelease and grant
Roles decide what can be seen and done.

It runs on top of the pages

Adapted product pages register readable state and executable actions.

  • Page state readable, actions executable
  • Out-of-scope actions rejected and logged
  • Knowledge base and MCP tools
  • Code and commands run in a sandbox

Actions AI can run

01

Operate pages

Open, filter, drill down and change time ranges without a human clicking.

02

Read knowledge

Knowledge base and MCP give answers with context.

03

Run actions

Batch runs, releases and rollbacks, opened by permission.

04

Leave a trail

Every call, action and result lands in audit.

Boundaries

PermissionsReuses product RBAC, roles down to pages and buttons
CoverageAdapted pages expose state and actions; other pages expose only title and path
ActionsOnly registered actions. Everything else is rejected.
AuditActor, action, parameters and result
ModelsMultiple providers and local models, offline capable

Fits

  • Teams that want AI to carry real operational work
  • Environments that require an audit trail for every automated action

Doesn't fit

  • Anyone hoping AI can bypass permissions and change production

Bring your system in

Tell us what you run: OS, kernel, public network or not, virtual machines or clusters. We will map the path in.