CertifiedData.io
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

DecisionTimestamp

dataset certified

3e9ce466-2ac9-42b6-8aef-0c75bd0f6f85

enterprise_auto_certified
Apr 12, 2026, 05:23 PM UTC

dataset generated

55958305-762f-4ec6-b783-789664954446

synthetic_generation_completed
Apr 12, 2026, 05:23 PM UTC

dataset generated

1fbf3a8c-e9e6-4f73-8d14-529a69b98215

synthetic_generation_completed
Apr 12, 2026, 05:23 PM UTC

dataset certified

f199f8d1-5676-4dd8-bfea-096f833ec594

free_tier_auto_certified
Apr 12, 2026, 05:23 PM UTC

dataset generated

87a95fa4-9a59-4c69-b83b-9eaf65e4f808

synthetic_generation_completed
Apr 12, 2026, 05:22 PM UTC

dataset generated

03426e89-7f1c-42a3-a085-8e023db0aaf6

synthetic_generation_completed
Apr 12, 2026, 05:22 PM UTC

dataset certified

c09ae65d-bdd5-4afd-8d15-d15c78d7ac69

pro_tier_certification
Apr 12, 2026, 04:49 PM UTC

dataset generated

1ee4699d-8330-4ba5-bc5c-63598ba8c843

synthetic_generation_completed
Apr 12, 2026, 04:49 PM UTC

dataset generated

2e479d8d-7faf-4d2f-940b-ed0964389687

synthetic_generation_completed
Apr 12, 2026, 04:49 PM UTC

dataset certified

2e247698-cdb3-4e23-89db-8e148a5b236e

free_tier_auto_certified
Apr 12, 2026, 04:49 PM UTC

dataset generated

0111890c-f118-40fb-8a57-32d066e9dca7

synthetic_generation_completed
Apr 12, 2026, 04:49 PM UTC

dataset generated

302fe2c4-743e-48d9-8cea-4fc43ccc588d

synthetic_generation_completed
Apr 12, 2026, 04:49 PM UTC

dataset certified

1769fcd5-6049-4cc6-acc9-93a5b6a1160a

team_tier_certification
Apr 12, 2026, 04:49 PM UTC

dataset generated

d5d4a3ac-1976-4bb9-a065-ea1c8ccaa566

synthetic_generation_completed
Apr 12, 2026, 04:49 PM UTC

dataset generated

904c562b-1dba-4bc5-97d3-0edd992d67ef

synthetic_generation_completed
Apr 12, 2026, 04:48 PM UTC

regulatory screening

0d5f627e-4acf-4727-9b10-4862d2e5062e

pep_indicator_detectedidentity_verifiedadverse_media_none
Apr 12, 2026, 03:22 PM UTC

transaction review

9235d647-8b4e-4577-9cef-02dc8aa979e0

velocity_within_thresholdmerchant_category_normalvelocity_threshold_exceeded
Apr 12, 2026, 03:22 PM UTC

credit risk assessment

c1710c3e-307d-42cd-b2a2-3cdfeb9c8ee3

thin_credit_fileincome_verifieddebt_ratio_within_threshold
Apr 12, 2026, 03:22 PM UTC

transaction review

07d4c53c-7e42-4c8f-a797-6e80610cc238

device_recognizedvelocity_within_thresholdamount_within_daily_limit
Apr 12, 2026, 03:22 PM UTC

loan underwriting

0fa530b4-d69c-4e95-b678-5b13a771a428

credit_score_qualifyingdti_acceptablereserves_adequate
Apr 12, 2026, 03:22 PM UTC

content moderation

12cb5546-c8d6-45c7-bcf2-0b03b8ca853d

no_policy_violation_detectedsafe_for_all_audiencesconfidence_above_threshold
Apr 12, 2026, 03:22 PM UTC

dataset certified

291c2749-1c5c-4a29-bd97-669a5f9d326d

enterprise_auto_certified
Apr 12, 2026, 02:31 PM UTC

dataset generated

4da23c19-efa5-44ad-ba55-c16849c40128

synthetic_generation_completed
Apr 12, 2026, 02:31 PM UTC

dataset certified

0f18697c-37ba-449d-8885-903f32bfed2f

free_tier_auto_certified
Apr 12, 2026, 02:31 PM UTC

dataset generated

f091bb78-05b0-48b4-b5b8-47a20e672213

synthetic_generation_completed
Apr 12, 2026, 02:31 PM 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