People should not have to guess what AI is doing with their data.
This is intentionally plain. A disclosure does not claim perfection. It tells people the minimum facts they should not have to beg for: what the AI is doing, who owns it, what data it touches, whether that data is reused for training, how a person can intervene, and what evidence exists when something goes wrong.
PAI maps the disclosure back to the Production Safety Framework and PAI-8 so small organisations can start with transparency, while serious deployments have a path into stronger evidence, Lab review, and formal assurance.
For business owners
Publish a disclosure before customers ask for one. It shows maturity without pretending a lightweight public statement is a full audit.
Create a disclosure ->For MSPs and consultants
Run a client session, capture the workflow, and leave behind a public disclosure that opens the deeper control conversation.
Open the MSP pack ->For governments and regulators
Use the disclosure as a simple public expectation: AI systems that affect people should have ownership, data-use clarity, and an escalation route.
Read PAI-8 ->For customers and workers
Ask for the disclosure. It is a direct way to request basic clarity without needing to understand the entire technical stack.
View registry ->From uncertainty to something people can inspect.
Name it
The organisation states where AI is used, what it does, and who owns it.
Explain it
People can see data boundaries, training reuse, human review, and incident routes in plain language.
Compare it
Customers, staff, partners, and communities can compare the disclosure with a public standard.
Improve it
Gaps become concrete work: clearer boundaries, escalation, evidence, and stronger controls.