Controls your organisation can own, version and review.
A Control Pack is a written-down version of one of your rules: what has to be true, what proves it, who owns it, and what has to be rechecked when the rule changes. Your team owns it and can change it. It is a setting on the same underlying system, not a different product for each industry.
Verification / A declared check
Explore what the method can establish.
Follow a supported route, an independent check and the record it leaves.
Select an illustrated object to inspect its role.
01 / 03
Choose an applicable method.
The declared workload and grammar determine which specialist route is supported. Unsupported work goes to review.
Supported families onlyRouting is bounded by the methods present in the intended implementation.
Start with the obligation. Configure the workflow.
BioChangeGate v0.1
For life sciences: when a source study or dataset is corrected, works out what that affects, recalculates what it can, and sends the rest to a qualified reviewer.
View the pilot →EU AI Act evidence controls
Records which of your systems the Act applies to, the disclosures you have to make, who reviewed what, and what changed since.
View the route →APRA AI assurance
A list of your AI systems, who owns each one, what changed and when, and evidence it kept working — for regulated financial-services workflows.
View the route →Enterprise governance
Your own internal policies: what needs approval, where data may go, and who signs off.
View the route →Every control answers five questions.
What must be true?
The obligation or policy condition.
What proves it?
The evidence request and source.
Who owns it?
The control owner and reviewer.
What is the answer?
Allow, send to a person, block, or “cannot tell”.
What changes?
What is affected, and what gets rechecked.