AB KineticsContact
● Framework · ABK-AL v1.0

Autonomy levels for industrial service agents.

How much may a service agent do on its own? My answer is a staircase of five levels. Each level says what the agent does, what the human does, and which controls must be in place before the agent is allowed to climb.

Document
ABK-AL
Version
1.0
Date
06.11.2026
Author
A. Kanwar
§01 — Section A–A · Elevation

An agent earns the right to act.

Autonomy is decided per class of action, not per agent: the same agent can recommend a recipe change (L1) and run a log export on its own (L3). Pick a level to see what it takes.
Human does→ Autonomy →Agent does

the hard step is L2 → L3: from approving actions to approving policy

Level L2 · Acts with approval

Agent does
Prepares the action and executes it only after a named engineer signs off.
Human does
Approves or rejects every single action and owns the outcome.

Controls required

  • Source citations on every answer(L0)
  • Access scoped to role and site(L0)
  • Evidence & confidence shown(L1)
  • Engineer feedback loop into evaluation(L1)
  • Human approval gate per action
  • Action audit log
  • Rollback plan per action class
§02 — Specification

Level by level.

Controls are cumulative: an agent at L3 needs everything L0 to L2 require, plus its own.
  1. L0

    Informs

    What the agent does

    Answers questions from manuals, service tickets and past fixes, and cites its sources.

    What the human does

    Diagnoses, decides and acts. Judges whether the answer applies to the machine in front of them.

    Required controls

    • Source citations on every answer
    • Access scoped to role and site

    Example · illustrative

    An engineer sees PM3 heater zone 2 reading 4 K above recipe and asks what could cause it. The agent answers from SOP 114 and three similar tickets, and cites them. The engineer does everything else.

  2. L1

    Recommends

    What the agent does

    Diagnoses a fault and proposes a fix, with the evidence and its confidence.

    What the human does

    Reviews the evidence, decides on the fix and carries it out.

    Required controls

    • Source citations on every answer(L0)
    • Access scoped to role and site(L0)
    • Evidence & confidence shown
    • Engineer feedback loop into evaluation

    Example · illustrative

    The agent notices the same deviation itself, diagnoses thermocouple drift and recommends a −4.0 K offset followed by one dummy wafer. The engineer checks the evidence and enters the offset by hand.

  3. L2

    Acts with approval

    What the agent does

    Prepares the action and executes it only after a named engineer signs off.

    What the human does

    Approves or rejects every single action and owns the outcome.

    Required controls

    • Source citations on every answer(L0)
    • Access scoped to role and site(L0)
    • Evidence & confidence shown(L1)
    • Engineer feedback loop into evaluation(L1)
    • Human approval gate per action
    • Action audit log
    • Rollback plan per action class

    Example · illustrative

    The agent prepares the −4.0 K offset and the dummy-wafer run, then waits. The service lead approves, the agent executes, verifies Δ 0.3 K and files the audit record. This is the sequence drawn on the home page.

  4. L3

    Acts within policy

    What the agent does

    Runs pre-approved classes of action on its own and escalates everything else.

    What the human does

    Defines and maintains the policy, monitors the agent and handles escalations.

    Required controls

    • Source citations on every answer(L0)
    • Access scoped to role and site(L0)
    • Evidence & confidence shown(L1)
    • Engineer feedback loop into evaluation(L1)
    • Human approval gate per action(L2)
    • Action audit log(L2)
    • Rollback plan per action class(L2)
    • Policy-as-code action limits
    • Live monitoring & alerting
    • Kill switch

    Example · illustrative

    Thermocouple offsets up to ±5 K on a module with no lot in process are a pre-approved class of action. The agent applies the offset, verifies and logs it on its own. A larger drift, or a module that is running product, goes to the engineer.

  5. L4

    Acts & reports

    What the agent does

    Owns whole service workflows end to end and reports what it did.

    What the human does

    Reviews by exception, audits the record and re-certifies the agent periodically.

    Required controls

    • Source citations on every answer(L0)
    • Access scoped to role and site(L0)
    • Evidence & confidence shown(L1)
    • Engineer feedback loop into evaluation(L1)
    • Human approval gate per action(L2)
    • Action audit log(L2)
    • Rollback plan per action class(L2)
    • Policy-as-code action limits(L3)
    • Live monitoring & alerting(L3)
    • Kill switch(L3)
    • Continuous evaluation
    • Incident & reporting process
    • Periodic re-certification

    Example · illustrative

    The agent owns thermocouple drift as a workflow across the installed base: it corrects within policy, books a replacement when offsets add up, and reports weekly. Engineers review the exceptions and re-certify the workflow each quarter.

§03 — Cite this · Revisions

Use it, cite it.

If the framework is useful in your own work, please cite the version you used. Later revisions are listed below.

Cite this

Author
Abhimanyu Kanwar
Title
Autonomy Levels for Industrial Service Agents
Version
ABK-AL v1.0
Year
2026
URL
https://ab-k.com/framework

Kanwar, A. (2026). Autonomy Levels for Industrial Service Agents (ABK-AL v1.0). AB Kinetics. https://ab-k.com/framework

BibTeX

@misc{kanwar2026abkal,
  author       = {Kanwar, Abhimanyu},
  title        = {Autonomy Levels for Industrial Service Agents},
  howpublished = {AB Kinetics},
  note         = {ABK-AL version 1.0},
  year         = {2026},
  url          = {https://ab-k.com/framework}
}

Revision table — ABK-AL

  • 1.006.11.2026First public version: five levels (L0–L4), the agent's and the human's role at each level, and cumulative controls.A. Kanwar

Release for production

Let's talk.

auf Deutsch geht's auch.

Conference talks, research collaborations, or a question about the framework — email is the fastest way to reach me.

Drawn
A. Kanwar
Location
Aachen, DE
Languages
English · Deutsch