The standard
The seven founding principles
Any product or system conforming to the ARIA standard must satisfy seven first-principle requirements. The standard rewards the architecture, not any brand.
First principles, not features
Each requirement describes an architectural property, not a product feature. A detector that satisfies all seven can run live, offline, on any hardware, without a user's media ever leaving the device — and every claim it makes can be checked by someone other than its maker. That is the bar a conforming product clears.
- 01
Real-time
Detection at the point of interaction, not post-event forensic upload. Synthesis happens live; detection must too.
- 02
On-device capable
Runs locally without mandatory cloud dependency. Sovereignty and latency demand this.
- 03
Air-gap compatible
Functions in offline or isolated environments. Critical for defense, healthcare, finance.
- 04
Privacy-preserving
Analysis can occur without media leaving the device. Compliant with GDPR, HIPAA, and regional data sovereignty law.
- 05
Hardware-agnostic
No lock-in to a single chip or vendor ecosystem. Portable across architectures.
- 06
Transparent scoring
Authenticity confidence is reported, not hidden. Response actions remain configurable per the deployer's governance policy.
- 07
Independently testable
All claims must be verifiable by a neutral benchmark. No self-reported accuracy.
“These principles map to real, shipped capability — which is why they are technically defensible.”
Principle 07
Verified, not asserted
Principle seven is the keystone. Every claim made against the first six is confirmed by an independent benchmark run by a neutral academic lab — never a self-reported accuracy figure. It is what turns a marketing claim into a certifiable one.
See how certification works →These principles are fixed in the charter.
They can be amended only by a vote of the membership. Read the founding document, or add your name to it.