INS-0012 · Role, system, consequence

Same system. Different responsibilities.

AI literacy follows the real work: what a person uses, reviews, changes or governs—and the consequences when something goes wrong.

M4TIC implementation aid informed by Article 4

An operating guide that connects capability and responsibility to context, not a legal scale.

Five roles, four shared lenses

Responsibility changes with the work. Read every role against the actual system and its possible consequence.

  1. Role
  2. System
  3. Consequence
Role in the workPurpose and authorityVerification, people and consequenceData and rightsControl, incidents and change
UsesOccasional user of an approved toolFor defined tasks, even when use is infrequent.Purpose and authorityKnows allowed and prohibited tasks; does not expand system authority.Verification and consequenceChecks facts and results before use; does not confuse fluency with reliability.Data and rightsDoes not enter prohibited or confidential data; follows privacy, confidentiality and IP rules.Control and changeStops, reports anomalies or exposure and knows where to ask for help.
ReliesReviewer or person relying on AI outputWhen a decision or action depends on the result.Purpose and authorityUnderstands which decision depends on the output and retains judgement.Verification and consequenceChecks sources, completeness, relevance, bias, affected people and severity of error.Data and rightsConsiders whether data or outputs may affect people, rights or interests.Control and changeCorrects, rejects, overrides or escalates; records the decision when required.
DefinesProcess owner or managerDesigns the work, controls and responsibilities.Purpose and authorityDefines intended use, roles, approvals, limits, fallback and authority boundaries.Verification and consequenceSets proportionate tests and standards; separates a demo from operating evidence.Data and rightsMaps data, people and consequences; triggers specialist review when needed.Control and changeAssigns oversight, logging, incident handling, review and refresh triggers.
ConfiguresBuilder, configurator or integration ownerChanges system behaviour, connections or capability.Purpose and authorityUnderstands components, versions, permissions, connected tools and authority boundaries.Verification and consequenceTests behaviour, failure modes, security, robustness and monitoring in context.Data and rightsProtects data and credentials; communicates limits and impacts to process owners.Control and changeManages change, rollback, dependencies, incidents and useful technical documentation.
Decides and governsLeadership, procurement, privacy, security and governanceMakes organisational decisions and assigns accountability.Purpose and authorityDecides whether to adopt, fund, buy, constrain or retire the system.Verification and consequenceRequests evidence, contractual terms, controls and context-appropriate capability.Data and rightsAssesses rights, sector, vendor, transfers and the need for qualified review.Control and changeProvides resources, accountability, escalation and review after change or incidents.

Limits of this aid:not statutory textnot a compliance score or maturity modelnot certificationnot legal adviceno role is an exemption

Complete text equivalent

This M4TIC implementation aid, informed by Article 4, connects AI literacy to role, system and consequence. The five roles describe different responsibilities in the work, not a legal hierarchy, score or path to compliance.

Occasional user of an approved tool

Knows allowed and prohibited tasks, does not expand system authority, verifies facts and results, protects confidential data and follows privacy, confidentiality and IP rules. Stops and reports anomalies, exposure or harmful output.

Reviewer or person relying on AI output

Understands which decision depends on the output, retains human judgement and checks sources, completeness, relevance, bias, affected people and consequences. Corrects, rejects, overrides or escalates and records the decision when required.

Process owner or manager

Defines intended use, roles, approvals, limits, fallback and authority. Sets proportionate tests and standards, maps data and people, identifies when specialist review is needed and assigns oversight, logging, incident handling and refresh triggers.

Builder, configurator or integration owner

Understands components, versions, permissions and connected tools. Tests behaviour, failure modes, security, robustness and monitoring; protects data and credentials and manages change, rollback, dependencies, incidents and technical documentation.

Leadership, procurement, privacy, security and governance

Decides whether to adopt, fund, buy, constrain or retire the system. Requests evidence and suitable terms, assesses rights, sector, vendors and transfers, triggers specialist or legal review when needed and provides resources, accountability, escalation and review.

In a small business one person may hold several roles and should combine the capabilities required by the actual work. No role, occasional use, external contractor status or low-consequence context creates an automatic exemption.