Notarized Artifact — 2026-04-28

Machine-readable record

Canonical JSON summary of this artifact for agents, systems, and developers. The certificate_id is the stable reference for verification via POST /api/verify.

{
  "term": "Notarized Artifact — 2026-04-28",
  "slug": "notarized-artifact-2026-04-28-5",
  "category": "registry",
  "artifact_type": "dataset",
  "certification_status": "certified",
  "issuer": "CertifiedData.io",
  "artifact_hash": "sha256:569e56697cd2957b0240bb040ec5daee5779e05c636006931f0e135dcfeacf83",
  "hash_algorithm": "SHA256",
  "schema_version": "1.0",
  "signing_algorithm": "Ed25519",
  "canonical_url": "https://certifieddata.io/registry/notarized-artifact-2026-04-28-5",
  "verification_auth_required": false,
  "openapi_spec": "https://certifieddata.io/openapi.json",
  "certificate_id": "253e569b-4e76-4473-ac28-6ff57d6971c8",
  "proof_surfaces": [
    "GET /api/certificates/253e569b-4e76-4473-ac28-6ff57d6971c8",
    "POST /api/verify → {\"certificate_id\":\"253e569b-4e76-4473-ac28-6ff57d6971c8\"}",
    "GET /.well-known/signing-keys.json"
  ],
  "certificate_endpoint": "/api/certificates/253e569b-4e76-4473-ac28-6ff57d6971c8",
  "generation_algorithm": "notary",
  "rows": 1,
  "columns": 1,
  "industry": "general"
}

Use cases for this synthetic dataset

This certified synthetic dataset includes a verifiable provenance record, making it suitable for environments where data integrity and auditability are required.

• ✓AI model training and validation without real data exposure
• ✓Data pipeline testing and integration validation
• ✓Regulatory compliance demonstrations (GDPR, HIPAA, CCPA)
• ✓Audit and reproducibility workflows requiring provenance proof
• ✓Synthetic data benchmarking and performance evaluation

What this certificate proves

This certificate proves the following about the registered artifact:

• ✓The artifact existed at the recorded issuance timestamp.
• ✓Its SHA-256 fingerprint was recorded as: 569e56697cd2…
• ✓The certificate payload was signed with an Ed25519 private key controlled by CertifiedData.io.
• ✓Any modification to the artifact — even a single byte — produces a different SHA-256 hash, invalidating the record.
• ✓The certificate has not been tampered with since issuance.

How to independently verify this synthetic dataset

Verification does not require an account or trust in CertifiedData. You can confirm artifact integrity entirely with local tools.

1. 01
   Obtain the original artifact

   Download or locate the artifact file you want to verify.
2. 02
   Compute its SHA-256 hash locally

   Run the following command on Linux/macOS: sha256sum artifact.csv or on Windows: Get-FileHash artifact.csv -Algorithm SHA256
3. 03
   Compare to the recorded artifact hash

   The recorded hash for this entry is: sha256:569e56697cd2957b0240bb04… A match confirms the artifact has not been modified since certification.
4. 04
   Validate the Ed25519 signature

   Follow the verification link below to confirm the Ed25519 digital signature against CertifiedData's published public key.