# XVIII. ACADEMY

Nexus Agile Framework Academy defines the **NAF learning and capability formation model** for Nexus Academy, Risk Academy, the Integrated Learning Account, work-integrated learning paths, micro-credentials, workforce resilience, and learning governance. This section explains how **learning pathways, contribution records, competence pathways, and bounded credentials** build public-good capability without creating professional licensing, procurement status, or execution authority.

This section sets the operating model for **capability formation**, **learning-to-contribution pathways**, **ILA records**, **WILPs**, **micro-credential architecture**, **Risk Academy curriculum**, and **workforce resilience**. It helps Nexus build national capability, strengthen public-safe reporting, improve data and AI literacy, and prepare lawful handoff context without implying employment, certification, public authority approval, or deployment authorization.

### What this section covers

* **Learning and capability pathways** - Defines Academy, Risk Academy, contribution pathways, competence records, and national capacity formation.
* **Learning records and credentials** - Explains ILA records, WILPs, micro-credentials, portfolio evidence, correction, and archive.
* **Governance and workforce resilience** - Defines curriculum review, mentor controls, AI and privacy controls, inclusion, reskilling, and upskilling.

Use this section with [Nexus Agile Framework (NAF)](/organization/operations/frameworks/nexus-agile-framework-naf.md) for the full framework overview, [XVII. REPORTS](/organization/operations/frameworks/nexus-agile-framework-naf/xvii.-reports.md) for public-safe reporting and knowledge products, [XVI. REGISTRY](/organization/operations/frameworks/nexus-agile-framework-naf/xvi.-registry.md) for learning records and status truth, [XV. GRID](/organization/operations/frameworks/nexus-agile-framework-naf/xv.-grid.md) for readiness and evidence pathways, and [XIV. STUDIO](/organization/operations/frameworks/nexus-agile-framework-naf/xiv.-studio.md) for simulations, exercises, and controlled learning workflows.

## 18.1 Learning as Delivery Infrastructure

### 18.1.1 Academy as Capability Engine.

18.1.1.1 Nexus Academy shall operate within NAF as the capability engine through which Nexus participants, contributors, reviewers, maintainers, National Working Groups, Nexus Competence Cells, public authority learning participants, community participants, youth and student participants, providers, sponsors, hosts, National Nodes, Nexus Consortiums, and lawful handoff recipients may develop the knowledge, judgment, methods, practical competence, public-safe reporting discipline, and boundary literacy required to participate in Nexus delivery.

18.1.1.2 Academy shall treat learning as infrastructure, not as a side activity. It shall support the formation of human capability required for Dockets, Campaigns, Foundry builds, Labs translation, Reports drafting, Marketplace discovery, Registry status truth, Studio workflows, Grid and TRL evidence, DICE data practices, GRIx semantic discipline, DRI interpretation, Observatory work, Nexus Universe preparation, Nexus Rails routing, National Portfolio formation, and lawful handoff context.

18.1.1.3 Academy shall structure learning through courses, modules, units, labs, scenarios, simulations, Studio exercises, public-safe reporting exercises, WILPs, micro-credentials, quests, bounties, builds, peer review, mentor review, portfolio artifacts, contribution records, ILA records, iCRS records, and Registry-linked learning evidence.

18.1.1.4 Academy shall not operate as a university by default, regulator, licensing body, professional certifier, employer, employment agency, immigration pathway authority, procurement qualification body, public authority training authority, deployment authority, or execution vehicle unless a separate lawful status is recorded for a specific context.

### 18.1.2 Risk Academy as Risk Literacy and Public-Safe Reporting Engine.

18.1.2.1 Risk Academy shall operate within NAF as the risk literacy and public-safe reporting engine for systems-risk understanding, all-hazards literacy, WFEH-B literacy, DRR learning, DRF literacy, DRI interpretation, GRIx vocabulary use, Observatory literacy, scenario literacy, public authority learning, finance-readiness boundary literacy, insurance-readiness boundary literacy, public-safe communication, and lawful handoff dependency literacy.

18.1.2.2 Risk Academy shall prepare participants to understand risk without overclaiming authority. It shall teach how to read indicators without converting them into ratings, how to interpret signals without converting them into warnings, how to use dashboards without converting them into decisions, how to understand scenarios without treating them as forecasts, and how to discuss readiness without converting it into financeability, insurability, procurement readiness, certification, deployment authorization, or execution.

18.1.2.3 Risk Academy outputs may include learning modules, public-safe reporting guides, DRI literacy exercises, GRIx vocabulary modules, Observatory signal interpretation exercises, Studio scenario exercises, National Portfolio literacy pathways, public authority learning materials, capital-reader literacy materials, insurance-reader literacy materials, and handoff dependency literacy notes.

18.1.2.4 Risk Academy shall preserve the non-execution posture of NAF. Risk literacy shall support better learning, evidence, review, reporting, participation, readiness, and handoff context, but shall not create public warning authority, emergency command, professional qualification, public authority decision-making authority, finance authority, insurance authority, procurement authority, consent authority, deployment authority, or execution authority.

### 18.1.3 Learning-to-Contribution Pathways.

18.1.3.1 NAF shall establish learning-to-contribution pathways through which participants may move from orientation, literacy, foundational competence, supervised practice, applied practice, peer review, mentor review, and portfolio creation into bounded contribution opportunities.

18.1.3.2 Learning-to-contribution pathways may route learners into Dockets, Campaigns, Foundry quests, bounties, builds, Reports drafting, data stewardship, software contribution, GRIx mapping, DRI interpretation, Observatory work, Studio workflow testing, Grid evidence preparation, TRL evidence notes, National Working Groups, Competence Cells, Nexus Universe preparation, Marketplace support, Registry record support, translation, accessibility, public-safe reporting, correction, and archive work.

18.1.3.3 Each learning-to-contribution pathway shall define prerequisite learning, scope of contribution, permitted tools, data and AI-use restrictions, public-safe restrictions, review requirements, mentor or maintainer oversight, support class, labor boundary, contribution recognition pathway, correction pathway, and archive rule.

18.1.3.4 Learning-to-contribution shall not create employment, compensation entitlement, procurement qualification, certification, professional license, public authority role, sponsor authority, provider validation, consent, deployment authorization, or execution by implication.

### 18.1.4 Contribution-to-Competence Pathways.

18.1.4.1 NAF shall establish contribution-to-competence pathways through which recorded contributions may become evidence of learning, practice, competence, review capability, maintainer capability, steward capability, national capability contribution, or handoff-context contribution.

18.1.4.2 Contribution-to-competence pathways shall rely on records, not claims. Evidence may include completed learning objects, WILP artifacts, quest outputs, bounty outputs, build outputs, reviewed code, reviewed data objects, reviewed Reports, Studio workflow outputs, public-safe summaries, DRI contributions, GRIx mappings, Observatory contributions, Grid inputs, TRL evidence notes, National Portfolio contributions, Nexus Universe outputs, correction actions, peer review, mentor verification, maintainer acceptance, reviewer notes, and Registry status records.

18.1.4.3 Contribution-to-competence pathways shall be bounded by scope, evidence basis, review level, date, version, context, limitations, support status, correction status, and archive status. A contribution record shall not be inflated into general competence beyond what the evidence supports.

18.1.4.4 Contribution-to-competence shall not create professional licensing, employment status, public authority qualification, procurement eligibility, finance authority, insurance authority, deployment authority, operational authority, or execution authority.

### 18.1.5 Competence-to-National-Capacity Pathways.

18.1.5.1 NAF shall establish competence-to-national-capacity pathways through which individual, team, Working Group, Competence Cell, Academy, Risk Academy, Foundry, Labs, Campaign, Risk Agency, DICE, GRIx, DRI, Observatory, Studio, Grid, Reports, Marketplace, Registry, Nexus Universe, and National Node learning records may contribute to National Portfolio memory.

18.1.5.2 National capacity pathways shall help countries identify competence gaps, skills needs, public authority learning needs, WFEH-B capability needs, DRR, DRF, and DRI capability needs, data stewardship needs, AI and cyber capability needs, public-safe reporting needs, Foundry build capacity, Studio operation capacity, Grid review capacity, Registry and Marketplace stewardship capacity, and handoff dependency literacy.

18.1.5.3 National capacity pathways shall be nationally routed and shall preserve national ownership before local delivery. They may inform National Nexus Consortiums, National Councils, National Working Groups, Nexus Competence Cells, National Nodes, Nexus Universe participation, and lawful handoff context.

18.1.5.4 Competence-to-national-capacity records shall not create country rankings, public authority approval, workforce certification, labor-market guarantee, public finance allocation, procurement eligibility, immigration status, employment status, consent, deployment authorization, or execution.

### 18.1.6 National Capacity-to-Handoff Context Pathways.

18.1.6.1 NAF shall establish national capacity-to-handoff context pathways through which recorded competence, learning, review capacity, maintainer capacity, National Portfolio readiness, public authority learning, safeguard learning, data and AI governance literacy, Studio practice, Grid evidence, TRL notes, and Nexus Universe outputs may become relevant context for lawful downstream review.

18.1.6.2 Handoff context may identify available national capability, missing capability, training needs, WILP needs, reviewer needs, maintainer needs, support needs, data stewardship gaps, AI governance gaps, cyber and privacy gaps, public-safe reporting gaps, safeguard gaps, and recipient responsibilities.

18.1.6.3 Handoff context shall transfer competence dependencies, not authority. It may help lawful recipients understand what capability exists and what additional diligence, training, contracting, certification, public authority action, procurement, finance, insurance, consent, or operational readiness may be required outside NAF.

18.1.6.4 National capacity-to-handoff context shall not create employment, contracting, certification, public authority approval, financeability, insurability, procurement readiness, consent, deployment authorization, or execution.

### 18.1.7 Learning Without Certification by Implication.

18.1.7.1 Learning in Nexus Academy, Risk Academy, WILPs, micro-credentials, Studio exercises, Foundry quests, Campaign tasks, Labs pathways, Risk Agency training, DICE training, GRIx training, DRI training, Observatory training, Grid training, Reports training, Marketplace training, Registry training, Nexus Universe preparation, and National Node training shall not create certification by implication.

18.1.7.2 Learning records may document participation, completion, assessment, contribution, review, mentor verification, work product, portfolio artifact, public-safe output, competence pathway progress, or micro-credential eligibility within scope, but shall not become professional license, degree, accreditation, regulated qualification, public authority qualification, procurement qualification, deployment approval, or execution authority unless separately and lawfully recorded by a competent authority.

18.1.7.3 Academy and Risk Academy shall use clear boundary language for learning objects, credentials, badges, WILPs, portfolio displays, public profiles, Marketplace listings, Registry records, and Reports.

18.1.7.4 The default rule shall be evidence before credential claim and records before recognition.

### 18.1.8 Learning as Continuous Delivery of Human Capability.

18.1.8.1 NAF shall treat learning as continuous delivery of human capability across the full Nexus lifecycle, from signal intake to Docket formation, Docket work, evidence assembly, review, release, Registry status, Marketplace discovery, Studio operation, Grid and TRL input, Reports publication, Nexus Universe presentation, National Portfolio continuation, lawful handoff context, correction, archive, and renewal.

18.1.8.2 Learning shall be iterative, modular, recorded, public-safe, accessible, inclusive, correctionable, and connected to real work. It shall support reskilling, upskilling, cross-domain mobility, public-good contribution, national capability formation, public authority learning, and lawful handoff literacy.

18.1.8.3 Continuous capability delivery shall include new learning objects, updated modules, revised pathways, corrected credentials, renewed WILPs, updated public-safe reporting practices, new AI-use controls, updated data and privacy controls, new safeguard materials, refreshed risk intelligence literacy, and archived outdated learning.

18.1.8.4 Learning continuity shall not create permanent credential status, indefinite competence claims, employment guarantees, procurement status, financeability, public authority approval, deployment authorization, or execution.

## 18.2 Integrated Learning Account

### 18.2.1 Learner Profile Records.

18.2.1.1 The Integrated Learning Account shall preserve Learner Profile Records for participants who engage in Nexus Academy, Risk Academy, WILPs, micro-credentials, Foundry work, Campaign work, Labs work, Risk Agency training, Studio exercises, Grid review learning, Reports learning, DICE learning, GRIx learning, DRI learning, Observatory learning, Marketplace learning, Registry learning, Nexus Universe preparation, National Node learning, or lawful handoff literacy.

18.2.1.2 Learner Profile Records may include identity attributes, learner-selected display name, affiliation, jurisdiction, language preferences, accessibility needs, consent and permission records, privacy settings, learning goals, pathway enrollments, public-safe display settings, youth protection status where applicable, safeguard status where applicable, and correction request history.

18.2.1.3 Learner Profile Records shall be governed by data minimization, purpose limitation, learner consent, access control, youth safeguards, sensitive profile controls, cross-border controls where applicable, data sovereignty where applicable, AI-use limits, deletion, sealing, correction, and archive.

18.2.1.4 Learner Profile Records shall not create employment, credential, visa, immigration, public authority, procurement, finance, insurance, deployment, or execution status.

### 18.2.2 Learning Achievement Records.

18.2.2.1 The Integrated Learning Account shall preserve Learning Achievement Records documenting completed courses, modules, units, lessons, labs, scenarios, simulations, Studio exercises, public-safe reporting exercises, Risk Academy modules, WILPs, micro-credentials, assessments, quests, bounties, builds, reviews, mentor-verified tasks, and portfolio artifacts.

18.2.2.2 Learning Achievement Records shall include title, pathway, competency linkage, completion date, evidence basis, assessment basis where applicable, review level, mentor verification where applicable, version, expiry where applicable, renewal status, public display setting, correction pathway, and archive rule.

18.2.2.3 Learning Achievement Records shall distinguish completion from competence, competence from credential, credential from license, and license from authority.

18.2.2.4 Learning Achievement Records shall not create professional qualification, employment status, procurement eligibility, public authority approval, deployment authorization, or execution.

### 18.2.3 Contribution Records.

18.2.3.1 The Integrated Learning Account shall preserve Contribution Records for learning-linked contributions, including data contributions, software contributions, research contributions, review contributions, public-safe reporting contributions, translation contributions, accessibility contributions, Campaign contributions, Foundry contributions, DICE contributions, GRIx contributions, DRI contributions, Observatory contributions, Studio contributions, Grid contributions, TRL evidence contributions, Marketplace contributions, Registry contributions, Nexus Universe contributions, National Portfolio contributions, correction contributions, and archive contributions.

18.2.3.2 Contribution Records shall include contribution type, object linkage, Docket linkage where applicable, role, date, scope, evidence, review status, maintainer acceptance where applicable, iCRS linkage where applicable, public display setting, labor boundary, correction pathway, and archive rule.

18.2.3.3 Contribution Records may support competence evidence, iCRS recognition, portfolio display, Marketplace discovery, Registry record support, and National Portfolio memory within scope.

18.2.3.4 Contribution Records shall not create employment, compensation entitlement, procurement qualification, provider validation, certification, public authority role, deployment authority, or execution.

### 18.2.4 Evidence-of-Learning Records.

18.2.4.1 The Integrated Learning Account shall preserve Evidence-of-Learning Records showing the basis for learning claims, pathway progress, micro-credential eligibility, competence pathway progress, reviewer readiness, maintainer readiness, and contribution recognition.

18.2.4.2 Evidence-of-Learning may include assessment results, work products, code commits, data objects, Reports, public-safe summaries, Studio outputs, dashboards, simulations, scenarios, method notes, GRIx mappings, DRI interpretations, Observatory summaries, Grid notes, TRL evidence, peer review, mentor verification, host verification, public-safe review, correction actions, and archive contributions.

18.2.4.3 Evidence-of-Learning Records shall include scope, date, version, reviewer, evidence class, limitations, expiry or renewal where applicable, correction pathway, and archive rule.

18.2.4.4 Evidence-of-Learning shall support validity by record, but shall not create license, certification, employment, procurement eligibility, public authority approval, consent, deployment authorization, or execution.

### 18.2.5 Competence Pathway Records.

18.2.5.1 The Integrated Learning Account shall preserve Competence Pathway Records documenting learner movement across 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.

18.2.5.2 Competence Pathway Records shall identify competency family, level, evidence requirements, completed learning, completed contributions, review requirements, mentor verification, remaining gaps, renewal needs, correction history, and archive status.

18.2.5.3 Competence Pathway Records shall be bounded by domain, scope, evidence, context, date, review level, and limitations. They shall not generalize beyond the recorded pathway.

18.2.5.4 Competence Pathway Records shall not create professional license, employment guarantee, public authority qualification, procurement eligibility, financeability, deployment authorization, or execution.

### 18.2.6 National Learning Records.

18.2.6.1 The Integrated Learning Account may preserve National Learning Records where learning, contribution, WILP participation, micro-credential participation, public authority learning, Foundry work, Campaign work, Competence Cell work, National Working Group work, Nexus Universe preparation, or National Portfolio activity is relevant to a national context.

18.2.6.2 National Learning Records shall support National Portfolio memory, national skills mapping, National Node continuity, Competence Cell formation, public authority learning, Nexus Universe preparation, and lawful handoff dependency mapping.

18.2.6.3 National Learning Records shall be governed by national routing, data sovereignty, localization, privacy, consent, youth safeguards, community safeguards, Indigenous protocols where applicable, public-safe display, correction, and archive.

18.2.6.4 National Learning Records shall not create country ranking, national certification, public authority approval, employment status, immigration status, procurement eligibility, consent, deployment authorization, or execution.

### 18.2.7 Safeguard Learning Records.

18.2.7.1 The Integrated Learning Account shall preserve Safeguard Learning Records for training and evidence related to community safeguards, Indigenous protocols where applicable, protected knowledge, youth safeguards, disability inclusion, accessibility, humanitarian sensitivity, non-extractive engagement, public-safe reporting, privacy, data protection, AI governance, cyber sensitivity, and community-facing correction.

18.2.7.2 Safeguard Learning Records shall identify training completed, practical exercises, scenario exercises, review status, mentor verification, renewal requirements, limitations, correction history, and archive rule.

18.2.7.3 Safeguard Learning Records may be required before participation in sensitive work, controlled rooms, public-safe review, community-facing work, protected knowledge handling, youth-facing work, secure-room work, data-room work, or public authority learning contexts.

18.2.7.4 Safeguard Learning Records shall not create consent authority, public authority approval, professional license, deployment authorization, or execution.

### 18.2.8 Public Authority Learning Participation Records.

18.2.8.1 The Integrated Learning Account may preserve Public Authority Learning Participation Records for public authority participants, public servants, agency participants, municipal participants, emergency-management participants, public health participants, infrastructure authority participants, regulators, public finance readers, and other public authority-adjacent participants who engage in Nexus learning.

18.2.8.2 Public Authority Learning Participation Records shall identify learning activity, role, public authority boundary notice, no-decision notice, no-warning notice, no-command notice, no-procurement notice, no-public-finance-allocation notice, materials accessed, review status where applicable, correction pathway, and archive rule.

18.2.8.3 Public Authority Learning Participation Records shall not create public authority approval, official adoption, regulation, permit, license, public warning, public finance allocation, procurement decision, emergency command, deployment authorization, or execution.

18.2.8.4 Public authority learning shall remain learning unless a competent public authority separately and lawfully takes action outside NAF.

### 18.2.9 Portability Records.

18.2.9.1 The Integrated Learning Account may preserve Portability Records that allow learners to export, share, display, verify, or transfer bounded learning records, micro-credentials, badges, contribution records, competence pathway records, WILP records, and portfolio artifacts.

18.2.9.2 Portability Records shall include learner permissions, display settings, evidence links, issuer identity where applicable, verification status, expiry where applicable, renewal status, privacy restrictions, public-safe notices, non-equivalence notices, correction history, and archive rule.

18.2.9.3 Portability shall be learner-respecting, privacy-preserving, interoperable where safe, and correctionable. It shall not force public disclosure of sensitive profile information, youth information, protected knowledge, community-sensitive information, or restricted data.

18.2.9.4 Portability Records shall not create legal equivalence, professional license, employment status, immigration status, procurement eligibility, public authority status, deployment authorization, or execution.

### 18.2.10 Correction and Archive Records.

18.2.10.1 The Integrated Learning Account shall preserve Correction and Archive Records for learning achievements, contribution records, evidence-of-learning records, competence pathway records, WILPs, micro-credentials, badges, portfolio artifacts, public display profiles, and National Learning Records.

18.2.10.2 Correction may include metadata correction, evidence correction, review correction, expiry correction, renewal correction, suspension, withdrawal, revocation where necessary, public display removal, privacy correction, data deletion, sealing, archive, or non-continuation.

18.2.10.3 Archive shall preserve historical learning memory without implying current validity, active support, current competence, certification, employment status, procurement eligibility, public authority approval, deployment authorization, or execution.

18.2.10.4 ILA correction shall propagate to iCRS, Registry, Marketplace, Academy records, Risk Academy records, WILP records, micro-credential records, National Portfolio records, Nexus Universe records, and handoff context where applicable.

## 18.3 Work-Integrated Learning Paths

### 18.3.1 WILP Function.

18.3.1.1 Work-Integrated Learning Paths shall function as evidence-bearing learning-through-work pathways that connect Academy learning, Risk Academy learning, Foundry work, Campaign work, Labs work, Risk Agency learning, Studio practice, DICE stewardship, GRIx mapping, DRI interpretation, Observatory work, Grid preparation, Reports drafting, Marketplace support, Registry support, National Portfolio formation, Nexus Universe preparation, and lawful handoff literacy.

18.3.1.2 WILPs shall convert learning into supervised practice and supervised practice into evidence without converting learning work into employment, procurement, certification, deployment, or execution.

18.3.1.3 WILPs may include apprenticeships, internships, cooperative education, clinical or field practicums, Studio-based practice, Foundry-based contribution, Campaign-based mobilization, National Working Group practice, Competence Cell practice, public authority learning placements, Risk Agency shadowing, remote distributed practice, and controlled-room exercises.

18.3.1.4 WILPs shall be governed by learning agreements, workplans, mentor assignment, supervision level, health and safety controls, safeguard controls, data and confidentiality controls, AI and tool-use controls, fair work controls, accessibility controls, correction channels, and archive rules.

### 18.3.2 WILP Scope.

18.3.2.1 Each WILP shall define scope, learning purpose, expected competencies, work objects, evidence requirements, permitted tasks, prohibited tasks, access class, data-use labels, AI-use labels, public-safe requirements, safeguard requirements, host role, mentor role, review requirements, support class, duration, completion criteria, correction pathway, and archive rule.

18.3.2.2 WILP scope shall distinguish observation, learning, supervised practice, contribution, review support, public-safe output, Studio exercise, controlled data work, Foundry work, Campaign work, National Portfolio work, and handoff-literacy work.

18.3.2.3 WILP scope shall not include unsupervised high-risk work, regulated professional work without lawful authority, public authority decisions, public warnings, finance activity, insurance activity, procurement action, community consent action, deployment authorization, operational command, or execution.

18.3.2.4 Any expansion of WILP scope shall require recorded review and correction of the learning agreement, host obligations, mentor obligations, learner protections, data controls, public-safe controls, and boundary notices.

### 18.3.3 WILP Host Roles.

18.3.3.1 WILP hosts may include universities, research bodies, employers, public authority learning hosts, community organizations, labs, Foundry programs, Campaign programs, National Nodes, National Working Groups, Competence Cells, Risk Agency engagements, Studio environments, National Consortium Companies, Project SPVs, and sponsor-supported environments where lawful and boundary-compliant.

18.3.3.2 Host roles shall be limited to providing supervised practice context, work context, mentorship support, evidence opportunity, safe access, feedback, and verification within the WILP scope.

18.3.3.3 Hosts shall protect learners from disguised labor, unpaid substitution of regular labor, unsafe work, harassment, abuse, excessive workload, surveillance misuse, data misuse, AI misuse, protected knowledge misuse, and public authority or execution overclaim.

18.3.3.4 Host participation shall not create employer endorsement, certification authority, procurement authority, public authority approval, provider validation, sponsor control, consent, deployment authorization, or execution.

### 18.3.4 WILP Mentor Roles.

18.3.4.1 WILP mentors shall support learner development, provide guidance, review work, verify evidence where appropriate, identify risks, support correction, ensure boundary compliance, and help learners understand public-good context.

18.3.4.2 Mentor roles may include technical mentor, data mentor, AI mentor, cyber mentor, privacy mentor, public-safe reporting mentor, safeguard mentor, community mentor, public authority learning mentor, Foundry mentor, Campaign mentor, Reports mentor, Studio mentor, Grid mentor, Registry mentor, Marketplace mentor, and handoff literacy mentor.

18.3.4.3 Mentors shall disclose conflicts, respect learner privacy, avoid exploitation, avoid credential overclaim, avoid employment overclaim, avoid public authority overclaim, avoid procurement overclaim, avoid finance overclaim, and avoid execution overclaim.

18.3.4.4 Mentor verification shall be evidence input only. It shall not create certification, professional license, employment status, procurement eligibility, public authority approval, deployment authorization, or execution.

### 18.3.5 WILP Learner Roles.

18.3.5.1 WILP learners shall participate within recorded scope, follow learning agreements, respect confidentiality, follow data-use and AI-use restrictions, follow public-safe reporting rules, follow safeguard rules, disclose conflicts where applicable, complete assigned learning, produce evidence artifacts where required, engage in review, respond to corrections, and respect archive rules.

18.3.5.2 Learners may serve as observers, trainees, supervised contributors, peer reviewers, documentation contributors, data stewards, software contributors, public-safe reporting contributors, Studio participants, Campaign contributors, Foundry contributors, National Portfolio contributors, or handoff-literacy participants within scope.

18.3.5.3 Learner participation shall not imply employment, contracting, public authority role, professional status, procurement eligibility, consent authority, deployment authority, operational authority, or execution.

18.3.5.4 Learners shall retain access to correction, grievance, withdrawal, privacy, accessibility, and safeguard channels.

### 18.3.6 WILP Artifact Records.

18.3.6.1 WILP Artifact Records shall document the work products created, reviewed, revised, corrected, or archived during a WILP, including Reports, data objects, software objects, dashboards, Studio outputs, simulations, scenarios, public-safe summaries, DRI interpretations, GRIx mappings, Observatory notes, Grid notes, TRL evidence notes, Marketplace support objects, Registry support objects, Campaign outputs, Foundry builds, National Portfolio inputs, and handoff-literacy notes.

18.3.6.2 WILP Artifact Records shall include learner role, host role, mentor role, object linkage, evidence status, review status, public-safe status, data-use status, AI-use status, support class, correction pathway, archive rule, and display permissions.

18.3.6.3 Artifact Records may support ILA, iCRS, Registry, Marketplace, Reports, National Portfolio memory, and micro-credential evidence within scope.

18.3.6.4 Artifact Records shall not create deployment authorization, production approval, procurement readiness, financeability, certification, public authority decision, consent, or execution.

### 18.3.7 WILP Public-Safe Outputs.

18.3.7.1 WILP Public-Safe Outputs may include summaries, learning notes, public-safe briefs, dashboards, visualizations, Reports, Campaign materials, Academy materials, Studio summaries, DRI literacy notes, GRIx vocabulary notes, Observatory summaries, and National Portfolio public-safe content.

18.3.7.2 Public-Safe Outputs shall be reviewed for no-warning, no-approval, no-finance, no-procurement, no-certification, no-consent, no-deployment, no-execution, no-rating, protected knowledge, sensitive geospatial, cyber-sensitive, privacy, youth, and safeguard controls.

18.3.7.3 Public-Safe Outputs may be included in Reports, Marketplace, Registry, Academy, Campaigns, Nexus Universe, National Portfolios, or handoff context only within release class and access class.

18.3.7.4 Public-Safe Outputs shall not create public warning, official status, certification, public authority approval, financeability, procurement readiness, consent, deployment authorization, or execution.

### 18.3.8 WILP Labor Boundary.

18.3.8.1 WILPs shall preserve a strict labor boundary. WILP participation shall be learning-first, evidence-bearing, supervised, recorded, and bounded. It shall not be used to disguise employment, replace paid labor, avoid labor law, avoid procurement rules, avoid contracting rules, extract unpaid value, or shift execution responsibility to learners.

18.3.8.2 WILP labor controls shall address scope, hours, workload, supervision, safety, compensation or stipend status where applicable, bounty recognition where applicable, reimbursement where applicable, learner protections, grievance channels, anti-harassment rules, anti-abuse rules, fieldwork safety, youth protections, data surveillance limits, and exit rights.

18.3.8.3 Where WILP work becomes materially equivalent to employment, contracting, professional services, regulated work, or execution, the pathway shall be corrected, suspended, reclassified, contracted, or terminated as appropriate under applicable law and Nexus boundary discipline.

18.3.8.4 WILP completion shall not create hiring commitment, wage guarantee, procurement qualification, professional certification, deployment authorization, or execution.

### 18.3.9 WILP Correction.

18.3.9.1 WILP Correction shall address errors, misclassification, labor boundary issues, unsafe work, data misuse, AI misuse, privacy issues, cyber issues, protected knowledge issues, public-safe issues, safeguard issues, harassment, abuse, mentor conflict, host conflict, evidence error, credential overclaim, employment overclaim, procurement overclaim, public authority overclaim, deployment overclaim, or execution overclaim.

18.3.9.2 WILP Correction may include scope revision, mentor change, host change, learner support, artifact correction, ILA correction, iCRS correction, micro-credential correction, public-safe notice, suspension, withdrawal, archive, grievance process, public repair, or referral to lawful process where required.

18.3.9.3 WILP Correction shall propagate to ILA, iCRS, Registry, Marketplace, Academy records, Reports, National Portfolio records, Nexus Universe records, and handoff context where applicable.

### 18.3.10 WILP Archive.

18.3.10.1 WILP Archive shall preserve WILP agreements, workplans, mentor records, host records, learner records, artifact records, review records, public-safe outputs, correction history, completion status, withdrawal status, non-continuation status, and archive notices.

18.3.10.2 Archived WILPs shall indicate whether the pathway is completed, withdrawn, superseded, suspended, corrected, non-continuing, or preserved for historical reference.

18.3.10.3 WILP Archive shall not create current competence, active credential, employment status, procurement status, public authority approval, deployment authorization, or execution.

## 18.4 Micro-Credential Architecture

### 18.4.1 Micro-Credential Scope.

18.4.1.1 Micro-credentials within NAF shall be bounded evidence records that document specific learning, competence, practice, contribution, review capability, maintainer capability, public-safe reporting capability, safeguard literacy, data stewardship, AI-use literacy, cyber literacy, DRI literacy, GRIx literacy, Observatory literacy, Studio practice, Grid literacy, TRL evidence literacy, Foundry contribution, Campaign contribution, Reports literacy, Marketplace literacy, Registry literacy, National Portfolio literacy, Nexus Universe preparation, or handoff literacy.

18.4.1.2 Each micro-credential shall define scope, competency linkage, learning outcomes, evidence requirements, assessment requirements, review level, expiry where applicable, renewal requirements, public display rules, ILA linkage, iCRS linkage, Registry linkage where applicable, Marketplace listing where applicable, correction pathway, and archive rule.

18.4.1.3 Micro-credential scope shall be narrow enough to prevent overclaim and strong enough to support evidence-based recognition.

18.4.1.4 A micro-credential shall not be represented as a degree, professional license, regulated qualification, employment qualification, public authority qualification, procurement qualification, certification of deployment readiness, financeability, insurability, consent, deployment authorization, or execution authority.

### 18.4.2 Evidence Basis.

18.4.2.1 Micro-credentials shall be issued only on the basis of recorded evidence. Evidence may include learning completion, assessment, work product, WILP artifact, simulation output, Studio output, peer review, mentor verification, host verification, public-good contribution, public-safe output, Foundry output, Reports output, data object, software object, DRI interpretation, GRIx mapping, Observatory contribution, Grid note, TRL evidence note, correction action, or portfolio artifact.

18.4.2.2 Evidence basis shall include evidence type, date, version, scope, reviewer, method, limitations, expiry where applicable, renewal requirement where applicable, correction history, and archive rule.

18.4.2.3 Evidence shall be sufficient for the micro-credential scope and shall not be inflated into unrelated domains, professional licensure, public authority qualification, procurement qualification, deployment authority, or execution.

### 18.4.3 Review Level.

18.4.3.1 Each micro-credential shall identify its review level, including automated completion record where appropriate, human-reviewed completion, peer-reviewed evidence, mentor-verified evidence, host-verified evidence, maintainer-accepted contribution, reviewer-approved evidence, steward-approved evidence, public-safe reviewed evidence, safeguard-reviewed evidence, or controlled-room reviewed evidence.

18.4.3.2 Review level shall be visible in the ILA record and any public display, Marketplace listing, Registry record, Reports reference, or National Portfolio context where applicable.

18.4.3.3 Review level shall not create certification, legal equivalence, public authority approval, procurement eligibility, employment status, deployment authorization, or execution.

### 18.4.4 Expiry.

18.4.4.1 Micro-credentials may include expiry where competence is time-sensitive, technology-sensitive, safety-sensitive, data-sensitive, AI-sensitive, cyber-sensitive, public-safe-sensitive, safeguard-sensitive, or dependent on current standards, protocols, tools, methods, or legal contexts.

18.4.4.2 Expiry records shall include expiry date, basis for expiry, renewal requirement, status after expiry, public display rule, Registry status where applicable, Marketplace status where applicable, correction pathway, and archive rule.

18.4.4.3 Expired micro-credentials shall not be displayed or used as current unless renewed or reinstated within recorded scope.

### 18.4.5 Renewal.

18.4.5.1 Renewal shall require updated learning, updated evidence, refreshed assessment, renewed review, current public-safe literacy, current data and AI-use literacy where applicable, current cyber and privacy literacy where applicable, current safeguard literacy where applicable, and correction history review.

18.4.5.2 Renewal may be required for AI-related credentials, cyber-related credentials, data governance credentials, public-safe reporting credentials, safeguard credentials, Studio credentials, Grid and TRL credentials, DRI credentials, GRIx credentials, Observatory credentials, and handoff-literacy credentials.

18.4.5.3 Renewal shall preserve the correctionability of competence claims. A renewed credential shall identify the new version and shall not silently erase prior versions.

### 18.4.6 Public Display.

18.4.6.1 Micro-credentials may be displayed through ILA, learner portfolio, Marketplace profile, Registry record, Academy record, National Portfolio context, Nexus Universe participation record, or controlled handoff context according to learner permissions, privacy controls, youth safeguards, public-safe controls, and display rules.

18.4.6.2 Public display shall show credential title, scope, evidence basis, review level, issuer or steward, issue date, expiry where applicable, renewal status, correction status, boundary notices, and archive status where applicable.

18.4.6.3 Public display shall not create endorsement, employment status, professional license, public authority approval, procurement qualification, financeability, deployment authorization, or execution.

### 18.4.7 ILA Record Linkage.

18.4.7.1 Each micro-credential shall be linked to the learner’s Integrated Learning Account, including evidence basis, review level, issue date, expiry, renewal, public display setting, correction history, withdrawal status, and archive status.

18.4.7.2 ILA linkage shall preserve learner control, privacy, portability, correction, and archive.

18.4.7.3 ILA linkage shall not create legal equivalence, employment status, public authority status, procurement eligibility, deployment authorization, or execution.

### 18.4.8 iCRS Recognition Linkage.

18.4.8.1 Micro-credentials may be linked to iCRS where contribution recognition supports competence evidence, public-good contribution memory, learner motivation, reviewer recognition, maintainer recognition, mentor recognition, Campaign recognition, Foundry recognition, public-safe reporting recognition, correction recognition, or National Portfolio contribution recognition.

18.4.8.2 iCRS linkage shall identify contribution type, recognition type, evidence basis, review status, credit status where applicable, display rule, correction pathway, and archive rule.

18.4.8.3 iCRS recognition shall not create currency, wage, compensation, equity, token, finance, employment, procurement qualification, professional license, public authority approval, deployment authorization, or execution.

### 18.4.9 No Professional License by Implication.

18.4.9.1 No micro-credential, badge, ILA record, iCRS record, WILP record, learner profile, portfolio display, Marketplace listing, Registry record, Reports reference, National Portfolio record, Nexus Universe showcase, or handoff context note shall be represented as a professional license unless separately and lawfully issued by a competent licensing authority.

18.4.9.2 Micro-credentials may describe bounded learning and evidence. They shall not authorize regulated practice, professional services, public authority functions, emergency functions, finance or insurance activities, procurement authority, deployment, operation, or execution.

18.4.9.3 Any external license, professional certification, statutory credential, degree, or regulated qualification may be referenced only with its source, scope, jurisdiction, expiry, limitations, and authority, and shall not be expanded by Nexus.

### 18.4.10 Correction and Withdrawal.

18.4.10.1 Micro-credentials shall be correctionable and withdrawable. Correction may address evidence errors, assessment errors, review errors, identity errors, scope errors, expiry errors, renewal errors, display errors, AI-use errors, data errors, public-safe errors, safeguard errors, credential overclaim, professional license overclaim, employment overclaim, procurement overclaim, public authority overclaim, deployment overclaim, or execution overclaim.

18.4.10.2 Withdrawal may occur where a micro-credential was issued in error, issued on defective evidence, misused, overclaimed, expired without renewal, superseded, revoked where necessary, or no longer supportable.

18.4.10.3 Correction and withdrawal shall propagate to ILA, iCRS, Registry, Marketplace, Academy records, Reports, National Portfolio records, Nexus Universe records, and handoff context where applicable.

## 18.5 Risk Academy Curriculum in NAF

### 18.5.1 Systems-Risk Literacy.

18.5.1.1 Risk Academy shall provide systems-risk literacy covering complex systems, cascading risk, interdependence, feedback loops, uncertainty, resilience, fragility, exposure, vulnerability, adaptive capacity, critical infrastructure, cyber-physical systems, supply chains, public authority dependencies, and public-good reporting.

18.5.1.2 Systems-risk literacy shall prepare participants to work across Nexus Dockets, National Portfolios, DRI, GRIx, Observatory, Studio, Reports, Grid, TRL, Campaigns, Foundry, and Nexus Universe.

18.5.1.3 Systems-risk literacy shall not create risk rating authority, public warning authority, public authority decision authority, finance authority, insurance authority, procurement authority, deployment authority, or execution.

### 18.5.2 DRR Learning.

18.5.2.1 DRR Learning shall cover disaster risk reduction concepts, hazard, exposure, vulnerability, preparedness, resilience capacity, prevention, mitigation, response learning, recovery learning, early-warning boundary literacy, community resilience, public-safe communication, National Portfolio relevance, and lawful handoff dependencies.

18.5.2.2 DRR Learning shall support all-hazards literacy and whole-of-society preparedness without substituting for competent public authority emergency management.

18.5.2.3 DRR Learning shall not create public warning authority, emergency command, public authority decision, public finance allocation, deployment authorization, or execution.

### 18.5.3 DRF Literacy.

18.5.3.1 DRF Literacy shall cover disaster risk finance concepts, protection gaps, risk layering, contingent finance concepts, public finance relevance, donor-readiness questions, insurance-readiness questions, capital-readability, assumptions, dependencies, diligence gaps, no-reliance discipline, and regulated-perimeter boundaries.

18.5.3.2 DRF Literacy shall prepare participants to understand finance-readiness language without providing investment advice, financial advice, insurance advice, underwriting, public finance allocation, donor commitment, or transaction activity.

18.5.3.3 DRF Literacy shall not create financeability, bankability, insurability, investment recommendation, underwriting view, donor commitment, public finance allocation, procurement status, or execution.

### 18.5.4 DRI Learning.

18.5.4.1 DRI Learning shall cover disaster risk intelligence structures, indicator records, signal records, confidence labels, uncertainty labels, public-safe intelligence summaries, hotspot records, multi-hazard records, cascade records, dashboard interpretation, correction records, and archive records.

18.5.4.2 DRI Learning shall teach participants to interpret intelligence without converting it into public warning, emergency command, rating, insurance score, investment signal, public authority decision, or operational instruction.

18.5.4.3 DRI Learning shall be linked to GRIx, Observatory, Studio, Reports, Grid, National Portfolios, Nexus Universe, and public-safe reporting.

### 18.5.5 WFEH-B Learning.

18.5.5.1 WFEH-B Learning shall cover water, food, energy, health, biodiversity, nature, cross-system cascades, climate and nature dependencies, infrastructure linkages, supply-chain dependencies, public health linkages, community impacts, protected knowledge issues, sensitive geospatial issues, and lawful handoff dependencies.

18.5.5.2 WFEH-B Learning shall support systems understanding and National Portfolio formation without creating environmental certification, public health decision, public warning, procurement preference, financeability, consent, deployment authorization, or execution.

18.5.5.3 WFEH-B Learning shall include public-safe reporting, community safeguards, Indigenous protocols where applicable, and correctionability.

### 18.5.6 Frontier STEM Risk Learning.

18.5.6.1 Frontier STEM Risk Learning shall cover AI, agentic systems, AI-RAN, O-RAN, telecom, private wireless, edge, HPC, sovereign compute, cloud, cybersecurity, geospatial systems, Earth observation, digital twins, drones, robotics, sensors, IoT, OT, IIoT, DLT, DePIN, Web3, quantum-relevant security, semiconductors, advanced manufacturing, biosecurity-sensitive systems, and frontier science infrastructure.

18.5.6.2 Frontier STEM Risk Learning shall teach participants to understand technical opportunity, risk, uncertainty, dual-use sensitivity, data and AI controls, cybersecurity controls, privacy controls, public-safe communication, standards-aware interfaces, and lawful handoff boundaries.

18.5.6.3 Frontier STEM Risk Learning shall not create technical certification, AI safety certification, security certification, standards conformance, procurement readiness, deployment authorization, or execution.

### 18.5.7 Data, AI, Cyber, and Privacy Learning.

18.5.7.1 Data, AI, Cyber, and Privacy Learning shall cover data classes, metadata, lineage, data-use labels, AI-use labels, rights review, data minimization, purpose limitation, consent and permission, cross-border controls, data sovereignty, secure rooms, compute-to-data, model cards, system cards, benchmark cards, agent workflow controls, prompt-injection controls, cyber hygiene, zero-trust principles, SBOM literacy, vulnerability pathways, privacy incident response, and public-safe output review.

18.5.7.2 This learning shall be required or recommended for participants working with DICE, AI objects, Studio workflows, secure rooms, data rooms, Observatory objects, DRI dashboards, Reports, Foundry builds, Grid inputs, TRL notes, Marketplace listings, Registry records, National Portfolios, and handoff context.

18.5.7.3 Data, AI, Cyber, and Privacy Learning shall not create data rights, AI safety certification, cybersecurity certification, legal compliance determination, public authority approval, procurement readiness, deployment authorization, or execution.

### 18.5.8 Public Authority Learning.

18.5.8.1 Public Authority Learning shall support public authorities and public authority-adjacent actors in understanding Nexus evidence, Reports, DRI, GRIx, Observatory, Studio, Grid, TRL, National Portfolios, Nexus Universe outputs, finance-readiness questions, procurement boundary issues, public-safe communication, and lawful handoff dependencies.

18.5.8.2 Public Authority Learning shall be designed for learning, not substitution. It may support public-good understanding, capacity building, scenario review, readiness questions, and policy learning, but it shall not become official public authority action.

18.5.8.3 Public Authority Learning shall include no-decision, no-warning, no-command, no-regulatory-action, no-procurement, no-public-finance-allocation, no-permit, no-license, no-approval, and no-execution notices.

### 18.5.9 Public-Safe Reporting Learning.

18.5.9.1 Public-Safe Reporting Learning shall teach participants how to communicate evidence, risk, readiness, uncertainty, limitations, public-safe summaries, corrections, archive status, and handoff context without unsafe disclosure or overclaim.

18.5.9.2 Public-Safe Reporting Learning shall cover no-warning language, no-approval language, no-finance language, no-procurement language, no-certification language, no-consent language, no-deployment language, no-execution language, protected knowledge controls, sensitive geospatial controls, cyber-sensitive controls, biosecurity-sensitive controls, public repair, and correction notices.

18.5.9.3 Public-Safe Reporting Learning shall be required or recommended for Reports authors, Campaign leads, Marketplace stewards, Registry stewards, Studio facilitators, DRI contributors, Observatory contributors, National Portfolio contributors, Nexus Universe presenters, and handoff context contributors.

### 18.5.10 Handoff Dependency Literacy.

18.5.10.1 Handoff Dependency Literacy shall teach participants how lawful handoff context is formed, recorded, routed, limited, corrected, recalled, and archived.

18.5.10.2 Handoff Dependency Literacy shall cover evidence context, data context, method context, Studio context, Grid context, TRL context, public-safe status, safeguard status, public authority dependencies, legal dependencies, finance and insurance questions, procurement boundaries, provider-neutrality notes, sponsor-boundary notes, recipient responsibilities, correction pathways, recall pathways, and archive linkage.

18.5.10.3 Handoff Dependency Literacy shall emphasize that handoff transfers dependencies, not authority, and that lawful recipients remain responsible for independent diligence, authorization, procurement, finance, insurance, consent processes, deployment decisions, operations, and execution outside NAF.

## 18.6 Workforce Resilience

### 18.6.1 Reskilling.

18.6.1.1 Academy shall support reskilling for participants, workers, learners, contributors, public servants, community actors, youth, career changers, displaced workers, informal workers, and sector professionals whose roles are affected by exponential technologies, climate risk, disaster risk, digital transformation, infrastructure transition, AI-enabled work redesign, and public-good capability needs.

18.6.1.2 Reskilling pathways may include foundational digital literacy, data literacy, AI literacy, cyber literacy, privacy literacy, WFEH-B literacy, DRR literacy, DRF literacy, DRI literacy, GRIx literacy, public-safe reporting, Studio practice, Foundry contribution, Campaign participation, Reports drafting, Registry and Marketplace stewardship, and handoff literacy.

18.6.1.3 Reskilling shall support transition and capability formation without promising employment, wage increase, hiring, procurement eligibility, certification, immigration status, public authority approval, deployment authorization, or execution.

### 18.6.2 Upskilling.

18.6.2.1 Academy shall support upskilling for participants who need deeper capability in Nexus domains, including advanced data stewardship, AI governance, cyber resilience, geospatial analysis, digital twins, Observatory methods, DRI interpretation, GRIx ontology, public-safe reporting, secure-room work, compute-to-data workflows, Foundry production, Studio operation, Grid review, TRL evidence preparation, National Portfolio formation, Nexus Universe preparation, and lawful handoff context.

18.6.2.2 Upskilling shall be modular, evidence-bearing, reviewable, portable where safe, and correctionable.

18.6.2.3 Upskilling records shall not create professional license, promotion entitlement, employment status, procurement eligibility, financeability, public authority approval, deployment authorization, or execution.

### 18.6.3 Cross-Domain Mobility.

18.6.3.1 Academy shall support cross-domain mobility by helping participants move across risk, resilience, technology, data, policy, public authority learning, public-safe reporting, finance-readiness literacy, community safeguards, and implementation-context literacy.

18.6.3.2 Cross-domain mobility pathways may connect water specialists to data literacy, engineers to public-safe reporting, public servants to DRI literacy, software contributors to safeguard literacy, community participants to Campaign and Reports pathways, students to Foundry builds, and technical contributors to handoff dependency literacy.

18.6.3.3 Cross-domain mobility records shall identify bridge competencies, evidence gaps, completed learning, remaining learning, supervised practice needs, correction history, and archive status.

18.6.3.4 Cross-domain mobility shall not guarantee job mobility, employment, wage changes, professional equivalence, certification, procurement eligibility, or public authority status.

### 18.6.4 National Capability Mapping.

18.6.4.1 Academy shall support National Capability Mapping by aggregating appropriate learning, contribution, WILP, micro-credential, Competence Cell, National Working Group, Nexus Universe, and National Portfolio records to identify national strengths, gaps, needs, and learning priorities.

18.6.4.2 National Capability Mapping may support National Nodes, National Nexus Consortiums, National Councils, National Working Groups, Competence Cells, Academy planning, Risk Academy planning, Foundry planning, Campaign planning, public authority learning, and lawful handoff dependency mapping.

18.6.4.3 National Capability Mapping shall use privacy-preserving, public-safe, non-ranking, non-social-scoring, safeguard-aware, and correctionable methods.

18.6.4.4 National Capability Mapping shall not create country ranking, individual ranking, public authority approval, workforce certification, employment guarantee, procurement eligibility, financeability, consent, deployment authorization, or execution.

### 18.6.5 Workforce Gap Records.

18.6.5.1 Workforce Gap Records shall document identified gaps in skills, roles, competencies, learning pathways, mentors, reviewers, maintainers, data stewards, AI reviewers, cyber reviewers, privacy reviewers, public-safe reviewers, safeguard reviewers, Foundry contributors, Studio operators, Grid reviewers, Reports authors, Registry stewards, Marketplace stewards, National Portfolio contributors, and handoff literacy.

18.6.5.2 Workforce Gap Records may be generated from National Portfolios, Academy data, ILA aggregates, WILP participation, Campaign demand signals, Foundry backlog needs, Risk Agency demand, DRI needs, Observatory needs, Studio needs, Grid needs, Marketplace needs, Registry needs, Nexus Universe outputs, and lawful handoff dependencies.

18.6.5.3 Workforce Gap Records shall guide learning design, not rank individuals or countries.

18.6.5.4 Workforce Gap Records shall not create employment guarantee, wage promise, public authority decision, procurement qualification, financeability, deployment authorization, or execution.

### 18.6.6 Academy-to-Foundry Routing.

18.6.6.1 Academy-to-Foundry Routing shall move prepared learners and contributors into Foundry programs, tracks, quests, bounties, builds, micro-production tasks, review gates, maintainer pathways, and release preparation where learning evidence supports participation.

18.6.6.2 Routing shall be governed by prerequisite learning, learner consent, mentor review, competence pathway record, data and AI-use restrictions, public-safe status, safeguard status, labor boundary, support class, contribution recognition pathway, and correction pathway.

18.6.6.3 Academy-to-Foundry Routing shall not create employment, procurement qualification, product certification, provider validation, deployment authorization, financeability, or execution.

### 18.6.7 Academy-to-Risk-Agency Routing.

18.6.7.1 Academy-to-Risk-Agency Routing shall move prepared participants into expert development, supervised advisory learning, scenario learning, public-safe reporting support, dashboard literacy support, public authority learning support, training support, and handoff support contexts where appropriate.

18.6.7.2 Routing shall distinguish learner, trainee, supervised contributor, expert, reviewer, mentor, and advisor roles.

18.6.7.3 Academy-to-Risk-Agency Routing shall not create professional license, expert certification, advisory reliance beyond stated scope, investment advice, underwriting authority, public authority decision, procurement status, deployment authorization, or execution.

### 18.6.8 Academy-to-National-Node Routing.

18.6.8.1 Academy-to-National-Node Routing shall support national localization of learning, National Portfolio capability formation, National Working Group readiness, Competence Cell formation, Nexus Universe preparation, public authority learning, public-safe reporting, and lawful handoff literacy.

18.6.8.2 Routing shall preserve national ownership, national data sovereignty where applicable, language access, accessibility, community safeguards, Indigenous protocols where applicable, protected knowledge controls, and national correction pathways.

18.6.8.3 Academy-to-National-Node Routing shall not create national certification, public authority approval, employment status, procurement eligibility, public finance allocation, consent, deployment authorization, or execution.

### 18.6.9 Workforce Analytics Boundary.

18.6.9.1 Workforce analytics within Academy shall be used for learning, equity, access, system health, capability planning, gap analysis, pathway improvement, and correction, not for social scoring, individual ranking, automated hiring, public authority determinations, procurement eligibility, finance decisions, insurance decisions, immigration decisions, or deployment authorization.

18.6.9.2 Workforce analytics shall be privacy-preserving, purpose-limited, access-controlled, bias-reviewed, human-reviewed, public-safe, and correctionable.

18.6.9.3 Analytics outputs shall not be used as employment decisions, wage determinations, professional licensing decisions, public authority decisions, procurement decisions, finance decisions, insurance decisions, or execution decisions by default.

### 18.6.10 No Employment or Procurement Status by Implication.

18.6.10.1 No Academy pathway, Risk Academy pathway, ILA record, WILP, micro-credential, badge, portfolio display, iCRS recognition, contribution record, learner profile, Marketplace listing, Registry record, Reports reference, National Portfolio record, Nexus Universe showcase, Risk Agency routing, Foundry routing, or National Node routing shall create employment or procurement status by implication.

18.6.10.2 Employers, hosts, public authorities, procurement bodies, National Consortium Companies, Project SPVs, providers, funders, insurers, and lawful handoff recipients shall conduct their own lawful processes outside Academy and outside NAF.

18.6.10.3 Academy records may inform learning and competence context only within recorded scope and shall not substitute for hiring, contracting, procurement, licensing, public authority, finance, insurance, consent, deployment, or execution decisions.

## 18.7 Learning Governance

### 18.7.1 Curriculum Review.

18.7.1.1 Curriculum Review shall ensure Academy and Risk Academy learning objects are accurate, current, evidence-bearing, public-safe, accessible, inclusive, standards-aware where applicable, scope-bounded, safeguard-aware, AI-use controlled, data-use controlled, correctionable, and aligned with NAF doctrine.

18.7.1.2 Curriculum Review shall assess learning outcomes, competency mapping, evidence requirements, assessment design, public-safe language, data and AI-use limits, cyber and privacy controls, safeguard controls, accessibility, localization, versioning, expiry where applicable, renewal where applicable, correction pathway, and archive rule.

18.7.1.3 Curriculum Review shall not create certification, accreditation, public authority approval, procurement qualification, employment status, deployment authorization, or execution.

### 18.7.2 Faculty and Mentor Controls.

18.7.2.1 Faculty and Mentor Controls shall govern instructors, mentors, coaches, reviewers, maintainers, public-safe reviewers, safeguard reviewers, technical mentors, data mentors, AI mentors, cyber mentors, privacy mentors, community mentors, public authority learning mentors, and handoff literacy mentors.

18.7.2.2 Controls shall include role definition, competence evidence, conflict disclosure, conduct rules, youth safeguards, privacy obligations, anti-harassment obligations, anti-exploitation obligations, public-safe obligations, data and AI-use obligations, protected knowledge obligations, correction obligations, and archive rules.

18.7.2.3 Faculty or mentor standing shall not create professional license, public authority role, certification authority, procurement authority, employment guarantee, deployment authority, or execution authority.

### 18.7.3 Assessment Controls.

18.7.3.1 Assessment Controls shall govern quizzes, assignments, labs, simulations, Studio exercises, public-safe reporting exercises, WILP artifacts, quests, bounties, builds, portfolio artifacts, peer review, mentor verification, host verification, maintainer acceptance, reviewer acceptance, and micro-credential evidence.

18.7.3.2 Assessment shall be fair, evidence-based, accessible, bias-aware, human-reviewable, privacy-preserving, secure, correctionable, and bounded by scope.

18.7.3.3 AI-assisted assessment shall require human review where material to credentialing, public display, competence pathway records, WILP completion, or handoff context.

18.7.3.4 Assessment shall not create professional license, employment status, procurement eligibility, public authority approval, deployment authorization, or execution.

### 18.7.4 Sponsor and Provider Controls.

18.7.4.1 Sponsor and Provider Controls shall prevent sponsor control, provider capture, curriculum capture, pay-to-influence, pay-to-routing, pay-to-credential, pay-to-validation, pay-to-procurement, hidden endorsement, hidden exclusivity, and public-good enclosure.

18.7.4.2 Sponsors and providers may support learning, provide tools, provide technical materials, provide experts, provide infrastructure, host WILPs, support translations, support accessibility, support events, or support Nexus Universe learning where recorded and boundary-compliant.

18.7.4.3 Sponsor or provider involvement shall be disclosed where material and shall not create sponsor control, provider validation, procurement preference, certification, endorsement, financeability, deployment authorization, or execution.

### 18.7.5 AI Learning Controls.

18.7.5.1 AI Learning Controls shall govern AI use in curriculum design, learner support, tutoring, translation, assessment support, summarization, feedback, coding assistance, scenario generation, Studio exercises, and portfolio support.

18.7.5.2 AI Learning Controls shall include AI-use labels, human review, data-use compatibility, learner privacy, youth protections, bias and harm review, prompt-injection controls, tool-permission limits, output review, accessibility review, public-safe review, incident response, correction, and archive.

18.7.5.3 AI shall not make automated high-stakes learning, credentialing, employment, procurement, public authority, finance, insurance, consent, deployment, or execution decisions by default.

### 18.7.6 Data and Privacy Controls.

18.7.6.1 Data and Privacy Controls shall govern learner data, profile data, assessment data, WILP data, credential data, portfolio data, contribution data, mentor records, host records, youth data, accessibility data, sensitive profile data, public display data, and National Learning Records.

18.7.6.2 Controls shall include data minimization, purpose limitation, consent and permission, access control, role-based permissions, encryption where appropriate, cross-border controls, data sovereignty where applicable, deletion, sealing, retention, archive, incident response, learner correction, and withdrawal.

18.7.6.3 Data and Privacy Controls shall prevent learner surveillance, unauthorized profiling, social scoring, employer scraping without permission, public authority overclaim, AI misuse, and public display overreach.

### 18.7.7 Safeguard Controls.

18.7.7.1 Safeguard Controls shall apply to community-facing learning, Indigenous protocol-sensitive learning where applicable, protected knowledge, youth learning, disability inclusion, accessibility, humanitarian-sensitive learning, fieldwork, WILPs, Campaigns, public authority learning, data-room work, secure-room work, Studio exercises, and public-safe reporting.

18.7.7.2 Safeguard Controls shall include informed participation, non-extractive engagement, protected knowledge handling, youth protections, accessibility, language access, fieldwork safety, community-facing correction, cultural sensitivity, trauma-informed practice where appropriate, and escalation pathways.

18.7.7.3 Safeguard participation shall not create consent, public authority approval, certification, deployment authorization, or execution.

### 18.7.8 Accessibility and Inclusion.

18.7.8.1 Academy shall be designed for accessibility and inclusion, including plain-language materials where appropriate, multilingual support where feasible, captions, transcripts, screen-reader compatibility, low-bandwidth formats, mobile access, offline packages where appropriate, accessible assessments, inclusive scheduling, disability accommodations, youth safeguards, gender inclusion, rural and remote access, and conflict-affected or disaster-affected access where applicable.

18.7.8.2 Accessibility and inclusion records shall support quality, public-good legitimacy, learning equity, National Portfolio capability formation, and correction.

18.7.8.3 Accessibility format shall not create a new license, alter evidence status, create certification, or create public authority approval by implication.

### 18.7.9 Correction and Renewal.

18.7.9.1 Academy learning objects, Risk Academy learning objects, ILA records, WILPs, micro-credentials, badges, assessments, portfolios, public displays, Marketplace listings, Registry records, Reports, and National Learning Records shall be correctionable and renewable.

18.7.9.2 Correction and Renewal may be triggered by outdated content, new evidence, changed standards, changed protocols, changed technology, AI drift, data issue, privacy issue, cyber issue, public-safe issue, safeguard issue, accessibility issue, translation issue, assessment issue, credential issue, WILP issue, labor boundary issue, sponsor or provider boundary issue, public authority overclaim, finance overclaim, procurement overclaim, certification overclaim, consent overclaim, deployment overclaim, or execution overclaim.

18.7.9.3 Renewal shall preserve version history and shall not silently erase prior learning, prior credentials, prior corrections, or prior archive records.

### 18.7.10 Archive.

18.7.10.1 Academy Archive shall preserve historical learning objects, pathway versions, retired curricula, expired micro-credentials, superseded WILPs, withdrawn learning materials, corrected assessments, archived learner records, archived contribution records, non-continuing pathways, and public-safe archive notices.

18.7.10.2 Archive records shall include archive date, reason, access class, sensitivity class, public-safe status, successor link where applicable, correction history, support status, license or use status, retention rule, deletion or sealing rule where applicable, and archive-not-current notice.

18.7.10.3 Archive shall preserve institutional memory without implying current validity, current competence, current credential status, current support, certification, employment status, procurement status, public authority approval, deployment authorization, or execution.

18.7.10.4 The final Academy rule of Part XVIII is that NAF may teach, train, credential in bounded form, record learning, recognize contribution, support WILPs, form capability, strengthen national capacity, prepare Nexus Universe participation, and create lawful handoff literacy only through evidence-bearing, learner-protective, public-safe, safeguard-aware, privacy-preserving, correctionable, archive-capable, non-certifying, non-employment, non-procurement, non-financial, non-public-authority, non-consent, non-deployment, and non-executing learning governance. No Academy pathway, Risk Academy module, ILA record, WILP, micro-credential, badge, portfolio display, iCRS record, learner profile, workforce analytics output, public authority learning record, Marketplace listing, Registry record, Reports reference, National Portfolio record, Nexus Universe showcase, Foundry routing, Risk Agency routing, National Node routing, or handoff literacy note shall become professional license, regulated qualification, employment status, wage guarantee, visa or immigration status, procurement eligibility, financeability, insurability, public authority approval, public warning, community consent, Indigenous consent where applicable, deployment authorization, operational command, agency, warranty, 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/nexus-agile-framework-naf/xviii.-academy.md?ask=<question>
```

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

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