Show the disclosure
Tell the recipient about the AI interaction or label AI-generated content where the requirement applies.
Bring together authority, oversight, and disclosure records so an AI Act review starts with evidence of what happened.
The EU AI Act takes a risk-based approach. Obligations depend on the AI system, its use, and whether your organization acts as a provider, deployer, or another regulated actor. Selected evidence mappings support that review; they do not determine which obligations apply.
When disclosure recording is enabled on supported surfaces, AI-interaction notices and content labels can leave a receipt connected to the organization’s history.
Explore agent governanceTell the recipient about the AI interaction or label AI-generated content where the requirement applies.
A supported disclosure event can record the surface and subject reference without copying the conversation into the receipt.
The disclosure receipt maps to Article 50 in the control catalog. Reviewers still assess the notice, delivery, and applicable duty.
These references describe the product’s advisory crosswalk. Evidence depends on the recorded activity, configured capabilities, and review window.
Product evidenceChained action receipts provide logging and traceability records.
Review limitsThe record covers captured activity. It does not establish complete logging for every AI system.
Product evidenceHeld, denied, or abstained actions and human-decided gates provide oversight records.
Review limitsObservation after execution cannot evidence an intervention before execution.
Product evidenceRegistered-agent attribution and scoped conformance packets support record review.
Review limitsA packet is one part of a deployer’s obligations, not a determination that they have all been met.
Product evidenceSupported AI-interaction and content-label disclosures can be recorded as receipts.
Review limitsDisclosure recording requires configuration. A receipt alone does not validate wording, delivery, or legal sufficiency.
Catalog 2026.09.2. A selected mapping supports evidence review; it does not establish compliance or certification.
Use the record alongside your legal and technical assessment of the AI system and its actual use.
System classification, intended purpose, and organizational role
Applicable obligations and current implementation dates
Technical documentation, risk controls, and disclosure design
No. Selected catalog mappings connect records to references in the Act. Legal applicability, risk classification, complete technical controls, and any required conformity assessment need a separate review.
No. Recording must be enabled and the interaction must pass through a supported disclosure surface. A label added elsewhere does not automatically become a recorded disclosure.
Imported activity can show what was observed. It cannot establish that an action was held or reviewed before it took effect. The packet keeps that distinction visible.
Framework requirements and their interpretation should be checked against the authoritative source.
Walk through the scope, available evidence, and remaining requirements with our team.