Risk-based obligations for AI systems, models, providers, deployers, and other actors.
Understand the law. Then operate under it.
Move from role and system classification into a persistent governed state: obligations, evidence, gaps, versions, changes, review and revalidation. TA-14 preserves what was established, what remains unsupported, and whether prior reliance still corresponds to the system that exists now.
It structures obligations, evidence, gaps, review routes, decisions, records and continuing evidence state.
One governed identity follows each system through classification, evidence, change and revalidation.
Supported propositions remain distinguishable from gaps, stale evidence and review-required conditions.
A changed system or source can trigger revalidation without rewriting the historical record.
Begin with the role you actually hold.
Different actors can carry different obligations for the same system or model. Choose the closest role to open a bounded pathway.
Provider
You develop an AI system or general-purpose AI model and place it on the market or put it into service under your name or trademark.
Open role pathway DEDeployer
You use an AI system under your authority in a professional or organisational context.
Open role pathway IMImporter
You place an AI system bearing the name or trademark of a provider established outside the Union on the Union market.
Open role pathway DIDistributor
You make an AI system available on the Union market without being the provider or importer.
Open role pathway PMProduct Manufacturer
You place an AI system on the market or put it into service together with your product under your own name or trademark.
Open role pathway ARAuthorised Representative
You are established in the Union and hold a written mandate to perform specified tasks on behalf of a provider.
Open role pathway GPGPAI Provider
You develop or place a general-purpose AI model on the market and need a model-level governance pathway.
Open role pathway ?Not Sure?
Use a guided route to identify possible roles, system categories, exceptions, and evidence still needed.
Open role pathwayI do not know whether my system is high-risk—or which role applies.
Walk through a bounded sequence that separates declared facts, unresolved facts, possible classifications, exceptions, and evidence still needed.
Open the Act by governance problem—not by guesswork.
Each destination preserves the legal source, actor, applicability basis, evidence expectations, unresolved questions, review route, and governed outputs.
Risk Classification
Determine whether a system is prohibited, high-risk, transparency-scoped, limited-risk, or outside a claimed category.
Explore requirementProhibited Practices
Map use cases against prohibited-practice categories, exceptions, evidence, and escalation boundaries.
Explore requirementHigh-Risk AI Systems
Explore lifecycle duties, risk management, data governance, documentation, oversight, logging, and monitoring.
Explore requirementGeneral-Purpose AI
Separate model-provider duties, systemic-risk pathways, technical information, copyright policy, and downstream support.
Explore requirementArticle 50 Transparency
Map direct-interaction disclosure, synthetic-content marking, biometric notice, deepfakes, and public-interest text.
Explore requirementConformity Assessment
Preserve the selected assessment route, evidence package, reviewers, findings, corrections, and resulting standing.
View roadmapPost-Market Monitoring
Govern continuing performance, incidents, material changes, corrective action, and evidence validity after deployment.
View roadmapIncident Reporting
Create bounded routes for detection, classification, chronology, notification, correction, and preserved outcome.
View roadmapHuman Oversight
Define accountable human authority, intervention capability, escalation, competence, and override boundaries.
Explore requirementTechnical Documentation
Bind system identity, intended purpose, architecture, data, testing, limits, versions, changes, and evidence ownership.
View roadmapFundamental Rights Impact Assessment
Structure affected-person context, risks, safeguards, governance decisions, review, and retained limitations.
Explore requirementRecordkeeping and Logs
Preserve identity, chronology, provenance, access, decisions, interventions, changes, and outcomes.
Explore requirementPlanned and expanding modules remain visibly bounded until their dedicated governed workspaces are ready.
Move from an uncertain system description to a verifiable governed record.
Identify
Identify the actor, system, model, product, use case, jurisdiction, and intended purpose.
→Classify
Separate role classification, system category, risk category, and claimed exceptions.
→Determine Applicability
State why each obligation is included, excluded, conditional, or unresolved.
→Map Requirements
Translate applicable requirements into bounded evidence and decision routes.
→Preserve Evidence
Bind claims to documents, tests, owners, versions, chronology, and limitations.
→Review
Challenge reasoning, expose gaps, preserve objections, and correct without erasing history.
→Governed Record
Create a dated, attributable record of applicability, evidence, decisions, and boundaries.
→Independent Verification
Test whether the preserved package still corresponds to the claimed implementation.
The platform must point back to the controlling source.
Each requirement route should identify the controlling article and preserve the exact source version used for the determination.
Recitals may provide context but should remain distinguishable from binding operative provisions.
Commission, AI Office, Board, standards, and authority guidance should be dated, attributed, and never silently substituted for the Regulation.
TA-14 structures governance routes and evidence. It does not replace the official text, competent legal advice, conformity assessment, or regulator judgment.
Do not collapse the law, the evidence, and the conclusion into one layer.
A regulation states obligations. An organisation declares how those obligations apply. Evidence supports that declaration. Review tests the evidence and reasoning.
Map the obligation before claiming the outcome.
These demonstration pathways separate provider and deployer duties, identify evidence dependencies, expose missing proof, and define review-ready outputs.
Direct AI interaction disclosure
Provider
Map whether a system interacts directly with natural persons and whether the disclosure design clearly informs them that they are interacting with AI.
- Interactive AI systems
- Chatbots and conversational systems
- Direct user-facing AI interfaces
- Intended-purpose statement
- User-interface captures
- Disclosure timing and wording
- Exception analysis
- Version and deployment record
- Applicability record
- Disclosure evidence map
- Gap and exception record
- Review-ready route package
Machine-readable marking and detectability
Provider
Preserve how synthetic or manipulated audio, image, video, and text outputs are marked in a machine-readable format and made detectable where technically feasible.
- Generative AI systems
- Synthetic media systems
- AI-generated or manipulated content
- Marking architecture
- Detection testing
- Interoperability evidence
- Robustness evidence
- Technical-feasibility determination
- Marking implementation record
- Detectability test record
- Technical limitation record
- Provider evidence package
Emotion recognition and biometric categorisation notice
Provider or Deployer
Map notice obligations where natural persons are exposed to emotion-recognition or biometric-categorisation systems, subject to applicable exceptions.
- Emotion-recognition systems
- Biometric-categorisation systems
- Workplace or public-facing deployments
- System classification
- Deployment context
- Notice design
- Exception analysis
- Affected-person pathway
- Applicability determination
- Notice implementation record
- Exception and limitation record
- Deployment evidence package
Deepfake and public-interest text disclosure
Deployer
Map deployer-side disclosure for deepfakes and certain AI-generated or manipulated text published to inform the public on matters of public interest.
- Deepfakes
- AI-generated public-interest text
- Professionally deployed synthetic media
- Content classification
- Editorial-control record
- Disclosure wording and placement
- Publication chronology
- Exception analysis
- Deployer disclosure record
- Editorial-control determination
- Publication evidence package
- Exception and boundary record
Every material claim should become a dated, attributable record.
Applicability Record
Preserves actor, role, system, use case, jurisdiction, scope, exceptions, and the basis for inclusion or exclusion.
Create record 02Evidence Map
Binds each obligation or commitment to documents, technical artifacts, tests, owners, versions, and unresolved gaps.
Create record 03Transparency Implementation Record
Preserves marking, notice, disclosure, placement, timing, detectability, and deployment state.
Create record 04Independent Review Record
Preserves reviewer identity, scope, evidence reviewed, findings, objections, corrections, and limitations.
Create record 05Change Record
Shows what changed, when, why, by whom, and whether prior evidence remains valid.
Create record 06Outcome Record
Preserves what was approved, held, denied, escalated, superseded, withdrawn, or left unresolved.
Create recordThe EU AI Act world is an operating layer inside the institution—not an isolated compliance page.
EU AI Act Command Center
Operate persistent system passports, obligation states, evidence gaps, change pressure and revalidation.
Open pathway 02AI Governance Registry
Preserve governance identity, establishment date, versions, claims, non-claims, evidence, and stewardship.
Open pathway 03Governance Routes
Convert obligations into inspectable pathways with inputs, gates, evidence, outputs, and explicit failure states.
Open pathway 04Governed Records
Preserve applicability, evidence, review, disclosure, change, and outcome records.
Open pathway 05Independent Review
Discover professionals through declared expertise, evidence signals, artifacts, and visible limitations.
Open pathwayKnow what applies. Know why. Know what evidence exists. Know what changed.
Build a persistent system passport, map obligations, preserve evidence, expose gaps, detect change and revalidate prior reliance before the representation outruns the condition underneath it.