# V. LEARNING ## **5.1 Learning Architecture Doctrine** ### **5.1.1 Learning as Public-Good Capability Formation.** 5.1.1.1 **Learning** within the Sustainable Competency Framework (SCF) shall mean the structured, evidence-bearing, accessible, inclusive, competency-mapped, reviewable, correctionable, and public-good process through which individuals, teams, institutions, communities, public authority learning participants, contributors, mentors, reviewers, maintainers, and lawful downstream actors develop the knowledge, skills, abilities, practice, judgment, disposition, role capability, contextual competence, and boundary literacy required to participate responsibly in the Nexus Ecosystem. 5.1.1.2 Learning under SCF shall not be treated as content consumption, course completion, credential accumulation, or platform engagement alone. It shall be a capability-formation architecture that connects learning objects, competency maps, WILPs, ILA records, iCRS recognition, micro-credentials, National Skills Maps, Competence Cells, National Working Groups, Nexus Academy, Risk Academy, Nexus Foundry, Nexus Campaigns, Nexus Reports, Nexus Marketplace, Nexus Registry, Nexus Studio, Nexus Grid, Nexus Universe, Nexus Rails, Nexus Network, National Portfolios, and lawful handoff context. 5.1.1.3 SCF learning shall be public-good by design. It shall support resilience, risk literacy, workforce transition, national capability formation, open and controlled digital public goods, evidence production, public-safe reporting, safeguard discipline, correctionability, and lawful handoff literacy without converting learning activity into professional licensure, employment status, public authority approval, procurement qualification, financeability, insurability, consent, deployment authorization, or execution authority. 5.1.1.4 Learning shall be structured as a continuing lifecycle rather than a one-time pathway. A learner may move through awareness, literacy, applied practice, supervised contribution, independent contribution, reviewer capability, maintainer capability, steward capability, mentor capability, systems leadership capability, national capability contribution, and handoff-context contribution, subject always to scope, evidence, review, privacy, display controls, safeguards, renewal, correction, and archive. ### **5.1.2 Learning as Risk Literacy Formation.** 5.1.2.1 SCF shall treat risk literacy as a foundational capability for all Nexus learning. Risk literacy shall include the ability to understand hazards, exposure, vulnerability, resilience, uncertainty, cascading risks, systems interdependencies, public-safe communication, data limitations, model limitations, safeguard obligations, public authority boundaries, finance and procurement boundaries, and correction pathways. 5.1.2.2 Risk literacy shall not be confined to emergency managers, researchers, public authorities, insurers, engineers, or technical specialists. It shall be embedded across Nexus Academy, Risk Academy, WILPs, Campaigns, Foundry builds, Studio exercises, Reports, National Portfolios, Nexus Universe pathways, and lawful handoff literacy so that every participant understands the risk meaning and boundary conditions of their work. 5.1.2.3 Risk literacy formation shall include DRR, DRF, DRI, WFEH-B systems, climate and nature risk, cyber and cyber-physical risk, AI and data risk, infrastructure risk, public health and biosecurity-sensitive risk, community and protected knowledge risk, public authority overclaim risk, finance-readiness overclaim risk, procurement overclaim risk, and execution overclaim risk. 5.1.2.4 Risk literacy shall not create public warning authority, emergency command, official forecast authority, insurance scoring authority, investment signal authority, public authority decision authority, or operational control. It shall equip participants to understand, communicate, escalate, and correct risk-related knowledge within approved public-safe boundaries. ### **5.1.3 Learning as Workforce Resilience.** 5.1.3.1 SCF shall treat learning as workforce resilience infrastructure. Learning pathways shall support reskilling, upskilling, cross-skilling, redeployment, transition, Recognition of Prior Learning, portfolio evidence, WILP participation, public-good contribution, micro-credentialing, skills-wallet development, employer-readable summaries, and National Skills Maps. 5.1.3.2 Workforce resilience learning shall respond to changing labor markets, AI and automation, climate and nature transition, disaster disruption, cyber and infrastructure risk, public-sector capacity needs, green and blue skills demand, informal and gig work realities, care responsibilities, youth transition, mid-career transition, displaced worker needs, rural and remote access, migration and diaspora capability, and equity gaps. 5.1.3.3 SCF shall not frame workforce resilience as an individual obligation alone. Learning systems shall recognize that workforce outcomes are shaped by employers, public policy, education access, digital access, care responsibilities, discrimination, safety, job quality, public infrastructure, regional opportunity, credential inflation, language access, disability access, and institutional coordination. 5.1.3.4 Workforce resilience learning shall not create employment guarantees, wage guarantees, hiring decisions, immigration outcomes, professional licensing, procurement eligibility, public authority approval, or enterprise execution status by implication. ### **5.1.4 Learning as National Capacity Formation.** 5.1.4.1 SCF shall treat learning as a national capacity formation mechanism. Learning pathways shall support country-level capability in WFEH-B systems, DRR, DRF, DRI, climate adaptation, nature and biodiversity, public health, infrastructure resilience, AI, data, cyber, privacy, geospatial, Earth observation, digital twins, telecom, AI-RAN, O-RAN, edge, HPC, sovereign compute, cloud, robotics, drones, sensors, IoT, OT, IIoT, DLT, DePIN, quantum-relevant security, semiconductors, advanced manufacturing, biosecurity-sensitive systems, and public-good software. 5.1.4.2 National capacity formation shall connect learning to National Skills Maps, National Capability Records, National Portfolios, National Working Groups, Nexus Competence Cells, National Nodes, National Councils, Helix Councils, public authority learning rooms, Nexus Universe preparation, and lawful handoff context. 5.1.4.3 Learning shall be nationally contextual. Global or regional learning materials may be reused, translated, localized, or adapted, but national language, legal context, public authority structures, labor-market realities, community safeguards, Indigenous protocols where applicable, data sovereignty, accessibility needs, and public-safe communication requirements shall govern localization. 5.1.4.4 National capacity learning shall not create country ranking, national endorsement, official public authority action, procurement status, financeability, insurability, consent, deployment authorization, or execution authority. ### **5.1.5 Learning as Contribution Preparation.** 5.1.5.1 SCF shall prepare learners to contribute to public-good work through Nexus Foundry quests, bounties, builds, Nexus Campaigns, public-safe reporting, data stewardship, software contribution, documentation, translation, accessibility work, review, mentoring, testing, issue triage, Studio exercises, Registry records, Marketplace listings, Reports, National Portfolio objects, Nexus Universe outputs, and correction. 5.1.5.2 Contribution preparation shall include competence, evidence requirements, review expectations, role discipline, public-safe language, data and AI-use labels, cyber and privacy controls, safeguard obligations, license and attribution rules, support classes, maintainer expectations, and correction pathways. 5.1.5.3 Learning-to-contribution pathways may create ILA records, iCRS records, skills-wallet evidence, micro-credential evidence, Registry records, Marketplace displays, and National Capability Records where appropriate. Such records shall remain bounded and shall not create employment, compensation, equity, token rights, procurement qualification, provider validation, professional license, public authority approval, deployment authorization, or execution. ### **5.1.6 Learning as Public Authority Learning Support.** 5.1.6.1 SCF shall support public authority learning by providing structured, public-safe, non-decision learning pathways for public officials, public agencies, emergency managers, public employment services, public finance readers, regulators, planners, infrastructure authorities, public health actors, workforce systems, education systems, and other public authority participants. 5.1.6.2 Public authority learning may include risk literacy, DRI literacy, WFEH-B literacy, AI and data literacy, cyber and privacy literacy, public-safe reporting, finance-readiness literacy, insurance-readiness literacy, procurement-neutrality literacy, Studio practice, disaster-risk learning, public employment service learning, credential-system learning, and lawful handoff literacy. 5.1.6.3 Public authority learning shall be structured as learning, not official action. Attendance, participation, completion, discussion, scenario work, Studio exercise, report review, or Nexus Universe presence shall not create public authority approval, public warning, regulation, procurement, public finance allocation, licensing, permitting, emergency command, official endorsement, or statutory recognition. 5.1.6.4 Where public authority learning materials touch regulated, emergency, public finance, procurement, public health, public safety, or statutory subjects, SCF shall include boundary notices, role-separation language, no-decision labels, and escalation pathways for competent authority review. ### **5.1.7 Learning as Lawful Handoff Literacy.** 5.1.7.1 SCF shall include lawful handoff literacy as a required learning layer for participants whose work may create handoff context for National Consortium Companies, Project SPVs, public authorities, providers, operators, contractors, funders, insurers, donors, universities, labs, community actors where appropriate, or other competent lawful actors. 5.1.7.2 Lawful handoff learning shall cover context transfer, dependency transfer, evidence transfer, recipient responsibility, public-good stack and enterprise-stack separation, public authority dependencies, legal dependencies, safeguard dependencies, data dependencies, AI and cyber dependencies, finance and insurance questions, procurement neutrality, provider-neutrality notes, sponsor-boundary notes, correction, recall, archive, and no-execution rules. 5.1.7.3 Handoff literacy shall help participants understand how public-good learning, evidence, Reports, Registry records, Marketplace discovery, Studio workflows, Grid inputs, TRL notes, National Portfolio records, and Nexus Universe outputs may inform downstream lawful review without authorizing downstream implementation. 5.1.7.4 Handoff learning shall not create handoff authorization, execution authority, procurement approval, investment advice, insurance approval, public finance allocation, public authority action, consent, deployment, operations, or legal reliance by implication. ### **5.1.8 Learning Without Credential Overclaim.** 5.1.8.1 SCF shall distinguish learning, completion, assessment, practice, evidence, micro-credentialing, badge display, portfolio display, skills-wallet records, Registry records, Marketplace listings, and professional or statutory qualifications. No learning object, course completion, pathway completion, WILP completion, micro-credential, badge, ILA record, iCRS record, or skills-wallet display shall be represented as a professional license, degree, statutory qualification, employment guarantee, public authority approval, procurement qualification, or deployment authorization unless separately and lawfully issued by a competent authority and expressly recorded. 5.1.8.2 Learning records shall state scope, level, evidence basis, issuer or steward, review status, expiry or renewal rules where applicable, display rules, limitations, and correction pathways. 5.1.8.3 SCF shall prohibit credential inflation, misleading badges, unbounded expertise claims, pay-to-credential capture, sponsor-controlled credentials, provider validation by course association, and public authority overclaim by learning participation. 5.1.8.4 The rule of learning under SCF shall be evidence before recognition, records before display, competence before credential claims, correction before trust, and no conversion of learning into authority by implication. *** ## **5.2 Nexus Academy Structure** ### **5.2.1 Foundational Learning Pathways.** 5.2.1.1 Nexus Academy shall provide foundational learning pathways for learners, contributors, workers, public-good participants, students, youth participants, community participants, public authority learning participants, and institutional actors entering the Nexus Ecosystem. 5.2.1.2 Foundational pathways shall include Nexus orientation, public-good doctrine, non-execution, validity by record, correctionability, public-good firewall, no-conversion, public-safe communication, evidence literacy, data literacy, AI literacy, cyber hygiene, privacy basics, risk literacy, WFEH-B introduction, DRR introduction, DRI introduction, digital public goods literacy, accessibility, safeguard awareness, community and protected knowledge awareness, and lawful handoff basics. 5.2.1.3 Foundational pathways shall be designed for multilingual access, plain-language access, low-bandwidth access, mobile-first delivery, accessibility, youth safeguards, adult learning, rural and remote participation, and different levels of prior education. 5.2.1.4 Completion of foundational pathways shall evidence awareness or literacy within scope only. It shall not create professional qualification, public authority competence, employment status, procurement eligibility, or execution capability. ### **5.2.2 Technical Learning Pathways.** 5.2.2.1 Nexus Academy shall provide technical learning pathways aligned with SCF competency families, National Portfolios, Nexus Foundry, DICE, GRIx, DRI, Observatory, Studio, Grid, Reports, Marketplace, Registry, and Nexus Universe needs. 5.2.2.2 Technical pathways may cover public-good software, data pipelines, APIs, dashboards, metadata, schemas, ontologies, AI evaluation, cyber hygiene, secure software, geospatial analysis, Earth observation, digital twins, sensors, robotics, drones, telecom, AI-RAN, O-RAN, edge, HPC, sovereign compute, cloud, secure rooms, compute-to-data, WFEH-B systems, DRR, DRF literacy, DRI, climate and nature skills, infrastructure resilience, biosecurity-sensitive governance, and advanced manufacturing literacy. 5.2.2.3 Technical pathways shall distinguish awareness, literacy, applied practice, supervised contribution, independent contribution, reviewer capability, maintainer capability, and handoff-context relevance. 5.2.2.4 Technical learning shall not authorize deployment, system access, safety-critical work, regulated practice, public authority action, procurement, finance, insurance, or execution unless separately and lawfully established outside SCF. ### **5.2.3 Data and AI Learning Pathways.** 5.2.3.1 Nexus Academy shall provide Data and AI learning pathways covering data literacy, metadata, data dictionaries, lineage, data quality, data rights, privacy, data minimization, purpose limitation, data-use labels, AI-use labels, public-safe data transformation, secure-room work, compute-to-data, model cards, system cards, benchmark cards, prompt-injection awareness, agentic workflow controls, AI evaluation, bias and harm review, AI incident escalation, human review, and public-safe AI outputs. 5.2.3.2 Data and AI pathways shall be governed by role-based access, data classification, AI-use controls, public-safe review, safeguard review, and no automated high-stakes decision rules. 5.2.3.3 AI learning shall not promote tool fluency as competence. Data and AI competence shall require judgment, context, evidence, security, privacy, public-safe output review, and correctionability. 5.2.3.4 Data and AI learning shall not create data access rights, AI safety certification, professional certification, deployment approval, public authority decision authority, financeability, insurability, procurement readiness, or execution. ### **5.2.4 Public-Good Software Learning Pathways.** 5.2.4.1 Nexus Academy shall provide public-good software learning pathways for contributors, maintainers, reviewers, documentation contributors, testers, translators, accessibility contributors, data contributors, model contributors, dashboard contributors, and software stewards. 5.2.4.2 These pathways shall include repository literacy, version control, issue tracking, code review, documentation, licensing, attribution, open-source governance, contribution terms, security disclosure, dependency scanning, SBOM literacy, secret scanning, secure defaults, API literacy, SDK literacy, connectors, reproducibility packages, release notes, support classes, deprecation, correction, withdrawal, and archive. 5.2.4.3 Public-good software learning shall be open where safe and controlled where necessary. It shall support public-good contribution and enterprise-grade support readiness without creating warranty, procurement preference, provider validation, deployment authorization, or execution. ### **5.2.5 National Portfolio Learning Pathways.** 5.2.5.1 Nexus Academy shall provide National Portfolio learning pathways to support country-level capability formation, National Systems-Risk Maps, National Challenge Briefs, National Skills Maps, National Capability Records, public authority learning records, Competence Cell workplans, Core Build requests, Nexus Universe preparation, and lawful handoff context. 5.2.5.2 National Portfolio pathways shall be localized by country context, language, legal environment, labor-market conditions, public authority structure, data sovereignty requirements, safeguards, accessibility needs, community context, Indigenous protocols where applicable, and National Node routing. 5.2.5.3 National Portfolio learning shall not create country ranking, public authority approval, national endorsement, procurement status, financeability, insurability, consent, deployment authorization, or execution. ### **5.2.6 Foundry Contributor Learning Pathways.** 5.2.6.1 Nexus Academy shall provide Foundry Contributor learning pathways that prepare learners to participate in quests, bounties, builds, micro-production, reviews, testing, documentation, public-safe summaries, data objects, software objects, dashboards, Studio workflows, Marketplace objects, Registry records, Grid inputs, TRL notes, Reports, National Portfolio objects, and handoff dependency packages. 5.2.6.2 Foundry Contributor pathways shall include task scoping, evidence requirements, contribution rules, license and attribution, support classes, review gates, maintainer roles, public-safe release classes, data and AI-use labels, cyber and privacy controls, safeguard rules, correction, archive, and no-employment boundaries. 5.2.6.3 Foundry learning shall prepare contribution, not employment or execution. Completion shall not create bounty entitlement beyond the applicable bounty terms, employment status, procurement qualification, provider validation, deployment approval, or lawful handoff authorization. ### **5.2.7 Marketplace and Registry Learning Pathways.** 5.2.7.1 Nexus Academy shall provide Marketplace and Registry learning pathways covering object metadata, listing rules, Registry status truth, support status, version records, provider contribution records, sponsor support records, public authority participation records, correction records, archive records, public-safe display, delisting, suspension, withdrawal, and no-conversion notices. 5.2.7.2 These pathways shall prepare learners, stewards, maintainers, contributors, and reviewers to make objects discoverable without turning discovery into endorsement, certification, procurement approval, provider validation, or implementation authority. 5.2.7.3 Marketplace and Registry learning records shall not create listing entitlement, status entitlement, public display entitlement, procurement status, employment status, certification, or endorsement. ### **5.2.8 Studio, Grid, and TRL Learning Pathways.** 5.2.8.1 Nexus Academy shall provide Studio, Grid, and TRL learning pathways covering controlled runtime environments, simulations, digital twins, dashboards, AI workflow review, secure-room workflows, public authority learning rooms, readiness rooms, assumptions registers, dependency registers, model limitations, no-decision rules, TRL 1–10 literacy, evidence sufficiency, review gates, downgrade, suspension, withdrawal, reinstatement, and handoff dependency readiness. 5.2.8.2 These pathways shall prepare participants to understand and produce bounded readiness evidence without confusing simulations, demonstrations, Grid status, or TRL notes with certification, procurement readiness, financeability, insurability, public authority approval, deployment authorization, or execution. ### **5.2.9 Nexus Universe Preparation Pathways.** 5.2.9.1 Nexus Academy shall provide Nexus Universe preparation pathways for participants, teams, National Working Groups, Competence Cells, Campaign teams, Foundry contributors, public authority learning participants, capital readers, insurance readers, donors, universities, communities, sponsors, providers, media-safe participants, and lawful downstream actors. 5.2.9.2 These pathways shall cover annual surge logic, National Portfolio convergence, Core Build participation, arena preparation, room protocols, public authority learning boundaries, readiness room boundaries, capital-reader and insurance-reader room boundaries, public-safe reporting, sponsor controls, provider controls, community safeguard rooms, protected knowledge rooms, correction rooms, continuation records, and archive. 5.2.9.3 Nexus Universe preparation shall not convert attendance, visibility, participation, room access, sponsor presence, provider demonstration, public authority presence, capital-reader presence, or outputs into endorsement, approval, procurement, finance, insurance, consent, certification, deployment authorization, or execution. ### **5.2.10 Lawful Handoff Learning Pathways.** 5.2.10.1 Nexus Academy shall provide lawful handoff learning pathways for participants whose learning, evidence, contribution, review, maintenance, Studio work, Grid work, Reports work, National Portfolio work, or Nexus Universe participation may become handoff context. 5.2.10.2 Handoff learning pathways shall cover public-good stack and enterprise-stack separation, recipient responsibility, dependency packages, evidence context, data context, method context, Studio context, Grid and TRL context, public-safe status, safeguard status, public authority dependencies, legal dependencies, finance and insurance questions, procurement boundaries, provider-neutrality notes, sponsor-boundary notes, correction and recall pathways, and archive. 5.2.10.3 Lawful handoff learning shall not create handoff approval, execution authority, procurement recommendation, investment advice, insurance approval, public finance allocation, public authority action, consent, deployment, operations, or legal reliance by implication. *** ## **5.3 Risk Academy Structure** ### **5.3.1 Systems-Risk Literacy.** 5.3.1.1 Risk Academy shall provide systems-risk literacy covering interdependence, cascading risk, feedback loops, complexity, uncertainty, resilience, vulnerability, exposure, hazard interaction, cyber-physical systems, infrastructure dependencies, WFEH-B systems, climate and nature systems, public health systems, supply chains, social systems, and institutional boundaries. 5.3.1.2 Systems-risk literacy shall equip participants to read, question, interpret, and communicate risk without overclaiming forecast certainty, public warning authority, official status, public authority decision, insurance scoring, investment signal, or command authority. ### **5.3.2 DRR Literacy.** 5.3.2.1 Risk Academy shall provide Disaster Risk Reduction literacy covering risk identification, risk reduction, preparedness, mitigation, resilience, vulnerability reduction, exposure reduction, community resilience, public-safe communication, after-action learning, and multi-hazard awareness. 5.3.2.2 DRR literacy shall support National Portfolios, public authority learning, Campaigns, DRI interpretation, Observatory outputs, Studio exercises, Nexus Universe arenas, and lawful handoff dependency awareness. 5.3.2.3 DRR literacy shall not create emergency response authority, public warning authority, public authority approval, or operational deployment authority. ### **5.3.3 DRF Literacy.** 5.3.3.1 Risk Academy shall provide Disaster Risk Finance literacy covering protection gaps, risk layering, contingency finance concepts, insurance-readiness questions, public finance relevance questions, donor-readiness questions, assumptions registers, dependency registers, diligence-gap registers, no-reliance statements, non-solicitation, non-transactionality, and regulated-perimeter discipline. 5.3.3.2 DRF literacy shall support finance-readiness understanding without crossing into investment advice, insurance advice, brokerage, underwriting, lending, guarantee issuance, rating, securities activity, donor allocation, public finance allocation, or transaction execution. ### **5.3.4 DRI Literacy.** 5.3.4.1 Risk Academy shall provide Disaster Risk Intelligence literacy covering indicators, signals, uncertainty labels, confidence labels, dashboard interpretation, hotspot records, multi-hazard records, cascade records, public-safe intelligence summaries, correction records, archive records, no-warning notices, and no-rating notices. 5.3.4.2 DRI literacy shall support DRI interpretation and public-safe communication. It shall not create official warning authority, forecast certainty, insurance score, investment signal, public authority decision, or emergency command. ### **5.3.5 WFEH-B Literacy.** 5.3.5.1 Risk Academy shall provide WFEH-B literacy covering water, food, energy, health, biodiversity, nature systems, infrastructure dependencies, climate impacts, cyber-physical dependencies, supply-chain dependencies, cross-system cascades, resilience capacity, and public-safe reporting. 5.3.5.2 WFEH-B literacy shall connect to National Portfolios, Nexus Observatory, GRIx, DRI, Studio simulations, Foundry builds, Campaigns, Reports, Nexus Universe, and lawful handoff context. 5.3.5.3 WFEH-B literacy shall not create public health decisions, environmental approvals, official risk classifications, procurement preferences, or project authorization. ### **5.3.6 Public-Safe Reporting Literacy.** 5.3.6.1 Risk Academy shall provide public-safe reporting literacy covering evidence translation, no-warning language, no-approval language, no-finance language, no-procurement language, no-certification language, no-consent language, no-execution language, sensitive data controls, protected knowledge controls, public repair, correction notices, and archive labels. 5.3.6.2 Public-safe reporting literacy shall be required for contributors to Reports, Campaigns, DRI summaries, Observatory outputs, National Portfolio summaries, Nexus Universe outputs, Marketplace listings, Registry records, and handoff context notes. 5.3.6.3 Public-safe reporting literacy shall not create public warning authority, official communication authority, media authority, public authority approval, or endorsement. ### **5.3.7 Public Authority Learning Literacy.** 5.3.7.1 Risk Academy shall provide public authority learning literacy covering role separation, public authority boundaries, no-decision rooms, public finance boundaries, procurement boundaries, emergency command boundaries, public warning boundaries, regulatory boundaries, official action outside SCF, and public authority participation records. 5.3.7.2 Public authority learning literacy shall support public officials and non-public participants in understanding the difference between learning, dialogue, evidence, and official action. 5.3.7.3 Public authority learning literacy shall not substitute for statutory training, official authority, legal authorization, regulatory approval, public finance allocation, or emergency command. ### **5.3.8 Finance-Readiness and Insurance-Readiness Literacy.** 5.3.8.1 Risk Academy shall provide finance-readiness and insurance-readiness literacy covering capital-readability, assumptions, dependencies, diligence gaps, risk layering, insurance-readiness questions, donor-readiness questions, public finance relevance questions, no-reliance, non-solicitation, non-transactionality, regulated perimeter, and handoff dependencies. 5.3.8.2 This literacy shall support understanding by learners, public authority learning participants, National Investors Councils, capital readers, insurers, donors, public finance readers, Foundry teams, National Working Groups, Competence Cells, and Nexus Universe participants. 5.3.8.3 Finance-readiness and insurance-readiness literacy shall not constitute investment advice, insurance advice, underwriting, brokerage, lending, guarantee issuance, donor commitment, public finance allocation, rating, valuation, bankability, financeability, insurability, or transaction execution. ### **5.3.9 Safeguard Literacy.** 5.3.9.1 Risk Academy shall provide safeguard literacy covering community safeguards, Indigenous protocols where applicable, protected knowledge, youth safeguards, disability inclusion, accessibility, humanitarian sensitivity, non-extractive engagement, privacy, sensitive data, sensitive geospatial information, community-facing correction, and consent boundaries. 5.3.9.2 Safeguard literacy shall be embedded in all public-good learning, WILPs, Foundry work, Campaigns, Reports, Studio exercises, National Portfolios, Nexus Universe, and handoff context. 5.3.9.3 Safeguard literacy shall not create consent, representation authority, protected knowledge permission, community endorsement, Indigenous authorization, public authority approval, or deployment authorization. ### **5.3.10 Crisis-Learning and After-Action Learning.** 5.3.10.1 Risk Academy shall provide crisis-learning and after-action learning pathways for reviewing disasters, disruptions, cyber incidents, public health events, infrastructure failures, climate extremes, humanitarian situations, Campaign incidents, data incidents, AI incidents, public-safe incidents, and boundary incidents. 5.3.10.2 After-action learning shall convert events into evidence, lessons, Docket items, learning updates, competency updates, public-safe summaries, correction records, safeguard updates, National Portfolio updates, and archive records. 5.3.10.3 Crisis-learning shall not create blame by default, legal determination, official inquiry, public authority decision, public warning, emergency command, insurance determination, investment signal, or procurement determination. *** ## **5.4 Learning Object Taxonomy** ### **5.4.1 Course.** 5.4.1.1 A **Course** shall mean a structured learning sequence composed of modules, units, lessons, exercises, assessments, practice activities, evidence requirements, and completion criteria mapped to SCF competencies. 5.4.1.2 Courses shall include purpose, scope, target learners, prerequisites, competency mapping, learning outcomes, evidence requirements, assessment method, accessibility status, language status, AI-use status, data-use status, public-safe status, credential relevance, correction pathway, version, and archive rule. 5.4.1.3 Course completion shall not create professional license, employment guarantee, public authority competence, procurement qualification, deployment approval, or execution authority. ### **5.4.2 Module.** 5.4.2.1 A **Module** shall mean a coherent component of a course or pathway focused on a competency family, domain, tool, method, task, role, risk, boundary, or evidence requirement. 5.4.2.2 Modules may be reused across pathways where context, prerequisites, language, accessibility, and public-safe status permit. 5.4.2.3 Module reuse shall not imply equivalence across all contexts. Localization, mapping, review, or supplementation may be required. ### **5.4.3 Unit.** 5.4.3.1 A **Unit** shall mean a smaller instructional block within a module that addresses a defined concept, task, method, boundary, scenario, or evidence requirement. 5.4.3.2 Units shall be versioned, reviewable, reusable, accessible where feasible, and linked to competency records or learning outcomes. ### **5.4.4 Lesson.** 5.4.4.1 A **Lesson** shall mean a discrete teaching object that may include explanation, examples, demonstrations, exercises, readings, videos, simulations, prompts, discussion questions, or practice tasks. 5.4.4.2 Lessons shall be designed to support comprehension, practice, evidence, and correction. Where lessons touch sensitive domains, they shall include public-safe and safeguard controls. ### **5.4.5 Lab.** 5.4.5.1 A **Lab** shall mean a guided practical learning environment for technical, data, AI, cyber, geospatial, software, field, Studio, simulation, public-safe reporting, or domain-specific practice. 5.4.5.2 Labs shall define permitted tools, datasets, AI-use labels, cyber controls, privacy controls, output review, supervision level, evidence requirements, and safety rules. 5.4.5.3 Lab completion shall not authorize deployment, system access, public authority action, or enterprise execution. ### **5.4.6 Scenario.** 5.4.6.1 A **Scenario** shall mean a structured hypothetical, historical, simulated, or synthetic situation used to teach judgment, risk interpretation, systems thinking, public-safe communication, decision boundaries, crisis learning, or handoff dependency awareness. 5.4.6.2 Scenarios shall include assumptions, scope, limitations, uncertainty, public-safe status, and debrief requirements. 5.4.6.3 Scenario learning shall not create forecast certainty, public warning, public authority decision, or operational command. ### **5.4.7 Simulation.** 5.4.7.1 A **Simulation** shall mean a model-based, role-based, data-based, digital twin-based, tabletop, Studio-based, or interactive environment used to practice interpretation, judgment, communication, coordination, or technical workflows. 5.4.7.2 Simulations shall record model basis, data basis, assumptions, limitations, confidence where applicable, output controls, and correction pathway. 5.4.7.3 Simulation outputs shall not be treated as certification, prediction, deployment approval, public authority decision, financeability, insurability, or execution. ### **5.4.8 Studio Exercise.** 5.4.8.1 A **Studio Exercise** shall mean a controlled runtime learning activity within Nexus Studio or comparable environment involving dashboards, digital twins, scenarios, AI workflow review, data rooms, secure rooms, public authority learning rooms, readiness rooms, capital-reader rooms, insurance-reader rooms, Nexus Universe workflows, or handoff demonstrations. 5.4.8.2 Studio Exercises shall include no-command rules, no-write-back rules, access controls, logging, output review, data export restrictions, AI-use restrictions, public-safe restrictions, shutdown triggers, correction triggers, and archive rules. 5.4.8.3 Studio Exercise participation shall not create operational authority, decision authority, public authority action, finance approval, insurance approval, deployment authorization, or execution. ### **5.4.9 Field Exercise.** 5.4.9.1 A **Field Exercise** shall mean a supervised learning activity conducted in a physical, community, environmental, infrastructure, workplace, disaster-risk, public service, health, biodiversity, or other real-world setting. 5.4.9.2 Field Exercises shall require safety controls, host permissions, privacy controls, community safeguards, protected knowledge controls, geospatial sensitivity controls, public-safe output review, supervision, and incident pathways. 5.4.9.3 Field Exercises shall not create land access rights, community consent, public authority approval, official inspection status, deployment authorization, or execution. ### **5.4.10 Review Exercise.** 5.4.10.1 A **Review Exercise** shall mean a learning object designed to build reviewer capability through evaluation of evidence, work products, learning outputs, public-safe outputs, data-use labels, AI-use labels, safeguard status, Registry records, Marketplace listings, Grid inputs, TRL notes, or handoff context. 5.4.10.2 Review Exercises shall include review criteria, conflict awareness, limitation statements, correction pathways, and escalation rules. 5.4.10.3 Completion of a Review Exercise shall not create reviewer appointment, certification authority, public authority approval, or procurement authority. ### **5.4.11 Public-Safe Reporting Exercise.** 5.4.11.1 A **Public-Safe Reporting Exercise** shall mean a learning object designed to teach 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, correction notices, and public repair. 5.4.11.2 Public-Safe Reporting Exercises shall be required where learners may contribute to Reports, Campaigns, Observatory summaries, DRI summaries, National Portfolio summaries, Marketplace listings, Registry records, Nexus Universe outputs, or handoff notes. ### **5.4.12 Contribution Task.** 5.4.12.1 A **Contribution Task** shall mean a scoped public-good task through which a learner or contributor may produce evidence, support a build, improve documentation, translate content, review an object, test software, classify data, create metadata, prepare public-safe summaries, or support correction. 5.4.12.2 Contribution Tasks shall include scope, evidence requirements, review status, attribution rules, license status, support class, labor boundary, and correction pathway. 5.4.12.3 Contribution Tasks shall not create employment, compensation, procurement qualification, provider validation, or execution by default. ### **5.4.13 Quest.** 5.4.13.1 A **Quest** shall mean a structured challenge or learning-to-contribution pathway aligned with Nexus Foundry, Campaigns, Academy, National Portfolios, DICE, GRIx, DRI, Observatory, Studio, Reports, Marketplace, Registry, Grid, TRL, Nexus Universe, or handoff dependency needs. 5.4.13.2 Quests shall define objective, context, required competencies, evidence outputs, review gates, public-safe rules, support class, bounty relationship where applicable, and archive rule. 5.4.13.3 Quest completion shall not create employment, procurement qualification, professional license, provider validation, deployment approval, or execution. ### **5.4.14 Bounty.** 5.4.14.1 A **Bounty** shall mean a scoped contribution opportunity with defined output, evidence requirement, review process, recognition or reward terms, labor boundary, support class, and correction pathway. 5.4.14.2 Bounties may support learning, public-good contribution, Foundry builds, Campaign outputs, data work, software work, documentation, translation, accessibility, review, testing, and correction. 5.4.14.3 Bounty participation shall not create employment by default. Any monetary, stipend, honorarium, or reward arrangement shall be separately governed, lawful, transparent, and non-converting. ### **5.4.15 Build.** 5.4.15.1 A **Build** shall mean an evidence-producing public-good production object, including software builds, data builds, dashboard builds, ontology builds, Studio workflow builds, learning builds, Report builds, Campaign builds, Marketplace builds, Registry builds, Grid builds, TRL evidence builds, National Portfolio builds, and handoff dependency builds. 5.4.15.2 Builds shall include purpose, scope, maintainers, contributors, dependencies, evidence requirements, review gates, release class, support class, public-safe status, license or rights status where applicable, correction pathway, and archive rule. 5.4.15.3 Build completion shall not create product certification, warranty, procurement recommendation, deployment authorization, provider validation, financeability, insurability, public authority approval, or execution. ### **5.4.16 Capstone.** 5.4.16.1 A **Capstone** shall mean an integrative learning object requiring learners to apply multiple competencies across a defined problem, domain, workflow, scenario, public-good challenge, National Portfolio need, Foundry build, Studio exercise, Report, Campaign, or handoff-context question. 5.4.16.2 Capstones shall require evidence, review, reflection, public-safe communication, correction pathway, and limitations. They may support portfolio evidence, micro-credential evidence, ILA records, iCRS records, and skills-wallet display. 5.4.16.3 Capstones shall not create professional license, degree equivalence, employment guarantee, procurement qualification, public authority approval, deployment authorization, or execution. ### **5.4.17 Portfolio Artifact.** 5.4.17.1 A **Portfolio Artifact** shall mean a curated piece of evidence included in a learner’s ILA, skills wallet, Marketplace profile where permitted, Registry record where applicable, micro-credential evidence package, WILP record, National Capability Record, or handoff competency context. 5.4.17.2 Portfolio Artifacts may include assessments, work products, simulations, field evidence, public-safe outputs, Foundry contributions, Campaign contributions, Reports contributions, reviews, mentor verifications, host verifications, and correction evidence. 5.4.17.3 Portfolio display shall be controlled by privacy, consent, display permissions, youth safeguards, sensitive profile controls, and no-overclaim notices. Display shall not be endorsement, hiring decision, professional certification, or public authority approval. *** ## **5.5 Curriculum Design** ### **5.5.1 Competency-Based Design.** 5.5.1.1 SCF curriculum shall be competency-based. Each learning object shall map to defined competencies, levels, evidence types, practice requirements, review requirements, and boundary rules. 5.5.1.2 Competency-based design shall support modular learning, micro-credentials, WILPs, ILA records, skills wallets, iCRS recognition, National Skills Maps, Foundry pathways, Risk Agency pathways, and lawful handoff context. 5.5.1.3 Competency mapping shall not create equivalence, license, professional certification, employment guarantee, procurement qualification, or public authority approval by default. ### **5.5.2 Outcomes-Based Design.** 5.5.2.1 SCF curriculum shall define clear learning outcomes that state what the learner should know, explain, perform, review, produce, communicate, correct, or escalate within scope. 5.5.2.2 Outcomes shall be written in evidence-bearing and boundary-aware terms. Outcomes shall distinguish awareness, literacy, applied practice, supervised contribution, independent contribution, reviewer capability, maintainer capability, mentor capability, steward capability, systems leadership, national capability contribution, and handoff-context contribution. 5.5.2.3 Outcomes shall avoid vague excellence claims, inflated expertise claims, and authority claims unless separately and lawfully grounded. ### **5.5.3 Work-Integrated Design.** 5.5.3.1 SCF curriculum shall include work-integrated design that connects learning to practice, WILPs, quests, bounties, builds, Studio exercises, field exercises, Campaigns, Reports, Marketplace objects, Registry records, Grid inputs, TRL evidence, National Portfolio objects, and Nexus Universe outputs. 5.5.3.2 Work-integrated design shall include learning agreements, task scopes, supervision rules, mentor roles, host roles, safety controls, fair work protections, data and confidentiality controls, AI and tool-use controls, accessibility, safeguard controls, evidence requirements, grievance channels, correction, and archive. 5.5.3.3 Work-integrated learning shall not become disguised labor, unpaid substitution of regular work, employment by implication, procurement qualification, public authority action, or execution. ### **5.5.4 Risk-Informed Design.** 5.5.4.1 SCF curriculum shall be risk-informed. Learning objects shall identify domain risks, safety risks, data risks, AI risks, cyber risks, privacy risks, public-safe reporting risks, safeguard risks, public authority boundary risks, finance boundary risks, procurement boundary risks, provider validation risks, sponsor control risks, consent overclaim risks, handoff overclaim risks, and execution overclaim risks where applicable. 5.5.4.2 Risk-informed design shall include escalation pathways, stop-the-line triggers, claims freeze rules, data freeze rules, technical freeze rules, correction pathways, withdrawal rules, and archive rules where relevant. 5.5.4.3 Risk-informed curriculum shall not make learners risk authorities, public warning actors, emergency commanders, public authority decision-makers, or operational responders by implication. ### **5.5.5 Sustainability-Integrated Design.** 5.5.5.1 SCF curriculum shall integrate sustainability, climate, nature, biodiversity, water, food, energy, health, infrastructure, circular economy, disaster resilience, just transition, and WFEH-B systems where relevant. 5.5.5.2 Sustainability-integrated design shall avoid greenwashing, resilience-washing, impact overclaim, public authority overclaim, procurement overclaim, and financeability overclaim. 5.5.5.3 Sustainability learning shall not certify environmental claims, approve projects, create procurement preferences, or grant public authority status. ### **5.5.6 AI-Augmented Design.** 5.5.6.1 SCF curriculum may use AI to support drafting, translation, tutoring, assessment support, simulation, feedback, accessibility, summarization, classification, learning analytics, and adaptive learning where permitted by data-use labels, AI-use labels, privacy controls, and human review. 5.5.6.2 AI-Augmented Design shall require human oversight, bias and harm review, learner privacy protection, transparency where appropriate, explainability where appropriate, data minimization, prompt-injection awareness, output review, and correction pathways. 5.5.6.3 SCF shall not use AI to make automated high-stakes credentialing, learner ranking, employment, exclusion, public authority, finance, insurance, procurement, or disciplinary decisions by default. ### **5.5.7 Public-Safe Design.** 5.5.7.1 SCF curriculum shall be public-safe by design where learning objects may become public, shared, reused, displayed, published, or routed into Reports, Marketplace, Registry, Campaigns, Nexus Universe, National Portfolios, or handoff context. 5.5.7.2 Public-safe design shall include no-warning language, no-approval language, no-finance language, no-procurement language, no-certification language, no-consent language, no-execution language, sensitive data controls, protected knowledge controls, geospatial sensitivity review, and correction notices. 5.5.7.3 Public-safe design shall not dilute technical rigor. It shall make outputs usable, bounded, responsible, and non-misleading. ### **5.5.8 Accessibility-by-Design.** 5.5.8.1 SCF curriculum shall be accessibility-by-design. Learning objects shall be designed, where feasible, for disability inclusion, screen-reader compatibility, captions, alt text, plain-language summaries, multilingual access, mobile access, low-bandwidth access, offline access, flexible pacing, and accessible assessment. 5.5.8.2 Accessibility requirements shall apply to learning platforms, documents, videos, simulations, dashboards, Studio exercises, WILPs, assessments, micro-credentials, portfolios, Marketplace displays, Registry records, and Reports where feasible. 5.5.8.3 Accessibility design shall not be treated as optional enhancement; it shall be part of public-good capability formation. ### **5.5.9 Safeguard-by-Design.** 5.5.9.1 SCF curriculum shall be safeguard-by-design. Learning objects shall include community safeguards, Indigenous protocols where applicable, protected knowledge controls, youth safeguards, disability inclusion, humanitarian sensitivity, privacy, non-extractive engagement, trauma-aware design where relevant, and community-facing correction. 5.5.9.2 Safeguard-by-design shall include review before sensitive publication, controlled access where necessary, data minimization, consent and permission rules, public-safe transformation, and withdrawal pathways. 5.5.9.3 Safeguard learning shall not create consent, representation authority, protected knowledge permission, public authority approval, or deployment authorization. ### **5.5.10 Correction-by-Design.** 5.5.10.1 SCF curriculum shall be correction-by-design. Every learning object, pathway, assessment, credential, WILP, portfolio artifact, public display, and learning record shall include mechanisms for correction, addendum, supersession, withdrawal, suspension, revocation where necessary, appeal where applicable, public repair, archive, and non-continuation. 5.5.10.2 Learners shall be taught that correction is part of competence. SCF shall recognize responsible correction as evidence of judgment, integrity, and public-good discipline. 5.5.10.3 Correction-by-design shall prevent outdated, misleading, unsafe, biased, inaccurate, overclaimed, or boundary-violating learning objects from remaining active without review. *** ## **5.6 Learning Pathway Types** ### **5.6.1 Introductory Pathways.** 5.6.1.1 **Introductory Pathways** shall provide entry-level orientation to Nexus, SCF, public-good doctrine, risk literacy, data literacy, AI literacy, cyber hygiene, public-safe reporting, safeguards, learning records, ILA, iCRS, WILPs, Campaigns, Foundry, Marketplace, Registry, Studio, Grid, Nexus Universe, and lawful handoff. 5.6.1.2 Introductory Pathways shall be accessible, modular, multilingual where feasible, low-bandwidth where feasible, and suitable for diverse education levels. 5.6.1.3 Introductory completion shall evidence awareness or basic literacy only. ### **5.6.2 Technical Pathways.** 5.6.2.1 **Technical Pathways** shall prepare learners for technical tasks in data, AI, cyber, privacy, geospatial, software, dashboards, APIs, digital twins, telecom, compute, cloud, edge, HPC, sensors, robotics, DRI, Observatory, Studio, Grid, Reports, and Foundry. 5.6.2.2 Technical Pathways shall include practical evidence, review gates, safety controls, data and AI-use labels, cyber controls, accessibility, public-safe output rules, and correction. 5.6.2.3 Technical Pathways shall not create deployment authorization, system access rights, regulated practice rights, certification, procurement status, or execution. ### **5.6.3 Cross-Domain Pathways.** 5.6.3.1 **Cross-Domain Pathways** shall connect competencies across domains, including WFEH-B, DRR, DRF, DRI, climate, nature, infrastructure, AI, data, cyber, public authority learning, finance-readiness literacy, public-safe reporting, safeguards, and lawful handoff. 5.6.3.2 Cross-Domain Pathways shall develop systems thinking, translation, collaboration, boundary literacy, and portfolio reasoning. 5.6.3.3 Cross-domain competence shall not imply mastery of each component domain or authorization to act in regulated domains. ### **5.6.4 National Portfolio Pathways.** 5.6.4.1 **National Portfolio Pathways** shall prepare learners to contribute to National Context Records, National Systems-Risk Maps, National Skills Maps, National Capability Records, National Challenge Briefs, public authority learning records, Competence Cell workplans, Nexus Universe preparation, and handoff dependency notes. 5.6.4.2 These pathways shall be nationally routed, localized, safeguard-reviewed, public-safe, and correctionable. 5.6.4.3 National Portfolio Pathway completion shall not create national endorsement, public authority approval, country ranking, procurement status, financeability, consent, or execution. ### **5.6.5 Foundry Contributor Pathways.** 5.6.5.1 **Foundry Contributor Pathways** shall prepare learners for quests, bounties, builds, micro-production, software contribution, data contribution, documentation, testing, review, public-safe reporting, Studio workflows, Marketplace objects, Registry records, Grid inputs, TRL notes, and handoff dependency packages. 5.6.5.2 These pathways shall include contribution rules, evidence requirements, review expectations, maintainer pathways, support classes, license and attribution rules, labor boundaries, correction, and archive. 5.6.5.3 Foundry Contributor Pathway completion shall not create employment, bounty award entitlement outside applicable terms, procurement qualification, provider validation, product certification, deployment authorization, or execution. ### **5.6.6 Campaign Contributor Pathways.** 5.6.6.1 **Campaign Contributor Pathways** shall prepare participants for public-good mobilization, volunteer coordination, signature tools, pledge tools, support tools where lawful, team and chapter formation, ambassador roles, campaign dashboards, public-safe storytelling, trust and safety, fraud prevention, data handling, sponsor controls, provider controls, community consent boundaries, and correction channels. 5.6.6.2 Campaign Contributor Pathways shall emphasize mobilization without mandate, support without control, public attention without approval, community participation without consent, and campaign success without execution authority. ### **5.6.7 Data Steward Pathways.** 5.6.7.1 **Data Steward Pathways** shall prepare learners to manage data objects, metadata, lineage, data quality, data-use labels, AI-use labels, rights review, privacy, secure rooms, compute-to-data, public-safe transformation, data availability statements, controlled access, correction, and archive. 5.6.7.2 Data Steward Pathways shall not create data ownership, data access rights, open data permission, public authority record status, or unrestricted publication rights. ### **5.6.8 Public-Safe Reviewer Pathways.** 5.6.8.1 **Public-Safe Reviewer Pathways** shall prepare reviewers to evaluate learning objects, Reports, Campaign materials, Marketplace listings, Registry records, DRI summaries, Observatory outputs, National Portfolio summaries, Nexus Universe outputs, and handoff notes for public-safe language and boundary compliance. 5.6.8.2 These pathways shall include no-warning, no-approval, no-finance, no-procurement, no-certification, no-consent, no-execution, protected knowledge, sensitive data, sensitive geospatial, public repair, and correction rules. 5.6.8.3 Public-Safe Reviewer Pathway completion shall not create reviewer appointment, certification authority, public authority approval, or official communication authority unless separately recorded within scope. ### **5.6.9 Risk Agency Expert Pathways.** 5.6.9.1 **Risk Agency Expert Pathways** shall prepare domain experts, technical experts, community leaders, public authority learning experts, readiness experts, safeguard experts, faculty experts, reviewers, maintainers, and cross-sphere translators for scoped expert routing, advisory support, training, public-safe reporting support, and handoff support. 5.6.9.2 These pathways shall include expert standing records, conflict disclosure, reliance labels, output records, public-safe advisory language, finance and insurance boundary rules, public authority boundary rules, community translation boundaries, and correction. 5.6.9.3 Risk Agency Expert Pathway completion shall not create professional license, certification, public authority approval, investment advice authority, underwriting authority, consent, or execution. ### **5.6.10 Handoff Literacy Pathways.** 5.6.10.1 **Handoff Literacy Pathways** shall prepare participants to understand how evidence, learning, work products, Studio outputs, Grid inputs, TRL notes, Reports, Registry records, Marketplace listings, National Portfolio records, and Nexus Universe outputs may support downstream lawful review without transferring authority. 5.6.10.2 Handoff Literacy Pathways shall cover recipient responsibility, public authority dependencies, legal dependencies, data dependencies, safeguard dependencies, finance and insurance questions, procurement neutrality, provider-neutrality notes, sponsor-boundary notes, correction and recall, and archive. 5.6.10.3 Handoff Literacy Pathway completion shall not authorize handoff, implementation, procurement, investment, insurance, public authority action, community consent, deployment, or execution. *** ## **5.7 Learning Governance** ### **5.7.1 Curriculum Stewardship.** 5.7.1.1 SCF curriculum shall be stewarded through recorded roles, version control, competency mapping, review cycles, public-safe controls, safeguard controls, data and AI-use controls, accessibility review, localization review, credential review, correction, and archive. 5.7.1.2 Curriculum stewards shall maintain alignment with SCF ontology, National Skills Maps, labor-market intelligence, Nexus Academy, Risk Academy, Foundry, Campaigns, Reports, Marketplace, Registry, Studio, Grid, Nexus Universe, National Portfolios, and lawful handoff context. 5.7.1.3 Curriculum stewardship shall not create ownership capture, sponsor control, provider validation, public authority approval, certification authority, or execution authority. ### **5.7.2 Learning Object Review.** 5.7.2.1 Learning objects shall be reviewed for purpose, scope, competency mapping, evidence requirements, assessment design, accessibility, language, data and AI-use, cyber and privacy, public-safe status, safeguards, credential implications, support class, correction pathway, and archive rule. 5.7.2.2 Higher-risk learning objects, including those involving AI, data, cyber, public authority learning, finance-readiness, insurance-readiness, DRR, DRI, public-safe reporting, protected knowledge, youth, health, biosecurity-sensitive topics, or fieldwork, shall require heightened review. 5.7.2.3 Learning object approval within SCF shall not create external certification, public authority approval, professional recognition, procurement status, or deployment authorization. ### **5.7.3 AI-Use Review.** 5.7.3.1 AI-use review shall apply where learning objects use AI for drafting, tutoring, translation, feedback, assessment support, simulation, learner analytics, content recommendation, classification, summarization, or practice. 5.7.3.2 AI-use review shall assess data inputs, learner privacy, bias and harm, explainability, human oversight, prompt-injection risk, model limitations, output review, accessibility impacts, youth safeguards where applicable, and correction pathways. 5.7.3.3 AI-use review shall prohibit automated high-stakes credentialing, learner ranking, employment decisions, exclusion, public authority decisions, finance decisions, insurance decisions, procurement decisions, or disciplinary determinations by default. ### **5.7.4 Data and Privacy Review.** 5.7.4.1 Data and privacy review shall apply to learner records, assessment data, portfolio artifacts, skills-wallet records, WILP records, micro-credential records, public display records, learning analytics, employer or host evidence, mentor records, youth data, sensitive profile data, and cross-border learning data. 5.7.4.2 Data and privacy review shall require data minimization, purpose limitation, consent and permission, access controls, retention rules, deletion or sealing where applicable, display settings, youth protections, sensitive profile controls, and incident response. 5.7.4.3 Learning data shall not be used for social scoring, automated hiring, unauthorized employer scraping, public ranking, discriminatory profiling, or public authority decisioning by default. ### **5.7.5 Public-Safe Review.** 5.7.5.1 Public-safe review shall apply to learning objects, summaries, public-facing courses, Reports, Campaign materials, Marketplace listings, Registry records, Nexus Universe materials, National Portfolio summaries, DRI summaries, Observatory outputs, Studio outputs, and handoff notes. 5.7.5.2 Public-safe review shall identify and correct warning overclaims, approval overclaims, finance overclaims, procurement overclaims, certification overclaims, consent overclaims, execution overclaims, public authority overclaims, provider validation overclaims, sponsor control risks, sensitive data exposure, protected knowledge exposure, and misleading claims. 5.7.5.3 Public-safe review shall preserve accuracy and usefulness while preventing authority by implication. ### **5.7.6 Safeguard Review.** 5.7.6.1 Safeguard review shall apply to learning objects involving communities, Indigenous protocols where applicable, protected knowledge, youth, disability, accessibility, humanitarian contexts, health-sensitive information, biodiversity-sensitive information, sensitive geospatial information, fieldwork, public authority learning, or high-risk technologies. 5.7.6.2 Safeguard review shall assess consent and permission, non-extractive engagement, protected knowledge restrictions, community-facing correction, accessibility, youth protection, privacy, public-safe display, and withdrawal pathways. 5.7.6.3 Safeguard review shall not create consent, representation authority, protected knowledge permission, public authority approval, or implementation authorization. ### **5.7.7 Accessibility Review.** 5.7.7.1 Accessibility review shall apply to learning platforms, documents, videos, assessments, simulations, Studio exercises, dashboards, WILPs, portfolio displays, micro-credentials, Marketplace listings, Registry records, and Reports where feasible. 5.7.7.2 Accessibility review shall consider screen-reader compatibility, captions, transcripts, alt text, plain-language summaries, color and visual design, mobile-first access, low-bandwidth formats, offline options, language access, flexible pacing, and disability inclusion. 5.7.7.3 Accessibility barriers shall be treated as system design issues requiring correction, not learner deficiencies. ### **5.7.8 Translation Review.** 5.7.8.1 Translation review shall apply where learning objects are translated across languages, jurisdictions, cultural contexts, public authority terminology, technical vocabulary, community contexts, or National Portfolios. 5.7.8.2 Translation review shall preserve semantic meaning, public-safe boundary language, legal-boundary language, safeguard requirements, data and AI-use labels, credential limitations, and correction notices. 5.7.8.3 Translation shall not create substantive approval, legal equivalence, public authority adoption, credential equivalence, or new license terms by implication. ### **5.7.9 Credential Review.** 5.7.9.1 Credential review shall apply to micro-credentials, badges, pathway completion records, WILP completion records, skills-wallet records, portfolio displays, and any learning record intended for public or controlled display. 5.7.9.2 Credential review shall verify scope, evidence basis, competency level, review method, issuer identity, expiry or renewal rules, display permissions, privacy controls, public-safe notices, professional license boundaries, employment boundaries, procurement boundaries, public authority boundaries, and correction or withdrawal pathways. 5.7.9.3 Credential review shall prevent credential overclaim, pay-to-credential capture, sponsor-controlled credentialing, provider validation by association, unbounded expertise claims, and misleading public display. ### **5.7.10 Correction and Archive.** 5.7.10.1 SCF learning governance shall include correction and archive for curricula, learning objects, assessments, WILPs, micro-credentials, badges, ILA records, skills-wallet displays, portfolio artifacts, public-facing summaries, Marketplace listings, Registry records, Reports, and Nexus Universe learning outputs. 5.7.10.2 Correction actions may include edit, erratum, addendum, revision, supersession, downgrade, suspension, withdrawal, revocation where necessary, public repair, archive, or non-continuation. 5.7.10.3 Archive records shall identify historical status, version, correction history, successor object where applicable, access class, public-safe status, license or rights status, and not-current notice. 5.7.10.4 Correction and archive shall be treated as trust infrastructure and not as failure by default. Learning systems shall remain credible because they can be corrected. *** ## **5.8 Final Part V Operating Statement** 5.8.1 Learning under SCF shall be the structured capability-formation architecture of Nexus. It shall convert knowledge, practice, evidence, contribution, review, mentorship, public-safe communication, safeguards, and correction into bounded competency records that support learners, workers, communities, public authority learning participants, contributors, National Portfolios, Nexus Foundry, Nexus Campaigns, Nexus Reports, Nexus Marketplace, Nexus Registry, Nexus Studio, Nexus Grid, Nexus Universe, and lawful handoff context. 5.8.2 Nexus Academy shall provide the broad capability engine for foundational, technical, data, AI, public-good software, National Portfolio, Foundry, Marketplace, Registry, Studio, Grid, TRL, Nexus Universe, and lawful handoff learning. Risk Academy shall provide the risk-literacy engine for systems risk, DRR, DRF, DRI, WFEH-B, public-safe reporting, public authority learning, finance-readiness and insurance-readiness literacy, safeguards, crisis-learning, and after-action learning. 5.8.3 Learning objects shall be modular, competency-mapped, evidence-bearing, accessible, localized where required, public-safe where needed, safeguard-reviewed where applicable, AI- and data-controlled where applicable, and correctionable throughout their lifecycle. Courses, modules, units, lessons, labs, scenarios, simulations, Studio exercises, field exercises, review exercises, public-safe reporting exercises, contribution tasks, quests, bounties, builds, capstones, and portfolio artifacts shall each carry scope, evidence, review, limitations, and correction rules. 5.8.4 Curriculum design under SCF shall be competency-based, outcomes-based, work-integrated, risk-informed, sustainability-integrated, AI-augmented where appropriate, public-safe, accessibility-by-design, safeguard-by-design, and correction-by-design. Learning governance shall preserve curriculum stewardship, object review, AI-use review, data and privacy review, public-safe review, safeguard review, accessibility review, translation review, credential review, correction, and archive. 5.8.5 The operating rule of Part V is that learning forms capability, not authority. SCF may make learning visible, portable, useful, evidence-bearing, nationally relevant, and handoff-aware, but it shall not convert learning, course completion, micro-credentials, WILPs, skills-wallet records, portfolio artifacts, Marketplace display, Registry status, Nexus Universe participation, or public authority learning participation into professional license, employment guarantee, public authority approval, procurement qualification, financeability, insurability, 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/v.-learning.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.