# XIX. CAMPAIGNS

Nexus Agile Framework Campaigns defines the **NAF civic mobilization and participation model** for Campaigns, support, pledges, signatures, volunteers, activation, public-safe storytelling, and lawful handoff awareness. This section explains how **Campaign records, support ledgers, volunteer pathways, and participation tools** mobilize public-good action without creating mandate, consent, procurement status, or execution authority.

This section sets the operating model for **public-good mobilization**, **National Portfolio activation**, **Nexus Universe preparation**, **Campaign platform functions**, **Campaign records**, and **trust and safety governance**. It helps Nexus organize learning, public-safe participation, evidence inputs, support, and volunteer activity while preserving sponsor boundaries, provider neutrality, public authority boundaries, and no-execution discipline.

### What this section covers

* **Mobilization and participation** - Defines Campaigns, signatures, pledges, volunteers, support pathways, and activation across national, regional, and thematic contexts.
* **Tools and records** - Explains Campaign dashboards, storytelling tools, support ledgers, intake records, correction records, and archive records.
* **Governance and boundaries** - Defines claims freezes, data freezes, sponsor controls, fraud controls, trust and safety, and no-mandate rules.

Use this section with [Nexus Agile Framework (NAF)](/organization/operations/frameworks/nexus-agile-framework-naf.md) for the full framework overview, [XVII. REPORTS](/organization/operations/frameworks/nexus-agile-framework-naf/xvii.-reports.md) for public-safe reporting and Campaign reports, [XVI. REGISTRY](/organization/operations/frameworks/nexus-agile-framework-naf/xvi.-registry.md) for Campaign records and status truth, [XVIII. ACADEMY](/organization/operations/frameworks/nexus-agile-framework-naf/xviii.-academy.md) for volunteer and learning pathways, and [XIV. STUDIO](/organization/operations/frameworks/nexus-agile-framework-naf/xiv.-studio.md) for Campaign-linked demonstrations and workflow environments.

## 19.1 Campaigns as Delivery Mobilization

### 19.1.1 Campaigns Defined.

19.1.1.1 Nexus Campaigns shall operate within NAF as structured public-good mobilization pathways through which people, institutions, communities, universities, youth, civil society, sponsors, hosts, providers, public authority learning participants, National Working Groups, Nexus Competence Cells, National Nodes, National Nexus Consortiums, Regional Nexus Consortiums, Global Nexus Consortium interfaces, Nexus Academy, Risk Academy, Nexus Foundry, Nexus Reports, DICE, GRIx, DRI, Nexus Observatory, Nexus Studio, Nexus Grid, Nexus Marketplace, Nexus Registry, Nexus Universe, Nexus Rails, and Nexus Network may organize support, participation, learning, evidence, public-safe communication, and readiness activity around recorded Nexus purposes.

19.1.1.2 Campaigns shall be delivery-mobilization instruments, not execution vehicles. They shall create structured attention, participation, support, signatures, pledges, volunteer pathways, contribution pathways, Docket inputs, evidence inputs, public-safe Reports inputs, Academy routing, Foundry routing, National Portfolio routing, Nexus Universe routing, and lawful handoff context, but shall not create mandate, vote, procurement, finance, insurance, certification, endorsement, consent, public authority action, deployment authorization, operational command, or execution.

19.1.1.3 A Campaign shall be valid within NAF only where its purpose, steward, scope, audience, public-safe status, data-use status, AI-use status, support status, sponsor status, provider status, volunteer status, signature status, pledge status, Docket linkage, National Portfolio linkage where applicable, Nexus Universe linkage where applicable, correction pathway, and archive rule are recorded.

19.1.1.4 Campaigns shall be governed by public-good discipline, non-execution, validity by record, correctionability, public-good firewall, no-conversion, national ownership, public authority learning without substitution, finance-readiness without finance, procurement neutrality, sponsor support without control, provider contribution without validation, participation without consent by implication, open-where-safe and controlled-where-necessary release, and public-safe reporting.

### 19.1.2 Campaigns as Public-Good Mobilization.

19.1.2.1 Campaigns shall mobilize public-good attention, learning, participation, contribution, evidence, support, narrative, community engagement, youth engagement, university engagement, technical contribution, public authority learning, sponsor support, provider contribution, and lawful handoff awareness around Nexus priorities.

19.1.2.2 Public-good mobilization may include calls to learn, calls to participate, calls to contribute, calls to volunteer, calls to join National Working Groups, calls to join Nexus Competence Cells, calls to support Campaigns, calls to join Nexus Universe preparation, calls to review public-safe Reports, calls to submit evidence, calls to submit local knowledge, calls to join Foundry quests, calls to support DRI or Observatory work, and calls to support National Portfolio formation.

19.1.2.3 Campaigns shall be structured to prevent extraction, capture, misinformation, overclaim, tokenization of communities, public authority confusion, sponsor control, provider validation, finance misuse, procurement misuse, consent overclaim, deployment overclaim, and execution overclaim.

19.1.2.4 Public-good mobilization shall remain bounded by the Campaign record. Support for a Campaign shall not mean support for every Nexus activity, support for a provider, support for a project, approval of implementation, public authority action, or community consent.

### 19.1.3 Campaigns as National Portfolio Activation.

19.1.3.1 Campaigns may activate National Portfolios by translating national systems-risk maps, national challenge briefs, evidence needs, Observatory needs, Core Build requests, safeguard records, public authority learning questions, readiness questions, Competence Cell workplans, and Nexus Universe routing needs into public-safe mobilization pathways.

19.1.3.2 National Portfolio Campaigns shall be nationally routed and shall preserve national ownership before local delivery. They may support National Nexus Consortiums, National Councils, National Leadership Councils, National Investors Councils, Helix Councils, National Working Groups, Nexus Competence Cells, National Nodes, universities, communities, public authority learning participants, sponsors, hosts, providers, and lawful handoff recipients, but shall not bypass national pathways.

19.1.3.3 National Portfolio Campaigns shall not rank countries, approve national policy, issue public warnings, allocate public finance, create procurement status, validate providers, grant consent, authorize deployment, or execute projects.

19.1.3.4 National Portfolio activation through Campaigns shall produce records, not authority. Such records may include participation records, support records, signature records, pledge records, volunteer records, evidence inputs, public-safe Reports inputs, Working Group formation records, Competence Cell formation records, Nexus Universe routing records, correction records, and archive records.

### 19.1.4 Campaigns as Nexus Universe Preparation.

19.1.4.1 Campaigns shall operate as preparation pathways for Nexus Universe by mobilizing participants, National Portfolios, Campaign teams, Academy learners, Risk Academy learners, Foundry contributors, Labs contributors, Risk Agency experts, DICE contributors, GRIx contributors, DRI contributors, Observatory contributors, Studio participants, Grid reviewers, Reports authors, Marketplace stewards, Registry stewards, sponsors, hosts, providers, public authority learning participants, communities, youth, universities, and media-safe public narrative actors before the annual Nexus Universe cycle.

19.1.4.2 Nexus Universe preparation Campaigns may support arena readiness, room readiness, public authority learning readiness, readiness-room preparation, capital-reader room preparation, insurance-reader room preparation, donor-reader room preparation, Studio workflow preparation, Foundry backlog preparation, Campaign showcase preparation, National Portfolio presentation preparation, public-safe Report preparation, Marketplace listing preparation, Registry update preparation, and handoff dependency note preparation.

19.1.4.3 Campaigns shall not convert Nexus Universe visibility into endorsement, approval, financeability, procurement readiness, public authority decision, sponsor control, provider validation, consent, deployment authorization, or execution.

19.1.4.4 Nexus Universe Campaign records shall route to Reports, Registry, Marketplace, Studio, Grid, National Portfolios, Nexus Network, Nexus Rails, and lawful handoff context only within recorded scope and release class.

### 19.1.5 Campaigns as Volunteer Mobilization.

19.1.5.1 Campaigns may mobilize volunteers for public-good work, including public-safe communications, translations, accessibility support, community outreach, learning support, Academy support, Risk Academy support, Campaign moderation, Foundry quests, bounty awareness, data annotation where lawful and safe, DRI literacy support, Observatory support, Reports support, Marketplace support, Registry support, Nexus Universe support, National Portfolio support, correction support, and archive support.

19.1.5.2 Volunteer mobilization shall be governed by role definition, scope, time expectations, supervision, data access limits, AI-use limits, public-safe rules, safeguard rules, youth protection where applicable, labor boundary rules, grievance channels, contribution recognition, correction, and archive.

19.1.5.3 Volunteer participation shall not be used to disguise employment, substitute for regular paid labor, avoid procurement, avoid contracting, bypass professional obligations, or transfer execution responsibility to volunteers.

19.1.5.4 Volunteer participation shall not create employment, compensation entitlement, professional qualification, procurement eligibility, public authority role, provider validation, sponsor authority, consent, deployment authorization, or execution.

### 19.1.6 Campaigns as Support Mobilization.

19.1.6.1 Campaigns may mobilize lawful support, including donations, grants, sponsorship, in-kind support, infrastructure support, venue support, cloud or compute support, data support where lawful, software support, communications support, translation support, accessibility support, volunteer support, expert support, university support, host support, and public-good capacity support.

19.1.6.2 Support mobilization shall be recorded through Support Ledgers and Campaign Support Records, including supporter identity where appropriate, support type, support value where lawfully recorded, support restrictions, no-control notice, sponsor-boundary notice, provider-neutrality notice, conflict review, public display rule, correction pathway, and archive rule.

19.1.6.3 Support shall be accepted only where it preserves public-good independence, anti-capture discipline, sponsor support without control, provider contribution without validation, procurement neutrality, finance boundary discipline, data and privacy rules, safeguard rules, and public-safe communications.

19.1.6.4 Support shall not create control, governance rights, editorial control, routing preference, provider validation, procurement preference, financeability, endorsement, public authority approval, consent, deployment authorization, or execution.

### 19.1.7 Campaigns as Evidence and Public-Safe Reporting Inputs.

19.1.7.1 Campaigns may generate evidence inputs, public-safe reporting inputs, DRI inputs, DICE contribution records, GRIx vocabulary needs, Observatory signal needs, National Portfolio insights, community context, learning needs, volunteer capacity records, support records, public narrative signals, demand signals, accessibility needs, translation needs, correction reports, and handoff dependency questions.

19.1.7.2 Campaign evidence shall be classified, reviewed, and transformed before use. Campaign inputs may include lived experience, local knowledge, survey responses, signatures, pledges, volunteer records, support records, public comments, challenge submissions, data contributions, public-safe stories, photographs, maps, technical inputs, and community concerns, but such inputs shall not be treated as verified evidence without review.

19.1.7.3 Campaign evidence and public-safe reporting inputs shall be routed through Dockets, DICE, GRIx, DRI, Observatory, Reports, Studio, Grid, Registry, Marketplace, National Portfolios, Nexus Universe, and handoff context only within recorded scope and after required review.

19.1.7.4 Campaign inputs shall not create public warnings, official findings, ratings, certification, public authority approval, financeability, procurement readiness, consent, deployment authorization, or execution.

### 19.1.8 Campaigns Without Mandate by Implication.

19.1.8.1 No Campaign shall create mandate by implication. Campaign participation, signatures, pledges, donations, sponsorship, volunteer activity, media attention, public authority attendance, provider contribution, community participation, youth participation, university participation, Nexus Universe visibility, or Marketplace discovery shall not create political mandate, public authority mandate, procurement mandate, finance mandate, community mandate, Indigenous mandate where applicable, execution mandate, or public consent.

19.1.8.2 Campaigns may demonstrate interest, participation, need, demand, concern, readiness, support, learning, evidence, and public-good momentum, but they shall not substitute for elections, public authority processes, community consent processes, Indigenous consent processes where applicable, procurement processes, finance processes, insurance processes, technical approval processes, deployment approvals, or lawful execution pathways.

19.1.8.3 Campaign materials shall include no-mandate language where public interpretation risk exists.

19.1.8.4 Any separate mandate, consent, approval, procurement, finance, insurance, deployment, or execution authority must be independently and lawfully created outside the Campaign and separately recorded.

## 19.2 Campaign Classes

### 19.2.1 National Campaigns.

19.2.1.1 National Campaigns shall mobilize country-level public-good participation, learning, support, signatures, pledges, volunteers, evidence inputs, National Working Group formation, Nexus Competence Cell formation, National Portfolio activation, public authority learning, Nexus Universe preparation, and lawful handoff awareness.

19.2.1.2 National Campaigns shall be nationally routed through the appropriate National Nexus Consortium, National Node, National Council, National Working Group, or other recorded national pathway where applicable.

19.2.1.3 National Campaigns shall preserve national ownership and shall not create national endorsement, public authority approval, public finance allocation, procurement status, country ranking, consent, deployment authorization, or execution.

### 19.2.2 Regional Campaigns.

19.2.2.1 Regional Campaigns shall mobilize public-good participation across regional clusters, cross-border corridors, regional systems-risk priorities, WFEH-B systems, DRR, DRF, DRI, climate and nature risks, infrastructure dependencies, supply-chain dependencies, and regional Nexus Universe preparation.

19.2.2.2 Regional Campaigns shall support Regional Nexus Consortiums and national pathways without creating regional supremacy, bypassing countries, overriding public authorities, displacing National Portfolios, or converting regional coordination into execution authority.

19.2.2.3 Regional Campaigns shall not create supranational authority, public authority approval, procurement status, financeability, provider validation, consent, deployment authorization, or execution.

### 19.2.3 Global Campaigns.

19.2.3.1 Global Campaigns shall mobilize worldwide public-good attention, learning, support, participation, evidence inputs, public-safe narrative, Nexus Universe readiness, global-to-regional routing, standards-aware learning, and cross-domain collaboration around recorded Nexus priorities.

19.2.3.2 Global Campaigns shall support global agenda formation without global supremacy. They shall not override regional or national pathways, public authority processes, community processes, Indigenous protocols where applicable, procurement processes, finance processes, or lawful handoff processes.

19.2.3.3 Global Campaigns shall not create endorsement by countries, official multilateral approval, public authority action, finance commitment, procurement status, consent, deployment authorization, or execution.

### 19.2.4 Thematic Campaigns.

19.2.4.1 Thematic Campaigns shall mobilize around a recorded Nexus theme, including WFEH-B, DRR, DRF, DRI, AI governance, cyber resilience, data commons, public-good software, open technical baselines, climate resilience, nature resilience, public health resilience, youth capability, public-safe reporting, workforce resilience, or lawful handoff literacy.

19.2.4.2 Thematic Campaigns may cut across countries, sectors, institutions, disciplines, and Nexus pillars, but shall preserve national routing where country-level activity is implicated.

19.2.4.3 Thematic Campaigns shall not create general authority, certification, public authority approval, financeability, procurement readiness, consent, deployment authorization, or execution.

### 19.2.5 Sector Campaigns.

19.2.5.1 Sector Campaigns shall mobilize public-good participation and learning within sectors, including water, food, energy, health, biodiversity, infrastructure, telecommunications, compute, cybersecurity, finance-readiness literacy, insurance-readiness literacy, education, humanitarian systems, public service, manufacturing, supply chains, and frontier technology sectors.

19.2.5.2 Sector Campaigns may collect sector challenge briefs, workforce needs, data needs, public-safe reporting needs, Foundry build needs, Studio workflow needs, Grid review needs, and handoff dependency questions.

19.2.5.3 Sector Campaigns shall not create sector endorsement, supplier approval, procurement preference, professional certification, public authority approval, financeability, deployment authorization, or execution.

### 19.2.6 WFEH-B Campaigns.

19.2.6.1 WFEH-B Campaigns shall mobilize around water, food, energy, health, biodiversity, nature, cross-system cascades, climate and nature dependencies, infrastructure linkages, community resilience, protected knowledge issues, sensitive geospatial issues, and National Portfolio priorities.

19.2.6.2 WFEH-B Campaigns may support public-safe storytelling, local evidence inputs, Academy learning, Risk Academy learning, DRI literacy, Observatory needs, Studio scenarios, Reports, Foundry builds, Nexus Universe preparation, and lawful handoff dependency awareness.

19.2.6.3 WFEH-B Campaigns shall not create environmental certification, public health decision, public warning, procurement preference, financeability, consent, deployment authorization, or execution.

### 19.2.7 DRR Campaigns.

19.2.7.1 DRR Campaigns shall mobilize learning, participation, public-safe reporting, community resilience awareness, evidence inputs, preparedness literacy, hazard literacy, vulnerability literacy, exposure literacy, resilience-capacity literacy, National Portfolio activation, and public authority learning around disaster risk reduction.

19.2.7.2 DRR Campaigns shall not issue public warnings, emergency alerts, evacuation notices, emergency commands, official risk determinations, public authority approvals, resource allocations, procurement recommendations, or deployment instructions.

19.2.7.3 DRR Campaigns shall preserve no-warning language and shall route urgent safety matters to competent public authorities where appropriate.

### 19.2.8 DRF Campaigns.

19.2.8.1 DRF Campaigns shall mobilize literacy, support, participation, public-good dialogue, protection-gap awareness, risk-layering questions, insurance-readiness questions, donor-readiness questions, public finance relevance questions, capital-readability questions, assumptions, dependencies, and diligence-gap records.

19.2.8.2 DRF Campaigns shall be no-reliance, non-advisory, non-soliciting, non-transactional, no-offer, no-valuation, no-bankability, no-financeability, no-underwriting, no-investment-advice, and no-public-finance-allocation by default.

19.2.8.3 DRF Campaigns shall not create donor commitment, investor commitment, insurance approval, public finance allocation, procurement readiness, financeability, or execution.

### 19.2.9 DRI Campaigns.

19.2.9.1 DRI Campaigns shall mobilize disaster risk intelligence literacy, indicator literacy, signal interpretation, confidence-label literacy, uncertainty-label literacy, public-safe intelligence summaries, dashboard literacy, hotspot literacy, multi-hazard literacy, cascade literacy, National DRI contributions, correction, and archive.

19.2.9.2 DRI Campaigns may support public-safe reporting and community-facing risk literacy, but shall not convert DRI signals into public warnings, ratings, insurance scores, investment signals, public authority decisions, or operational instructions.

19.2.9.3 DRI Campaigns shall include no-warning and no-rating notices wherever risk of misinterpretation exists.

### 19.2.10 Youth Campaigns.

19.2.10.1 Youth Campaigns shall mobilize youth and student participation in learning, public-safe storytelling, Academy pathways, Risk Academy pathways, Campaign tasks, Foundry quests, accessibility contributions, translation contributions, data literacy, AI literacy, cyber literacy, climate and resilience literacy, Nexus Universe preparation, and National Portfolio awareness.

19.2.10.2 Youth Campaigns shall apply youth safeguards, age-appropriate participation, consent and permission controls, privacy controls, data minimization, anti-exploitation controls, accessibility, supervision, public-safe display controls, and correction pathways.

19.2.10.3 Youth Campaigns shall not create employment, credential, procurement, public authority, consent, deployment, or execution status by implication.

### 19.2.11 University Campaigns.

19.2.11.1 University Campaigns shall mobilize students, faculty, researchers, labs, centers, institutes, clinics, capstones, WILPs, service-learning pathways, public-good software projects, data projects, public-safe reporting projects, Foundry builds, Labs streams, National Portfolio contributions, Nexus Universe participation, and lawful handoff literacy.

19.2.11.2 University Campaigns shall preserve the separateness of Nexus learning, university credit, university credentials, research ethics approvals, employment relationships, procurement relationships, public authority relationships, and lawful execution processes.

19.2.11.3 University participation shall not create university endorsement, Nexus certification, public authority approval, procurement status, financeability, consent, deployment authorization, or execution.

### 19.2.12 Public Authority Learning Campaigns.

19.2.12.1 Public Authority Learning Campaigns shall mobilize public servants, agencies, municipalities, emergency management actors, infrastructure authorities, public health actors, regulators, public finance readers, and other public authority-adjacent participants into learning contexts concerning evidence, risk, DRI, GRIx, Observatory, Studio, Grid, TRL, Reports, National Portfolios, Nexus Universe, and handoff dependencies.

19.2.12.2 Public Authority Learning Campaigns shall include no-decision, no-warning, no-command, no-regulatory-action, no-procurement, no-public-finance-allocation, no-permit, no-license, no-approval, and no-execution notices.

19.2.12.3 Public authority participation in a Campaign shall not create public authority approval, official adoption, regulation, permit, license, public warning, public finance allocation, procurement decision, emergency command, deployment authorization, or execution.

### 19.2.13 Nexus Universe Campaigns.

19.2.13.1 Nexus Universe Campaigns shall mobilize annual cycle participation, National Portfolio readiness, arena preparation, room preparation, Core Build readiness, Foundry backlog preparation, Studio workflow preparation, Reports preparation, Marketplace listing preparation, Registry update preparation, Academy learning, Risk Academy learning, public authority learning, capital-reader room preparation, insurance-reader room preparation, donor-reader room preparation, sponsor support, provider contribution, volunteer participation, and public-safe narrative.

19.2.13.2 Nexus Universe Campaigns shall preserve the annual surge principle: temporary concentration, permanent record; open participation, controlled release; global capability, national ownership; public-good learning, lawful handoff; ambition without execution by implication.

19.2.13.3 Nexus Universe Campaigns shall not create endorsement, approval, certification, financeability, procurement readiness, public authority decision, consent, deployment authorization, or execution.

### 19.2.14 Foundry Campaigns.

19.2.14.1 Foundry Campaigns shall mobilize contributors, maintainers, reviewers, mentors, learners, sponsors, providers, hosts, universities, National Working Groups, Competence Cells, and public-good builders around Foundry programs, tracks, quests, bounties, builds, micro-production tasks, open technical baselines, public-good software, data pipelines, dashboards, Studio workflows, Marketplace objects, Registry records, Grid inputs, TRL evidence notes, Reports, Campaign tools, National Portfolio builds, and handoff dependency builds.

19.2.14.2 Foundry Campaigns shall include labor boundary controls, bounty controls, support controls, contribution recognition, public-safe release rules, secure software controls, data and AI-use labels, review gates, correction loops, and archive rules.

19.2.14.3 Foundry Campaigns shall not create employment, procurement qualification, product certification, provider validation, deployment authorization, financeability, or execution.

### 19.2.15 Handoff Awareness Campaigns.

19.2.15.1 Handoff Awareness Campaigns shall mobilize understanding of lawful handoff dependency packages, recipient responsibilities, public authority dependencies, legal dependencies, finance and insurance questions, procurement boundaries, provider-neutrality notes, sponsor-boundary notes, safeguard status, public-safe status, correction pathways, recall pathways, and archive linkage.

19.2.15.2 Handoff Awareness Campaigns shall prepare lawful recipients, National Consortium Companies, Project SPVs, public authorities, providers, operators, contractors, funders, insurers, donors, universities, labs, community actors where appropriate, and other competent lawful actors to understand what NAF can and cannot transfer.

19.2.15.3 Handoff Awareness Campaigns shall transfer understanding, not authority. They shall not authorize implementation, procurement, finance, insurance, public authority action, consent, deployment, operation, contracting, construction, integration, emergency action, public warning, community action, or execution.

## 19.3 Campaign Platform Functions

### 19.3.1 Signature Tools.

19.3.1.1 Signature Tools may be used to record expressions of interest, support, awareness, participation, alignment with a public-good purpose, desire for learning, request for attention, request for National Portfolio consideration, request for public-safe reporting, or support for Nexus Universe preparation.

19.3.1.2 Signature Tools shall record Campaign identity, signatory permission, privacy status, display preference, jurisdiction where appropriate, public-safe notice, no-vote notice, no-mandate notice, no-consent notice, correction pathway, and archive rule.

19.3.1.3 Signatures shall not be votes, public authority mandates, community consent, Indigenous consent where applicable, procurement approvals, finance commitments, public warnings, deployment authorizations, or execution instructions.

### 19.3.2 Pledge Tools.

19.3.2.1 Pledge Tools may record non-binding expressions of intended support, participation, learning, volunteering, contribution, hosting interest, sponsorship interest, provider contribution interest, university participation, public authority learning interest, donor interest, capital-reader interest, insurance-reader interest, or Nexus Universe interest.

19.3.2.2 Pledge Tools shall distinguish non-binding pledges from binding agreements, donations, contracts, grants, sponsorship agreements, procurement commitments, finance commitments, insurance commitments, public authority commitments, and handoff commitments.

19.3.2.3 Pledges shall include no-binding-finance notice, no-procurement notice, no-public-authority-commitment notice, no-consent notice, no-execution notice, correction pathway, and archive rule.

### 19.3.3 Support and Donation Tools Where Lawful.

19.3.3.1 Support and Donation Tools may be used only where lawful, authorized, properly stewarded, transparently recorded, financially controlled, privacy-protected, public-safe, and consistent with the legal status and fiscal arrangements of the relevant Nexus institution or authorized support vehicle.

19.3.3.2 Support and Donation Tools shall record support purpose, supporter identity where appropriate, amount or in-kind description where appropriate, restrictions, acknowledgement rule, sponsor boundary, provider boundary, tax or receipt limitations where applicable, refund or correction pathway where applicable, reporting rule, and archive rule.

19.3.3.3 Support and donations shall not create control, governance rights, procurement preference, provider validation, public authority approval, financeability, investment status, insurance status, consent, deployment authorization, or execution.

### 19.3.4 Volunteer Tools.

19.3.4.1 Volunteer Tools shall support volunteer registration, role matching, availability, skills, learning needs, safeguarding requirements, task assignment, supervision, training completion, public-safe rules, data and AI-use rules, contribution recording, iCRS linkage where applicable, correction, grievance, and archive.

19.3.4.2 Volunteer Tools shall include labor boundary notices, no-employment notices, no-compensation-by-default notices, no-execution notices, confidentiality rules where applicable, conduct rules, and exit rights.

19.3.4.3 Volunteer Tools shall not create employment, contracting, public authority role, professional status, procurement eligibility, deployment authority, operational authority, or execution.

### 19.3.5 Team and Chapter Tools.

19.3.5.1 Team and Chapter Tools may support local, national, regional, university, youth, thematic, sectoral, or Campaign-specific teams and chapters for mobilization, learning, public-safe reporting, volunteer coordination, Campaign moderation, outreach, translation, accessibility, Foundry preparation, National Portfolio preparation, and Nexus Universe preparation.

19.3.5.2 Teams and chapters shall have recorded scope, steward, conduct rules, data rules, public-safe rules, use-of-name rules, sponsor rules, provider rules, public authority boundary rules, correction pathway, and archive rule.

19.3.5.3 Team or chapter status shall not create legal agency, authority to bind Nexus, public authority role, procurement authority, finance authority, consent authority, deployment authority, or execution authority.

### 19.3.6 Ambassador Tools.

19.3.6.1 Ambassador Tools may support approved individuals who help communicate Campaign purposes, recruit learners, mobilize volunteers, support public-safe storytelling, promote Academy or Risk Academy pathways, support Nexus Universe preparation, and route interested participants to recorded Nexus channels.

19.3.6.2 Ambassador roles shall be bounded by approved language, name-use rules, public-safe claims, conflict disclosure, sponsor and provider boundaries, no-authority notices, no-endorsement notices, no-fundraising authority unless separately authorized, no-procurement notices, no-consent notices, and correction pathways.

19.3.6.3 Ambassador status shall not create employment, agency, public authority role, certification authority, fundraising authority by default, procurement authority, finance authority, consent authority, deployment authority, or execution authority.

### 19.3.7 Quest and Bounty Tools.

19.3.7.1 Quest and Bounty Tools may connect Campaign participants to Foundry quests, bounties, builds, micro-production tasks, review tasks, translation tasks, accessibility tasks, public-safe reporting tasks, data tasks, software tasks, GRIx mapping tasks, DRI interpretation tasks, Observatory tasks, Studio testing tasks, Reports tasks, Marketplace tasks, Registry tasks, and correction tasks.

19.3.7.2 Quest and Bounty Tools shall define task scope, evidence requirements, review requirements, support class, reward or recognition status where applicable, labor boundary, data and AI-use restrictions, public-safe status, safeguard status, correction pathway, and archive rule.

19.3.7.3 Quest and bounty participation shall not create employment, procurement qualification, certification, provider validation, deployment authorization, financeability, or execution.

### 19.3.8 Campaign Dashboards.

19.3.8.1 Campaign Dashboards may display public-safe information concerning participation, signatures, pledges, support, volunteers, learning activity, contribution activity, Campaign readiness, National Portfolio routing, Nexus Universe preparation, Foundry tasks, Reports, DICE contributions, DRI contributions, Working Group formation, Competence Cell formation, correction status, and archive status.

19.3.8.2 Campaign Dashboards shall use public-safe data, aggregation where appropriate, privacy controls, youth protections, sensitive location controls, no-ranking rules where applicable, no-social-scoring rules, no-warning rules, no-approval rules, no-finance rules, no-procurement rules, no-consent rules, and no-execution rules.

19.3.8.3 A Campaign Dashboard shall not be a public authority decision, public warning, official count, vote, rating, finance signal, procurement signal, consent record, deployment instruction, or execution command.

### 19.3.9 Public-Safe Storytelling Tools.

19.3.9.1 Public-Safe Storytelling Tools may support stories, case notes, participant narratives, community narratives, youth stories, university stories, volunteer stories, sponsor acknowledgements, provider contribution notes, public authority learning summaries, Foundry stories, National Portfolio stories, Nexus Universe stories, and correction stories.

19.3.9.2 Public-Safe Storytelling shall require consent and permission where personal stories are used, protection of sensitive information, avoidance of exploitative narratives, community safeguards, Indigenous protocols where applicable, youth safeguards, privacy controls, public-safe review, and correction channels.

19.3.9.3 Public-Safe Storytelling shall not create endorsement, consent to implementation, public authority approval, financeability, procurement readiness, certification, deployment authorization, or execution.

### 19.3.10 Public Reports.

19.3.10.1 Campaigns may produce Public Reports documenting Campaign purpose, participation, support, signatures, pledges, volunteer activity, public-safe evidence, DICE contributions, DRI contributions, Working Group formation, Competence Cell formation, Nexus Universe routing, correction, and archive.

19.3.10.2 Campaign Public Reports shall follow Part XVII public-safe reporting rules, including no-warning, no-approval, no-finance, no-procurement, no-certification, no-consent, no-deployment, no-execution, protected knowledge, public repair, and correction notices.

19.3.10.3 Campaign Public Reports shall not create mandate, endorsement, public authority approval, finance commitment, procurement status, consent, deployment authorization, or execution.

### 19.3.11 Support Ledgers.

19.3.11.1 Campaign Support Ledgers shall record support received or pledged, including donations where lawful, grants where lawful, sponsorship, in-kind support, infrastructure support, venue support, volunteer support, expert support, provider contribution, university support, host support, and other support categories.

19.3.11.2 Support Ledgers shall record supporter, support type, date, restrictions, acknowledgement rule, sponsor boundary, provider boundary, conflict review, public display rule, use status, correction pathway, and archive rule.

19.3.11.3 Support Ledger entries shall not create control, ownership, governance rights, procurement preference, provider validation, financeability, public authority approval, consent, deployment authorization, or execution.

### 19.3.12 Correction Channels.

19.3.12.1 Campaign Correction Channels shall allow participants, communities, public authorities, sponsors, providers, volunteers, donors, learners, reviewers, maintainers, and affected persons to report errors, overclaims, unsafe content, data issues, privacy issues, AI issues, cyber issues, protected knowledge issues, safeguard concerns, consent overclaims, public authority overclaims, finance overclaims, procurement overclaims, sponsor control, provider validation, labor boundary issues, fraud, harassment, abuse, or execution overclaims.

19.3.12.2 Correction Channels shall provide intake, triage, classification, escalation, claims freeze where needed, data freeze where needed, technical freeze where needed, public-safe review, Registry update where applicable, Marketplace update where applicable, public repair where needed, handoff recall where applicable, archive, and closure records.

19.3.12.3 Correction Channels shall be visible, accessible, trusted, non-retaliatory, privacy-protective, and capable of stop-the-line escalation.

## 19.4 Campaign Records

### 19.4.1 Campaign Intake Record.

19.4.1.1 A Campaign Intake Record shall be created before a Campaign is activated. It shall identify Campaign title, purpose, steward, sponsor or support status, provider contribution status, jurisdictional scope, national routing where applicable, audience, Campaign class, Docket linkage, National Portfolio linkage where applicable, Nexus Universe linkage where applicable, data-use status, AI-use status, public-safe status, safeguard status, support rules, signature rules, pledge rules, volunteer rules, public display rules, correction pathway, and archive rule.

19.4.1.2 Campaign Intake shall screen for role confusion, public authority overclaim, finance overclaim, procurement overclaim, certification overclaim, consent overclaim, deployment overclaim, execution overclaim, sponsor control, provider validation, protected knowledge exposure, data risk, AI risk, cyber risk, privacy risk, youth risk, community risk, and fraud risk.

19.4.1.3 A Campaign shall not proceed from intake to activation unless required boundary controls are recorded.

### 19.4.2 Campaign Purpose Record.

19.4.2.1 A Campaign Purpose Record shall state the public-good purpose, problem statement, audience, intended mobilization pathway, expected outputs, Nexus routing, public-safe language, support needs, participation options, learning options, contribution options, and boundary notices.

19.4.2.2 The Purpose Record shall distinguish awareness, learning, participation, support, evidence input, volunteer activity, public-safe reporting, National Portfolio activation, Nexus Universe preparation, Foundry routing, and handoff awareness.

19.4.2.3 The Purpose Record shall not imply mandate, approval, endorsement, certification, financeability, procurement readiness, consent, deployment authorization, or execution.

### 19.4.3 Campaign Public-Safe Record.

19.4.3.1 A Campaign Public-Safe Record shall document public-safe review of Campaign language, visuals, dashboards, stories, signatures, pledges, support messages, volunteer materials, Reports, social content, media materials, public authority references, sponsor acknowledgements, provider acknowledgements, community references, and Nexus Universe materials.

19.4.3.2 The Public-Safe Record shall include no-warning, no-approval, no-finance, no-procurement, no-certification, no-consent, no-deployment, no-execution, protected knowledge, sensitive geospatial, cyber-sensitive, youth, privacy, accessibility, translation, and correction review.

19.4.3.3 Campaign materials shall not be publicly released where public-safe status is unresolved for the intended release class.

### 19.4.4 Campaign Support Record.

19.4.4.1 A Campaign Support Record shall document donations where lawful, pledges, sponsorship, grants, in-kind support, volunteer support, expert support, provider contribution, host support, university support, infrastructure support, data support where lawful, cloud or compute support where lawful, and other support.

19.4.4.2 Support Records shall identify supporter, support type, conditions, restrictions, acknowledgement language, conflict review, sponsor boundary, provider boundary, public display status, use status, correction pathway, and archive rule.

19.4.4.3 Support Records shall not create supporter control, governance rights, editorial rights, routing preference, provider validation, procurement preference, financeability, public authority approval, consent, deployment authorization, or execution.

### 19.4.5 Campaign Volunteer Record.

19.4.5.1 A Campaign Volunteer Record shall document volunteer registration, role, scope, training, supervision, safeguards, data access, AI-use permission, public-safe duties, hours where appropriate, contribution outputs, iCRS linkage where applicable, grievance access, correction pathway, and archive rule.

19.4.5.2 Volunteer Records shall protect privacy and shall not be used for social scoring, unauthorized employment screening, public ranking, or procurement qualification.

19.4.5.3 Volunteer Records shall not create employment, compensation entitlement, professional qualification, procurement eligibility, public authority role, deployment authorization, or execution.

### 19.4.6 Campaign Signature Record.

19.4.6.1 A Campaign Signature Record shall document signatory expression, Campaign purpose, date, permissions, privacy setting, display setting, jurisdiction where appropriate, duplicate handling, withdrawal option, correction pathway, and archive rule.

19.4.6.2 Signature Records shall be protected against fraud, duplication, manipulation, unauthorized scraping, unauthorized public display, youth data misuse, and misleading mandate claims.

19.4.6.3 Signature Records shall not be votes, binding commitments, public authority mandates, community consent, Indigenous consent where applicable, finance commitments, procurement approvals, deployment authorizations, or execution instructions.

### 19.4.7 Campaign Pledge Record.

19.4.7.1 A Campaign Pledge Record shall document non-binding expressions of intended support, volunteer interest, learning interest, contribution interest, sponsorship interest, provider contribution interest, hosting interest, public authority learning interest, donor interest, capital-reader interest, insurance-reader interest, Nexus Universe interest, or lawful handoff awareness interest.

19.4.7.2 Pledge Records shall distinguish expressions of interest from binding commitments, donations, contracts, grants, sponsorship agreements, procurement commitments, finance commitments, insurance commitments, public authority commitments, and handoff commitments.

19.4.7.3 Pledge Records shall not create binding finance, donor commitment, procurement commitment, public authority action, consent, deployment authorization, or execution.

### 19.4.8 Campaign DICE Contribution Record.

19.4.8.1 A Campaign DICE Contribution Record shall document Campaign-linked data, metadata, software, knowledge, learning, innovation commons, secure-room, data-room, clean-room, or compute-to-data contributions.

19.4.8.2 DICE Contribution Records shall include data class, rights status, data-use label, AI-use label, public-safe status, sensitivity status, lineage, contributor permission, access class, review status, correction pathway, and archive rule.

19.4.8.3 DICE Contribution Records shall not create data rights, open data status, unrestricted use, AI training permission, public authority approval, handoff permission, deployment authorization, or execution.

### 19.4.9 Campaign DRI Contribution Record.

19.4.9.1 A Campaign DRI Contribution Record shall document Campaign-linked disaster risk intelligence contributions, including indicator suggestions, signal observations, local risk observations, public-safe narratives, dashboard feedback, hotspot concerns, multi-hazard observations, cascade concerns, confidence notes, uncertainty notes, and correction reports.

19.4.9.2 DRI Contribution Records shall be reviewed before inclusion in DRI outputs, Reports, dashboards, Observatory records, Studio workflows, National Portfolios, Nexus Universe materials, or handoff context.

19.4.9.3 DRI Contribution Records shall not create public warnings, ratings, insurance scores, investment signals, public authority decisions, emergency commands, deployment authorization, or execution.

### 19.4.10 Campaign Working Group Formation Record.

19.4.10.1 A Campaign Working Group Formation Record shall document where Campaign participation leads to the proposal, formation, renewal, or activation of a National Working Group or thematic Working Group.

19.4.10.2 The record shall include purpose, proposed scope, participants, national routing where applicable, steward, Docket linkage, evidence needs, learning needs, public-safe rules, safeguard rules, support status, sponsor and provider boundaries, correction pathway, and archive rule.

19.4.10.3 Working Group formation through a Campaign shall not create public authority approval, board authority, procurement status, certification, consent, deployment authorization, or execution.

### 19.4.11 Campaign Competence Cell Formation Record.

19.4.11.1 A Campaign Competence Cell Formation Record shall document where Campaign participation leads to the proposal, formation, activation, or renewal of a Nexus Competence Cell.

19.4.11.2 The record shall identify cell purpose, domain, workplan, participants, required learning, required safeguards, evidence outputs, learning outputs, Foundry outputs, Studio outputs, Reports outputs, handoff dependencies, review needs, correction pathway, and archive rule.

19.4.11.3 Competence Cell formation through a Campaign shall not create employment, certification, public authority approval, provider validation, procurement status, consent, deployment authorization, or execution.

### 19.4.12 Campaign Universe Routing Record.

19.4.12.1 A Campaign Universe Routing Record shall document how Campaign outputs are routed into Nexus Universe preparation, including arena relevance, room relevance, National Portfolio relevance, Foundry relevance, Studio relevance, Academy relevance, Risk Academy relevance, Reports relevance, Marketplace relevance, Registry relevance, public authority learning relevance, capital-reader room relevance, insurance-reader room relevance, donor-reader room relevance, and handoff dependency relevance.

19.4.12.2 Universe routing shall include public-safe status, release class, support status, sponsor boundary, provider boundary, correction pathway, archive rule, and no-conversion notices.

19.4.12.3 Universe routing shall not create endorsement, public authority approval, financeability, procurement readiness, certification, consent, deployment authorization, or execution.

### 19.4.13 Campaign Correction Record.

19.4.13.1 A Campaign Correction Record shall document errors, overclaims, unsafe language, false claims, misleading dashboards, data issues, AI issues, cyber issues, privacy issues, protected knowledge exposure, sponsor control, provider validation, public authority overclaim, finance overclaim, procurement overclaim, certification overclaim, consent overclaim, deployment overclaim, execution overclaim, fraud, harassment, abuse, or labor boundary issues.

19.4.13.2 Correction Records shall identify trigger, affected materials, affected participants, containment action, claims freeze where applicable, data freeze where applicable, technical freeze where applicable, public-safe notice where applicable, Registry update where applicable, Marketplace update where applicable, Report correction where applicable, handoff recall where applicable, archive action, and closure.

19.4.13.3 Campaign Correction Records shall be routed to correction registers, Registry, Marketplace, Reports, DICE, DRI, National Portfolios, Nexus Universe, Nexus Network, and lawful handoff recipients where applicable.

### 19.4.14 Campaign Archive Record.

19.4.14.1 A Campaign Archive Record shall preserve Campaign purpose, intake, public-safe status, support records, volunteer records, signature records, pledge records, DICE contribution records, DRI contribution records, Working Group formation records, Competence Cell formation records, Nexus Universe routing records, correction records, non-continuation records, and archive notices.

19.4.14.2 Archived Campaigns shall include archive-not-current notice, archive date, archive reason, access class, sensitivity class, public-safe status, support status, correction history, successor link where applicable, retention rule, deletion or sealing rule where applicable, and historical-use note.

19.4.14.3 Campaign Archive shall not create current mandate, active support, active authority, endorsement, financeability, procurement readiness, consent, deployment authorization, or execution.

## 19.5 Campaign Governance

### 19.5.1 Campaign Readiness Levels.

19.5.1.1 Campaign Readiness Levels shall classify Campaigns by preparation status, including concept, intake, classified, draft, public-safe reviewed, support-ready, volunteer-ready, signature-ready, pledge-ready, launch-ready, active, under review, corrected, suspended, withdrawn, archived, or non-continuing.

19.5.1.2 Readiness Levels shall be based on Campaign purpose, public-safe status, data status, AI-use status, support status, sponsor status, provider status, volunteer controls, signature controls, pledge controls, safeguard status, trust and safety status, fraud controls, correction channel readiness, and archive readiness.

19.5.1.3 Campaign readiness shall not create approval, certification, public authority status, financeability, procurement readiness, consent, deployment authorization, or execution.

### 19.5.2 Claims Freeze.

19.5.2.1 A Claims Freeze shall be imposed where a Campaign may contain misleading claims, unsafe claims, public authority overclaims, finance overclaims, procurement overclaims, certification overclaims, consent overclaims, endorsement overclaims, deployment overclaims, execution overclaims, sponsor overclaims, provider validation claims, public warning claims, or unsupported impact claims.

19.5.2.2 During a Claims Freeze, affected Campaign materials shall not be newly published, promoted, amplified, translated, listed, routed, presented at Nexus Universe, routed to Marketplace, routed to Reports, routed to National Portfolios, or included in handoff context except for correction, public-safe notice, or containment.

19.5.2.3 Claims Freeze shall remain until review, correction, public-safe transformation, withdrawal, archive, or reinstatement is recorded.

### 19.5.3 Data Freeze.

19.5.3.1 A Data Freeze shall be imposed where Campaign data may involve privacy risk, consent issue, rights issue, youth data issue, health data issue, community-sensitive information, Indigenous protocol-sensitive information where applicable, protected knowledge, cyber-sensitive information, infrastructure-sensitive information, geospatial-sensitive information, data integrity issue, unauthorized access, unauthorized scraping, unauthorized AI use, or public-safe risk.

19.5.3.2 During a Data Freeze, affected data shall not be exported, published, displayed, shared, used for AI, routed to DICE, routed to DRI, routed to Observatory, routed to Studio, included in Reports, listed on Marketplace, displayed on dashboards, routed to National Portfolios, or included in handoff context except for containment, review, correction, lawful preservation, or archive.

19.5.3.3 Data Freeze shall remain until data review, rights review, privacy review, public-safe review, safeguard review, correction, deletion, sealing, restriction, or archive is recorded.

### 19.5.4 Technical Freeze.

19.5.4.1 A Technical Freeze shall be imposed where Campaign tools, dashboards, signature tools, pledge tools, donation tools, volunteer tools, team tools, ambassador tools, quest and bounty tools, APIs, data pipelines, software objects, integrations, or AI workflows may be unsafe, compromised, misleading, misconfigured, vulnerable, noncompliant with access controls, or boundary-breaching.

19.5.4.2 During a Technical Freeze, affected technical components shall not be deployed, updated for public use, integrated, promoted, routed, or used for active Campaign functions except for containment, debugging, security review, correction, rollback, or archive.

19.5.4.3 Technical Freeze shall remain until review, remediation, public-safe confirmation, security confirmation, data confirmation, AI-use confirmation, correction, or archive is recorded.

### 19.5.5 Support Controls.

19.5.5.1 Support Controls shall govern donations where lawful, grants, sponsorship, in-kind support, infrastructure support, compute support, data support, provider support, university support, host support, volunteer support, expert support, and other forms of Campaign support.

19.5.5.2 Support Controls shall include support eligibility, conflict review, anti-capture review, acknowledgement rules, support restrictions, no-control notice, no-procurement notice, no-provider-validation notice, finance boundary notice, public display rules, Support Ledger entry, correction pathway, and archive rule.

19.5.5.3 Support Controls shall prevent pay-to-influence, pay-to-route, pay-to-validate, pay-to-prioritize, pay-to-procure, hidden sponsorship, hidden exclusivity, and public-good enclosure.

### 19.5.6 Sponsor Controls.

19.5.6.1 Sponsor Controls shall ensure that sponsors may support Campaigns without controlling purpose, governance, content, evidence, public-safe reporting, Docket routing, National Portfolio routing, Nexus Universe routing, Foundry routing, Marketplace listing, Registry status, handoff context, or execution pathways.

19.5.6.2 Sponsor acknowledgements shall be factual, bounded, public-safe, non-promotional where required, and shall not imply endorsement, validation, procurement preference, financeability, public authority approval, community consent, deployment authorization, or execution.

19.5.6.3 Sponsor misconduct, sponsor overclaim, sponsor control attempt, or sponsor boundary breach shall trigger correction, acknowledgement removal, support restriction, suspension, withdrawal, public repair, or archive as appropriate.

### 19.5.7 Provider Controls.

19.5.7.1 Provider Controls shall ensure that providers may contribute tools, expertise, data where lawful, software, cloud, compute, infrastructure, training, demos, technical support, or other Campaign-relevant resources without becoming validated, preferred, certified, procured, endorsed, or routed by implication.

19.5.7.2 Provider contributions shall be recorded with provider-neutrality notes, conflict review, contribution scope, technical review where applicable, data and AI-use review where applicable, public-safe review, support status, no-validation notice, correction pathway, and archive rule.

19.5.7.3 Provider contribution shall not create provider validation, supplier approval, procurement preference, standards conformance, technical certification, financeability, public authority approval, deployment authorization, or execution.

### 19.5.8 Public Authority Boundary Controls.

19.5.8.1 Public Authority Boundary Controls shall prevent Campaigns from implying public authority approval, official action, regulation, public warning, emergency command, public finance allocation, procurement decision, permit, license, public policy adoption, or government endorsement.

19.5.8.2 Public authority participation in a Campaign shall be recorded as learning, observation, dialogue, support where lawful, or participation within scope, not as approval, mandate, public authority action, or execution.

19.5.8.3 Campaigns referencing public authorities shall use approved language, no-decision notices, no-warning notices, no-command notices, no-procurement notices, no-public-finance-allocation notices, and correction pathways.

### 19.5.9 Community Consent Boundary Controls.

19.5.9.1 Community Consent Boundary Controls shall prevent Campaign participation, signatures, pledges, stories, local knowledge, volunteer activity, public meetings, stakeholder engagement, or public-safe narratives from being represented as community consent, Indigenous consent where applicable, social license, project approval, land access, data permission, protected knowledge permission, deployment approval, or execution authorization.

19.5.9.2 Community participation shall be structured, non-extractive, public-safe, privacy-protective, safeguard-aware, and correctionable.

19.5.9.3 Where Indigenous protocols, protected knowledge, community governance, local consent processes, or rights-bearing processes apply, Campaigns shall route matters to appropriate lawful and culturally competent processes outside the Campaign unless a separate recorded protocol applies.

### 19.5.10 Trust and Safety Controls.

19.5.10.1 Trust and Safety Controls shall govern moderation, abuse prevention, harassment prevention, misinformation response, fraud prevention, impersonation prevention, spam control, bot control, youth protection, privacy protection, sensitive content handling, community protection, public-safe communication, and incident escalation.

19.5.10.2 Trust and Safety Controls shall apply to Campaign pages, signature tools, pledge tools, donation tools, volunteer tools, team and chapter tools, ambassador tools, dashboards, stories, comments, social media, public Reports, Nexus Universe displays, Marketplace listings, and Registry-linked Campaign records.

19.5.10.3 Trust and Safety incidents may trigger content removal, user restriction, claims freeze, data freeze, technical freeze, public-safe notice, correction, public repair, suspension, withdrawal, archive, or referral to lawful authorities where required.

### 19.5.11 Fraud Controls.

19.5.11.1 Fraud Controls shall prevent false signatures, duplicate signatures, fake pledges, fraudulent donations, false support claims, fake volunteer records, impersonation, sponsor misrepresentation, provider misrepresentation, public authority misrepresentation, inflated impact claims, manipulated dashboards, automated abuse, and misuse of Campaign records.

19.5.11.2 Fraud Controls may include verification, duplicate detection, audit logs, anomaly detection, human review, payment review where applicable, supporter review, signature review, pledge review, public display limits, correction channels, and archive records.

19.5.11.3 Fraud control outputs shall not become public rankings, social scores, employment decisions, procurement decisions, public authority decisions, finance decisions, insurance decisions, consent determinations, deployment decisions, or execution decisions.

### 19.5.12 Stop-the-Line Controls.

19.5.12.1 Stop-the-Line Controls shall apply where a Campaign creates or may create significant public-safe risk, data risk, AI risk, cyber risk, privacy risk, protected knowledge risk, youth risk, community risk, Indigenous protocol risk where applicable, public authority overclaim, finance overclaim, procurement overclaim, certification overclaim, consent overclaim, deployment overclaim, execution overclaim, sponsor capture, provider validation, fraud, abuse, or unsafe mobilization.

19.5.12.2 Stop-the-Line may require immediate suspension of Campaign publication, signature collection, pledge collection, donation collection, volunteer assignment, dashboards, stories, social content, provider demonstrations, sponsor acknowledgements, Marketplace listing, Registry status, Nexus Universe presentation, Reports routing, National Portfolio routing, Foundry routing, Studio routing, DRI routing, DICE routing, Observatory routing, and handoff routing.

19.5.12.3 Stop-the-Line shall remain until containment, review, correction, public repair, withdrawal, archive, reinstatement, or lawful escalation is recorded.

## 19.6 Campaign Boundaries

### 19.6.1 Signature Is Not Vote.

19.6.1.1 A Campaign signature shall record an expression of interest, support, awareness, participation, concern, or alignment within the Campaign’s recorded purpose. It shall not be a vote, election, referendum, public authority mandate, board decision, community consent, Indigenous consent where applicable, procurement approval, finance commitment, public warning, deployment authorization, or execution instruction.

19.6.1.2 Signature totals shall not be represented as democratic mandate, official mandate, community mandate, public authority mandate, or consent mandate.

### 19.6.2 Pledge Is Not Binding Finance.

19.6.2.1 A Campaign pledge shall be non-binding unless a separate lawful agreement states otherwise. It shall not create donation obligation, grant obligation, sponsorship agreement, investment commitment, insurance commitment, public finance allocation, procurement commitment, donor commitment, underwriting commitment, or transaction obligation by implication.

19.6.2.2 Pledge records may support planning and public-good learning, but they shall not be booked, represented, or relied upon as binding finance unless separately and lawfully documented outside the Campaign.

### 19.6.3 Support Is Not Control.

19.6.3.1 Support for a Campaign, including donation, sponsorship, grant, in-kind support, volunteer support, expert support, infrastructure support, data support where lawful, cloud or compute support, venue support, university support, provider support, or host support, shall not create control.

19.6.3.2 Supporters shall not control Campaign purpose, evidence, public-safe reporting, Registry status, Marketplace listing, Docket routing, National Portfolio routing, Nexus Universe routing, Foundry routing, public authority learning, handoff context, or execution pathways.

19.6.3.3 Support shall be accepted only under public-good boundary discipline.

### 19.6.4 Volunteer Participation Is Not Employment.

19.6.4.1 Volunteer participation in a Campaign shall not create employment, contracting, wages, benefits, compensation entitlement, agency, professional status, procurement eligibility, public authority role, deployment authority, operational authority, or execution authority.

19.6.4.2 Volunteer roles shall be scoped, supervised, recorded, safeguarded, and correctionable. Where work requires employment, contracting, regulated professional service, procurement, or execution authority, it shall be routed outside volunteer participation.

### 19.6.5 Public Attention Is Not Public Authority Approval.

19.6.5.1 Media attention, public attention, social media reach, Campaign visibility, public attendance, public authority attendance, public authority learning participation, sponsor presence, provider demonstrations, Nexus Universe visibility, or Marketplace discovery shall not create public authority approval.

19.6.5.2 Public authority action must occur separately through competent public authority processes and shall not be inferred from Campaign attention.

### 19.6.6 Community Participation Is Not Consent.

19.6.6.1 Community participation, public stories, local knowledge contributions, signatures, pledges, attendance, volunteer work, Campaign support, public-safe summaries, stakeholder meetings, or Nexus Universe participation shall not create community consent, Indigenous consent where applicable, social license, land access, data permission, protected knowledge permission, project approval, deployment approval, or execution authorization.

19.6.6.2 Consent-sensitive matters shall be routed to appropriate lawful, community-governed, Indigenous protocol-sensitive where applicable, rights-respecting, and recorded processes outside Campaign participation unless a separate lawful consent record exists.

### 19.6.7 Donor Interest Is Not Commitment.

19.6.7.1 Donor interest, philanthropic interest, grant interest, public finance interest, capital-reader interest, insurance-reader interest, sponsor interest, or pledge interest shall not create commitment.

19.6.7.2 Donor interest may be recorded as a learning, support, or readiness signal, but shall not be represented as funding approval, financeability, bankability, public finance allocation, grant award, investment commitment, insurance commitment, procurement commitment, or execution readiness.

### 19.6.8 Campaign Success Is Not Execution Authority.

19.6.8.1 Campaign success, including high participation, many signatures, strong public attention, high volunteer activity, substantial pledges, sponsorship, media visibility, Nexus Universe visibility, National Portfolio activation, Foundry participation, Reports publication, Marketplace listing, Registry record, or public authority learning participation, shall not create execution authority.

19.6.8.2 Execution may occur only through competent lawful actors, lawful public authority processes, lawful procurement processes, lawful finance processes, lawful insurance processes, lawful consent processes, lawful contracting, lawful deployment authorization, and lawful operational accountability outside NAF unless separately and expressly recorded.

19.6.8.3 The final Campaigns rule of Part XIX is that NAF may mobilize people, institutions, support, signatures, pledges, volunteers, learning, evidence, public-safe stories, Campaign Reports, DICE contributions, DRI contributions, Working Groups, Competence Cells, Nexus Universe preparation, National Portfolio activation, Foundry activity, Academy participation, public authority learning, and lawful handoff awareness only through record-bearing, public-safe, safeguard-aware, support-controlled, sponsor-bounded, provider-neutral, trust-and-safety-governed, fraud-controlled, correctionable, archive-capable, no-mandate, no-vote, no-finance, no-procurement, no-certification, no-consent, no-deployment, and non-executing Campaign governance. No Campaign, signature, pledge, donation, support, sponsorship, provider contribution, volunteer role, ambassador role, team, chapter, dashboard, story, public Report, Support Ledger, Campaign DICE record, Campaign DRI record, Working Group formation record, Competence Cell formation record, Nexus Universe routing record, Marketplace listing, Registry record, National Portfolio activation, public authority learning participation, media attention, donor interest, capital-reader interest, insurance-reader interest, or handoff awareness note shall become endorsement, mandate, public authority approval, public warning, finance commitment, investment activity, insurance approval, procurement readiness, certification, community consent, Indigenous consent where applicable, deployment authorization, operational command, agency, warranty, 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/nexus-agile-framework-naf/xix.-campaigns.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.