# XVII. EMPLOYERS

## **17.1 Employer Interface Doctrine**

### **17.1.1 Employer Interface as Demand Signal, Not Control.**

17.1.1.1 **SCF shall treat employer participation as a demand-signal interface, not as curriculum control, credential control, labor-market control, public-good priority control, or institutional capture.** Employers may provide information about emerging skill needs, occupational changes, task requirements, technology adoption patterns, workforce gaps, hiring difficulties, apprenticeship needs, work-integrated learning opportunities, sector challenges, safety-critical tasks, and lawful handoff contexts, but such input shall be received as evidence to be reviewed, classified, recorded, compared, corrected, and balanced within SCF.

17.1.1.2 Employer demand signals shall be useful to SCF because they help reveal the changing relationship between work, technology, skills, resilience, productivity, safety, public-good capability, sector transformation, and national capacity. Such signals may inform competency maps, learning objects, WILPs, micro-credentials, Foundry Quests, Bounties, Builds, National Skills Maps, National Portfolio records, Nexus Universe preparation, Marketplace opportunities, Registry records, and lawful handoff literacy.

17.1.1.3 Employer input shall not override public-good purpose, national ownership, worker protection, learner protection, community safeguards, Indigenous protocols where applicable, public authority boundaries, credential integrity, competency evidence requirements, accessibility, inclusion, correctionability, or the public-good firewall. Employer demand shall be treated as one source of intelligence among official labor statistics, public employment service data, education and training data, worker voice, labor organization input, community knowledge, sector evidence, public authority learning records, Nexus Campaign signals, Nexus Academy signals, Foundry records, Registry records, Marketplace signals, and National Portfolio needs.

17.1.1.4 No employer, sector body, sponsor, provider, host, capital reader, insurer, donor, public finance reader, or industry participant shall acquire by participation any right to determine SCF competencies, control curriculum, approve credentials, exclude competitors, validate providers, influence procurement, create employment rankings, control public-good records, suppress correction, or convert public-good competency infrastructure into a private workforce pipeline.

### **17.1.2 Skill Demand Without Curriculum Capture.**

17.1.2.1 **SCF shall allow employers and sector actors to submit skill demand while prohibiting curriculum capture.** Skill demand may include required knowledge, technical tasks, emerging tools, safety requirements, job-family shifts, workforce shortages, digital transformation needs, AI augmentation needs, green transition needs, resilience needs, cybersecurity needs, public-good software needs, data stewardship needs, and lawful handoff skill needs.

17.1.2.2 Curriculum capture shall mean any attempt by an employer, sponsor, provider, sector actor, platform, vendor, funder, or other participant to cause SCF learning objects, micro-credentials, WILPs, competency maps, assessments, Foundry Quests, or Marketplace opportunities to serve private recruitment, vendor lock-in, product promotion, procurement preference, workforce extraction, credential inflation, or brand validation rather than public-good capability formation.

17.1.2.3 Employer skill demand may influence curriculum only after review for:\
(a) evidence basis;\
(b) labor-market relevance;\
(c) public-good relevance;\
(d) national capacity relevance;\
(e) worker and learner protection;\
(f) accessibility and inclusion;\
(g) data, AI, cyber, and privacy implications;\
(h) safeguard implications;\
(i) sponsor and provider neutrality;\
(j) correction and archive requirements.

17.1.2.4 SCF curriculum shall remain competency-based, evidence-bearing, transferable, public-good disciplined, reviewable, correctable, and not controlled by any employer or provider. Employer-relevant learning may be created, but shall not become employer-owned curriculum unless separately and lawfully documented outside the public-good SCF default posture.

### **17.1.3 Work Host Without Employment by Default.**

17.1.3.1 **SCF shall distinguish work-host participation from employment.** Employers, universities, public authorities, community institutions, labs, Foundry hosts, National Nodes, National Working Groups, Competence Cells, National Consortium Companies, Project SPVs, sponsors, providers, and other lawful host organizations may host WILPs, apprenticeships, internships, practice environments, supervised projects, field placements, Studio exercises, Foundry contributions, Campaign activities, or Risk Agency shadowing activities.

17.1.3.2 A host role shall not by itself create employment, contractor status, wage entitlement, visa or immigration status, professional qualification, procurement eligibility, hiring commitment, public authority appointment, enterprise execution status, or deployment authority.

17.1.3.3 Where a work-host arrangement creates or may create employment, contractor, stipend, honorarium, workplace safety, tax, social security, insurance, immigration, youth protection, confidentiality, data protection, intellectual property, union, collective agreement, or labor-law obligations, such obligations shall be separately identified, recorded, and managed through competent legal and institutional processes.

17.1.3.4 Work-host participation shall require scope clarity, supervision clarity, learning objectives, task boundaries, evidence requirements, health and safety controls, anti-harassment controls, accessibility accommodations, data and confidentiality controls, AI and tool-use controls, grievance channels, correction pathways, and exit rules.

### **17.1.4 Hiring Signal Without Hiring Commitment.**

17.1.4.1 **SCF shall permit hiring signals while prohibiting hiring overclaim.** Employers may signal interest in skills, competency profiles, portfolios, WILP graduates, micro-credential holders, Foundry contributors, maintainers, reviewers, Competence Cell participants, or National Portfolio contributors, but such signals shall not constitute hiring commitments, employment offers, wage guarantees, visa sponsorship commitments, recruitment promises, procurement eligibility, or professional recognition.

17.1.4.2 Hiring signals may inform labor-market intelligence, skills-gap analysis, transition pathways, employer-readable portfolio design, micro-credential relevance, WILP host mapping, sector skill compacts, and National Skills Maps, but shall remain evidence signals subject to review, uncertainty, correction, and boundary notices.

17.1.4.3 SCF shall not rank individuals for employers by default, automate hiring decisions, provide social scoring, create employer-controlled talent lists without permission, enable unauthorized scraping of learner profiles, or convert learner records into employment screening tools without lawful basis, learner consent, privacy controls, and public-safe display rules.

17.1.4.4 No SCF record shall be represented as a guarantee of employability, job placement, wage level, promotion, immigration outcome, professional licensing, procurement qualification, security clearance, public authority appointment, or enterprise readiness.

### **17.1.5 Employer-Readable Portfolios.**

17.1.5.1 **SCF may support employer-readable portfolios as controlled, learner-permissioned, evidence-based summaries of learning, competence, contribution, WILP participation, micro-credentials, Foundry Builds, Quest and Bounty contributions, review outcomes, public-safe outputs, and correction history.**

17.1.5.2 Employer-readable portfolios shall be designed to improve clarity, portability, mobility, and skills-based opportunity without reducing learners to automated rankings or unreviewed skill claims. They shall include boundary notices, evidence links, scope labels, review labels, expiry or renewal notes where applicable, privacy controls, display permissions, correction pathways, and non-equivalence statements.

17.1.5.3 Employer-readable portfolio content may include:\
(a) competency records;\
(b) micro-credential records;\
(c) WILP records;\
(d) Quest and Bounty records;\
(e) Build contribution records;\
(f) review records;\
(g) mentor records;\
(h) public-safe output records;\
(i) Registry and Marketplace display records;\
(j) correction and withdrawal records.

17.1.5.4 Employer-readable portfolios shall not create employer verification by default, hiring decisions, employment eligibility, wage entitlement, professional license, immigration status, procurement qualification, public authority credential, deployment approval, or endorsement. Employers and hosts shall conduct independent diligence according to applicable law, sector requirements, worker protections, and role-specific responsibilities.

### **17.1.6 Employer Validation Boundaries.**

17.1.6.1 **SCF shall distinguish employer feedback from employer validation.** Employers may provide evidence about observed work products, task performance, WILP participation, mentorship, project experience, sector relevance, occupation needs, and competency gaps, but employer feedback shall not itself validate a credential, license a person, certify competence, approve a provider, or create public-good authority.

17.1.6.2 Employer validation overclaim shall include any representation that an employer’s participation, review, hosting, sponsorship, challenge submission, Quest sponsorship, mentorship, or feedback creates SCF certification, employer-approved curriculum, preferred provider status, hiring guarantee, procurement qualification, public authority approval, or market endorsement.

17.1.6.3 Employer feedback may be used as one evidence input within SCF where it is:\
(a) source-identified;\
(b) scope-limited;\
(c) role-specific;\
(d) reviewable;\
(e) non-exclusive;\
(f) conflict-disclosed;\
(g) privacy-compliant;\
(h) worker-protective;\
(i) correctable;\
(j) archived.

17.1.6.4 SCF shall not permit employer validation to become a pay-to-credential, pay-to-access, pay-to-rank, pay-to-hire, pay-to-prioritize, or pay-to-influence mechanism.

### **17.1.7 Fair Work and Anti-Exploitation Controls.**

17.1.7.1 **SCF shall apply fair work and anti-exploitation controls to employer, host, industry, sector, sponsor, provider, and work-integrated interfaces.** Such controls shall protect learners, workers, contributors, youth participants, displaced workers, informal workers, migrants, refugees, people with disabilities, underrepresented groups, community participants, and public-good contributors from misuse of learning, contribution, portfolio, credential, or WILP systems.

17.1.7.2 Fair work controls shall include:\
(a) no disguised employment;\
(b) no unpaid substitution of regular labor;\
(c) clear scope and learning purpose;\
(d) transparent support or compensation status where applicable;\
(e) workload and hours discipline;\
(f) health, safety, and wellbeing controls;\
(g) harassment and abuse prevention;\
(h) accessible participation conditions;\
(i) data and surveillance limits;\
(j) grievance, complaint, correction, and exit channels.

17.1.7.3 Anti-exploitation controls shall prevent employers, hosts, sponsors, providers, and sector actors from using SCF to extract unpaid work, capture learner data, pressure participants into unpaid availability, create informal hiring funnels without transparency, inflate credentials, impose proprietary training without public-good relevance, or use public-good contribution as a substitute for lawful employment or procurement.

17.1.7.4 Any employer or host that violates fair work, safeguard, data, privacy, youth protection, accessibility, anti-harassment, labor boundary, or correction obligations may be subject to correction, suspension, restriction, removal, archive, public-safe notice, or referral to competent processes where applicable.

### **17.1.8 No Employer Capture of Public-Good Competencies.**

17.1.8.1 **SCF shall preserve public-good competencies against employer capture.** No employer, industry group, provider, sponsor, platform, donor, funder, capital reader, insurer, or public-private actor shall control the definition, recognition, display, routing, correction, or archive of SCF competencies for private advantage.

17.1.8.2 Employer capture may include:\
(a) steering competencies toward one vendor stack without public-good justification;\
(b) converting open learning into proprietary dependence;\
(c) using credentials as private gatekeeping tools;\
(d) suppressing worker voice or labor protections;\
(e) excluding competitors through credential design;\
(f) turning WILPs into unpaid labor pipelines;\
(g) influencing Marketplace listings for procurement advantage;\
(h) using sponsorship to control curriculum;\
(i) using data access to rank workers without consent;\
(j) resisting correction of overclaims.

17.1.8.3 SCF shall use public-good firewall rules, provider-neutrality rules, sponsor-boundary rules, conflict disclosure, independent review, labor and worker organization input, public authority learning boundaries, correctionability, and archive discipline to prevent employer capture.

***

## **17.2 Employer Functions**

### **17.2.1 Skill Demand Submission.**

17.2.1.1 Employers may submit skill demand records to SCF in order to identify current, emerging, declining, crisis-driven, AI-driven, green-transition, resilience, cybersecurity, infrastructure, public authority capacity, sector-specific, or National Portfolio-linked skill needs.

17.2.1.2 A skill demand submission should include:\
(a) occupation or role family;\
(b) task description;\
(c) skill or competency need;\
(d) urgency and time horizon;\
(e) sector context;\
(f) technology context;\
(g) safety or regulatory sensitivity;\
(h) location or national context;\
(i) evidence source;\
(j) boundary notice.

17.2.1.3 Skill demand submissions shall be reviewed against labor-market evidence, worker voice, public-good purpose, national capacity needs, equity considerations, data and privacy requirements, AI and automation implications, safeguard issues, and correction history.

17.2.1.4 Skill demand submission shall not create curriculum control, credential control, hiring commitment, employment guarantee, public authority decision, procurement priority, sector compact approval, or execution authority.

### **17.2.2 Occupation and Task Review.**

17.2.2.1 Employers may participate in occupation and task review to help identify how roles, jobs, work systems, safety-critical tasks, automation exposure, AI augmentation, digital transformation, climate transition, infrastructure change, and sector shifts are changing skill requirements.

17.2.2.2 Occupation and task review may support:\
(a) occupational families;\
(b) role profiles;\
(c) task inventories;\
(d) critical task mapping;\
(e) human-AI task allocation;\
(f) automation exposure mapping;\
(g) augmentation opportunity mapping;\
(h) safety-critical task mapping;\
(i) public authority-sensitive task mapping;\
(j) handoff-relevant task mapping.

17.2.2.3 Employer task review shall be balanced by worker input, educator input, public authority learning, official labor-market sources, sector evidence, community context, and SCF review. It shall not be treated as full labor-market truth or as authority over competency design.

17.2.2.4 Occupation and task review shall not create job classifications, official occupational standards, wage classifications, professional licensing requirements, labor-market forecasts, hiring decisions, public authority determinations, or procurement rules unless separately issued by competent bodies.

### **17.2.3 WILP Hosting.**

17.2.3.1 Employers may act as WILP hosts where they provide structured learning-through-work environments, supervised practice, work product opportunities, mentorship, sector exposure, safety discipline, and evidence-bearing practice opportunities.

17.2.3.2 Employer-hosted WILPs shall require:\
(a) learning agreement;\
(b) scope and workplan;\
(c) mentor or supervisor assignment;\
(d) supervision level;\
(e) health and safety controls;\
(f) data and confidentiality controls;\
(g) AI and tool-use controls;\
(h) fair work and anti-exploitation controls;\
(i) accessibility and inclusion controls;\
(j) correction and grievance controls.

17.2.3.3 WILP hosting shall not create employment by default, hiring commitment, procurement qualification, employer endorsement of SCF credentials, public authority approval, deployment authorization, or execution.

17.2.3.4 Employer WILP hosts shall respect learner rights, worker protections, privacy, confidentiality, anti-harassment duties, youth safeguards, accessibility requirements, grievance pathways, correction pathways, and exit rights.

### **17.2.4 Mentorship.**

17.2.4.1 Employers may provide mentors, coaches, technical guides, sector advisors, supervisors, or reviewers to support learners, workers, WILP participants, Foundry contributors, Competence Cells, National Working Groups, and Nexus Universe preparation.

17.2.4.2 Employer mentorship shall be recorded with:\
(a) mentor identity or role;\
(b) scope;\
(c) time period;\
(d) learner or contributor relationship;\
(e) conflict disclosure;\
(f) confidentiality obligations;\
(g) safeguard obligations;\
(h) review limitations;\
(i) correction pathway;\
(j) archive rule.

17.2.4.3 Mentorship shall not create employment, hiring commitment, professional license, credential approval, public authority approval, procurement qualification, provider validation, deployment authorization, or execution authority.

17.2.4.4 Mentors shall not misuse their position to extract work, solicit employment without transparency, influence credentials improperly, obtain confidential information outside scope, control learning outcomes for private advantage, or create coercive dependencies.

### **17.2.5 Work Product Review.**

17.2.5.1 Employers may review work products where they have relevant sector, technical, operational, safety, customer, infrastructure, workforce, or handoff-context knowledge.

17.2.5.2 Work product review may apply to:\
(a) WILP artifacts;\
(b) Foundry Builds;\
(c) software contributions;\
(d) data objects;\
(e) dashboards;\
(f) Studio outputs;\
(g) reports;\
(h) public-safe summaries;\
(i) National Portfolio objects;\
(j) handoff-context notes.

17.2.5.3 Employer work product review shall be treated as scoped feedback, not as certification, professional assessment by default, provider validation, procurement evaluation, public authority decision, financeability assessment, insurability assessment, deployment approval, or execution approval.

17.2.5.4 Employer reviewers shall disclose conflicts, avoid vendor favoritism, respect confidentiality, preserve public-good purpose, avoid overclaim, and accept correction.

### **17.2.6 Competence Feedback.**

17.2.6.1 Employers may provide competence feedback regarding observed skills, task performance, work readiness, safety awareness, collaboration, communication, technical fluency, data stewardship, AI-use discipline, public-safe reporting, sector literacy, or handoff literacy.

17.2.6.2 Competence feedback shall be recorded with:\
(a) feedback source;\
(b) observed context;\
(c) task scope;\
(d) evidence basis;\
(e) review level;\
(f) limitation statement;\
(g) learner permission where required;\
(h) privacy control;\
(i) correction process;\
(j) archive.

17.2.6.3 Competence feedback shall not create credential issuance, credential revocation, professional licensing, employment decision, wage decision, immigration decision, procurement qualification, public authority approval, or deployment authorization by implication.

### **17.2.7 Sector Challenge Definition.**

17.2.7.1 Employers may help define sector challenges that become Challenge Briefs, Quests, Bounties, Builds, WILPs, Academy pathways, Risk Academy modules, National Portfolio inputs, Nexus Campaigns, Nexus Universe arenas, or handoff-context questions.

17.2.7.2 Sector challenge definition shall include:\
(a) problem statement;\
(b) public-good relevance;\
(c) sector relevance;\
(d) affected systems;\
(e) competency needs;\
(f) evidence needs;\
(g) data needs;\
(h) safeguard considerations;\
(i) expected outputs;\
(j) boundary notices.

17.2.7.3 Sector challenge definition shall not create procurement priority, vendor preference, sponsor control, employer ownership of public-good outputs, public authority adoption, financeability, insurability, or execution authority.

### **17.2.8 Foundry Quest Sponsorship.**

17.2.8.1 Employers may sponsor or support Foundry Quests where such support is lawful, transparent, public-good aligned, non-controlling, provider-neutral where required, and subject to sponsor-boundary rules.

17.2.8.2 Foundry Quest sponsorship may include support for learning resources, data access where lawful, mentorship, technical context, infrastructure support, prizes, stipends, honoraria, operational context, or review participation, provided such support does not control outcomes or suppress correction.

17.2.8.3 Foundry Quest sponsorship shall be recorded with:\
(a) sponsor identity;\
(b) support type;\
(c) purpose;\
(d) restrictions;\
(e) conflicts;\
(f) data conditions;\
(g) intellectual property conditions;\
(h) public display permissions;\
(i) boundary notices;\
(j) correction and withdrawal rules.

17.2.8.4 Sponsorship shall not create curriculum control, credential control, procurement status, provider validation, employer endorsement, Marketplace preference, Registry status preference, public authority approval, financeability, insurability, or execution authority.

### **17.2.9 National Portfolio Input.**

17.2.9.1 Employers may provide National Portfolio input concerning sector capacity, workforce gaps, technology adoption, infrastructure needs, supply-chain resilience, WFEH-B systems, DRR / DRF / DRI priorities, public-good software needs, skill shortages, host capacity, and lawful handoff conditions.

17.2.9.2 National Portfolio input shall be reviewed against national ownership, public authority learning, labor-market evidence, worker voice, community context, public-good priorities, safeguard conditions, data rights, public-safe publication rules, and correctionability.

17.2.9.3 Employer input into National Portfolios shall not create national policy, public authority decision, procurement priority, public finance allocation, endorsement, provider validation, country ranking, sector ranking, execution authority, or community consent.

### **17.2.10 Handoff Recipient Interface.**

17.2.10.1 Employers may serve as lawful handoff recipients or prospective handoff-context reviewers where they are competent, authorized, and separately responsible for downstream diligence, legal compliance, safety, employment, procurement, finance, insurance, deployment, or execution obligations.

17.2.10.2 Handoff recipient interface may include review of:\
(a) evidence context;\
(b) data context;\
(c) method context;\
(d) Studio context;\
(e) Grid and TRL context;\
(f) public-safe status;\
(g) safeguard status;\
(h) public authority dependencies;\
(i) legal dependencies;\
(j) finance, insurance, procurement, and recipient responsibility notes.

17.2.10.3 Handoff recipient participation shall not transfer authority from SCF or Nexus. It shall not create procurement approval, financeability, insurability, public authority approval, deployment authorization, employment obligation, or execution unless separately and lawfully established by the recipient and competent actors.

***

## **17.3 Public Authority Interface**

### **17.3.1 Public Authority Learning Role.**

17.3.1.1 **SCF shall treat public authority participation as public authority learning by default.** Public authorities may participate in SCF to understand workforce capability, skill needs, training pathways, credential systems, public employment service gaps, TVET modernization, public sector capacity, AI-era work, green transition skills, disaster resilience skills, public-safe reporting, National Portfolio needs, Nexus Universe preparation, and lawful handoff literacy.

17.3.1.2 Public authority learning may support policy understanding, capacity mapping, public service workforce planning, public employment service modernization, TVET system learning, public authority training needs, resilience planning, digital trust literacy, and public-good skill infrastructure.

17.3.1.3 Public authority participation shall not by itself create official approval, regulatory endorsement, public finance allocation, procurement decision, credential recognition, professional licensing, public warning, emergency command, public authority adoption, or execution authority.

17.1.3.4 Public authority learning records shall include scope, participants, purpose, materials reviewed, boundary notices, data restrictions, public-safe status, unresolved questions, correction pathway, and archive rule.

### **17.3.2 Workforce Policy Learning.**

17.3.2.1 Public authorities may use SCF as a learning environment for workforce policy questions, including skill gaps, transition pathways, AI-era work, green skills, resilience skills, public sector capacity, youth employment pathways, displaced worker support, informal worker recognition, migrant and refugee skill recognition, disability inclusion, regional workforce disparities, and labor-market intelligence.

17.3.2.2 Workforce policy learning shall be structured around evidence, public-good purpose, worker protections, equity, accessibility, national ownership, official data limitations, employer and worker input, correctionability, and public-safe reporting.

17.3.2.3 Workforce policy learning shall not be represented as official policy, law, regulation, grant allocation, procurement rule, credential recognition, employment service determination, immigration decision, wage policy, or public authority approval unless separately issued by a competent public authority through lawful processes.

### **17.3.3 TVET System Learning.**

17.3.3.1 Public authorities, TVET bodies, technical institutes, and education agencies may interface with SCF to learn from competency maps, WILP models, micro-credential evidence, labor-market intelligence, employer and worker signals, National Skills Maps, AI-era work redesign, green and resilience skills, public-good software pathways, and Nexus Academy / Risk Academy structures.

17.3.3.2 TVET system learning may support modernization of curricula, occupational standards discussions, work-integrated pathways, recognition of prior learning, learner records, digital credentials, accessibility, and public-good capability formation.

17.3.3.3 SCF shall not replace TVET authorities, education ministries, accreditation bodies, qualification frameworks, institutional governance, professional bodies, public employment services, or competent public authorities. SCF outputs may inform such actors but shall not bind them by implication.

### **17.3.4 Public Employment Service Learning.**

17.3.4.1 Public employment services may interface with SCF to learn from labor-market intelligence, skills gap records, transition pathways, ILA records where lawfully shared, employer-readable portfolios, WILP host maps, micro-credential maps, National Skills Maps, and sector skill compacts.

17.3.4.2 Public employment service learning may support reskilling, upskilling, displacement response, youth pathways, migrant and refugee skill recognition, disability inclusion, rural access, crisis recovery, and worker transition support.

17.3.4.3 SCF shall not make public employment decisions, assign benefits, determine eligibility, provide immigration status, guarantee job placement, issue public employment service determinations, or substitute for public employment authority.

### **17.3.5 Credential Authority Interface.**

17.3.5.1 Credential authorities, qualification bodies, professional bodies, accreditation bodies, education institutions, and public authorities may interface with SCF to understand micro-credentials, digital badges, competency evidence, RPL pathways, skills wallets, portfolio records, WILP evidence, and public-good contribution records.

17.3.5.2 Credential authority interface may support mapping, comparison, evidence review, quality discussion, interoperability, portability, and correction discipline.

17.3.5.3 SCF credential records shall not create legal equivalence, degree status, professional license, regulated credential recognition, accreditation, qualification framework recognition, immigration recognition, procurement qualification, or public authority approval unless separately and lawfully recorded by the competent authority.

### **17.3.6 Public Sector Workforce Capacity.**

17.3.6.1 SCF may support public sector workforce capacity learning by identifying skills and competencies needed for public-safe reporting, disaster risk reduction, disaster risk finance literacy, disaster risk intelligence, WFEH-B systems, AI governance, data stewardship, cyber resilience, privacy, geospatial literacy, digital twins, public authority learning rooms, controlled data rooms, secure rooms, public procurement literacy, regulatory perimeter literacy, and lawful handoff literacy.

17.3.6.2 Public sector workforce capacity records may support National Portfolio inputs, Academy pathways, Risk Academy modules, public authority learning records, Competence Cell formation, Nexus Universe arenas, and public-safe Reports.

17.3.6.3 Such records shall not create public service appointment, civil service qualification, official training mandate, public authority decision, public procurement authority, emergency command authority, public warning authority, or public finance allocation.

### **17.3.7 Public Authority Data Controls.**

17.3.7.1 Public authority data used in SCF shall be subject to strict data controls, including purpose limitation, data minimization, access control, confidentiality, public-safe transformation, privacy, cross-border restrictions, retention, deletion, sealing, archive, audit records, and correction.

17.3.7.2 Public authority-sensitive data shall not be converted into open data, Marketplace objects, employer-readable profiles, AI training data, public Reports, dashboards, or handoff packages unless separately authorized, reviewed, transformed, and recorded.

17.3.7.3 Public authority participation shall not authorize SCF to publish restricted data, disclose confidential information, issue official statistics, create public authority records, make regulatory determinations, or release public warnings.

### **17.3.8 No Public Authority Approval by Participation.**

17.3.8.1 No participation by a public authority, public official, ministry, agency, municipality, regulator, public employment service, public education body, public finance actor, emergency management body, public health authority, or public procurement body shall constitute approval, endorsement, adoption, certification, credential recognition, procurement decision, public finance allocation, public warning, emergency command, consent, or execution authority by implication.

17.3.8.2 Public authority participation shall be described accurately as learning, dialogue, evidence review, capacity-building, consultation, observation, or interface participation unless a competent public authority separately records a different legal status through lawful processes.

***

## **17.4 Labor and Worker Organization Interface**

### **17.4.1 Worker Voice.**

17.4.1.1 **SCF shall treat worker voice as essential evidence for competence, job quality, transition design, WILP integrity, AI-era work redesign, fair work safeguards, and labor-market intelligence.** Worker organizations, unions, cooperatives, professional associations, worker centers, informal worker groups, migrant worker organizations, disability advocates, youth groups, community organizations, and worker representatives may provide input into SCF.

17.4.1.2 Worker voice may address:\
(a) actual task performance;\
(b) skill gaps;\
(c) training relevance;\
(d) job quality;\
(e) workplace safety;\
(f) AI and algorithmic management impacts;\
(g) unpaid labor risks;\
(h) surveillance concerns;\
(i) transition barriers;\
(j) grievance and correction needs.

17.4.1.3 Worker voice shall be protected against tokenization, retaliation, extractive consultation, employer capture, data misuse, public display without consent, and overclaim.

17.4.1.4 Worker participation shall not itself create consent to data use, employer validation, public authority approval, labor agreement modification, union endorsement, employment commitment, or execution authority.

### **17.4.2 Job Quality Review.**

17.4.2.1 SCF shall incorporate job quality review into employer, WILP, sector, transition, and labor-market interfaces. Job quality review shall evaluate whether pathways support decent work, safe work, fair pay awareness, non-exploitation, worker voice, accessibility, inclusion, dignity, privacy, and sustainable career mobility.

17.4.2.2 Job quality review may consider:\
(a) workload;\
(b) pay awareness;\
(c) safety;\
(d) stability;\
(e) supervision quality;\
(f) harassment risk;\
(g) data and surveillance practices;\
(h) AI management practices;\
(i) advancement pathways;\
(j) grievance channels.

17.4.2.3 Job quality review shall not create wage determination, labor-law ruling, employment classification, collective bargaining outcome, regulatory finding, public authority decision, or employer certification unless separately issued by competent authority.

### **17.4.3 Transition Support.**

17.4.3.1 Labor and worker organizations may contribute to transition support for displaced workers, mid-career workers, informal workers, gig workers, platform workers, public sector workers, climate-affected workers, disaster-affected workers, migrants, refugees, youth, women, people with disabilities, rural workers, and underrepresented groups.

17.4.3.2 Transition support may include pathway review, RPL input, skills mapping, bridge learning, WILP safeguards, worker data protection, grievance routes, accessibility support, AI-era work literacy, green skills pathways, and public-good contribution pathways.

17.4.3.3 Transition support shall not be represented as job placement, wage guarantee, employment agency activity by default, immigration assistance, professional licensing, public authority approval, procurement qualification, or execution.

### **17.4.4 Fair Work Safeguards.**

17.4.4.1 Labor and worker organizations may assist SCF in designing and reviewing fair work safeguards for WILPs, apprenticeships, internships, practice environments, Foundry Bounties, micro-production, volunteer contributions, open-source contributions, sector skill compacts, and employer-hosted learning.

17.4.4.2 Fair work safeguards shall include:\
(a) no disguised employment;\
(b) no unpaid substitution of regular labor;\
(c) safe work controls;\
(d) workload limits;\
(e) clear support or compensation status;\
(f) anti-harassment protections;\
(g) accessible participation;\
(h) youth protections;\
(i) worker data protection;\
(j) grievance and correction channels.

17.4.4.3 Fair work safeguards shall be recorded, reviewed, corrected, and archived. Failure to apply such safeguards may trigger correction, suspension, removal, public-safe notice, or escalation.

### **17.4.5 Apprenticeship and Training Quality.**

17.4.5.1 Labor and worker organizations may participate in apprenticeship and training quality review to ensure that work-integrated pathways provide meaningful learning, fair treatment, adequate supervision, safe work, transferable skills, recognized evidence, and protection from exploitation.

17.4.5.2 Apprenticeship and training quality review may consider:\
(a) learning objectives;\
(b) mentor quality;\
(c) task relevance;\
(d) progression;\
(e) evidence quality;\
(f) workload;\
(g) safety;\
(h) accessibility;\
(i) grievance access;\
(j) correction history.

17.4.5.3 Apprenticeship and training quality review shall not create legal apprenticeship status, regulated credential approval, employment classification, wage determination, or public authority approval unless separately established by competent processes.

### **17.4.6 AI and Algorithmic Management Impacts.**

17.4.6.1 SCF shall include labor and worker organization input on AI and algorithmic management impacts, including automation exposure, task redesign, surveillance, productivity pressure, bias, discrimination, scheduling algorithms, platform work, worker scoring, workplace monitoring, and AI-assisted assessment.

17.4.6.2 AI and algorithmic management review shall support:\
(a) human-AI task allocation;\
(b) augmentation opportunity mapping;\
(c) displacement risk review;\
(d) bias and harm review;\
(e) worker surveillance limits;\
(f) algorithmic transparency literacy;\
(g) no automated high-stakes employment decision by SCF;\
(h) grievance channels;\
(i) correction;\
(j) archive.

17.4.6.3 SCF shall not automate worker ranking by default, conduct hiring decisions, make employment determinations, authorize workplace surveillance, validate algorithmic management systems, or certify AI workplace tools.

### **17.4.7 Worker Data Rights.**

17.4.7.1 SCF shall treat worker and learner data as sensitive where it may affect employment, reputation, wages, safety, migration status, vulnerability, discrimination risk, or access to opportunity.

17.4.7.2 Worker data controls shall include:\
(a) purpose limitation;\
(b) data minimization;\
(c) consent and permissions;\
(d) access controls;\
(e) portfolio visibility settings;\
(f) no unauthorized scraping;\
(g) no social scoring by default;\
(h) correction and withdrawal rights;\
(i) deletion, sealing, and archive;\
(j) incident response.

17.4.7.3 Worker participation shall not constitute consent for employer access, public display, AI training, third-party profiling, public authority use, immigration use, procurement screening, or ranking beyond the specific recorded permission.

### **17.4.8 Grievance and Correction Pathways.**

17.4.8.1 SCF shall provide grievance and correction pathways for learners, workers, contributors, mentors, reviewers, maintainers, WILP participants, Competence Cell members, and public-good contributors affected by employer, host, sector, credential, data, AI, privacy, labor, or safeguard issues.

17.4.8.2 Grievance and correction pathways shall address:\
(a) inaccurate records;\
(b) credential misuse;\
(c) unfair assessment;\
(d) employer overclaim;\
(e) WILP misclassification;\
(f) exploitation concerns;\
(g) harassment or abuse;\
(h) privacy violations;\
(i) AI or bias harms;\
(j) retaliation or exclusion.

17.4.8.3 Grievance records shall be handled with confidentiality, procedural fairness, protection from retaliation, correctionability, public-safe reporting where appropriate, and archive discipline.

***

## **17.5 Sector Interfaces**

### **17.5.1 Infrastructure and Construction.**

17.5.1.1 SCF shall support infrastructure and construction interfaces by mapping competencies for resilient infrastructure, project preparation literacy, digital design, geospatial data, digital twins, materials, safety, climate adaptation, public procurement literacy, fieldwork safety, community safeguards, and lawful handoff dependency awareness.

17.5.1.2 Infrastructure and construction sector input may inform National Portfolios, WFEH-B portfolios, DRR portfolios, Foundry Builds, Studio simulations, Grid and TRL evidence notes, WILPs, micro-credentials, and Nexus Universe arenas.

17.5.1.3 SCF outputs in this sector shall not create construction approval, engineering license, building permit, procurement recommendation, safety certification, public authority approval, financeability, insurability, or execution authority.

### **17.5.2 Energy and Utilities.**

17.5.2.1 SCF shall support energy and utilities interfaces by mapping competencies for energy transition, grid resilience, distributed energy, renewable energy, energy efficiency, utility continuity, critical infrastructure cybersecurity, OT / IoT systems, edge networks, disaster resilience, public-safe reporting, and lawful handoff literacy.

17.5.2.2 Energy and utility sector input may inform WFEH-B records, National Portfolio records, DRI indicators, Observatory needs, Studio workflows, Foundry Builds, Academy pathways, Risk Academy modules, and lawful handoff packages.

17.5.2.3 SCF shall not create utility approval, grid interconnection authorization, energy certification, environmental approval, procurement status, public finance allocation, operational command, or deployment authorization.

### **17.5.3 Water and Sanitation.**

17.5.3.1 SCF shall support water and sanitation interfaces by mapping competencies for water security, watershed management, hydrological data literacy, drought and flood resilience, water quality monitoring, sanitation systems, community water governance, climate adaptation, public health sensitivity, and public-safe communication.

17.5.3.2 Water and sanitation sector inputs may support WFEH-B portfolios, DRI indicators, Observatory signals, National Portfolios, Studio scenarios, Reports, Academy pathways, and Nexus Universe arenas.

17.5.3.3 SCF shall not create water rights, water quality certification, public health decision, infrastructure approval, public authority warning, procurement preference, financeability, insurability, or execution.

### **17.5.4 Agriculture and Food Systems.**

17.5.4.1 SCF shall support agriculture and food system interfaces by mapping competencies for climate-smart agriculture, food systems resilience, soil health, supply-chain resilience, cold chains, food safety literacy, agri-tech, sensors, biosecurity-sensitive systems, nature-based solutions, community safeguards, and public-safe reporting.

17.5.4.2 Agriculture and food system inputs may inform WFEH-B portfolios, National Portfolios, DRI indicators, Foundry Quests, data builds, Studio scenarios, Academy pathways, Risk Academy modules, and Nexus Universe arenas.

17.5.4.3 SCF shall not create food safety certification, agricultural certification, biosecurity approval, market access, procurement status, public authority decision, financeability, insurability, or deployment authorization.

### **17.5.5 Health and Care.**

17.5.5.1 SCF shall support health and care interfaces by mapping competencies for public health resilience, climate-health risk literacy, One Health literacy, health data protection, care workforce resilience, emergency preparedness, community health, disability inclusion, youth safeguards, protected knowledge, and public-safe reporting.

17.5.5.2 Health and care sector input may inform Academy pathways, Risk Academy modules, National Portfolios, DRI records, public authority learning records, Studio scenarios, and lawful handoff context.

17.5.5.3 SCF shall not provide medical advice, public health orders, clinical certification, health professional licensing, patient care decisions, public health warnings, health data access rights, procurement recommendations, financeability, insurability, or execution authority.

### **17.5.6 Education and Training.**

17.5.6.1 SCF shall support education and training interfaces by mapping competencies, learning outcomes, WILPs, micro-credentials, digital badges, RPL pathways, learner records, skills wallets, faculty capacity, digital learning infrastructure, accessibility, public-safe publication, and credential governance.

17.5.6.2 Education and training sector input may inform Nexus Academy, Risk Academy, ILA, WILPs, credential design, curriculum review, TVET system learning, National Skills Maps, and Nexus Universe learning outputs.

17.5.6.3 SCF shall not replace education institutions, qualification authorities, accreditation bodies, professional bodies, ministries, or competent credentialing authorities, and shall not create degree equivalence, accreditation, professional license, immigration recognition, or public authority approval by implication.

### **17.5.7 Technology and Telecommunications.**

17.5.7.1 SCF shall support technology and telecommunications interfaces by mapping competencies for AI, agentic systems, AI-RAN, O-RAN, telecom, private wireless, edge, cloud, HPC, sovereign compute, secure enclaves, APIs, SDKs, connectors, software maintenance, cybersecurity, digital trust, interoperability, and provider-neutral architecture.

17.5.7.2 Technology and telecommunications sector input may inform Foundry Builds, public-good software, open technical baselines, Studio workflows, Grid and TRL notes, DICE, Nexus Observatory, National Portfolios, Nexus Universe, and lawful handoff context.

17.5.7.3 SCF shall not create telecom approval, spectrum authorization, standards certification, provider validation, procurement preference, security certification, deployment authorization, or execution authority.

### **17.5.8 Cybersecurity and Digital Trust.**

17.5.8.1 SCF shall support cybersecurity and digital trust interfaces by mapping competencies for cyber hygiene, identity and access management, zero trust, secure repositories, dependency literacy, SBOM literacy, vulnerability reporting, incident response, critical infrastructure sensitivity, OT / IoT / edge security, AI security, privacy, and public-safe technical disclosure.

17.5.8.2 Cybersecurity and digital trust input may inform Academy pathways, Risk Academy modules, Foundry secure software controls, DICE, Studio secure-room workflows, public-safe Reports, National Portfolios, and lawful handoff context.

17.5.8.3 SCF shall not create cybersecurity certification, compliance determination, security clearance, vulnerability disclosure authority, public warning, procurement approval, provider validation, deployment authorization, or operational command.

### **17.5.9 Manufacturing and Supply Chains.**

17.5.9.1 SCF shall support manufacturing and supply-chain interfaces by mapping competencies for advanced manufacturing, semiconductors, supply-chain resilience, quality systems, digital manufacturing, robotics, sensors, additive manufacturing, export-control awareness, dual-use sensitivity, circular economy, logistics resilience, and public-safe reporting.

17.5.9.2 Manufacturing and supply-chain input may support National Portfolios, Technology Portfolios, Foundry Builds, Studio simulations, Academy pathways, Risk Academy modules, Nexus Universe arenas, and handoff-context packages.

17.5.9.3 SCF shall not create manufacturing certification, export-control determination, procurement approval, supplier validation, product qualification, financeability, insurability, deployment approval, or execution.

### **17.5.10 Finance, Insurance, and Public Finance Literacy.**

17.5.10.1 SCF shall support finance, insurance, and public finance literacy by mapping competencies for capital-readability, insurance-readiness literacy, disaster-risk-finance literacy, protection-gap literacy, risk-layering literacy, donor-readiness literacy, public finance relevance, diligence-gap literacy, no-reliance discipline, and regulated-perimeter awareness.

17.5.10.2 Finance, insurance, and public finance actors may provide learning signals, diligence questions, risk interpretation needs, insurance-readiness questions, donor-readiness questions, and public finance relevance questions.

17.5.10.3 SCF shall not provide investment advice, insurance advice, underwriting, brokerage, lending, fundraising, donor allocation, public finance allocation, ratings, bankability determinations, financeability determinations, insurability determinations, securities activity, or financial promotion by implication.

### **17.5.11 Emergency Management and Humanitarian Systems.**

17.5.11.1 SCF shall support emergency management and humanitarian interfaces by mapping competencies for disaster preparedness, DRR, DRI, crisis learning, after-action learning, logistics, public-safe risk communication, community safeguards, humanitarian sensitivity, degraded-mode operations, public authority learning, and public warning boundary literacy.

17.5.11.2 Emergency management and humanitarian input may support Risk Academy, DRI, Nexus Observatory, Studio scenarios, National Portfolios, public-safe Reports, Nexus Universe arenas, and lawful handoff context.

17.5.11.3 SCF shall not issue emergency warnings, command emergency response, replace emergency management authorities, determine humanitarian targeting, allocate public resources, create public authority action, or authorize execution.

### **17.5.12 Climate, Nature, and Biodiversity.**

17.5.12.1 SCF shall support climate, nature, and biodiversity interfaces by mapping competencies for climate adaptation, nature-based solutions, biodiversity monitoring, ecosystem services literacy, carbon accounting literacy, environmental monitoring, sensitive species data controls, protected knowledge, Indigenous protocols where applicable, community safeguards, and public-safe environmental communication.

17.5.12.2 Climate, nature, and biodiversity input may support WFEH-B portfolios, DRI, Nexus Observatory, National Portfolios, Studio scenarios, Foundry Builds, Reports, Academy pathways, Risk Academy modules, Nexus Universe arenas, and lawful handoff context.

17.5.12.3 SCF shall not create environmental certification, green claim certification, protected knowledge permission, environmental approval, biodiversity offset approval, public authority decision, procurement preference, financeability, insurability, or execution authority.

***

## **17.6 Sector Skill Compacts**

### **17.6.1 Compact Intake.**

17.6.1.1 **A Sector Skill Compact shall be a recorded, public-good, non-exclusive, non-procurement, non-certifying coordination instrument through which employers, workers, educators, public authority learning participants, sector bodies, civil society, communities, sponsors, providers, and Nexus actors may identify skill needs, competency maps, WILP host opportunities, micro-credential needs, National Portfolio links, public-safe publication pathways, and correction rules.**

17.6.1.2 Compact intake shall include:\
(a) sector identity;\
(b) public-good purpose;\
(c) participating roles;\
(d) demand signals;\
(e) worker voice inputs;\
(f) national or regional context;\
(g) data and confidentiality status;\
(h) conflicts and sponsor/provider interests;\
(i) boundary notices;\
(j) correction and archive rules.

17.6.1.3 Compact intake shall not create legal compact status, procurement framework, credential authority, employer coalition control, public authority adoption, finance commitment, donor commitment, community consent, or execution authority.

### **17.6.2 Demand Signal Review.**

17.6.2.1 Demand signal review shall assess employer, worker, public authority learning, labor-market, technology, crisis, climate, AI, green transition, resilience, and National Portfolio signals before any sector compact is used to shape SCF outputs.

17.6.2.2 Demand signal review shall consider:\
(a) evidence quality;\
(b) representativeness;\
(c) uncertainty;\
(d) labor-market limitations;\
(e) worker protection implications;\
(f) equity implications;\
(g) public-good relevance;\
(h) national ownership;\
(i) sponsor or provider conflicts;\
(j) correction needs.

17.6.2.3 Demand signal review shall not create employer commitment, public authority decision, funding commitment, procurement priority, hiring guarantee, wage promise, certification, or execution.

### **17.6.3 Competency Map.**

17.6.3.1 A Sector Skill Compact may produce a competency map identifying skills, knowledge, abilities, practices, judgment, dispositions, role capabilities, contextual competencies, and evidence requirements relevant to a sector.

17.6.3.2 A competency map may include:\
(a) foundational competencies;\
(b) technical and vocational competencies;\
(c) digital and data competencies;\
(d) AI and human-AI collaboration competencies;\
(e) cyber and digital trust competencies;\
(f) sustainability and resilience competencies;\
(g) public-safe reporting competencies;\
(h) safeguard competencies;\
(i) lawful handoff literacy;\
(j) correction and renewal requirements.

17.6.3.3 A competency map shall not create legal equivalence, professional license, credential recognition, qualification framework adoption, public authority approval, procurement qualification, or employment guarantee.

### **17.6.4 WILP Host Map.**

17.6.4.1 A Sector Skill Compact may produce a WILP Host Map identifying potential hosts, practice environments, supervision capacity, mentor capacity, safety conditions, accessibility conditions, data conditions, AI and tool-use conditions, and grievance channels.

17.6.4.2 WILP Host Maps shall include:\
(a) host identity;\
(b) host role;\
(c) learning scope;\
(d) supervision model;\
(e) safety controls;\
(f) data and confidentiality controls;\
(g) fair work controls;\
(h) accessibility controls;\
(i) correction pathway;\
(j) host boundary notice.

17.6.4.3 A WILP Host Map shall not create employment, hiring commitment, host certification, public authority approval, procurement status, placement guarantee, or execution authority.

### **17.6.5 Micro-Credential Map.**

17.6.5.1 A Sector Skill Compact may produce a Micro-Credential Map identifying proposed micro-credential families, evidence requirements, review levels, expiry or renewal rules, badge metadata, ILA linkage, iCRS linkage, Registry status, Marketplace display eligibility, and correction pathways.

17.6.5.2 Micro-Credential Maps shall be reviewed for:\
(a) evidence basis;\
(b) competency alignment;\
(c) assessment integrity;\
(d) portability;\
(e) accessibility;\
(f) labor-market relevance;\
(g) worker protection;\
(h) public authority boundary;\
(i) professional license boundary;\
(j) correction and withdrawal.

17.6.5.3 A Micro-Credential Map shall not create degree status, professional license, regulated credential recognition, employment guarantee, procurement qualification, public authority approval, deployment authorization, or community consent.

### **17.6.6 National Portfolio Link.**

17.6.6.1 A Sector Skill Compact may link sector skills to National Portfolio needs, including national systems-risk maps, WFEH-B priorities, DRR / DRF / DRI priorities, National Skills Maps, public authority learning records, Core Build requests, Competence Cell workplans, Nexus Universe arenas, and handoff-context dependencies.

17.6.6.2 National Portfolio links shall respect national ownership, national routing, public authority boundaries, public-good purpose, worker protections, community safeguards, data sovereignty, protected knowledge, and correctionability.

17.6.6.3 A National Portfolio link shall not create national policy, public authority approval, public finance allocation, country ranking, procurement priority, financeability, insurability, deployment authorization, community consent, Indigenous consent, or execution.

### **17.6.7 Public-Safe Publication.**

17.6.7.1 A Sector Skill Compact may produce public-safe publications, including competency summaries, sector learning reports, public-safe skills maps, WILP opportunity summaries, micro-credential summaries, labor-market learning notes, and correction notices.

17.6.7.2 Public-safe publication shall include:\
(a) no-employment-guarantee language;\
(b) no-wage-guarantee language;\
(c) no-procurement language;\
(d) no-public-authority-approval language;\
(e) no-professional-license language;\
(f) no-certification-overclaim language;\
(g) no-finance language;\
(h) data limitation statements;\
(i) correction pathway;\
(j) archive status.

17.6.7.3 Public-safe publication shall not create official labor-market statistics, public authority policy, credential recognition, procurement framework, employer commitment, worker consent, financeability, insurability, or execution authority.

### **17.6.8 Correction and Renewal.**

17.6.8.1 Sector Skill Compacts shall be correctable and renewable. Changes in labor markets, technology, AI, climate risk, public authority needs, sector practice, worker voice, credential quality, host quality, safeguard conditions, data rights, or public-good priorities shall trigger review where material.

17.6.8.2 Correction and renewal may include:\
(a) demand signal correction;\
(b) competency map correction;\
(c) WILP host map correction;\
(d) micro-credential map correction;\
(e) National Portfolio link correction;\
(f) public-safe publication correction;\
(g) participant role correction;\
(h) conflict correction;\
(i) withdrawal or suspension;\
(j) archive.

17.6.8.3 Renewal shall not imply endorsement, certification, procurement status, public authority approval, employer commitment, or execution. It shall preserve accuracy, relevance, fairness, public-good discipline, and institutional memory.

***

## **17.7 Interface Boundary Rules**

### **17.7.1 Employer Input Is Not Credential Control.**

17.7.1.1 Employer input, including skill demand submissions, occupation and task reviews, WILP hosting, mentorship, work product review, competence feedback, sector challenge definition, Quest sponsorship, National Portfolio input, and handoff recipient interface participation, shall not create control over SCF credentials, micro-credentials, badges, learning objects, competency maps, assessment methods, Registry records, Marketplace listings, or public-safe publications.

17.7.1.2 Credential control shall remain subject to SCF governance, evidence requirements, review standards, issuer governance, assessor governance, public-good purpose, correctionability, and applicable lawful authority where relevant.

### **17.7.2 Public Authority Participation Is Not Approval.**

17.7.2.1 Public authority participation in SCF shall not create approval, endorsement, adoption, public finance allocation, procurement decision, regulatory recognition, professional licensing, official credential recognition, public warning, emergency command, public authority record, or execution authority by implication.

17.7.2.2 Public authority participation shall be described as learning, observation, consultation, evidence review, policy learning, capacity-building, or interface participation unless a competent public authority separately records a different status through lawful processes.

### **17.7.3 Labor-Market Signal Is Not Hiring Commitment.**

17.7.3.1 Labor-market signals, including employer demand, job posting intelligence, skills gaps, wage signals, transition signals, worker feedback, sector compact records, and Marketplace demand signals, shall not create hiring commitments, job offers, wage guarantees, placement guarantees, visa commitments, employment eligibility, or employment decisions.

17.7.3.2 Labor-market signals shall be interpreted as evidence subject to uncertainty, incompleteness, bias, correction, and context.

### **17.7.4 Sector Compact Is Not Procurement Framework.**

17.7.4.1 No Sector Skill Compact, competency map, WILP host map, micro-credential map, National Portfolio link, public-safe publication, or sector challenge record shall constitute a procurement framework, vendor list, supplier approval, tender requirement, preferred-provider system, purchasing recommendation, financeability statement, insurability statement, or public authority procurement decision.

17.7.4.2 Procurement, where applicable, shall remain outside SCF default posture and shall be conducted by competent actors through lawful procurement processes.

### **17.7.5 Host Role Is Not Certification Authority.**

17.7.5.1 No employer, university, public authority, community institution, lab, Foundry host, National Node, National Consortium Company, Project SPV, sponsor, provider, or other host shall acquire certification authority, professional licensing authority, credential approval authority, public authority status, deployment authority, procurement authority, or execution authority merely by hosting WILPs, practice environments, apprenticeships, internships, Studio exercises, Foundry contributions, or learning activities.

17.7.5.2 Host feedback may be used as evidence only within recorded scope and subject to review, privacy controls, conflict disclosure, correction, and archive.

### **17.7.6 Worker Participation Is Not Consent to Data Use Beyond Record.**

17.7.6.1 Worker, learner, contributor, mentor, reviewer, maintainer, WILP participant, or community participation in SCF shall not create consent to employer access, public display, AI training, third-party profiling, automated ranking, public authority use, immigration use, procurement screening, or data sharing beyond the specific recorded permission.

17.7.6.2 Worker and learner data shall remain subject to privacy, data protection, purpose limitation, consent and permission, access control, portfolio visibility settings, correction rights, withdrawal rights, deletion, sealing, archive, and incident response.

***

## **17.8 Final Part XVII Operating Statement**

17.8.1 SCF shall treat employer, industry, public authority, labor, worker organization, and sector interfaces as essential evidence channels for dynamic competency formation, but shall preserve public-good purpose, learner protection, worker protection, national ownership, credential integrity, data protection, public authority boundaries, sponsor and provider neutrality, correctionability, and lawful handoff discipline.

17.8.2 Employers may submit demand signals, review occupations and tasks, host WILPs, provide mentorship, review work products, provide competence feedback, define sector challenges, sponsor Foundry Quests, contribute National Portfolio input, and participate as lawful handoff-context recipients, but such participation shall not create curriculum control, credential control, employment commitments, procurement status, public authority approval, financeability, insurability, deployment authorization, or execution authority.

17.8.3 Public authorities may participate in workforce policy learning, TVET system learning, public employment service learning, credential authority interface discussions, public sector workforce capacity learning, and public authority data-controlled environments, but such participation shall not create official approval, regulatory endorsement, public finance allocation, procurement decision, credential recognition, public warning, emergency command, public authority action, or execution.

17.8.4 Labor and worker organizations shall be recognized as essential participants in SCF because worker voice, job quality review, transition support, fair work safeguards, apprenticeship and training quality, AI and algorithmic management review, worker data rights, and grievance pathways are necessary to prevent skill systems from becoming exploitative, exclusionary, extractive, or captured.

17.8.5 Sector interfaces shall allow SCF to map competencies for infrastructure and construction, energy and utilities, water and sanitation, agriculture and food systems, health and care, education and training, technology and telecommunications, cybersecurity and digital trust, manufacturing and supply chains, finance and insurance literacy, emergency management and humanitarian systems, and climate, nature, and biodiversity, while preserving the rule that sector input does not create certification, procurement, public authority approval, professional licensing, financeability, insurability, deployment authorization, or execution.

17.8.6 Sector Skill Compacts shall provide a structured way to record demand signals, competency maps, WILP host maps, micro-credential maps, National Portfolio links, public-safe publications, and correction and renewal pathways, but shall remain non-exclusive, non-procurement, non-certifying, non-financial, non-employment-guaranteeing, and non-executing instruments unless separately and lawfully transformed by competent actors outside SCF default posture.

17.8.7 The final rule of Part XVII is that SCF shall open itself to employers, sectors, public authorities, labor organizations, worker representatives, educators, communities, sponsors, providers, and lawful downstream actors as sources of evidence and participation, while preventing any interface from converting public-good competency infrastructure into private control, credential capture, labor extraction, procurement preference, public authority overclaim, finance overclaim, consent overclaim, 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/xvii.-employers.md?ask=<question>
```

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

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