Best fit
AI providers and deployers must connect product labels, human notices, technical markings, content disclosures, scope decisions, and release claims before qualified legal review.
Reconcile owner-defined AI transparency scope with labels, notices, technical markings, and release claims.
AI providers and deployers must connect product labels, human notices, technical markings, content disclosures, scope decisions, and release claims before qualified legal review.
AI providers and deployers must connect product labels, human notices, technical markings, content disclosures, scope decisions, and release claims before qualified legal review.
findings.csv with stable codes and evidence sources. review-manifest.csv with every reviewed record.
A qualified legal reviewer must define scope and decide whether the recorded surfaces satisfy applicable law.
No. It reads one normalized local JSON packet and makes no network request.
No. It produces evidence findings; the responsible owner makes every decision and action outside the package.
Yes. Stable finding codes, sorted records, and a SHA-256 receipt make repeated review inspectable.
Unreadable JSON, missing arrays, duplicate core identifiers, invalid timestamps, and invalid core numbers fail closed.
No. READY means no automated finding appeared in the supplied normalized packet; source truth still requires human review.
The listing includes the tested package, realistic samples, declared permissions, and known limitations.
Get AI Transparency Surface Evidence Gate on Agensi