CertifiedData.io
← AI Decision Ledger/Live public feed
Public · Ed25519-signed · Hash-chained

Decision Log

The public record of AI decisions made against CertifiedData certified artifacts. Each entry is cryptographically signed, appended to an append-only log, and independently verifiable without an account.

This page shows decisions logged with public_mode=true. Private records are not published. Machine-readable: GET /api/decision-log

How decision records reach this log

Step 1

Artifact certified

A dataset or AI artifact is cryptographically certified and registered in the artifact registry.

Step 2

Artifact used

A model or workflow consumes the certified artifact to produce a decision or output.

Step 3

Decision logged

The operator logs the decision via POST /v1/decisions, optionally referencing the certificate ID.

Step 4

Published here

Records with public_mode=true are Ed25519-signed, chain-linked, and appear in this log.

Live public records· showing 125 of 6,170

DecisionTimestamp

anomaly detection

f9839e2e-75b4-4e60-b2f5-fcecfcccaa0f

metrics_within_baselinelatency_spike_detectedno_statistical_outliers
Jul 12, 2026, 03:41 PM UTC

credit risk assessment

9e90a3bc-b022-4550-b878-458891e36b00

income_verifiedcredit_history_positive
Jul 12, 2026, 03:41 PM UTC

churn risk assessment

88cacb03-969c-49bc-a2e7-538d6c37388c

engagement_decliningengagement_stablerecent_product_usage_high
Jul 12, 2026, 03:41 PM UTC

content moderation

994dc0e2-c146-49df-aeca-508cbbadc37e

violates_harassment_policyconfidence_above_threshold
Jul 12, 2026, 03:41 PM UTC

dataset certified

b07b9ac7-d3f7-449d-a914-1d19a772fb86

schema_validatedno_pii_detectedrow_count_within_limits
Jul 12, 2026, 03:41 PM UTC

dataset certified

0b61617a-7b9b-44e9-aaaf-0f694a1ba9f6

hash_verifiedrow_count_within_limitsschema_validated
Jul 12, 2026, 03:41 PM UTC

dataset certified

9ad1f9cc-fe04-4981-aa59-cf10a33263f1

pro_tier_certification
Jul 12, 2026, 03:13 PM UTC

dataset generated

9345ca22-93c0-4cd1-a08f-516678741957

synthetic_generation_completed
Jul 12, 2026, 03:13 PM UTC

dataset certified

9db2c1fc-5b46-4f1f-8b2b-fa8d920abfaf

pro_tier_certification
Jul 12, 2026, 03:13 PM UTC

dataset generated

274819b6-d417-4b2c-9985-b45779825612

synthetic_generation_completed
Jul 12, 2026, 03:13 PM UTC

dataset certified

1278c0f7-71cd-44db-b564-44bf645fbeea

team_tier_certification
Jul 12, 2026, 03:13 PM UTC

dataset generated

4d7b1f82-378f-4d1f-8fc0-a6f2a6eb8cec

synthetic_generation_completed
Jul 12, 2026, 03:13 PM UTC

dataset certified

ba006567-6117-4aa0-801e-959dfd04afa0

enterprise_auto_certified
Jul 12, 2026, 03:13 PM UTC

dataset generated

e9283a41-fa28-40ae-ab50-452ba138fc35

synthetic_generation_completed
Jul 12, 2026, 03:13 PM UTC

dataset certified

b8b866de-e3d5-4c9f-a988-de5b74ff2b54

free_tier_auto_certified
Jul 12, 2026, 03:13 PM UTC

dataset generated

da936d05-1ded-433a-b079-c429076503dc

synthetic_generation_completed
Jul 12, 2026, 03:13 PM UTC

credit risk assessment

ac217fc5-ad7c-45e3-baae-f8e517e591ea

payment_history_cleanincome_verifieddebt_ratio_within_threshold
Jul 12, 2026, 10:42 AM UTC

insurance claim

c267ef31-8f94-4813-ac9b-93e90df9d665

duplicate_claim_detectedpre_auth_on_fileservice_date_valid
Jul 12, 2026, 10:42 AM UTC

dataset generated

aaea1d02-aa97-467f-b348-8e6e705a8130

synthetic_generation_completed
Jul 12, 2026, 08:44 AM UTC

dataset generated

a0c1bcb7-a001-4c20-9a4a-a2fafa7f184b

synthetic_generation_completed
Jul 12, 2026, 08:44 AM UTC

dataset generated

f91d7a0a-8a84-450b-875d-4c170b775dfa

synthetic_generation_completed
Jul 12, 2026, 08:44 AM UTC

dataset generated

3f355409-fc4b-4b7f-8900-3012705453e2

synthetic_generation_completed
Jul 12, 2026, 08:44 AM UTC

dataset certified

8ddd97c1-3c4d-4c39-b736-3b67b2e8bdc3

enterprise_auto_certified
Jul 12, 2026, 04:06 AM UTC

dataset generated

efcc0479-a851-4dfd-b06b-1bb482375125

synthetic_generation_completed
Jul 12, 2026, 04:06 AM UTC

dataset generated

cce28644-d81f-46eb-b2b0-ecb100feee58

synthetic_generation_completed
Jul 12, 2026, 04:06 AM UTC
Entries 125

Record structure and API

Public API endpoints

GET /api/decision-log

?limit=25&offset=0

GET /api/decision-log/latest

GET /api/decision-log/:id

GET /api/decision-log/:id/verify

GET /.well-known/decision-signing-keys.json

Response fields (public records)

decision_id — unique identifier

decision_label — event type

selected_option — outcome

certificate_id — linked artifact (optional)

public_hash — SHA-256 of this record

previous_public_hash — chain link

signature_alg — Ed25519

integrity_status — verified | pending

timestamp — ISO 8601

Integrity model

Each public record is signed with Ed25519 using the key identified in /.well-known/decision-signing-keys.json.

The previous_public_hash field links each record to the prior entry. Any modification to a prior record changes its hash and breaks the chain.

Signature verification is available at /api/decision-log/:id/verify without authentication.

Current implementation scope

Public decision records are available via the API and on this page. Records are optionally linked to certified artifact IDs.

Ed25519 signing and SHA-256 chain linking are active for all public records. The /verify endpoint performs live signature checks.

Only records explicitly submitted with public_mode=true appear here. Private records are not published.

Log a decision

Use POST /v1/decisions with an authenticated API key. Set public_mode: true to publish the record to this log. Reference a certificate_id to link the decision to a certified artifact.

POST /v1/decisions
Authorization: Bearer <api_key>

{
  "decision_label": "loan_approved",
  "selected_option": "approved",
  "public_mode": true,
  "artifact_reference": {
    "certificate_id": "cert_01j9k..."
  }
}

Questions

What is a decision record?

A decision record is a structured log entry that captures an AI system action: the decision label, selected outcome, input context, model version, policy version, and timestamp. Records submitted with public_mode=true are signed with Ed25519, assigned a SHA-256 hash, and appended to this public log.

How is the decision log different from the artifact registry?

The artifact registry records certified datasets and AI artifacts — what was built and signed. The decision log records how those artifacts were used downstream — decisions made by systems that consumed certified data. Certification is about provenance; decision logging is about use.

How does decision lineage connect to artifact certification?

Each decision record can reference a certificate_id, linking the decision to the specific certified artifact used. This creates a traceable chain: certified dataset → model trained on it → decision made by that model. The chain allows auditors to follow a decision backwards to its data origin.

Can decision records be independently verified?

Each record includes an Ed25519 signature and a chain hash linking it to the prior entry. The signing public key is available at /.well-known/decision-signing-keys.json. Any party with the record payload and the public key can verify the signature without contacting CertifiedData.

Are all AI system decisions published here?

No. Only decisions logged via POST /v1/decisions with public_mode=true appear in this log. Private decision records are retained but not published. Operators choose what to make public at the record level.

Why does decision logging matter for governance?

AI governance requires verifiable evidence of how systems behave — not just what data they were trained on. Decision logs provide timestamped, cryptographically signed records of individual AI actions, satisfying audit and traceability requirements for frameworks like the EU AI Act (Articles 12 and 19).

Related

Public Decision Log — Live Feed of Signed AI Decisions | CertifiedData