SETTING GLOBAL STANDARDS FOR TRUSTED AI CREDENTIALSAI Competence Framework v1.29 · current release
You are reading the current version of the framework, v1.29.Permanent address for this version

Extensions

An extension is a set of statements specific to an applied technology, sector or business function. Extensions are how the framework grows: new contexts are served by adding statements, never by modifying core ones.

A credential awarded against version 1.29 does not become invalid because a new sector was added in a later release. That guarantee is the reason extensions exist.

Published 5 · reserved 12 · version 1.29

Published extensions
X-AGTPUBLISHED

Agentic systems

Agentic systems: operating, containing and governing systems that determine their own sequence of actions.

9 statements published

Statements in X-AGT
X-RAGPUBLISHED

Retrieval and grounding

Retrieval and grounding: designing, evaluating and governing systems that answer from retrieved sources.

9 statements published

Statements in X-RAG
X-MODPUBLISHED

Model development

Model development: dataset design, tuning, evaluation and documentation for models built rather than consumed.

9 statements published

Statements in X-MOD
X-GENPUBLISHED

Generative media

Generative media: disclosure, rights and review for synthetic image, audio and video output.

9 statements published

Statements in X-GEN
X-SWEPUBLISHED

Software engineering

Software engineering: review, testing and provenance practice for AI-assisted code.

9 statements published

Statements in X-SWE
Reserved namespaces

Published openly, without dates

Publishing the reserved list signals direction without committing to a timetable, and prevents third parties claiming the codes. Reserved is not planned: a reserved code has a declared subject and no drafting position.

Business function
X-MKTMarketing and sales
X-HRMPeople and hiring
X-LEGLegal and contracting
X-FINFinance
X-CSRCustomer service
X-OPSOperations
Sector
X-HLTHealth and care
X-BFSBanking and financial services
X-EDUEducation
X-PUBPublic sector
X-MFGManufacturing
Technology
X-EMBEmbedded and on-device
Why extensions rather than more domains

Eight domains, indefinitely many contexts

A ninth domain would apply to everyone in every role. Almost nothing proposed as a new domain meets that test; most proposals are contexts, and a context that becomes a domain makes the framework longer for every reader who does not work in it.

Extensions keep the core stable and the addition visible. An extension statement carries its namespace in its identifier, so any credential citing it declares the context it assumes.

How to propose an extension
1State the context and who works in it. An extension serves people in a context, not a product.
2State what core statements already cover, and what they do not reach. A proposal that duplicates core is refused.
3Draft statements against the controlled verb list for their level, with indicators.
4Name an editorial group willing to maintain the extension across versions.
5Submit for public review. Submissions and the response to each are published.

This page displays version 1.29 · last reviewed 30.08.2026