# VIII. PATHWAYS ## **8.1 WILP Doctrine** ### **8.1.1 WILPs as Evidence-Bearing Learning Through Work.** 8.1.1.1 **Work-Integrated Learning Paths (WILPs)** shall mean structured, supervised, scoped, evidence-bearing, safeguard-aware, and correctionable learning pathways through which learners, workers, career changers, students, contributors, public authority learning participants, and public-good participants acquire, demonstrate, apply, and record competencies through real or simulated work objects, practice environments, supervised contribution, field experience, public-good production, or controlled institutional participation. 8.1.1.2 WILPs shall be designed to connect learning with practice without collapsing learning into employment, contribution into execution, practice into professional authorization, or host participation into endorsement. A WILP shall always state its learning purpose, work scope, host context, supervision level, evidence outputs, learner status, data and confidentiality rules, health and safety controls, public-safe output rules, safeguard requirements, correction pathway, and labor boundary. 8.1.1.3 WILPs shall be evidence-bearing because each WILP shall produce records. Such records may include learning agreements, workplans, mentor assignments, supervision records, portfolio artifacts, work product evidence, public-safe summaries, host verification, mentor verification, reflection records, competency evidence, micro-credential eligibility, ILA records, iCRS records, Registry linkages where applicable, Marketplace display eligibility where appropriate, National Portfolio inputs, Nexus Universe participation records, and lawful handoff-context notes. 8.1.1.4 WILPs shall be governed as learning infrastructure, not as informal labor markets. Where a WILP involves paid employment, contracted work, stipends, honoraria, apprenticeships, co-operative education, internships, public service placements, or other work-connected arrangements, the relevant legal, employment, education, host, health and safety, wage, tax, insurance, immigration, child protection, accessibility, and labor standards obligations shall remain outside SCF’s default credentialing role and shall be handled by the competent parties. ### **8.1.2 WILPs as Bridges Between Learning and Contribution.** 8.1.2.1 WILPs shall operate as bridges between learning and contribution by allowing learners to move from course completion, risk literacy, technical training, public-safe reporting, data literacy, AI literacy, cyber literacy, safeguard learning, or domain learning into bounded practice and supervised contribution. 8.1.2.2 The bridge function of WILPs shall be structured in stages:\ (a) learning orientation;\ (b) competency mapping;\ (c) scope definition;\ (d) host or practice-environment assignment;\ (e) mentor or supervisor assignment;\ (f) workplan approval;\ (g) evidence production;\ (h) review;\ (i) reflection;\ (j) credential or contribution recording where applicable;\ (k) correction;\ (l) archive or continuation. 8.1.2.3 WILPs may route learners into Nexus Academy, Risk Academy, Nexus Foundry, Nexus Campaigns, Nexus Labs, Nexus Reports, Nexus Marketplace, Nexus Registry, Nexus Studio, Nexus Grid, Nexus Universe, National Working Groups, Competence Cells, Risk Agency pathways, National Portfolios, and lawful handoff literacy pathways. 8.1.2.4 WILP contribution shall not be treated as proof of authority. Contribution shall become evidence only within its recorded scope, review status, and competency context. ### **8.1.3 WILPs as National Capability Formation Tools.** 8.1.3.1 WILPs shall support national capability formation by connecting learners and contributors to national skills needs, National Skills Maps, National Portfolios, National Challenge Briefs, National Working Groups, Competence Cells, National Nodes, National Nexus Consortium pathways, Nexus Universe preparation, and lawful handoff literacy. 8.1.3.2 WILPs may support national capability in WFEH-B systems, DRR, DRF, DRI, climate adaptation, public health resilience, infrastructure resilience, food systems, water systems, energy systems, biodiversity, cyber-physical systems, AI, data, cyber, geospatial, Earth observation, telecom, edge, HPC, cloud, sovereign compute, digital twins, sensors, robotics, drones, manufacturing, semiconductors, biosecurity-sensitive systems, public-safe reporting, public authority learning, and finance-readiness literacy. 8.1.3.3 National capability use of WILP records shall preserve learner privacy, data minimization, permission controls, youth protections, sensitive profile controls, community safeguards, Indigenous protocols where applicable, protected knowledge restrictions, and non-ranking rules. 8.1.3.4 WILPs shall not create national endorsement, public authority approval, public employment status, public procurement qualification, official workforce certification, immigration status, public finance eligibility, or execution authority by implication. ### **8.1.4 WILPs as Public-Good Production Pathways.** 8.1.4.1 WILPs may function as public-good production pathways where learners contribute to public-good software, datasets, metadata, dashboards, reports, public-safe summaries, ontologies, schemas, learning objects, Campaign objects, Marketplace listings, Registry records, Studio workflows, Grid inputs, TRL evidence notes, DRI summaries, Observatory outputs, National Portfolio objects, and handoff dependency notes. 8.1.4.2 Public-good production through WILPs shall be scoped, supervised, reviewed, attributed, licensed where applicable, recorded, and corrected. It shall preserve public-good stack and enterprise-stack separation and shall avoid any implication that learner work creates deployment authorization, production warranty, procurement recommendation, professional certification, or enterprise execution. 8.1.4.3 Public-good WILP production may support Nexus Foundry and BuildGrid by routing learners into quests, bounties, builds, micro-tasks, micro-reviews, documentation, testing, translation, accessibility improvements, data stewardship, public-safe reporting, and correction work. 8.1.4.4 Where public-good production produces reusable objects, those objects shall be governed through applicable SCF, NAF, DDPGF, DICE, Registry, Marketplace, Reports, Grid, Studio, and correction controls. ### **8.1.5 WILPs as Safe Practice Environments.** 8.1.5.1 WILPs shall be safe practice environments. They shall permit learners to practice, contribute, fail safely, receive feedback, correct outputs, and build competence without being exposed to unmanaged risks, disguised labor, unsafe field conditions, unauthorized data access, exploitative work demands, professional overclaim, public authority overclaim, or execution pressure. 8.1.5.2 Safe practice environments may include classrooms, labs, studios, simulations, digital twins, secure rooms, data rooms, clean rooms, field exercises, public authority learning rooms, readiness rooms, Campaign rooms, Foundry build environments, National Working Group contexts, Competence Cells, and supervised host settings. 8.1.5.3 WILP safety shall include physical safety, psychosocial safety, digital safety, privacy, cybersecurity, harassment prevention, discrimination prevention, accessibility, workload control, youth protection, fieldwork safeguards, protected knowledge safeguards, public-safe communications, and clear exit channels. 8.1.5.4 WILP safety shall be a governance obligation, not an optional program feature. ### **8.1.6 WILPs Without Disguised Labor.** 8.1.6.1 WILPs shall not be used to disguise regular labor, replace paid staff, avoid employment obligations, extract unpaid work, fill operational capacity gaps, create shadow workforces, or transfer execution burdens onto learners. 8.1.6.2 Every WILP shall define whether the activity is learning, supervised practice, public-good contribution, stipend-supported contribution, bounty-supported contribution, internship, apprenticeship, co-operative education, contracted work, employment, or another lawful arrangement. Where the arrangement is employment or otherwise regulated, the relevant legal obligations shall be honored by the competent parties. 8.1.6.3 WILP workplans shall be reviewed for exploitation risk, excessive workload, unclear compensation, role ambiguity, safety risk, data exposure, intellectual property ambiguity, sponsor capture, provider capture, or execution overclaim. 8.1.6.4 Where a WILP begins to function as labor rather than learning, it shall be corrected, reclassified, paused, compensated where required by law or agreement, or transferred into an appropriate lawful work arrangement. ### **8.1.7 WILPs Without Employment by Implication.** 8.1.7.1 WILP participation shall not create employment, hiring commitment, worker status, contractor status, wage entitlement, benefits entitlement, immigration status, union status, tax status, procurement status, or future work entitlement by implication. 8.1.7.2 Where employment, apprenticeship, internship, co-op placement, contract, stipend, honorarium, or other paid arrangement exists, that status shall arise from the relevant legal, institutional, or contractual arrangement, not from the WILP record alone. 8.1.7.3 WILP documentation shall state learner status, host status, compensation or support status where applicable, supervision structure, permitted work, prohibited work, IP and attribution terms, health and safety rules, confidentiality obligations, data-use limits, and grievance pathways. 8.1.7.4 WILP completion shall not be represented as hiring commitment, employment verification, job guarantee, wage guarantee, or employer endorsement. ### **8.1.8 WILPs Without Execution by Implication.** 8.1.8.1 WILPs shall not create execution authority. A WILP may produce learning evidence, contribution evidence, portfolio artifacts, public-safe outputs, readiness notes, handoff-context notes, or public-good objects, but it shall not authorize deployment, operations, procurement, public authority action, public warning, finance, insurance, medical action, emergency command, community consent, or enterprise execution. 8.1.8.2 Where WILP outputs are relevant to downstream execution, they shall be routed as context, evidence, dependency notes, or learning records to competent lawful actors. Such actors remain responsible for independent diligence, legal authority, professional judgment, procurement, safety review, public authority processes, finance processes, insurance processes, community engagement, and implementation. 8.1.8.3 WILP outputs shall include boundary notices where their use could be misunderstood. *** ## **8.2 WILP Types** ### **8.2.1 Apprenticeships.** 8.2.1.1 Apprenticeships under SCF may be recognized as structured work-learning pathways where learners receive supervised practical training, progressive skill development, mentor guidance, workplace exposure, and evidence-based competency recording. 8.2.1.2 Apprenticeship pathways shall identify the responsible employer, training provider, public authority or apprenticeship body where applicable, mentor, supervisor, competency map, workplan, safety controls, wage or stipend status where applicable, assessment rules, legal status, and credential pathway. 8.2.1.3 SCF recognition of apprenticeship learning shall not replace statutory apprenticeship requirements, labor law, occupational licensing, collective agreements, public authority approvals, employer obligations, or professional standards. ### **8.2.2 Internships.** 8.2.2.1 Internships may be used where a learner participates in a structured work-learning placement with defined learning objectives, supervision, duration, outputs, feedback, and recordable evidence. 8.2.2.2 Internship WILPs shall include safeguards against unpaid substitution of regular labor, excessive workload, ambiguous work status, unsafe work, harassment, discrimination, hidden recruitment, data misuse, and unclear IP terms. 8.2.2.3 Internship completion shall not constitute hiring commitment, employer endorsement, procurement qualification, public authority approval, or professional credential by implication. ### **8.2.3 Cooperative Education.** 8.2.3.1 Cooperative education WILPs may connect learners, educational institutions, employers, National Nodes, public-good programs, and host environments through structured periods of study and practice. 8.2.3.2 Cooperative education records shall preserve the role of the education institution, host, learner, mentor, assessor, and SCF steward. They shall include work-term scope, learning outcomes, assessment method, evidence outputs, host verification, institutional verification, and correction pathway. 8.2.3.3 Cooperative education shall remain subject to applicable educational, labor, privacy, safety, and host rules. ### **8.2.4 Clinical, Field, and Practicum Models.** 8.2.4.1 Clinical, field, and practicum WILPs may be used where learners require supervised practice in real-world, community, environmental, infrastructure, health-relevant, humanitarian, disaster, policy, public authority learning, lab, or applied technical contexts. 8.2.4.2 Such models shall require heightened attention to safety, supervision, confidentiality, privacy, protected knowledge, community safeguards, public-safe communication, fieldwork risk, trauma sensitivity, local protocols, accessibility, and emergency escalation. 8.2.4.3 Clinical, field, and practicum records shall not authorize independent practice, medical decision-making, public health action, public authority action, emergency response, field deployment, or community consent by implication. ### **8.2.5 Studio-Based Practice.** 8.2.5.1 Studio-based WILPs may occur in Nexus Studio or comparable controlled runtime environments where learners practice using dashboards, simulations, digital twins, AI workflows, secure-room outputs, public-safe summaries, readiness-room materials, or scenario exercises. 8.2.5.2 Studio-based practice shall include no-write-back rules, no-command rules, access controls, output review, logging, AI-use labels, data export restrictions, public-safe restrictions, model limitations, assumptions, confidence and uncertainty notes where applicable, and correction triggers. 8.2.5.3 Studio-based WILP outputs shall not be represented as operational decisions, forecasts, public authority decisions, finance approvals, insurance approvals, deployment authorizations, or emergency commands. ### **8.2.6 Foundry-Based Contribution.** 8.2.6.1 Foundry-based WILPs may connect learners to Nexus Foundry and BuildGrid through quests, bounties, builds, micro-production, public-good software, data pipelines, dashboards, reports, Studio workflows, Marketplace objects, Registry records, Grid inputs, TRL notes, Campaign builds, National Portfolio builds, and handoff dependency builds. 8.2.6.2 Foundry-based WILPs shall define contribution scope, review gates, maintainer roles, support class, licensing terms, attribution, evidence records, iCRS linkage, micro-credential eligibility, correction pathway, and archive rule. 8.2.6.3 Foundry-based WILPs shall not create employment, procurement qualification, product certification, provider validation, warranty, deployment authorization, or execution. ### **8.2.7 Campaign-Based Mobilization Work.** 8.2.7.1 Campaign-based WILPs may involve learners in public-good mobilization, signatures, pledges, volunteer coordination, public-safe storytelling, translation, accessibility, trust and safety, campaign dashboards, public Reports, support ledgers, correction channels, and Nexus Universe preparation. 8.2.7.2 Campaign WILPs shall include public-safe communication rules, no-mandate notices, no-consent notices, fraud controls, volunteer boundary rules, sponsor controls, provider controls, data controls, youth protections, and correction channels. 8.2.7.3 Campaign work shall not create vote, mandate, public authority approval, donor commitment, finance commitment, community consent, employment, or execution authority. ### **8.2.8 National Working Group Practice.** 8.2.8.1 National Working Group WILPs may allow learners and contributors to participate in national challenge identification, skills mapping, evidence needs, National Portfolio preparation, public authority learning questions, DRI interpretation, safeguard review, Campaign preparation, Nexus Universe preparation, and lawful handoff literacy. 8.2.8.2 National Working Group WILPs shall be nationally routed and shall preserve role separation between learners, contributors, experts, public authorities, National Consortiums, National Companies, Project SPVs, providers, sponsors, and execution actors. 8.2.8.3 National Working Group participation shall not create public authority approval, national endorsement, procurement status, policy adoption, community consent, or execution authority. ### **8.2.9 Competence Cell Practice.** 8.2.9.1 Competence Cell WILPs may place learners in applied capability units focused on defined domains, such as data, AI, cyber, geospatial, WFEH-B, DRR, DRF, DRI, public-safe reporting, safeguards, software, Observatory, Studio, Grid, Reports, Campaigns, or handoff literacy. 8.2.9.2 Competence Cell WILPs shall include cell identity, cell scope, learner role, mentor role, contribution scope, evidence outputs, review gates, public-safe controls, safeguard controls, correction, and archive. 8.2.9.3 Competence Cell participation shall not create employment, professional license, reviewer authority beyond record, maintainer authority beyond record, public authority approval, procurement qualification, deployment authorization, or execution. ### **8.2.10 Public Authority Learning Placements.** 8.2.10.1 Public Authority Learning Placements may allow learners, public officials, public authority staff, students, researchers, and contributors to participate in structured learning environments involving public authority questions, policy learning, regulatory literacy, public-safe reporting, Studio exercises, readiness rooms, DRI interpretation, National Portfolio work, or Nexus Universe activities. 8.2.10.2 Such placements shall state that they are learning environments only unless a competent public authority separately records official action. They shall include public authority boundary notices, confidentiality rules, non-decision status, public-safe communication controls, and role separation. 8.2.10.3 Public Authority Learning Placements shall not create official action, public authority approval, procurement authority, public finance authority, regulatory authorization, emergency command, public warning authority, or public employment status by implication. ### **8.2.11 Risk Agency Shadowing and Supervised Practice.** 8.2.11.1 Risk Agency shadowing and supervised practice WILPs may allow learners to observe or participate in bounded risk advisory, resilience support, public-safe reporting support, capacity-building, cross-sphere translation, handoff support, or training contexts under supervision. 8.2.11.2 Such WILPs shall include reliance labels, advisory boundaries, conflict controls, client confidentiality, learner role limits, mentor supervision, public-safe output review, professional-license boundaries, finance and insurance boundaries, community-consent boundaries, and correction pathways. 8.2.11.3 Risk Agency WILPs shall not create professional license, advisory authority, investment advice authority, insurance advice authority, legal advice authority, public authority decision authority, client reliance, or execution authority. ### **8.2.12 Remote and Distributed WILPs.** 8.2.12.1 Remote and distributed WILPs may be used where learners participate through digital platforms, remote collaboration, low-bandwidth tools, asynchronous work, distributed teams, open-source workflows, data rooms, secure rooms, Studio environments, Foundry repositories, Campaign platforms, or National Node coordination. 8.2.12.2 Remote and distributed WILPs shall include identity and access controls, communication rules, time-zone expectations, workload limits, supervision cadence, documentation standards, secure collaboration rules, data protection, accessibility, digital wellbeing, harassment prevention, and correction channels. 8.2.12.3 Remote participation shall not reduce host responsibility, mentor responsibility, safety obligations, privacy obligations, or labor boundary discipline. *** ## **8.3 WILP Host Model** ### **8.3.1 Employer Hosts.** 8.3.1.1 Employer hosts may provide supervised work-learning environments, projects, mentors, practice settings, feedback, evidence verification, and exposure to occupational tasks. 8.3.1.2 Employer hosts shall define learner status, work scope, supervision, permitted tasks, prohibited tasks, safety rules, confidentiality requirements, data rules, AI and tool-use rules, compensation or support status where applicable, IP terms, evidence outputs, and complaint channels. 8.3.1.3 Employer hosting shall not create hiring commitment, endorsement, procurement preference, provider validation, professional certification, public authority approval, or execution authority by implication. ### **8.3.2 University Hosts.** 8.3.2.1 Universities and research institutions may host WILPs through labs, courses, practicums, research streams, clinics, studios, capstones, field schools, public-good projects, and Nexus-linked learning pathways. 8.3.2.2 University-hosted WILPs shall preserve academic governance, research ethics, data rights, human participant protections, student protections, accessibility, IP rules, publication rules, public-safe output controls, and correction obligations. 8.3.2.3 University hosting shall not convert SCF records into degree credits, academic awards, professional qualifications, or statutory credentials unless separately authorized by the competent institution. ### **8.3.3 Public Authority Learning Hosts.** 8.3.3.1 Public authorities may host or observe WILPs as learning, capacity-building, public-safe reporting, policy literacy, public authority learning, or National Portfolio contexts. 8.3.3.2 Public authority learning hosts shall maintain non-decision status unless official action is separately taken through proper authority. WILP learners shall not represent the public authority, issue statements on its behalf, make public decisions, access restricted data without authorization, or participate in official actions beyond their recorded role. 8.3.3.3 Public authority hosting shall not create public authority approval, public employment, statutory credential, procurement approval, public finance allocation, public warning, emergency command, or regulatory action by implication. ### **8.3.4 Community Hosts.** 8.3.4.1 Community hosts may support WILPs involving local knowledge, lived-risk knowledge, resilience priorities, accessibility needs, community engagement, public-safe reporting, field learning, Campaigns, or National Portfolio work. 8.3.4.2 Community-hosted WILPs shall be non-extractive, respectful, safeguard-reviewed, consent-aware, protected knowledge-sensitive, accessible, and correctionable. 8.3.4.3 Community hosting shall not be represented as community consent, community endorsement, representation authority, Indigenous authorization, protected knowledge permission, public authority approval, or deployment authorization. ### **8.3.5 Lab Hosts.** 8.3.5.1 Lab hosts may provide research, testing, experimentation, data analysis, simulation, model evaluation, prototyping, technical methods, and controlled practice environments. 8.3.5.2 Lab-hosted WILPs shall apply research ethics, data governance, AI-use controls, cyber controls, safety controls, dual-use review where applicable, public-safe publication rules, protected knowledge restrictions, and correction pathways. 8.3.5.3 Lab hosting shall not create approval, certification, deployment authorization, public authority decision, financeability, insurability, or execution. ### **8.3.6 Foundry Hosts.** 8.3.6.1 Foundry hosts may provide build environments, repositories, maintainer support, quests, bounties, micro-production tasks, review gates, contribution records, and public-good object routing. 8.3.6.2 Foundry-hosted WILPs shall apply maintainer governance, repository rules, contribution terms, licensing, security review, public-safe review, safeguard review where applicable, support-class rules, Registry routing, Marketplace routing, correction, and archive. 8.3.6.3 Foundry hosting shall not create employment, procurement qualification, product certification, provider validation, warranty, deployment authorization, or execution authority. ### **8.3.7 National Node Hosts.** 8.3.7.1 National Nodes may host WILPs connected to national skills needs, National Portfolios, National Working Groups, Competence Cells, Nexus Universe preparation, public authority learning, public-safe reporting, and lawful handoff literacy. 8.3.7.2 National Node hosts shall preserve national ownership, local context, language access, data sovereignty, protected knowledge controls, public authority boundaries, sponsor controls, provider controls, and national archive rules. 8.3.7.3 National Node hosting shall not create public authority approval, national endorsement, procurement qualification, employment status, financeability, insurability, community consent, deployment authorization, or execution. ### **8.3.8 Project SPV and National Company Interfaces.** 8.3.8.1 National Consortium Companies and Project SPVs may interface with WILPs as lawful downstream recipients, host environments, evidence users, handoff-context recipients, or practice partners where appropriate and separately governed. 8.3.8.2 Any interface with National Companies or Project SPVs shall preserve public-good stack and enterprise-stack separation. WILP participation shall not transfer public-good learners into enterprise execution without lawful arrangement, appropriate consent, labor compliance, IP clarity, confidentiality controls, data controls, safety controls, and boundary notices. 8.3.8.3 Project SPV or National Company interface shall not convert WILP outputs into procurement approval, investment readiness, financeability, insurability, public authority approval, deployment authorization, or execution by Nexus. ### **8.3.9 Sponsor-Supported Hosts.** 8.3.9.1 Sponsors may support WILPs through funding, scholarships, infrastructure, tools, venues, mentors, datasets, learning materials, or public-good support, subject to support-without-control rules. 8.3.9.2 Sponsor support shall not control learner selection, credential outcomes, assessment results, public display, curriculum content, Registry status, Marketplace visibility, procurement routing, National Portfolio priorities, public authority interpretation, or handoff recommendations. 8.3.9.3 Sponsor-supported WILPs shall include sponsor-boundary notices and conflict controls. ### **8.3.10 Host Boundary Rules.** 8.3.10.1 Host participation shall not create endorsement, certification, employment guarantee, procurement preference, provider validation, public authority approval, public finance allocation, insurance approval, investment readiness, community consent, deployment authorization, or execution authority. 8.3.10.2 Hosts shall not overclaim learner outputs, credential status, public authority participation, community participation, sponsor support, provider contribution, or Nexus affiliation. 8.3.10.3 Hosts shall comply with WILP governance, labor protections, safety controls, data controls, confidentiality rules, harassment prevention, accessibility duties, correction channels, and archive obligations within their role. *** ## **8.4 WILP Governance** ### **8.4.1 Learning Agreement.** 8.4.1.1 Every WILP shall be governed by a **Learning Agreement** or equivalent record that states the learner, host, mentor or supervisor, pathway, purpose, scope, duration, learning objectives, competency map, workplan, evidence outputs, review process, compensation or support status where applicable, data and confidentiality rules, safety rules, IP and attribution terms, public-safe output rules, grievance pathway, correction pathway, and boundary notices. 8.4.1.2 The Learning Agreement shall identify whether the WILP is unpaid learning, paid employment, stipend-supported learning, bounty-supported contribution, internship, apprenticeship, co-operative education, contracted work, volunteer contribution, public authority learning, or another lawful arrangement. 8.4.1.3 Learning Agreements shall be plain enough for learners to understand and precise enough for hosts, mentors, institutions, and reviewers to administer. ### **8.4.2 Scope and Workplan.** 8.4.2.1 Every WILP shall include a defined **Scope and Workplan** describing tasks, deliverables, permitted activities, prohibited activities, expected outputs, review gates, timelines, tools, data access, collaboration requirements, public-safe requirements, and evidence records. 8.4.2.2 Scope and Workplan records shall prevent role ambiguity, uncontrolled task expansion, disguised labor, unsafe work, unsupported fieldwork, excessive workload, data misuse, and execution overclaim. 8.4.2.3 Any material change to scope shall be recorded, reviewed, and approved by the relevant learner, mentor, host, and WILP steward where required. ### **8.4.3 Mentor Assignment.** 8.4.3.1 Every WILP shall assign at least one mentor, supervisor, faculty guide, host supervisor, maintainer, reviewer, or practice lead appropriate to the work scope and risk class. 8.4.3.2 Mentor records shall identify mentor role, qualifications or standing where relevant, supervision responsibilities, cadence, conflict status, safeguard obligations, youth protection obligations where applicable, and escalation duties. 8.4.3.3 Mentorship shall be active, not symbolic. A WILP without adequate mentorship, supervision, or review shall not be treated as properly governed. ### **8.4.4 Supervision Level.** 8.4.4.1 Each WILP shall state the required supervision level, including observation-only, guided practice, supervised contribution, independent contribution with review, maintainer-supervised contribution, field supervision, secure-room supervision, public authority learning supervision, or host-supervised practice. 8.4.4.2 Supervision level shall be proportionate to learner readiness, work risk, data sensitivity, AI-use risk, cyber risk, public-safe risk, safeguard risk, fieldwork risk, host context, and downstream relevance. 8.4.4.3 Learners shall not be assigned independent or safety-sensitive tasks beyond their demonstrated competence and recorded supervision level. ### **8.4.5 Health, Safety, and Safeguard Controls.** 8.4.5.1 WILPs shall apply health, safety, and safeguard controls appropriate to their environment, including physical safety, fieldwork safety, mental health and wellbeing, psychosocial safety, harassment prevention, discrimination prevention, trauma sensitivity, community safeguards, Indigenous protocols where applicable, youth safeguards, disability inclusion, humanitarian sensitivity, and protected knowledge controls. 8.4.5.2 Fieldwork, clinical practice, community engagement, humanitarian contexts, disaster contexts, infrastructure contexts, biosecurity-sensitive contexts, public health contexts, and sensitive geospatial contexts shall require heightened review. 8.4.5.3 WILP safety controls shall include stop-work, withdrawal, emergency contact, incident reporting, escalation, correction, and archive procedures. ### **8.4.6 Data and Confidentiality Controls.** 8.4.6.1 WILPs involving data, confidential information, public authority-sensitive information, employer information, community-sensitive information, Indigenous protocol-sensitive information where applicable, protected knowledge, health data, youth data, cyber-sensitive information, infrastructure-sensitive information, or geospatial-sensitive information shall include data and confidentiality controls. 8.4.6.2 Such controls shall include access permissions, need-to-know access, no-download rules where applicable, secure-room rules where applicable, data-use labels, AI-use labels, confidentiality obligations, output review, public-safe transformation, retention rules, deletion or sealing rules, and incident reporting. 8.4.6.3 Learners shall not be granted access to restricted data or confidential systems unless the access is necessary, authorized, supervised, logged, and governed. ### **8.4.7 AI and Tool Use Controls.** 8.4.7.1 WILPs shall define permitted and prohibited AI, software, collaboration tools, code tools, data tools, modeling tools, dashboards, cloud tools, secure-room tools, and communication tools. 8.4.7.2 AI and tool-use controls shall identify whether AI may be used for learning, drafting, summarization, translation, coding, classification, evaluation, review support, or other purposes, and shall state human review obligations, data restrictions, prompt restrictions, output restrictions, and incident pathways. 8.4.7.3 AI shall not be used to bypass learner work, fabricate evidence, expose confidential data, generate unreviewed public outputs, make high-stakes decisions, or create misleading competency claims. ### **8.4.8 Fair Work and Anti-Exploitation Controls.** 8.4.8.1 WILPs shall include fair work and anti-exploitation controls to prevent unpaid substitution of regular labor, excessive workload, coercive participation, hidden employment, unclear compensation, unfair IP extraction, unsafe work, harassment, discrimination, or retaliation. 8.4.8.2 Stipends, honoraria, bounties, expenses, wages, or other support shall be clearly described where applicable. Absence of compensation shall not permit host exploitation or replacement of paid work. 8.4.8.3 Learners shall have access to exit, complaint, correction, and escalation channels without retaliation. ### **8.4.9 Accessibility and Inclusion Controls.** 8.4.9.1 WILPs shall be designed for accessibility and inclusion, including reasonable accommodations, accessible materials, accessible digital platforms, language access, flexible pacing where feasible, remote participation where appropriate, disability inclusion, gender equity, youth safeguards, rural and remote access, and culturally respectful participation. 8.4.9.2 Accessibility needs shall be handled as sensitive profile information and shall not be used to exclude, stigmatize, or reduce opportunity. 8.4.9.3 WILP hosts and stewards shall correct access barriers where identified. ### **8.4.10 Correction and Grievance Controls.** 8.4.10.1 WILPs shall include correction and grievance controls for inaccurate records, unsafe conditions, harassment, discrimination, excessive workload, disguised labor, data misuse, AI misuse, public-safe overclaim, safeguard breach, host misconduct, mentor misconduct, assessment concerns, credential concerns, and retaliation. 8.4.10.2 Grievance mechanisms shall be accessible, documented, non-retaliatory, timely, and proportionate. They shall allow escalation where safety, youth protection, protected knowledge, harassment, discrimination, data breach, public authority overclaim, or labor misclassification is involved. 8.4.10.3 Correction outcomes may include record correction, scope change, mentor change, host review, suspension, withdrawal, reclassification, compensation review where applicable, public-safe notice, credential correction, archive, or referral to competent authorities. *** ## **8.5 Work Product and Evidence** ### **8.5.1 Portfolio Artifacts.** 8.5.1.1 WILPs shall produce **Portfolio Artifacts** where appropriate, including work samples, reflections, reports, data objects, software contributions, dashboards, public-safe summaries, Studio outputs, Campaign materials, review notes, mentor notes, host verification, and correction records. 8.5.1.2 Portfolio Artifacts shall be classified by visibility, evidence value, privacy status, data-use label, AI-use label, public-safe status, rights status, review status, and archive rule. 8.5.1.3 Portfolio display shall not create employment verification, endorsement, procurement qualification, public authority approval, professional certification, or deployment authorization. ### **8.5.2 Reports.** 8.5.2.1 WILP Reports may include learning reports, field reports, technical notes, public-safe summaries, data notes, Studio notes, Campaign reports, DRI notes, Observatory summaries, National Portfolio summaries, or handoff literacy notes. 8.5.2.2 Reports shall follow public-safe reporting controls, including no-warning, no-approval, no-finance, no-procurement, no-certification, no-consent, and no-execution language where applicable. 8.5.2.3 A WILP Report shall not be public authority action, official report, certification, finance opinion, procurement recommendation, community consent, or execution instruction by default. ### **8.5.3 Data Objects.** 8.5.3.1 WILP Data Objects may include metadata, data dictionaries, codebooks, cleaned data, public-safe data summaries, synthetic data, dashboards, lineage records, data quality notes, DRI indicator inputs, Observatory inputs, and National Portfolio data notes. 8.5.3.2 Data Objects shall be governed by data classification, rights review, data-use labels, AI-use labels, lineage, access controls, public-safe transformation, sensitive data restrictions, correction, and archive. 8.5.3.3 Data Object creation shall not create data rights, unrestricted access, public authority records, deployment authorization, or execution. ### **8.5.4 Software Contributions.** 8.5.4.1 WILP Software Contributions may include code, documentation, tests, notebooks, APIs, SDKs, connectors, adapters, dashboards, configuration files, infrastructure-as-code templates, reproducibility packages, and security or accessibility improvements. 8.5.4.2 Software Contributions shall be governed by repository rules, contribution terms, license review, code review, dependency review, secret scanning, security review, SBOM records where applicable, public-safe documentation, maintainer review, correction, and archive. 8.5.4.3 Software contribution shall not create warranty, certification, security approval, production approval, procurement recommendation, provider validation, deployment authorization, or execution. ### **8.5.5 Studio Outputs.** 8.5.5.1 WILP Studio Outputs may include dashboard exercises, simulation results, digital twin notes, scenario interpretations, AI output reviews, readiness-room notes, public authority learning summaries, capital-reader literacy notes, insurance-reader literacy notes, and handoff demonstration notes. 8.5.5.2 Studio Outputs shall include assumptions, model basis, data basis, uncertainty, confidence where applicable, limitations, output review, no-decision status, and public-safe interpretation. 8.5.5.3 Studio Outputs shall not constitute forecast certainty, public authority decision, finance approval, insurance approval, deployment authorization, operational command, or execution. ### **8.5.6 Campaign Outputs.** 8.5.6.1 WILP Campaign Outputs may include campaign summaries, public-safe storytelling, volunteer coordination records, signature or pledge summaries, support ledger inputs, translation, accessibility outputs, trust and safety notes, public Reports inputs, and Nexus Universe preparation records. 8.5.6.2 Campaign Outputs shall include no-mandate, no-vote, no-finance, no-consent, no-public-authority, no-execution, and sponsor-boundary notices where applicable. 8.5.6.3 Campaign Outputs shall not create mandate, public authority approval, donor commitment, community consent, employment, or execution. ### **8.5.7 Public-Safe Summaries.** 8.5.7.1 WILP Public-Safe Summaries shall translate learner work into safe, bounded, non-overclaiming, publicly usable summaries where appropriate. 8.5.7.2 Public-Safe Summaries shall remove or restrict protected knowledge, sensitive data, sensitive geospatial detail, confidential host information, youth information, unsafe cyber detail, unverified claims, and overclaiming language. 8.5.7.3 Public-Safe Summaries shall not be public warnings, official approvals, finance recommendations, procurement recommendations, certifications, consents, deployment authorizations, or execution instructions. ### **8.5.8 Review Notes.** 8.5.8.1 WILP Review Notes shall document review of learner outputs, evidence sufficiency, competency mapping, public-safe status, safeguard status, data status, AI-use status, cyber status, privacy status, quality status, and correction requirements. 8.5.8.2 Review Notes shall state reviewer role, scope, criteria, date, conflicts, limitations, outcome, and correction pathway. 8.5.8.3 Review Notes shall not create certification, public authority approval, professional license, procurement approval, endorsement, or deployment authorization by default. ### **8.5.9 Mentor Verification.** 8.5.9.1 Mentor Verification shall document mentor observations, learner progression, supervision, practice quality, reflection quality, evidence completion, strengths, development needs, and readiness for next pathway. 8.5.9.2 Mentor Verification shall be bounded to mentor role and supervision context. It shall not create employment verification, professional qualification, official certification, public authority approval, or endorsement. 8.5.9.3 Mentor Verification may support ILA records, micro-credential eligibility, WILP completion, portfolio evidence, and progression decisions within SCF. ### **8.5.10 Host Verification.** 8.5.10.1 Host Verification shall document host-confirmed participation, task completion, work product submission, workplace learning, attendance where relevant, safety compliance where relevant, and host feedback within scope. 8.5.10.2 Host Verification shall state whether the host is an employer, university, public authority learning host, community host, lab host, Foundry host, National Node host, sponsor-supported host, National Company, Project SPV, or other lawful participant. 8.5.10.3 Host Verification shall not create hiring commitment, employment status, endorsement, procurement approval, professional qualification, public authority approval, deployment authorization, or execution by default. *** ## **8.6 Labor and Worker Protections** ### **8.6.1 No Disguised Employment.** 8.6.1.1 WILPs shall not be used to disguise employment, avoid labor obligations, misclassify workers, avoid wages, avoid benefits, avoid worker protections, or create unpaid operational capacity for hosts. 8.6.1.2 Indicators of disguised employment may include routine substitution of paid staff, excessive hours, production dependency, lack of learning objectives, lack of supervision, host economic control, mandatory outputs unrelated to learning, absence of feedback, indefinite duration, retaliatory discipline, and lack of exit rights. 8.6.1.3 Where disguised employment risk is identified, the WILP shall be paused, corrected, re-scoped, compensated where required, transferred into a lawful employment or contract arrangement, or terminated. ### **8.6.2 No Unpaid Substitution of Regular Labor.** 8.6.2.1 WILPs shall not permit unpaid learners to replace regular employees, contractors, public servants, operators, professional staff, field staff, emergency staff, technical staff, or administrative staff. 8.6.2.2 Public-good contribution may create valuable outputs, but such value shall be governed by learning purpose, supervision, evidence, contribution recognition, public-good use, and labor boundary controls. 8.6.2.3 Hosts shall not rely on unpaid WILP participation for mission-critical, safety-critical, revenue-critical, regulatory, procurement, emergency, operational, or service-level obligations. ### **8.6.3 Stipend and Bounty Controls.** 8.6.3.1 Where WILPs include stipends, honoraria, bounties, expenses, rewards, or other support, the terms shall be recorded clearly before work begins. 8.6.3.2 Stipend and bounty records shall state eligibility, scope, expected outputs, review criteria, payment or reward condition where lawful, tax or reporting responsibility where applicable, timing, non-employment status where applicable, dispute pathway, and correction process. 8.6.3.3 Stipends and bounties shall not be used to evade employment law, exploit learners, impose excessive work, create unclear compensation, or imply equity, token, finance, procurement, or employment rights by default. ### **8.6.4 Hours, Workload, and Wellbeing Controls.** 8.6.4.1 WILPs shall include reasonable expectations for hours, workload, deadlines, communication cadence, rest, wellbeing, and flexibility. 8.6.4.2 Workload shall be proportionate to learning goals, learner status, supervision level, compensation or support status, academic obligations, employment obligations, caregiving responsibilities, disability accommodations, youth status, field conditions, and wellbeing considerations. 8.6.4.3 Excessive workload, persistent urgency, coercive availability expectations, unpaid overtime pressure, unclear deliverables, or unmanaged stress shall trigger review and correction. ### **8.6.5 Harassment and Abuse Prevention.** 8.6.5.1 WILPs shall prohibit harassment, discrimination, bullying, retaliation, coercion, intimidation, exploitation, abuse of authority, sexual harassment, online abuse, discriminatory exclusion, and hostile learning or work environments. 8.6.5.2 Hosts, mentors, supervisors, reviewers, learners, contributors, sponsors, providers, public authority participants, and community participants shall be subject to conduct rules appropriate to their role. 8.6.5.3 WILP governance shall include safe reporting channels, confidentiality where appropriate, anti-retaliation protections, escalation, interim measures, correction, and archive of incident handling. ### **8.6.6 Occupational Health and Safety.** 8.6.6.1 WILPs shall apply occupational health and safety controls appropriate to the environment, including physical safety, lab safety, field safety, ergonomic safety, digital safety, psychosocial safety, travel safety, emergency procedures, incident reporting, and supervision. 8.6.6.2 Safety-critical tasks shall require appropriate training, supervision, equipment, permissions, insurance where applicable, and competent host responsibility. 8.6.6.3 Learners shall have the right to refuse unsafe work within applicable law, institutional policy, and WILP governance. ### **8.6.7 Fieldwork Safety.** 8.6.7.1 Fieldwork WILPs shall require field risk assessment, site permissions, local context review, travel safety, emergency contacts, communications plan, weather and hazard awareness, community protocol review, health precautions, data security, geospatial sensitivity, and exit procedures. 8.6.7.2 Fieldwork in disaster, humanitarian, conflict-affected, climate-affected, infrastructure-sensitive, public health, biosecurity-sensitive, or community-sensitive contexts shall require heightened review. 8.6.7.3 Fieldwork learning shall not imply emergency response authority, public authority action, community consent, media authority, or operational deployment. ### **8.6.8 Youth Learner Protections.** 8.6.8.1 Youth learner WILPs shall apply age-appropriate design, guardian or institutional permissions where required, restricted working hours, restricted task types, mentor screening where appropriate, safe communication rules, restricted public display, and heightened privacy controls. 8.6.8.2 Youth learners shall not be placed in unsafe, exploitative, adult-only, high-risk, unsupervised, confidential, field-risk, or psychologically harmful environments. 8.6.8.3 Youth participation shall be treated as learning and development, not labor substitution, public authority participation, or execution. ### **8.6.9 Data and Surveillance Limits.** 8.6.9.1 WILPs shall limit data collection, monitoring, analytics, and surveillance to what is necessary for learning, safety, supervision, evidence, credentialing, security, and compliance. 8.6.9.2 Learners shall not be subjected to disproportionate productivity surveillance, hidden monitoring, biometric tracking, intrusive behavioral profiling, automated ranking, or algorithmic management by default. 8.6.9.3 Monitoring tools, AI analytics, platform logs, and learning analytics shall be disclosed where required, purpose-limited, reviewed, and correctable. ### **8.6.10 Exit, Complaint, and Correction Channels.** 8.6.10.1 WILPs shall include clear exit channels, complaint channels, correction channels, and escalation routes. 8.6.10.2 Learners may exit or request modification of a WILP where safety, harassment, discrimination, workload, exploitation, data misuse, confidentiality, accessibility, health, youth protection, safeguard, or role-boundary concerns arise. 8.6.10.3 Exit from a WILP shall not automatically penalize the learner. Records shall distinguish incomplete participation, justified withdrawal, host failure, safety withdrawal, correction withdrawal, and non-continuation. *** ## **8.7 WILP Boundary Rules** ### **8.7.1 WILP Is Not Employment by Default.** 8.7.1.1 A WILP shall not create employment, contractor status, wages, benefits, tax status, immigration status, work authorization, union status, public employment status, or future work entitlement by default. 8.7.1.2 Where employment or another regulated arrangement exists, it shall arise from a separate lawful agreement or statutory status and shall be recorded accurately. ### **8.7.2 WILP Completion Is Not Hiring Commitment.** 8.7.2.1 Completion of a WILP shall not require or imply that a host, employer, National Node, National Consortium, sponsor, provider, public authority, National Company, Project SPV, or downstream actor will hire, contract, promote, interview, sponsor, fund, procure, or continue with the learner. 8.7.2.2 WILP completion may support evidence of learning and competence, but hiring and contracting remain separate decisions. ### **8.7.3 Host Participation Is Not Endorsement.** 8.7.3.1 Host participation shall not be represented as endorsement of SCF, Nexus, a learner, a credential, a work product, a provider, a sponsor, a National Portfolio, a Campaign, a public authority position, or a downstream project unless expressly and separately recorded. 8.7.3.2 Host verification shall remain limited to the host’s recorded observations and scope. ### **8.7.4 Work Product Is Not Deployment Authorization.** 8.7.4.1 WILP work product shall not authorize deployment, operations, procurement, production use, public infrastructure action, public health action, emergency action, field implementation, data release, model release, or enterprise execution by default. 8.7.4.2 Work product may be reviewed, corrected, archived, routed, published in public-safe form, listed, registered, or transferred as handoff context where appropriate. ### **8.7.5 Public Authority WILP Is Not Public Authority Decision.** 8.7.5.1 A WILP involving a public authority, public official, public authority learning room, public authority host, public dataset, public policy question, or public authority learning summary shall not create official action, approval, procurement, funding, public warning, emergency command, regulatory determination, permit, license, or public authority credential by implication. 8.7.5.2 Official public authority action must occur outside WILP through competent legal channels. ### **8.7.6 Community WILP Is Not Consent.** 8.7.6.1 A WILP involving communities, Indigenous participants where applicable, civil society, place-based actors, youth, public-interest actors, humanitarian actors, or affected stakeholders shall not create community consent, Indigenous consent, protected knowledge permission, representation authority, public endorsement, social license, or deployment authorization by implication. 8.7.6.2 Consent, where required, must be separately and lawfully obtained, recorded, respected, and governed under applicable protocols. *** ## **8.8 Final Part VIII Operating Statement** 8.8.1 WILPs shall be the practice bridge of SCF. They shall convert learning into supervised, evidence-bearing, safe, fair, and correctionable practice while preserving learner dignity, labor protections, public-good discipline, role separation, data safeguards, public-safe communication, and no-conversion boundaries. 8.8.2 WILPs shall connect Nexus Academy, Risk Academy, Nexus Foundry, Nexus Campaigns, Nexus Labs, Nexus Reports, Nexus Marketplace, Nexus Registry, Nexus Studio, Nexus Grid, Nexus Universe, National Portfolios, National Working Groups, Competence Cells, Risk Agency pathways, National Nodes, hosts, employers, universities, communities, public authority learning environments, and lawful downstream actors through structured learning agreements, workplans, supervision, evidence, review, correction, and archive. 8.8.3 WILPs shall produce portfolio artifacts, Reports, data objects, software contributions, Studio outputs, Campaign outputs, public-safe summaries, review notes, mentor verification, host verification, ILA records, micro-credential evidence, iCRS records, Registry linkages where applicable, Marketplace display where appropriate, National Portfolio inputs, and handoff-context notes. Such outputs shall remain bounded to their recorded scope and shall not become authority by implication. 8.8.4 WILPs shall never be used as disguised labor, unpaid substitution of regular work, hidden employment, unsafe fieldwork, exploitative contribution, uncontrolled data access, sponsor capture, provider validation, public authority substitution, community consent overclaim, or enterprise execution. Where a WILP crosses into employment, contracting, regulated apprenticeship, public authority activity, procurement, deployment, or execution, the appropriate lawful framework must be separately used and recorded. 8.8.5 The final rule of Part VIII is that WILPs make learning practical, contribution visible, competence evidence-bearing, and national capability stronger; they do not create employment, hiring commitments, professional licenses, procurement qualifications, public authority approvals, community consent, deployment authorization, financeability, insurability, or execution by implication. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.therisk.global/organization/operations/frameworks/sustainable-competency-framework-scf/viii.-pathways.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.