A source someone can inspect
The proof should name where the fact came from: tenant export, policy, incident log, disclosure statement, workflow map, deployment record, or owner attestation.
Proof model
Evidence proof preview
This page explains the public proof PAI expects when teams claim an AI system is ready, disclosed, controlled, or safely deployed.
A boundary that is not vague
The proof should say which users, systems, data classes, connectors, and actions are in scope and which are explicitly outside scope.
A control that changes behavior
The proof should identify the approval, logging, review, access, escalation, or rollback control that contains the risk.
A named accountable role
The proof should identify who owns the system, who reviews exceptions, and who can change the deployment boundary.
A date and review cadence
The proof should make clear when it was collected and when it should be checked again.
A plain-English public summary
The proof should support an answer that a buyer, user, journalist, or regulator can understand without reading the whole file.
Examples
Where proof shows up in the retained resources.
Discovery
Tenant discovery evidence
Licence inventory, Copilot configuration, security posture, sharing settings, DLP posture, and automation footprint.
WorkflowCurrent-state workflow evidence
Handoffs, systems, approvals, exceptions, manual steps, and the difference between current and AI-assisted work.
ControlsControl-diff evidence
A before-and-after view that shows which PSF controls improve, degrade, or need explicit mitigation.
DisclosureRight-to-know evidence
The public facts needed to explain where AI is used, what humans review, and what the organisation will not claim.
DeploymentAgent deployment evidence
System owner, tool access, action limits, evaluation evidence, telemetry, rollback, and incident response.
BenchmarkAgent readiness benchmark
A public reference point for comparing readiness signals across agent deployment patterns.
Boundary
What this page does not do anymore.
- It does not ask a reader to request or buy a practice pack.
- It does not present a package or payment step.
- It does not describe proof as a marketing badge; proof is evidence that can survive inspection.
- It preserves the URL while the future graph/evidence-wallet model is still being defined.