# IX. CONTRIBUTIONS ## **9.1 iCRS Doctrine** ### **9.1.1 iCRS as Contribution Recognition System.** 9.1.1.1 **Integrated Credits and Rewards System (iCRS)** shall mean the SCF-aligned contribution recognition system through which Nexus records, classifies, recognizes, displays, reviews, corrects, and archives learning contributions, public-good contributions, technical contributions, review contributions, mentorship contributions, Campaign contributions, Foundry contributions, public-safe reporting contributions, correction contributions, and other bounded contribution activity within the Nexus Ecosystem. 9.1.1.2 iCRS shall operate as contribution recognition infrastructure, not as compensation infrastructure by default. It shall recognize contribution as evidence, learning, participation, service, public-good support, portfolio signal, and capability formation, while preserving strict separation from employment, wages, equity, tokens, financial instruments, procurement qualification, public authority approval, professional credentialing, deployment authorization, and execution. 9.1.1.3 iCRS shall be integrated with SCF, ILA, WILPs, Micro-Credentials, Nexus Academy, Risk Academy, Nexus Foundry, Nexus Campaigns, Nexus Reports, Nexus Marketplace, Nexus Registry, Nexus Studio, Nexus Grid, Nexus Universe, Nexus Labs, Risk Agency, DICE, GRIx, DRI, National Portfolios, National Working Groups, Competence Cells, National Nodes, and lawful handoff pathways. 9.1.1.4 iCRS shall recognize contribution only within recorded scope. No contribution record shall imply competence beyond evidence, authority beyond role, reward beyond recorded support terms, employment beyond legal arrangement, or downstream acceptance by employers, public authorities, funders, insurers, donors, sponsors, providers, National Consortium Companies, Project SPVs, or other lawful actors. ### **9.1.2 iCRS as Public-Good Contribution Memory.** 9.1.2.1 iCRS shall preserve **Public-Good Contribution Memory** by recording who contributed, what was contributed, when the contribution was made, under what pathway, under what scope, under what review status, under what support class, under what license or use terms where applicable, and with what correction or archive status. 9.1.2.2 Public-Good Contribution Memory may include:\ (a) learning pathway participation;\ (b) WILP outputs;\ (c) Foundry quests, bounties, builds, and reviews;\ (d) Campaign mobilization;\ (e) data, software, dashboard, ontology, schema, model, API, report, and Studio contributions;\ (f) public-safe reporting;\ (g) translation and accessibility work;\ (h) mentorship and review;\ (i) correction and public repair;\ (j) National Portfolio and Nexus Universe contribution;\ (k) safeguard and community-facing contribution. 9.1.2.3 iCRS shall prevent contribution loss, invisible labor, institutional amnesia, uncredited public-good work, sponsor capture, provider capture, and informal extraction by ensuring contribution records are durable, attributable where appropriate, privacy-protective, reviewable, and correctionable. 9.1.2.4 Public-Good Contribution Memory shall not become social scoring, worker ranking, public authority ranking, country ranking, provider validation, procurement ranking, financial valuation, or reputation scoring by default. ### **9.1.3 iCRS as Skills Evidence Input.** 9.1.3.1 iCRS records may serve as **Skills Evidence Inputs** for SCF competency records, ILA records, Skills Wallet entries, Micro-Credential eligibility, WILP completion, portfolio artifacts, Foundry contributor pathways, reviewer pathways, maintainer pathways, mentor pathways, Risk Agency pathways, National Skills Maps, National Capability Records, and employer-readable summaries. 9.1.3.2 Skills Evidence Inputs shall remain evidence inputs, not automatic competency determinations. A contribution may support evidence of competence only where it is mapped to a competency, reviewed within scope, supported by sufficient documentation, and recorded with level, quality, role, supervision, and limitation metadata. 9.1.3.3 iCRS shall distinguish:\ (a) participation from contribution;\ (b) contribution from accepted contribution;\ (c) accepted contribution from reviewed contribution;\ (d) reviewed contribution from competency evidence;\ (e) competency evidence from Micro-Credential issuance;\ (f) Micro-Credential issuance from professional license;\ (g) contribution recognition from employment or compensation. 9.1.3.4 iCRS records shall not be used for automated hiring, automated ranking, automated exclusion, social scoring, wage determination, public authority decisioning, procurement decisioning, finance decisioning, or insurance decisioning by default. ### **9.1.4 iCRS as Nexus Portfolio Signal.** 9.1.4.1 iCRS may function as a **Nexus Portfolio Signal** by showing where public-good capacity is forming, where learners and contributors are active, which domains attract contribution, where skills gaps remain, where translation and accessibility are needed, where support is useful, where National Portfolios are maturing, and where Nexus Universe preparation is gaining momentum. 9.1.4.2 Portfolio signals may be used for learning design, Campaign planning, Foundry backlog planning, National Working Group formation, Competence Cell formation, National Skills Maps, National Capability Records, Nexus Universe preparation, public-safe reporting, and public-good support planning. 9.1.4.3 Portfolio signals shall be aggregated, privacy-protective, non-ranking, public-safe, and boundary-controlled unless specific contributor-level display is authorized by the contributor and appropriate under applicable privacy, youth, safeguard, and protected knowledge rules. 9.1.4.4 iCRS portfolio signals shall not be converted into country rankings, institutional rankings, worker rankings, provider rankings, procurement preferences, finance signals, insurance scores, public authority performance claims, or labor-market guarantees by default. ### **9.1.5 iCRS as Contributor Motivation Mechanism.** 9.1.5.1 iCRS may support contributor motivation by making public-good contribution visible, portable, meaningful, cumulative, reviewable, and connected to learning, recognition, community, opportunity discovery, pathway progression, and National Portfolio impact. 9.1.5.2 Motivation may be supported through recognition credits, contribution records, public-good contributor profiles, badges, Micro-Credential evidence, Marketplace display where appropriate, Registry linkages where applicable, Nexus Universe visibility, Campaign acknowledgment, Foundry maintainer pathways, mentorship recognition, reviewer recognition, and correction recognition. 9.1.5.3 iCRS motivation design shall avoid manipulative gamification, coercive competition, exploitative reward loops, social scoring, unhealthy comparison, hidden ranking, discriminatory profiling, or contribution pressure that undermines wellbeing, inclusion, fair work, or public-good integrity. 9.1.5.4 iCRS shall reward trustworthy contribution, reviewed contribution, public-safe contribution, accessibility contribution, safeguard contribution, mentorship contribution, and correction contribution, not merely volume, speed, visibility, or popularity. ### **9.1.6 iCRS Without Wage, Employment, Equity, Token, Finance, or Procurement Claim by Default.** 9.1.6.1 iCRS credits, rewards, records, badges, recognition entries, value reports, support-linked records, and contribution profiles shall not constitute wages, salary, employment compensation, equity, tokens, securities, financial instruments, investment rights, profit-sharing rights, ownership rights, procurement eligibility, vendor status, supplier approval, public finance eligibility, or insurance relevance by default. 9.1.6.2 Where a stipend, honorarium, bounty payment, reimbursement, grant, contract payment, wage, scholarship, or other monetary support is lawfully provided, it shall be separately recorded under its applicable legal, fiscal, tax, employment, procurement, donor, or contractual framework. iCRS may reference that support as a record, but shall not convert recognition into compensation. 9.1.6.3 No iCRS credit shall be designed, marketed, transferred, exchanged, redeemed, tokenized, collateralized, securitized, traded, or represented as currency or financial value by default. 9.1.6.4 iCRS shall preserve a hard boundary between recognition and finance. ### **9.1.7 iCRS Correctionability.** 9.1.7.1 iCRS shall be correctionable. Contribution records, credits, badges, value statements, contributor profiles, public displays, Registry links, Marketplace links, ILA links, Micro-Credential links, WILP links, and National Portfolio signals may be corrected, clarified, downgraded, suspended, withdrawn, superseded, archived, or publicly repaired where necessary. 9.1.7.2 Correction triggers may include inaccurate attribution, duplicate contribution, inflated claim, omitted contributor, incorrect role, incorrect evidence, false contribution, plagiarism, AI misuse, data misuse, IP misuse, license error, privacy breach, public-safe overclaim, sponsor overclaim, provider overclaim, procurement overclaim, employment overclaim, safeguard breach, protected knowledge issue, or contribution quality failure. 9.1.7.3 Correction shall propagate to affected ILA records, Skills Wallet entries, Micro-Credential eligibility records, public profiles, Marketplace displays, Registry records, Reports, Campaign pages, Foundry records, National Portfolio summaries, and Nexus Universe displays where applicable. 9.1.7.4 Correction of contribution shall not be treated as reputational punishment when performed responsibly. Responsible correction may itself be recognized as public-good contribution. ### **9.1.8 iCRS Archive.** 9.1.8.1 iCRS shall preserve contribution records through archive rules that distinguish current contribution, historical contribution, superseded contribution, withdrawn contribution, corrected contribution, non-continuing contribution, and archived contribution. 9.1.8.2 Archive records shall include contributor identity or privacy-preserving identifier where appropriate, contribution class, pathway, date, version, review status, support status, correction history, visibility status, rights status, current relevance, successor object where applicable, and not-current notice where required. 9.1.8.3 Archive shall preserve institutional memory without creating current authority. Archived contribution shall not be displayed as current standing, current competence, current maintainer status, current reviewer status, current support status, current credential, or current endorsement. *** ## **9.2 Contribution Classes** ### **9.2.1 Learning Contribution.** 9.2.1.1 **Learning Contribution** shall mean contribution made through participation in SCF, Nexus Academy, Risk Academy, WILPs, Micro-Credentials, Studio exercises, simulations, labs, learning cohorts, peer learning, public-safe reporting exercises, or learner reflection. 9.2.1.2 Learning Contribution may include completing learning objects, contributing discussion, peer feedback, learning artifacts, reflections, learning translations, accessibility improvements, curriculum feedback, learner guides, and pathway testing. 9.2.1.3 Learning Contribution may support ILA records, Micro-Credential evidence, WILP progression, and learning value reporting, but shall not imply competence beyond evidence, credential issuance, employment, or professional status by default. ### **9.2.2 Data Contribution.** 9.2.2.1 **Data Contribution** shall mean contribution to data objects, metadata, data dictionaries, schemas, codebooks, data quality notes, lineage records, data cleaning, public-safe transformation, synthetic data documentation, DRI indicators, Observatory inputs, National Portfolio datasets, or DICE records. 9.2.2.2 Data Contribution shall be governed by data-use labels, AI-use labels, rights review, lineage, sensitivity class, access class, public-safe status, privacy controls, protected knowledge controls, geospatial sensitivity, review status, correction, and archive. 9.2.2.3 Data Contribution shall not create data rights, unrestricted access, data ownership, public authority record status, publication permission, or deployment authorization by default. ### **9.2.3 Software Contribution.** 9.2.3.1 **Software Contribution** shall mean contribution to public-good software, repositories, libraries, services, applications, dashboards, APIs, SDKs, connectors, adapters, command-line tools, notebooks, tests, documentation, infrastructure-as-code, security fixes, accessibility improvements, or reference implementations. 9.2.3.2 Software Contribution shall be governed by repository rules, license terms, contribution terms, code review, maintainer review, dependency review, secret scanning, security review, SBOM where applicable, public-safe documentation, support class, correction, and archive. 9.2.3.3 Software Contribution shall not create warranty, security certification, production approval, procurement recommendation, provider validation, deployment authorization, employment, or ownership rights beyond recorded terms. ### **9.2.4 Research Contribution.** 9.2.4.1 **Research Contribution** shall mean contribution to research questions, evidence gaps, literature reviews, method notes, testbed records, dataset records, model cards, benchmark records, scenario records, public-safe summaries, research impact records, or Foundry transfer records. 9.2.4.2 Research Contribution shall be governed by research ethics, data rights, AI-use controls, public-safe publication, protected knowledge controls, community safeguards, public authority boundaries, sponsor and provider controls, dual-use review where applicable, correction, and archive. 9.2.4.3 Research Contribution shall not create approval, certification, policy decision, public authority action, financeability, insurability, community consent, or deployment authorization. ### **9.2.5 Review Contribution.** 9.2.5.1 **Review Contribution** shall mean contribution through structured review of learning objects, credentials, WILP outputs, data objects, software objects, AI outputs, public-safe summaries, safeguards, reports, Marketplace listings, Registry records, Studio workflows, Grid inputs, TRL notes, Campaign materials, or handoff context. 9.2.5.2 Review Contribution shall include reviewer identity or role, review scope, criteria, date, conflict status, outcome, required corrections, limitations, and archive. 9.2.5.3 Review Contribution shall not create certification, public authority approval, professional license, legal opinion, procurement approval, endorsement, deployment authorization, or execution authority by default. ### **9.2.6 Mentorship Contribution.** 9.2.6.1 **Mentorship Contribution** shall mean contribution through learner guidance, WILP supervision, pathway coaching, technical guidance, public-safe writing support, Foundry maintainer support, Risk Academy coaching, Campaign mentorship, community learning support, or reviewer development. 9.2.6.2 Mentorship Contribution shall record mentor role, pathway, learner or group, duration, scope, supervision level, conflicts, safeguarding obligations, youth protection where applicable, and correction or feedback. 9.2.6.3 Mentorship Contribution shall not create employment relationship, professional supervision authority, legal responsibility beyond role, public authority status, or certification authority by default. ### **9.2.7 Translation Contribution.** 9.2.7.1 **Translation Contribution** shall mean contribution to language translation, localization, terminology mapping, plain-language adaptation, accessibility-oriented rewriting, cultural-context adaptation, public-safe translation, or national-context translation. 9.2.7.2 Translation Contribution shall include source version, target language or context, translator role, review status, localization status, limitations, sensitive terminology notes, public-safe status, and correction pathway. 9.2.7.3 Translation Contribution shall not constitute substantive approval, legal equivalence, public authority adoption, official translation, community consent, or standards adoption by default. ### **9.2.8 Accessibility Contribution.** 9.2.8.1 **Accessibility Contribution** shall mean contribution to accessible formats, screen-reader compatibility, alt text, captions, transcripts, plain-language summaries, low-bandwidth versions, mobile-first access, disability inclusion review, inclusive design, usability improvements, and accessible learning pathways. 9.2.8.2 Accessibility Contribution shall be recorded with object class, accessibility need addressed, review status, user testing where applicable, limitations, correction pathway, and archive. 9.2.8.3 Accessibility Contribution shall not create legal compliance determination, certification of accessibility, or public authority approval unless separately and lawfully recorded. ### **9.2.9 Campaign Contribution.** 9.2.9.1 **Campaign Contribution** shall mean contribution to Nexus Campaigns through mobilization, public-safe storytelling, volunteer coordination, signatures, pledges, support records, translation, accessibility, outreach, trust and safety, fraud prevention, campaign dashboards, public Reports, support ledgers, Campaign correction, or Nexus Universe preparation. 9.2.9.2 Campaign Contribution shall be governed by no-mandate, no-vote, no-finance, no-consent, no-public-authority, no-execution, sponsor-boundary, provider-boundary, trust and safety, privacy, and correction rules. 9.2.9.3 Campaign Contribution shall not create public mandate, vote, public authority approval, donor commitment, finance commitment, employment, community consent, or execution authority. ### **9.2.10 Foundry Contribution.** 9.2.10.1 **Foundry Contribution** shall mean contribution through Nexus Foundry and BuildGrid, including quests, bounties, builds, micro-production tasks, maintainer work, documentation, testing, data pipelines, dashboards, Studio workflows, Marketplace object builds, Registry record builds, Grid input builds, TRL evidence builds, National Portfolio builds, Reports builds, Campaign builds, and handoff dependency builds. 9.2.10.2 Foundry Contribution shall be scoped, reviewed, support-classified, attributed, licensed where applicable, routed, corrected, and archived. 9.2.10.3 Foundry Contribution shall not create employment, procurement qualification, product certification, provider validation, warranty, deployment authorization, or execution. ### **9.2.11 Public-Safe Reporting Contribution.** 9.2.11.1 **Public-Safe Reporting Contribution** shall mean contribution to safe, bounded, accurate, non-overclaiming public communication of Nexus outputs, including summaries, Reports, campaign materials, Registry notices, Marketplace descriptions, DRI summaries, Observatory summaries, National Portfolio summaries, Studio summaries, and handoff-context language. 9.2.11.2 Public-Safe Reporting Contribution shall apply no-warning, no-approval, no-finance, no-procurement, no-certification, no-consent, no-execution, protected knowledge, privacy, and safeguard controls. 9.2.11.3 Public-Safe Reporting Contribution shall not create official communication authority, spokesperson authority, public warning authority, public authority approval, certification, endorsement, or execution authority. ### **9.2.12 Correction Contribution.** 9.2.12.1 **Correction Contribution** shall mean contribution to identifying, documenting, escalating, repairing, revising, withdrawing, superseding, recalling, publicly repairing, archiving, or preventing errors, overclaims, outdated records, unsafe outputs, misleading displays, boundary violations, data issues, AI issues, cyber issues, safeguard issues, or credential issues. 9.2.12.2 Correction Contribution shall be positively recognized where it improves trust, safety, accuracy, public-good discipline, inclusion, accessibility, or boundary integrity. 9.2.12.3 Correction Contribution shall not be suppressed because it is inconvenient, reputationally uncomfortable, or contrary to sponsor, provider, institutional, or contributor preferences. *** ## **9.3 Credit and Reward Types** ### **9.3.1 Recognition Credits.** 9.3.1.1 **Recognition Credits** shall be non-monetary iCRS records acknowledging participation, contribution, review, mentorship, correction, accessibility, translation, public-safe reporting, Foundry work, Campaign work, or other public-good effort. 9.3.1.2 Recognition Credits shall record contribution class, contribution scope, pathway, date, evidence basis, review status, public display status, and correction pathway. 9.3.1.3 Recognition Credits shall not be currency, wages, tokens, equity, financial instruments, procurement status, employment status, or credential status by default. ### **9.3.2 Learning Credits.** 9.3.2.1 **Learning Credits** shall record contribution to learning pathways, including course participation, module completion, peer learning, reflection, WILP participation, Studio exercises, Risk Academy work, and learning artifact development. 9.3.2.2 Learning Credits may support ILA records, learning progression, Micro-Credential eligibility, WILP completion, and competency evidence where reviewed. 9.3.2.3 Learning Credits shall not be academic credit, degree credit, professional credit, continuing education unit, public authority training credit, or certification credit unless separately and lawfully recognized by a competent institution. ### **9.3.3 Contribution Credits.** 9.3.3.1 **Contribution Credits** shall recognize accepted contribution to public-good work objects, including data, software, Reports, Campaigns, Foundry builds, Marketplace objects, Registry records, Studio outputs, Grid inputs, TRL notes, DRI summaries, Observatory summaries, National Portfolio objects, and handoff dependency notes. 9.3.3.2 Contribution Credits shall distinguish submitted, accepted, reviewed, incorporated, published, archived, corrected, withdrawn, and superseded contributions. 9.3.3.3 Contribution Credits shall not create employment, ownership, payment, procurement qualification, endorsement, or execution by implication. ### **9.3.4 Review Credits.** 9.3.4.1 **Review Credits** shall recognize structured review work performed within defined scope, criteria, conflict rules, and review status. 9.3.4.2 Review Credits may support reviewer pathway records, maintainer pathway records, Micro-Credential eligibility, ILA records, and National Capability Records. 9.3.4.3 Review Credits shall not constitute certification authority, public authority approval, legal opinion, procurement approval, professional license, endorsement, or deployment authorization. ### **9.3.5 Mentor Credits.** 9.3.5.1 **Mentor Credits** shall recognize mentorship, coaching, supervision, pathway guidance, learner support, WILP supervision, Foundry guidance, Risk Academy coaching, public-safe reporting support, and reviewer development. 9.3.5.2 Mentor Credits shall record mentor role, learner or cohort context, pathway, scope, duration, feedback status, safeguarding obligations where applicable, and correction pathway. 9.3.5.3 Mentor Credits shall not create employment, professional supervisory license, teaching certification, public authority status, or credentialing authority by default. ### **9.3.6 Bounty Recognition Records.** 9.3.6.1 **Bounty Recognition Records** shall document contribution to scoped bounty opportunities, including task scope, bounty class, expected output, review criteria, contributor role, support or reward terms where applicable, acceptance status, correction status, and archive. 9.3.6.2 Bounty Recognition Records shall distinguish non-monetary bounty recognition from lawful monetary bounty payment, stipend, honorarium, reimbursement, contract payment, or other support. 9.3.6.3 Bounty Recognition Records shall not create employment, wages, equity, tokens, procurement qualification, ownership, warranty, deployment authorization, or execution. ### **9.3.7 Support-Linked Recognition Records.** 9.3.7.1 **Support-Linked Recognition Records** may document contributions made with support from sponsors, donors, hosts, providers, universities, public authorities, National Nodes, National Consortiums, or other lawful supporters. 9.3.7.2 Such records shall distinguish support from control. They shall identify sponsor or supporter role, support type, support boundary, conflict status, public display status, and no-control notice. 9.3.7.3 Support-linked recognition shall not create sponsor ownership, provider validation, pay-to-prioritize, pay-to-validate, procurement preference, endorsement, finance commitment, or public authority approval. ### **9.3.8 Non-Monetary Recognition.** 9.3.8.1 Non-monetary recognition may include acknowledgments, badges, certificates of participation within scope, contributor profiles, public-good contributor display, Nexus Universe recognition, Campaign recognition, Foundry maintainer pathway recognition, reviewer recognition, mentorship recognition, accessibility recognition, translation recognition, and correction recognition. 9.3.8.2 Non-monetary recognition shall be inclusive, fair, evidence-based, reviewable, privacy-respecting, non-exploitative, and correctionable. 9.3.8.3 Non-monetary recognition shall not be represented as compensation, employment, professional qualification, procurement status, financial value, or public authority approval. ### **9.3.9 Stipend or Honorarium Records Where Lawful.** 9.3.9.1 Where stipends, honoraria, reimbursements, or comparable support are lawfully provided, iCRS may record their existence as support records connected to contribution records. 9.3.9.2 Such records shall state support type, lawful basis, scope, eligibility, amount or category where appropriate, payment status, tax or reporting responsibility where applicable, non-employment status where applicable, dispute pathway, and correction process. 9.3.9.3 Stipend or honorarium records shall not convert iCRS credits into wages, employment, equity, tokens, financial instruments, procurement qualification, or entitlement to future support. ### **9.3.10 Correction of Credits.** 9.3.10.1 Credits and rewards shall be correctable. Correction may include metadata correction, attribution correction, duplicate removal, role clarification, review-status correction, support-status correction, public display correction, downgrade, suspension, withdrawal, reissue, archive, or public repair. 9.3.10.2 Credit correction shall protect contributors from inaccurate omission and inaccurate overclaim. 9.3.10.3 Where correction affects Micro-Credentials, ILA records, WILP records, Marketplace profiles, Registry records, Reports, National Portfolios, or Nexus Universe displays, correction shall propagate where applicable. *** ## **9.4 Integrated Value Reporting** ### **9.4.1 Value Reporting Defined.** 9.4.1.1 **Integrated Value Reporting** within iCRS shall mean the structured reporting of public-good value, learning value, contribution value, evidence value, resilience value, national capability value, support value, and correction value arising from contributions recorded under SCF. 9.4.1.2 Integrated Value Reporting shall be designed for learning, accountability, public-good stewardship, National Portfolio intelligence, Campaign planning, Foundry planning, Academy improvement, donor and sponsor transparency, and public-safe reporting. 9.4.1.3 Value reporting shall not be financial valuation by default. It shall not convert contribution into money, equity, tokens, compensation, investment value, procurement value, insurance value, accounting value, or public finance value unless separately and lawfully governed. ### **9.4.2 Public-Good Value.** 9.4.2.1 **Public-Good Value** shall refer to the usefulness of a contribution for shared learning, resilience, risk reduction, capability formation, public-safe knowledge, open technical baselines, public-good software, data commons, accessibility, inclusion, correction, and lawful handoff context. 9.4.2.2 Public-Good Value may be described qualitatively or through bounded non-financial indicators such as reuse, accessibility improvement, language availability, public-safe publication, evidence completion, correction completion, National Portfolio relevance, or Nexus Universe readiness. 9.4.2.3 Public-Good Value shall not imply monetary value, procurement value, sponsor value, investor value, or market value by default. ### **9.4.3 Learning Value.** 9.4.3.1 **Learning Value** shall refer to how contribution supports learner development, competency evidence, pathway progression, WILP completion, Micro-Credential eligibility, mentor development, reviewer development, and public-good capability formation. 9.4.3.2 Learning Value may be recorded through ILA, SCF competency records, WILP records, Micro-Credential evidence, learner reflections, mentor verification, peer review, and Academy analytics. 9.4.3.3 Learning Value shall not guarantee credential issuance, employment, wage outcomes, professional qualification, public authority recognition, or procurement status. ### **9.4.4 Contribution Value.** 9.4.4.1 **Contribution Value** shall refer to the substance, quality, effort, usefulness, review status, and public-good relevance of a contribution. 9.4.4.2 Contribution Value shall consider role, scope, complexity, originality, review acceptance, reusability, documentation quality, public-safe status, accessibility, correction handling, and support class. 9.4.4.3 Contribution Value shall not become a contributor ranking, productivity score, wage proxy, financial value, or employment score by default. ### **9.4.5 Evidence Value.** 9.4.5.1 **Evidence Value** shall refer to the extent to which a contribution strengthens evidence, methods, data quality, reproducibility, reviewability, transparency, public-safe publication, or readiness context. 9.4.5.2 Evidence Value may support Registry records, Marketplace listings, Reports, Studio workflows, Grid inputs, TRL notes, DRI records, Observatory records, National Portfolio records, and handoff dependency packages. 9.4.5.3 Evidence Value shall not be certification, approval, validation, financeability, insurability, procurement readiness, or deployment authorization. ### **9.4.6 Resilience Value.** 9.4.6.1 **Resilience Value** shall refer to the contribution’s relevance to all-hazards resilience, WFEH-B systems, DRR, DRF literacy, DRI, climate adaptation, infrastructure continuity, public health resilience, cyber-physical resilience, supply-chain resilience, community resilience, and degraded-mode awareness. 9.4.6.2 Resilience Value may inform National Portfolios, Campaigns, DRI summaries, Reports, public authority learning, Nexus Universe arenas, and lawful handoff context. 9.4.6.3 Resilience Value shall not constitute public warning, official risk rating, public authority decision, emergency command, insurance score, or investment signal. ### **9.4.7 National Capability Value.** 9.4.7.1 **National Capability Value** shall refer to contribution relevance for National Skills Maps, National Capability Records, National Portfolios, National Working Groups, Competence Cells, National Nodes, public authority learning, Nexus Universe preparation, and lawful handoff literacy. 9.4.7.2 National Capability Value shall be nationally contextualized and shall preserve national ownership, data sovereignty, local language, public authority boundaries, community safeguards, and no-ranking rules. 9.4.7.3 National Capability Value shall not rank countries, certify national readiness, approve public policy, create public authority action, or imply national endorsement. ### **9.4.8 Support Value.** 9.4.8.1 **Support Value** shall refer to the contribution of sponsors, donors, hosts, providers, universities, mentors, public authorities, National Nodes, and other supporters to enabling public-good participation, learning, infrastructure, translation, accessibility, fieldwork, tools, scholarships, or safe practice environments. 9.4.8.2 Support Value shall be reported with support-without-control discipline, including support type, scope, limitations, conflict controls, and no-control notices. 9.4.8.3 Support Value shall not imply ownership, control, validation, endorsement, procurement preference, public authority approval, financial return, or influence over credentialing and contribution recognition. ### **9.4.9 Correction Value.** 9.4.9.1 **Correction Value** shall refer to the trust value created by identifying, correcting, withdrawing, superseding, recalling, publicly repairing, archiving, or preventing errors, overclaims, unsafe outputs, misleading displays, boundary failures, or outdated records. 9.4.9.2 Correction Value shall be treated as positive public-good value because correction preserves trust, safety, accuracy, fairness, public-safe communication, safeguard integrity, and institutional memory. 9.4.9.3 Correction Value shall not be hidden, punished, or treated as failure where correction is responsible and timely. ### **9.4.10 No Financial Valuation by Default.** 9.4.10.1 Integrated Value Reporting shall not assign financial value to credits, contribution, learning, public-good outputs, resilience, national capability, sponsor support, or correction by default. 9.4.10.2 Value reports shall not be financial statements, investment materials, valuation reports, impact-investment claims, donor allocation decisions, procurement scoring tools, insurance scoring tools, public finance records, or accounting records unless separately and lawfully prepared under competent frameworks. 9.4.10.3 Any financial, accounting, investment, insurance, public finance, or procurement use shall occur outside iCRS by competent actors under separate lawful processes and no-reliance boundaries. *** ## **9.5 Contribution Governance** ### **9.5.1 Contribution Intake.** 9.5.1.1 Contribution Intake shall record contributor identity or permitted pseudonym, contribution class, pathway, object, purpose, scope, date, rights status, support status, data-use label, AI-use label, public-safe status, safeguard status where applicable, review needs, attribution preference, display permissions, and correction pathway. 9.5.1.2 Contribution Intake shall prevent unreviewed, unsafe, mislabeled, infringing, confidential, exploitative, protected knowledge, sensitive data, sponsor-captured, provider-captured, or overclaimed contribution from entering iCRS as recognized contribution. 9.5.1.3 Contributions may be accepted, held for review, returned for correction, restricted, rejected, withdrawn, or archived. ### **9.5.2 Contribution Verification.** 9.5.2.1 Contribution Verification shall confirm that a contribution was made, by whom or by what permitted identifier, under what role, through what pathway, with what evidence, and under what rights and review status. 9.5.2.2 Verification may include repository logs, submission records, mentor verification, host verification, peer review, maintainer review, platform records, WILP records, Campaign records, Reports records, Studio logs, Registry entries, Marketplace entries, or contributor attestations. 9.5.2.3 Verification shall not convert contribution into competence, credential, employment, compensation, procurement qualification, endorsement, or execution authority by default. ### **9.5.3 Contribution Review.** 9.5.3.1 Contribution Review shall assess contribution quality, scope, usefulness, evidence basis, public-safe status, data status, AI-use status, cyber status, privacy status, safeguard status, rights status, support status, and correction needs. 9.5.3.2 Review shall be proportionate to risk. Contributions involving AI, data, cyber, privacy, public-safe reporting, protected knowledge, youth, community participation, public authority learning, finance-readiness, insurance-readiness, procurement boundaries, fieldwork, or handoff context shall receive heightened review. 9.5.3.3 Review shall be recorded and shall not be represented as certification, public authority approval, professional license, legal approval, procurement approval, financeability, insurability, deployment authorization, or execution. ### **9.5.4 Contributor Conflicts.** 9.5.4.1 Contributors shall disclose actual, potential, or perceived conflicts where the contribution relates to their employer, sponsor, provider, funder, public authority role, procurement interest, investment interest, insurance interest, political role, community role, or downstream commercial interest. 9.5.4.2 Conflict management may include disclosure, labeling, independent review, restricted display, separation of roles, recusal, additional review, correction, or exclusion. 9.5.4.3 Conflict disclosure shall not automatically disqualify contribution, but undisclosed conflicts may trigger correction, withdrawal, or incident handling. ### **9.5.5 Sponsor and Provider Controls.** 9.5.5.1 Sponsor-supported and provider-supported contributions shall be governed by support-without-control and contribution-without-validation rules. 9.5.5.2 Sponsors and providers shall not control contribution recognition, credit assignment, credential eligibility, public display, Registry status, Marketplace visibility, National Portfolio priority, public authority interpretation, procurement routing, or handoff recommendations. 9.5.5.3 Provider contribution shall not validate the provider’s products, services, platforms, infrastructure, models, datasets, tools, or systems. Sponsor support shall not create ownership, control, endorsement, or priority. ### **9.5.6 Public Display Controls.** 9.5.6.1 Public display of iCRS records shall be controlled by contributor permissions, privacy rules, youth protections, sensitive profile controls, public-safe rules, data rights, IP rules, protected knowledge restrictions, safeguard review, and correction status. 9.5.6.2 Public display may include contributor profiles, badges, credits, contribution summaries, leaderboards only where non-exploitative and non-ranking-by-default controls are met, Campaign acknowledgments, Foundry contributor listings, Reports acknowledgments, Marketplace contributor metadata, and Registry attribution. 9.5.6.3 Public display shall not expose restricted personal data, youth data, sensitive community affiliation, protected knowledge, confidential host information, restricted work products, or unsafe cyber or geospatial information. ### **9.5.7 Contributor Privacy.** 9.5.7.1 Contributor Privacy shall be protected through data minimization, purpose limitation, consent and permission controls, pseudonymity where appropriate, selective disclosure, access controls, display settings, withdrawal options, and correction rights. 9.5.7.2 Contributors shall not be forced to publicize contribution as a condition of learning, fair participation, or recognition where privacy, safety, youth protection, community sensitivity, political sensitivity, employment sensitivity, migration sensitivity, or protected knowledge concerns exist. 9.5.7.3 Contributor analytics shall not be used for hidden ranking, social scoring, automated employment decisions, or discriminatory profiling by default. ### **9.5.8 Contributor Appeals.** 9.5.8.1 Contributors shall have access to appeal or review pathways for omitted contribution, incorrect attribution, incorrect classification, credit denial, credit downgrade, unfair review, conflict mismanagement, display errors, privacy violations, withdrawal, suspension, or correction disputes. 9.5.8.2 Appeal records shall include request, issue, evidence, reviewer, outcome, correction where applicable, and archive. 9.5.8.3 Appeals shall be handled fairly, accessibly, timely, and without retaliation. ### **9.5.9 Credit Withdrawal.** 9.5.9.1 Credits may be withdrawn where they were issued in error, based on false evidence, duplicated, misattributed, unsupported, plagiarized, infringing, affected by misconduct, affected by AI misuse, affected by data misuse, public-safe noncompliant, safeguard noncompliant, or materially misleading. 9.5.9.2 Credit Withdrawal shall update affected iCRS records, ILA records, Micro-Credential eligibility, public profiles, Marketplace displays, Registry records, Reports acknowledgments, Campaign acknowledgments, National Portfolio summaries, and Nexus Universe displays where applicable. 9.5.9.3 Credit Withdrawal may be accompanied by correction, reissue, appeal, public repair, archive, or incident handling. ### **9.5.10 Archive.** 9.5.10.1 Contribution governance shall include archive of contribution records, credits, public displays, withdrawn credits, corrected credits, superseded contributions, deprecated objects, and non-continuing contribution pathways. 9.5.10.2 Archive shall preserve institutional memory while preventing outdated or withdrawn contribution records from being mistaken for current standing. 9.5.10.3 Archive records shall remain subject to privacy, access, protected knowledge, correction, and retention rules. *** ## **9.6 Public-Good Labor Boundary** ### **9.6.1 Volunteer Contribution Boundary.** 9.6.1.1 Volunteer contribution shall be voluntary, scoped, non-coercive, non-exploitative, recordable, and correctable. 9.6.1.2 Volunteer contribution shall not replace regular labor, create employment, waive legal rights, transfer IP beyond agreed terms, require excessive workload, or imply future opportunity. 9.6.1.3 Volunteer contribution may be recognized by iCRS, but recognition shall not be compensation, currency, credential, employment, procurement qualification, or execution authority. ### **9.6.2 Learning Contribution Boundary.** 9.6.2.1 Learning contribution shall be participation or output connected to learning, WILPs, Academy pathways, Risk Academy pathways, Studio exercises, or supervised practice. 9.6.2.2 Learning contribution shall not be used as disguised labor, unpaid operational delivery, or compulsory contribution beyond learning scope. 9.6.2.3 Learning contribution may support competency evidence only where reviewed and mapped. ### **9.6.3 Bounty Contribution Boundary.** 9.6.3.1 Bounty contribution shall be scoped, time-bounded where appropriate, reviewable, support-defined, and governed by clear terms. 9.6.3.2 Bounty contribution may be non-monetary by default or may involve lawful monetary support where separately governed. 9.6.3.3 Bounty contribution shall not create employment, wages, future payment entitlement, equity, token rights, procurement status, product approval, or deployment authorization. ### **9.6.4 Stipend Contribution Boundary.** 9.6.4.1 Stipend-supported contribution shall be recorded clearly with lawful basis, scope, duration, amount or support class where appropriate, expectations, tax or reporting responsibilities where applicable, and non-employment status where applicable. 9.6.4.2 Stipends shall not be used to avoid wage obligations where work is legally employment. 9.6.4.3 Stipend records shall not convert iCRS credits into compensation systems, equity systems, token systems, or employment systems. ### **9.6.5 Contracted Work Boundary.** 9.6.5.1 Contracted work shall be governed by separate lawful agreements. iCRS may record contribution evidence, attribution, output status, and public-good relevance, but shall not replace the contract, payment terms, IP terms, tax obligations, confidentiality terms, insurance terms, or legal obligations. 9.6.5.2 Contracted work records in iCRS shall be labeled so they are not confused with volunteer contribution, learning contribution, or unpaid public-good contribution. 9.6.5.3 Contracted work recognition shall not create procurement preference, endorsement, provider validation, or future contract entitlement. ### **9.6.6 Open-Source Contribution Boundary.** 9.6.6.1 Open-source contribution shall be governed by repository rules, license terms, contribution terms, maintainer governance, code of conduct, security disclosure rules, attribution rules, support class, and correction rules. 9.6.6.2 Open-source contribution may be recognized in iCRS, but shall not create employment, compensation, ownership, warranty, procurement approval, security certification, provider validation, or deployment authorization. 9.6.6.3 Contributor recognition shall respect pseudonymity, privacy, safety, and community governance where appropriate. ### **9.6.7 No Equity or Token Claim by Default.** 9.6.7.1 iCRS credits, contribution records, recognition records, badges, contributor profiles, value reports, bounty records, and support-linked records shall not create equity, ownership, token rights, revenue share, profit share, securities, digital assets, credits redeemable for money, investment rights, or financial instruments by default. 9.6.7.2 No contributor shall represent iCRS records as investable, tradable, transferable for value, redeemable, collateralizable, or monetizable unless a separate lawful framework expressly provides otherwise and the record is clearly separated from default iCRS recognition. 9.6.7.3 iCRS shall maintain public-good recognition without financialization. ### **9.6.8 No Employment by Contribution.** 9.6.8.1 Contribution recorded in iCRS shall not create employment, contractor status, wages, benefits, tax status, work authorization, immigration status, union status, public employment status, or future work entitlement by default. 9.6.8.2 Where employment or contracting exists, it shall be governed separately and recorded accurately. 9.6.8.3 iCRS shall not be used to misclassify workers, avoid labor law, or extract unpaid work. *** ## **9.7 iCRS Boundary Rules** ### **9.7.1 Credit Is Not Currency by Default.** 9.7.1.1 iCRS credit shall not be currency, legal tender, token, points redeemable for money, stored value, payment instrument, voucher, financial asset, security, commodity, or transferable financial unit by default. 9.7.1.2 iCRS credit shall be a recognition and record object unless separately and lawfully governed otherwise outside default iCRS. ### **9.7.2 Recognition Is Not Compensation by Default.** 9.7.2.1 Recognition shall not be compensation, wage, salary, stipend, bounty payment, honorarium, reimbursement, grant, contract payment, or benefit by default. 9.7.2.2 Where compensation or support exists, it shall be separately recorded and governed by the appropriate legal, fiscal, labor, donor, procurement, tax, or contractual framework. ### **9.7.3 Contribution Is Not Employment.** 9.7.3.1 Contribution shall not create employment, contractor status, worker status, wage entitlement, benefits, tax status, immigration status, public employment, or future work entitlement by implication. 9.7.3.2 Contribution pathways shall preserve fair work, anti-exploitation, no disguised labor, and no unpaid substitution rules. ### **9.7.4 Credit Is Not Credential by Default.** 9.7.4.1 iCRS credit shall not be a Micro-Credential, professional credential, certification, degree, license, qualification, public authority credential, or deployment authorization by default. 9.7.4.2 iCRS credit may support credential evidence only where mapped, reviewed, and accepted under SCF credential governance. ### **9.7.5 Value Report Is Not Financial Statement.** 9.7.5.1 Integrated Value Reports shall not be financial statements, accounting reports, valuation reports, investment materials, audit reports, procurement scores, donor allocation decisions, insurance scores, public finance records, or regulated impact claims by default. 9.7.5.2 Value reports shall be public-good learning and stewardship records unless separately and lawfully prepared for another purpose by competent actors. ### **9.7.6 Contributor Standing Is Not Procurement Qualification.** 9.7.6.1 Contributor standing, maintainer standing, reviewer standing, mentor standing, public-good contributor profile, Foundry record, Campaign record, or iCRS record shall not create procurement qualification, preferred supplier status, vendor validation, tender eligibility, public procurement approval, purchasing recommendation, or provider endorsement by default. 9.7.6.2 Procurement decisions must occur through separate lawful processes by competent procurement actors. *** ## **9.8 Final Part IX Operating Statement** 9.8.1 iCRS shall be the contribution-memory and recognition layer of SCF. It shall make public-good work visible, portable, reviewable, meaningful, and correctionable without converting contribution into wages, employment, equity, tokens, financial instruments, procurement qualifications, professional credentials, public authority approvals, deployment authorization, or execution. 9.8.2 iCRS shall recognize learning contribution, data contribution, software contribution, research contribution, review contribution, mentorship contribution, translation contribution, accessibility contribution, Campaign contribution, Foundry contribution, public-safe reporting contribution, and correction contribution. Each contribution shall be scoped, attributed where appropriate, reviewed where necessary, privacy-protective, public-safe, and correctable. 9.8.3 iCRS credits and rewards shall include recognition credits, learning credits, contribution credits, review credits, mentor credits, bounty recognition records, support-linked recognition records, non-monetary recognition, lawful stipend or honorarium records where applicable, and correction of credits. Such records shall remain recognition records unless separately governed under a lawful compensation or support framework. 9.8.4 Integrated Value Reporting shall describe public-good value, learning value, contribution value, evidence value, resilience value, national capability value, support value, and correction value without default financial valuation. Value reporting shall support learning, stewardship, accountability, National Portfolio intelligence, Nexus Universe preparation, and public-good continuity, not investment, procurement, insurance, wage, or public finance claims. 9.8.5 Contribution governance shall require contribution intake, verification, review, conflict management, sponsor and provider controls, public display controls, contributor privacy, appeals, withdrawal, and archive. iCRS shall protect contributors from omission, misattribution, exploitation, hidden ranking, unsafe exposure, and misuse of their work. 9.8.6 The final rule of Part IX is that contribution deserves memory, recognition, and correction; recognition does not become compensation, credit does not become currency, contribution does not become employment, value reporting does not become financial valuation, and contributor standing does not become credential, procurement qualification, public authority approval, or execution authority 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/ix.-contributions.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.