# IV. ONTOLOGY ## **4.1 SCF Competency Ontology** ### **4.1.1 Competency Defined.** 4.1.1.1 **Competency** within the Sustainable Competency Framework (SCF) shall mean a structured, evidence-bearing, context-aware, reviewable, and correctionable capability to apply knowledge, skills, abilities, practice, judgment, disposition, tools, methods, safeguards, and role discipline to a defined task, role, domain, work system, public-good contribution, learning pathway, public authority learning context, Nexus production context, or lawful handoff context. 4.1.1.2 A competency shall not be reduced to a skill keyword, course title, job title, employer preference, credential label, platform badge, tool familiarity, task completion, or self-declared expertise. A competency shall require recorded scope, domain context, expected performance, evidence type, review level, limitations, validity status, renewal or expiry conditions where applicable, public-safe display status, and correction pathway. 4.1.1.3 SCF competencies may apply to technical, vocational, digital, data, AI, cyber, privacy, geospatial, WFEH-B, DRR, DRF, DRI, climate, nature, public health, infrastructure, care, community, governance, ethics, public-safe reporting, labor-market transition, public authority learning, finance-readiness literacy, insurance-readiness literacy, Foundry production, Campaign mobilization, Studio practice, Grid and TRL evidence, Nexus Universe participation, and lawful handoff literacy. 4.1.1.4 A competency record shall describe what has been evidenced, within what context, against what criteria, by what source, at what level, with what review status, and subject to what limitations. It shall not become professional license, employment guarantee, public authority approval, procurement qualification, financeability, insurability, consent, deployment authorization, or execution authority by implication. ### **4.1.2 Skill Defined.** 4.1.2.1 **Skill** shall mean a learnable and demonstrable capability to perform a defined action, method, technique, task, analysis, communication, operation, review, judgment-support activity, tool use, or contribution within a bounded context. 4.1.2.2 Skills may be foundational, technical, digital, cognitive, social, manual, analytical, creative, supervisory, public-safe, safeguard-related, domain-specific, cross-domain, role-specific, or context-specific. Skills may include data cleaning, model evaluation, prompt review, secure repository use, public-safe writing, field observation, stakeholder facilitation, dashboard interpretation, risk classification, community engagement, mentoring, review, maintenance, and correction. 4.1.2.3 A skill shall not by itself establish competence unless accompanied by relevant knowledge, practice, judgment, evidence, and context. Tool familiarity shall not equal skill; task exposure shall not equal skill; course attendance shall not equal skill; and skill display shall not equal employment readiness, professional qualification, or lawful authority. ### **4.1.3 Knowledge Defined.** 4.1.3.1 **Knowledge** shall mean structured understanding of facts, concepts, principles, theories, methods, standards-interface references, domain vocabulary, risk categories, legal boundaries, ethical considerations, technical systems, public-good doctrines, labor-market context, and operational constraints relevant to a competency. 4.1.3.2 Knowledge may be declarative, procedural, contextual, systems-based, tacit, community-based, scientific, technical, legal-boundary, public-safe, or safeguard-sensitive. SCF shall recognize knowledge from formal learning, practice, research, public service, community work, Indigenous knowledge systems where applicable and lawfully handled, humanitarian experience, informal work, and public-good contribution. 4.1.3.3 Knowledge evidence shall be handled with context and safeguards. The existence of knowledge shall not imply permission to use restricted data, protected knowledge, sensitive geospatial information, community knowledge, Indigenous protocol-sensitive knowledge, proprietary information, cyber-sensitive information, or public authority-sensitive information. ### **4.1.4 Ability Defined.** 4.1.4.1 **Ability** shall mean the capacity to apply skills and knowledge under conditions of complexity, uncertainty, time constraint, resource constraint, safety sensitivity, ethical ambiguity, data limitation, public-safe communication need, or changing operational context. 4.1.4.2 Ability may include analysis, synthesis, adaptation, prioritization, communication, collaboration, supervision, escalation, correction, field judgment, systems thinking, resilience, accessibility-aware practice, cross-cultural practice, and human-AI oversight. 4.1.4.3 Ability shall be assessed through appropriate evidence and context. A person may possess knowledge without demonstrated ability, may possess ability in one context but not another, and may require supervision or safeguards for higher-risk contexts. SCF records shall distinguish these conditions. ### **4.1.5 Practice Defined.** 4.1.5.1 **Practice** shall mean repeated, observable, and contextually relevant application of knowledge, skills, abilities, tools, methods, and judgment through learning exercises, WILPs, simulations, Studio workflows, fieldwork, Foundry builds, Campaign work, National Working Group outputs, Competence Cell work, public-safe reporting, research activity, review work, maintenance work, or lawful downstream work. 4.1.5.2 Practice may be simulated, supervised, independent, field-based, remote, hybrid, site-based, controlled-room-based, secure-room-based, data-room-based, public authority learning room-based, or handoff-recipient-based. 4.1.5.3 Practice evidence shall include scope, setting, supervision level, task type, output type, review status, risk sensitivity, data and AI-use status, safeguards, and limitations. Practice in a learning environment shall not equal authorization to perform the same task in an operational, regulated, safety-critical, public authority, or enterprise execution environment. ### **4.1.6 Judgment Defined.** 4.1.6.1 **Judgment** shall mean the capacity to make reasoned, ethical, context-aware, risk-aware, evidence-aware, public-safe, safeguard-sensitive, and boundary-compliant choices when applying competence under uncertainty. 4.1.6.2 Judgment may include knowing when to proceed, when to stop, when to escalate, when to seek review, when to apply no-AI or restricted-AI labels, when to protect data, when to avoid public disclosure, when to avoid public authority overclaim, when to avoid finance or procurement language, when to protect community or Indigenous knowledge, when to correct an output, and when to archive or withdraw a record. 4.1.6.3 SCF shall treat judgment as central to high-risk, public-good, all-hazards, AI-enabled, data-intensive, cyber-sensitive, public authority-sensitive, finance-boundary, safeguard-sensitive, and handoff-relevant work. Competency records that lack evidence of judgment shall be limited accordingly. ### **4.1.7 Disposition Defined.** 4.1.7.1 **Disposition** shall mean the professional, civic, ethical, collaborative, public-good, learning-oriented, correction-oriented, and safeguard-aware orientation with which a person or role applies competence. 4.1.7.2 Relevant dispositions may include integrity, humility, care, diligence, respect for evidence, respect for community knowledge, respect for Indigenous protocols where applicable, accessibility awareness, privacy awareness, public-safe communication, anti-capture discipline, willingness to correct, respect for role separation, and refusal to overclaim authority. 4.1.7.3 Disposition shall not be used as an opaque personality judgment, social score, political screen, subjective exclusion tool, or unmanaged gatekeeping device. Where disposition is recorded, it shall be tied to observable conduct, role requirements, safeguards, review notes, and correction or appeal pathways. ### **4.1.8 Role Capability Defined.** 4.1.8.1 **Role Capability** shall mean a competency package required to perform a defined SCF role, Nexus role, work-system role, public-good contribution role, learning role, review role, maintainer role, mentor role, public authority learning role, or handoff-context role. 4.1.8.2 Role Capability may include a role profile, task inventory, required competencies, optional competencies, supervision conditions, evidence requirements, review authority, boundary notices, conflicts rules, privacy obligations, data-use limits, AI-use limits, public-safe communication obligations, safeguard obligations, and correction responsibilities. 4.1.8.3 Role Capability shall not imply employment, appointment, professional license, public authority role, procurement qualification, finance role, insurance role, standards authority, or execution authority unless separately and lawfully recorded by the competent actor. ### **4.1.9 Contextual Competence Defined.** 4.1.9.1 **Contextual Competence** shall mean competence that is valid only within a specified context, such as a jurisdiction, sector, technology, hazard, community, language, culture, data environment, public authority setting, enterprise setting, secure room, Studio workflow, field environment, National Portfolio, Nexus Universe arena, or lawful handoff recipient environment. 4.1.9.2 SCF shall treat context as essential. Competence demonstrated in one country, sector, language, tool, dataset, model, public authority learning room, WILP, simulation, or Foundry build shall not automatically transfer to another context without review, localization, mapping, additional evidence, or lawful recognition where required. 4.1.9.3 Contextual Competence records shall identify jurisdictional context, language context, cultural context, domain context, data context, AI-use context, safeguard context, public authority context, labor-market context, supervision context, and handoff relevance where applicable. ### **4.1.10 Evidence of Competence Defined.** 4.1.10.1 **Evidence of Competence** shall mean recorded proof, artifact, assessment, review, verification, work product, portfolio, simulation output, field output, public-good contribution, public-safe output, mentor verification, host verification, peer review, Registry status, Marketplace display, Grid input, TRL note, Nexus Universe output, or correction record used to support a competency claim. 4.1.10.2 Evidence of Competence shall be classified by source, date, scope, method, review status, confidence where applicable, limitations, privacy status, display permission, renewal or expiry conditions where applicable, correction history, and archive rule. 4.1.10.3 Evidence of Competence shall not become authority by itself. Evidence may support learning, recognition, review, portfolio display, workforce transition, National Capability Records, or handoff context, but it shall not create professional license, employment guarantee, public authority approval, procurement qualification, financeability, insurability, consent, deployment authorization, or execution. *** ## **4.2 Competency Families** ### **4.2.1 Foundational Literacies.** 4.2.1.1 **Foundational Literacies** shall include reading, writing, numeracy, digital access, information literacy, evidence literacy, scientific literacy, systems literacy, civic literacy, media literacy, data literacy, AI literacy at an introductory level, risk literacy, accessibility literacy, and public-safe communication basics. 4.2.1.2 Foundational Literacies shall support broad participation in SCF, Nexus Academy, Risk Academy, Campaigns, Foundry pathways, WILPs, National Portfolios, and Nexus Universe. They shall be designed for inclusion, language access, disability access, low-bandwidth access, youth pathways, adult learning, and lifelong learning. 4.2.1.3 Foundational Literacy records shall not be represented as professional qualifications, job guarantees, public authority competence, or procurement readiness. ### **4.2.2 Technical and Vocational Competencies.** 4.2.2.1 **Technical and Vocational Competencies** shall include practical, occupational, craft, trade, engineering, operational, maintenance, field, laboratory, infrastructure, manufacturing, energy, water, food, health, logistics, telecommunications, equipment, and safety-related competencies. 4.2.2.2 SCF shall map technical and vocational competencies to occupation and task profiles, WILPs, apprenticeships, traineeships, field practice, technical micro-credentials, National Skills Maps, National Capability Records, Foundry builds, Studio exercises, and lawful handoff dependencies. 4.2.2.3 Technical or vocational competency records shall not override professional licensing, trade certification, occupational safety rules, public authority approvals, employer training requirements, or statutory qualification systems. ### **4.2.3 Digital and Data Competencies.** 4.2.3.1 **Digital and Data Competencies** shall include digital collaboration, digital identity literacy, data collection, metadata, data dictionaries, data quality, lineage, data governance, data visualization, analytics, dashboards, secure data handling, public-safe data transformation, data-use labels, AI-use labels, compute-to-data literacy, secure-room participation, and data rights literacy. 4.2.3.2 Digital and Data Competencies shall support DICE, Nexus Studio, Nexus Observatory, DRI dashboards, GRIx mapping, Nexus Reports, Nexus Marketplace, Nexus Registry, Nexus Foundry, National Portfolios, and lawful handoff packages. 4.2.3.3 Data competence shall not create data access rights. Digital competence shall not create system access. Metadata literacy shall not create permission to publish data. Dashboard skill shall not create decision authority. ### **4.2.4 AI and Human-AI Collaboration Competencies.** 4.2.4.1 **AI and Human-AI Collaboration Competencies** shall include AI literacy, prompt and interaction skills, AI-assisted research, AI-assisted coding, retrieval-augmented workflow literacy, model evaluation, red-team literacy, bias and harm review, model card literacy, system card literacy, benchmark card literacy, agentic workflow literacy, human-in-the-loop practice, human-on-the-loop oversight, data leakage prevention, prompt-injection awareness, and AI incident escalation. 4.2.4.2 AI competencies shall be governed by AI-use labels, data-use labels, human review, secure-room controls where applicable, public-safe output review, and no automated high-stakes decision rules. 4.2.4.3 AI tool use shall not equal AI competence. AI competence shall not equal AI safety certification, deployment approval, professional license, public authority approval, employment guarantee, financeability, insurability, or procurement readiness. ### **4.2.5 Cybersecurity and Digital Trust Competencies.** 4.2.5.1 **Cybersecurity and Digital Trust Competencies** shall include cyber hygiene, identity and access management, secure collaboration, secure software basics, dependency awareness, SBOM literacy, vulnerability reporting, incident response literacy, critical infrastructure sensitivity, OT and IoT awareness, AI security, public-safe technical disclosure, privacy awareness, and zero-trust principles. 4.2.5.2 Cybersecurity competence shall be public-safe and role-scoped. SCF shall distinguish awareness, literacy, supervised practice, independent contribution, reviewer capability, and security maintainer capability. 4.2.5.3 Cyber competence records shall not constitute security certification, operational authorization, vulnerability disclosure authority, public warning authority, or permission to access systems. ### **4.2.6 Systems Thinking and Complexity Competencies.** 4.2.6.1 **Systems Thinking and Complexity Competencies** shall include systems mapping, feedback loops, interdependencies, cascades, uncertainty, scenario thinking, resilience, adaptation, emergence, cross-sector coordination, risk propagation, portfolio logic, and whole-of-society analysis. 4.2.6.2 These competencies shall support WFEH-B systems, DRR, DRI, Nexus Observatory, Studio simulations, National Systems-Risk Maps, Nexus Universe arenas, National Portfolio formation, and lawful handoff dependency mapping. 4.2.6.3 Systems thinking competence shall not create forecasting certainty, public authority decision, investment signal, insurance score, country ranking, or operational command. ### **4.2.7 Risk, Resilience, and Crisis Competencies.** 4.2.7.1 **Risk, Resilience, and Crisis Competencies** shall include hazard literacy, vulnerability literacy, exposure literacy, preparedness, resilience planning, crisis-learning, after-action learning, public-safe risk communication, DRI interpretation, DRI correction, humanitarian sensitivity, emergency boundary literacy, continuity planning, and degraded-mode awareness. 4.2.7.2 These competencies shall support Risk Academy, Nexus Observatory, DRI, GRIx, Studio, National Portfolios, Campaigns, Nexus Universe, and lawful handoff context. 4.2.7.3 Risk and crisis competence shall not create public warning authority, emergency command, public authority approval, insurance scoring, investment recommendation, or deployment authorization. ### **4.2.8 Sustainability, Climate, Nature, and Green Skills.** 4.2.8.1 **Sustainability, Climate, Nature, and Green Skills** shall include climate adaptation, nature-based solutions, biodiversity monitoring, water security, food systems resilience, energy transition, circular economy, sustainable infrastructure, climate-health literacy, carbon accounting literacy, ecosystem services literacy, blue economy literacy, environmental data literacy, and just transition literacy. 4.2.8.2 These competencies shall be linked to WFEH-B systems, National Portfolios, public authority learning, community safeguards, Indigenous protocol-sensitive knowledge where applicable, DRI, Observatory outputs, and public-safe reporting. 4.2.8.3 Green skills records shall not certify environmental claims, procurement preferences, climate compliance, biodiversity data permissions, public authority approvals, or project execution. ### **4.2.9 Governance, Ethics, and Public-Good Competencies.** 4.2.9.1 **Governance, Ethics, and Public-Good Competencies** shall include role separation, non-execution discipline, validity by record, correctionability, no-conversion, public-good firewall, conflicts management, anti-capture, public authority boundary literacy, finance-readiness boundary literacy, procurement neutrality, sponsor and provider boundary literacy, data ethics, AI ethics, community safeguards, and public-safe publication. 4.2.9.2 These competencies shall be required for reviewers, maintainers, mentors, stewards, National Working Groups, Competence Cells, Nexus Universe participants, public authority learning rooms, Registry and Marketplace stewards, Reports contributors, and lawful handoff context contributors. 4.2.9.3 Governance competency shall not create board authority, public authority status, legal authority, certification authority, procurement authority, or execution authority. ### **4.2.10 Communication, Collaboration, and Leadership Competencies.** 4.2.10.1 **Communication, Collaboration, and Leadership Competencies** shall include public-safe writing, technical communication, plain-language explanation, facilitation, stakeholder dialogue, cross-sector collaboration, conflict navigation, mentorship, supervision, team coordination, systems leadership, distributed work, multilingual communication, accessibility-aware communication, and media-safe communication. 4.2.10.2 These competencies shall support Campaigns, Academy, Risk Academy, Foundry, National Councils, Helix Councils, National Working Groups, Competence Cells, Nexus Universe, Reports, Studio rooms, and Risk Agency engagements. 4.2.10.3 Leadership competence shall not imply appointment, public authority role, board status, employment status, endorsement, command authority, or execution authority. ### **4.2.11 Public-Safe Reporting Competencies.** 4.2.11.1 **Public-Safe Reporting Competencies** shall include evidence translation, risk communication, 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 geospatial controls, correction notices, and public repair. 4.2.11.2 Public-safe reporting competence shall support Nexus Reports, Risk Academy, Campaigns, Observatory outputs, DRI summaries, National Portfolio Reports, Nexus Universe outputs, and Handoff Competency Context Notes. 4.2.11.3 Public-safe reporting shall not create public warning authority, official notice, public authority approval, emergency command, certification, procurement recommendation, finance recommendation, or consent. ### **4.2.12 Safeguard and Inclusion Competencies.** 4.2.12.1 **Safeguard and Inclusion Competencies** shall include community safeguards, Indigenous protocols where applicable, protected knowledge handling, youth safeguards, disability inclusion, accessibility, humanitarian sensitivity, non-extractive engagement, gender equity, rural and remote access, language access, trauma-informed practice, privacy protection, and community-facing correction. 4.2.12.2 Safeguard competencies shall be embedded across learning, WILPs, Campaigns, Foundry, Studio, Reports, Registry, Marketplace, National Portfolios, Nexus Universe, and lawful handoff contexts. 4.2.12.3 Safeguard competence shall not create consent, protected knowledge permission, community representation authority, Indigenous authorization, public authority approval, or deployment authorization. ### **4.2.13 Entrepreneurship and Innovation Competencies.** 4.2.13.1 **Entrepreneurship and Innovation Competencies** shall include opportunity identification, problem framing, user and stakeholder discovery, systems innovation, public-good innovation, venture literacy, social enterprise literacy, product discovery, evidence-led iteration, R\&D translation, open technical baseline literacy, finance-readiness literacy, risk management, and lawful handoff literacy. 4.2.13.2 These competencies shall support Nexus Foundry, Nexus Labs, Campaigns, Marketplace, Registry, National Portfolios, National Consortium Companies, Project SPVs, and lawful downstream enterprise contexts. 4.2.13.3 Entrepreneurship competence shall not create venture approval, investment readiness, financeability, bankability, insurance approval, donor commitment, procurement status, public authority approval, or execution authority. ### **4.2.14 Care, Community, and Civic Competencies.** 4.2.14.1 **Care, Community, and Civic Competencies** shall include caregiving, mutual aid, community facilitation, civic participation, local risk knowledge, community resilience, accessibility support, mediation, translation, public-interest participation, community health literacy, disaster support, place-based knowledge, and non-extractive engagement. 4.2.14.2 These competencies may arise through paid work, unpaid work, informal work, volunteer work, community work, humanitarian work, and lived experience. SCF shall handle such evidence with privacy, dignity, consent, safeguards, and anti-exploitation controls. 4.2.14.3 Community or civic competence shall not imply community consent, representation authority, protected knowledge permission, public authority approval, employment status, or execution. ### **4.2.15 Lawful Handoff Literacy Competencies.** 4.2.15.1 **Lawful Handoff Literacy Competencies** shall include understanding of context transfer, dependency transfer, evidence transfer, recipient responsibility, public-good stack and enterprise-stack separation, procurement neutrality, finance-readiness without finance, insurance-readiness without underwriting, public authority dependencies, legal dependencies, data dependencies, safeguard dependencies, provider-neutrality notes, sponsor-boundary notes, correction and recall pathways, and no-execution rules. 4.2.15.2 Handoff literacy shall be required for persons and teams contributing to handoff context, National Consortium Company interfaces, Project SPV interfaces, public authority learning records, readiness rooms, capital-reader rooms, insurance-reader rooms, donor-reader rooms, National Portfolios, and Nexus Universe outputs. 4.2.15.3 Handoff literacy shall not authorize handoff, execution, procurement, finance, insurance, public authority approval, consent, deployment, or operations. It shall support responsible boundary-aware transition to competent lawful actors. *** ## **4.3 Nexus Domain Competency Clusters** ### **4.3.1 WFEH-B Competency Cluster.** 4.3.1.1 The **WFEH-B Competency Cluster** shall include competencies for water, food, energy, health, biodiversity, nature, infrastructure, climate, supply-chain, resilience, and cross-system cascade understanding. 4.3.1.2 This cluster shall support National Portfolios, DRI, GRIx, Observatory signals, Studio simulations, public authority learning, Campaigns, Foundry builds, Reports, Nexus Universe arenas, and lawful handoff context. 4.3.1.3 WFEH-B competence shall not create technical certification, environmental approval, public health authority, public warning authority, procurement preference, or project authorization. ### **4.3.2 DRR Competency Cluster.** 4.3.2.1 The **Disaster Risk Reduction (DRR) Competency Cluster** shall include competencies for hazard, exposure, vulnerability, risk reduction, resilience planning, preparedness, prevention, mitigation, recovery learning, public-safe risk communication, community resilience, and multi-hazard systems. 4.3.2.2 DRR competence shall support Risk Academy, National Portfolios, Nexus Observatory, Studio scenarios, DRI records, Campaigns, Nexus Universe, and lawful handoff dependencies. 4.3.2.3 DRR competence shall not create emergency command, public warning authority, public authority decision, or deployment authorization. ### **4.3.3 DRF Competency Cluster.** 4.3.3.1 The **Disaster Risk Finance (DRF) Competency Cluster** shall include literacy in risk-layering, protection gaps, insurance-readiness questions, public finance relevance questions, donor-readiness questions, contingency finance literacy, resilience finance context, no-reliance literacy, non-solicitation, non-transactionality, and regulated-perimeter discipline. 4.3.3.2 DRF competence shall support GRA-aligned learning, Risk Academy, National Investors Councils, readiness rooms, capital-reader rooms, insurance-reader rooms, donor-reader rooms, National Portfolios, Nexus Universe, and handoff context. 4.3.3.3 DRF competence shall not constitute investment advice, insurance advice, underwriting, brokerage, finance approval, donor commitment, guarantee, rating, valuation, or transaction activity. ### **4.3.4 DRI Competency Cluster.** 4.3.4.1 The **Disaster Risk Intelligence (DRI) Competency Cluster** shall include competencies for indicator literacy, signal interpretation, uncertainty labels, confidence labels, dashboard interpretation, hotspot and cascade literacy, public-safe intelligence writing, correction, archive, no-warning language, and no-rating language. 4.3.4.2 DRI competence shall support Risk Academy, Nexus Observatory, Reports, Studio, National Portfolios, Campaigns, Nexus Universe, and lawful handoff context. 4.3.4.3 DRI competence shall not create public warning authority, official forecast, insurance score, investment signal, emergency command, or public authority decision. ### **4.3.5 DICE and Data Commons Competency Cluster.** 4.3.5.1 The **DICE and Data Commons Competency Cluster** shall include data commons literacy, innovation commons literacy, software commons literacy, knowledge commons literacy, metadata skills, data dictionary skills, schema skills, lineage skills, data quality skills, data availability statements, privacy literacy, AI-use labels, compute-to-data literacy, secure-room literacy, and controlled output publication. 4.3.5.2 DICE competence shall support Nexus Academy, Foundry, Reports, Marketplace, Registry, Studio, Observatory, DRI, National Portfolios, and handoff packages. 4.3.5.3 DICE competence shall not create data rights, system access, open data permission, unrestricted publication permission, or public authority record status. ### **4.3.6 GRIx and Risk Ontology Competency Cluster.** 4.3.6.1 The **GRIx and Risk Ontology Competency Cluster** shall include controlled vocabulary use, taxonomy mapping, semantic interoperability, risk categorization, WFEH-B category mapping, DRR/DRF/DRI mapping, frontier technology risk categories, safeguard categories, public authority boundary categories, finance and insurance boundary categories, and handoff dependency categories. 4.3.6.2 GRIx competence shall support Reports, Registry, Marketplace, Studio, Grid, DRI, National Portfolios, Nexus Universe, and public-safe communication. 4.3.6.3 Risk ontology competence shall not create legal classification, rating, standards authority, certification, public authority approval, or procurement status. ### **4.3.7 Observatory and Geospatial Competency Cluster.** 4.3.7.1 The **Observatory and Geospatial Competency Cluster** shall include observability literacy, sensor and edge signal literacy, geospatial literacy, Earth observation literacy, digital twin input literacy, sensitive location controls, degraded-mode awareness, public-safe observability outputs, dashboard review, and correction. 4.3.7.2 This cluster shall support Nexus Observatory, DRI, Studio, Reports, National Portfolios, Campaigns, Nexus Universe, and handoff context. 4.3.7.3 Observatory and geospatial competence shall not create surveillance authority, public warning authority, official map status, emergency command, public authority decision, or deployment authorization. ### **4.3.8 Studio and Simulation Competency Cluster.** 4.3.8.1 The **Studio and Simulation Competency Cluster** shall include scenario design, simulation interpretation, dashboard workflows, digital twin workflows, AI workflow review, data-room workflows, secure-room workflows, public authority learning room participation, readiness-room participation, assumptions register use, dependency register use, model limitation literacy, and no-decision runtime controls. 4.3.8.2 Studio and simulation competence shall support learning, public authority learning, readiness, public-safe reporting, Foundry builds, National Portfolios, Nexus Universe, and handoff context. 4.3.8.3 Simulation competence shall not create forecast certainty, certification, operational command, deployment authorization, finance approval, insurance approval, or public authority action. ### **4.3.9 Foundry and Build Competency Cluster.** 4.3.9.1 The **Foundry and Build Competency Cluster** shall include competencies for quests, bounties, builds, micro-production, software contribution, data pipeline contribution, dashboard contribution, ontology contribution, public-safe reporting contribution, Studio workflow contribution, National Portfolio builds, Marketplace and Registry builds, Grid and TRL evidence builds, maintainer pathways, and correction handling. 4.3.9.2 Foundry competence shall support applied practice, public-good production, iCRS recognition, ILA records, skills wallets, micro-credentials, National Capability Records, Nexus Universe outputs, and lawful handoff context. 4.3.9.3 Foundry competence shall not create employment, procurement qualification, product certification, provider validation, deployment authorization, or execution. ### **4.3.10 Campaign and Mobilization Competency Cluster.** 4.3.10.1 The **Campaign and Mobilization Competency Cluster** shall include public-good mobilization, volunteer coordination, signature tool literacy, pledge tool literacy, support tool literacy, team and chapter coordination, ambassador practice, public-safe storytelling, Campaign dashboard literacy, trust and safety, fraud awareness, community participation boundaries, and correction channels. 4.3.10.2 Campaign competence shall support Nexus Campaigns, Academy pathways, Risk Academy pathways, Foundry routing, National Portfolios, Nexus Universe, Reports, Registry, Marketplace, and public-safe communication. 4.3.10.3 Campaign competence shall not create mandate, vote, consent, public authority approval, donor commitment, employment, procurement status, or execution authority. ### **4.3.11 Reports and Publication Competency Cluster.** 4.3.11.1 The **Reports and Publication Competency Cluster** shall include evidence translation, publication lifecycle, metadata preparation, repository deposit literacy, DOI discipline, FAIR metadata literacy, licensing literacy, data availability statements, AI-use statements, public-safe abstracts, controlled repository exclusions, sensitive knowledge restrictions, correction notices, public repair, withdrawal, and archive. 4.3.11.2 Reports competence shall support Nexus Reports, Academy, Risk Academy, Foundry, Labs, DICE, GRIx, DRI, Observatory, Marketplace, Registry, Grid, Nexus Universe, National Portfolios, and handoff context. 4.3.11.3 Publication competence shall not create approval, public warning, certification, unrestricted use, public authority decision, financeability, procurement readiness, or country ranking. ### **4.3.12 Marketplace and Registry Competency Cluster.** 4.3.12.1 The **Marketplace and Registry Competency Cluster** shall include discovery governance, listing metadata, object classification, status truth, versioning, support status, correction status, archive status, public-safe display, provider-neutrality review, sponsor-boundary review, procurement-neutrality review, finance-boundary review, delisting, and withdrawal. 4.3.12.2 This cluster shall support Marketplace listings, Registry records, skills-wallet display, micro-credential display, learning objects, WILPs, Competence Cells, Foundry outputs, Reports, National Portfolio records, Nexus Universe outputs, and handoff context. 4.3.12.3 Marketplace and Registry competence shall not create certification, endorsement, procurement approval, employment eligibility, provider validation, public authority approval, or execution. ### **4.3.13 Grid and TRL Competency Cluster.** 4.3.13.1 The **Grid and TRL Competency Cluster** shall include readiness evidence literacy, TRL 1–10 literacy, evidence sufficiency, method sufficiency, data sufficiency, AI-use sufficiency, cyber sufficiency, public-safe sufficiency, safeguard sufficiency, support sufficiency, reproducibility sufficiency, correction sufficiency, review gates, downgrade, suspension, withdrawal, and reinstatement. 4.3.13.2 Grid and TRL competence shall support Nexus Grid, Foundry, Studio, Reports, Marketplace, Registry, National Portfolios, Nexus Universe, and handoff context. 4.3.13.3 Grid and TRL competence shall not create maturity certification, procurement readiness, financeability, insurability, public authority approval, deployment authorization, or execution. ### **4.3.14 Risk Agency Expert Competency Cluster.** 4.3.14.1 The **Risk Agency Expert Competency Cluster** shall include expert matching literacy, risk advisory competence, resilience consulting support, public-safe reporting support, capacity-building support, cross-sphere translation, handoff support, conflict disclosure, reliance labels, training delivery, supervision, and correction. 4.3.14.2 Risk Agency competence shall support advisory pathways, expert routing, supervised practice, mentor pathways, reviewer pathways, public authority learning, community translation, and lawful handoff support. 4.3.14.3 Risk Agency expert standing shall not create professional license, certification, public authority approval, investment advice, underwriting, consent, or execution. ### **4.3.15 Nexus Universe Competency Cluster.** 4.3.15.1 The **Nexus Universe Competency Cluster** shall include competencies for annual surge participation, National Portfolio convergence, public authority learning concentration, Foundry build concentration, Campaign mobilization, Academy and Labs concentration, Marketplace and Registry discovery, Core Build participation, arena participation, room participation, continuation records, and archive. 4.3.15.2 Nexus Universe competence shall support talent display, capability convergence, learning outputs, Competence Cell showcases, public authority learning records, Foundry continuation, National Portfolio updates, and handoff dependency notes. 4.3.15.3 Nexus Universe participation shall not create endorsement, public authority approval, finance, underwriting, procurement status, provider validation, consent, deployment authorization, or execution. *** ## **4.4 Competency Levels** ### **4.4.1 Awareness.** 4.4.1.1 **Awareness** shall mean basic exposure to a concept, domain, tool, risk, rule, framework, or practice sufficient to recognize its relevance and boundaries. 4.4.1.2 Awareness may be evidenced by participation, introductory assessment, reflection, short exercise, orientation completion, or public-safe understanding check. 4.4.1.3 Awareness shall not authorize practice, review, independent contribution, public-safe publication, public authority learning facilitation, or handoff context contribution. ### **4.4.2 Literacy.** 4.4.2.1 **Literacy** shall mean the ability to understand, explain, interpret, and apply basic concepts, vocabulary, boundaries, and use cases within a defined domain. 4.4.2.2 Literacy may be evidenced by assessments, scenario interpretation, short written outputs, dashboard interpretation, vocabulary mapping, public-safe summaries, or structured exercises. 4.4.2.3 Literacy shall not equal operational competence, professional qualification, independent practice, certification, employment readiness, or deployment authority. ### **4.4.3 Applied Practice.** 4.4.3.1 **Applied Practice** shall mean the ability to perform defined tasks in a controlled, supervised, simulated, educational, Studio, WILP, Foundry, Campaign, or comparable practice environment. 4.4.3.2 Applied Practice shall require work product evidence, assessment evidence, practice records, supervision records, or review notes appropriate to the task. 4.4.3.3 Applied Practice shall not authorize unsupervised, safety-critical, regulated, public authority, enterprise execution, or deployment work unless separately and lawfully established. ### **4.4.4 Supervised Contribution.** 4.4.4.1 **Supervised Contribution** shall mean contribution to public-good work, learning objects, data objects, software objects, Reports, Campaigns, Foundry builds, Studio workflows, National Working Groups, Competence Cells, or Nexus Universe outputs under review, mentorship, or supervision. 4.4.4.2 Supervised Contribution may support ILA records, iCRS records, skills-wallet records, micro-credential evidence, Registry records, or Marketplace display where permitted. 4.4.4.3 Supervised Contribution shall not create employment, independent authority, professional license, procurement qualification, public authority approval, deployment authorization, or execution. ### **4.4.5 Independent Contribution.** 4.4.5.1 **Independent Contribution** shall mean the ability to complete defined work within scope without continuous supervision, while complying with SCF evidence, review, data, AI, cyber, privacy, safeguard, public-safe, and correction requirements. 4.4.5.2 Independent Contribution may be evidenced by accepted work products, reviewed contributions, maintained records, Reports contributions, Foundry outputs, Studio outputs, Marketplace objects, Registry records, or National Portfolio contributions. 4.4.5.3 Independent Contribution shall remain bounded by scope. It shall not authorize regulated practice, public authority action, professional licensing, procurement qualification, finance or insurance activity, deployment, or execution. ### **4.4.6 Reviewer Capability.** 4.4.6.1 **Reviewer Capability** shall mean the ability to evaluate evidence, learning outputs, work products, public-safe outputs, data and AI-use labels, safeguard status, competence evidence, WILP artifacts, micro-credential submissions, Foundry outputs, or handoff context within a defined review scope. 4.4.6.2 Reviewer Capability shall require competence in criteria, conflicts, evidence sufficiency, public-safe boundaries, correction, and escalation. 4.4.6.3 Reviewer Capability shall not create certification authority, public authority approval, professional licensing authority, employment decision authority, procurement authority, or deployment authority. ### **4.4.7 Maintainer Capability.** 4.4.7.1 **Maintainer Capability** shall mean the ability to steward, update, support, correct, version, document, deprecate, withdraw, or archive an SCF object, learning object, software object, data object, competency map, WILP, micro-credential, Registry record, Marketplace listing, Report package, or Foundry object within a defined scope. 4.4.7.2 Maintainer Capability shall require knowledge of versioning, support status, evidence status, security and privacy where applicable, accessibility, public-safe display, licensing where applicable, correction, withdrawal, and archive. 4.4.7.3 Maintainer Capability shall not create ownership, certification authority, provider validation, professional license, employment status, public authority approval, deployment authority, or execution. ### **4.4.8 Steward Capability.** 4.4.8.1 **Steward Capability** shall mean the ability to govern SCF objects, pathways, records, roles, corrections, claims, boundaries, displays, registers, or institutional interfaces within a defined governance mandate. 4.4.8.2 Steward Capability shall include role separation, anti-capture discipline, conflict management, public-safe language, sponsor and provider controls, privacy, data and AI controls, safeguard review, public authority boundary discipline, finance and procurement boundary discipline, and correction. 4.4.8.3 Steward Capability shall not create hidden agency, shared liability, public authority status, board status, legal authority beyond mandate, certification authority, or execution authority. ### **4.4.9 Mentor Capability.** 4.4.9.1 **Mentor Capability** shall mean the ability to guide, support, supervise, advise, review, and develop learners, workers, WILP participants, Foundry contributors, Campaign participants, Competence Cell members, or Nexus Universe participants within a defined mentoring scope. 4.4.9.2 Mentor Capability shall require subject-matter competence, safeguarding competence, feedback competence, privacy awareness, youth protection where applicable, conflict awareness, and correction pathways. 4.4.9.3 Mentor Capability shall not create employment authority, professional license, credential authority, public authority approval, procurement status, or execution authority. ### **4.4.10 Systems Leadership Capability.** 4.4.10.1 **Systems Leadership Capability** shall mean the ability to coordinate across institutions, sectors, domains, hazards, technologies, communities, public authority learning contexts, and lawful handoff pathways while preserving role separation, public-good discipline, evidence, safeguards, and correctionability. 4.4.10.2 Systems Leadership Capability may support National Councils, National Leadership Councils, Helix Councils, National Working Groups, Competence Cells, Nexus Universe, National Portfolios, and cross-pillar coordination. 4.4.10.3 Systems Leadership Capability shall not imply command authority, public authority role, board appointment, institutional control, endorsement, procurement authority, finance authority, or execution. ### **4.4.11 National Capability Contributor.** 4.4.11.1 **National Capability Contributor** shall mean a person, team, institution, Working Group, Competence Cell, learner, mentor, reviewer, maintainer, or contributor whose evidenced competence supports National Skills Maps, National Capability Records, National Portfolios, national Nexus pathways, public authority learning, Nexus Universe preparation, or lawful handoff context. 4.4.11.2 National Capability Contributor status shall be nationally contextual, evidence-based, and correctionable. It may be displayed only within approved privacy and public-safe rules. 4.4.11.3 National Capability Contributor status shall not create national endorsement, public authority appointment, employment status, procurement status, professional license, financeability, consent, deployment authorization, or execution. ### **4.4.12 Handoff Context Contributor.** 4.4.12.1 **Handoff Context Contributor** shall mean a person or role whose evidence, learning, review, practice, or contribution may be relevant to a lawful handoff dependency package or Handoff Competency Context Note. 4.4.12.2 Handoff Context Contributor records may describe competence relevant to downstream review, but shall not authorize downstream work, employment, contracting, professional practice, public authority action, finance, insurance, procurement, consent, deployment, or execution. 4.4.12.3 Downstream recipients shall independently review any Handoff Context Contributor record before relying on it for lawful downstream purposes. *** ## **4.5 Competency Evidence Types** ### **4.5.1 Assessment Evidence.** 4.5.1.1 **Assessment Evidence** shall include examinations, quizzes, practical tests, structured evaluations, scenario assessments, simulations, demonstrations, oral defenses, written assignments, rubric-based evaluations, and competency checks. 4.5.1.2 Assessment Evidence shall record assessment scope, criteria, date, assessor or system used, review level, limitations, accommodations where applicable, AI-use status, privacy status, and correction pathway. 4.5.1.3 Assessment Evidence shall not equal professional certification, employment readiness, public authority competence, procurement qualification, or deployment authorization by default. ### **4.5.2 Work Product Evidence.** 4.5.2.1 **Work Product Evidence** shall include reports, code, datasets, models, dashboards, documentation, maps, analyses, plans, designs, public-safe summaries, Studio outputs, Campaign materials, Foundry builds, Registry records, Marketplace listings, or handoff notes created by a learner or contributor. 4.5.2.2 Work Product Evidence shall be evaluated for scope, quality, authorship, contribution level, review status, data and AI-use compliance, public-safe status, license status, and correctionability. 4.5.2.3 Work Product Evidence shall not create ownership, employment, procurement status, certification, deployment approval, or execution authority by default. ### **4.5.3 Portfolio Evidence.** 4.5.3.1 **Portfolio Evidence** shall mean a curated set of assessment evidence, work product evidence, WILP evidence, contribution records, micro-credential records, public-safe outputs, reviews, mentor verifications, host verifications, and correction records demonstrating competence across time. 4.5.3.2 Portfolio Evidence may support ILA records, skills-wallet displays, Marketplace profiles, Registry records, employer-readable summaries, National Capability Records, and handoff context. 4.5.3.3 Portfolio Evidence shall not be treated as employer verification, professional license, procurement qualification, wage entitlement, public authority approval, or execution authority by default. ### **4.5.4 Simulation Evidence.** 4.5.4.1 **Simulation Evidence** shall include evidence produced through scenario exercises, Studio workflows, digital twins, tabletop exercises, model-based exercises, crisis-learning exercises, AI workflow review, public authority learning rooms, readiness rooms, and controlled demonstrations. 4.5.4.2 Simulation Evidence shall record assumptions, model basis, data basis, scenario scope, limitations, uncertainty, confidence where applicable, role performed, review status, and public-safe interpretation. 4.5.4.3 Simulation Evidence shall not create forecast certainty, certification, public authority decision, deployment approval, operational command, finance approval, insurance approval, or execution. ### **4.5.5 Field Evidence.** 4.5.5.1 **Field Evidence** shall include evidence generated through field observation, site visits, community engagement, field exercises, environmental monitoring, disaster-risk observation, infrastructure review, WILP field practice, or comparable real-world learning activity. 4.5.5.2 Field Evidence shall include safety controls, consent and permission status where applicable, community safeguards, protected knowledge controls, geospatial sensitivity controls, privacy controls, public-safe status, and correction pathway. 4.5.5.3 Field Evidence shall not create land access, community consent, public authority approval, official inspection status, deployment authorization, or execution. ### **4.5.6 Peer Review Evidence.** 4.5.6.1 **Peer Review Evidence** shall include review by qualified peers, contributors, domain reviewers, technical reviewers, public-safe reviewers, data reviewers, AI-use reviewers, safeguard reviewers, or other scoped reviewers. 4.5.6.2 Peer Review Evidence shall record reviewer identity or role, review criteria, conflicts, scope, outcome, limitations, and correction pathway. 4.5.6.3 Peer review shall not create certification, professional licensing, public authority approval, procurement qualification, or deployment authority. ### **4.5.7 Mentor Verification Evidence.** 4.5.7.1 **Mentor Verification Evidence** shall include recorded mentor observations, supervision notes, practice confirmations, feedback summaries, performance reflections, improvement records, and completion statements within a WILP, learning pathway, Foundry contribution, Campaign pathway, Competence Cell, or Nexus Universe activity. 4.5.7.2 Mentor Verification Evidence shall be scoped, non-inflated, and privacy-aware. It shall record what the mentor observed, under what conditions, and with what limitations. 4.5.7.3 Mentor verification shall not create certification, employment, professional license, public authority approval, procurement status, or execution authority. ### **4.5.8 Employer or Host Evidence.** 4.5.8.1 **Employer or Host Evidence** shall include evidence from WILP hosts, employers, field hosts, university hosts, community hosts, public authority learning hosts, lab hosts, Foundry hosts, National Node hosts, or lawful downstream hosts. 4.5.8.2 Employer or Host Evidence may confirm participation, task exposure, work product, supervision, conduct within scope, safety compliance, or feedback. It shall not be converted into a hiring commitment, employment status, wage promise, professional license, procurement qualification, or public authority approval. 4.5.8.3 Host evidence shall be subject to conflict review, fair work safeguards, anti-exploitation controls, learner privacy, and correction or appeal pathways. ### **4.5.9 Public-Good Contribution Evidence.** 4.5.9.1 **Public-Good Contribution Evidence** shall include contributions to open-source software, public-good data, public-safe documentation, Reports, Campaigns, Foundry builds, Registry records, Marketplace objects, translations, accessibility improvements, mentoring, review, testing, issue triage, community support, and correction. 4.5.9.2 Public-Good Contribution Evidence may support iCRS, ILA, skills-wallet records, micro-credentials, National Capability Records, and Nexus Universe outputs. 4.5.9.3 Public-Good Contribution Evidence shall not create employment, compensation, equity, token, procurement qualification, provider validation, professional license, or execution by default. ### **4.5.10 Public-Safe Output Evidence.** 4.5.10.1 **Public-Safe Output Evidence** shall include evidence that a person or team can translate complex information into public-facing outputs without overclaiming warning, approval, finance, procurement, certification, consent, execution, or public authority status. 4.5.10.2 Such evidence may include public-safe summaries, no-warning risk communication, sensitive-data transformation, accessible summaries, community-facing materials, protected knowledge redaction, correction notices, and public repair statements. 4.5.10.3 Public-Safe Output Evidence shall not create public warning authority, media authority, public authority approval, certification, procurement recommendation, or consent. ### **4.5.11 National Portfolio Contribution Evidence.** 4.5.11.1 **National Portfolio Contribution Evidence** shall include contributions to National Context Records, National Systems-Risk Maps, National Challenge Briefs, National Skills Maps, National Capability Records, Observatory need records, Core Build requests, safeguard records, public authority learning records, readiness question records, Competence Cell workplans, Nexus Universe routing records, and National Portfolio archives. 4.5.11.2 National Portfolio Contribution Evidence shall be nationally contextual, public-safe, safeguard-reviewed where applicable, and correctionable. 4.5.11.3 Such evidence shall not create country ranking, national endorsement, public authority approval, procurement status, financeability, professional qualification, consent, or execution. ### **4.5.12 Correction Evidence.** 4.5.12.1 **Correction Evidence** shall include evidence that a person, team, role, or institution has identified, reported, corrected, amended, superseded, withdrawn, retracted where necessary, recalled, archived, or publicly repaired an SCF object or related output. 4.5.12.2 Correction Evidence shall be treated as positive trust infrastructure where performed responsibly. Competence includes the ability to correct and not merely the ability to produce. 4.5.12.3 Correction Evidence shall not be used punitively without due process, context, appeal where applicable, and boundary review. *** ## **4.6 Competency Mapping Standards** ### **4.6.1 SCF-to-ESCO Mapping.** 4.6.1.1 SCF may map competencies to the European Skills, Competences, Qualifications and Occupations framework or comparable taxonomies for interoperability, cross-reference, translation, and labor-market intelligence. 4.6.1.2 SCF-to-ESCO mapping shall be treated as semantic mapping, not legal equivalence, credential equivalence, employment eligibility, public authority recognition, or professional qualification. ### **4.6.2 SCF-to-O\*NET Mapping.** 4.6.2.1 SCF may map competencies to O\*NET or comparable occupational information systems for occupation-to-task-to-skill decomposition, transferable skills analysis, labor-market intelligence, and role profile development. 4.6.2.2 SCF-to-O\*NET mapping shall support analysis only and shall not create U.S. employment status, occupational licensing, wage determination, immigration classification, or procurement qualification. ### **4.6.3 SCF-to-ISCO Mapping.** 4.6.3.1 SCF may map occupation and role profiles to the International Standard Classification of Occupations or comparable classification systems to support international comparability, national skills mapping, statistical interpretation, and cross-border competency translation. 4.6.3.2 SCF-to-ISCO mapping shall not create legal classification, credential equivalence, labor authorization, employment eligibility, professional recognition, or public authority decision. ### **4.6.4 SCF-to-TVET Mapping.** 4.6.4.1 SCF may map competencies to technical and vocational education and training frameworks, apprenticeship standards, qualification frameworks, occupational standards, training packages, and national skills systems. 4.6.4.2 SCF-to-TVET mapping shall support alignment, bridge learning, WILP design, Recognition of Prior Learning, and National Skills Maps. It shall not replace TVET authorities, qualification authorities, apprenticeship regulators, or statutory credential systems. ### **4.6.5 SCF-to-Higher-Education Learning Outcomes Mapping.** 4.6.5.1 SCF may map competencies to higher-education learning outcomes, course outcomes, program outcomes, capstone outcomes, research training outcomes, continuing education outcomes, and micro-credential outcomes. 4.6.5.2 Such mapping shall support curriculum alignment, credit discussions, portfolio evidence, and learner mobility, but shall not create academic credit, degree equivalence, admission status, faculty approval, institutional accreditation, or university recognition by implication. ### **4.6.6 SCF-to-Micro-Credential Mapping.** 4.6.6.1 SCF shall map competencies to micro-credentials by defining scope, evidence basis, level, review requirement, issuer identity, expiry or renewal rule, display rule, ILA linkage, iCRS linkage, Registry status, and correction pathway. 4.6.6.2 Micro-credential mapping shall not create professional certification, professional license, employment eligibility, procurement qualification, public authority approval, or deployment authority unless separately and lawfully recorded by the competent authority. ### **4.6.7 SCF-to-Professional-Body Mapping.** 4.6.7.1 SCF may map competencies to professional-body frameworks, continuing professional development requirements, occupational standards, ethical codes, or practice expectations where relevant. 4.6.7.2 Such mapping shall not create membership, licensure, certification, professional standing, continuing education credit, regulated practice authority, or professional-body approval unless separately and lawfully recorded by that body. ### **4.6.8 SCF-to-Public-Authority-Learning Mapping.** 4.6.8.1 SCF may map competencies to public authority learning needs, public-sector workforce capability, public employment service learning, disaster-risk learning, public finance learning, procurement literacy, regulatory literacy, emergency management learning, public health learning, and public-safe reporting literacy. 4.6.8.2 Public authority learning mapping shall not create public authority approval, official training completion unless separately recorded, statutory competence, public decision, regulatory clearance, public finance allocation, public warning authority, or emergency command. ### **4.6.9 SCF-to-National-Portfolio Mapping.** 4.6.9.1 SCF shall map competencies to National Portfolios by identifying skills, role capabilities, learning needs, WILP needs, Competence Cell needs, public authority learning needs, National Skills Map needs, National Capability Record needs, Nexus Universe preparation needs, and lawful handoff dependency needs. 4.6.9.2 National Portfolio mapping shall support country-level capability formation and national ownership. It shall not create country ranking, national endorsement, public authority approval, procurement status, financeability, insurability, consent, or execution. ### **4.6.10 SCF-to-Foundry-Object and Handoff-Dependency Mapping.** 4.6.10.1 SCF shall map competencies to Foundry objects and handoff dependencies, including quests, bounties, builds, software objects, data objects, model objects, dashboard objects, Studio workflows, Reports, Registry records, Marketplace objects, Grid inputs, TRL notes, National Portfolio objects, and Handoff Competency Context Notes. 4.6.10.2 Such mapping shall identify required competence, evidence basis, review needs, safeguard needs, data and AI-use labels, support class, public-safe status, handoff relevance, and correction pathway. 4.6.10.3 Foundry and handoff mapping shall not create execution authority, deployment approval, employment, procurement, finance, insurance, public authority approval, professional license, or consent. *** ## **4.7 Competency Boundary Rules** ### **4.7.1 Competency Record Is Not License.** 4.7.1.1 A Competency Record shall not be a professional license, trade license, statutory qualification, regulated practice approval, academic degree, legal authorization, public authority credential, or professional-body certification unless separately and lawfully issued by the competent authority and expressly recorded as such. 4.7.1.2 SCF shall use clear notices wherever competency records could be mistaken for licensure or regulated qualification. ### **4.7.2 Skill Evidence Is Not Employment Guarantee.** 4.7.2.1 Skill evidence shall not guarantee employment, placement, promotion, income, wage level, contract award, apprenticeship acceptance, visa outcome, immigration pathway, or hiring decision. 4.7.2.2 Employers and lawful downstream recipients shall remain responsible for independent review, hiring decisions, legal compliance, labor protections, and supervision. ### **4.7.3 Micro-Credential Is Not Professional Certification Unless Separately Recorded.** 4.7.3.1 A micro-credential shall be a bounded evidence record by default. It shall not be a professional certification, license, degree, public authority credential, statutory qualification, procurement qualification, deployment approval, or employment eligibility unless separately and lawfully recorded by a competent authority. 4.7.3.2 Micro-credentials shall include scope, evidence basis, review level, issuer identity, expiry or renewal rules where applicable, public display rules, correction rules, and no-conversion notices. ### **4.7.4 Reviewer Capability Is Not Public Authority Approval.** 4.7.4.1 Reviewer Capability shall authorize review only within the reviewer’s recorded scope and SCF role. It shall not create public authority approval, regulatory decision, certification, procurement clearance, finance approval, insurance approval, legal determination, or emergency command. 4.7.4.2 Reviews involving public authority-sensitive, finance-sensitive, procurement-sensitive, data-sensitive, AI-sensitive, cyber-sensitive, safeguard-sensitive, or community-sensitive matters shall include boundary notices and escalation pathways. ### **4.7.5 Maintainer Capability Is Not Deployment Authority.** 4.7.5.1 Maintainer Capability shall authorize stewardship, versioning, support, correction, withdrawal, and archive within scope. It shall not authorize deployment, operational use, production release by a downstream actor, public authority adoption, procurement, finance, insurance, or execution. 4.7.5.2 A maintainer may maintain a public-good object without warranting its use, validating its provider, certifying its safety, or authorizing implementation. ### **4.7.6 Learning Evidence Is Not Procurement Qualification.** 4.7.6.1 Learning evidence, assessment evidence, WILP evidence, micro-credential evidence, portfolio evidence, or public-good contribution evidence shall not create procurement qualification, preferred supplier status, vendor validation, tender eligibility, procurement recommendation, or public purchasing approval by default. 4.7.6.2 Procurement decisions shall remain outside SCF and shall require separate lawful procurement processes by competent actors. ### **4.7.7 Competency Mapping Is Not Equivalence by Default.** 4.7.7.1 Competency mapping to ESCO, O\*NET, ISCO, TVET frameworks, higher-education outcomes, professional-body frameworks, micro-credentials, public authority learning, National Portfolios, Foundry objects, or handoff dependencies shall not create equivalence by default. 4.7.7.2 Mapping shall mean only that a relationship has been identified for learning, translation, analysis, interoperability, portfolio design, or handoff context. Equivalence, recognition, credit, license, certification, or statutory effect shall require separate competent authority decision and record. *** ## **4.8 Final Part IV Operating Statement** 4.8.1 SCF shall operate through a disciplined competency ontology that distinguishes competency, skill, knowledge, ability, practice, judgment, disposition, role capability, contextual competence, and evidence of competence. This ontology shall prevent vague skill claims, inflated credential claims, tool-use overclaims, and unbounded expertise claims from becoming authority. 4.8.2 SCF shall organize competencies into families and Nexus domain clusters that cover foundational literacies, technical and vocational competence, digital and data competence, AI and human-AI collaboration, cybersecurity and digital trust, systems thinking, risk and resilience, sustainability and green skills, governance and ethics, communication and leadership, public-safe reporting, safeguards and inclusion, entrepreneurship and innovation, care and civic competence, lawful handoff literacy, WFEH-B, DRR, DRF, DRI, DICE, GRIx, Observatory, Studio, Foundry, Campaigns, Reports, Marketplace, Registry, Grid, Risk Agency, and Nexus Universe. 4.8.3 SCF shall classify competence by level, from Awareness through Literacy, Applied Practice, Supervised Contribution, Independent Contribution, Reviewer Capability, Maintainer Capability, Steward Capability, Mentor Capability, Systems Leadership Capability, National Capability Contributor, and Handoff Context Contributor. Each level shall have distinct evidence, review, scope, limitation, display, and correction requirements. 4.8.4 SCF shall accept multiple evidence types, including assessment evidence, work product evidence, portfolio evidence, simulation evidence, field evidence, peer review evidence, mentor verification, employer or host evidence, public-good contribution evidence, public-safe output evidence, National Portfolio contribution evidence, and correction evidence. No evidence type shall create authority beyond its recorded scope. 4.8.5 SCF may map to external occupational, skills, education, professional, credential, public authority learning, National Portfolio, Foundry, and handoff frameworks for interoperability and translation. Such mapping shall not create equivalence, license, employment status, public authority approval, procurement qualification, financeability, insurability, consent, deployment authorization, or execution by default. 4.8.6 The operating rule of Part IV is that competence must be structured, evidenced, contextual, reviewable, display-controlled, correctionable, and bounded. SCF may make capability visible, portable, useful, and nationally relevant, but it shall not convert competency records, skill evidence, micro-credentials, reviewer status, maintainer status, learning evidence, or mapping into authority 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/iv.-ontology.md?ask= ``` 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.