For teams building AI
The AI Act reaches the product, not the department. The assistant shows how the classification is built, which articles come with each class, and what a disclosure looks like when it has to hold up under review.
Share this page
From product to duty
- Risk classification as its own flow, with the article behind each step visible.
- The system card as a template: what is built, what never happens, where the limit sits.
- Transparency duties separately, for systems that speak directly to users.
- US rules in parallel, for teams shipping into both markets.
How we do it ourselves
- NovaCopilot has its own published system card at a fixed address.
- Answers are deterministic: the same question returns the same rows, with a hash.
- No training happens on the questions, and question text never leaves the device for the journal.
FAQ
- Does it give a finished classification of our product?
- No. It shows how the regulation classifies and which articles apply per class. The conclusion about your product is yours, ideally with legal support.
- Can we copy your system card as a template?
- Read it as a model by all means. The content has to describe your own system, otherwise it will not hold up.
- Are the duties available machine-readable?
- Yes, the same nodes exist on the machine surface with hash and provenance, so your own system can fetch them.
Next step
Three ways to put the register to work in your own practice.
Start with your task
Litigation
Find support in a judgment
Search guiding decisions, see what became final and follow changes in the law.
In-house, deals
Map the rules in a transaction
Move from theme to act and on to the article that carries the duty.
Compliance
Assess the risk in a process
Risk scoring per legal area, with the sources behind every score.