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 4,306

DecisionTimestamp

dataset certified

a1dbe413-4b2b-4c6b-bc8a-ff74c1d11e83

enterprise_auto_certified
May 28, 2026, 11:47 AM UTC

dataset generated

ff4cca94-f98f-41ed-8bda-b7f53e1e0ebd

synthetic_generation_completed
May 28, 2026, 11:47 AM UTC

dataset generated

8a498820-d8e0-456e-b22d-14f5ce419a7c

synthetic_generation_completed
May 28, 2026, 11:47 AM UTC

dataset generated

4b8582ee-881e-481c-8baa-81a0eb966215

synthetic_generation_completed
May 28, 2026, 05:46 AM UTC

dataset generated

ff865bb1-15fd-41f0-bc81-35bff7072e42

synthetic_generation_completed
May 28, 2026, 05:46 AM UTC

dataset certified

bcf937e6-260e-4cc2-8178-2d6a2309634a

team_tier_certification
May 27, 2026, 11:37 PM UTC

dataset generated

2965f417-bc58-4d86-9f03-55adf36429b6

synthetic_generation_completed
May 27, 2026, 11:37 PM UTC

dataset generated

eac36e15-bd53-4f54-8485-d9123156d1ad

synthetic_generation_completed
May 27, 2026, 11:37 PM UTC

dataset generated

99c9ab0e-7fb5-4d7f-81e9-b37c938f8519

synthetic_generation_completed
May 27, 2026, 11:37 PM UTC

dataset certified

6b6ef8d2-4108-4942-8c07-e2d7d7a6391d

free_tier_auto_certified
May 27, 2026, 11:37 PM UTC

dataset generated

5e4f40a7-f58d-45cb-ac33-706a1d76d018

synthetic_generation_completed
May 27, 2026, 11:37 PM UTC

dataset generated

7e78037b-3435-4992-8fa8-8f8bdd34f347

synthetic_generation_completed
May 27, 2026, 11:37 PM UTC

dataset certified

03892942-7dae-4ac6-a4bb-23d4a6b18ded

enterprise_auto_certified
May 27, 2026, 07:04 PM UTC

dataset generated

9f4eae1d-1d5e-4e88-8fd3-13870234d004

synthetic_generation_completed
May 27, 2026, 07:04 PM UTC

dataset certified

47d58c01-f497-4007-8a04-ca17ce20816a

enterprise_auto_certified
May 27, 2026, 07:04 PM UTC

dataset generated

74efbc3f-6df8-41fb-9d77-55b18e79cba9

synthetic_generation_completed
May 27, 2026, 07:04 PM UTC

dataset certified

b823f3b6-249d-490d-81ea-06764bab2e29

enterprise_auto_certified
May 27, 2026, 07:04 PM UTC

dataset generated

28027bfe-ca4e-41e2-b279-c6d1d0e2c7d2

synthetic_generation_completed
May 27, 2026, 07:04 PM UTC

dataset generated

7d3076e1-a15c-4774-ad6f-52e739ac291a

synthetic_generation_completed
May 27, 2026, 07:04 PM UTC

dataset generated

133f65c3-44ca-41ee-b72d-2ac2e43f07f7

synthetic_generation_completed
May 27, 2026, 07:04 PM UTC

dataset generated

1a99cebf-cfe6-432b-8d79-5b409dadda91

synthetic_generation_completed
May 27, 2026, 03:39 PM UTC

dataset certified

2dc6f165-d7b8-4759-a242-e11a9346aa54

team_tier_certification
May 27, 2026, 03:39 PM UTC

dataset generated

88d1540e-686a-4ddc-89c8-f335471705e4

synthetic_generation_completed
May 27, 2026, 03:39 PM UTC

dataset certified

1491bdb6-4519-4f20-8aa9-0bd3a4bc0c36

enterprise_auto_certified
May 27, 2026, 09:06 AM UTC

dataset generated

7d5a07ab-239b-4e9b-a234-863d12a9f06c

synthetic_generation_completed
May 27, 2026, 09: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