AI NATIVE CERTIFICATE / STANDARDS IN DEVELOPMENT
A credential should say exactly what was assessed.
The planned AI Native Certificate will have multiple levels. Their names, evidence requirements and thresholds are not approved yet, and no certificate is issued by this preview.
ASSESSED SNAPSHOT
What the certificate is intended to record.
A future credential should identify the standard and version used, the level reached, assessment scope and date, issuer, and current status. A recipient should be able to check these facts at a direct verification link.
LIVING PROFILE
What can keep growing afterward.
Project records can show business use cases, connected systems, delivery stage and the person's contribution. New work or corrected context belongs in the evolving profile; it must not silently rewrite a past assessment.
01 / LEVELS
More than one level, with clear criteria.
We intend to define multiple levels for developers and automation specialists. Until the standards are approved, we cannot name a level, state its threshold or promise that selected project material will qualify someone.
02 / EVIDENCE
Contribution and quality need context.
Evidence of a CRM automation prototype is different from evidence of a production deployment. A person's decisions, testing, reliability and role should be examined separately from generated output and unsupported outcome claims.
03 / LIMIT
Not an FDE qualification by itself.
Holding an AI Native Certificate alone will not establish readiness for a forward-deployed engineering engagement. Project fit, independent delivery and role-specific evaluation remain separate questions.
SEE THE DISTINCTION