# Integrated Learning Account (ILA) #### Summary The Integrated Learning Account (ILA) is the learner record layer of Nexus. It captures learning, contribution, evidence, and pathway progress in one governed account. It supports lifelong learning, micro-credentials, work-integrated learning, and workforce development without implying certification, employment status, or execution authority. **Related topics** * [Nexus Academy](/organization/organization/architecture/ii.-definitions/xxiii.-nexus-academy.md) * [Integrated Credits Rewards System (iCRS)](/organization/operations/mechanisms/integrated-credits-rewards-system-icrs.md) * [Work-Integrated Learning Paths (WILPs)](/organization/operations/mechanisms/work-integrated-learning-paths-wilps.md) ### 1. Mechanism Identity, Purpose, and System Function **1.1 Integrated Learning Account Defined.** The **Integrated Learning Account (ILA)** shall be a governed Nexus Ecosystem mechanism for recording, structuring, verifying, classifying, routing, supporting, correcting, renewing, and archiving digital learning records, learning progress, contribution evidence, competence formation, skills tracking, micro-credentials, work-integrated learning, experiential learning, formal education, professional development, lifelong learning, Nexus Academy participation, Foundry participation, Nexus Universe participation, National Working Group participation, Competence Cell participation, Studio participation, public authority learning participation, and lawful workforce-transition pathways. **1.2 Nexus Upgrade.** The ILA shall not be a generic lifelong-learning wallet. It shall be a **record-bearing, privacy-aware, learner-controlled, nationally localizable, public-good competence-formation mechanism** within Nexus. It shall translate learning into structured records that can support Nexus Academy, Nexus Foundry, Nexus Universe, Nexus Network, Nexus Observatory, Nexus Rails, Nexus Grid, Nexus Marketplace, Nexus Registry, Nexus Studio, National Nodes, National Nexus Consortiums, National Working Groups, Nexus Competence Cells, universities, training providers, employers, public authorities, and lawful downstream actors without creating certification, employment entitlement, public authority approval, procurement status, financeability, deployment authorization, or execution authority by implication. **1.3 Problem.** The ILA responds to the structural gap identified in the initial draft: conventional education and workforce systems often fail to keep pace with technological, industrial, and societal change, leaving learners, institutions, employers, and public-good systems without a durable mechanism for continuous capability formation, practical contribution recognition, and adaptive skills renewal. **1.4 Solution.** The ILA upgrades the initial credit-based concept into a Nexus mechanism that recognizes diverse learning experiences, including formal education, professional certifications, micro-credentials, experiential learning, work-integrated participation, and contribution records, while imposing verification, scope, expiry, privacy, correction, support-class, and no-conversion controls. **1.5 Institutional Character.** The ILA shall be a **learning record and capability-routing mechanism**, not a school, university, accreditor, professional regulator, certification body, employer, labor-market ranking system, social-credit system, immigration pathway, procurement qualification system, public authority approval system, or execution platform. **1.6 System Purpose.** The ILA shall allow learners to build portable, structured, privacy-controlled, evidence-linked digital learning records while allowing Nexus institutions to understand capability formation, identify skills gaps, route learners to appropriate learning and workforce-development pathways, support national capacity development, and preserve the public-good integrity of learning outputs. **1.7 Public-Good Purpose.** The ILA shall support the formation of a skilled, adaptable, resilient, ethically grounded, technically capable, and public-good-oriented workforce able to participate in systems-risk reduction, resilience building, technological transformation, public authority learning, community-sensitive work, and lawful implementation support without collapsing education into certification, readiness into finance, participation into consent, or learning into execution. *** ### 2. Nexus System Placement **2.1 Placement Within Nexus Ecosystem.** The ILA shall form part of the human-capability, competence-formation, learning-record, and workforce-readiness layer of the Nexus Ecosystem. It shall connect individuals, universities, colleges, training providers, public-good institutions, National Nodes, National Nexus Consortiums, National Working Groups, Nexus Competence Cells, Nexus Academy, Nexus Foundry, Nexus Universe, Nexus Network, public authority learning pathways, enterprise-interface pathways, and lawful handoff environments. **2.2 Relationship to Nexus Network.** Nexus Network shall serve as the permanent record rail for authorized ILA records, including Learning Achievement Records, Contribution Records, Competence Pathway Records, Academy Records, Quest Records, Bounty Records, Build Records, Studio Participation Records, National Node Learning Records, Competence Cell Records, Public Authority Learning Participation Records, Support Records, Correction Records, Renewal Records, and Archive Records. Network persistence shall preserve learning memory without creating certification or current authority. **2.3 Relationship to Nexus Academy.** Nexus Academy shall provide the structured learning architecture for the ILA, including learning objectives, pathways, curricula, modules, quests, bounties, work-integrated learning tracks, onboarding pathways, reviewer training, maintainer training, public-safe communication training, safeguard training, technical tracks, and domain learning tracks. Academy completion may create an ILA record, but not a professional license, public authority approval, procurement qualification, or employment entitlement by implication. **2.4 Relationship to Nexus Foundry.** Nexus Foundry shall provide practical production contexts for ILA-aligned learning. Learners may contribute to documentation, evidence capture, test records, schemas, connectors, dashboards, AI workflow controls, public-safe reports, safeguard materials, readiness products, Marketplace metadata, Registry status records, Studio runtime preparation, TRL evidence support, Grid input support, teardown, archive, and correction. Foundry participation shall be recordable learning and contribution, not execution authority. **2.5 Relationship to Nexus Universe.** Nexus Universe shall provide annual-cycle learning contexts, including arena preparation, Nexus Core Build participation, public authority learning rooms, readiness rooms, capital-reader rooms, insurance-reader rooms, donor-reader rooms, public finance learning rooms, Studio demonstrations, Marketplace discovery, Registry interpretation, Grid preparation, TRL review support, public-safe reporting, after-action review, and next-cycle formation. ILA records may capture participation and contribution, but Arena visibility shall not become qualification or authority. **2.6 Relationship to Nexus Core Build.** Nexus Core Build shall provide high-intensity technical learning environments where ILA participants may contribute to network, compute, cloud, data room, secure room, AI, dashboard, Observatory, Studio, public-safe reporting, support, teardown, and archive work under supervision and record controls. Core Build participation shall be treated as controlled work-integrated learning unless separately governed by another competent legal arrangement. **2.7 Relationship to Nexus Observatory.** Nexus Observatory shall inform ILA pathway design by identifying emerging skills, domain signals, capability gaps, workforce needs, public authority learning needs, national technical needs, and system-risk learning priorities. Observatory-derived learning recommendations shall be advisory, public-safe, and non-commanding. **2.8 Relationship to Nexus Rails.** Nexus Rails shall route ILA records through appropriate learning, evidence, Academy, Foundry, National Node, Studio, Marketplace, Registry, Grid, TRL, Archive, Correction, Renewal, and lawful handoff pathways. Rails shall prevent informal conversion of learning into certification, employment qualification, procurement qualification, finance-readiness, or deployment authority. **2.9 Relationship to Nexus Grid.** Nexus Grid may receive bounded inputs concerning learning-pack maturity, training-object maturity, support readiness, documentation quality, evidence sufficiency, or contribution-pathway quality. ILA learner records shall not be converted into Grid certification, maturity certification, professional standing, or procurement status. **2.10 Relationship to Nexus Marketplace.** Nexus Marketplace may make learning resources, Academy modules, Foundry quests, contribution opportunities, public-good tools, training packs, learning packs, and support materials discoverable. Marketplace discovery shall not imply quality approval, accreditation, procurement preference, employer endorsement, or professional certification. **2.11 Relationship to Nexus Registry.** Nexus Registry may preserve status truth for learning packs, Academy modules, ILA templates, credential templates, support status, lifecycle state, correction state, archive state, and public-safe notices. Registry status shall not create accreditation, certification, degree equivalence, or statutory recognition. **2.12 Relationship to Nexus Studio.** Nexus Studio may provide controlled runtime learning environments for simulations, dashboards, AI workflows, agentic workflows, public authority learning rooms, secure rooms, data rooms, readiness demonstrations, and handoff dependency demonstrations. Studio participation shall be access-controlled, output-reviewed, privacy-aware, and non-authoritative. **2.13 Relationship to Nexus Consortiums and National Nodes.** National Nodes, National Nexus Consortiums, National Councils, National Working Groups, and Nexus Competence Cells may use the ILA to form national capability, localize learning pathways, support national portfolios, train contributors, develop public authority learning cohorts, and structure workforce-readiness pathways. National use shall preserve national ownership, national data controls, language localization, legal localization, cultural context, community safeguards, and Indigenous protocols where applicable. **2.14 Relationship to Lawful Handoff.** ILA records may support lawful handoff by documenting learner participation, training history, contribution evidence, support exposure, or competence-pathway status where authorized. Such records shall support recipient diligence only and shall not create employment suitability, professional competence certification, safety clearance, procurement qualification, financeability, deployment authorization, or execution authority. *** ### 3. Account Architecture and Record Structure **3.1 Account Architecture.** Each ILA shall be structured as a learner-linked record environment containing identity controls, learner profile settings, privacy settings, accessibility needs where voluntarily provided, language preferences, jurisdictional context, learning achievements, contribution records, competence pathways, evidence references, review levels, support needs, sharing permissions, correction history, expiry status, renewal rules, portability settings, sealing rules, and archive status. **3.2 Learner-Controlled Profile.** The ILA shall support learner agency by enabling the learner to understand what is recorded, what is visible, what is shareable, what is private, what is sealed, what is archived, what is expired, what is portable, and what requires correction, subject to lawful retention, institutional record obligations, incident preservation, public-safe obligations, and archive rules. **3.3 Record Classes.** The ILA may include: **3.3.1 Learner Profile Record.** A record of learner-selected profile information, learning goals, pathway preferences, language preferences, accessibility preferences where voluntarily provided, and jurisdictional context. **3.3.2 Learning Achievement Record.** A record of completed formal education, modules, courses, micro-credentials, Academy tracks, professional learning, informal learning, experiential learning, and structured self-directed learning where recordable. **3.3.3 Contribution Record.** A record of participation in Nexus quests, bounties, builds, documentation, testing, translation, accessibility work, public-safe reporting, safeguard review support, data work, cyber work, AI work, Marketplace support, Registry support, Studio support, Grid support, TRL evidence support, teardown, archive, or correction. **3.3.4 Evidence-of-Learning Record.** A record of artifacts, reviewer notes, assessment results, repository references, public-safe outputs, supervised demonstrations, peer review, mentor review, Studio logs where appropriate, secure-room records where permitted, or other evidence supporting a learning claim. **3.3.5 Competence Pathway Record.** A record of progress through a defined pathway, including prerequisites, modules, work-integrated tasks, review status, renewal requirements, and limits. **3.3.6 National Learning Record.** A record of national-context learning, National Node participation, National Working Group participation, Competence Cell participation, language localization, legal localization, public authority learning exposure, and national systems-risk learning. **3.3.7 Safeguard Learning Record.** A record of learning related to community safeguards, Indigenous protocols where applicable, protected knowledge, accessibility, plain language, youth safeguards, disability inclusion, rights-bearing data, and public-interest participation. **3.3.8 Public Authority Learning Participation Record.** A record of participation in public authority learning contexts without implying public authority approval, official status, public employment qualification, or public procurement status. **3.3.9 Support and Mentorship Record.** A record of mentorship, supervision, coaching, feedback, reviewer engagement, or learning support without creating employment, professional licensure, or competency certification by implication. **3.3.10 Portability Record.** A record stating what may be exported, shared, verified, restricted, sealed, transferred, or archived. **3.3.11 Correction Record.** A record of correction, downgrade, expiry, supersession, withdrawal, sealing, deletion where required, or archive. **3.3.12 Archive Record.** A historical record of prior learning status, expired credits, superseded pathways, withdrawn credentials, sealed records, non-current status, and reinstatement rules. **3.4 Validity-by-Record.** No ILA status shall exist by implication. Learning credit, pathway progress, competence evidence, contribution credit, support exposure, Studio participation, Core Build participation, Nexus Universe participation, National Node participation, or Competence Cell participation shall be recognized only where recorded. **3.5 Status Classes.** ILA records may be classified as draft, self-attested, issuer-submitted, learner-verified, peer-reviewed, mentor-reviewed, institution-issued, Academy-issued, Foundry-reviewed, National Node-reviewed, secure-room-reviewed, public-safe-reviewed, externally verified, expired, withdrawn, superseded, sealed, archived, or deletion-verified. *** ### 4. Learning Credit and Competence Model **4.1 Learning Credit Defined.** **Learning Credit** shall mean a bounded record of completed learning, contribution, assessment, experience, or review within a defined scope, issuer context, pathway, evidence level, expiry rule, and support status. **4.2 Credit Classes.** ILA credits may include formal education credits, continuing professional learning credits, micro-credential credits, Academy module credits, Quest credits, Bounty credits, Build credits, Studio participation credits, Core Build learning credits, Nexus Universe participation credits, National Working Group credits, Competence Cell credits, public authority learning credits, safeguard learning credits, public-safe communication credits, and domain learning credits. **4.3 Credit Accumulation.** Credits may accumulate within pathways, portfolios, learner profiles, national learning programs, Academy tracks, Foundry contributor pathways, Competence Cell workplans, or professional development histories. Accumulation shall not imply qualification unless a competent authority or institution separately grants such status. **4.4 Credit Meaning.** Each credit shall state issuer, scope, evidence basis, review level, date, version, expiry, renewal requirement, support status, portability, restrictions, and limitations. A credit without scope shall not be treated as a generalized competence claim. **4.5 Micro-Credential Boundary.** Micro-credentials may record bounded learning achievements. They shall not become degrees, professional licenses, regulated qualifications, public authority approvals, procurement qualifications, security clearances, finance qualifications, insurance qualifications, or employment guarantees by implication. **4.6 Competence Pathways.** Competence pathways shall organize credits and evidence into structured progressions. They may identify foundational, intermediate, advanced, reviewer, maintainer, steward, or specialist learning levels, but pathway levels shall not be represented as professional certification unless separately authorized. **4.7 Competence Evidence.** Competence evidence may include assessed work, supervised contributions, reviewed artifacts, repository history, Studio participation, public-safe outputs, documentation, test records, incident lessons, safeguard participation, and mentor review. Evidence shall remain contextual and bounded. **4.8 Credit Expiry and Renewal.** Credits may expire where the underlying knowledge, technology, safety practice, legal context, AI practice, cyber control, data control, public-safe language, or support framework changes materially. Expired credits may remain historical but shall not be displayed as current. **4.9 Credit Portability.** Credits may be portable across Nexus Academy, Foundry, National Nodes, universities, training providers, employers, or other lawful recipients where permitted by learner control, issuer rules, jurisdictional law, data controls, privacy rules, and interoperability standards. **4.10 Credit Interoperability.** ILA credits may map to skills taxonomies, learning standards, qualification frameworks, competency frameworks, professional development systems, or institutional learning systems. Mapping shall not imply equivalence unless expressly recorded by a competent body. *** ### 5. Pathway Architecture **5.1 Personalized Learning Pathways.** The ILA shall support personalized learning pathways based on learner goals, national priorities, Nexus Academy tracks, Foundry backlogs, Nexus Universe preparation, domain needs, Observatory signals, public authority learning needs, Competence Cell needs, and lawful workforce-transition requirements. **5.2 Nexus Foundry Contributor Pathway.** This pathway shall prepare learners to contribute to intake, classification support, scoping support, documentation, evidence capture, testing, release preparation, Marketplace preparation, Registry preparation, Studio preparation, Grid support, TRL evidence support, teardown, archive, and correction. **5.3 Nexus Observatory and DRI Pathway.** This pathway shall cover signals, observations, DRI, GRIx, indicators, dashboards, uncertainty, confidence, drift labels, geospatial sensitivity, public-safe risk summaries, and no-warning discipline. **5.4 Nexus Public-Safe Reporting Pathway.** This pathway shall cover claims-safe language, public-safe summaries, accessibility, translation, no-warning notices, no-approval notices, no-finance notices, no-procurement notices, no-consent notices, correction notices, withdrawal notices, and archive notices. **5.5 Data, Privacy, Cyber, and AI Pathway.** This pathway shall cover data classification, privacy, cybersecurity, secure rooms, data rooms, AI output review, agentic workflow controls, prompt-injection awareness, model and system cards, secure technical operations, incident response, and correction. **5.6 National Portfolio Pathway.** This pathway shall cover National Context Records, National Systems-Risk Maps, National Challenge Briefs, Evidence Need Records, Observatory Need Records, Core Build Requests, Safeguard Records, Public Authority Learning Records, Readiness Question Records, Competence Cell Workplans, Arena Routing Records, and National Portfolio Archives. **5.7 Readiness and Handoff Pathway.** This pathway shall cover assumptions registers, dependency registers, diligence-gap registers, finance-readiness notes, insurance-readiness question maps, donor-readiness notes, public finance relevance notes, no-reliance language, recipient responsibilities, lawful handoff dependency packages, correction, and recall. **5.8 Marketplace, Registry, and Studio Pathway.** This pathway shall cover bounded discovery, status truth, lifecycle states, support labels, release classes, Registry fields, Marketplace metadata, Studio runtime controls, no-write-back rules, no-command rules, output review, shutdown triggers, and archive. **5.9 TRL and Grid Pathway.** This pathway shall cover TRL 1–10 as a bounded technical readiness classification, evidence packs, test records, safeguard records, support records, public-safe records, Grid input records, downgrade triggers, suspension triggers, reinstatement rules, and no-certification discipline. **5.10 Safeguards and Protected Knowledge Pathway.** This pathway shall cover community safeguards, Indigenous protocols where applicable, protected knowledge, accessibility, plain-language requirements, youth participation, disability inclusion, rights-bearing data, public-interest participation, consent boundaries, sealing, deletion, and community-facing correction. **5.11 Domain and Sector Pathways.** Domain pathways may include water, energy, food, health, biodiversity, climate adaptation, disaster risk intelligence, disaster risk finance, infrastructure resilience, ports and corridors, cities, public health and biosecurity, cyber and cyber-physical systems, AI and agentic systems, AI-RAN/O-RAN and telecom, geospatial and Earth observation, drones and robotics, sensors and IoT, sovereign compute, HPC, cloud, Edge, DePIN, DLT, blockchain, trust infrastructure, quantum-relevant security, semiconductors, advanced manufacturing, supply chains, humanitarian systems, community resilience, and public-safe communications. **5.12 Pathway Adaptation.** Pathways shall be dynamic. They may be updated based on Observatory signals, labor-market shifts, national priorities, public authority learning needs, Foundry backlogs, new technologies, incidents, corrections, support changes, legal developments, safeguards, and next-cycle formation. *** ### 6. Verification, Evidence, and Trust Model **6.1 Verification Principle.** ILA records shall be verified proportionately to the claim they support. A low-stakes learning reflection may require lighter verification; a record used for controlled room access, secure work, public authority learning, safety-sensitive work, or handoff support may require stronger review. **6.2 Zero-Trust Learning Environment.** The ILA shall operate under a zero-trust learning-record posture. No credential, claim, artifact, badge, certificate, micro-credential, contribution, repository entry, public statement, digital signature, blockchain anchor, or provider-issued record shall be assumed valid without context, scope, issuer status, review level, expiry, limitations, and correction status. **6.3 Verification Sources.** Verification may include issuer confirmation, university records, training provider records, Academy records, Foundry records, National Node records, mentor review, peer review, supervisor review, repository records, assessment records, Studio logs where appropriate, data-room records, secure-room records, public-safe review records, contribution artifacts, and third-party credential systems. **6.4 Verifiable Credentials.** The ILA may support verifiable credentials, cryptographic attestations, digital signatures, proof receipts where authorized, tamper-evident records, repository proofs, or DLT-based records where they improve provenance, portability, and auditability. **6.5 Verifiable Technology Boundary.** Blockchain, DLT, cryptographic proof, verifiable credentials, or proof receipts shall support record integrity only. They shall not create competence, professional licensure, degree equivalence, certification, employment suitability, public authority approval, procurement status, financeability, or universal truth by implication. **6.6 Review Levels.** ILA records may display review levels, including self-attested, peer-reviewed, mentor-reviewed, issuer-confirmed, Academy-reviewed, Foundry-reviewed, National Node-reviewed, public-safe-reviewed, secure-room-reviewed, externally verified, expired, withdrawn, superseded, sealed, or archived. **6.7 Evidence Linkage.** Learning records shall link to evidence only where lawful, safe, privacy-compliant, and appropriate. Sensitive artifacts, protected knowledge, secure-room outputs, youth-related records, health-related information, disability-related information, public authority-sensitive records, or restricted work shall not be exposed through evidence links. **6.8 Fraud, Error, and Misrepresentation.** Fraudulent, misleading, duplicated, unsupported, or overclaimed records shall be corrected, restricted, withdrawn, downgraded, sealed, or archived. The ILA shall maintain correction history proportionate to privacy and public-safe requirements. *** ### 7. Data, Privacy, Security, and Learner Rights **7.1 Learner Data Classification.** ILA data shall be treated as learner-sensitive data. It may include identity data, education data, work history, contribution history, learning preferences, accessibility needs where voluntarily provided, language preferences, jurisdictional data, assessment data, mentor feedback, behavioral learning data, AI interaction data, and sensitive pathway records. **7.2 Data Minimization.** The ILA shall collect only data reasonably required for learning records, pathway support, verification, learner control, portability, correction, reporting, support, renewal, and archive. **7.3 Learner Control.** Learners shall have meaningful visibility and control over sharing, portability, privacy, correction requests, expiry visibility, archive visibility, and third-party access, subject to lawful retention, legal hold, institutional obligations, incident preservation, and archive requirements. **7.4 Consent and Permission.** Where consent or permission is required, it shall be specific, informed, recorded, revocable where lawful, and separate from participation pressure. Participation in Nexus learning shall not require unnecessary exposure of personal data. **7.5 Sensitive Data Controls.** Youth data, health-sensitive data, disability-related data, biometric data, location data, protected knowledge, Indigenous knowledge where applicable, community-sensitive data, public authority data, secure-room records, and behavioral telemetry shall receive heightened classification, access control, retention, sealing, deletion, and publication protections. **7.6 Security Controls.** The ILA shall implement appropriate authentication, authorization, encryption where appropriate, least privilege, access logs where appropriate, credential management, API security, connector governance, incident response, deletion, sealing, archive controls, and cybersecurity correction. **7.7 Analytics Boundary.** Analytics may support pathway recommendations, skill-gap identification, learning-resource suggestions, national capacity planning, Academy design, Foundry workforce planning, and public-safe aggregate insight. Analytics shall not create automated employment decisions, public authority decisions, insurance decisions, credit decisions, immigration decisions, procurement decisions, professional licensing decisions, or social ranking. **7.8 AI Use Boundary.** AI may assist with pathway recommendations, skills mapping, learning-resource suggestion, translation, accessibility, feedback support, and gap analysis. AI outputs shall be reviewable, explainable where appropriate, correctable, non-authoritative, and subject to bias, privacy, safeguard, and public-safe review. **7.9 Surveillance Prohibition.** The ILA shall not become a surveillance system, productivity-monitoring system, employment surveillance tool, behavioral scoring system, social ranking system, public authority intelligence system, insurer scoring system, credit scoring system, or procurement scoring system. **7.10 Data Deletion, Sealing, and Archive.** ILA records shall support deletion where required, sealing where preservation without access is required, and archive where memory must be preserved without current status. Archived learning records shall not appear current unless reinstated by current record. *** ### 8. Technical Architecture **8.1 Platform Architecture.** The ILA may be implemented through a secure digital platform supporting learner profiles, learning records, contribution records, credential records, evidence references, pathway maps, review levels, support classes, privacy settings, sharing permissions, verification status, correction records, expiry status, renewal triggers, portability controls, and archive states. **8.2 Interoperability.** The ILA should interoperate with learning management systems, credential systems, identity systems, repository systems, Nexus Academy systems, Nexus Foundry systems, Nexus Marketplace, Nexus Registry, Nexus Studio, Nexus Network records, National Node systems, and lawful external systems where appropriate. **8.3 Controlled Vocabulary.** ILA records shall use controlled vocabulary for skills, domains, competence areas, pathway levels, credential types, review levels, verification levels, support status, expiry, correction, archive, sharing permissions, and no-conversion labels. **8.4 APIs and Connectors.** ILA APIs and connectors shall be governed by access controls, data minimization, permission rules, interoperability testing, security review, privacy review, rate limits, audit logs where appropriate, retirement rules, and connector archive. **8.5 Digital Credential Stack.** The ILA may support signed credentials, verifiable credentials, issuer registries, proof receipts where authorized, cryptographic attestations, and tamper-evident records. These shall be used for provenance and portability, not universal validation. **8.6 Integration With Learning Management Systems.** LMS integrations may allow import of course completion, module progress, assessment results, instructor feedback, and learning artifacts where authorized. Imported records shall retain source, date, scope, issuer, review level, expiry, and correction status. **8.7 Repository Integration.** Repository integration may record contribution evidence, documentation work, code contributions, issue participation, pull request review, release support, and archive participation. Repository contribution shall not imply competence certification or employment qualification. **8.8 Studio Integration.** Studio integration may record participation in controlled simulations, dashboards, AI workflows, data-room exercises, secure-room exercises, and public authority learning rooms. Studio learning records shall be privacy-aware and shall not expose sensitive runtime information by default. **8.9 Marketplace and Registry Integration.** Marketplace may expose learning resources; Registry may preserve status truth for learning objects. ILA integration with both shall display support class, lifecycle state, review level, expiry, correction status, and no-conversion language. **8.10 Recommendation Engine.** The ILA may include recommendation tools that suggest learning pathways, modules, quests, bounties, mentors, Competence Cells, National Working Groups, or domain tracks. Recommendations shall remain advisory and shall not determine access, employment, certification, public authority status, procurement status, or financeability by implication. *** ### 9. Institutional Interfaces **9.1 Nexus Academy Interface.** Nexus Academy may design and issue learning modules, pathway maps, learning packs, training materials, work-integrated learning tracks, reviewer training, maintainer training, public-safe communication training, safeguard training, and domain learning tracks that feed ILA records. **9.2 University and Training Provider Interface.** Universities, colleges, schools, training providers, professional learning organizations, and public-good education partners may issue or map learning records into the ILA where permitted. Their participation shall not make Nexus the accreditor of those institutions by default. **9.3 Employer and Enterprise Interface.** Employers and enterprise actors may review learner-authorized ILA records for independent diligence, talent development, training support, or workforce planning. Employers remain responsible for their own hiring, safety, legal, compliance, security, professional, and employment decisions. **9.4 Public Authority Interface.** Public authorities may use aggregate, anonymized, public-safe, or authorized ILA insights for workforce planning, public authority learning, national capacity assessment, or education-policy learning. ILA records shall not create public employment eligibility, licensing status, public procurement qualification, immigration status, public funding entitlement, or public authority approval by implication. **9.5 National Node Interface.** National Nodes may use the ILA to structure national learning cohorts, public authority learning cohorts, domain learning tracks, National Portfolio support teams, Competence Cell pathways, Academy cohorts, and national workforce-readiness pathways. **9.6 Competence Cell Interface.** Competence Cells may use the ILA to record participation, track learning progress, identify capability gaps, route learners to quests and bounties, document contribution evidence, support mentorship, and prepare national capacity formation. **9.7 Sponsor and Provider Interface.** Sponsors and providers may support learning resources, compute, tools, venues, scholarships, translation, accessibility, mentorship, technical content, or infrastructure. Such support shall not create sponsor control, provider validation, preferred-vendor status, certification, employment guarantee, procurement preference, or financeability. **9.8 Community and Public-Interest Interface.** Community organizations, public-interest actors, youth groups, accessibility advocates, humanitarian actors, and civil society participants may engage with ILA pathways where appropriate. Their participation shall be non-extractive, accessible, protected, and not converted into consent or endorsement. **9.9 Indigenous Protocol Interface.** Where Indigenous participants, knowledge, data, lands, protocols, or governance contexts are implicated, ILA records shall apply appropriate protocol safeguards, protected knowledge rules, consent-boundary language, access restrictions, sealing rules, and public-safe communication controls. *** ### 10. National Capacity and Workforce Resilience Function **10.1 National Capacity Formation.** The ILA shall support National Nodes, National Nexus Consortiums, National Working Groups, and Competence Cells in building national capability across priority domains, including climate adaptation, disaster risk, water, energy, food, health, biodiversity, infrastructure, cities, cyber, AI, telecom, geospatial, sovereign compute, public-safe reporting, safeguards, readiness mapping, and lawful handoff support. **10.2 Workforce Resilience.** The ILA shall support workforce resilience by enabling continuous learning, reskilling, upskilling, cross-domain mobility, public-good contribution, work-integrated learning, and adaptive learning pathways that respond to technological, economic, environmental, and societal change. **10.3 National Portfolio Linkage.** National Portfolios may identify capability needs that inform ILA pathways. ILA learning records may in turn help National Nodes understand capacity formation, but shall not be used as public authority approval, employment entitlement, procurement qualification, or finance-readiness proof. **10.4 Public Authority Learning Linkage.** Public authority learning needs may inform Academy tracks and ILA pathways, including resilience planning literacy, evidence interpretation, dashboard interpretation, data governance, AI literacy, public-safe language, readiness questions, and non-decision records. **10.5 Domain Capability Mapping.** Aggregate and privacy-protected ILA data may help identify national or regional capability gaps, such as shortage of reviewers, maintainers, data stewards, AI reviewers, cyber stewards, public-safe writers, domain experts, accessibility reviewers, safeguard reviewers, or handoff-support roles. **10.6 Workforce Planning Boundary.** ILA-derived workforce insights shall not be used as deterministic ranking, employment gatekeeping, public authority eligibility, procurement scoring, insurance scoring, immigration scoring, or social scoring. *** ### 11. Public-Safe Reporting and Knowledge Base Function **11.1 Public-Safe ILA Outputs.** The ILA may generate public-safe aggregate reports on learning trends, emerging skills, Academy pathway uptake, Foundry contribution patterns, National Node capability formation, Competence Cell growth, Nexus Universe learning outputs, and workforce-readiness needs. **11.2 Privacy-Preserving Reporting.** Public reporting shall avoid personally identifying information unless lawfully authorized and necessary. It shall protect sensitive learner data, youth data, health-related data, disability-related data, protected knowledge, Indigenous knowledge where applicable, community-sensitive information, and public authority-sensitive learning records. **11.3 Claims Discipline.** Public-safe ILA outputs shall not rank individuals, communities, Indigenous groups, institutions, countries, providers, or sponsors in unsafe or misleading ways. Reports shall avoid employment-market overclaim, certification overclaim, public authority overclaim, finance overclaim, procurement overclaim, and social-ranking effects. **11.4 Knowledge Base Integration.** ILA public-safe materials may become Nexus knowledge-base resources, including pathway explainers, learning guides, public-good competence maps, contribution guides, support materials, public-safe summaries, correction notices, and institutional learning reports. **11.5 Reporting Boundary.** Public-safe ILA reporting shall not create government approval, workforce certification, institutional ranking, country ranking, provider validation, employer recommendation, procurement preference, financeability, public finance allocation, public authority decision, or execution authority. *** ### 12. Governance, Stewardship, and Accountability **12.1 ILA Stewardship.** The ILA shall be stewarded through role-separated Nexus governance pathways addressing learning design, technical architecture, data protection, privacy, cybersecurity, public-safe communication, safeguards, national localization, support, correction, archive, and renewal. **12.2 GCRI-Supported Functions.** The Global Centre for Risk and Innovation (GCRI) may support ILA evidence methods, ontology, controlled vocabulary, observability linkages, public-good software, technical baselines, data and AI controls, verifiable records, and competence-related research. **12.3 GRF-Supported Functions.** The Global Risks Forum (GRF) may support ILA public-good legitimacy, claims discipline, stakeholder formation, public-safe reporting, standing records, learning-record meaning, Gazette notices where applicable, and correction culture. **12.4 GRA-Supported Functions.** The Global Risks Alliance (GRA) may support learning pathways related to finance-readiness, capital-readability, insurance-readiness, diligence translation, no-reliance rooms, regulated-perimeter discipline, and readiness-room literacy without creating finance, insurance, or investment activity. **12.5 Institutional Role Separation.** The ILA shall not collapse the roles of GCRI, GRF, GRA, protocol authority, Nexus Consortiums, National Nodes, National Consortium Companies, Project SPVs, universities, training providers, public authorities, sponsors, providers, employers, capital readers, insurers, donors, communities, Indigenous participants where applicable, or enterprise actors. **12.6 Quality Governance.** ILA governance shall maintain quality controls over pathway design, learning-record standards, issuer participation, verification rules, review levels, public-safe labels, privacy controls, support labels, expiry, correction, withdrawal, archive, and renewal. **12.7 Conflict Controls.** Conflicts may arise where providers issue learning records related to their own tools, employers review learner records, sponsors fund pathways, public authorities participate in learning rooms, or universities map credentials. Such conflicts shall be disclosed, recorded, managed, and corrected. **12.8 Accessibility and Inclusion.** ILA governance shall ensure accessibility, plain-language explanations, multilingual pathways where appropriate, reasonable accommodation processes, and non-discriminatory pathway design. **12.9 Accountability.** ILA accountability shall include privacy accountability, security accountability, bias accountability, correction accountability, public-safe reporting accountability, accessibility accountability, issuer accountability, platform accountability, and national localization accountability. *** ### 13. Lifecycle, Support, Correction, and Archive **13.1 Lifecycle Stages.** ILA records may move through draft, submitted, classified, reviewed, verified, issued, active, shareable, restricted, expired, renewed, corrected, withdrawn, sealed, retired, archived, or deletion-verified states. **13.2 Support Classes.** ILA learning objects, pathway templates, Academy modules, credential templates, and learning packs may be Unsupported, Community-Supported, Maintained, Controlled Support, Enterprise-Supported, National-Node-Supported, Regional-Supported, Deprecated, Retired, or Archived. **13.3 Correction.** Incorrect records, overstated credits, expired credentials, unsupported badges, wrong issuer information, duplicated records, privacy errors, AI recommendation errors, pathway mapping errors, public-safe reporting errors, or misleading public displays shall be corrected. **13.4 Expiry.** Learning records may expire based on time, technology change, legal change, safety change, cyber change, AI change, public-safe language change, domain change, support lapse, issuer withdrawal, or pathway redesign. **13.5 Renewal.** Renewal may require updated learning, reassessment, review, evidence update, public-safe update, data/cyber update, AI update, safeguard update, or national localization update. **13.6 Withdrawal.** Records may be withdrawn where issued in error, unsupported, unsafe, fraudulent, privacy-violating, misclassified, overclaimed, duplicated, or superseded. **13.7 Sealing.** Sensitive records may be sealed where access must be restricted but preservation is required, including youth records, health-related records, disability-related records, protected knowledge records, Indigenous protocol-sensitive records where applicable, public authority-sensitive records, secure-room records, incident records, and legal-hold records. **13.8 Archive.** Archived records shall preserve memory without current status. Archived records shall not be displayed as active credit, current competence, current pathway completion, current qualification, or current support. **13.9 Renewal Without Automatic Continuation.** No ILA pathway, credit, credential, badge, contribution record, support record, competence record, or public display shall continue automatically into a new cycle merely because it was previously earned, issued, supported, sponsored, displayed, or used. Renewal shall require current record where current meaning matters. *** ### 14. Claims, Display, and Public Meaning **14.1 Display Discipline.** ILA dashboards, learner profiles, badges, certificates, pathway displays, progress bars, shareable records, public summaries, Marketplace listings, Registry entries, and knowledge-base references shall display status truth, review level, support class, expiry, limitations, and no-conversion language where reliance risk exists. **14.2 Badge Discipline.** Badges shall be designed to avoid overclaim. A badge may show completion, participation, review level, pathway progress, or contribution class, but shall not imply certification, licensure, employment suitability, procurement qualification, financeability, safety clearance, public authority approval, or deployment authority. **14.3 Public Profile Discipline.** Learner-facing and public-facing profiles shall clearly distinguish self-attested learning, verified learning, reviewed contribution, formal credential, Academy pathway progress, Competence Cell participation, and archived records. **14.4 Employer-Facing Discipline.** Employer-facing exports shall include limitations, issuer context, review level, evidence references where shareable, expiry, correction history where appropriate, and no-guarantee language. **14.5 Public Authority-Facing Discipline.** Public authority-facing reports shall distinguish aggregate workforce-learning insight from approval, eligibility, public employment status, public procurement status, licensing, immigration status, or public funding entitlement. **14.6 Public-Safe Display Formula.** ILA display shall follow the formula: **show learning truth clearly, show limits visibly, protect privacy, prevent overclaim, correct stale status, and never let display become certification, employment entitlement, procurement, finance, or authority.** *** ### 15. Standard No-Conversion Rule **15.1 No-Conversion.** No ILA account, learning record, credit, micro-credential, badge, pathway, Academy module, Quest completion, Bounty completion, Build contribution, Studio participation, Core Build participation, Nexus Universe participation, National Node participation, National Working Group participation, Competence Cell participation, public authority learning participation, Marketplace interaction, Registry reference, Grid support, TRL support, readiness-room participation, Handoff Package support, sponsor-supported learning, provider-supported learning, public-safe report, analytics output, recommendation, export, portfolio, or archive record shall create scientific consensus, recognition, certification, accreditation, academic degree, professional license, employment eligibility, hiring recommendation, legal compliance, ethical certification, privacy compliance, cybersecurity certification, government approval, public authority approval, public warning, official classification, procurement status, commercial approval, provider validation, supplier approval, financeability, insurability, underwriting acceptance, investment readiness, donor commitment, public finance allocation, rating, valuation, solicitation, offer, transaction readiness, maturity certification beyond recorded bounded status, warranty beyond stated terms, community consent, Indigenous consent where applicable, consultation completion, protected knowledge permission, land access, rights waiver, spectrum approval, flight approval, operational authorization, deployment authorization, operational command, or execution authority by implication. *** ### 16. Final Integrated Learning Account Operating Formula **16.1 Final ILA Formula.** The controlling Integrated Learning Account formula is that **Nexus Academy designs learning pathways; Nexus Foundry supplies work-integrated learning objects; Nexus Universe concentrates annual learning and contribution opportunities; Nexus Core Build provides high-intensity technical learning contexts; Nexus Observatory identifies emerging competence needs; Nexus Network preserves authorized learning records; Nexus Rails route learning records; Nexus Registry preserves status truth for learning objects; Nexus Marketplace enables bounded discovery of learning resources; Nexus Studio provides controlled runtime learning; Nexus Grid may receive bounded maturity inputs for learning objects without certification; National Nodes localize competence formation; National Working Groups and Competence Cells convert learning into national capability; universities and training providers contribute learning records within their own roles; employers and enterprise actors conduct independent diligence; public authorities may learn from aggregate or authorized records without approval by implication; and lawful handoff may receive dependency-support records without Nexus executing. The ILA records learning, contribution, evidence, review, support, correction, renewal, and archive; it does not certify, license, employ, procure, finance, insure, approve, consent, deploy, command, or execute by implication.** ### Concise summary The ILA is Nexus’s governed learner record. It connects learning, contribution, evidence, and pathway progress across the ecosystem. It supports portability, skills tracking, and workforce formation without becoming certification or authority. ### Next steps * Explore [Nexus Academy](/organization/organization/architecture/ii.-definitions/xxiii.-nexus-academy.md) for structured learning pathways. * Connect learning and contribution records through [Integrated Credits Rewards System (iCRS)](/organization/operations/mechanisms/integrated-credits-rewards-system-icrs.md). * Use [Work-Integrated Learning Paths (WILPs)](/organization/operations/mechanisms/work-integrated-learning-paths-wilps.md) to move into applied learning. ### Related topics * [Nexus Academy](/organization/organization/architecture/ii.-definitions/xxiii.-nexus-academy.md) * [Integrated Credits Rewards System (iCRS)](/organization/operations/mechanisms/integrated-credits-rewards-system-icrs.md) * [Work-Integrated Learning Paths (WILPs)](/organization/operations/mechanisms/work-integrated-learning-paths-wilps.md) --- # 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/mechanisms/integrated-learning-account-ila.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.