SETTING GLOBAL STANDARDS FOR TRUSTED AI CREDENTIALSAI Competence Framework v1.29 · current release
Explainer

Why statement identifiers are never reused

An identifier is a contract with every credential that cited it. Renumbering would silently change what those credentials claim, years after they were awarded.

A statement identifier is permanent from the moment it is published. It is never renumbered, never reused for a different competence, and resolves for as long as the framework exists. This is the most boring commitment in the specification and probably the most important.

What reuse would do

A credential awarded in 2027 cites a set of identifiers. Its coverage map, its certificate and possibly its regulatory filings all refer to them. If we later reuse one of those identifiers for a different competence, every one of those documents now claims something nobody asserted, and there is no way for a reader in 2031 to tell.

Renumbering for tidiness has the same effect and is more tempting, because it usually happens during a reorganisation that feels like an improvement. A gap in a numbering sequence is not a defect; it is evidence that something was deprecated rather than quietly overwritten.

How change happens instead

A statement whose meaning changes is deprecated and a new identifier carries the new meaning. The deprecated identifier stays published permanently, marked, pointing at its successor where there is one. A reader following an old citation reaches a page that tells them what happened rather than a 404 or, worse, a different competence wearing the same number.

Editorial corrections — a typo, a broken cross-reference, a clarified indicator that does not change what is being asserted — are made in place and published as a dated correction. The test is whether an assessor would judge a candidate differently. If they would, it is a new identifier.

What this article discusses

Framework material referenced

These links run one way. The article points at the specification; the specification does not cite the article as guidance.

D6.L3.04Justify the choice of automated, model-graded or human evaluation for a given task.

Discusses framework version 0.1 · the article itself carries no version

Revision history

No revision since publication

23.08.2026First published.

A notice is never edited. An article may be, and every substantive change appears above with the date it was made.

The author

Ingrid Palm, Registrar

Registrar, AI Certification Standards

Holds the appointed post of Registrar: cuts releases, freezes the dated trees, maintains the deprecation record and administers the register of conformance claims.

Writes the practical guidance on coverage maps and tiers because those are the documents that arrive on this desk incomplete.

Declared interests, in full
AI Certification StandardsDeclared

Employed as Registrar. No economic interest in the organisation, which has no shareholders.

Conformance holdersDeclared

None. Holds no interest in any organisation listed on the register, and none in any applicant.

Cite this article

Ingrid Palm, Registrar (2026) “Why statement identifiers are never reused”, Explainer, AI Certification Standards. Non-normative. Available at aicertificationstandards.org/articles/why-identifiers-are-never-reused (accessed date).

Cite the article as an article. If you need to cite the competence itself, cite the statement: a credential specification or coverage map should reference statement identifiers, never this page.

Article last updated 23.08.2026 · page last reviewed 30.08.2026 · non-normative, not part of any framework version