# X. COMPETENCE ## **10.1 Competence Cells Defined** ### **10.1.1 Competence Cells as Applied Capability Units.** 10.1.1.1 **Competence Cells** shall mean bounded, role-separated, evidence-bearing, domain-specific, nationally routable, and correctionable applied capability units within SCF through which learners, workers, career changers, mentors, reviewers, maintainers, experts, faculty, public authority learning participants, community participants, and contributors organize around defined competency domains, work objects, public-good outputs, learning pathways, National Portfolio needs, Nexus Foundry tasks, Nexus Campaign needs, Nexus Studio workflows, Nexus Reports outputs, Nexus Registry records, Nexus Marketplace listings, Nexus Grid inputs, Nexus Universe preparation, and lawful handoff-context requirements. 10.1.1.2 Competence Cells shall operate as capability formation infrastructure, not as default employers, professional licensing bodies, certifiers, public authorities, procurement bodies, project developers, contractors, funders, insurers, investment vehicles, standards authorities, or execution vehicles. A Competence Cell may assemble, train, coordinate, review, produce, test, document, translate, publish, and correct public-good outputs within scope, but it shall not create authority beyond its recorded mandate. 10.1.1.3 Each Competence Cell shall have a defined identity, scope, domain, host or steward where applicable, relationship to SCF, relationship to National Working Groups, relationship to Nexus Academy and Risk Academy, relationship to Nexus Foundry and BuildGrid where applicable, relationship to DICE, GRIx, DRI, Nexus Observatory, Nexus Studio, Nexus Reports, Nexus Marketplace, Nexus Registry, Nexus Grid, Nexus Universe, and lawful handoff pathways where applicable. 10.1.1.4 Competence Cell formation shall be evidence-based. A cell may be formed where there is a documented competency need, National Skills Map gap, National Portfolio requirement, Campaign mobilization need, Nexus Universe preparation need, Foundry backlog need, DRI or Observatory need, public authority learning need, WFEH-B or DRR/DRF/DRI need, technology-domain need, public-safe reporting need, safeguard need, or lawful handoff-context need. ### **10.1.2 Competence Cells as National Capacity Engines.** 10.1.2.1 Competence Cells shall function as **National Capacity Engines** by converting skills gaps, labor-market intelligence, learning pathways, public-good contribution, WILPs, Micro-Credentials, iCRS records, National Working Group priorities, and National Portfolio requirements into applied capability formation. 10.1.2.2 National capacity formation through Competence Cells may include:\ (a) identifying competency gaps;\ (b) preparing learners and contributors;\ (c) supporting WILP practice;\ (d) producing public-good outputs;\ (e) reviewing work products;\ (f) supporting National Portfolio evidence;\ (g) preparing Nexus Universe participation;\ (h) strengthening public authority learning records;\ (i) supporting public-safe reporting;\ (j) supporting lawful handoff literacy;\ (k) preserving correction and archive. 10.1.2.3 Competence Cells shall be nationally grounded and context-aware. They shall respect national ownership, local language, local institutions, data sovereignty, public authority boundaries, sector needs, community safeguards, Indigenous protocols where applicable, accessibility needs, labor-market conditions, and lawful implementation pathways. 10.1.2.4 Competence Cells shall not be used to bypass national institutions, replace education systems, replace employers, replace public authorities, override professional bodies, substitute for unions or worker organizations, or create execution capacity by implication. ### **10.1.3 Competence Cells as Foundry and Academy Bridges.** 10.1.3.1 Competence Cells shall operate as bridges between learning and production by connecting Nexus Academy, Risk Academy, SCF competency maps, ILA records, WILPs, Micro-Credentials, iCRS recognition, Nexus Foundry, BuildGrid, quests, bounties, builds, maintainers, review gates, and public-good production. 10.1.3.2 Through the Academy interface, a Competence Cell may identify learning needs, propose learning objects, test learning pathways, support learner cohorts, mentor WILPs, review learning evidence, develop public-safe learning materials, and route learners toward contribution pathways. 10.1.3.3 Through the Foundry interface, a Competence Cell may contribute to quests, bounties, builds, data pipelines, software objects, dashboards, Studio workflows, Reports, Marketplace objects, Registry records, Grid inputs, TRL evidence notes, National Portfolio objects, Campaign objects, and handoff dependency notes. 10.1.3.4 Competence Cell work shall remain public-good production and learning support unless separately transferred into a lawful employment, contract, procurement, public authority, National Company, Project SPV, or other execution arrangement. ### **10.1.4 Competence Cells as DICE / GRIx / DRI / Observatory Work Units.** 10.1.4.1 Competence Cells may function as work units for DICE, GRIx, DRI, and Nexus Observatory where the cell has a defined data, ontology, risk-intelligence, observability, geospatial, indicator, dashboard, public-safe reporting, or national signal-processing scope. 10.1.4.2 DICE-related Competence Cells may support data stewardship, metadata creation, data dictionaries, schemas, data quality review, public-safe transformation, rights review, data-use labels, AI-use labels, secure-room workflows, compute-to-data literacy, and archive. 10.1.4.3 GRIx-related Competence Cells may support risk ontology, controlled vocabulary, taxonomy mapping, WFEH-B categories, DRR/DRF/DRI categories, systems-risk categories, safeguard categories, public authority boundary categories, finance and insurance boundary categories, and handoff dependency categories. 10.1.4.4 DRI-related Competence Cells may support indicator records, signal interpretation, uncertainty labels, confidence labels, hotspot records, multi-hazard records, cascade records, public-safe intelligence summaries, dashboards, correction, and archive. 10.1.4.5 Observatory-related Competence Cells may support observability methods, sensor signals, edge signals, geospatial records, Earth observation records, digital twin needs, degraded-mode awareness, public-safe Observatory outputs, National Dense Nexus Core profiles, and Nexus Universe preparation. 10.1.4.6 No Competence Cell shall convert DICE, GRIx, DRI, or Observatory work into data rights, legal classification, public warning, official map, surveillance authority, public authority decision, insurance score, investment signal, or emergency command by implication. ### **10.1.5 Competence Cells as Nexus Universe Preparation Units.** 10.1.5.1 Competence Cells shall support Nexus Universe preparation by converting year-round learning, WILPs, Campaigns, Foundry work, National Portfolio needs, public authority learning questions, public-safe reporting needs, and readiness-room questions into prepared arena inputs, room materials, build demonstrations, Reports, Registry updates, Marketplace listings, Studio workflows, Grid inputs, TRL notes, and continuation records. 10.1.5.2 Nexus Universe preparation through Competence Cells may include:\ (a) preparing national competency portfolios;\ (b) preparing challenge briefs;\ (c) preparing public-safe summaries;\ (d) preparing Foundry build records;\ (e) preparing Studio demonstrations;\ (f) preparing DRI and Observatory summaries;\ (g) preparing Campaign evidence;\ (h) preparing public authority learning records;\ (i) preparing readiness questions;\ (j) preparing handoff dependency notes;\ (k) preparing correction and archive materials. 10.1.5.3 Competence Cell participation in Nexus Universe shall not create endorsement, public authority approval, procurement status, financeability, insurance approval, certification, deployment authorization, community consent, or execution authority. ### **10.1.6 Competence Cells as Handoff Context Producers.** 10.1.6.1 Competence Cells may produce **Handoff Context** by documenting competency evidence, learning records, public-good outputs, technical notes, data context, method context, Studio context, Grid and TRL context, public-safe status, safeguard status, public authority dependencies, legal dependencies, finance and insurance questions, procurement boundaries, provider-neutrality notes, sponsor-boundary notes, recipient responsibilities, and correction pathways. 10.1.6.2 Handoff context produced by Competence Cells shall be routed as dependency information and evidence context only. It shall not transfer authority, make recommendations by default, create procurement preference, certify readiness, create financeability, create insurability, authorize deployment, or initiate execution. 10.1.6.3 Lawful downstream recipients, including National Consortium Companies, Project SPVs, public authorities, providers, operators, contractors, universities, donors, funders, insurers, and other competent actors, shall remain responsible for independent diligence, legal authority, safety review, procurement processes, finance processes, insurance processes, community protocols, and implementation decisions. ### **10.1.7 Competence Cells Without Execution by Default.** 10.1.7.1 Competence Cells shall not execute projects by default. They may learn, map, build, review, test, document, report, prepare, support, correct, and route, but they shall not operate infrastructure, issue public warnings, command emergencies, deploy systems, procure vendors, approve projects, provide regulated finance or insurance, certify products, represent public authorities, grant community consent, or act as implementation vehicles unless separately and lawfully authorized outside default SCF. 10.1.7.2 Competence Cell outputs shall include boundary labels where necessary, including no-certification, no-employment, no-procurement, no-finance, no-insurance, no-public-authority, no-consent, no-deployment, no-execution, no-warranty, no-endorsement, and no-reliance notices. 10.1.7.3 Where a Competence Cell’s work begins to cross into execution, procurement, employment, public authority action, regulated advice, professional practice, field deployment, or operational command, the work shall be paused, reclassified, escalated, transferred to competent lawful actors, or corrected. *** ## **10.2 National Working Groups** ### **10.2.1 Formation.** 10.2.1.1 **National Working Groups** shall be formed as nationally routed, public-good, role-separated, evidence-bearing, and correctionable working bodies within the SCF and broader Nexus architecture to identify competency needs, support National Skills Maps, review labor-market intelligence, design learning pathways, coordinate WILPs, support Competence Cells, prepare National Portfolio inputs, and prepare Nexus Universe participation. 10.2.1.2 A National Working Group may be formed by or through the relevant National Nexus Consortium, National Council, Helix Council, National Node, Nexus Academy pathway, Risk Academy pathway, National Portfolio process, Campaign process, Foundry process, public authority learning process, or other approved public-good formation pathway. 10.2.1.3 Formation records shall identify:\ (a) national context;\ (b) convening pathway;\ (c) scope and mandate;\ (d) chair or facilitator where applicable;\ (e) participating institutions;\ (f) learner and worker participation rules;\ (g) mentor and reviewer roles;\ (h) Competence Cell relationships;\ (i) data and confidentiality rules;\ (j) public authority boundary;\ (k) sponsor and provider boundary;\ (l) outputs;\ (m) correction and archive pathway. 10.2.1.4 National Working Group formation shall not create public authority approval, national endorsement, procurement status, employment status, professional credentialing authority, community consent, financeability, insurance approval, project authorization, or execution authority. ### **10.2.2 Competency Needs Identification.** 10.2.2.1 National Working Groups shall identify competency needs by examining National Portfolio priorities, labor-market signals, employer demand, public authority learning questions, community needs, disaster-risk conditions, WFEH-B vulnerabilities, technology readiness gaps, workforce transition needs, public-safe reporting needs, safeguard requirements, Nexus Universe preparation needs, and lawful handoff dependencies. 10.2.2.2 Competency needs shall be recorded as competency need records, skills gap notes, pathway proposals, WILP needs, Micro-Credential needs, Competence Cell formation needs, Academy pathway needs, Risk Academy pathway needs, Foundry task needs, and National Portfolio capability inputs. 10.2.2.3 Competency needs identification shall avoid deficit framing that blames individuals or communities for structural gaps. Skills gaps shall be interpreted as system signals involving education, access, infrastructure, employer demand, digital divide, language, disability access, gender equity, rural access, labor conditions, migration, public authority capacity, and economic transition. 10.2.2.4 Competency needs records shall not be used as individual rankings, worker scoring, country ranking, hiring decisions, wage promises, public authority determinations, procurement decisions, or finance signals by default. ### **10.2.3 National Skills Mapping.** 10.2.3.1 National Working Groups shall support **National Skills Mapping** by mapping occupations, tasks, competencies, learning pathways, WILPs, Micro-Credentials, hosts, mentors, reviewers, Competence Cells, public authority learning needs, National Portfolio priorities, and labor-market transition pathways. 10.2.3.2 National Skills Maps may include:\ (a) occupation and task profiles;\ (b) competency families;\ (c) skills taxonomies;\ (d) digital, AI, cyber, data, geospatial, WFEH-B, DRR, DRF, DRI, public-safe reporting, safeguard, and handoff literacy clusters;\ (e) learner pipelines;\ (f) workforce transition pools;\ (g) host maps;\ (h) mentor maps;\ (i) reviewer maps;\ (j) Competence Cell maps;\ (k) National Portfolio capability maps. 10.2.3.3 National Skills Maps shall use recognized reference mappings where appropriate, including competency taxonomies, occupation taxonomies, skills classification systems, education outcomes frameworks, professional-body references, and public authority learning references, while preserving non-equivalence by default. 10.2.3.4 National Skills Maps shall not certify national competence, rank countries, approve curricula, replace labor statistics, guarantee employment, create procurement eligibility, or create public authority action. ### **10.2.4 Labor-Market Intelligence Review.** 10.2.4.1 National Working Groups shall review labor-market intelligence relevant to national capability formation, including official labor statistics, public employment service data, job postings, employer surveys, sector body signals, education completion data, wage and vacancy data, shortage data, informal work signals, gig work signals, care work signals, humanitarian work signals, migration and diaspora signals, and Nexus contribution signals. 10.2.4.2 Labor-market intelligence review shall include human review of AI-supported analysis and shall identify uncertainty, coverage gaps, source limits, geographic bias, language bias, informal economy limits, digital divide effects, credential inflation, underemployment, job quality risks, automation exposure, augmentation opportunities, green transition needs, and public-good capability gaps. 10.2.4.3 Labor-market intelligence outputs shall be public-safe and non-overclaiming. They shall state limitations and shall not be treated as forecast certainty, employer commitment, wage guarantee, hiring guarantee, public authority decision, procurement signal, or finance signal. ### **10.2.5 Academy Pathway Design.** 10.2.5.1 National Working Groups may design or recommend Academy and Risk Academy pathways responsive to national competency needs, including foundational learning, technical learning, public-good software learning, data and AI learning, cyber and privacy learning, WFEH-B learning, DRR/DRF/DRI learning, public-safe reporting learning, safeguard learning, public authority learning, and lawful handoff literacy. 10.2.5.2 Academy pathway design shall identify target competencies, learner profiles, entry requirements, accessibility needs, language needs, learning objects, WILP connections, Micro-Credential options, mentor requirements, review criteria, AI-use rules, data rules, public-safe requirements, and correction pathways. 10.2.5.3 National Working Group pathway design shall not override universities, TVET authorities, schools, professional bodies, employers, public authorities, credential authorities, or regulators. External adoption must occur through competent institutions and lawful processes. ### **10.2.6 WILP and Host Mapping.** 10.2.6.1 National Working Groups shall support WILP and host mapping by identifying appropriate employer hosts, university hosts, public authority learning hosts, community hosts, lab hosts, Foundry hosts, National Node hosts, sponsor-supported hosts, National Company interfaces, Project SPV interfaces, mentors, supervisors, field sites, Studio environments, secure rooms, and data rooms. 10.2.6.2 WILP and host mapping shall include fair work review, anti-exploitation controls, learner safety, youth protection, accessibility, workload expectations, data and confidentiality controls, AI and tool-use controls, IP and attribution terms, public-safe output rules, grievance channels, and correction. 10.2.6.3 Host mapping shall not create host endorsement, hiring commitment, procurement status, public authority approval, project approval, community consent, or execution authority. ### **10.2.7 National Portfolio Inputs.** 10.2.7.1 National Working Groups shall prepare National Portfolio inputs by translating competency needs, skills maps, labor-market intelligence, WILP records, Competence Cell outputs, public authority learning questions, Campaign signals, Foundry outputs, DRI signals, Observatory signals, safeguard records, and public-safe reporting needs into National Portfolio capability records. 10.2.7.2 National Portfolio inputs may include:\ (a) national capability gap records;\ (b) skills map summaries;\ (c) learning pathway recommendations;\ (d) Competence Cell formation notes;\ (e) WILP host maps;\ (f) public authority learning notes;\ (g) Nexus Universe preparation notes;\ (h) handoff literacy notes;\ (i) support needs;\ (j) correction and archive records. 10.2.7.3 National Portfolio inputs shall not be country rankings, public authority decisions, procurement plans, investment recommendations, insurance recommendations, workforce guarantees, or execution plans by default. ### **10.2.8 Nexus Universe Preparation.** 10.2.8.1 National Working Groups shall prepare Nexus Universe participation by coordinating national competency inputs, Competence Cell outputs, WILP outputs, Academy outputs, Risk Academy outputs, Campaign outputs, Foundry outputs, public-safe Reports, Registry updates, Marketplace listings, Studio workflows, Grid inputs, TRL evidence notes, public authority learning records, and readiness-room questions. 10.2.8.2 Nexus Universe preparation shall include public-safe language, boundary notices, contribution records, support records, sponsor and provider controls, protected knowledge review, accessibility review, translation review, correction pathways, and post-cycle continuation planning. 10.2.8.3 Nexus Universe preparation shall not imply endorsement, public authority approval, procurement status, financeability, insurance approval, certification, community consent, deployment authorization, or execution. ### **10.2.9 Correction and Archive.** 10.2.9.1 National Working Groups shall maintain correction and archive discipline for competency needs, skills maps, labor-market intelligence, learning pathway designs, WILP maps, host maps, Competence Cell records, National Portfolio inputs, Nexus Universe preparation records, and public-safe outputs. 10.2.9.2 Correction triggers may include outdated skills data, inaccurate labor-market interpretation, incorrect competency mapping, inequitable access, misleading pathway claims, host boundary issue, WILP exploitation risk, credential overclaim, public authority overclaim, sponsor control, provider validation, data issue, privacy issue, safeguard issue, protected knowledge issue, or public display error. 10.2.9.3 Archive shall distinguish current, historical, superseded, corrected, withdrawn, suspended, non-continuing, and archived records. *** ## **10.3 Guilds and Communities of Practice** ### **10.3.1 Data Guilds.** 10.3.1.1 **Data Guilds** shall be communities of practice focused on data literacy, data stewardship, metadata, schemas, data dictionaries, lineage, data quality, data-use labels, AI-use labels, rights review, public-safe transformation, DICE practices, secure-room literacy, compute-to-data literacy, data incident awareness, and archive. 10.3.1.2 Data Guilds may support Academy pathways, WILPs, Competence Cells, National Working Groups, Foundry builds, DRI datasets, Observatory inputs, Reports, Marketplace listings, Registry records, Studio workflows, Grid inputs, and handoff context. 10.3.1.3 Data Guild participation shall not create data access rights, data ownership, data release permission, privacy compliance determination, or public authority approval. ### **10.3.2 AI Guilds.** 10.3.2.1 **AI Guilds** shall be communities of practice focused on AI literacy, human-AI collaboration, model cards, system cards, benchmark cards, agent workflow cards, AI-use labels, evaluation, red-team records, prompt-injection controls, human review, bias and harm review, model limitations, AI incident response, and responsible AI practice. 10.3.2.2 AI Guilds may support AI learning pathways, AI WILPs, AI Competence Cells, Foundry AI builds, Studio AI workflows, public-safe AI outputs, Grid AI inputs, TRL evidence notes, and National Portfolio AI capability records. 10.3.2.3 AI Guild participation shall not create AI safety certification, model approval, deployment authorization, automated decision authority, public authority decision, procurement readiness, financeability, or insurability. ### **10.3.3 Cyber Guilds.** 10.3.3.1 **Cyber Guilds** shall be communities of practice focused on cybersecurity literacy, digital trust, zero trust, secure collaboration, secure repositories, SBOM literacy, dependency review, vulnerability disclosure, incident response, critical infrastructure sensitivity, OT/IoT/edge security, AI security, secure-room technical review, and public-safe cyber reporting. 10.3.3.2 Cyber Guilds may support secure software controls, WILPs, Foundry builds, Studio workflows, DICE controls, Registry records, Marketplace listings, Grid inputs, National Portfolio cyber capability, and public-safe Reports. 10.3.3.3 Cyber Guild participation shall not create security certification, operational command, vulnerability disclosure authority beyond scope, public warning, procurement qualification, or deployment authorization. ### **10.3.4 Privacy Guilds.** 10.3.4.1 **Privacy Guilds** shall be communities of practice focused on privacy principles, data minimization, purpose limitation, consent and permission literacy, sensitive data handling, youth data protection, health data protection, community data protection, cross-border data literacy, portfolio display controls, learner privacy, worker data protection, and privacy incident awareness. 10.3.4.2 Privacy Guilds may support SCF governance, ILA records, WILPs, Micro-Credentials, public display controls, data rooms, secure rooms, DICE, Reports, Campaigns, Registry, Marketplace, and National Portfolio privacy controls. 10.3.4.3 Privacy Guild participation shall not create legal compliance determination, privacy certification, data protection officer status, public authority approval, or legal advice by default. ### **10.3.5 Geospatial Guilds.** 10.3.5.1 **Geospatial Guilds** shall be communities of practice focused on geospatial literacy, Earth observation, remote sensing, GIS, location data, sensitive location controls, public-safe map publishing, digital twins, sensor data, protected species data, infrastructure-sensitive data, sacred site and protected knowledge controls, and geospatial correction. 10.3.5.2 Geospatial Guilds may support DRI, Nexus Observatory, National Portfolios, Studio workflows, WFEH-B mapping, disaster-risk mapping, climate adaptation, Campaigns, Reports, Grid inputs, and lawful handoff context. 10.3.5.3 Geospatial Guild participation shall not create official maps, public authority records, surveillance authority, protected knowledge permission, public warning, or deployment authorization. ### **10.3.6 WFEH-B Guilds.** 10.3.6.1 **WFEH-B Guilds** shall be communities of practice focused on Water, Food, Energy, Health, and Biodiversity systems, including cross-system cascades, resilience indicators, systems-risk literacy, local context, public-safe reporting, sustainability competencies, climate and nature transition skills, and National Portfolio capability formation. 10.3.6.2 WFEH-B Guilds may support Academy pathways, Risk Academy modules, Competence Cells, National Working Groups, DRI summaries, Observatory signals, Studio scenarios, Campaigns, Reports, Nexus Universe arenas, and handoff dependency notes. 10.3.6.3 WFEH-B Guild participation shall not create environmental certification, public health decision, public authority approval, emergency action, community consent, procurement preference, or execution. ### **10.3.7 DRR / DRF / DRI Guilds.** 10.3.7.1 **DRR / DRF / DRI Guilds** shall be communities of practice focused on Disaster Risk Reduction, Disaster Risk Finance literacy, Disaster Risk Intelligence, protection gaps, risk layering, public-safe risk communication, indicators, uncertainty, confidence labels, hotspot records, cascade records, resilience planning, and finance-readiness literacy. 10.3.7.2 Such Guilds may support Risk Academy, National Working Groups, Competence Cells, Nexus Observatory, DRI dashboards, public authority learning rooms, capital-reader literacy, insurance-reader literacy, Reports, Nexus Universe readiness, and handoff context. 10.3.7.3 DRR / DRF / DRI Guild participation shall not create public warning authority, insurance score, investment signal, underwriting, finance advice, public authority decision, emergency command, or certification. ### **10.3.8 Public-Safe Reporting Guilds.** 10.3.8.1 **Public-Safe Reporting Guilds** shall be communities of practice focused on safe, accurate, bounded, non-overclaiming public communication of risk, resilience, learning, contribution, readiness, National Portfolio outputs, Nexus Universe outputs, Campaign outputs, DRI summaries, Observatory outputs, Reports, Registry notices, Marketplace descriptions, and correction notices. 10.3.8.2 Public-Safe Reporting Guilds shall preserve no-warning, no-approval, no-finance, no-procurement, no-certification, no-consent, no-execution, protected knowledge, youth protection, community safeguard, and public repair controls. 10.3.8.3 Public-Safe Reporting Guild participation shall not create spokesperson authority, official publication authority, public warning authority, endorsement, certification, or public authority approval. ### **10.3.9 Safeguard Guilds.** 10.3.9.1 **Safeguard Guilds** shall be communities of practice focused on community safeguards, Indigenous protocols where applicable, protected knowledge, youth safeguards, disability inclusion, humanitarian sensitivity, non-extractive learning, trauma sensitivity, accessibility, public-interest participation, and community-facing correction. 10.3.9.2 Safeguard Guilds may support Academy pathways, WILPs, Campaigns, National Working Groups, Competence Cells, Reports, Studio workflows, Nexus Universe rooms, public-safe summaries, National Portfolios, and handoff context. 10.3.9.3 Safeguard Guild participation shall not create community consent, Indigenous consent, protected knowledge permission, social license, public authority approval, or deployment authorization. ### **10.3.10 Labor-Market Intelligence Guilds.** 10.3.10.1 **Labor-Market Intelligence Guilds** shall be communities of practice focused on labor-market data, job posting analysis, occupation and task analysis, skills gap analysis, workforce transition, AI-era work redesign, green and resilience skills, wage and job quality context, informal work signals, gig work signals, care work signals, public service work, migration and diaspora skills, and National Skills Maps. 10.3.10.2 Labor-Market Intelligence Guilds may support National Working Groups, SCF competency ontology, Academy pathway design, WILP and host mapping, Micro-Credential design, public-safe skills reporting, and National Portfolio capability records. 10.3.10.3 Labor-Market Intelligence Guild participation shall not create labor-market certainty, hiring guarantees, wage guarantees, public authority decisions, employment agency status, worker ranking, or social scoring. ### **10.3.11 Credential and Assessment Guilds.** 10.3.11.1 **Credential and Assessment Guilds** shall be communities of practice focused on Micro-Credentials, digital badges, competency evidence, assessment design, reviewer training, assessor governance, recognition of prior learning, credential metadata, verification, revocation, correction, and archive. 10.3.11.2 Credential and Assessment Guilds may support SCF Micro-Credentials, ILA records, Skills Wallets, WILPs, Academy pathways, Risk Academy pathways, Registry records, Marketplace display, and public-safe credential notices. 10.3.11.3 Credential and Assessment Guild participation shall not create professional license, statutory credential authority, university credit authority, public authority credential authority, or certification authority unless separately and lawfully recorded. ### **10.3.12 Handoff Literacy Guilds.** 10.3.12.1 **Handoff Literacy Guilds** shall be communities of practice focused on lawful handoff literacy, dependency transfer, evidence context, data context, method context, Studio context, Grid and TRL context, public-safe status, safeguard status, public authority dependencies, legal dependencies, finance and insurance questions, procurement boundaries, provider-neutrality notes, sponsor-boundary notes, recipient responsibilities, correction pathways, and recall. 10.3.12.2 Handoff Literacy Guilds may support National Working Groups, Competence Cells, Risk Agency pathways, Foundry outputs, Nexus Universe readiness rooms, National Portfolio handoff notes, and lawful downstream recipient literacy. 10.3.12.3 Handoff Literacy Guild participation shall not create legal advice, investment advice, insurance advice, procurement advice, public authority approval, execution authority, or recipient responsibility. *** ## **10.4 Mentors and Coaches** ### **10.4.1 Mentor Roles.** 10.4.1.1 **Mentors** shall support learners, contributors, WILP participants, Competence Cells, National Working Groups, Academy cohorts, Risk Academy cohorts, Foundry contributors, Campaign contributors, reviewers, maintainers, and public-good workforce communities through guidance, supervision, feedback, reflection, practice support, professional socialization, public-good discipline, and correction. 10.4.1.2 Mentor roles may include learning mentor, WILP mentor, technical mentor, data mentor, AI mentor, cyber mentor, privacy mentor, geospatial mentor, WFEH-B mentor, DRR/DRF/DRI mentor, public-safe reporting mentor, safeguard mentor, Foundry mentor, Campaign mentor, National Portfolio mentor, public authority learning mentor, Risk Agency mentor, reviewer mentor, and maintainer mentor. 10.4.1.3 Mentorship shall be bounded to the recorded role. Mentor status shall not create employment relationship, professional licensing authority, certification authority, public authority approval, procurement authority, finance authority, insurance authority, community consent authority, deployment authority, or execution authority. ### **10.4.2 Coach Roles.** 10.4.2.1 **Coaches** shall support pathway navigation, learning progression, competency development, career transition, workforce resilience, WILP readiness, contribution readiness, public-good participation, reflection, confidence, collaboration, and pathway continuity. 10.4.2.2 Coach roles may include learning coach, career transition coach, WILP coach, Academy coach, Risk Academy coach, Foundry coach, Campaign coach, accessibility coach, public-safe communication coach, and handoff literacy coach. 10.4.2.3 Coaching shall not be represented as employment placement, immigration advice, legal advice, therapy, regulated professional advice, public authority approval, finance advice, insurance advice, procurement advice, or guaranteed career outcome unless separately and lawfully authorized. ### **10.4.3 Mentor Qualification Records.** 10.4.3.1 Mentor Qualification Records shall identify mentor identity or permitted identifier, domain, experience basis, competency basis, training completed, safeguarding status where applicable, youth protection status where applicable, conflict status, approved pathways, supervision scope, renewal requirements, and correction history. 10.4.3.2 Mentor qualification may be supported by SCF records, Micro-Credentials, ILA records, iCRS records, professional experience, academic experience, technical contribution, public-good contribution, host verification, peer review, and steward review. 10.4.3.3 Mentor Qualification Records shall not be professional licenses, teaching licenses, public authority appointments, or legal authorization to supervise regulated work unless separately and lawfully recorded. ### **10.4.4 Supervision Records.** 10.4.4.1 Supervision Records shall document mentor or coach interactions, supervision cadence, learner progress, feedback, work scope, evidence status, safety concerns, safeguard concerns, data concerns, AI-use concerns, correction needs, and completion status. 10.4.4.2 Supervision Records shall be privacy-protective and shall not disclose sensitive learner information, youth information, health information, disability information, community-sensitive information, or protected knowledge beyond authorized use. 10.4.4.3 Supervision Records may support ILA records, WILP records, Micro-Credential evidence, iCRS recognition, Competence Cell records, and correction pathways. ### **10.4.5 Mentor Conflicts.** 10.4.5.1 Mentors and coaches shall disclose actual, potential, or perceived conflicts, including employer interests, sponsor interests, provider interests, procurement interests, investment interests, insurance interests, public authority roles, personal relationships, academic conflicts, assessment conflicts, commercial interests, or downstream handoff interests. 10.4.5.2 Conflict management may include disclosure, recusal, role limitation, independent review, reassignment, additional oversight, restricted assessment role, correction, or removal. 10.4.5.3 Mentor conflict disclosure shall protect learner fairness, assessment integrity, public-good neutrality, sponsor boundaries, provider boundaries, and public trust. ### **10.4.6 Safeguard Obligations.** 10.4.6.1 Mentors and coaches shall comply with safeguard obligations, including respect for learner dignity, youth protection, disability inclusion, accessibility, anti-harassment, anti-discrimination, trauma sensitivity, community safeguards, Indigenous protocols where applicable, protected knowledge controls, privacy, and non-extractive participation. 10.4.6.2 Mentors and coaches shall escalate safety issues, harassment, discrimination, exploitation, data misuse, AI misuse, protected knowledge issues, public-safe overclaims, labor misclassification, and other incidents through appropriate channels. 10.4.6.3 Mentor and coach misconduct may trigger correction, suspension, removal, record withdrawal, public-safe repair, or referral to competent authorities where appropriate. ### **10.4.7 Youth and Vulnerable Learner Controls.** 10.4.7.1 Mentorship or coaching involving youth or vulnerable learners shall apply heightened controls, including age-appropriate communication, guardian or institutional permissions where required, screening where appropriate, safe communication channels, restricted private contact where required, data minimization, restricted public display, and escalation procedures. 10.4.7.2 Youth and vulnerable learners shall not be exposed to unsafe work, exploitative contribution, unmoderated adult environments, field risk, sensitive data, protected knowledge, high-pressure production demands, or public exposure without appropriate safeguards. 10.4.7.3 Youth protection records shall be handled as sensitive records. ### **10.4.8 Mentor Review and Correction.** 10.4.8.1 Mentor and coach performance shall be reviewable through learner feedback, host feedback, steward review, safeguard review, contribution outcomes, supervision records, complaint records, correction records, and renewal review. 10.4.8.2 Correction may include coaching, additional training, scope limitation, supervision change, conflict management, suspension, removal, record correction, public-safe repair, or archive. 10.4.8.3 Mentor review shall not become public ranking, social scoring, or reputational punishment by default. *** ## **10.5 Reviewers and Assessors** ### **10.5.1 Competency Reviewers.** 10.5.1.1 **Competency Reviewers** shall review competency evidence, learning outcomes, WILP evidence, Micro-Credential evidence, ILA records, portfolio artifacts, iCRS contribution records, and pathway completion evidence within recorded scope. 10.5.1.2 Competency Reviewers shall apply defined criteria, competency maps, evidence sufficiency, level descriptors, fairness controls, accessibility controls, conflict rules, and correction pathways. 10.5.1.3 Competency review shall not create professional license, statutory qualification, employment guarantee, procurement qualification, public authority approval, or deployment authorization by default. ### **10.5.2 Technical Reviewers.** 10.5.2.1 **Technical Reviewers** shall review technical work products, software, data pipelines, dashboards, APIs, models, digital twins, simulations, notebooks, infrastructure notes, technical Reports, Foundry builds, Studio workflows, Grid inputs, TRL notes, and handoff technical context. 10.5.2.2 Technical Reviewers shall assess scope, correctness within scope, documentation, reproducibility, security, accessibility, data dependencies, model limitations, assumptions, support class, public-safe status, and correction needs. 10.5.2.3 Technical review shall not create certification, warranty, production approval, security certification, provider validation, procurement recommendation, or deployment authorization. ### **10.5.3 Data Reviewers.** 10.5.3.1 **Data Reviewers** shall review data objects, metadata, lineage, data dictionaries, schemas, data quality, rights status, data-use labels, AI-use labels, access class, public-safe transformation, sensitive data controls, DICE records, DRI records, Observatory inputs, and archive rules. 10.5.3.2 Data Reviewers shall assess rights, provenance, sensitivity, minimization, purpose limitation, public-safe status, correction needs, and downstream use limits. 10.5.3.3 Data review shall not create data ownership, data access rights, open data status, legal compliance determination, public authority record status, or publication permission beyond recorded scope. ### **10.5.4 AI-Use Reviewers.** 10.5.4.1 **AI-Use Reviewers** shall review AI-use labels, model cards, system cards, benchmark cards, agent workflow cards, prompt-use records, retrieval settings, fine-tuning status, training permissions, agentic workflow controls, human review requirements, output classifications, AI incident records, and correction needs. 10.5.4.2 AI-Use Reviewers shall assess intended use, prohibited use, data provenance, training constraints, evaluation records, bias and harm review, prompt-injection controls, tool-permission controls, logging, red-team records, drift detection, and withdrawal conditions. 10.5.4.3 AI-use review shall not create AI safety certification, model approval, public authority decision, automated decision authority, financeability, insurability, procurement readiness, or deployment authorization. ### **10.5.5 Public-Safe Reviewers.** 10.5.5.1 **Public-Safe Reviewers** shall review public-facing materials, Reports, Campaign outputs, Registry notices, Marketplace descriptions, DRI summaries, Observatory summaries, Studio summaries, National Portfolio summaries, Nexus Universe materials, public authority learning summaries, and handoff-context language. 10.5.5.2 Public-Safe Reviewers shall ensure no-warning, no-approval, no-finance, no-procurement, no-certification, no-consent, no-execution, protected knowledge, youth protection, privacy, community safeguard, accessibility, and correction controls. 10.5.5.3 Public-safe review shall not create public warning authority, official publication authority, public authority approval, endorsement, certification, or legal approval. ### **10.5.6 Safeguard Reviewers.** 10.5.6.1 **Safeguard Reviewers** shall review community safeguards, Indigenous protocols where applicable, protected knowledge, youth safeguards, disability inclusion, accessibility, humanitarian sensitivity, non-extractive participation, fieldwork risk, trauma sensitivity, public-interest participation, and community-facing correction. 10.5.6.2 Safeguard Reviewers shall assess risks of extraction, tokenization, consent overclaim, protected knowledge exposure, unsafe public display, inaccessible participation, community harm, youth harm, and inequitable participation. 10.5.6.3 Safeguard review shall not create community consent, Indigenous consent, protected knowledge permission, social license, public authority approval, or deployment authorization. ### **10.5.7 National Pathway Reviewers.** 10.5.7.1 **National Pathway Reviewers** shall review national routing, National Skills Maps, National Working Group records, Competence Cell records, National Portfolio inputs, Nexus Universe preparation, public authority learning records, host maps, WILP maps, and national localization. 10.5.7.2 National Pathway Reviewers shall assess national ownership, local context, language, public authority boundaries, data sovereignty, labor-market relevance, public-safe status, accessibility, safeguard status, and handoff dependencies. 10.5.7.3 National pathway review shall not create national endorsement, public authority approval, country ranking, procurement status, financeability, insurability, community consent, or execution authority. ### **10.5.8 Handoff Context Reviewers.** 10.5.8.1 **Handoff Context Reviewers** shall review handoff dependency packages, evidence context, data context, method context, Studio context, Grid and TRL context, public-safe status, safeguard status, public authority dependencies, legal dependencies, finance and insurance questions, procurement boundaries, provider-neutrality notes, sponsor-boundary notes, recipient responsibilities, correction pathways, and recall conditions. 10.5.8.2 Handoff Context Reviewers shall ensure that handoff materials transfer context and dependencies only, not authority. 10.5.8.3 Handoff context review shall not create legal advice, investment advice, insurance advice, procurement recommendation, public authority approval, certification, deployment authorization, or execution. ### **10.5.9 Reviewer Conflicts.** 10.5.9.1 Reviewers and assessors shall disclose actual, potential, or perceived conflicts, including employer relationships, sponsor interests, provider interests, learner relationships, academic conflicts, procurement interests, investment interests, insurance interests, public authority roles, political roles, community roles, or downstream implementation interests. 10.5.9.2 Conflict controls may include disclosure, recusal, second review, independent review, role limitation, restricted public display, correction, suspension, or removal. 10.5.9.3 Reviewer conflicts shall be managed to preserve fairness, public-good neutrality, credential integrity, data integrity, public-safe reporting, and lawful handoff boundaries. ### **10.5.10 Reviewer Correction.** 10.5.10.1 Reviewer decisions and review records shall be correctable. Correction may address error, bias, conflict failure, evidence omission, incorrect scope, incorrect criteria, public-safe failure, data error, AI-use error, safeguard failure, overclaim, underclaim, or reviewer misconduct. 10.5.10.2 Reviewer correction may result in amended review, second review, withdrawal of review, credit correction, credential correction, Registry update, Marketplace update, Report correction, public-safe repair, or archive. 10.5.10.3 Reviewer correction shall preserve procedural fairness and shall not be used to pressure reviewers into sponsor, provider, public authority, employer, or contributor-preferred outcomes. *** ## **10.6 Workforce Community Records** ### **10.6.1 Participation Records.** 10.6.1.1 Participation Records shall document participation in Competence Cells, National Working Groups, Guilds, mentoring, coaching, review, WILPs, Academy pathways, Risk Academy pathways, Campaigns, Foundry, Studio, Reports, Marketplace, Registry, Grid, Nexus Universe, and National Portfolio work. 10.6.1.2 Participation Records shall identify role, pathway, scope, dates, visibility, privacy status, evidence status, contribution status, review status, support status, correction pathway, and archive rule. 10.6.1.3 Participation Records shall not create authority, credential, employment, endorsement, procurement qualification, public authority approval, community consent, or execution. ### **10.6.2 Learning Records.** 10.6.2.1 Learning Records shall document learning activities, learning outcomes, pathway progress, WILP participation, Micro-Credential eligibility, ILA entries, reflections, assessments, mentor verification, and correction. 10.6.2.2 Learning Records shall be governed by privacy, learner permissions, youth protections, accessibility needs, data-use labels, AI-use labels, public display controls, and correction rights. 10.6.2.3 Learning Records shall not create professional license, employment guarantee, immigration status, procurement qualification, public authority credential, or deployment authorization. ### **10.6.3 Contribution Records.** 10.6.3.1 Contribution Records shall document public-good contribution through iCRS, including data, software, research, review, mentorship, translation, accessibility, Campaign, Foundry, public-safe reporting, and correction contributions. 10.6.3.2 Contribution Records shall distinguish submitted, accepted, reviewed, incorporated, published, corrected, withdrawn, superseded, archived, and non-continuing contribution. 10.6.3.3 Contribution Records shall not create compensation, employment, equity, tokens, financial value, procurement qualification, credential, public authority approval, or execution. ### **10.6.4 Mentor Records.** 10.6.4.1 Mentor Records shall document mentor roles, pathways, learner or cohort context, qualification basis, supervision records, safeguard obligations, conflict status, feedback, review, correction, and archive. 10.6.4.2 Mentor Records shall be privacy-protective and shall not expose sensitive learner information, youth data, protected knowledge, or confidential host information beyond authorized use. 10.6.4.3 Mentor Records shall not create employment, professional license, teaching certification, public authority status, or credentialing authority by default. ### **10.6.5 Reviewer Records.** 10.6.5.1 Reviewer Records shall document reviewer role, review scope, criteria, conflicts, review outcome, limitations, correction requirements, appeal status, and archive. 10.6.5.2 Reviewer Records may support reviewer pathway development, quality assurance, Micro-Credential governance, Registry records, Marketplace governance, public-safe review, Grid review, and handoff context review. 10.6.5.3 Reviewer Records shall not create certification authority, legal authority, public authority approval, professional license, procurement approval, or deployment authorization by default. ### **10.6.6 Guild Records.** 10.6.6.1 Guild Records shall document Guild identity, purpose, domain, convening pathway, participation, activities, outputs, learning objects, contribution records, review records, public-safe outputs, correction records, and archive. 10.6.6.2 Guild Records shall identify whether a Guild is active, forming, under review, supported, unsupported, suspended, withdrawn, superseded, archived, or non-continuing. 10.6.6.3 Guild Records shall not create professional membership status, license, certification, employment status, public authority approval, procurement qualification, or execution authority. ### **10.6.7 Competence Cell Records.** 10.6.7.1 Competence Cell Records shall document cell identity, domain, scope, mandate, host or steward where applicable, members, mentors, reviewers, workplans, outputs, evidence records, learning records, contribution records, WILP records, public-safe records, safeguard records, National Portfolio links, Nexus Universe links, handoff dependency links, correction records, and archive. 10.6.7.2 Competence Cell Records shall state status, review level, support class, public display class, data-use class, AI-use class, public-safe status, and boundary notices. 10.6.7.3 Competence Cell Records shall not create execution authority, certification, professional standing, public authority approval, procurement status, financeability, insurability, or community consent. ### **10.6.8 National Working Group Records.** 10.6.8.1 National Working Group Records shall document formation, mandate, participation, competency needs, National Skills Maps, labor-market intelligence reviews, Academy pathway design, WILP and host mapping, National Portfolio inputs, Nexus Universe preparation, correction, and archive. 10.6.8.2 National Working Group Records shall preserve national ownership, public authority boundaries, sponsor and provider boundaries, labor-market limits, data sensitivity, protected knowledge controls, and public-safe reporting. 10.6.8.3 National Working Group Records shall not create public authority approval, national endorsement, procurement status, country ranking, financeability, insurance approval, community consent, or execution authority. ### **10.6.9 Public Display Controls.** 10.6.9.1 Public display of workforce community records shall be governed by privacy, consent and permission, youth protection, sensitive profile controls, public-safe rules, accessibility, correction status, contributor preferences, host confidentiality, data rights, protected knowledge restrictions, and safeguard review. 10.6.9.2 Public display may include contributor profiles, Guild pages, Competence Cell summaries, National Working Group summaries, mentor profiles, reviewer profiles, learning achievements, Micro-Credentials, public-safe Reports, Nexus Universe showcases, Marketplace listings, and Registry records where permitted. 10.6.9.3 Public display shall not create public ranking, social scoring, employment guarantee, credential overclaim, endorsement, procurement qualification, public authority approval, community consent, or execution authority. ### **10.6.10 Archive.** 10.6.10.1 Workforce Community Records shall be archived according to status, sensitivity, retention, correction, withdrawal, supersession, non-continuation, privacy, youth protection, protected knowledge, and public-safe rules. 10.6.10.2 Archive records shall distinguish current from historical status and shall include not-current notices where necessary. 10.6.10.3 Archive shall preserve institutional memory without creating current authority. *** ## **10.7 Community Boundary Rules** ### **10.7.1 Participation Is Not Authority.** 10.7.1.1 Participation in a Competence Cell, National Working Group, Guild, mentorship pathway, reviewer pathway, WILP, Campaign, Foundry build, Academy cohort, Risk Academy cohort, Nexus Universe activity, or National Portfolio activity shall not create authority by implication. 10.7.1.2 Participation shall not create public authority approval, institutional endorsement, procurement status, credential status, employment status, professional license, community consent, financeability, insurance approval, deployment authorization, or execution authority. ### **10.7.2 Mentorship Is Not Employment.** 10.7.2.1 Mentorship, coaching, supervision, learner support, pathway guidance, WILP support, Foundry support, or Campaign support shall not create employment, contractor status, wages, benefits, tax status, work authorization, public employment, or future work entitlement by default. 10.7.2.2 Where mentorship is paid, contracted, employed, or otherwise legally governed, that status shall arise from a separate lawful arrangement and shall be accurately recorded. ### **10.7.3 Review Is Not Certification by Default.** 10.7.3.1 Review by a competency reviewer, technical reviewer, data reviewer, AI-use reviewer, public-safe reviewer, safeguard reviewer, national pathway reviewer, or handoff context reviewer shall not create certification, professional license, public authority approval, procurement approval, legal approval, product approval, deployment authorization, or execution authority by default. 10.7.3.2 Review shall remain bounded to scope, criteria, evidence, role, limitations, and correction pathway. ### **10.7.4 Working Group Participation Is Not Public Authority Approval.** 10.7.4.1 Participation by public authorities, public officials, ministries, agencies, municipalities, regulators, public employment services, or public institutions in National Working Groups shall not create official action, public authority approval, regulatory determination, public finance allocation, procurement approval, public warning, emergency command, or policy adoption by implication. 10.7.4.2 Official public authority action must occur through separate competent legal channels. ### **10.7.5 Competence Cell Work Is Not Execution.** 10.7.5.1 Competence Cell work may produce learning evidence, public-good outputs, Reports, data objects, software contributions, Studio outputs, Campaign outputs, Grid inputs, TRL evidence notes, National Portfolio inputs, and handoff dependency notes, but shall not create implementation, operations, deployment, procurement, finance, insurance, public authority action, emergency command, or community consent by implication. 10.7.5.2 Execution must occur separately through competent lawful actors, including public authorities, employers, National Consortium Companies, Project SPVs, operators, contractors, providers, funders, insurers, or other lawful recipients. ### **10.7.6 Guild Standing Is Not Professional License.** 10.7.6.1 Guild membership, Guild contribution, Guild leadership, Guild review, Guild mentorship, Guild recognition, or Guild public display shall not create professional license, statutory qualification, academic credential, public authority credential, procurement qualification, vendor approval, or professional certification by default. 10.7.6.2 Guild standing may support learning, contribution recognition, competency evidence, public-good participation, and pathway progression only within recorded scope. *** ## **10.8 Final Part X Operating Statement** 10.8.1 Competence Cells, National Working Groups, Guilds, mentors, reviewers, assessors, and workforce communities shall form the human capability operating layer of SCF. They shall convert learning, labor-market intelligence, National Portfolio needs, public-good contribution, Foundry production, Campaign mobilization, DICE data practices, GRIx risk meaning, DRI intelligence, Observatory signals, Studio workflows, Grid inputs, Nexus Universe preparation, and lawful handoff literacy into structured, evidence-bearing, nationally grounded, and correctionable capability formation. 10.8.2 Competence Cells shall function as applied capability units, national capacity engines, Foundry and Academy bridges, DICE / GRIx / DRI / Observatory work units, Nexus Universe preparation units, and handoff-context producers. They shall not function as execution vehicles, employers, professional licensing bodies, certifiers, public authorities, procurement bodies, finance actors, insurers, project developers, or operators by default. 10.8.3 National Working Groups shall identify competency needs, support National Skills Maps, review labor-market intelligence, design Academy pathways, map WILPs and hosts, prepare National Portfolio inputs, prepare Nexus Universe participation, and maintain correction and archive discipline. They shall preserve national ownership, role separation, labor-market limits, public authority boundaries, sponsor and provider boundaries, data safeguards, protected knowledge, and public-safe reporting. 10.8.4 Guilds and communities of practice shall build shared competence across data, AI, cyber, privacy, geospatial, WFEH-B, DRR, DRF, DRI, public-safe reporting, safeguards, labor-market intelligence, credentials, assessment, and handoff literacy. They shall support learning and practice without becoming professional licensing bodies, certification bodies, public authorities, procurement filters, or execution channels. 10.8.5 Mentors, coaches, reviewers, and assessors shall provide guidance, supervision, feedback, review, assessment, correction, and pathway support within recorded scope. Their roles shall be governed by qualification records, supervision records, conflict rules, safeguard duties, youth and vulnerable learner controls, review criteria, correction pathways, and archive. 10.8.6 Workforce community records shall preserve participation, learning, contribution, mentorship, review, Guild activity, Competence Cell activity, National Working Group activity, public display permissions, correction, and archive. Such records shall strengthen public-good capability and institutional memory without creating social scoring, employment guarantees, professional licenses, procurement qualifications, public authority approvals, community consent, deployment authorization, financeability, insurability, or execution authority. 10.8.7 The final rule of Part X is that communities build capability, records preserve meaning, mentorship supports growth, review strengthens trust, cells convert learning into applied practice, working groups align national needs, and Guilds sustain shared competence; none of these forms of participation creates authority, certification, employment, public authority approval, procurement status, professional license, consent, 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/x.-competence.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.