What this sample includes
- Provider-side package sections from the minimum EU path.
- Technical evidence files generated from sample runs.
- Only a small curated set of outputs, not the whole internal workspace.
Public EU demo
See a sample EU AI Act minimum package
This is a controlled public example of the minimum package path. It shows what the output can look like before your team runs the workflow on its own system.
What this sample does not show
- It is not your final package.
- It does not replace the draft your team writes in Builder.
- It does not replace system-specific runs on your own agent.
Open the sample files
Start with the readable runtime report, then open the article-level outputs that make the package concrete.
Readable runtime report
A readable technical report built from the sample runs.
Open sample fileCompare report
The machine-readable comparison between baseline and new runs.
Open sample fileAnnex IV technical documentation
A sample Annex IV technical documentation output.
Open sample fileArticle 50 transparency marking
A sample Article 50 transparency evidence output.
Open sample fileArticle 9 risk register
A sample risk-management output for Article 9.
Open sample fileArticle 10 data governance
A sample data-governance output for Article 10.
Open sample fileHuman oversight summary
A sample oversight and traceability output.
Open sample fileWhat to do next
- Open Builder if you want to draft the selected EU package path.
- Open the EU starter if you want a first self-serve check on your own agent.
FAQ
Frequently asked questions
What does the sample EU AI Act package show?
It shows a controlled public example of the minimum package path: a readable report, structured article-level outputs, evidence files, and links that help a reviewer understand how the sample run was packaged.
Is the sample package a complete compliance file?
No. It is a public demonstration, not your final package. A real package needs your own system facts, runs, evidence, role and scope choices, owner completion, and final human review.
Why are only selected files visible in the sample?
The demo exposes a curated set of public-safe outputs so buyers can understand the handoff shape without exposing a full internal workspace or confidential system data.
How should I use the sample before buying support?
Use it to check whether the package format matches what your reviewers need. Then use Builder or the starter to see how the same path would begin for your own system.