Lesson objective

Write the scope, systems and data-class sections of an agent authority register entry, with a named owner, before the agent is connected to any live plant system.

Plain-language explanation

Why this matters now

Module 01 produced two decisions for each agent action: the rung it runs on, and the result of the three-question test. Decisions that live in a meeting, an email thread or a vendor's settings screen drift. An administrator widens a scope on a Friday to fix a problem. A new quality engineer assumes the agent was cleared for their customer programme because it runs on the one next door. The integrator moves on and nobody knows what the rules were.

The answer is to write the authority down, in one place, before the agent touches anything live. This programme calls that document the agent authority register, with one entry per agent.

Be clear about its status. No law, regulation or standard in this course requires an agent authority register. It is this programme's own instrument, an AI Coalition Network recommendation. It borrows ideas from voluntary frameworks, but it is not taken from any of them.

  • Professional guidance (NIST, AI RMF 1.0, NIST AI 100-1, January 2023; voluntary): the Core has four functions, GOVERN, MAP, MEASURE and MANAGE, and GOVERN "applies to all stages" of AI risk management. Appendix C says human roles in decision making and oversight "need to be clearly defined and differentiated." A register entry is one practical way to define those roles for a single agent. NIST has announced that version 1.0 is being revised; this lesson refers to 1.0. There is no NIST certification.
  • Quality systems (ISO 9001:2026, published 16 September 2026; voluntary consensus standard): ISO describes the standard as covering, among other topics, Context of the organization, Leadership, Planning, Support and Operation. It is not law anywhere in the United States; it becomes binding on a plant only where a customer contract or a regulator requires it, and ISO itself does not certify anyone. No AI-specific requirement in ISO 9001 was verified for this course, and this lesson quotes no clause. A register does not "comply with" ISO 9001; if your plant runs a certified quality system, decide with your quality manager how the register fits the system you already have.

A question to sit with

If your integrator left tomorrow, could anyone in the plant say, from a document, which product lines, systems and kinds of data each running agent is allowed to touch?

What goes wrong

The configuration is the only record. What the agent may do is whatever the platform currently allows. Nobody can tell whether today's setting is the one that was agreed.

Scope is written as a system, not a job. "The agent works in the QMS" says nothing about which records, which product lines or which customer programmes. A QMS holds records for every customer the plant has.

Data classes are never named. The agent is scoped to "supplier documents", and supplier documents include a customer's drawings, a defence programme's technical data and price lists under a confidentiality agreement. Each class carries different obligations.

The owner is the enthusiast. The entry is signed by the person who wanted the agent, not by the person who owns the records it will touch.

The entry describes what already happens. It was written after the agent went live, from its current settings, and blesses whatever the integrator connected.

The practical answer

Keep one register for the plant, one entry per agent. The entry has two halves. This lesson covers the first half: who, what for, where and with what data. Lesson 2 covers the second: what it may do, how much and how often, and when it is reviewed.

Field What to write Fictional example
ID and name A unique ID and a plain name AG-007 Receiving certificate check
Agent owner Named person and deputy who answer for how it runs Manufacturing IT lead; deputy the controls engineer
Output owner Named person who owns the records it affects Receiving inspection supervisor
Purpose One sentence of the job it does Compare incoming material certificates with purchase order requirements and list mismatches
Rung and test Rung from Module 01 and the date of the three-question test Rung 1 for comparison; rung 2 for filing; tested 2026-09-10
Scope Product lines, customer programmes and sites it may serve Commercial and industrial programmes at the main plant only
Exclusions Programmes, sites or record types it must never serve Any defence programme; any file marked export-controlled
Systems Each system, and read or write for each ERP purchase orders: read. Document system receiving folder: read and file. QMS: none
Data classes Each class it may see, and each it must not May see: internal, supplier commercial. Must not see: controlled or export-controlled technical data
Trigger The exact event that starts a run A certificate arrives at the receiving mailbox from a supplier on the approved list

Write scope as a job, not a system. Name the product lines, customer programmes and sites. Then write the exclusions just as clearly, because an exclusion is what stops scope creep. "All commercial programmes except those whose purchase orders carry customer-specific quality requirements" is a scope a person can check. "Receiving" is not.

List systems one by one, with read or write for each. For every system, say whether the agent reads, writes or has no access at all. "None" is an entry, not a blank. Where the agent writes, Lesson 2 lists exactly what it may write.

Name the data classes, using the plant's own scheme. Most plants already sort information into classes, even if informally. A simple scheme for this register:

Class Typical content Default for an agent
Public Published catalogue data, public specifications May read
Internal Work instructions, schedules, maintenance history May read within scope
Commercial confidential Supplier pricing, customer quotes, contract terms Read only where the job needs it
Customer proprietary Customer drawings, specifications and process requirements Read only where the job needs it and the customer's terms allow it
Controlled CUI under a government contract; export-controlled technical data Excluded unless the export or contract authority approves in writing

Five classes, each with a default. Your plant may need more; it should not need fewer.

Understand why "controlled" is its own class. The rules differ by source, and the register should not flatten them.

  • Law / rule (32 CFR Part 2002, the Controlled Unclassified Information programme; binds executive branch agencies): the programme covers unclassified information that requires safeguarding but does not meet the criteria for classification. It distinguishes CUI Basic from CUI Specified, which carries handling controls that differ from CUI Basic. The regulation binds agencies, not manufacturers directly; a manufacturer's obligations arise from the terms of its contract. So the register records what the contract requires, as the plant's contract owner reads it, and never treats all CUI alike.
  • Export-controlled technical data is treated in Lesson 4. For this lesson, the point is simpler: an agent's scope should exclude controlled data by default, and only the person who owns export and contract compliance in the plant can open it.

Name the owners by person and by role. "Quality" is not an owner. "The quality manager, currently D. Mensah, deputy the senior quality engineer" is. The agent owner answers for how it runs. The output owner answers for the records it affects, and signs the entry.

Remember this

  • The agent authority register is this programme's recommendation; no law or standard in this course requires one, and it quotes no quality standard clause.
  • Write scope as product lines, customer programmes and sites, with exclusions written as clearly as inclusions.
  • List every system with read, write or none.
  • Name the data classes the agent may and may not see, with controlled data excluded by default.
  • CUI obligations reach a plant through its contract, and CUI Specified carries its own controls.

Manufacturing example

Marlin Gear & Spline is a fictional gear manufacturer with three kinds of work: commercial agricultural gearboxes, automotive spline shafts under a tier-one customer's supplier requirements, and a small defence subcontract for actuator gears. Its manufacturing IT lead, Dana Whitcombe, has an agent running on a trial basis that reads incoming supplier certificates and compares them with purchase order requirements. It was set up by an integrator with access to "the receiving mailbox and the ERP". Before extending it, the quality manager, Samuel Kovacs, asks for a register entry. Writing it exposes three gaps. First, scope: the receiving mailbox serves all three kinds of work, so the agent has been reading certificates and attached drawings for the defence subcontract. Dana rewrites the scope as "commercial and automotive programmes at the main plant" and adds an exclusion for "any purchase order on the defence programme and any file marked controlled or export-controlled". Second, systems: the integrator's account could read and write the whole ERP. The entry lists "ERP purchase orders: read. Document system receiving folder: read and file. QMS: none. MES: none." Third, data classes: the automotive customer's drawings are customer proprietary, and its supplier requirements restrict who may see them. Samuel checks those terms and confirms the agent may read the drawing revision block only. The contracts manager, Aisha Grant, who owns the defence subcontract, confirms the exclusion and asks that defence purchase orders go to a separate mailbox the agent cannot reach. The entry names Dana as agent owner and the receiving inspection supervisor as output owner, and is signed before the integrator changes the account to match.

Responsible-use warning

Do not scope an agent by system alone. A mailbox, a QMS or a document system usually holds records for every customer programme the plant has, including controlled and customer-proprietary data. An agent scoped to "the receiving mailbox" reads everything that arrives there. Write scope as product lines, customer programmes and sites, write the exclusions just as precisely, and change the plumbing, such as separate mailboxes or folders, so the exclusion is enforced and not just stated.

Human-review requirement

The agent owner drafts the entry. The output owner for the affected records signs it: the quality manager or the person the quality system names for quality records, the receiving supervisor for receiving records, the materials manager for purchasing data. Where the entry touches customer-proprietary or controlled data, the contracts owner and the person responsible for export compliance confirm the data classes and exclusions. Each approval is recorded with name and date.

Practical exercise

Use a fictional plant, or your own with nothing confidential.

  1. Choose one agent, running or proposed, and write its ID, name and one-sentence purpose.
  2. Name the agent owner and a deputy, and the output owner for the records it affects, by role and by person.
  3. List the product lines, customer programmes and sites it will serve, then write the exclusions just as precisely.
  4. List every system the agent's account can reach today, and mark each read, write or none according to what the job actually needs.
  5. Using the five-class scheme in this lesson, or your plant's own, list the data classes the agent may see and those it must not see.
  6. Check whether any mailbox, folder or queue the agent reads also receives controlled or customer-proprietary data, and describe the plumbing change that would keep that data away from it.
  7. Identify which contracts, if any, place CUI or other handling terms on the data in scope, and who in the plant owns reading them.
  8. Give your draft to someone unfamiliar with the agent, ask which records they think it could touch, and record any gap.
  9. Record the date, the names of the signers and the configuration changes needed to make the live account match the entry.

Knowledge check

  1. Does any law or standard in this course require an agent authority register?

    Answer guidance: No. The register is this programme's own recommendation. It borrows the idea of defined roles from voluntary frameworks such as NIST AI RMF 1.0, but no source requires it and it quotes no quality standard clause.

  2. Why should scope be written as a job rather than a system?

    Answer guidance: Because a system such as a QMS or mailbox holds records for every customer programme, so naming the system says nothing about which programmes, product lines or sites the agent may serve.

  3. What are the five data classes in this lesson's simple scheme?

    Answer guidance: Public, internal, commercial confidential, customer proprietary and controlled, with controlled data such as CUI and export-controlled technical data excluded from agents by default.

  4. How do CUI obligations reach a manufacturer under 32 CFR Part 2002?

    Answer guidance: The regulation binds executive branch agencies; a manufacturer's obligations arise from its contract. CUI Specified also carries handling controls that differ from CUI Basic.

Sources and further reading