# VII. CREDENTIALS

## **7.1 Credential Doctrine**

### **7.1.1 Micro-Credentials as Bounded Evidence Records.**

7.1.1.1 **Micro-Credentials** under the Sustainable Competency Framework (SCF) shall mean bounded, evidence-based, scope-limited, reviewable, portable, correctionable, and time-sensitive records of learning, competency, practice, contribution, or role capability within a defined domain, level, method, task, pathway, or public-good context.

7.1.1.2 Micro-Credentials shall not be treated as broad declarations of expertise, professional licenses, degrees, diplomas, statutory qualifications, employment qualifications, procurement qualifications, immigration credentials, public authority credentials, deployment authorizations, or execution permissions by default. Each Micro-Credential shall state what it records, what evidence supports it, who issued or stewarded it, what level it represents, what it does not represent, when it expires or requires renewal where applicable, and how it may be corrected, suspended, withdrawn, or archived.

7.1.1.3 Micro-Credentials shall be tied to the SCF competency ontology, including competency family, domain cluster, level, evidence type, assessment method, review status, issue date, version, expiry or renewal rule where applicable, ILA linkage, Registry linkage where applicable, Marketplace display eligibility where applicable, and boundary notices.

7.1.1.4 Micro-Credentials may support learner progression, WILPs, Foundry contribution, Risk Academy progression, public-safe reporting pathways, reviewer and maintainer pathways, National Skills Maps, National Capability Records, Nexus Universe participation, employer-readable summaries, public-good contributor profiles, and lawful handoff literacy, but shall remain evidence records rather than legal authority.

### **7.1.2 Digital Badges as Display Objects.**

7.1.2.1 **Digital Badges** shall mean display-oriented records used to represent participation, completion, contribution, competency achievement, review role, maintainer pathway, mentorship, public-safe output, WILP participation, Nexus Universe participation, Campaign contribution, Foundry contribution, or other bounded SCF-recognized status.

7.1.2.2 Digital Badges shall be clear, non-misleading, metadata-rich, scope-limited, and correctionable. Badge classes shall distinguish at minimum:\
(a) participation badges;\
(b) completion badges;\
(c) assessment badges;\
(d) competency badges;\
(e) contribution badges;\
(f) reviewer pathway badges;\
(g) maintainer pathway badges;\
(h) mentor pathway badges;\
(i) WILP badges;\
(j) public-safe reporting badges;\
(k) Nexus Universe participation badges;\
(l) archived or historical badges.

7.1.2.3 Digital Badges shall not obscure the difference between attendance, completion, assessment, competence, contribution, role standing, and legal qualification. A badge shall never be designed, titled, displayed, or described in a manner that implies professional licensure, degree status, public authority approval, procurement qualification, financeability, insurability, employment eligibility, community consent, deployment authorization, or execution unless separately and lawfully recorded by a competent authority.

7.1.2.4 Badge display shall be governed by ILA visibility settings, privacy controls, youth protections, public-safe display rules, safeguard review where applicable, and correction or withdrawal mechanisms.

### **7.1.3 Credentialing Without Professional License Overclaim.**

7.1.3.1 SCF credentialing shall provide bounded evidence of learning and competence without representing itself as a professional licensing system unless a separate competent legal or professional authority expressly issues such status under applicable law.

7.1.3.2 SCF shall preserve a strict distinction between:\
(a) learning completion;\
(b) competency evidence;\
(c) Micro-Credential issuance;\
(d) Digital Badge display;\
(e) professional certification;\
(f) statutory qualification;\
(g) public authority credential;\
(h) employment eligibility;\
(i) procurement qualification;\
(j) deployment authorization.

7.1.3.3 No Micro-Credential or Badge shall use language such as “licensed,” “certified professional,” “approved provider,” “official authority,” “public authority qualified,” “deployment-ready,” “procurement-ready,” “finance-ready,” “insurable,” “Nexus-approved,” or equivalent formulations unless such status is separately lawful, separately recorded, narrowly scoped, and approved for use.

7.1.3.4 Where a Micro-Credential references an external standard, occupation, skill taxonomy, educational framework, professional body, or qualification system, the reference shall be framed as mapping, alignment, or relevance only unless formal equivalence has been separately granted by the competent authority.

### **7.1.4 Recognition Without Employment Guarantee.**

7.1.4.1 SCF may recognize learning, contribution, review, mentorship, WILP participation, Foundry work, Campaign work, public-safe reporting, Risk Academy learning, Nexus Universe participation, and National Portfolio contribution through Micro-Credentials, Badges, ILA records, iCRS records, Marketplace display, Registry records, and employer-readable summaries.

7.1.4.2 Such recognition shall support visibility, portability, learner agency, workforce resilience, employer interpretation, public-good contribution, and National Capability Records, but shall not guarantee employment, hiring, interview access, promotion, wage level, work authorization, immigration status, procurement eligibility, professional recognition, or downstream acceptance.

7.1.4.3 Employers, hosts, public authorities, professional bodies, education institutions, credential authorities, procurement bodies, immigration authorities, funders, insurers, and lawful downstream recipients remain responsible for independent diligence, recognition decisions, legal determinations, employment decisions, procurement decisions, and suitability assessments.

7.1.4.4 Recognition shall not be used to mislead learners into believing that SCF credentials alone create labor-market outcomes, legal eligibility, or official status.

### **7.1.5 Verification Without Legal Equivalence by Default.**

7.1.5.1 SCF verification shall mean confirmation that a record exists, was issued by an identified issuer or steward, relates to a defined learner or contributor, contains stated metadata, has a particular status, and is supported by specified evidence within recorded scope.

7.1.5.2 Verification shall not mean that the record is legally equivalent to another credential, recognized by a regulator, accepted by an employer, accepted by a public authority, accepted by a university, accepted for immigration, accepted for procurement, accepted for insurance, accepted for finance, or accepted for deployment.

7.1.5.3 Digital verification may confirm authenticity, issuer identity, record integrity, expiry, revocation, suspension, correction history, and evidence links. It shall not expand the credential’s scope or convert a bounded learning record into a legal qualification.

7.1.5.4 Every verification interface shall include appropriate public-safe notices and non-equivalence statements where a reasonable user could misunderstand the record.

### **7.1.6 Credential Portability With Jurisdictional Limits.**

7.1.6.1 SCF credentials shall be designed for technical, semantic, and learner-controlled portability where feasible, including use through the ILA, Skills Wallet, employer-readable summaries, Registry-linked records, Marketplace profiles, and exportable records.

7.1.6.2 Portability shall remain subject to jurisdictional law, data protection, data sovereignty, credential recognition rules, professional licensing rules, public authority rules, language localization, translation accuracy, youth protections, sensitive profile controls, protected knowledge restrictions, sanctions, export-control concerns, and conflict-of-law review where applicable.

7.1.6.3 A credential that is portable in data form shall not be legally portable as qualification by default. Recognition, equivalence, credit transfer, professional status, employment status, procurement status, immigration relevance, or public authority relevance must be separately determined by the competent receiving actor.

7.1.6.4 Cross-border credential display shall include jurisdictional limitation notices, source-context metadata, translation status where applicable, and non-equivalence language.

### **7.1.7 Credential Correctionability.**

7.1.7.1 Every SCF credential shall be correctionable. Correctionability shall apply to errors, outdated records, misleading descriptions, incorrect metadata, wrong competency mapping, inaccurate evidence links, privacy violations, public-safe overclaims, safeguard issues, issuer errors, assessment integrity issues, display errors, and misuse.

7.1.7.2 Correction actions may include metadata correction, evidence update, public-safe language correction, addendum, scope clarification, expiry update, downgrade, suspension, withdrawal, revocation where necessary, reissue, public repair, archive, or non-continuation.

7.1.7.3 Credential correction shall propagate where applicable to ILA records, Skills Wallet displays, Registry records, Marketplace profiles, employer-readable summaries, National Portfolio summaries, public-good contributor displays, and exported verification links.

7.1.7.4 Correction shall be treated as trust infrastructure. A credential system that cannot correct itself shall not be considered trustworthy within SCF.

### **7.1.8 Credential Archive.**

7.1.8.1 Every SCF credential shall carry archive rules. Credential archive shall preserve historical record integrity while preventing outdated, withdrawn, superseded, revoked, suspended, or non-continuing credentials from being mistaken for current status.

7.1.8.2 Archive records shall include credential name, version, issuer, date issued, date archived, archive reason, current status, correction history, successor credential where applicable, expiry or withdrawal status, evidence retention status, public-safe notice, and not-current notice.

7.1.8.3 Archived credentials may remain visible in private ILA records, controlled records, or verification history where necessary, but public display shall be restricted or clearly labeled where current reliance would be misleading.

7.1.8.4 Archive shall not erase responsibility for correction, misuse handling, privacy compliance, safeguard obligations, or public repair where required.

***

## **7.2 Micro-Credential Classes**

### **7.2.1 Foundational Literacy Credentials.**

7.2.1.1 **Foundational Literacy Credentials** may recognize basic awareness or literacy in Nexus doctrine, SCF, public-good principles, non-execution, validity by record, correctionability, no-conversion, public-safe communication, data literacy, AI literacy, cyber hygiene, privacy basics, risk literacy, WFEH-B introduction, DRR introduction, DRI introduction, accessibility, safeguard awareness, and lawful handoff basics.

7.2.1.2 Foundational Literacy Credentials shall be expressly limited to introductory or baseline learning. They shall not represent applied technical competence, professional qualification, public authority competence, review authority, maintainer status, or deployment capability.

7.2.1.3 These credentials may support entry into further pathways, WILPs, Campaigns, Foundry orientation, National Portfolio pathways, and Nexus Universe preparation, subject to additional requirements where applicable.

### **7.2.2 Technical Skills Credentials.**

7.2.2.1 **Technical Skills Credentials** may recognize bounded technical competencies in software, data, dashboards, APIs, SDKs, connectors, reproducibility packages, public-good repositories, documentation, secure software basics, digital twins, simulation, geospatial analysis, Earth observation, telecom literacy, edge systems, cloud, HPC, sensors, robotics, drones, or related Nexus technical domains.

7.2.2.2 Technical Skills Credentials shall state tool scope, method scope, data scope, system scope, level, evidence basis, supervision level, review status, and limitations.

7.2.2.3 Technical Skills Credentials shall not authorize production deployment, access to restricted systems, safety-critical work, regulated engineering practice, cybersecurity certification, public authority operations, procurement status, or execution.

### **7.2.3 Data and AI Credentials.**

7.2.3.1 **Data and AI Credentials** may recognize competencies in data stewardship, metadata, lineage, data quality, data-use labels, AI-use labels, privacy-aware data handling, compute-to-data literacy, model cards, system cards, benchmark cards, AI evaluation, prompt-injection awareness, human review, bias and harm review, agentic workflow controls, AI incident escalation, and public-safe AI output review.

7.2.3.2 Data and AI Credentials shall identify whether the credential concerns literacy, applied practice, supervised contribution, independent contribution, review capability, or maintainer capability.

7.2.3.3 Data and AI Credentials shall not create data access rights, AI safety certification, model approval, automated decision authority, deployment authorization, public authority decision authority, financeability, insurability, procurement readiness, or execution authority.

### **7.2.4 Cyber and Privacy Credentials.**

7.2.4.1 **Cyber and Privacy Credentials** may recognize competencies in cyber hygiene, identity and access management literacy, secure collaboration, secure software basics, SBOM literacy, dependency awareness, vulnerability disclosure literacy, incident response literacy, privacy principles, consent, data minimization, purpose limitation, sensitive data handling, youth data protection, health data protection, community data protection, cross-border data literacy, and data incident escalation.

7.2.4.2 Cyber and Privacy Credentials shall distinguish literacy from technical practice, technical practice from professional certification, and professional certification from statutory authority.

7.2.4.3 Cyber and Privacy Credentials shall not constitute security certification, privacy compliance determination, legal compliance opinion, penetration testing authorization, operational cyber authority, public warning authority, or public authority approval.

### **7.2.5 WFEH-B Credentials.**

7.2.5.1 **WFEH-B Credentials** may recognize competencies related to water, food, energy, health, biodiversity, nature systems, cross-system dependencies, climate resilience, public-safe systems communication, data interpretation, infrastructure dependencies, and cascading-risk awareness.

7.2.5.2 WFEH-B Credentials shall state the domain, system boundary, evidence basis, learning level, and limitations. They may support National Portfolio pathways, Risk Academy learning, Campaigns, Foundry work, Studio exercises, Reports, and Nexus Universe participation.

7.2.5.3 WFEH-B Credentials shall not create public health authority, environmental approval, official planning authority, procurement preference, project authorization, community consent, or operational authority.

### **7.2.6 DRR Credentials.**

7.2.6.1 **DRR Credentials** may recognize competencies in disaster risk reduction literacy, hazard exposure, vulnerability, preparedness, mitigation, resilience, public-safe communication, after-action learning, community resilience, and multi-hazard awareness.

7.2.6.2 DRR Credentials may support participation in Risk Academy, National Portfolios, public authority learning rooms, Campaigns, DRI interpretation, Studio exercises, Nexus Universe arenas, and lawful handoff literacy.

7.2.6.3 DRR Credentials shall not create emergency response authority, public warning authority, public authority approval, official hazard classification authority, emergency command authority, or deployment authorization.

### **7.2.7 DRF Literacy Credentials.**

7.2.7.1 **DRF Literacy Credentials** may recognize bounded literacy in disaster risk finance concepts, protection gaps, risk layering, assumptions registers, dependency registers, diligence-gap registers, insurance-readiness questions, donor-readiness questions, public finance relevance questions, no-reliance principles, non-solicitation, non-transactionality, and regulated-perimeter discipline.

7.2.7.2 DRF Literacy Credentials shall be expressly literacy credentials unless separately classified otherwise. They shall not authorize financial advice, insurance advice, underwriting, brokerage, lending, guarantee issuance, rating, securities activity, donor allocation, public finance allocation, or transaction execution.

7.2.7.3 DRF Literacy Credentials may support public authority learning, National Investors Council literacy, capital-reader room preparation, insurance-reader room preparation, donor-reader room preparation, and handoff dependency understanding.

### **7.2.8 DRI Credentials.**

7.2.8.1 **DRI Credentials** may recognize competencies in disaster risk intelligence literacy, indicator interpretation, signal interpretation, uncertainty labels, confidence labels, dashboard interpretation, hotspot records, multi-hazard records, cascade records, public-safe intelligence summaries, no-warning communication, no-rating communication, correction, and archive.

7.2.8.2 DRI Credentials shall distinguish learning, interpretation, review, and contribution capability from public warning authority or official intelligence authority.

7.2.8.3 DRI Credentials shall not create public warning authority, forecast authority, emergency command authority, insurance score authority, investment signal authority, public authority decision authority, or official rating authority.

### **7.2.9 Public-Safe Reporting Credentials.**

7.2.9.1 **Public-Safe Reporting Credentials** may recognize competencies in evidence translation, no-warning language, no-approval language, no-finance language, no-procurement language, no-certification language, no-consent language, no-execution language, protected knowledge controls, sensitive data controls, public repair, correction notices, and archive labels.

7.2.9.2 Public-Safe Reporting Credentials may support roles in Reports, Campaigns, Marketplace, Registry, DRI summaries, Observatory summaries, National Portfolio summaries, Nexus Universe outputs, and handoff notes.

7.2.9.3 Public-Safe Reporting Credentials shall not create official communication authority, public warning authority, public authority approval, media authority, institutional spokesperson authority, or endorsement authority.

### **7.2.10 Safeguard Credentials.**

7.2.10.1 **Safeguard Credentials** may recognize competencies in community safeguards, Indigenous protocols where applicable, protected knowledge controls, youth safeguards, disability inclusion, accessibility, humanitarian sensitivity, non-extractive engagement, privacy-sensitive participation, sensitive geospatial controls, and community-facing correction.

7.2.10.2 Safeguard Credentials shall be carefully scoped and shall not be used to imply representation authority, community consent, Indigenous authorization, protected knowledge permission, public authority approval, ethics-board approval, or deployment authorization.

7.2.10.3 Safeguard Credentials may support participation in public-safe review, Campaign governance, WILP design, field exercises, Reports review, National Portfolio work, Nexus Universe rooms, and handoff dependency review.

### **7.2.11 Foundry Contributor Credentials.**

7.2.11.1 **Foundry Contributor Credentials** may recognize competencies in quests, bounties, builds, micro-production, documentation, testing, data contribution, software contribution, dashboard work, Studio workflow contribution, Marketplace object preparation, Registry record preparation, Grid input preparation, TRL evidence notes, Reports contribution, Campaign builds, National Portfolio builds, and handoff dependency packages.

7.2.11.2 Foundry Contributor Credentials shall distinguish participation, contribution, accepted contribution, reviewed contribution, maintainer-reviewed contribution, and maintainer capability.

7.2.11.3 Foundry Contributor Credentials shall not create employment, compensation entitlement, procurement qualification, provider validation, product certification, deployment authorization, ownership, or execution authority.

### **7.2.12 Reviewer and Maintainer Credentials.**

7.2.12.1 **Reviewer and Maintainer Credentials** may recognize bounded capability to review, maintain, steward, correct, or archive specific classes of learning objects, data objects, software objects, AI-use records, public-safe outputs, safeguard-sensitive objects, Marketplace listings, Registry records, Studio workflows, Grid inputs, TRL notes, or handoff-context records.

7.2.12.2 Reviewer and Maintainer Credentials shall state the object class, domain, level, review authority within SCF, conflict rules, renewal requirements, suspension rules, withdrawal rules, and limitations.

7.2.12.3 Reviewer and Maintainer Credentials shall not create professional license, public authority approval, external certification authority, procurement authority, legal compliance authority, deployment authorization, or execution authority.

### **7.2.13 Risk Agency Pathway Credentials.**

7.2.13.1 **Risk Agency Pathway Credentials** may recognize pathway completion or readiness for scoped expert routing, advisory support, training support, public-safe reporting support, capacity-building support, cross-sphere translation, risk interpretation, community translation, safeguard advisory, or handoff support.

7.2.13.2 Risk Agency Pathway Credentials shall include reliance labels, advisory boundaries, conflict rules, professional-license boundaries, public authority boundaries, finance and insurance boundaries, and community-consent boundaries.

7.2.13.3 Risk Agency Pathway Credentials shall not create professional license, advisor licensure, investment advice authority, insurance advice authority, underwriting authority, public authority decision authority, legal advice authority, consent authority, or execution authority.

### **7.2.14 Handoff Literacy Credentials.**

7.2.14.1 **Handoff Literacy Credentials** may recognize competencies in lawful handoff context, dependency packages, recipient responsibility, public-good stack and enterprise-stack separation, public authority dependencies, legal dependencies, data dependencies, safeguard dependencies, finance and insurance questions, procurement neutrality, provider-neutrality notes, sponsor-boundary notes, correction, recall, and archive.

7.2.14.2 Handoff Literacy Credentials may support learners, contributors, reviewers, public authority learning participants, National Working Groups, Competence Cells, Foundry teams, National Consortium Companies, Project SPVs, providers, operators, funders, insurers, donors, and other lawful downstream actors in understanding handoff boundaries.

7.2.14.3 Handoff Literacy Credentials shall not create handoff approval, implementation authorization, procurement recommendation, investment advice, insurance approval, public finance allocation, public authority action, community consent, deployment authorization, operations authority, or execution.

***

## **7.3 Credential Evidence Requirements**

### **7.3.1 Learning Completion Evidence.**

7.3.1.1 **Learning Completion Evidence** shall document completion of courses, modules, lessons, labs, scenarios, simulations, Studio exercises, public-safe reporting exercises, field exercises, or other learning objects.

7.3.1.2 Learning Completion Evidence shall include learning object identity, version, completion date, learner identity or account linkage, completion criteria, assessment requirement where applicable, instructor or platform verification where applicable, AI-use status where relevant, and correction pathway.

7.3.1.3 Completion evidence alone shall not be represented as competence unless the credential expressly states that completion has been assessed against defined competency criteria.

### **7.3.2 Assessment Evidence.**

7.3.2.1 **Assessment Evidence** shall document performance against defined criteria, including quizzes, exams, practical exercises, simulations, portfolio assessments, Studio exercises, field evaluations, oral reviews, peer assessments, mentor assessments, host assessments, or rubric-based reviews.

7.3.2.2 Assessment Evidence shall identify assessment method, criteria, assessor or automated-support use where applicable, human review status, date, score or qualitative outcome where appropriate, limitations, appeal pathway, and correction pathway.

7.3.2.3 Assessment Evidence shall not be used for automated high-stakes ranking, employment decisioning, public authority decisioning, or procurement qualification by default.

### **7.3.3 Work Product Evidence.**

7.3.3.1 **Work Product Evidence** shall include artifacts produced by the learner or contributor, including reports, code, data objects, metadata, dashboards, models, system cards, benchmark cards, public-safe summaries, Studio workflows, Campaign materials, Registry records, Marketplace listings, Grid inputs, TRL notes, National Portfolio objects, or handoff dependency notes.

7.3.3.2 Work Product Evidence shall include scope, contribution role, review status, version, attribution, license or rights status, public-safe status, data-use label, AI-use label where applicable, support class, correction history, and archive rule.

7.3.3.3 Work Product Evidence shall not create employment, ownership, professional qualification, certification, procurement readiness, deployment authorization, or execution.

### **7.3.4 Simulation or Studio Evidence.**

7.3.4.1 **Simulation or Studio Evidence** shall document learner performance or participation in controlled runtime environments, scenarios, digital twins, dashboards, AI workflow reviews, secure rooms, data rooms, public authority learning rooms, readiness rooms, Nexus Universe workflows, or handoff demonstrations.

7.3.4.2 Simulation or Studio Evidence shall state scenario scope, model basis, data basis, assumptions, limitations, uncertainty, confidence where applicable, participant role, output review, and no-decision status.

7.3.4.3 Simulation or Studio Evidence shall not create forecast certainty, public authority decision, certification, deployment authorization, financeability, insurability, or execution authority.

### **7.3.5 Peer Review Evidence.**

7.3.5.1 **Peer Review Evidence** shall document review by peers, contributors, reviewers, maintainers, faculty, or domain participants within defined criteria and conflict rules.

7.3.5.2 Peer Review Evidence shall identify reviewer role, review scope, review criteria, conflicts, date, outcome, required correction, limitations, and archive status.

7.3.5.3 Peer Review Evidence shall support learning and quality assurance but shall not constitute certification, professional license, public authority approval, procurement approval, or endorsement by default.

### **7.3.6 Mentor Verification Evidence.**

7.3.6.1 **Mentor Verification Evidence** shall document mentor observations, supervision, feedback, progression, practice quality, reflection, correction, and readiness for next learning or contribution steps.

7.3.6.2 Mentor Verification Evidence shall state mentor identity or role, relationship to learner, pathway, scope, date, supervision level, conflicts where relevant, and limitations.

7.3.6.3 Mentor Verification Evidence shall not create employment verification, professional supervision status, legal guardianship, official qualification, public authority approval, or deployment authorization.

### **7.3.7 Host or Employer Evidence.**

7.3.7.1 **Host or Employer Evidence** may document WILP participation, hosted practice, workplace learning, fieldwork, employer feedback, host verification, task completion, safety compliance, teamwork, applied practice, or work product acceptance within scope.

7.3.7.2 Host or Employer Evidence shall state host identity, role, scope, workplan, period, supervision level, evidence basis, conflicts, limitations, and whether the record is learning evidence, work evidence, or separately contracted work evidence.

7.3.7.3 Host or Employer Evidence shall not create employment status, hiring commitment, wage entitlement, background verification, professional license, procurement qualification, public authority approval, or endorsement by default.

### **7.3.8 Public-Good Contribution Evidence.**

7.3.8.1 **Public-Good Contribution Evidence** shall document learner or contributor participation in public-good work, including Foundry builds, Campaigns, Reports, data commons, software commons, GRIx, DRI, Observatory, Marketplace, Registry, Studio, Grid, Nexus Universe, National Portfolios, translation, accessibility, documentation, review, mentorship, and correction.

7.3.8.2 Public-Good Contribution Evidence shall identify contribution type, contribution scope, accepted output, review status, attribution, license or terms, iCRS linkage where applicable, support class, correction history, and display permissions.

7.3.8.3 Public-Good Contribution Evidence shall not create employment, compensation, procurement qualification, provider validation, sponsor endorsement, ownership transfer, public authority approval, or execution.

### **7.3.9 Correction Evidence.**

7.3.9.1 **Correction Evidence** shall document the learner’s or contributor’s responsible identification, escalation, repair, revision, withdrawal, addendum, public repair, archive, or non-continuation of inaccurate, outdated, misleading, unsafe, biased, overclaimed, or boundary-violating work.

7.3.9.2 Correction Evidence may be used positively as evidence of judgment, integrity, public-good discipline, review capability, maintainer capability, and trustworthiness.

7.3.9.3 Correction Evidence shall not be used unfairly to punish learners for responsible correction. However, repeated negligent, reckless, deceptive, or harmful conduct may trigger credential review, suspension, withdrawal, or incident handling.

### **7.3.10 Expiry and Renewal Evidence.**

7.3.10.1 Credentials shall include expiry or renewal rules where the competency is time-sensitive, technology-sensitive, risk-sensitive, regulation-sensitive, safety-sensitive, data-sensitive, AI-sensitive, cyber-sensitive, safeguard-sensitive, or dependent on ongoing practice.

7.3.10.2 **Renewal Evidence** may include refresher learning, updated assessments, practice evidence, recent contribution, reviewer confirmation, maintainer confirmation, public-safe review, updated safeguard review, updated AI or cyber review, or correction of outdated materials.

7.3.10.3 Expired credentials shall not be displayed as current. They may remain archived with not-current notices and renewal pathways where appropriate.

***

## **7.4 Digital Verification**

### **7.4.1 Verifiable Credential Records.**

7.4.1.1 SCF may support **Verifiable Credential Records** where technical verification improves trust, portability, integrity, learner control, or cross-system interoperability.

7.4.1.2 Verifiable Credential Records shall include issuer identity, learner subject, credential type, credential scope, issue date, expiry where applicable, evidence links where appropriate, revocation or suspension status, correction history, privacy controls, and verification method.

7.4.1.3 Verification shall prove record authenticity and status within scope; it shall not create legal equivalence, professional license, employment guarantee, public authority approval, procurement qualification, financeability, insurability, deployment authorization, or execution.

### **7.4.2 Digital Badge Metadata.**

7.4.2.1 Digital Badge metadata shall include badge title, badge class, description, issuer, criteria, evidence basis, competency mapping, issue date, expiry where applicable, version, status, display permissions, revocation or suspension status, correction link, and boundary notices.

7.4.2.2 Badge metadata shall avoid inflated or ambiguous claims. Badge visuals and titles shall not imply more than the metadata supports.

7.4.2.3 Where badges are displayed outside SCF systems, metadata shall preserve scope, limitations, and correction links where feasible.

### **7.4.3 Issuer Identity.**

7.4.3.1 Every SCF credential shall identify its issuer or steward. Issuer identity shall include the issuing institution, pathway, program, department, authorized role, or governance body responsible for issuance within scope.

7.4.3.2 Issuer identity shall not imply endorsement by all Nexus institutions. A credential issued within one pathway, Academy, National Node, Foundry program, Risk Academy track, or credential stewardship process shall not be represented as universal approval by GCRI, The Global Risks Forum, The Global Risks Alliance, public authorities, sponsors, providers, employers, or National Consortiums.

7.4.3.3 Issuer authority shall be bounded, recorded, auditable, and correctionable.

### **7.4.4 Evidence Links.**

7.4.4.1 Digital credentials may include evidence links to assessments, portfolio artifacts, WILP records, contribution records, public-safe outputs, review records, mentor records, host records, Registry records, Marketplace objects, Reports, or archived evidence.

7.4.4.2 Evidence links shall respect privacy, consent, intellectual property, protected knowledge, sensitive data, youth protection, access controls, and public-safe display restrictions.

7.4.4.3 Absence of public evidence links shall not invalidate a credential where evidence is properly held in controlled records. Public evidence links shall not expose restricted information.

### **7.4.5 Expiry and Renewal.**

7.4.5.1 Digital verification shall clearly display whether a credential is current, expired, renewed, pending renewal, suspended, withdrawn, revoked, superseded, archived, or non-continuing.

7.4.5.2 Renewal rules shall be visible before issuance where feasible and shall state whether renewal requires updated learning, assessment, practice, contribution, review, safeguarding, or correction.

7.4.5.3 Expiry shall be treated as lifecycle governance, not personal failure. It shall reflect that certain competencies require refresh due to changing technology, risk, law, public-safe practice, standards, or institutional context.

### **7.4.6 Revocation and Suspension.**

7.4.6.1 Credentials may be suspended or revoked where there is material error, fraud, assessment integrity failure, misuse, overclaim, public-safe risk, safeguard breach, data misuse, AI misuse, credential misuse, issuer error, or other serious governance issue.

7.4.6.2 Suspension shall indicate that a credential is under review or temporarily inactive. Revocation shall indicate that the credential is no longer valid within scope and should not be relied upon as current evidence.

7.4.6.3 Revocation and suspension processes shall include notice where appropriate, record update, correction pathway, appeal or review where applicable, public-safe display update, Registry update where applicable, Marketplace update where applicable, and archive.

### **7.4.7 Correction History.**

7.4.7.1 Digital credential systems shall preserve correction history sufficient to maintain trust, transparency, and status truth.

7.4.7.2 Correction history may include metadata corrections, evidence corrections, scope clarifications, title corrections, status updates, expiry updates, public-safe corrections, suspension, reinstatement, withdrawal, revocation, reissue, supersession, archive, and public repair.

7.4.7.3 Public correction display shall balance transparency, privacy, fairness, youth protection, and public-safe needs.

### **7.4.8 Privacy-Preserving Display.**

7.4.8.1 Digital verification shall support privacy-preserving display, including minimal disclosure, selective disclosure, controlled sharing, learner-controlled export, restricted evidence links, anonymized or pseudonymized display where appropriate, and non-public verification channels.

7.4.8.2 Credential displays shall avoid unnecessary exposure of birth date, legal name where not required, address, sensitive profile data, disability status, youth status, health information, community affiliation, Indigenous affiliation where applicable, protected knowledge, or sensitive contribution details.

7.4.8.3 Privacy-preserving display shall not be used to obscure material limitations, expiry, suspension, revocation, or correction status.

### **7.4.9 Offline and Low-Bandwidth Verification.**

7.4.9.1 SCF should support offline and low-bandwidth verification where feasible to enable use in rural, remote, disaster-affected, low-connectivity, field, humanitarian, and infrastructure-constrained contexts.

7.4.9.2 Offline or low-bandwidth verification may include downloadable credential packages, QR codes, signed metadata, printable summaries, lightweight verification pages, and delayed synchronization.

7.4.9.3 Offline verification shall include freshness limits, status-check notices, revocation-check limitations, and instructions for confirming current status when connectivity is available.

### **7.4.10 Public-Safe Verification Notices.**

7.4.10.1 Verification interfaces shall include public-safe notices where needed, including no-license, no-degree, no-employment-guarantee, no-procurement, no-public-authority, no-finance, no-insurance, no-consent, no-deployment, no-execution, and non-equivalence notices.

7.4.10.2 Notices shall be written plainly enough for learners, employers, hosts, public authorities, communities, sponsors, providers, funders, insurers, donors, and downstream actors to understand.

7.4.10.3 Where a credential is likely to be misunderstood, SCF shall require stronger boundary wording, controlled display, or restricted verification.

***

## **7.5 Recognition of Prior Learning**

### **7.5.1 RPL Intake.**

7.5.1.1 **Recognition of Prior Learning (RPL)** under SCF shall mean the structured intake, review, mapping, and evidence-based recognition of competencies acquired through prior education, work, informal learning, community practice, public service, military service, emergency response, humanitarian work, self-directed learning, open-source contribution, caregiving, entrepreneurship, migration experience, diaspora expertise, or lived-risk experience.

7.5.1.2 RPL intake shall record applicant identity, claimed competencies, evidence sources, jurisdictional context, language context, data permissions, sensitive information controls, safeguard issues, desired credential or pathway, review requirements, bridge learning needs, and correction or appeal pathway.

7.5.1.3 RPL shall not automatically convert experience into credential status. It shall require evidence, mapping, review, and bounded recognition.

### **7.5.2 Work Experience Evidence.**

7.5.2.1 Work experience evidence may include employer records, contracts, work samples, supervisor attestations, project records, safety records, client records where lawful, portfolios, public outputs, professional references, union or worker organization records, cooperative records, and self-employment records.

7.5.2.2 Work experience evidence shall be reviewed for relevance, authenticity, scope, recency, context, level, independence, supervision, and transferability.

7.5.2.3 Work experience evidence shall not create employment verification, legal work authorization, wage claim, professional license, or procurement qualification by default.

### **7.5.3 Informal Learning Evidence.**

7.5.3.1 Informal learning evidence may include self-directed study, community learning, online learning, open-source participation, volunteer work, peer learning, family enterprise work, care work, informal apprenticeship, platform work, civic participation, and practical experience.

7.5.3.2 Informal learning evidence shall be treated with seriousness and fairness, especially where formal credentials are inaccessible, but it shall still be mapped to competencies and reviewed within scope.

7.5.3.3 Informal learning recognition shall not erase the need for bridge learning where safety, public authority, data, AI, cyber, safeguard, or regulated-domain issues are present.

### **7.5.4 Community Knowledge Evidence.**

7.5.4.1 Community knowledge evidence may include place-based knowledge, lived-risk knowledge, community resilience practice, local environmental knowledge, public health practice, mutual aid experience, disaster experience, accessibility practice, diaspora knowledge, and protected knowledge where lawfully and ethically shareable.

7.5.4.2 Community knowledge evidence shall be handled through non-extractive, respectful, consent-aware, safeguard-reviewed, and protected knowledge-sensitive processes.

7.5.4.3 Community knowledge recognition shall not convert community participation into consent, representation authority, Indigenous authorization, protected knowledge permission, public authority approval, or deployment authorization.

### **7.5.5 Military, Emergency, Humanitarian, and Public Service Experience.**

7.5.5.1 RPL may recognize competencies developed through military service, emergency services, humanitarian response, civil protection, public service, public health response, crisis management, infrastructure operations, logistics, communications, field operations, or after-action learning.

7.5.5.2 Such experience shall be reviewed for transferable competencies, safety-critical boundaries, confidentiality restrictions, security restrictions, trauma sensitivity, public-safe output requirements, and jurisdictional limits.

7.5.5.3 Recognition shall not create current operational authority, emergency command authority, security clearance, public authority status, regulated professional status, or deployment authorization.

### **7.5.6 Migrant and Refugee Skill Recognition.**

7.5.6.1 SCF shall support fair recognition pathways for migrants, refugees, displaced persons, diaspora talent, and cross-border learners whose prior learning, work history, documentation, language, or credential recognition may be disrupted or difficult to verify.

7.5.6.2 Recognition pathways may include portfolio-based assessment, practical assessment, interview, peer review, mentor review, bridge learning, translation review, contextual evidence, and controlled verification.

7.5.6.3 RPL for migrants and refugees shall protect privacy, legal sensitivity, safety, dignity, and non-discrimination. It shall not create immigration status, work authorization, asylum determination, legal equivalence, professional licensing, or public authority approval by default.

### **7.5.7 Portfolio-Based Assessment.**

7.5.7.1 Portfolio-based assessment may be used where formal documentation is incomplete, unavailable, non-comparable, unsafe to provide, or insufficient to capture real competence.

7.5.7.2 Portfolio assessment may include work products, explanations, reflections, demonstrations, simulations, interviews, field evidence, community evidence, open-source contributions, public-safe outputs, and correction records.

7.5.7.3 Portfolio assessment shall be structured, rubric-based where feasible, reviewer-governed, conflict-managed, accessible, and appealable where appropriate.

### **7.5.8 Bridge Learning Requirements.**

7.5.8.1 Where RPL evidence demonstrates partial competence but gaps remain, SCF may require bridge learning before issuing a credential, advancing a learner, permitting display, or recognizing a pathway.

7.5.8.2 Bridge learning may address local law, public-safe reporting, safeguards, data protection, AI-use controls, cyber controls, WFEH-B context, DRR, DRI, public authority boundaries, finance-readiness boundaries, procurement neutrality, language, accessibility, or Nexus-specific mechanisms.

7.5.8.3 Bridge learning shall be designed to close gaps without unnecessarily repeating what the learner already knows.

### **7.5.9 RPL Correction and Appeal.**

7.5.9.1 RPL applicants shall have access to correction and appeal pathways where evidence is misunderstood, records are incomplete, translation is inaccurate, competence is misclassified, bridge learning is excessive, display is misleading, or recognition is denied.

7.5.9.2 RPL correction may include record correction, additional evidence submission, reassessment, alternate assessment, reviewer reassignment, translation correction, safeguard correction, and appeal review.

7.5.9.3 RPL appeals shall be recorded and resolved with fairness, transparency, and boundary discipline.

### **7.5.10 RPL Boundary Rules.**

7.5.10.1 RPL shall not create legal equivalence, professional license, employment guarantee, wage entitlement, immigration status, procurement qualification, public authority approval, deployment authorization, or execution by default.

7.5.10.2 RPL recognition shall remain bounded to the credential, competency, pathway, or evidence record issued within SCF.

7.5.10.3 RPL shall not extract, expose, or misuse community knowledge, protected knowledge, sensitive personal history, migration history, trauma history, or confidential work experience.

***

## **7.6 Credential Governance**

### **7.6.1 Issuer Governance.**

7.6.1.1 Credential issuers under SCF shall be authorized, recorded, scoped, reviewed, and accountable for the credentials they issue.

7.6.1.2 Issuer governance shall define eligible issuers, issuer scope, issuer approval, issuer renewal, issuer conflicts, issuer suspension, issuer withdrawal, credential classes, evidence requirements, assessment requirements, display rules, correction obligations, and archive obligations.

7.6.1.3 Issuers shall not issue credentials outside their authorized scope. Issuer status shall not imply universal authority, public authority status, professional licensing authority, procurement authority, or execution authority.

### **7.6.2 Assessor Governance.**

7.6.2.1 Assessors shall be authorized for specific assessment scopes, competency families, levels, methods, domains, and risk classes.

7.6.2.2 Assessor governance shall include assessor qualification records, training, conflict disclosure, bias awareness, accessibility obligations, youth safeguards where applicable, data and AI-use controls, rubric discipline, appeal pathways, correction, and renewal.

7.6.2.3 AI-supported assessment may assist but shall not replace human judgment for high-stakes credentialing by default.

### **7.6.3 Reviewer Governance.**

7.6.3.1 Reviewers shall be governed by scope, competency, evidence type, public-safe obligations, safeguard obligations, conflict rules, review criteria, escalation rules, correction duties, and renewal requirements.

7.6.3.2 Reviewer standing may be recorded through ILA, Registry, or controlled governance records, but shall not create professional license, external certification authority, public authority approval, or procurement authority.

7.6.3.3 Reviewer misconduct, conflict concealment, negligent review, biased review, public-safe failure, or credential misuse shall trigger review, correction, suspension, or withdrawal where appropriate.

### **7.6.4 Conflict Management.**

7.6.4.1 Credential governance shall require disclosure and management of actual, potential, and perceived conflicts involving issuers, assessors, reviewers, mentors, hosts, employers, sponsors, providers, public authority participants, funders, National Consortiums, National Companies, Project SPVs, and downstream recipients.

7.6.4.2 Conflicts may be financial, institutional, professional, personal, political, sponsor-related, provider-related, employer-related, public authority-related, or role-based.

7.6.4.3 Conflict controls may include disclosure, recusal, independent review, second review, restricted display, credential hold, correction, suspension, or withdrawal.

### **7.6.5 Sponsor and Provider Controls.**

7.6.5.1 Sponsors and providers may support learning, platforms, infrastructure, scholarships, content, expertise, tools, datasets, labs, or pathways only under support-without-control and contribution-without-validation rules.

7.6.5.2 Sponsor support shall not control credential criteria, credential issuance, learner selection, assessment outcome, public display, Registry status, Marketplace visibility, procurement routing, or public authority interpretation.

7.6.5.3 Provider contribution shall not validate the provider, certify its products, create procurement preference, imply endorsement, or convert a credential into vendor qualification by default.

### **7.6.6 Public Authority Boundary Controls.**

7.6.6.1 Public authority participation in credential design, review, learning, public authority learning rooms, WILPs, Nexus Universe, or National Portfolio contexts shall not convert SCF credentials into public authority credentials, statutory training, public approval, procurement eligibility, licensing, public finance eligibility, emergency command authority, or official recognition by default.

7.6.6.2 Where a public authority separately adopts or recognizes a credential, that action must be expressly recorded by the competent authority and must not be implied from participation.

7.6.6.3 Public authority boundary notices shall be required for credentials likely to be misunderstood as official public authority training or approval.

### **7.6.7 Quality Assurance.**

7.6.7.1 Credential quality assurance shall include competency mapping, evidence sufficiency, assessment validity, review integrity, accessibility, fairness, privacy, data governance, AI-use governance, public-safe display, safeguard review, issuer governance, assessor governance, conflict management, correction, and archive.

7.6.7.2 Quality assurance shall be proportionate to risk. Credentials involving AI, data, cyber, privacy, public authority learning, finance-readiness, insurance-readiness, DRR, DRI, public-safe reporting, protected knowledge, youth, health, biosecurity-sensitive topics, fieldwork, or safety-sensitive domains shall require heightened review.

7.6.7.3 Quality assurance within SCF shall not be represented as external certification, accreditation, regulatory approval, or professional licensing unless separately and lawfully issued.

### **7.6.8 Credential Misuse Controls.**

7.6.8.1 Credential misuse shall include false claims, inflated claims, expired credential display as current, suspended or revoked credential display as valid, altered badge metadata, unauthorized logo use, public authority overclaim, professional license overclaim, employment overclaim, procurement overclaim, finance overclaim, insurance overclaim, consent overclaim, deployment overclaim, and execution overclaim.

7.6.8.2 Credential misuse may trigger notice, correction, display removal, Registry update, Marketplace update, suspension, withdrawal, revocation, public repair, archive, account action, or escalation to lawful authorities where necessary.

7.6.8.3 Credential misuse controls shall apply to learners, employers, sponsors, providers, hosts, public authority participants, National Nodes, National Consortium actors, Project SPVs, and downstream users of credential records.

### **7.6.9 Credential Withdrawal.**

7.6.9.1 Credentials may be withdrawn where issued in error, based on insufficient evidence, affected by assessment integrity failure, materially misleading, materially outdated, misused, unsafe, public-safe noncompliant, safeguard noncompliant, privacy noncompliant, or no longer supported.

7.6.9.2 Withdrawal shall update ILA records, Skills Wallet display, Registry status where applicable, Marketplace display where applicable, employer-readable summaries where feasible, and verification interfaces.

7.6.9.3 Withdrawal may be accompanied by reissue, bridge learning, correction, appeal, public repair, or archive depending on the case.

### **7.6.10 Credential Archive.**

7.6.10.1 Credential archive shall preserve record history while preventing archived credentials from being mistaken for current status.

7.6.10.2 Archived credential records shall include status, reason, issue date, archive date, issuer, evidence retention status, correction history, successor credential where applicable, visibility rules, and not-current notice.

7.6.10.3 Archive shall apply to expired, superseded, withdrawn, revoked, non-continuing, replaced, or retired credentials.

***

## **7.7 Credential Boundary Rules**

### **7.7.1 Micro-Credential Is Not Degree.**

7.7.1.1 A Micro-Credential shall not be represented as a degree, diploma, academic award, formal qualification, professional license, statutory qualification, or institutional credential unless separately and lawfully issued by a competent awarding body and accurately recorded.

7.7.1.2 Micro-Credentials may be stackable, portable, and evidence-rich, but stacking shall not create degree equivalence by implication.

### **7.7.2 Badge Is Not License.**

7.7.2.1 A Digital Badge shall not be represented as a professional license, practice permit, public authority authorization, regulated credential, safety approval, procurement qualification, deployment authorization, or execution authority.

7.7.2.2 Badge titles, visuals, metadata, and public displays shall avoid language that could reasonably imply legal or professional authority beyond the badge’s recorded scope.

### **7.7.3 Credential Is Not Job Guarantee.**

7.7.3.1 No SCF credential shall guarantee employment, interview access, promotion, wage level, contract award, work authorization, immigration outcome, or employer acceptance.

7.7.3.2 Employer-readable summaries and Marketplace profiles may support discovery and interpretation but shall not substitute for employer diligence, fair hiring processes, legal compliance, or workplace suitability assessment.

### **7.7.4 Credential Is Not Procurement Qualification by Default.**

7.7.4.1 No SCF credential shall create procurement qualification, supplier approval, vendor validation, preferred provider status, tender eligibility, public procurement status, or purchasing recommendation by default.

7.7.4.2 Procurement bodies and downstream recipients remain responsible for their own procurement rules, diligence, legal review, vendor assessment, and contracting decisions.

### **7.7.5 Credential Is Not Public Authority Approval.**

7.7.5.1 No SCF credential shall create public authority approval, regulatory approval, statutory training status, public finance eligibility, permit, license, official decision, emergency command authority, public warning authority, or public authority credential by implication.

7.7.5.2 Public authority participation in learning, credential design, review, or Nexus Universe activities shall not alter this rule unless the competent public authority separately and expressly records an official action.

### **7.7.6 Credential Is Not Deployment Authorization.**

7.7.6.1 No SCF credential shall authorize deployment, operation, field implementation, safety-critical work, restricted data access, secure room access beyond recorded permissions, public infrastructure work, medical or public health action, emergency response, cyber operation, or enterprise execution by implication.

7.7.6.2 Deployment and operation require separate lawful authorization, competent actors, technical review, safety review, public authority dependencies, procurement processes where applicable, and recipient responsibility.

### **7.7.7 Credential Is Not Community Consent.**

7.7.7.1 No SCF credential, safeguard credential, community-learning credential, fieldwork credential, public-safe reporting credential, or National Portfolio credential shall create community consent, Indigenous consent, protected knowledge permission, representation authority, community endorsement, or social license by implication.

7.7.7.2 Community and Indigenous consent, where required, must be separately and lawfully obtained, recorded, respected, and governed through appropriate protocols outside the credential record.

***

## **7.8 Final Part VII Operating Statement**

7.8.1 SCF credentials shall make learning, competence, contribution, review, mentorship, public-safe practice, safeguard literacy, Foundry work, Risk Academy learning, WILP participation, National Portfolio contribution, Nexus Universe preparation, and lawful handoff literacy visible, portable, reviewable, and correctionable without converting them into legal authority.

7.8.2 Micro-Credentials shall function as bounded evidence records. Digital Badges shall function as display objects. Verification shall confirm authenticity and status within scope. Recognition shall support learner agency and public-good capability formation. Portability shall support movement of records without creating legal equivalence by default.

7.8.3 Credential evidence shall be based on learning completion, assessment, work products, simulations, Studio exercises, peer review, mentor verification, host or employer evidence, public-good contribution, correction, expiry, and renewal. Evidence shall be sufficient for the credential’s stated scope and shall not be inflated beyond that scope.

7.8.4 Recognition of Prior Learning shall allow SCF to honor formal, informal, community, work, military, emergency, humanitarian, public service, migrant, refugee, diaspora, open-source, caregiving, and lived-risk experience through fair, evidence-based, safeguard-aware, and correctionable pathways, without converting prior experience into unreviewed credential status.

7.8.5 Credential governance shall preserve issuer accountability, assessor discipline, reviewer integrity, conflict management, sponsor and provider controls, public authority boundary controls, quality assurance, misuse controls, withdrawal, and archive. Credentials shall remain trustworthy because they are bounded, evidenced, reviewable, correctable, and not-current when archived.

7.8.6 The final rule of Part VII is that SCF credentials recognize learning and competence within scope; they do not create degrees, licenses, employment guarantees, wage guarantees, immigration status, procurement qualifications, public authority approvals, financeability, insurability, community consent, deployment authorization, or execution by implication.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.therisk.global/organization/operations/frameworks/sustainable-competency-framework-scf/vii.-credentials.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.