Your members need this. Your quality process will interrogate it.

What you are usually being offered

Tool training with a certificate attached. Content with no assessment model, or an assessment model that tests recall of features rather than demonstrated capability. Claims about outcomes with no evidence behind them, presented in a way that would fail your own academic integrity standards if a student submitted it.

The awkward part is that member demand is real, so the pressure to license something is real too.

What we think holds up

• A defined construct. AI capability specified as seven measurable dimensions plus role overlays, not as a vibe.
• A documented method. A ten-stage workflow design method with published stages, escalation controls within Engineer and Govern, and application contexts — visible in full on this site, not behind a sales call.
• Assessment of demonstrated capability (future). The microcredential is future architecture; when it exists it would assess artefacts, workflow operation, verification decisions and reflection, not attendance. It is not available to enrol in today.
• Explicit claim boundaries. We separate internal method evidence from client field-work evidence and say which is which, using the six evidence terms. Your validation panel will ask this question; the answer is already written down.
• Named limits. Any future microcredential would not imply professional licensure or universal competence, and would say so.

What we are not claiming, and what we can do now

No microcredential exists yet, none is externally accredited or mapped to any framework, and no institution has adopted one — licensing and microcredentials are Future, and facilitator-readiness and cohort-deployment tooling are not finished. What we can do now is a scoped pilot: a defined cohort of your members or students, a real evaluation, and a decision made on evidence from your own context rather than our description of the method.