AI Artifact Trust Infrastructure
AI artifact certification: know which claim you are verifying
CertifiedData uses cryptographic records for both supported synthetic-data certification and external-artifact notarization. They are independently verifiable, but they do not make the same claim.
CERTIFICATION
Synthetic dataset certification
For a synthetic dataset produced by a supported CertifiedData generation workflow, the issued record can bind the dataset fingerprint, generation timestamp, generation metadata, schema version, and CertifiedData issuer signature.
The record can establish
- ✓The signed certification record was issued by CertifiedData and has not been altered
- ✓The relying party's dataset matches the certified SHA-256 fingerprint when the bytes are supplied for comparison
- ✓The generation facts encoded by the supported issuance workflow
NOTARIZATION / ATTESTATION
External artifact notarization
For an existing model file, AI output, external dataset, report, or other artifact, the AI Artifact Notary fingerprints the submitted bytes and issues a signed integrity/existence attestation.
The record can establish
- ✓The signed attestation record was issued by CertifiedData and has not been altered
- ✓The artifact supplied later matches the SHA-256 fingerprint recorded at notarization time
- ✓The submitted artifact fingerprint existed in this notarization workflow at the recorded time
What neither record proves by itself
Verify the signed facts, not a broader inference
A valid Ed25519 signature establishes integrity and issuer authenticity for the signed payload. The payload and issuance workflow determine what was actually certified or attested. See the Certificate Policy for the authoritative scope boundary.