qodiqa
SpecificationRun a simulation
CoE AI Convention (identification only)

Frameworks · Laws and regulations

qodiqa and the Council of Europe AI Convention

qodiqa checks each AI request before the call and keeps tamper-evident, offline-verifiable evidence. This page shows where that evidence supports the Council of Europe AI Convention, and where it does not.

  • Law
  • Council of Europe
  • Opened for signature 5 Sep 2024.
  • Verified 2026-11-01

Overview

What it is

CoE AI Convention (identification only)
Issuer
Council of Europe
Type
Law
Status
Opened for signature 5 Sep 2024 (Vilnius); entry-into-force status not checked
Official text
rm.coe.int

Council of Europe Framework Convention on Artificial Intelligence and Human Rights, Democracy and the Rule of Law (CETS No. 225). The Framework Convention is a treaty opened for signature at Vilnius on 5 September 2024. It obliges its parties to adopt or maintain measures so that activities across the lifecycle of AI systems respect human rights, democracy and the rule of law, with articles on transparency and oversight, accountability, remedies, procedural safeguards and risk and impact management.

Who it applies to. States that become parties. Public authorities, and private actors acting on their behalf, are covered, and each party chooses how it addresses other private actors. The treaty does not impose duties on a company directly.

Where it meets qodiqa

The parts of the Council of Europe AI Convention where the evidence matters.

Accountability

Records a third party can verify support establishing what happened.

Transparency

A disclosure block on responses supports notifying people that an AI is involved.

Traceability

A per-request record supports documentation of decisions for contestation.

Risk management

Metrics and alerts support monitoring of the system once it is in use.

Robustness and security

Fail-closed checks and signed, single-use artifacts support reliability.

Human oversight

Revocation and a kill switch support the oversight requirements.

Mapping

What qodiqa provides, and what stays with you.

Requirement or controlWhat qodiqa providesWhat stays with you
Art. 8 Transparency and oversight requirements, tailored to context and risk, including identification of AI-generated content.An AI disclosure block on every executed response, and records that oversight bodies can verify.Oversight structures, and labelling of AI-generated content beyond the disclosure block.
Art. 9 Accountability and responsibility for adverse impacts on human rights, democracy and the rule of law.Verifiable records of what was checked and decided, which help establish what happened.Assigning responsibility and answering for impacts.
Art. 12 Reliability: promoting reliability of AI systems and trust in their outputs, including quality and security.Fail-closed enforcement, signed artifacts and a published test-vector set.Quality and reliability of the model and the product.
Art. 14(2)(a)–(b) Remedies: relevant information about AI systems and their use is documented and sufficient for affected persons to contest decisions.A per-request record, signed receipt and evidence bundle that document a decision.The remedies themselves, access for affected people and the complaints route (Art. 14(2)(c)).
Art. 15(2) People interacting with an AI system are notified that they are not dealing with a human.The disclosure block and header on executed responses.Showing the notice in your product.
Art. 16(2)(e)–(f) Risk and impact management: monitoring for risks and adverse impacts, and documentation of risks and the approach.Metrics, alerts and records for monitoring the gateway’s decisions.Identifying and assessing risks and impacts to human rights, and documenting your approach.

The specification’s Regulatory Alignment Matrix does not cover the Council of Europe AI Convention. This page maps the gateway documentation only.

How it fits

What the Council of Europe AI Convention asks, and what qodiqa produces.

  1. Transparency (Art. 8) is supported by AI disclosure block (On every executed response).
  2. Documented decisions (Art. 14(2)) is supported by Receipts and evidence bundles (Per-request records).
  3. Monitoring (Art. 16(2)(e)) is supported by Metrics and alerts (Decisions by reason).

Evidence

Evidence you can hand to an auditor.

Five artifacts, each checkable on its own

  • Consent artifact Signed with Ed25519, bound to one request, single use.
  • INTENT entry The audit entry written before the provider call.
  • Receipt A signed decision record that checks offline.
  • Audit export Hash-chained entries with a Merkle inclusion proof.
  • Anchor proof A signed checkpoint pinned outside the gateway.
Verify offline, from a clone of qodiqa-verify
node bin/verify.bundle.external.js \
  --keys examples/front-half/keys.json \
  --transparency-keys examples/front-half/transparency-keys.json \
  examples/front-half/bundle-with-proof.json

The example files ship with the repository and are signed with throwaway keys. The command exits 0 and prints "valid": true. For your own evidence, take keys and anchors from a source other than the gateway that wrote it.

Scope and limits

Scope and limits

Technical evidence, not a compliance outcome

qodiqa produces verifiable technical evidence that supports parts of the Council of Europe AI Convention. It is not a compliance certification, it is not legal advice, and no regulator or standards body has endorsed it. Whether your use meets the Council of Europe AI Convention is a decision for you and your advisers.

What qodiqa does not address:

  • Ratification and entry-into-force status, which this page does not state.
  • Impact assessments, remedies and procedural safeguards a state or deployer must provide.
  • Which activities fall under the Convention in your jurisdiction.
  • Only requests that pass through the gateway are checked, and a receipt proves a decision was recorded, not that it was correct.

Sources

Sources

Article, clause and control references were read in the official texts listed first. The remaining links are qodiqa’s own documents. Checked on 2026-11-01; rules change, so read the current text.

Next steps

See the evidence for yourself.