IV. Campaigns
Nexus Campaigns for public-good campaigns, resilience, disaster risk reduction, disaster risk finance readiness, disaster risk intelligence, public-safe reporting, and volunteer mobilization.
Summary
The Nexus Campaigns pillar is the public-good campaign, mobilization, and support rail of Nexus. It structures resilience campaigns, disaster risk reduction campaigns, disaster risk finance readiness campaigns, disaster risk intelligence campaigns, public-safe reporting campaigns, volunteer mobilization, and lawful support pathways across national, regional, and global contexts.
It supports signatures, pledges, donations where lawful, training, builds, and public participation. It does not imply endorsement, public authority approval, or operational execution.
1. Identity, Purpose, Thesis, and Public-Good Campaign Doctrine
1.1 Nexus Campaigns Defined
1.1.1 Definition. Nexus Campaigns are the purpose-built public-good campaign, mobilization, support, contribution, learning, evidence, readiness, and lawful-routing infrastructure of the Nexus Ecosystem. They provide the structured digital and institutional mechanism through which national, regional, global, thematic, sectoral, local, community, university, youth, laboratory, volunteer, public authority learning, resilience, disaster-risk-reduction, disaster-risk-finance, disaster-risk-intelligence, Nexus Foundry, Nexus Universe, and lawful handoff campaigns may be created, governed, supported, reviewed, corrected, renewed, and archived.
1.1.2 Campaigns as mobilization infrastructure. Nexus Campaigns shall convert public concern, stakeholder interest, institutional capability, volunteer energy, technical expertise, public-good support, signatures, pledges, donations, sponsorship, in-kind support, data contributions, evidence submissions, learning participation, public authority learning questions, community context, Working Group needs, Competence Cell needs, Nexus Foundry build needs, Nexus Observatory signals, GRIx mappings, DRI records, DICE commons objects, Nexus Universe readiness needs, and lawful handoff dependency questions into structured campaign records.
1.1.3 Campaigns as operating system, not publicity layer. Nexus Campaigns shall not be treated as ordinary marketing campaigns, public relations drives, fundraising pages, petition pages, event promotion pages, advocacy-only campaigns, vendor campaigns, investment campaigns, procurement campaigns, public warning campaigns, emergency response campaigns, or political campaigns. They shall be a governed public-good operating layer for mobilizing support, participation, evidence, learning, builds, readiness, public-safe reporting, and continuation through recorded Nexus pathways.
1.1.4 Campaigns as public-good action surfaces. A Nexus Campaign may allow persons and institutions to:
1.1.4.1 sign or support a public-good statement within recorded scope;
1.1.4.2 pledge time, expertise, data, equipment, compute, venue support, translation, accessibility support, communications support, technical support, or financial support where lawful;
1.1.4.3 donate or contribute public-good support through governed support channels where lawful;
1.1.4.4 volunteer for tasks, quests, bounties, builds, learning pathways, public-safe reporting, data stewardship, accessibility, translation, dashboard testing, field support, review, maintenance, and correction;
1.1.4.5 join or support National Working Groups, Competence Cells, Guild pathways, campaign teams, chapters, ambassador pathways, public authority learning rooms, readiness rooms, community safeguard rooms, DRI dashboard rooms, Nexus Universe rooms, and Core Build preparation rooms;
1.1.4.6 submit evidence, data, observations, public-safe reports, problem statements, challenge briefs, research questions, build proposals, technical needs, community concerns, safeguard concerns, and correction notices;
1.1.4.7 follow progress through campaign dashboards, support ledgers, Campaign Record Cards, public-safe updates, Registry records, Marketplace listings, Studio workflows, Grid inputs, TRL evidence notes, Nexus Universe routing records, and archive records.
1.1.5 Campaigns as disciplined public participation. Nexus Campaigns shall make public participation more useful by turning participation into recorded contributions, reviewable outputs, supportable teams, traceable evidence, public-safe communication, safeguard-aware learning, and lawful continuation. Participation shall not be left as raw enthusiasm, vague endorsement, unreviewed volunteer work, unsupported public claims, donor attention, sponsor visibility, media momentum, or event attendance.
1.2 Campaigns as Public-Good Mobilization Infrastructure
1.2.1 Public-good infrastructure status. Nexus Campaigns shall function as public-good mobilization infrastructure for national resilience, global risk reduction, public-good technology, disaster-risk reduction, disaster-risk finance readiness, disaster-risk intelligence, evidence formation, public authority learning, volunteer mobilization, community protection, youth participation, Nexus Foundry build conversion, Nexus Universe preparation, and lawful handoff dependency formation.
1.2.2 Beyond petitions and crowdfunding. Nexus Campaigns shall incorporate the useful functions of petition platforms, crowdfunding platforms, civic support platforms, public pledge platforms, volunteer platforms, challenge platforms, open-source contribution systems, public dashboard platforms, public-good reporting tools, impact update systems, and civic capital-readiness environments, while correcting their common weaknesses: weak evidence discipline, inflated claims, poor support transparency, shallow signatures, unsafe public pressure, unclear use of funds, insufficient data controls, weak fraud prevention, limited safeguard protection, over-reliance on outrage, weak correction, and unclear legal boundaries.
1.2.3 Purpose-built for Nexus. Nexus Campaigns shall be designed specifically for the Nexus Ecosystem and shall therefore operate with:
1.2.3.1 public-good purpose before publicity;
1.2.3.2 national ownership before global amplification;
1.2.3.3 evidence before claims;
1.2.3.4 safeguards before publication;
1.2.3.5 data rights before data use;
1.2.3.6 AI-use labels before AI processing;
1.2.3.7 public-safe summaries before mass communication;
1.2.3.8 volunteer protection before task assignment;
1.2.3.9 support ledgers before support claims;
1.2.3.10 no-reliance readiness before finance-facing discussion;
1.2.3.11 public authority learning before public authority action;
1.2.3.12 provider neutrality before technology visibility;
1.2.3.13 correction before reputational defense;
1.2.3.14 archive before forgetting;
1.2.3.15 lawful handoff before implementation.
1.2.4 Infrastructure for public-good momentum. Nexus Campaigns shall allow momentum to become cumulative rather than temporary. Signatures shall become Support Records; pledges shall become Pledge Records; donations and in-kind support shall become Support Ledger entries; volunteer roles shall become Contribution Records; evidence submissions shall become Evidence Intake Records; data contributions shall become DICE-governed records; risk signals shall become Observatory, GRIx, and DRI inputs; public authority learning shall become Non-Decision Learning Records; build requests shall become Nexus Foundry tasks, quests, bounties, or builds; public-facing outputs shall become Public-Safe Summaries; Nexus Universe materials shall become Arena Routing Records; and post-cycle outcomes shall become Continuation, Correction, Non-Continuation, Handoff, or Archive Records.
1.2.5 Campaigns as public trust architecture. Nexus Campaigns shall maintain trust by making campaign identity, steward identity, funding support, support use, review status, public-safe status, data status, safeguard status, Nexus Universe status, Marketplace status, Registry status, Studio status, Grid and TRL status, incident status, correction status, and archive status visible within recorded limits. Trust shall arise from record discipline, not from popularity, celebrity, institutional prestige, sponsor logos, public authority attendance, media coverage, or funding size.
1.3 Campaigns as Annual National, Regional, Global, and Thematic Mobilization Protocols
1.3.1 Scaled campaign architecture. Nexus Campaigns shall support multiple campaign scales, including national campaigns, regional campaigns, global campaigns, thematic campaigns, sector campaigns, domain campaigns, technology campaigns, local campaigns, city campaigns, community campaigns, university campaigns, youth campaigns, diaspora campaigns, public authority learning campaigns, laboratory campaigns, Nexus Foundry campaigns, Nexus Universe campaigns, and lawful handoff readiness campaigns.
1.3.2 National campaigns. A National Nexus Campaign shall mobilize a country’s stakeholders around all-hazards resilience, DRR, DRF, DRI, National Working Group formation, Competence Cell activation, volunteer mobilization, public authority learning, DICE commons contribution, Nexus Observatory needs, GRIx and DRI records, Nexus Foundry build inputs, Nexus Universe readiness, National Portfolio formation, and lawful national continuation. National Campaigns shall be country-led, nationally owned, Nexus-supported, non-binding, non-exclusive, non-decision, and subject to national law, national procedures, national priorities, public authority processes, community safeguards, Indigenous protocols where applicable, data sovereignty, and lawful national pathways.
1.3.3 Regional campaigns. A Regional Nexus Campaign shall mobilize countries, National Nodes, regional stakeholders, regional institutions, universities, laboratories, public authorities in learning roles, communities, donors, insurers, development actors, providers, sponsors, and regional networks around shared hazards, corridors, ecosystems, climate systems, WEFH-B interdependencies, disaster-risk patterns, infrastructure systems, humanitarian systems, data gaps, Observatory needs, regional Nexus Universe arenas, and regional public-safe learning. Regional Campaigns shall support national pathways and shall not create regional supremacy over countries.
1.3.4 Global campaigns. A Global Nexus Campaign shall mobilize public-good participation around global risk, resilience, public-good technology, DRR, DRF, DRI, climate adaptation, public authority learning, Nexus Foundry builds, DICE commons, public-safe reporting, global Nexus Universe preparation, and cross-regional capability. Global Campaigns shall not be framed as intergovernmental adoption, official global endorsement, treaty process, country ranking, public authority approval, finance platform, procurement platform, certification scheme, or execution program.
1.3.5 Thematic campaigns. A Thematic Nexus Campaign shall mobilize around a theme such as water security, energy resilience, food systems, health systems, biodiversity, climate adaptation, disaster-risk intelligence, disaster-risk finance readiness, cyber resilience, AI for public-good resilience, AI-RAN/O-RAN and telecom resilience, geospatial intelligence, drones and sensors, sovereign compute, digital twins, supply chains, ports, logistics, public-safe communications, youth resilience, community safeguards, protected knowledge, or lawful handoff readiness.
1.3.6 Local and community campaigns. A Local or Community Nexus Campaign shall mobilize place-based participation around a city, region, watershed, corridor, campus, community, infrastructure system, hazard, service system, or protected public-interest concern. Local and community campaigns shall preserve consent boundaries, protected knowledge, accessibility, non-extraction, public-safe communication, local benefit, and national routing where national pathways are implicated.
1.3.7 Campaigns as annual protocol. Each campaign may operate through a recurring annual cycle of mandate, scoping, stakeholder mobilization, signature and support mobilization, volunteer onboarding, Working Group formation, Competence Cell activation, data and evidence mapping, Foundry conversion, public authority learning, readiness room review, public-safe publication, Nexus Universe preparation, live-cycle participation, after-action review, correction, continuation, lawful handoff dependency preparation, non-continuation, renewal, and archive.
1.3.8 Campaigns as year-round and surge-ready. Nexus Campaigns shall operate year-round while preparing for annual Nexus Universe surge cycles. Campaigns shall not treat Nexus Universe as a one-week event only. Nexus Universe shall be the annual concentration point for a year of campaign mobilization, evidence formation, build work, support raising, public-safe communication, readiness mapping, and national or thematic preparation.
1.4 Campaigns as the Public Platform for Signatures, Support, Volunteers, Builds, and Readiness
1.4.1 Campaign action center. Each Nexus Campaign may include a governed action center through which users can sign, pledge, support, donate where lawful, volunteer, join a team, join a Working Group, join a Competence Cell, take training, complete a WILP or micro-credential pathway, submit evidence, propose a build, share public-safe materials, request a briefing, nominate a stakeholder, attend a room, follow progress, or report a concern.
1.4.2 Signatures and public support. Campaign signatures shall record support for the stated campaign purpose only. A signature shall not constitute a vote, referendum, legal mandate, policy adoption, public consultation result, public authority approval, procurement support, funding approval, community consent, Indigenous consent where applicable, land access, protected knowledge permission, or project authorization.
1.4.3 Pledges. Campaign pledges may include volunteer hours, expert review time, data contribution subject to rights, compute support, equipment support, venue support, communications support, translation support, accessibility support, public-safe reporting support, training support, sponsor support, provider contribution, donor support, or financial support where lawful. A pledge shall be an expression of potential support until accepted, governed, recorded, and routed under applicable terms.
1.4.4 Donations and support. Campaigns may receive donations, sponsorship, grants, philanthropic support, institutional support, in-kind support, challenge funding, bounty funding, travel support, scholarship support, cloud credits, compute credits, equipment support, venue support, media support, and other public-good support where lawful. Support shall be governed by support terms, fiscal stewardship, payment controls, restricted or unrestricted support records, use-of-support reporting, conflicts, public-safe display rules, and correction pathways.
1.4.5 Civic capital-readiness without regulated finance. Nexus Campaigns may make public-good initiatives, National Portfolio needs, DRF readiness questions, resilience needs, Foundry builds, data commons gaps, and Nexus Universe outputs more readable to capital readers, insurers, donors, development actors, and public finance readers. Such readability shall occur through no-reliance, non-soliciting, non-transactional, regulated-perimeter-controlled rooms and records. Nexus Campaigns shall not provide investment advice, securities crowdfunding, lending, banking, deposit-taking, insurance, underwriting, valuation, rating, solicitation, offer, public finance allocation, donor commitment, or transaction readiness by implication.
1.4.6 Volunteer mobilization. Campaigns shall mobilize volunteers through clear role records, training, supervision, data-access limits, AI-use rules, field activity limits, youth safeguards, public-safe obligations, iCRS linkage, WILP and micro-credential pathways where applicable, escalation channels, correction channels, and archive. Volunteers shall not be used as unpaid substitutes for employment, contractor work, professional services, public authority work, emergency response, procurement work, or execution.
1.4.7 Build mobilization. Campaigns shall allow teams to mobilize around public-good builds, including datasets, dashboards, open-source tools, public-good software, digital twins, Studio workflows, DRI dashboards, GRIx mappings, public-safe explainers, training modules, technical packs, Core Build requests, and lawful handoff dependency packages. Build participation shall not create deployment authorization, procurement status, product validation, financeability, insurance approval, certification, or execution authority.
1.4.8 Readiness mobilization. Campaigns may generate readiness records, including assumptions registers, dependency registers, diligence-gap registers, finance-readiness notes, insurance-readiness question maps, donor-readiness notes, public finance relevance notes, DRF readiness notes, public authority dependency notes, legal dependency notes, safeguard readiness notes, data readiness notes, technical readiness notes, and handoff support notes. Such records shall support learning and independent diligence only.
1.5 Campaigns as DRR / DRF / DRI Mobilization Spine
1.5.1 All-hazards operating spine. Nexus Campaigns shall be built around an all-hazards and whole-of-society operating spine integrating disaster-risk reduction, disaster-risk finance readiness, and disaster-risk intelligence. This spine shall allow campaigns to mobilize risk knowledge, evidence, data, public-safe communication, public authority learning, community safeguards, volunteer support, technical builds, and readiness questions across hazards, systems, technologies, sectors, and jurisdictions.
1.5.2 DRR function. The DRR function of Nexus Campaigns shall mobilize national, regional, global, thematic, and local work around hazard awareness, prevention, preparedness, exposure reduction, vulnerability reduction, critical services continuity, community resilience, infrastructure resilience, public-safe communication, public authority learning, field learning, National Portfolio formation, and Nexus Foundry tasks. DRR campaign work shall not issue emergency commands, public warnings, public safety orders, or official risk classifications.
1.5.3 DRF function. The DRF function of Nexus Campaigns shall mobilize work around protection gaps, risk-layering questions, insurance-readiness questions, donor-readiness questions, public finance relevance, resilience finance literacy, assumptions registers, dependency registers, diligence-gap registers, no-reliance readiness rooms, and lawful handoff dependencies. DRF campaign work shall not create financeability, bankability, investment readiness, insurance approval, underwriting acceptance, donor commitment, public finance allocation, valuation, rating, solicitation, offer, or transaction readiness.
1.5.4 DRI function. The DRI function of Nexus Campaigns shall mobilize work around signals, indicators, GRIx category mappings, DRI dashboards, Nexus Observatory needs, Edge observations, geospatial layers, digital twins, confidence labels, uncertainty statements, public-safe risk summaries, correction records, and National Dense Nexus Core needs. DRI campaign work shall not create official warnings, sovereign ratings, investment ratings, insurance scores, public authority classifications, emergency alerts, intelligence products, or operational directives.
1.5.5 Integration across WEFH-B and critical systems. Campaigns shall integrate DRR, DRF, and DRI across water, energy, food, health, biodiversity, climate, infrastructure, ports, logistics, cities, public health, biosecurity-sensitive systems, cyber-physical systems, AI systems, telecom, AI-RAN/O-RAN, private wireless, Edge systems, geospatial systems, drones, robotics, sensors, sovereign compute, cloud, HPC, DLT, quantum-relevant security, semiconductors, supply chains, humanitarian systems, and public-safe communications.
1.5.6 Public-safe risk communication. Nexus Campaigns shall translate risk and readiness information into public-safe summaries that communicate uncertainty, limitations, evidence status, public authority boundaries, finance boundaries, insurance boundaries, procurement boundaries, community consent boundaries, protected knowledge restrictions, and correction pathways. Campaign risk communication shall mobilize learning and action without panic, false certainty, official warning, blame, ranking, or unsafe exposure.
1.6 Campaigns as Nexus Universe Preparation Rail
1.6.1 Nexus Universe preparation function. Nexus Campaigns shall serve as the principal public-facing preparation rail for Nexus Universe. They shall convert year-round national, regional, global, thematic, sectoral, local, youth, university, lab, community, and volunteer mobilization into Nexus Universe-ready outputs, including National Portfolio summaries, public-safe risk summaries, DRI dashboards, GRIx mappings, Foundry build outputs, Core Build technical packs, public authority learning records, readiness question maps, safeguard records, public-good software objects, DICE commons contributions, Risk Academy pathways, iCRS contribution records, Marketplace candidates, Registry records, Studio demonstrations, Grid inputs, TRL evidence notes, and lawful handoff dependency candidates.
1.6.2 Nexus Universe without event overclaim. Campaign preparation for Nexus Universe shall not turn Nexus Universe into a trade fair, investor demo day, procurement show, product validation event, regulatory sandbox by implication, government endorsement stage, public authority approval forum, public warning platform, or execution command center. Nexus Universe shall concentrate public-good surge capacity, not confer authority by visibility.
1.6.3 Arena routing. Campaigns shall maintain Arena Routing Records identifying whether campaign outputs should route to global, regional, national, thematic, sectoral, youth, university, lab, community, public authority learning, readiness, Core Build, Studio, Marketplace, Registry, Grid, TRL, continuation, correction, non-continuation, handoff, or archive pathways.
1.6.4 Claims freeze. Before Nexus Universe or any major live campaign cycle, the campaign may apply a Claims Freeze to public-facing statements, sponsor acknowledgments, provider acknowledgments, lab claims, technology claims, readiness claims, public authority claims, finance claims, insurance claims, procurement claims, community claims, and public-safe summaries. A Claims Freeze shall stabilize public meaning and prevent overclaim; it shall not create approval.
1.6.5 Data freeze and technical freeze. Campaigns may apply Data Freeze and Technical Freeze controls to stabilize datasets, AI-use labels, data-use labels, secure-room contents, public authority materials, geospatial layers, dashboards, Studio workflows, software versions, network configurations, compute workloads, model versions, benchmark versions, and Core Build packs before live activities. Such freezes shall support integrity and safety only and shall not imply completeness, correctness, approval, or readiness beyond recorded scope.
1.6.6 Post-Universe continuation. After Nexus Universe, campaign outputs shall be classified for national continuation, regional continuation, Foundry continuation, DICE routing, Observatory routing, Risk Academy routing, Risk Agency consideration, Marketplace listing, Registry status update, Studio workflow renewal, Grid input review, TRL evidence update, lawful handoff dependency packaging, correction, withdrawal, non-continuation, retirement, or archive.
1.7 Campaigns as Nexus Foundry Intake and Build Conversion Layer
1.7.1 Foundry intake function. Nexus Campaigns shall be a principal intake surface for Nexus Foundry. They shall identify buildable needs from public concern, national priorities, Working Group records, Competence Cell work, community context, data gaps, public authority learning questions, DRR needs, DRF questions, DRI needs, GRIx gaps, DICE commons gaps, public-safe reporting needs, Nexus Universe readiness needs, and lawful handoff dependency needs.
1.7.2 Campaign-to-Foundry conversion. Campaign inputs may be converted into Foundry tasks, quests, bounties, builds, evidence packs, method packs, dataset packs, dashboard packs, public-good software, AI workflow packs, cyber packs, geospatial packs, DRI packs, GRIx packs, public-safe reporting packs, Studio workflow packs, Nexus Core Build requests, National Portfolio packs, readiness packs, and handoff dependency packs.
1.7.3 Campaign tasks. A campaign task shall be a bounded unit of public-good work with scope, steward, eligible contributors, data rules, AI-use rules, IP and license status, review requirement, public-safe status, support status, contribution record, correction pathway, and archive rule.
1.7.4 Campaign quests. A campaign quest shall be a structured challenge that invites contributors to address a defined public-good problem, evidence gap, data gap, technical need, public-safe communication need, accessibility need, safeguard need, readiness need, or build need under recorded terms.
1.7.5 Campaign bounties. A campaign bounty shall be a specific deliverable with acceptance criteria, reward or support status where lawful, IP and license terms, contribution records, public-safe review, data controls, AI-use controls, labor boundary controls, correction pathway, and archive rule.
1.7.6 Campaign builds. A campaign build shall be a coordinated production effort that may create public-good software, datasets, dashboards, digital twins, simulations, Studio workflows, methods, reports, public-safe summaries, learning modules, evidence packs, or technical baselines. A campaign build shall not authorize deployment, procurement, finance, insurance, public authority action, certification, or execution.
1.7.7 Core Build requests. Campaigns may generate Core Build Requests for Nexus Universe or Nexus Foundry preparation. A Core Build Request shall identify technical pack needs, compute needs, network needs, data-room needs, secure-room needs, dashboard needs, AI workflow needs, simulation needs, public-safe reporting kits, support needs, teardown needs, and archive rules. A Core Build Request shall not guarantee Core Build acceptance or create deployment approval.
1.7.8 Foundry conversion discipline. Campaign-to-Foundry conversion shall occur only through record-bearing pathways. Popular demand, signatures, donations, sponsor support, provider visibility, media attention, or public authority attendance shall not by themselves determine Foundry priority, build acceptance, Nexus Universe routing, Marketplace listing, Registry status, Grid input, TRL evidence status, or handoff eligibility.
1.8 Campaigns as Civic Support and Public-Good Support Infrastructure
1.8.1 Support infrastructure function. Nexus Campaigns shall provide governed support infrastructure through which public-good campaigns can receive support, pledges, donations where lawful, sponsorship, in-kind contributions, expert time, volunteer time, compute credits, cloud credits, data contributions, venue support, equipment support, travel support, scholarship support, accessibility support, translation support, media support, community support, technical support, challenge funding, bounty funding, and fellowship support.
1.8.2 Support classes. Campaign support may be classified as donation support, sponsorship support, donor support, philanthropic support, institutional support, public-good grant support, in-kind support, compute support, equipment support, data support, venue support, volunteer support, expert support, learning support, scholarship support, travel support, bounty support, challenge support, media support, public-safe communication support, community safeguard support, and Nexus Universe participation support.
1.8.3 Public-good support lane. The public-good support lane shall support campaign activities without financial return. It may support research, training, volunteer mobilization, translation, accessibility, public-safe reporting, community safeguards, public-good software, DICE commons, National Portfolio preparation, Nexus Universe participation, Core Build preparation, secure rooms, data rooms, field research, student support, WILPs, micro-credentials, and correction.
1.8.4 Readiness interest lane. The readiness interest lane shall allow capital readers, insurers, donors, development actors, public finance readers, and lawful stakeholders to follow campaign outputs, join no-reliance rooms, ask diligence questions, understand assumptions, identify gaps, and support public-good readiness learning without creating investment interest, financeability, insurability, donor commitment, public finance allocation, underwriting, valuation, rating, solicitation, offer, or transaction readiness.
1.8.5 Lawful enterprise handoff lane. The lawful enterprise handoff lane shall route mature campaign records into lawful handoff dependency packages for competent recipients such as National Consortium Companies, Project SPVs, public authorities, providers, operators, contractors, funders, insurers, donors, public finance readers, universities, or other lawful actors. This lane shall not make Nexus Campaigns an implementation actor.
1.8.6 Support Ledger. Each campaign receiving material support should maintain a Support Ledger recording support source class, support type, restricted or unrestricted status, support purpose, support use, public-safe display status, conflicts, reporting obligations, correction records, reallocation rules, refund rules where applicable, and archive.
1.8.7 Fiscal stewardship. Campaigns involving funds shall identify the fiscal steward, payment processor, recipient entity, lawful basis, restrictions, reporting rules, tax or receipt status where applicable, anti-fraud controls, sanctions or AML checks where required, refund or reallocation terms, and non-continuation rules. Nexus shall not be presumed to hold or administer campaign funds unless separately and lawfully structured.
1.8.8 No pay-to-influence. Support shall not purchase campaign influence, Working Group influence, Competence Cell influence, public-safe publication, Nexus Universe routing, Marketplace status, Registry status, Studio authorization, Grid input, TRL classification, Risk Agency routing, public authority learning output, readiness output, or handoff eligibility.
1.8.9 Support without authority. Donations, signatures, pledges, sponsorship, grants, equipment support, compute credits, media support, public authority attendance, capital-reader interest, insurer interest, donor interest, or public finance reader interest shall not create approval, certification, procurement status, financeability, insurability, public authority action, consent, deployment authorization, or execution authority.
1.9 Campaigns as Participation Without Endorsement
1.9.1 Core diplomatic and institutional posture. Nexus Campaigns shall be structured so that countries, missions, ministries, public authorities, public institutions, global institutions, development actors, public finance actors, universities, labs, cities, regions, communities, companies, sponsors, providers, donors, insurers, capital readers, media actors, and other stakeholders may participate, observe, contribute, host, convene, support learning, nominate stakeholders, attend rooms, provide technical dialogue, or prepare Nexus Universe pathways without being deemed to endorse, approve, adopt, recognize, fund, procure, certify, regulate, finance, insure, command, consent to, or execute any Nexus Campaign, output, provider contribution, sponsor-supported activity, public-safe report, readiness note, Nexus Universe output, or handoff pathway.
1.9.2 No endorsement request by default. Nexus Campaigns shall not default to requesting country endorsement, mission endorsement, ministerial endorsement, public authority endorsement, institutional endorsement, global forum endorsement, or official adoption. The preferred posture shall be voluntary participation, technical dialogue, observer participation, national stakeholder routing, learning participation, non-binding collaboration, public-good cooperation, and Nexus Universe preparation.
1.9.3 Country-led and nationally owned participation. National campaigns shall be country-led, nationally owned, and Nexus-supported. Campaigns shall support national stakeholder mobilization, public authority learning, Working Group formation, Competence Cell activation, National Portfolio preparation, and Nexus Universe readiness without replacing national plans, public authority mandates, public consultation processes, procurement systems, regulatory processes, public finance systems, emergency management systems, or national development priorities.
1.9.4 Non-binding and non-exclusive participation. Participation in a Nexus Campaign shall be voluntary, non-binding, non-exclusive, non-treaty, non-regulatory, non-procurement, non-financial, non-certifying, non-decision, and non-executing. Participation shall not prevent any actor from participating in other national, regional, multilateral, humanitarian, academic, public-good, DRR, DRF, DRI, climate, resilience, technology, development, or implementation initiatives.
1.9.5 Public listing controls. No country, mission, ministry, public authority, public institution, official, delegate, community actor, Indigenous participant where applicable, donor, insurer, capital reader, sponsor, provider, or institution shall be publicly listed, named, quoted, displayed, or described as endorsing, supporting, approving, adopting, recognizing, funding, validating, partnering with, or backing a Nexus Campaign unless the specific public language has been separately reviewed and authorized through the applicable public-safe communication pathway.
1.9.6 Global forum language. Where Nexus Campaigns are presented, discussed, convened, or advanced in global forums, public-facing language shall describe participation as public-good dialogue, learning, capacity-building, technical exchange, stakeholder mobilization, public authority learning, national resilience preparation, or Nexus Universe preparation only. Such participation shall not be framed as intergovernmental negotiation, official country endorsement, multilateral adoption, public authority approval, project approval, funding commitment, procurement action, policy decision, or implementation commitment.
1.9.7 High-level participation menu. Nexus Campaigns may provide high-level action options for leaders, missions, ministries, cities, public authorities, public institutions, international-facing actors, public finance actors, development institutions, philanthropic institutions, universities, and industry groups, including requesting a briefing, observing, nominating a focal point, nominating stakeholders, joining technical dialogue, hosting a learning room, supporting Working Group formation, supporting Nexus Universe preparation, offering in-kind support, supporting youth or volunteer mobilization, supporting public-safe reporting, and supporting readiness mapping. Each option shall carry no-endorsement, no-approval, no-finance, no-procurement, no-public-authority, no-consent, and no-execution boundaries.
1.9.8 Sovereignty and reputation safeguards. Nexus Campaigns shall not rank, shame, score, expose, or publicly criticize countries, communities, public authorities, or institutions through campaign dashboards, GRIx mappings, DRI records, public-safe summaries, or campaign metrics. Campaign intelligence shall support learning, evidence needs, public-good readiness, national capacity formation, and correction. It shall not become a sovereign rating, country ranking, public warning, investment rating, insurance score, credit score, official risk classification, or reputational sanction.
1.10 Campaigns as Non-Execution, No-Conversion, Public-Safe Mobilization
1.10.1 Non-execution doctrine. Nexus Campaigns shall mobilize, convene, support, train, record, route, publish safely, raise support where lawful, facilitate signatures and pledges, support volunteers, structure Working Groups, activate Competence Cells, generate Foundry inputs, prepare Nexus Universe outputs, maintain public-safe records, and prepare lawful handoff dependencies. They shall not by default deploy, operate, procure, finance, insure, underwrite, certify, regulate, command, warn, approve, implement, maintain, or execute projects.
1.10.2 Standard no-conversion rule. No Nexus Campaign mandate, campaign page, signature, petition, public statement, pledge, donation, support contribution, sponsorship, provider contribution, volunteer role, Working Group record, Competence Cell work package, campaign room, public-safe summary, DICE object, GRIx mapping, DRI record, iVRS record, Risk Academy pathway, iCRS credit, Risk Agency route, Foundry task, quest, bounty, build, Nexus Universe output, Marketplace listing, Registry entry, Studio workflow, Grid input, TRL evidence note, National Portfolio record, readiness note, public authority learning record, community participation, Indigenous protocol-sensitive engagement where applicable, media coverage, public dashboard, Campaign Record Card, support ledger, or handoff dependency package shall create endorsement, scientific consensus, certification, accreditation, academic degree, professional license, employment eligibility, compensation entitlement, legal compliance, ethical certification, privacy compliance, cybersecurity certification, government approval, public authority approval, public warning, official classification, procurement status, commercial approval, provider validation, supplier approval, financeability, insurability, underwriting acceptance, investment readiness, donor commitment, public finance allocation, rating, valuation, solicitation, offer, transaction readiness, maturity certification, warranty, community consent, Indigenous consent where applicable, consultation completion, protected knowledge permission, land access, public safety command, emergency response authority, deployment authorization, operational command, project authorization, or execution authority by implication.
1.10.3 Public-safe discipline. Nexus Campaigns shall maintain public-safe communication in all public pages, campaign updates, signature statements, fundraising or support materials, volunteer calls, public dashboards, media materials, social media materials, public authority learning materials, risk summaries, public-safe reports, Nexus Universe materials, and handoff-facing materials. Public-safe discipline shall prevent panic, false certainty, public authority overclaim, finance overclaim, insurance overclaim, procurement overclaim, certification overclaim, provider validation, sponsor control, community consent overclaim, protected knowledge exposure, data misuse, AI misuse, and execution overclaim.
1.10.4 Correctionability. Nexus Campaigns shall be correctionable by design. Campaigns shall provide concern reporting, overclaim reporting, data issue reporting, AI issue reporting, cyber issue reporting, safeguard concern reporting, public authority boundary reporting, finance boundary reporting, procurement boundary reporting, consent boundary reporting, sponsor/provider overclaim reporting, misinformation reporting, fraud reporting, and public-safe correction pathways. Campaign outputs may be corrected, clarified, downgraded, suspended, withdrawn, delisted, sealed, recalled, archived, or marked non-continuing.
1.10.5 Stop-the-line. Nexus Campaigns shall maintain stop-the-line authority where continued campaign activity may cause harm, overclaim, rights violation, public-safe failure, safeguard failure, security risk, data exposure, AI misuse, public authority boundary failure, finance boundary failure, procurement boundary failure, consent overclaim, protected knowledge exposure, volunteer harm, fraud, misinformation, or role collapse.
1.10.6 Archive and memory. Nexus Campaigns shall preserve institutional memory through archives. Archived campaign records shall preserve what was attempted, supported, signed, pledged, funded, built, reviewed, corrected, withdrawn, continued, handed off, or discontinued. Archive shall not imply current validity, current support, current approval, current readiness, or current authority.
1.10.7 Final formula. Nexus Campaigns shall be the public-good mobilization rail through which concern becomes signatures, signatures become support, support becomes teams, teams become Working Groups, Working Groups become Competence Cells, Competence Cells become Foundry tasks and builds, builds become Nexus Universe outputs, outputs become public-good records, records become readiness questions, readiness questions become lawful handoff dependencies, and handoff dependencies become competent downstream action where lawful. Throughout that sequence, Nexus Campaigns shall remain non-executing, public-safe, safeguard-aware, data-disciplined, support-transparent, nationally grounded, globally interoperable, correctionable, and bounded against false authority.
2. Campaign Classes, Scales, Product Families, and Mobilization Blueprints
2.1 Campaign Classification Doctrine
2.1.1 Classification purpose. Nexus Campaigns shall be classified so that each campaign has a clear purpose, scale, pathway, stakeholder surface, platform configuration, support model, evidence requirement, safeguard requirement, public-safe communication rule, Nexus Universe relationship, Foundry relationship, data and AI-use rule, readiness pathway, continuation rule, correction pathway, and archive status. Classification shall prevent campaign ambiguity, overclaim, duplicate mobilization, support misuse, stakeholder confusion, public authority overreach, finance overclaim, procurement drift, sponsor capture, provider validation, community consent misuse, and execution by implication.
2.1.2 Campaign class as routing tool. Campaign class shall determine the appropriate campaign template, Campaign Record Card, public page structure, action center tools, signature language, support tools, volunteer roles, campaign rooms, Working Group pathways, Competence Cell pathways, Nexus Foundry conversion options, DICE rules, GRIx and DRI interface, Risk Academy pathways, Nexus Universe routing, Marketplace listing rules, Registry status rules, Studio workflow options, Grid and TRL input limits, lawful handoff controls, and archive treatment.
2.1.3 Campaign class not authority. A campaign class shall describe scope and routing only. It shall not create endorsement, public authority approval, official classification, funding entitlement, procurement status, financeability, insurability, certification, rating, consent, deployment authorization, or execution authority.
2.1.4 Multi-class campaigns. A single campaign may carry more than one class where appropriate, including national and thematic, regional and DRR, community and data commons, youth and Nexus Universe, or Foundry and DRI. Multi-class campaigns shall identify the controlling class, secondary classes, applicable safeguards, platform tools, support rules, and no-conversion boundaries.
2.1.5 Campaign hierarchy without command. Campaign classes may be nested, linked, federated, or routed across global, regional, national, local, thematic, sectoral, university, youth, community, laboratory, Working Group, Competence Cell, Foundry, Universe, and handoff pathways. Such nesting shall create coordination, record linkage, and interoperability only. It shall not create command hierarchy, supremacy, legal agency, shared liability, public authority delegation, procurement authority, finance authority, or execution mandate.
2.2 National Nexus Campaigns
2.2.1 National Campaign defined. A National Nexus Campaign is a country-level, nationally routed, annual or cycle-based public-good mobilization campaign designed to organize all-hazards and whole-of-society participation around national resilience, DRR, DRF, DRI, public authority learning, National Working Groups, Nexus Competence Cells, National Portfolio preparation, Nexus Universe readiness, Nexus Foundry conversion, DICE contribution, Nexus Observatory linkage, GRIx and DRI records, Risk Academy learning, volunteer mobilization, support raising, public-safe reporting, and lawful national continuation.
2.2.2 Country-led and nationally owned. National Campaigns shall be country-led, nationally owned, and Nexus-supported. They shall preserve national law, national data controls, national public authority processes, national institutional context, national stakeholder ownership, national language needs, national community safeguards, Indigenous protocols where applicable, national procurement boundaries, national public finance boundaries, and lawful national routing.
2.2.3 National Campaign objectives. A National Campaign may pursue one or more of the following objectives:
2.2.3.1 mobilizing national stakeholders around a priority resilience, risk, hazard, systems, or technology theme;
2.2.3.2 creating or supporting National Working Groups;
2.2.3.3 activating Nexus Competence Cells;
2.2.3.4 collecting risk signals, evidence needs, data needs, and public authority learning questions;
2.2.3.5 forming National Systems-Risk Maps and National Challenge Briefs;
2.2.3.6 supporting DICE data commons and public-good knowledge commons;
2.2.3.7 producing GRIx mappings, DRI records, and Observatory Need Records;
2.2.3.8 converting national needs into Nexus Foundry tasks, quests, bounties, builds, technical packs, and public-good software;
2.2.3.9 training national volunteers, students, public-good contributors, Working Group participants, public authority learners, reviewers, maintainers, and campaign stewards;
2.2.3.10 preparing Nexus Universe participation, Core Build requests, Studio workflows, Marketplace candidates, Registry records, Grid inputs, TRL evidence notes, and National Portfolio outputs;
2.2.3.11 preparing lawful handoff dependency packages where appropriate.
2.2.4 National Campaign platform configuration. Each National Campaign should include a country campaign page, Campaign Record Card, National Campaign Mandate, stakeholder map, helix pathways, signature or public-support tools where appropriate, volunteer portal, Working Group workspace, Competence Cell workspace, Risk Academy pathway, DICE interface, Observatory / GRIx / DRI interface, Foundry conversion board, public authority learning room, readiness room, community safeguard room, support ledger where support is received, Nexus Universe routing room, incident channel, correction channel, and archive record.
2.2.5 National Campaign outputs. National Campaign outputs may include National Campaign Mandate, National Stakeholder Mobilization Record, National Helix Activation Record, National Systems-Risk Map, National Challenge Briefs, Working Group Formation Records, Competence Cell Work Packages, Volunteer Mobilization Records, Training and Micro-Credential Records, DICE Contributions, GRIx Mappings, DRI Records, Observatory Need Records, Foundry Tasks, Public Authority Learning Records, Safeguard Records, Public-Safe Summaries, Readiness Question Records, Arena Routing Records, National Continuation Records, Lawful Handoff Dependency Notes, Correction Notices, Non-Continuation Records, and Archives.
2.2.6 National Campaign boundary. National Campaigns shall not replace national plans, public authority decisions, emergency management systems, public consultation processes, national procurement systems, national public finance systems, regulatory processes, judicial processes, community consent processes, Indigenous protocols where applicable, or lawful implementation processes. National Campaigns support national mobilization; they do not govern the country.
2.3 Regional Nexus Campaigns
2.3.1 Regional Campaign defined. A Regional Nexus Campaign is a multi-country, corridor, basin, cluster, regional system, shared-hazard, or regional public-good mobilization campaign designed to support regional learning, regional coordination, regional Nexus Universe preparation, regional public-safe reporting, shared DRI, shared GRIx mappings, regional DICE contributions, cross-border resilience questions, and national campaign support without creating regional supremacy over national pathways.
2.3.2 Regional campaign purpose. Regional Campaigns may address shared risk corridors, river basins, coastal systems, island systems, mountain systems, ports and logistics corridors, regional food systems, regional energy systems, regional water systems, regional health systems, biodiversity systems, migration and humanitarian systems, cyber-physical interdependencies, telecom and Edge systems, regional climate adaptation needs, regional disaster-risk finance questions, and regional public authority learning.
2.3.3 Regional-to-national discipline. Regional Campaigns shall support National Campaigns and National Nodes; they shall not bypass or override them. Regional outputs affecting a country shall be routed through the relevant national pathway where national implications exist. Regional Campaigns shall not create regional authority, regional public warning, supranational approval, regional procurement preference, regional financeability, regional implementation mandate, or regional consent.
2.3.4 Regional stakeholder architecture. Regional Campaigns may mobilize regional organizations, national stakeholders, public authorities in learning roles, universities, regional development actors, insurers, donors, public finance readers, infrastructure actors, communities, Indigenous participants where applicable, youth networks, diaspora networks, labs, providers, sponsors, and civil society actors. Participation shall remain voluntary, non-binding, non-exclusive, non-decision, and role-separated.
2.3.5 Regional Campaign outputs. Regional Campaigns may produce Regional Systems-Risk Maps, Regional Hazard Briefs, Corridor Risk Records, Regional Observatory Needs, Regional GRIx mappings, DRI dashboard candidates, Regional Nexus Universe Arena Routing Records, Regional Working Group support records, Regional Competence Cell support records, National Node support notes, public-safe regional summaries, DRF readiness question maps, donor-readiness notes, public finance relevance notes, and regional archive records.
2.3.6 Regional Campaign boundary. Regional Campaigns shall not create supranational authority, public authority approval, procurement status, financeability, insurability, donor commitment, public finance allocation, regional certification, policy adoption, country ranking, public warning, emergency command, community consent, Indigenous consent where applicable, or execution authority by implication.
2.4 Global Nexus Campaigns
2.4.1 Global Campaign defined. A Global Nexus Campaign is a global public-good mobilization campaign addressing risks, technologies, systems, public-good assets, data commons, resilience priorities, DRR, DRF, DRI, Nexus Foundry builds, Nexus Universe preparation, youth mobilization, public-safe reporting, or lawful handoff dependency themes that require global participation, global visibility, cross-regional learning, or global public-good infrastructure.
2.4.2 Global Campaign purpose. Global Campaigns may mobilize stakeholders around global climate risk, disaster-risk reduction, disaster-risk finance readiness, disaster-risk intelligence, AI governance for resilience, cyber resilience, WEFH-B systems, public-good software, DICE commons, open technical baselines, protected knowledge safeguards, public authority learning, digital public infrastructure, sovereign compute, geospatial risk intelligence, humanitarian systems, public-safe communications, Nexus Universe global arenas, or global-to-national campaign pathways.
2.4.3 Participation without global endorsement. Global Campaigns shall not ask countries, missions, ministries, public authorities, global institutions, development actors, or public finance actors for endorsement by default. They shall invite voluntary participation, observer participation, technical dialogue, public-good cooperation, national stakeholder routing, learning participation, and Nexus Universe preparation. Global Campaign participation shall not create intergovernmental adoption, official country approval, treaty obligation, diplomatic commitment, public authority action, funding commitment, procurement action, or implementation commitment.
2.4.4 Global-to-national routing. Global Campaigns may create global templates, global public-safe materials, global challenge calls, global signature statements, global data commons, global Foundry tasks, global public-good software, and global Nexus Universe pathways, but national deployment, national public authority learning, national stakeholder mobilization, national data use, national public-safe publication, and national handoff shall route through national pathways where national implications exist.
2.4.5 Global Campaign outputs. Global Campaign outputs may include Global Campaign Statements, global public-good petitions or signatures, global supporter records, global public-safe summaries, global DICE commons objects, global Foundry tasks and builds, global GRIx and DRI methods, global learning pathways, global volunteer pathways, global Nexus Universe routing, global support ledgers, global correction records, and global archives.
2.4.6 Global Campaign boundary. Global Campaigns shall not create global public authority, international legal obligation, country endorsement, country ranking, official global standard, certification, procurement status, financeability, insurability, public finance allocation, public warning, emergency command, project authorization, or execution authority.
2.5 Thematic Nexus Campaigns
2.5.1 Thematic Campaign defined. A Thematic Nexus Campaign is a campaign organized around a defined risk, system, technology, population, public-good need, resilience question, data gap, public authority learning need, Foundry build need, Nexus Universe theme, or lawful handoff dependency question that may operate across national, regional, global, sectoral, local, university, youth, community, or lab pathways.
2.5.2 Thematic Campaign domains. Thematic Campaigns may include water security, energy resilience, food systems, health systems, biodiversity, climate adaptation, disaster-risk reduction, disaster-risk finance readiness, disaster-risk intelligence, infrastructure resilience, ports, logistics, cities, cyber resilience, AI and agentic systems, AI-RAN/O-RAN, telecom and Edge, geospatial systems, Earth observation, drones, robotics, sensors, IoT, OT, IIoT, sovereign compute, HPC, cloud, DLT, blockchain, DePIN, trust infrastructure, quantum-relevant security, semiconductors, advanced manufacturing, supply chains, humanitarian systems, public-safe communications, youth resilience, disability inclusion, public-interest safeguards, and protected knowledge.
2.5.3 Thematic Campaign routing. Thematic Campaigns may route into National Campaigns, Regional Campaigns, Global Campaigns, Nexus Foundry programs, Nexus Universe arenas, Risk Academy pathways, DICE commons, GRIx and DRI records, Nexus Observatory needs, Marketplace listings, Registry records, Studio workflows, Grid inputs, TRL evidence notes, and lawful handoff dependency packages.
2.5.4 Thematic Campaign safeguards. Each Thematic Campaign shall identify domain-specific safeguards, including data sensitivity, AI-use restrictions, cyber risk, geospatial risk, biosecurity-sensitive risk, infrastructure sensitivity, health-sensitive controls, public authority boundaries, finance and insurance boundaries, procurement boundaries, community safeguards, Indigenous protocols where applicable, protected knowledge, accessibility, youth safeguards, public-safe communication needs, and correction pathways.
2.5.5 Thematic Campaign boundary. A thematic campaign shall not become a standards authority, certification program, policy mandate, official public authority initiative, investment thesis, insurance rating, procurement preference, technology validation, provider endorsement, public warning, or execution program by implication.
2.6 Sector and Systems Campaigns
2.6.1 Sector Campaign defined. A Sector Campaign is a campaign organized around a defined sector, infrastructure class, system, or public service area for the purpose of mobilizing evidence, stakeholders, volunteers, public authority learning, technical builds, public-safe summaries, DRI records, readiness questions, and Nexus Universe outputs.
2.6.2 Systems Campaign defined. A Systems Campaign is a campaign organized around interdependent systems, including water-energy-food-health-biodiversity systems, climate-infrastructure systems, cyber-physical systems, logistics-energy-food systems, health-climate systems, urban-resilience systems, or public authority-data-technology systems. Systems Campaigns shall be especially attentive to cascading risk, compound risk, interdependencies, uncertainty, and public-safe communication.
2.6.3 Sector Campaign examples. Sector Campaigns may include Water Systems Campaigns, Energy Systems Campaigns, Food Systems Campaigns, Health Systems Campaigns, Biodiversity Campaigns, Climate Adaptation Campaigns, Infrastructure Resilience Campaigns, Ports and Logistics Campaigns, Cities Campaigns, Public Health and Biosecurity-Sensitive Campaigns, Cyber Campaigns, Telecom and Edge Campaigns, AI Governance Campaigns, Geospatial and Earth Observation Campaigns, Drone and Robotics Campaigns, Sovereign Compute Campaigns, DLT and Trust Infrastructure Campaigns, Semiconductor Resilience Campaigns, Supply Chain Campaigns, and Humanitarian Systems Campaigns.
2.6.4 Sector-specific records. Each Sector or Systems Campaign shall identify sector stakeholders, public authority interfaces, operator interfaces, provider interfaces, data classes, field conditions, public-safe reporting needs, hazard dependencies, technical dependencies, finance and insurance questions, procurement boundaries, community implications, protected knowledge risks, Nexus Foundry needs, and Nexus Universe routing.
2.6.5 Sector and Systems Campaign boundary. Sector and Systems Campaigns shall not certify sector readiness, approve operators, validate providers, create procurement status, create financeability or insurability, issue public warnings, substitute for regulators, or authorize deployment.
2.7 DRR Campaigns
2.7.1 DRR Campaign defined. A Disaster-Risk Reduction Campaign is a Nexus Campaign focused on reducing, preventing, preparing for, adapting to, or learning from disaster risk across hazards, systems, communities, infrastructure, technologies, and public authority learning pathways.
2.7.2 DRR Campaign purposes. DRR Campaigns may mobilize hazard awareness, exposure mapping, vulnerability mapping, community resilience, public-safe preparedness learning, critical service continuity, infrastructure resilience, field observation, public authority learning, youth participation, volunteer mobilization, public-safe reporting, DICE contributions, DRI records, GRIx mappings, Foundry tasks, Nexus Universe outputs, and National Portfolio records.
2.7.3 DRR Campaign action tools. DRR Campaigns may use signatures, public support statements, volunteer roles, public-safe explainers, hazard learning modules, community safeguard rooms, public authority learning rooms, DRI dashboard rooms, data commons requests, field observation support, translation, accessibility, support raising, Foundry build calls, and Nexus Universe readiness actions.
2.7.4 DRR Campaign outputs. DRR Campaign outputs may include Hazard Profiles, Exposure and Vulnerability Maps, Critical Services Continuity Maps, Community Resilience Briefs, Preparedness Learning Records, Public Authority Learning Questions, National Challenge Briefs, Foundry Task Lists, Public-Safe DRR Summaries, DRI Records, GRIx Mappings, and Correction Records.
2.7.5 DRR Campaign boundary. A DRR Campaign shall not issue emergency warnings, evacuation instructions, public safety orders, disaster declarations, official classifications, public authority decisions, operational commands, public procurement decisions, public finance allocations, or implementation mandates.
2.8 DRF Readiness Campaigns
2.8.1 DRF Readiness Campaign defined. A Disaster-Risk Finance Readiness Campaign is a Nexus Campaign focused on making disaster-risk, resilience needs, protection gaps, assumptions, dependencies, and public-good priorities more readable to capital readers, insurers, donors, development actors, public finance readers, National Consortium Companies, Project SPVs, and lawful downstream actors without creating finance, insurance, donor, public finance, procurement, or transaction status.
2.8.2 DRF Campaign purposes. DRF Readiness Campaigns may mobilize protection-gap analysis, risk-layering questions, insurance-readiness question maps, donor-readiness notes, public finance relevance notes, resilience finance literacy, data need records, DRI linkages, GRIx linkages, iVRS records, assumptions registers, dependency registers, diligence-gap registers, no-reliance rooms, and lawful handoff dependency records.
2.8.3 DRF Campaign rooms. DRF Readiness Campaigns may include Capital-Reader Rooms, Insurance-Reader Rooms, Donor-Reader Rooms, Public Finance Learning Rooms, DRF Readiness Rooms, National Portfolio Readiness Rooms, and Lawful Handoff Rooms. Each room shall be no-reliance, non-soliciting, non-transactional, confidentiality-aware, competition-compliant, and regulated-perimeter controlled.
2.8.4 DRF Campaign outputs. DRF Campaign outputs may include Protection-Gap Maps, Risk-Layering Question Maps, Insurance-Readiness Question Maps, Donor-Readiness Notes, Public Finance Relevance Notes, Assumptions Registers, Dependency Registers, Diligence-Gap Registers, No-Reliance Room Records, iVRS Inputs, GRIx Records, DRI Records, Safeguard Readiness Notes, and Handoff Dependency Notes.
2.8.5 DRF Campaign boundary. DRF Campaigns shall not create investment advice, securities crowdfunding, lending, banking, insurance, underwriting, brokerage, guarantee approval, valuation, rating, financeability, bankability, insurability, donor commitment, public finance allocation, solicitation, offer, transaction readiness, or regulated financial service by implication.
2.9 DRI and Risk Intelligence Campaigns
2.9.1 DRI Campaign defined. A Disaster-Risk Intelligence Campaign is a Nexus Campaign focused on mobilizing signals, indicators, dashboards, data, GRIx mappings, DRI records, Observatory needs, Edge observations, geospatial layers, digital twins, confidence labels, uncertainty statements, public-safe summaries, and correction pathways for public-good risk intelligence.
2.9.2 Risk intelligence purpose. DRI Campaigns shall help national, regional, global, thematic, local, and sectoral actors understand what must be observed, measured, interpreted, contextualized, communicated, corrected, and routed. Risk intelligence shall support learning, evidence needs, public-safe reporting, National Portfolio formation, Foundry builds, Nexus Universe preparation, and lawful handoff dependencies.
2.9.3 DRI Campaign action tools. DRI Campaigns may invite signal submissions, data contributions, indicator proposals, dashboard volunteers, geospatial reviewers, public-safe summary contributors, field observation supporters, DICE data stewards, GRIx mappers, AI workflow reviewers, and correction reporters.
2.9.4 DRI Campaign outputs. DRI Campaign outputs may include Signal Registers, Indicator Libraries, GRIx Category Mappings, DRI Dashboard Candidates, Public-Safe Risk Summaries, Confidence and Uncertainty Labels, Geospatial Sensitivity Reviews, Observatory Need Records, Edge Observation Needs, Digital Twin Needs, Data Quality Notes, and Correction Records.
2.9.5 DRI Campaign boundary. DRI Campaigns shall not create official public warnings, public authority classifications, sovereign ratings, credit ratings, insurance scores, investment ratings, emergency alerts, operational directives, intelligence products, policing tools, surveillance systems, or public authority decisions.
2.10 Public-Good Build Campaigns
2.10.1 Public-Good Build Campaign defined. A Public-Good Build Campaign is a Nexus Campaign that mobilizes contributors, volunteers, experts, data stewards, reviewers, maintainers, sponsors, providers, universities, labs, public-interest actors, and support around a defined Nexus Foundry task, quest, bounty, build, public-good software object, dataset, dashboard, Studio workflow, model card, system card, benchmark card, public-safe summary, or technical baseline.
2.10.2 Build campaign purpose. Public-Good Build Campaigns shall convert public-good need into buildable, reviewable, supportable, versioned, and correctionable outputs. They shall make public-good work visible, fundable through lawful support, contributable, reviewable, and routable without converting builds into deployment approval.
2.10.3 Build campaign action tools. Build Campaigns may include join-the-build tools, Git/repository links, task boards, bounty pages, support tools, compute support requests, data support requests, reviewer calls, maintainer calls, public-safe documentation, training pathways, Studio preparation, Marketplace candidate routing, Registry status, Grid input records, TRL evidence notes, and Nexus Universe readiness pathways.
2.10.4 Build campaign outputs. Build Campaign outputs may include Code Repositories, Public-Good Software, Dataset Packs, Method Packs, Dashboard Packs, Studio Workflow Packs, DRI Packs, GRIx Packs, Evidence Packs, Model Cards, System Cards, Benchmark Cards, Technical Reports, Public-Safe Summaries, Support Records, Correction Records, and Archive Records.
2.10.5 Build campaign boundary. A Public-Good Build Campaign shall not create product certification, production readiness, cybersecurity certification, procurement status, financeability, insurability, public authority approval, deployment authorization, operational responsibility, warranty, or execution authority.
2.11 Data Commons Campaigns
2.11.1 Data Commons Campaign defined. A Data Commons Campaign is a Nexus Campaign focused on mobilizing datasets, metadata, schemas, data stewards, rights records, AI-use labels, data-use labels, public-good knowledge objects, public-good software, documentation, data quality work, privacy controls, cyber controls, geospatial sensitivity review, protected knowledge controls, and DICE contribution pathways.
2.11.2 Data Commons purpose. Data Commons Campaigns shall make data more usable for public-good purposes without making data unrestricted. They shall support DICE, Nexus Observatory, GRIx, DRI, Nexus Foundry, Nexus Studio, Nexus Universe, National Portfolios, and lawful handoff dependencies through record-bearing data governance.
2.11.3 Data contribution boundary. Data contributed through a campaign shall not be treated as open, publishable, AI-trainable, transferable, commercializable, or handoff-ready unless the applicable Data Source Record, Data Rights Record, Data Use Terms, AI Use Terms, public-safe review, and safeguard review expressly permit such use.
2.11.4 Data Commons outputs. Data Commons Campaign outputs may include Data Source Records, Data Rights Records, Dataset Packs, Metadata Records, Schema Records, Data Dictionaries, AI-Use Records, Data-Use Labels, Quality Notes, Lineage Records, DICE Objects, Public-Safe Data Summaries, Secure-Room Routing Records, Correction Records, and Archives.
2.11.5 Data Commons boundary. Data Commons Campaigns shall not override privacy, data protection, data sovereignty, national data controls, public authority restrictions, community safeguards, Indigenous data governance where applicable, protected knowledge restrictions, cyber controls, geospatial sensitivity controls, or cross-border transfer rules.
2.12 Youth, University, Volunteer, and WILP Campaigns
2.12.1 Youth Campaign defined. A Youth Nexus Campaign is a campaign designed to mobilize youth participation, youth learning, student contribution, youth leadership, public-safe communication, micro-credentials, WILPs, volunteer roles, public-good builds, climate and resilience engagement, data stewardship, accessibility work, translation, and Nexus Universe participation under heightened youth safeguards.
2.12.2 University Campaign defined. A University Nexus Campaign is a campaign operated with or through a university, college, research institute, student group, faculty network, lab, or campus community to mobilize learning, research, WILPs, micro-credentials, data commons work, Foundry builds, public-safe reporting, National Working Group support, Nexus Universe preparation, and public-good contribution.
2.12.3 Volunteer Campaign defined. A Volunteer Nexus Campaign is a campaign focused on mobilizing volunteers for public-good tasks, support roles, translation, accessibility, public-safe summaries, dashboard testing, data stewardship, DRI mapping, GRIx mapping, field support within limits, correction reporting, campaign rooms, Nexus Universe support, and archive support.
2.12.4 WILP Campaign defined. A WILP Campaign is a campaign that connects work-integrated learning, supervised contribution, skills development, micro-credentials, public-good builds, data stewardship, risk intelligence, public-safe reporting, and Nexus Universe preparation. WILP Campaigns shall protect learners from exploitation, unclear IP terms, unsupported responsibility, unsafe data access, and false credential claims.
2.12.5 Youth and learner safeguards. Youth, university, volunteer, and WILP campaigns shall include role clarity, supervision, training, data limits, AI-use rules, field activity limits, public-safe review, accessibility, privacy protection, non-extraction, iCRS records, correction channels, and archive.
2.12.6 Youth and learner boundary. Youth, university, volunteer, and WILP campaigns shall not create employment, internship status, professional certification, academic degree, procurement qualification, public authority approval, financeability, insurability, deployment authority, or execution responsibility by implication.
2.13 Community and Public-Interest Campaigns
2.13.1 Community Campaign defined. A Community Nexus Campaign is a campaign focused on community resilience, place-based risk, local knowledge, public-safe reporting, accessibility, public-interest safeguards, youth participation, disability inclusion, humanitarian concerns, protected knowledge controls, public authority learning, National Portfolio input, and lawful routing under non-extractive conditions.
2.13.2 Public-Interest Campaign defined. A Public-Interest Nexus Campaign is a campaign organized around public-interest concerns, civic participation, transparency, accessibility, rights-bearing data, public-safe communication, disaster-risk learning, community resilience, digital public goods, public-good technology, correction, and accountability without becoming a political campaign, litigation campaign, official consultation, or public authority action by implication.
2.13.3 Community campaign action tools. Community and public-interest campaigns may include public-safe signature statements, story submissions, community safeguard rooms, accessibility reviews, translation support, local risk mapping, volunteer roles, community-facing summaries, public authority learning questions, DRI records, Foundry tasks, and Nexus Universe participation pathways.
2.13.4 Protected knowledge controls. Community and public-interest campaigns shall not extract, publish, geocode, score, benchmark, tokenize, AI-train, commercialize, credentialize, or hand off protected knowledge, Indigenous knowledge where applicable, sacred knowledge, culturally sensitive knowledge, place-based knowledge, rights-bearing data, or community-sensitive information without lawful and appropriate authority.
2.13.5 Consent boundary. Community participation, Indigenous protocol-sensitive engagement where applicable, workshop attendance, public-safe review, signature, pledge, data contribution, story contribution, or Nexus Universe participation shall not imply consent, consultation completion, rights waiver, land access, protected knowledge permission, public authority approval, endorsement, or project authorization.
2.14 Nexus Universe Campaigns
2.14.1 Nexus Universe Campaign defined. A Nexus Universe Campaign is a campaign designed to prepare a national, regional, global, thematic, university, youth, lab, community, Working Group, Competence Cell, Foundry, or public-good pathway for Nexus Universe and Nexus Core Build participation.
2.14.2 Nexus Universe Campaign purpose. Nexus Universe Campaigns may mobilize teams, signatures, support, volunteers, training, public-safe reporting, technical packs, data packs, Studio demonstrations, public authority learning rooms, readiness rooms, DICE objects, DRI dashboards, GRIx mappings, Foundry builds, National Portfolio summaries, and lawful handoff dependency candidates for annual surge participation.
2.14.3 Arena readiness. Nexus Universe Campaigns shall prepare Arena Routing Records identifying the appropriate arena, room, track, readiness status, public-safe status, data status, AI-use status, safeguard status, support status, review level, claims freeze status, data freeze status, technical freeze status, continuation pathway, correction pathway, and archive rule.
2.14.4 Core Build connection. Nexus Universe Campaigns may prepare Core Build Requests where technical, data, compute, network, dashboard, AI workflow, public-good software, secure-room, data-room, public-safe reporting, or simulation work should be concentrated in a Core Build environment. A Core Build Request shall not imply acceptance or deployment approval.
2.14.5 Nexus Universe boundary. Nexus Universe Campaigns shall not represent arena participation as endorsement, certification, public authority approval, procurement status, financeability, insurability, public warning, community consent, Indigenous consent where applicable, implementation commitment, or execution authority.
2.15 Lawful Handoff Readiness Campaigns
2.15.1 Lawful Handoff Readiness Campaign defined. A Lawful Handoff Readiness Campaign is a campaign designed to prepare evidence, data, technical, safeguard, public authority, legal, finance, insurance, support, provider-neutrality, correction, recall, and recipient responsibility records for possible downstream use by competent actors.
2.15.2 Handoff readiness purpose. Handoff Readiness Campaigns shall help clarify what is known, what is unknown, what dependencies exist, what safeguards remain, what public authority processes may be required, what legal review may be required, what finance or insurance questions remain, what data restrictions apply, what support status exists, and what recipients must independently diligence.
2.15.3 Handoff campaign outputs. Handoff Readiness Campaign outputs may include Evidence Packs, Public-Safe Summaries, Technical Readiness Notes, Data Readiness Notes, Safeguard Readiness Notes, Assumptions Registers, Dependency Registers, Diligence-Gap Registers, Public Authority Dependency Notes, Legal Dependency Notes, Provider-Neutrality Notes, Sponsor Influence Notes, Finance-Readiness Notes, Insurance-Readiness Question Maps, Donor-Readiness Notes, Public Finance Relevance Notes, Recipient Responsibility Statements, Correction and Recall Pathways, and Archive Notes.
2.15.4 Handoff recipient interface. Handoff Readiness Campaigns may interface with National Consortium Companies, Project SPVs, public authorities, providers, operators, contractors, funders, insurers, donors, public finance readers, universities, communities, and lawful implementation actors. Such interface shall be no-reliance by default and shall not authorize implementation.
2.15.5 Handoff boundary. Handoff Readiness Campaigns shall not create project approval, procurement approval, financing approval, insurance approval, donor commitment, public finance allocation, public authority approval, community consent, Indigenous consent where applicable, provider validation, deployment authorization, operational command, or execution authority.
2.16 Campaign Templates and Mobilization Blueprints
2.16.1 Template purpose. Nexus Campaigns shall use templates and mobilization blueprints to make campaign creation scalable, safe, public-good aligned, nationally adaptable, platform-native, and correctionable. Templates shall reduce friction while preserving data rights, public-safe communication, safeguards, sponsor/provider controls, no-conversion notices, support rules, and archive.
2.16.2 Standard template components. Each template should include campaign title, campaign class, scale, jurisdiction, purpose, problem statement, evidence status, campaign ask, signature language, pledge options, support options, volunteer roles, stakeholder pathways, Working Group pathway, Competence Cell pathway, DICE pathway, GRIx / DRI pathway, Foundry conversion pathway, Risk Academy pathway, Nexus Universe pathway, support ledger rules, safeguards, public-safe communication rules, data and AI-use rules, incident channel, correction channel, readiness levels, gates, metrics, continuation options, handoff boundaries, and archive rule.
2.16.3 National blueprint library. Nexus Campaigns may maintain national blueprints, including National All-Hazards Resilience Campaign, National DRR Campaign, National DRF Readiness Campaign, National DRI Dashboard Campaign, National Youth Resilience Campaign, National Water Security Campaign, National Heat Resilience Campaign, National Flood Resilience Campaign, National Cyber-Physical Resilience Campaign, National AI for Public-Good Resilience Campaign, National Community Safeguards Campaign, and National Nexus Universe Mobilization Campaign.
2.16.4 Regional blueprint library. Nexus Campaigns may maintain regional blueprints, including Regional Climate Risk Campaign, Regional Disaster-Risk Intelligence Campaign, Regional Corridor Resilience Campaign, Regional WEFH-B Campaign, Regional Humanitarian Systems Campaign, Regional Public Finance Learning Campaign, Regional Insurance-Readiness Campaign, and Regional Nexus Universe Arena Campaign.
2.16.5 Global blueprint library. Nexus Campaigns may maintain global blueprints, including Global Public-Good Software Campaign, Global DICE Commons Campaign, Global DRI Methods Campaign, Global Youth Resilience Campaign, Global AI for Resilience Campaign, Global Public-Safe Reporting Campaign, Global Protected Knowledge Safeguard Campaign, Global Nexus Universe Mobilization Campaign, and Global Lawful Handoff Readiness Campaign.
2.16.6 Thematic blueprint library. Nexus Campaigns may maintain thematic blueprints across water, energy, food, health, biodiversity, climate, infrastructure, ports, cities, cyber, AI, telecom, geospatial, drones, robotics, sensors, sovereign compute, DLT, quantum-relevant security, semiconductors, supply chains, humanitarian systems, public-safe communications, community safeguards, accessibility, and youth.
2.16.7 Template localization. Templates shall be localized for national law, language, culture, public authority structures, data protection, public-safe communication, community safeguards, Indigenous protocols where applicable, support rules, payment rules, sponsorship rules, provider contribution rules, volunteer rules, youth rules, and archive requirements. Localization shall not create semantic forking without controlled vocabulary mapping and boundary notes.
2.16.8 Template boundary. Use of a Nexus Campaign template or blueprint shall not create approval, endorsement, certification, procurement status, financeability, insurability, public authority action, consent, deployment authorization, or execution authority. A template is a structured starting point, not a validation.
2.17 Campaign Portfolio Architecture
2.17.1 Campaign portfolio defined. A Campaign Portfolio shall mean a structured set of campaigns linked by country, region, theme, hazard, sector, Nexus Universe cycle, Nexus Foundry program, National Portfolio, Working Group, Competence Cell, public authority learning pathway, youth pathway, data commons, or lawful handoff pathway.
2.17.2 National Campaign Portfolio. A National Campaign Portfolio may include the full set of active and archived campaigns in a country, including national, local, thematic, youth, university, community, sectoral, DRR, DRF, DRI, Foundry, Nexus Universe, and handoff readiness campaigns. The portfolio shall preserve national ownership, public-safe reporting, data sovereignty, national routing, and archive.
2.17.3 Regional Campaign Portfolio. A Regional Campaign Portfolio may include campaigns across multiple countries, hazards, corridors, ecosystems, or shared systems. It shall preserve national routing and shall not rank countries or create regional authority.
2.17.4 Global Campaign Portfolio. A Global Campaign Portfolio may include global public-good campaigns, global signature campaigns, global support campaigns, global data commons campaigns, global Foundry campaigns, global Nexus Universe campaigns, and global public-safe reporting campaigns. It shall not claim global endorsement or official adoption.
2.17.5 Portfolio status. Campaign Portfolios may display active, draft, under review, public-safe released, support-enabled, volunteer-enabled, Foundry-linked, DICE-linked, Observatory-linked, Nexus Universe candidate, Marketplace listed, Registry recorded, Studio prepared, Grid input candidate, TRL evidence candidate, handoff candidate, corrected, withdrawn, non-continuing, retired, or archived status.
2.17.6 Portfolio boundary. Campaign Portfolio inclusion shall not imply priority, approval, endorsement, funding, procurement, financeability, insurance approval, public authority action, certification, community consent, Indigenous consent where applicable, or execution authority.
2.18 Campaign Product Families
2.18.1 Product family purpose. Nexus Campaigns shall maintain product families to standardize the objects campaigns create, mobilize, support, publish, route, correct, and archive.
2.18.2 Campaign public products. Public products may include campaign pages, signature statements, public pledges, campaign briefings, public-safe summaries, story pages, public dashboards, volunteer calls, support pages, campaign kits, social media cards, video explainers, public event pages, public correction notices, and campaign archives.
2.18.3 Campaign institutional products. Institutional products may include briefing notes, participation records, technical dialogue records, public authority learning records, non-decision room records, stakeholder maps, Working Group mandates, Competence Cell workplans, sponsor terms, provider terms, host terms, data terms, support terms, and public listing approvals.
2.18.4 Campaign technical products. Technical products may include DICE objects, datasets, schemas, metadata, data-use labels, AI-use labels, GRIx mappings, DRI dashboards, Observatory Need Records, code repositories, public-good software, technical packs, Studio workflows, Grid inputs, TRL evidence notes, model cards, system cards, benchmark cards, and Core Build requests.
2.18.5 Campaign readiness products. Readiness products may include assumptions registers, dependency registers, diligence-gap registers, DRF readiness notes, insurance-readiness question maps, donor-readiness notes, public finance relevance notes, public authority dependency notes, legal dependency notes, provider-neutrality notes, sponsor influence notes, and lawful handoff dependency packages.
2.18.6 Campaign learning products. Learning products may include Risk Academy modules, WILPs, micro-credentials, volunteer training, reviewer training, maintainer training, public-safe communication training, data stewardship training, AI-use training, cyber hygiene training, public authority learning materials, and Nexus Universe preparation modules.
2.18.7 Campaign support products. Support products may include support ledgers, donation pages where lawful, sponsorship packages, in-kind contribution forms, compute support forms, equipment support forms, venue support records, scholarship support records, travel support records, challenge funding records, bounty funding records, refund or reallocation rules, and support archive records.
2.18.8 Campaign lifecycle products. Lifecycle products may include Campaign Mandates, Readiness Level Records, Gate Records, Claims Freeze Records, Data Freeze Records, Technical Freeze Records, Incident Records, Stop-the-Line Records, Correction Notices, Withdrawal Notices, Non-Continuation Records, Renewal Records, and Archive Records.
2.19 Campaign Naming, Identity, and Public Presentation
2.19.1 Naming discipline. Campaign names shall be accurate, public-safe, non-misleading, non-political by default, non-authority-claiming, non-procurement-signaling, non-finance-signaling, non-warning-signaling, and non-consent-signaling. Campaign names shall identify purpose without implying official approval, government adoption, public authority action, certification, funding commitment, or execution.
2.19.2 Preferred naming. Preferred campaign names may use terms such as “public-good,” “resilience,” “learning,” “readiness,” “mobilization,” “support,” “working group support,” “data commons,” “risk intelligence,” “Nexus Universe preparation,” “public-safe reporting,” “volunteer mobilization,” “capacity-building,” “technical dialogue,” and “lawful handoff readiness.”
2.19.3 Restricted naming. Campaign names should avoid “official,” “government-approved,” “certified,” “endorsed,” “authorized,” “investment-ready,” “insured,” “procurement-ready,” “public warning,” “emergency command,” “national approval,” “country adoption,” “UN-approved,” “World Bank-backed,” “IMF-backed,” “ministerial endorsement,” or similar language unless separately and lawfully true, approved, and recorded.
2.19.4 Public presentation. Campaign public pages shall display campaign class, steward, scope, status, review level, public-safe status, support status, data status, AI-use status, safeguard status, Nexus pathway, no-conversion notices, correction channel, support ledger where applicable, and archive status where relevant.
2.19.5 Identity boundary. Campaign identity shall not create legal personality, agency, employment, partnership, public authority status, procurement status, finance status, insurance status, certification status, consent status, deployment status, or execution status.
2.20 Final Section 2 Statement
2.20.1 Final classification formula. Nexus Campaigns shall be classified, templated, scaled, and routed so that every campaign can mobilize the right people, support, signatures, volunteers, data, evidence, builds, learning, safeguards, public-safe communication, readiness questions, Nexus Universe outputs, and lawful continuation pathways without becoming vague, unsafe, overclaimed, politically heavy, financially ambiguous, procurement-distorting, sponsor-captured, provider-validating, community-extractive, or execution-implying.
2.20.2 Final declaration. National Campaigns shall mobilize countries without bypassing national ownership. Regional Campaigns shall mobilize shared systems without creating regional supremacy. Global Campaigns shall mobilize public-good attention without seeking endorsement by implication. Thematic Campaigns shall mobilize focused domains without becoming standards or certification schemes. Sector Campaigns shall mobilize systems without authorizing operators. DRR Campaigns shall reduce risk without issuing warnings. DRF Campaigns shall make questions readable without creating finance. DRI Campaigns shall make intelligence useful without creating ratings. Build Campaigns shall produce public-good assets without authorizing deployment. Data Commons Campaigns shall make data useful without making data unrestricted. Youth, university, volunteer, and WILP Campaigns shall build capacity without exploiting learners. Community Campaigns shall protect participation without overclaiming consent. Nexus Universe Campaigns shall prepare annual surge without event overclaim. Lawful Handoff Readiness Campaigns shall prepare competent downstream actors without Nexus executing.
3. Nexus Campaign Digital Platform, Campaign Hub, Action Center, and Campaign Record Card
3.1 Nexus Campaign Digital Platform
3.1.1 Platform identity. The Nexus Campaign Digital Platform shall be the governed digital operating environment through which Nexus Campaigns are created, published, mobilized, supported, signed, pledged, funded where lawful, staffed, trained, routed, reviewed, corrected, renewed, and archived. It shall provide the public-facing and controlled-access infrastructure for campaign pages, campaign teams, stakeholder pathways, signatures, pledges, donations and support, volunteer roles, Working Group workspaces, Competence Cell workspaces, public authority learning rooms, readiness rooms, community safeguard rooms, Nexus Foundry conversion, DICE contributions, GRIx and DRI records, Nexus Observatory linkages, Risk Academy pathways, iCRS contribution records, Risk Agency routing, Nexus Universe preparation, Marketplace discovery, Registry status truth, Studio workflows, Grid inputs, TRL evidence notes, lawful handoff dependency packages, public-safe updates, support ledgers, incident reporting, correction, withdrawal, non-continuation, renewal, and archive.
3.1.2 Platform purpose. The platform shall allow Nexus Campaigns to combine the public mobilization power of signature and petition systems, the support-raising power of crowdfunding and civic support systems, the organizing power of volunteer and team platforms, the production discipline of open-source task / quest / bounty / build systems, the trust discipline of evidence registries, the learning discipline of Risk Academy, WILPs, and micro-credentials, the intelligence discipline of DICE, GRIx, DRI, and Nexus Observatory, the annual surge discipline of Nexus Universe, and the no-conversion discipline of the Nexus public-good stack.
3.1.3 Platform as public-good infrastructure, not marketplace by default. The platform shall be public-good mobilization infrastructure. It shall not be treated as a general fundraising website, securities crowdfunding portal, investment marketplace, procurement marketplace, public authority system, emergency command platform, public warning system, certification platform, social-credit system, vendor marketplace, lobbying platform, or political campaign system by default. Where any regulated, financial, public authority, procurement, charitable solicitation, lobbying, tax, consumer, payment, data, youth, or jurisdiction-specific obligations apply, the applicable module shall be governed by separate lawful terms and controls.
3.1.4 Platform operating formula. The platform shall operate through the following formula:
3.1.4.1 campaign creation is structured before public launch;
3.1.4.2 public support is recorded before it is claimed;
3.1.4.3 signatures are scoped before they are counted;
3.1.4.4 pledges are governed before they are accepted;
3.1.4.5 support is stewarded before it is spent or displayed;
3.1.4.6 volunteers are trained before sensitive work;
3.1.4.7 evidence is reviewed before public-safe reporting;
3.1.4.8 data rights are recorded before data use;
3.1.4.9 AI-use labels are applied before AI processing;
3.1.4.10 public authority participation is classified before public communication;
3.1.4.11 community participation is protected before public display;
3.1.4.12 sponsor and provider support is bounded before visibility;
3.1.4.13 campaign outputs are gated before Nexus Universe routing;
3.1.4.14 continuation is recorded before handoff;
3.1.4.15 correction remains available after every release;
3.1.4.16 archive preserves memory without current authority.
3.1.5 Platform user classes. The platform may support public users, supporters, signatories, donors where lawful, sponsors, providers, volunteers, students, WILP participants, micro-credential candidates, campaign teams, campaign stewards, National Nodes, National Nexus Consortiums, National Councils, National Working Groups, Nexus Competence Cells, Nexus Guilds, community participants, Indigenous protocol-sensitive participants where applicable, public-interest actors, universities, labs, public authorities in learning roles, public finance readers, capital readers, insurers, donors, development actors, media actors, reviewers, maintainers, mentors, public-safe communicators, data stewards, Risk Academy learners, Risk Agency candidates, Nexus Universe participants, Marketplace users, Registry viewers, Studio users, Grid reviewers, TRL reviewers, and lawful handoff recipients.
3.1.6 Platform trust posture. The platform shall make status visible and limits visible. Every public or controlled platform object should show, as applicable, its steward, campaign class, jurisdiction, support status, signature status, pledge status, volunteer status, review level, public-safe status, data status, AI-use status, safeguard status, sponsor or provider status, Nexus pathway, Nexus Universe status, Marketplace status, Registry status, Studio status, Grid / TRL status, correction status, archive status, and no-conversion notices.
3.2 Campaign Creation Studio
3.2.1 Campaign Creation Studio defined. The Campaign Creation Studio shall be the governed platform environment through which eligible campaign creators, National Nodes, National Nexus Consortiums, Working Groups, Competence Cells, Guilds, universities, labs, community actors, youth teams, public-interest actors, and approved campaign stewards may draft, classify, configure, review, and submit campaigns before public launch or controlled circulation.
3.2.2 Campaign creation intake. The Campaign Creation Studio shall require campaign creators to identify, at minimum:
3.2.2.1 campaign name;
3.2.2.2 campaign class and scale;
3.2.2.3 jurisdiction, country, region, locality, sector, domain, or theme;
3.2.2.4 steward and responsible organization or team;
3.2.2.5 campaign purpose;
3.2.2.6 problem statement;
3.2.2.7 public-good rationale;
3.2.2.8 intended participants;
3.2.2.9 signature or petition language where applicable;
3.2.2.10 pledge and support options where applicable;
3.2.2.11 volunteer roles;
3.2.2.12 data needs and data sensitivity;
3.2.2.13 AI-use expectations;
3.2.2.14 safeguard issues;
3.2.2.15 public authority relevance;
3.2.2.16 finance or insurance relevance;
3.2.2.17 procurement risk;
3.2.2.18 sponsor or provider relationships;
3.2.2.19 Nexus Foundry relationship;
3.2.2.20 DICE, GRIx, DRI, Observatory, Risk Academy, iCRS, Risk Agency, Marketplace, Registry, Studio, Grid, TRL, Nexus Universe, and handoff relationships where applicable;
3.2.2.21 correction pathway;
3.2.2.22 non-continuation rule;
3.2.2.23 archive rule.
3.2.3 Campaign template selection. Campaign creators shall select an approved campaign template or blueprint where available, including national resilience, regional resilience, global public-good, thematic, DRR, DRF readiness, DRI, public-good build, data commons, youth, university, volunteer, community, Nexus Universe, or lawful handoff readiness templates. Template use shall accelerate campaign setup without substituting for review.
3.2.4 Campaign classification prompts. The Campaign Creation Studio shall use guided prompts to classify campaign risks, including public authority risk, finance risk, insurance risk, procurement risk, legal risk, data risk, AI risk, cyber risk, geospatial risk, dual-use risk, community risk, Indigenous protocol relevance where applicable, protected knowledge risk, youth risk, volunteer safety risk, media risk, sponsor or provider influence risk, and handoff overclaim risk.
3.2.5 Public-safe drafting support. The Campaign Creation Studio may support drafting of campaign pages, signature statements, pledge language, support descriptions, volunteer calls, social media cards, public-safe summaries, and leader briefings through controlled templates and, where appropriate, AI-assisted drafting subject to human review, public-safe checks, and no-conversion checks.
3.2.6 Pre-launch review. A campaign shall not be publicly launched unless applicable pre-launch checks have been completed or the campaign is expressly marked as draft, pilot, internal, restricted, invitation-only, no-publication, or archive-only. Pre-launch checks may include identity check, steward check, public-safe communication review, support configuration review, data and AI-use review, safeguard review, sponsor and provider review, public authority boundary review, finance and insurance boundary review, procurement boundary review, and legal terms check.
3.2.7 Campaign launch states. The Campaign Creation Studio may classify campaigns as draft, steward-submitted, under review, internal pilot, invite-only, public-safe launch-ready, public launch, support-enabled, signature-enabled, volunteer-enabled, Foundry-linked, Universe-candidate, Marketplace-candidate, Registry-recorded, paused, corrected, withdrawn, non-continuing, or archived.
3.2.8 Creation boundary. Submission or drafting of a campaign in the Campaign Creation Studio shall not create approval, public launch entitlement, funding entitlement, support acceptance, Nexus Universe routing, Marketplace status, Registry status, public authority participation, endorsement, procurement status, financeability, insurability, certification, consent, deployment authorization, or execution authority.
3.3 Public Campaign Page
3.3.1 Public Campaign Page defined. Each publicly visible Nexus Campaign may have a Public Campaign Page serving as the campaign’s primary public-safe interface. The page shall present campaign purpose, scope, problem statement, public-good rationale, campaign ask, campaign actions, steward, status, support needs, volunteer opportunities, learning pathways, progress, outputs, safeguards, public-safe updates, correction channel, no-conversion notices, and archive status.
3.3.2 Required public page elements. A Public Campaign Page should include:
3.3.2.1 campaign name;
3.3.2.2 campaign class;
3.3.2.3 campaign scale;
3.3.2.4 jurisdiction or thematic scope;
3.3.2.5 campaign steward;
3.3.2.6 campaign status;
3.3.2.7 campaign purpose;
3.3.2.8 public-good rationale;
3.3.2.9 campaign ask;
3.3.2.10 action buttons;
3.3.2.11 signature language where applicable;
3.3.2.12 pledge and support options where applicable;
3.3.2.13 volunteer roles;
3.3.2.14 Working Group and Competence Cell linkages;
3.3.2.15 learning pathways;
3.3.2.16 Nexus Foundry relationship;
3.3.2.17 DICE, GRIx, DRI, and Observatory linkages where applicable;
3.3.2.18 Nexus Universe relationship where applicable;
3.3.2.19 public-safe summaries;
3.3.2.20 support ledger where applicable;
3.3.2.21 campaign progress;
3.3.2.22 safeguard statement;
3.3.2.23 data and AI-use summary;
3.3.2.24 sponsor and provider display where applicable;
3.3.2.25 correction channel;
3.3.2.26 no-conversion notice;
3.3.2.27 archive and version information.
3.3.3 Problem statement discipline. The problem statement shall describe the issue being addressed without exaggerating certainty, assigning unsupported blame, creating public panic, issuing public warnings, implying government failure, implying official classification, making finance claims, making procurement claims, or exposing sensitive information.
3.3.4 Campaign ask discipline. A campaign ask shall be precise. It may ask users to sign, pledge, donate where lawful, volunteer, learn, join a team, submit evidence, contribute data subject to rights, propose a build, attend a room, share public-safe materials, nominate stakeholders, request a briefing, or report a concern. A campaign ask shall not imply legal mandate, public authority approval, investment opportunity, procurement opportunity, emergency instruction, or execution.
3.3.5 Public support display. Signature counts, supporter counts, pledge counts, volunteer counts, support raised, and other public participation metrics may be displayed where lawful and public-safe. Such metrics shall not be represented as public mandate, public consultation, public authority approval, community consent, Indigenous consent where applicable, financeability, procurement priority, policy adoption, or official ranking.
3.3.6 Sponsor and provider display. Public Campaign Pages may acknowledge sponsors, providers, hosts, media partners, universities, labs, or other supporters only according to approved display rules. Display shall identify support without implying control, validation, endorsement, procurement status, financeability, insurability, public authority approval, certification, consent, deployment, or execution.
3.3.7 Public authority display. Public authorities, missions, ministries, public institutions, officials, or delegates shall not be displayed as endorsers, supporters, partners, adopters, funders, approvers, or validators unless the precise public language has been separately reviewed and authorized. Public authority participation shall normally be described as observer participation, learning participation, technical dialogue, public authority learning, national stakeholder routing, or Nexus Universe preparation.
3.3.8 Public page correction. Public Campaign Pages shall include visible correction pathways and, where necessary, correction notices, public-safe clarifications, withdrawn statements, updated counts, updated support information, updated review status, and archive notices.
3.3.9 Public page boundary. Publication of a Public Campaign Page shall not create endorsement, approval, public authority action, procurement status, financeability, insurability, certification, consent, deployment authorization, or execution authority.
3.4 Campaign Action Center
3.4.1 Campaign Action Center defined. The Campaign Action Center shall be the platform module through which supporters, participants, volunteers, institutions, experts, public authorities in learning roles, sponsors, providers, donors, insurers, capital readers, universities, labs, communities, and public-interest actors take structured campaign actions.
3.4.2 Standard action modules. The Campaign Action Center may include:
3.4.2.1 Sign the Campaign for scoped public support;
3.4.2.2 Make a Pledge for time, expertise, data, equipment, venue, compute, translation, accessibility, communications, or other support;
3.4.2.3 Donate or Support where lawful and configured;
3.4.2.4 Offer In-Kind Support for non-cash contributions;
3.4.2.5 Volunteer for campaign roles;
3.4.2.6 Join a Team for local, national, thematic, university, youth, or build-based participation;
3.4.2.7 Join a Working Group where open or by application;
3.4.2.8 Join a Competence Cell Pathway where open or by application;
3.4.2.9 Take a Learning Pathway through Risk Academy, WILPs, or micro-credentials;
3.4.2.10 Submit Evidence for documents, observations, datasets, reports, public-safe materials, or research inputs;
3.4.2.11 Contribute Data subject to DICE data rights and AI-use rules;
3.4.2.12 Propose a Build for Foundry conversion;
3.4.2.13 Attend a Room such as public authority learning, DRR learning, DRF readiness, DRI dashboard, community safeguard, media, volunteer, or Nexus Universe readiness rooms;
3.4.2.14 Request a Briefing for leaders, missions, ministries, cities, universities, sponsors, providers, donors, insurers, public finance readers, or labs;
3.4.2.15 Nominate a Stakeholder such as an institution, expert, community group, youth group, lab, public authority contact, donor, provider, sponsor, or media actor;
3.4.2.16 Share Public-Safe Materials using approved campaign media;
3.4.2.17 Report a Concern for overclaim, fraud, safeguarding, data, AI, cyber, public authority, finance, procurement, consent, sponsor, provider, misinformation, or platform issues;
3.4.2.18 Follow the Campaign for updates, milestones, public-safe reports, Nexus Universe status, correction notices, and archive.
3.4.3 Action eligibility. Some actions may be open to the public; others may require account status, training, verification, invitation, age eligibility, role approval, data access approval, public-safe review, safeguard review, or institutional authorization. The platform shall distinguish open actions from controlled actions.
3.4.4 Action records. Material campaign actions shall generate records, including Signature Records, Pledge Records, Support Records, Volunteer Role Records, Training Records, Evidence Submission Records, Data Contribution Records, Build Proposal Records, Room Attendance Records, Briefing Request Records, Stakeholder Nomination Records, Concern Reports, and Follow Records.
3.4.5 Action limits. Campaign actions shall be scoped. Signing shall not equal consent. Pledging shall not equal binding contribution until accepted under terms. Donating shall not buy influence. Volunteering shall not create employment or authority. Submitting evidence shall not validate the evidence. Attending a room shall not create approval. Requesting a briefing shall not create partnership. Nominating a stakeholder shall not create affiliation.
3.4.6 Action Center boundary. Use of the Campaign Action Center shall not create endorsement, public authority approval, procurement, finance, insurance, certification, consent, deployment, command, employment, agency, or execution by implication.
3.5 Campaign Dashboard
3.5.1 Campaign Dashboard defined. The Campaign Dashboard shall be the public-safe or controlled platform view through which campaign teams, stewards, participants, and authorized viewers monitor campaign status, progress, actions, outputs, support, risks, safeguards, readiness, corrections, and archive.
3.5.2 Dashboard modes. A Campaign Dashboard may have public mode, steward mode, Working Group mode, Competence Cell mode, National Node mode, public authority learning mode, readiness room mode, support ledger mode, Nexus Universe mode, and archive mode. Each mode shall display only information appropriate to access rights, public-safe status, data rules, and safeguard restrictions.
3.5.3 Public dashboard metrics. Public dashboards may display public-safe metrics such as supporter counts, signatures, volunteers trained, Working Groups formed, Competence Cell work packages, public-safe summaries, DICE contributions, GRIx mappings, DRI dashboard candidates, Foundry tasks, builds, learning completions, Nexus Universe readiness, support received where lawful, support used, corrections, and archive status.
3.5.4 Non-vanity metrics. Campaign dashboards shall prioritize evidence-bearing progress over vanity metrics. Attendance, media impressions, sponsor logos, social engagement, public authority attendance, capital-reader attendance, or famous speakers shall not be treated as campaign success by themselves. Core metrics shall focus on signals processed, records created, work completed, safeguards reviewed, volunteers trained, public-safe outputs issued, corrections made, and lawful continuation prepared.
3.5.5 Sensitive dashboard controls. Dashboards involving sensitive data, public authority data, health-sensitive data, infrastructure-sensitive data, cyber-sensitive information, geospatial-sensitive layers, protected knowledge, youth data, community-sensitive data, sponsor-confidential data, provider-confidential data, or readiness-room data shall be access-controlled, redacted, aggregated, delayed, sealed, or withheld as appropriate.
3.5.6 Dashboard interpretation labels. Dashboards shall include interpretation labels explaining what each metric means and does not mean. A dashboard metric shall not be interpreted as official status, public authority approval, national ranking, community consent, financeability, procurement status, risk rating, insurance score, certification, or execution readiness unless separately and lawfully recorded.
3.5.7 Dashboard correction. Dashboard errors shall be corrected through visible or controlled correction records depending on public meaning. Dashboard correction may include updated counts, corrected status, withdrawn metrics, revised public-safe summaries, Registry updates, Marketplace updates, Studio status changes, Grid input withdrawals, TRL downgrades, support ledger corrections, and archive notes.
3.5.8 Dashboard boundary. Campaign Dashboards are status and progress surfaces. They shall not be treated as public authority dashboards, emergency dashboards, investment dashboards, procurement dashboards, official risk dashboards, insurance dashboards, or certification dashboards by implication.
3.6 Campaign Record Card
3.6.1 Campaign Record Card defined. A Campaign Record Card shall be the structured status-truth profile for each Nexus Campaign. It shall summarize the campaign’s identity, class, scale, steward, pathway, review status, public-safe status, support status, participation status, data status, AI-use status, safeguard status, Nexus relationships, readiness level, incidents, corrections, continuation, and archive.
3.6.2 Record Card purpose. The Campaign Record Card shall prevent public confusion by showing what the campaign is, what it has produced, what stage it is in, what support it has received, what reviews have occurred, what boundaries apply, what has been corrected, and what may or may not be relied upon.
3.6.3 Required Record Card fields. A Campaign Record Card should include:
3.6.3.1 campaign name;
3.6.3.2 campaign identifier;
3.6.3.3 campaign class;
3.6.3.4 campaign scale;
3.6.3.5 country, region, locality, theme, or sector;
3.6.3.6 steward;
3.6.3.7 linked National Node or Nexus body where applicable;
3.6.3.8 linked Working Groups;
3.6.3.9 linked Competence Cells;
3.6.3.10 hazard or thematic scope;
3.6.3.11 DRR, DRF, and DRI scope;
3.6.3.12 campaign actions enabled;
3.6.3.13 signature status;
3.6.3.14 pledge status;
3.6.3.15 support status;
3.6.3.16 volunteer status;
3.6.3.17 data status;
3.6.3.18 AI-use status;
3.6.3.19 public-safe status;
3.6.3.20 safeguard status;
3.6.3.21 sponsor and provider status;
3.6.3.22 DICE linkage;
3.6.3.23 GRIx / DRI linkage;
3.6.3.24 Nexus Observatory linkage;
3.6.3.25 Nexus Foundry linkage;
3.6.3.26 Risk Academy linkage;
3.6.3.27 iCRS linkage;
3.6.3.28 Risk Agency interface status;
3.6.3.29 Nexus Universe status;
3.6.3.30 Marketplace status;
3.6.3.31 Registry status;
3.6.3.32 Studio status;
3.6.3.33 Grid and TRL status;
3.6.3.34 readiness level;
3.6.3.35 handoff status;
3.6.3.36 incident status;
3.6.3.37 correction status;
3.6.3.38 non-continuation status;
3.6.3.39 archive status;
3.6.3.40 standard no-conversion notice.
3.6.4 Record Card public and controlled fields. Some Record Card fields may be public; others may be controlled, restricted, sealed, or archive-only depending on data sensitivity, public authority restrictions, community safeguards, protected knowledge, cyber sensitivity, youth privacy, finance or insurance room confidentiality, support confidentiality, or legal restrictions.
3.6.5 Record Card badges. The Record Card may display status badges such as Mandate Recorded, Public-Safe Reviewed, Safeguard Screened, Data Terms Recorded, AI-Use Labels Applied, Working Group Linked, Competence Cell Linked, Foundry Linked, DICE Linked, Observatory Linked, GRIx / DRI Linked, Risk Academy Linked, Nexus Universe Candidate, Core Build Candidate, Marketplace Listed, Registry Recorded, Studio Prepared, Grid Input Candidate, TRL Evidence Candidate, Correction Available, Support Ledger Active, Archived, or Non-Continuing. Such badges shall describe recorded status only.
3.6.6 Prohibited badge meanings. Record Card badges shall not use or imply approved, certified, official, government-backed, finance-ready, investment-ready, insured, procurement-ready, vendor-approved, risk-rated, community-consented, Indigenous-consented where applicable, execution-ready, or deployment-ready unless separately and lawfully true and recorded.
3.6.7 Record Card correction. The Campaign Record Card shall be updated when status changes, support changes, public-safe review changes, data status changes, AI-use status changes, safeguard status changes, sponsor or provider status changes, Nexus Universe routing changes, Marketplace status changes, Registry status changes, Studio status changes, Grid or TRL status changes, handoff status changes, incidents occur, corrections occur, or archive occurs.
3.6.8 Record Card boundary. A Campaign Record Card preserves campaign status truth. It shall not create approval, certification, procurement status, financeability, insurability, public authority action, consent, deployment authorization, or execution authority.
3.7 Campaign Trust Layer
3.7.1 Trust Layer defined. The Campaign Trust Layer shall be the platform’s integrated system for identity, stewardship, verification, records, support transparency, public-safe review, safeguard review, data governance, AI-use governance, sponsor and provider disclosure, role classification, moderation, fraud prevention, correction, and archive.
3.7.2 Trust elements. The Campaign Trust Layer may include campaign steward verification, organization verification, payment recipient verification where support is enabled, campaign classification, public-safe review, data and AI-use review, safeguard review, sponsor and provider disclosure, support ledger, incident reporting, concern reporting, bot and duplicate detection, identity verification tiers, role permissions, public listing approvals, and correction pathways.
3.7.3 Steward verification. Campaign stewards may be verified according to role, organization, National Node linkage, Working Group linkage, Competence Cell linkage, university affiliation, lab affiliation, community role, youth role, sponsor role, provider role, or other pathway. Steward verification shall not create endorsement, certification, public authority approval, procurement status, financeability, or execution authority.
3.7.4 Organization verification. Organizations participating in campaigns may be verified for identity and role. Verification shall not validate the organization’s products, services, legal compliance, public authority status, procurement eligibility, financeability, or public-good legitimacy beyond the recorded scope.
3.7.5 Payment and support verification. Where a campaign receives funds or support, the platform shall identify the support recipient, fiscal steward, payment processor, restrictions, public support status, support use, refund or reallocation rules where applicable, and support ledger. Payment verification shall not imply charitable status, tax deductibility, public finance approval, or legal compliance beyond the recorded terms.
3.7.6 Review status. Trust Layer review status may include unreviewed, self-declared, steward-reviewed, public-safe reviewed, safeguard screened, data reviewed, AI-use reviewed, finance-boundary reviewed, public authority boundary reviewed, support reviewed, sponsor/provider reviewed, Nexus Universe reviewed, or archived. Review status shall describe review performed, not approval created.
3.7.7 Fraud and abuse controls. The Trust Layer shall include mechanisms for detecting and addressing fake campaigns, impersonation, fraudulent support appeals, fake signatures, bot activity, duplicate signatures, false endorsements, false public authority claims, false sponsor or provider claims, false impact claims, misinformation, harassment, protected knowledge exposure, data leaks, abusive content, and campaign manipulation.
3.7.8 Trust Layer boundary. Trust Layer controls increase reliability and reduce misuse. They shall not create certification, guarantee, warranty, official approval, public authority validation, procurement status, financeability, insurability, or execution readiness.
3.8 Campaign Rooms
3.8.1 Campaign Rooms defined. Campaign Rooms are platform-native spaces for structured campaign work, learning, support, review, readiness, community safeguarding, public-safe communication, Nexus Universe preparation, and lawful routing. Campaign Rooms may be public, invitation-only, controlled, confidential, secure-room-linked, data-room-linked, or archive-only depending on purpose and sensitivity.
3.8.2 Room classes. Campaign Rooms may include Signature Rooms, Support Rooms, Volunteer Rooms, Working Group Rooms, Competence Cell Rooms, Public Authority Learning Rooms, DRR Learning Rooms, DRF Readiness Rooms, DRI Dashboard Rooms, Capital-Reader Rooms, Insurance-Reader Rooms, Donor-Reader Rooms, Public Finance Learning Rooms, Community Safeguard Rooms, Youth and Volunteer Rooms, Media and Public-Safe Communications Rooms, Nexus Universe Rooms, Core Build Preparation Rooms, Data Rooms, Secure Rooms, Studio Rooms, and Handoff Rooms.
3.8.3 Room terms. Each Campaign Room shall have room terms identifying purpose, participant class, access rules, confidentiality, permitted use, prohibited use, data rules, AI-use rules, public-safe rules, public authority boundary, finance and insurance boundary, procurement boundary, consent boundary, sponsor/provider boundary, output status, recording status, correction pathway, and archive.
3.8.4 Public Authority Learning Rooms. Public Authority Learning Rooms shall support non-decision learning by public authorities. They shall not issue warnings, official classifications, approvals, procurement decisions, public finance decisions, regulatory comfort, permits, licenses, emergency commands, or public authority decisions.
3.8.5 Readiness Rooms. DRF, capital-reader, insurance-reader, donor-reader, and public finance learning rooms shall be no-reliance, non-soliciting, non-transactional, confidentiality-aware, competition-compliant, and regulated-perimeter controlled. They shall generate readiness questions, not finance or insurance outcomes.
3.8.6 Community Safeguard Rooms. Community Safeguard Rooms shall support non-extractive participation, public-safe communication, accessibility, protected knowledge controls, consent boundary review, Indigenous protocol-sensitive review where applicable, and community-facing correction. They shall not create consent, consultation completion, rights waiver, land access, protected knowledge permission, or project authorization.
3.8.7 Media Rooms. Media and Public-Safe Communications Rooms shall prepare approved public-safe materials, media briefings, social media guidance, sponsor/provider display language, no-warning language, no-approval language, no-finance language, no-procurement language, correction notices, and public repair.
3.8.8 Nexus Universe Rooms. Nexus Universe Rooms shall prepare campaign outputs for annual surge, including arena routing, Core Build preparation, claims freeze, data freeze, technical freeze, public-safe review, safeguard review, readiness review, continuation planning, and archive.
3.8.9 Room boundary. Participation in a Campaign Room shall not create endorsement, approval, public authority action, procurement, finance, insurance, certification, consent, deployment, command, employment, agency, or execution by implication.
3.9 Campaign Team Pages
3.9.1 Campaign Team Page defined. A Campaign Team Page shall be a platform profile for a team formed around a campaign, country, region, city, university, youth chapter, community, hazard, theme, Working Group, Competence Cell, Foundry build, DICE contribution, DRI dashboard, GRIx mapping, Nexus Universe pathway, or lawful handoff readiness pathway.
3.9.2 Team purposes. Campaign teams may coordinate volunteers, assign roles, manage tasks, prepare events, support public-safe reporting, collect evidence, work on data, contribute to builds, translate materials, conduct accessibility review, support community safeguards, prepare Nexus Universe outputs, maintain support updates, and report concerns.
3.9.3 Team roles. Campaign teams may include team lead, campaign coordinator, data steward, volunteer steward, communications steward, safeguard steward, technical lead, public authority learning liaison, community liaison, Indigenous protocol liaison where applicable, youth lead, accessibility lead, support lead, sponsor liaison, provider liaison, media liaison, Nexus Universe liaison, correction steward, and archive steward.
3.9.4 Team status. Team status may be unverified, registered, trained, reviewed, National Node-linked, Working Group-linked, Competence Cell-linked, Foundry-linked, DICE-linked, Observatory-linked, Nexus Universe candidate, Nexus Universe-ready, corrected, non-continuing, retired, or archived. Team status shall not create authority or certification.
3.9.5 Team formation controls. Teams may self-mobilize, but public visibility, support collection, sensitive data access, public authority engagement, youth participation, community engagement, sponsor/provider display, and Nexus Universe routing may require review.
3.9.6 Chapters. Campaign Teams may become or support chapters, including national chapters, city chapters, university chapters, youth chapters, diaspora chapters, community chapters, lab chapters, or thematic chapters. Chapter status shall be scoped and shall not imply legal agency, endorsement, approval, or authority.
3.9.7 Team boundary. A Campaign Team is a mobilization and contribution unit only. It shall not become a public authority, procurement body, finance actor, insurer, certifier, representative of a community, representative of Indigenous peoples where applicable, official national delegation, operator, contractor, or execution vehicle by implication.
3.10 Chapters, Ambassadors, Champions, and Self-Mobilization
3.10.1 Chapter model. Nexus Campaigns may support chapters to organize local, national, university, youth, diaspora, community, lab, or thematic campaign participation. Chapters shall operate under recorded terms, public-safe communication rules, sponsor/provider boundaries, data rules, volunteer rules, safeguarding rules, correction pathways, and archive.
3.10.2 Ambassador model. Campaigns may designate Campaign Ambassadors, Youth Ambassadors, University Ambassadors, City Ambassadors, Diaspora Ambassadors, Community Ambassadors, Technical Ambassadors, Data Ambassadors, Public-Safe Communications Ambassadors, Accessibility Ambassadors, Nexus Universe Ambassadors, and other scoped mobilization roles.
3.10.3 Champion model. Campaigns may recognize Community Champions, Technical Champions, Data Champions, Public-Safe Communications Champions, Accessibility Champions, Volunteer Champions, Sponsor Support Champions, Provider Contribution Champions, and Nexus Universe Champions. Champion status shall recognize contribution or mobilization within scope only.
3.10.4 Self-mobilization. The platform may allow users to start draft local campaigns, team pages, chapters, signature drives, volunteer groups, public-safe events, support requests, or build proposals. Public launch shall require applicable checks, including identity, campaign class, public-safe language, no-conversion notices, safeguard screens, support rules, and data rules.
3.10.5 Ambassador and champion boundaries. Ambassador, champion, chapter, or self-mobilization status shall not create authority, endorsement, certification, employment, agency, partnership, public authority role, procurement status, financeability, insurance status, community representation, Indigenous representation where applicable, consent, deployment authorization, or execution authority.
3.10.6 Conduct rules. Ambassadors, champions, chapter leads, and self-mobilizing teams shall follow conduct rules prohibiting false authority claims, false public authority claims, false sponsor/provider claims, misinformation, harassment, protected knowledge exposure, manipulative support appeals, political misuse, public warning overclaim, finance overclaim, procurement overclaim, and consent overclaim.
3.10.7 Suspension and archive. Chapters, ambassadors, champions, and self-mobilizing teams may be corrected, suspended, delisted, restricted, retired, or archived where they violate public-safe rules, support rules, data rules, safeguard rules, sponsor/provider rules, public authority boundaries, finance boundaries, procurement boundaries, consent boundaries, or platform integrity rules.
3.11 APIs, Widgets, Embedded Campaign Tools, and Multi-Channel Mobilization
3.11.1 Multi-channel mobilization principle. Nexus Campaigns shall be capable of mobilizing across the web platform, mobile interfaces, email, SMS or messaging channels where lawful, social media, webinars, local events, university chapters, community rooms, public authority learning rooms, Nexus Universe arenas, partner websites, QR codes, campaign kits, public-safe media packs, APIs, and embeddable widgets. Multi-channel mobilization shall remain synchronized with the Campaign Record Card and platform records.
3.11.2 Embedded signature widgets. The platform may provide embedded signature widgets that allow partner sites, universities, campaign teams, and public-good partners to collect signatures within scoped campaign language. Embedded signatures shall remain subject to signature terms, privacy rules, duplicate detection, bot controls, public-safe language, and no-mandate boundaries.
3.11.3 Embedded support widgets. The platform may provide embedded support widgets for donations, sponsorship, in-kind pledges, compute support, equipment support, venue support, scholarship support, challenge funding, or bounty support where lawful. Embedded support shall remain subject to payment controls, support terms, fiscal stewardship, support ledger rules, fraud prevention, and no-pay-to-influence rules.
3.11.4 Embedded volunteer widgets. The platform may provide embedded volunteer widgets for role sign-up, training pathways, WILP pathways, micro-credential pathways, volunteer schedules, task boards, and campaign team onboarding. Embedded volunteer tools shall preserve role clarity, supervision, youth safeguards, data-access limits, public-safe rules, and labor boundaries.
3.11.5 Embedded progress widgets. The platform may provide public-safe progress widgets showing campaign status, outputs, support use, public-safe summaries, Nexus Universe readiness, corrections, and archive status. Progress widgets shall not display sensitive data or imply rankings, approvals, financeability, procurement status, or certification.
3.11.6 Campaign APIs. Campaign APIs may support partner integrations, public-safe progress feeds, event calendars, signature counts, support ledger summaries, volunteer opportunities, public-safe reports, Marketplace discovery, Registry status, and Nexus Universe countdowns. API access shall be governed by data minimization, privacy controls, security review, rate limits, access controls, consent rules, and public-safe restrictions.
3.11.7 Data export. Data export shall be controlled by role, purpose, data rights, privacy, data-use labels, AI-use labels, public-safe status, safeguard status, and legal restrictions. Export shall not create ownership, AI-training rights, commercialization rights, publication rights, or handoff rights by implication.
3.11.8 Multi-channel correction. Corrections shall propagate across relevant widgets, APIs, embedded pages, public dashboards, partner pages, social cards, public-safe reports, Marketplace records, Registry records, Studio records, and Nexus Universe materials where public meaning or downstream use may be affected.
3.11.9 Multi-channel boundary. Multi-channel distribution shall extend campaign reach without extending campaign authority. Embedded widgets, APIs, and partner pages shall not create endorsement, approval, procurement, finance, insurance, certification, consent, deployment, or execution by implication.
3.12 AI Campaign Copilot with Human Review and Boundary Controls
3.12.1 AI Campaign Copilot defined. The platform may include an AI Campaign Copilot to assist campaign creators, stewards, volunteers, public-safe communicators, data stewards, Working Groups, Competence Cells, and Nexus Universe teams with drafting, translation, summarization, classification, routing, volunteer matching, public-safe checks, overclaim detection, and report preparation.
3.12.2 Permitted AI assistance. The AI Campaign Copilot may assist with campaign page drafts, public-safe language suggestions, no-conversion checks, translation drafts, accessibility suggestions, evidence summaries, volunteer role matching, task suggestions, Foundry conversion prompts, DICE metadata suggestions, GRIx mapping support, DRI indicator suggestions, public-safe social media drafts, support update drafts, incident triage prompts, and correction draft support.
3.12.3 AI no-approval rule. The AI Campaign Copilot shall not approve campaigns, publish public materials without human review where material, issue public warnings, make official classifications, approve public authority language, approve finance or insurance claims, validate providers, certify outputs, authorize procurement, allocate support, approve donations, accept legal terms on behalf of users, approve data publication, approve AI training rights, approve Nexus Universe routing, assign Grid or TRL status, create Risk Agency standing, or authorize handoff.
3.12.4 AI-use labels. Campaign materials created, assisted, classified, translated, summarized, or routed with AI support shall be labeled where material. AI-use labels shall identify whether AI was used for drafting, summarization, translation, classification, matching, analytics, fraud detection, public-safe checking, or other support.
3.12.5 AI public-safe checker. The AI Campaign Copilot may include a public-safe checker that flags public authority overclaim, finance overclaim, insurance overclaim, procurement overclaim, certification overclaim, endorsement overclaim, consent overclaim, emergency language, panic language, unsupported certainty, sponsor overclaim, provider validation, protected knowledge exposure, and execution overclaim.
3.12.6 AI data sensitivity checker. The AI Campaign Copilot may flag potential personal data, youth data, health-sensitive data, public authority data, infrastructure-sensitive data, cyber-sensitive data, geospatial-sensitive data, community-sensitive data, protected knowledge, Indigenous protocol-sensitive content where applicable, and confidential sponsor or provider information.
3.12.7 AI anti-fraud and trust support. AI may support bot detection, duplicate signature detection, suspicious support patterns, impersonation detection, fraudulent campaign signals, misinformation detection, harassment detection, and platform abuse triage. Such tools shall be subject to human review where material consequences exist.
3.12.8 AI contributor matching. AI may suggest volunteer, expert, Working Group, Competence Cell, Risk Academy, WILP, micro-credential, Foundry task, or Nexus Universe pathways based on user-provided skills and interests. Matching shall not create employment, certification, expert standing, procurement qualification, or public authority role.
3.12.9 AI limitations. AI outputs shall be reviewed for hallucination, bias, fabricated evidence, invented citations, missing context, translation error, legal-boundary error, cultural error, protected knowledge exposure, public authority overclaim, finance overclaim, procurement overclaim, consent overclaim, and public-safe risk.
3.12.10 AI boundary. AI Campaign Copilot support shall be assistance only. Human stewards, reviewers, maintainers, public-safe communicators, data stewards, safeguard stewards, and competent actors remain responsible for review, approval within internal process limits, publication, correction, and archive.
3.13 Campaign Knowledge Base and Public Resource Library
3.13.1 Campaign Knowledge Base defined. The Campaign Knowledge Base shall be the public-safe and controlled resource library for campaign templates, public-safe explainers, training guides, campaign playbooks, support guides, volunteer guides, public authority learning notes, DRR materials, DRF readiness materials, DRI materials, DICE guides, GRIx guides, Nexus Foundry guides, Nexus Universe guides, community safeguard guides, media kits, correction guides, and no-conversion notices.
3.13.2 Knowledge Base purposes. The Campaign Knowledge Base shall help campaign teams understand how to create campaigns, mobilize safely, collect signatures, raise support lawfully, manage volunteers, protect data, use AI safely, communicate publicly, prepare Nexus Universe outputs, avoid endorsement overclaim, preserve national ownership, and correct mistakes.
3.13.3 Resource classes. Knowledge Base resources may include public resources, steward resources, volunteer resources, Working Group resources, Competence Cell resources, public authority learning resources, readiness room resources, support steward resources, sponsor and provider resources, media resources, community safeguard resources, youth resources, data steward resources, AI-use resources, and Nexus Universe resources.
3.13.4 Versioning and correction. Knowledge Base resources shall be versioned, corrected, retired, and archived. Superseded resources shall not be used as current guidance unless expressly reinstated.
3.13.5 Knowledge Base boundary. Knowledge Base resources shall not constitute legal advice, financial advice, insurance advice, procurement advice, public authority guidance, certification criteria, consent procedures, deployment instructions, or execution commands unless separately and lawfully recorded by competent actors within proper authority.
3.14 Campaign Platform Governance Records
3.14.1 Platform records. The Nexus Campaign Digital Platform shall generate and preserve governance records for campaign creation, public page publication, action center configuration, support enablement, volunteer onboarding, team formation, room creation, widget issuance, API access, AI Copilot use, public-safe review, support ledger updates, incidents, corrections, withdrawals, renewals, and archives.
3.14.2 Platform auditability. The platform shall be auditable by record. Material changes to campaign pages, signature language, support terms, sponsor display, provider display, public authority language, community language, data status, AI-use status, public-safe status, Nexus Universe status, Marketplace status, Registry status, Studio status, Grid / TRL status, and handoff status shall be versioned or logged where appropriate.
3.14.3 Platform access records. Access to controlled campaign spaces, data rooms, secure rooms, readiness rooms, public authority learning rooms, Studio workflows, support ledgers, sensitive dashboards, and handoff records shall be recorded according to role, purpose, time, data classification, and security requirements where appropriate.
3.14.4 Platform incident records. Platform incidents shall be recorded and classified, including campaign impersonation, fraudulent support appeal, payment issue, bot signature activity, public authority overclaim, sponsor overclaim, provider validation overclaim, data leak, AI misuse, cyber issue, protected knowledge exposure, harassment, misinformation, youth safety issue, support misuse, widget misuse, API misuse, and public page misrepresentation.
3.14.5 Platform archive. Platform archive shall preserve campaign history, support history, public-safe releases, corrections, withdrawals, non-continuation, deactivated widgets, retired APIs, closed rooms, closed team pages, and campaign records without implying current validity or authority.
3.15 Final Section 3 Statement
3.15.1 Final platform formula. The Nexus Campaign Digital Platform shall make public-good mobilization concrete. It shall give every campaign a creation pathway, public page, action center, dashboard, Campaign Record Card, Trust Layer, rooms, team pages, chapters, ambassadors, widgets, APIs, AI assistance, Knowledge Base, support records, correction channels, and archive. It shall allow people and institutions to sign, pledge, support, volunteer, learn, build, contribute data, submit evidence, join teams, form Working Groups, activate Competence Cells, prepare Nexus Universe outputs, and route lawful handoff dependencies without collapsing public participation into false authority.
3.15.2 Final declaration. The platform shall be powerful enough to mobilize countries, regions, communities, youth, universities, labs, sponsors, providers, donors, insurers, public authorities in learning roles, capital readers, experts, and volunteers at scale, while disciplined enough to prevent fraud, overclaim, unsafe publication, data misuse, AI misuse, sponsor capture, provider validation, public authority substitution, finance overclaim, procurement drift, consent overclaim, and execution by implication. Its purpose is not to make campaigns louder; its purpose is to make mobilization trustworthy, cumulative, public-safe, evidence-bearing, support-transparent, nationally grounded, Nexus Universe-ready, and lawfully routed.
4. Signatures, Petitions, Pledges, Support-Raising, Crowdfunding, Civic Capital Readiness, and Support Ledgers
4.1 Signature Campaigns
4.1.1 Signature Campaign defined. A Signature Campaign is a Nexus Campaign action pathway through which individuals, teams, institutions, communities, universities, public-interest actors, youth groups, diaspora groups, laboratories, companies, sponsors, providers, public authorities in learning roles where appropriate, donors, insurers, capital readers, and other stakeholders may record support for a specific public-good statement, campaign purpose, learning call, resilience mobilization call, Working Group formation call, Nexus Universe preparation call, data commons call, public-good build call, public-safe reporting call, or lawful handoff readiness call within a clearly bounded scope.
4.1.2 Signature purpose. Signatures shall help demonstrate public-good interest, stakeholder attention, community concern, volunteer momentum, national or thematic relevance, support for learning, support for resilience dialogue, support for Working Group formation, support for public-safe reporting, support for Nexus Foundry build conversion, or support for Nexus Universe preparation. Signatures shall make participation visible; they shall not create legal mandate, public authority mandate, public consultation result, sovereign position, institutional endorsement, or binding commitment.
4.1.3 Signature statement. Each Signature Campaign shall include a plain, public-safe, bounded Signature Statement identifying exactly what the signatory supports. The Signature Statement shall avoid vague endorsement language, government approval language, public warning language, procurement language, finance language, insurance language, certification language, consent language, emergency command language, deployment language, or execution language unless separately and lawfully recorded by a competent actor.
4.1.4 Signature identity options. Signature Campaigns may allow signatures by individuals, organizations, teams, institutions, or controlled participant classes. The campaign shall identify whether signatures are public, private, anonymized, aggregated, verified, unverified, organization-submitted, or steward-reviewed. Public display of personal or institutional signatures shall require appropriate permission and public-safe handling.
4.1.5 Signature verification. The platform may use verification, duplicate detection, bot detection, email confirmation, account controls, institutional domain checks, organization verification, CAPTCHA or equivalent controls, and moderation to reduce fraud, impersonation, manipulation, duplicate signing, or artificial inflation. Verification status shall not create legal authority or endorsement by the verified actor beyond the recorded signature.
4.1.6 Signature counts. Signature counts may be displayed on campaign pages, dashboards, widgets, public-safe reports, and Campaign Record Cards where appropriate. Counts shall be interpreted as recorded support for the scoped Signature Statement only. They shall not be represented as a vote, referendum, public consultation, survey, demographic finding, government mandate, community consent, Indigenous consent where applicable, institutional endorsement, policy adoption, procurement support, funding approval, financeability, public authority approval, or project authorization.
4.1.7 Institutional signatures. Where an institution signs a campaign statement, the campaign shall identify the signing entity, signer role where appropriate, authorization level if provided, signature scope, public display permission, and any restrictions. Institutional signature shall not imply official governmental endorsement, procurement support, finance commitment, institutional partnership, public authority action, or implementation commitment unless separately and expressly recorded.
4.1.8 Public authority signatures. Public authorities, missions, ministries, public institutions, officials, and delegates shall not be asked by default to “endorse” a campaign through signatures. Where such actors participate, the preferred status shall be observer, technical dialogue participant, public authority learning participant, national stakeholder routing participant, or public-safe knowledge exchange participant. Any public signature or public listing shall require specific reviewed language.
4.1.9 Signature withdrawal and correction. Signatories shall have appropriate pathways to correct, withdraw, or update signatures where lawful and operationally feasible. Campaigns shall correct signature counts, public listings, institutional displays, and signature descriptions where errors, impersonation, unauthorized representation, duplicate signatures, or public-safe issues are identified.
4.1.10 Signature boundary. A signature shall create only a record of support for the stated campaign language within the campaign’s recorded scope. It shall not create endorsement beyond the statement, approval, certification, procurement, finance, insurance, donor commitment, public finance allocation, public authority action, public warning, community consent, Indigenous consent where applicable, deployment authorization, employment, agency, partnership, or execution authority.
4.2 Petition and Public Statement Tools
4.2.1 Petition tools defined. Petition and Public Statement Tools are campaign platform functions that allow campaign stewards to collect public support for calls to learn, convene, mobilize, form a Working Group, support public-good research, address a public-good resilience need, build a data commons, prepare a DRI dashboard, launch a Nexus Foundry task, support Nexus Universe preparation, improve public-safe reporting, protect community knowledge, or invite public-good technical dialogue.
4.2.2 Petition language discipline. Nexus petitions shall be public-safe, evidence-bounded, non-defamatory, non-harassing, non-panicking, non-coercive, non-misleading, and non-executing. They shall avoid unsupported accusations, public shaming, manipulative urgency, disaster exploitation, false government claims, false institutional claims, false support claims, finance overclaims, procurement overclaims, consent overclaims, and public authority overclaims.
4.2.3 Preferred petition forms. Preferred Nexus petition forms include:
4.2.3.1 call for public-good learning;
4.2.3.2 call for national resilience dialogue;
4.2.3.3 call for Working Group formation;
4.2.3.4 call for technical exchange;
4.2.3.5 call for public-safe DRR readiness;
4.2.3.6 call for DRF readiness question formation;
4.2.3.7 call for DRI dashboard learning;
4.2.3.8 call for data commons contribution;
4.2.3.9 call for public-good build support;
4.2.3.10 call for accessibility and translation support;
4.2.3.11 call for youth and volunteer mobilization;
4.2.3.12 call for Nexus Universe preparation;
4.2.3.13 call for lawful handoff dependency mapping.
4.2.4 Restricted petition forms. Petitions shall not be framed as demands for government action, emergency orders, procurement action, funding allocation, official warning, regulatory approval, public finance commitment, insurance approval, project authorization, community consent, Indigenous consent where applicable, or implementation unless reviewed under applicable public authority, legal, advocacy, lobbying, charitable, political activity, and public-safe controls.
4.2.5 Addressees. A petition or public statement may be addressed to the public, national stakeholders, campaign supporters, universities, civil society, technical communities, public authorities in learning roles, development actors, donors, insurers, public finance readers, Nexus Universe participants, or internal Nexus pathways. Where a public authority, mission, ministry, or global institution is named, the language shall be reviewed to prevent endorsement, pressure, misrepresentation, or public authority overclaim.
4.2.6 Delivery and publication. Petition results may be delivered, published, summarized, or included in campaign records only within public-safe limits. Delivery to a public authority, public institution, donor, insurer, capital reader, global forum actor, or development actor shall be framed as a public-good input, learning signal, or stakeholder interest record, not as a mandate or approval.
4.2.7 Petition updates. Petition campaigns shall provide updates when the statement changes, public-safe wording is corrected, addressees change, signature counts change, support pathways change, or the campaign is paused, withdrawn, archived, or routed to Nexus Universe.
4.2.8 Petition boundary. Nexus petition tools shall mobilize public-good attention and structured participation. They shall not create legal obligation, governmental duty, public consultation result, public authority action, official policy adoption, procurement duty, funding duty, finance commitment, insurance commitment, consent, deployment authorization, or execution.
4.3 Public Pledge Tools
4.3.1 Public Pledge Tools defined. Public Pledge Tools are campaign platform functions through which individuals, teams, institutions, companies, universities, labs, public-interest actors, sponsors, providers, donors, media actors, public authorities in learning roles, and other stakeholders may express willingness to contribute time, expertise, resources, data, infrastructure, venues, compute, funding support where lawful, public-safe communication, training, mentoring, review, maintenance, or other public-good support.
4.3.2 Pledge classes. Campaign pledges may include:
4.3.2.1 volunteer time pledges;
4.3.2.2 expert review pledges;
4.3.2.3 mentorship pledges;
4.3.2.4 training pledges;
4.3.2.5 translation pledges;
4.3.2.6 accessibility support pledges;
4.3.2.7 data contribution pledges subject to rights review;
4.3.2.8 compute, cloud, GPU, HPC, or Edge support pledges;
4.3.2.9 equipment pledges;
4.3.2.10 venue or hosting pledges;
4.3.2.11 public-safe communications pledges;
4.3.2.12 scholarship or travel support pledges;
4.3.2.13 bounty or challenge support pledges;
4.3.2.14 sponsorship pledges;
4.3.2.15 philanthropic support pledges;
4.3.2.16 donor or grant interest pledges;
4.3.2.17 provider contribution pledges;
4.3.2.18 public authority learning participation pledges;
4.3.2.19 Nexus Universe participation pledges;
4.3.2.20 lawful handoff interest pledges.
4.3.3 Pledge records. Each material pledge shall generate a Pledge Record identifying pledgor, pledgor class, pledge type, value or non-monetary scope where appropriate, restrictions, conditions, acceptance status, public display permission, conflicts, data implications, public-safe status, sponsor/provider status where applicable, expiration, correction pathway, withdrawal pathway, and archive rule.
4.3.4 Pledge acceptance. A pledge shall not be treated as accepted merely because it is submitted. Acceptance may require steward review, legal review, support terms, data terms, sponsor terms, provider terms, fiscal review, conflict review, safeguard review, public authority boundary review, finance boundary review, procurement boundary review, security review, or public-safe review depending on pledge type.
4.3.5 Pledge display. Pledges may be displayed publicly or privately according to permission, public-safe status, support rules, and confidentiality. Public display of pledges shall avoid implying endorsement, funding commitment, procurement preference, public authority approval, financeability, insurance approval, or execution commitment.
4.3.6 Conditional pledges. Conditional pledges shall identify conditions clearly, including campaign milestone, support threshold, legal review, data review, public authority pathway, Matching support, fiscal host approval, recipient eligibility, or Nexus Universe routing. Conditions shall not be hidden or used to mislead supporters.
4.3.7 Pledge withdrawal and expiry. Pledges may expire, be withdrawn, be corrected, be rejected, be accepted, be fulfilled, be partially fulfilled, be redirected, or be archived according to pledge terms. Expired or withdrawn pledges shall not be counted as active support.
4.3.8 Pledge boundary. A pledge is not a donation, contract, grant, procurement commitment, finance commitment, insurance commitment, public authority commitment, endorsement, partnership, or implementation obligation unless separately accepted and governed by a lawful instrument.
4.4 Institutional Letters of Interest and Participation Records
4.4.1 Institutional Letter of Interest defined. An Institutional Letter of Interest is a scoped, non-binding record through which an institution may express interest in learning, observing, participating, contributing, supporting, hosting, providing technical dialogue, nominating stakeholders, providing data subject to review, joining a room, supporting a Working Group, supporting a Competence Cell, supporting Nexus Universe preparation, or exploring lawful continuation.
4.4.2 Purpose. Institutional Letters of Interest shall provide a safer alternative to endorsement letters. They shall allow institutions, public authorities in learning roles, missions, ministries, universities, labs, companies, donors, insurers, development actors, public finance readers, cities, regions, community organizations, youth organizations, and public-interest actors to signal interest without creating approval, adoption, funding commitment, procurement status, financeability, or execution.
4.4.3 Required contents. A Letter of Interest should identify:
4.4.3.1 institution name;
4.4.3.2 representative submitting the letter;
4.4.3.3 role or authorization level if stated;
4.4.3.4 campaign of interest;
4.4.3.5 interest type;
4.4.3.6 permitted public display, if any;
4.4.3.7 restrictions;
4.4.3.8 no-endorsement statement;
4.4.3.9 no-commitment statement;
4.4.3.10 contact pathway;
4.4.3.11 review or renewal date;
4.4.3.12 withdrawal pathway.
4.4.4 Participation Record. Where a campaign needs a lighter instrument than a Letter of Interest, it may use a Participation Record identifying that an actor participated as observer, learner, technical dialogue participant, volunteer, supporter, contributor, sponsor, provider, public authority learning participant, readiness room participant, or Nexus Universe pathway participant.
4.4.5 Public authority participation. For public authorities and international-facing actors, the Participation Record shall avoid endorsement language and shall identify the non-binding, non-decision, non-exclusive, public-good, technical dialogue, public authority learning, or observer nature of participation.
4.4.6 Public listing. Letters of Interest and Participation Records shall not be publicly displayed unless the specific display wording is approved. “Interested,” “observing,” “participating in technical dialogue,” “joining a learning pathway,” or “supporting public-good discussion” shall be preferred over “endorsing,” “backing,” “approving,” “adopting,” or “partnering,” unless the latter terms are separately authorized and accurate.
4.4.7 Boundary. Institutional Letters of Interest and Participation Records shall not create endorsement, partnership, agency, procurement status, finance commitment, insurance commitment, public finance allocation, public authority approval, policy adoption, legal reliance, community consent, Indigenous consent where applicable, implementation commitment, or execution authority.
4.5 Public-Good Support Campaigns
4.5.1 Public-Good Support Campaign defined. A Public-Good Support Campaign is a campaign or campaign module through which support may be raised, pledged, received, recorded, stewarded, reported, corrected, reallocated, refunded where applicable, or archived for a defined public-good campaign purpose.
4.5.2 Supportable purposes. Public-Good Support Campaigns may support:
4.5.2.1 public-good research;
4.5.2.2 National Working Group support;
4.5.2.3 Competence Cell support;
4.5.2.4 volunteer mobilization;
4.5.2.5 Risk Academy learning;
4.5.2.6 WILPs and micro-credentials;
4.5.2.7 student and youth participation;
4.5.2.8 translation and accessibility;
4.5.2.9 community safeguards;
4.5.2.10 public-safe reporting;
4.5.2.11 DICE commons;
4.5.2.12 DRI dashboards;
4.5.2.13 GRIx mappings;
4.5.2.14 Nexus Foundry tasks, quests, bounties, and builds;
4.5.2.15 public-good software;
4.5.2.16 datasets and metadata;
4.5.2.17 secure-room or data-room costs;
4.5.2.18 field learning where lawful and safe;
4.5.2.19 Nexus Universe preparation;
4.5.2.20 Core Build preparation;
4.5.2.21 public-safe media and knowledge-base work;
4.5.2.22 correction, archive, and public repair.
4.5.3 Support page. A campaign support page shall identify campaign purpose, support categories, fiscal steward, payment processor where applicable, restricted or unrestricted support status, use-of-support categories, reporting frequency, refund or reallocation rules where applicable, non-continuation rule, conflicts, sponsor/provider rules, public-safe display rules, and no-conversion notices.
4.5.4 Support acceptance. Campaign support shall not be accepted where it would create unlawful fundraising, improper charitable solicitation, sanctions risk, AML risk where applicable, bribery risk, conflict risk, sponsor capture, provider capture, public authority distortion, community harm, protected knowledge risk, procurement distortion, finance overclaim, insurance overclaim, political misuse, or reputational misuse.
4.5.5 Restricted support. Restricted support shall be accepted only where the restriction is lawful, public-good aligned, operationally feasible, transparent to the appropriate audience, not controlling, not overclaiming, not inconsistent with campaign safeguards, and not inconsistent with Nexus no-conversion discipline.
4.5.6 Support target. Support targets may be displayed where public-safe and lawful. Targets shall be framed as support goals, not investment targets, revenue projections, public finance allocations, grant commitments, or guarantees that outputs will be completed.
4.5.7 Use-of-support reporting. Campaigns receiving support shall provide appropriate use-of-support updates. Reporting may include support received, support used, support category, outputs supported, remaining balance where applicable, in-kind support received, restricted support, unresolved issues, corrections, reallocation, refund, and archive.
4.5.8 Support boundary. Public-good support shall not purchase influence, validation, endorsement, Nexus Universe routing, Marketplace status, Registry status, Studio authorization, Grid input, TRL status, Risk Agency standing, public authority learning output, readiness output, handoff eligibility, procurement status, financeability, insurance approval, consent, deployment, or execution.
4.6 Donations, Sponsorship, Grants, In-Kind Support, and Compute / Equipment Support
4.6.1 Donations. Donations may be accepted where lawful, properly stewarded, and governed by donation terms, payment controls, tax or receipt rules where applicable, refund or reallocation rules where applicable, support ledger rules, and public-safe display rules. Donation acceptance shall not create donor control, donor commitment beyond the donation, public finance status, procurement status, financeability, or endorsement.
4.6.2 Sponsorship. Sponsorship may support campaigns, rooms, training, translation, accessibility, public-safe reporting, Nexus Universe participation, public-good builds, scholarships, bounties, events, or technical infrastructure where lawful. Sponsorship shall be governed by sponsor terms, public-safe display rules, conflict controls, no-control rules, no-validation rules, no-pay-to-influence rules, and correction obligations.
4.6.3 Grants and philanthropic support. Grants and philanthropic support may support public-good campaign purposes subject to grant terms, funder restrictions, public-safe display rules, reporting obligations, conflicts, public-good alignment, correction rights, and archive. Grant support shall not convert funder priorities into national priorities without national routing.
4.6.4 In-kind support. In-kind support may include venues, translation, accessibility services, data services, communications support, technical support, training, staff time, expert time, legal or administrative support where lawful, equipment, cloud resources, compute, travel support, accommodation, or media support. In-kind support shall be valued or described where appropriate and shall be recorded in the Support Ledger.
4.6.5 Compute and cloud support. Compute credits, cloud credits, GPU access, HPC access, Edge resources, storage, networking, secure-room infrastructure, AI tools, analytics tools, and other technical resources may be contributed subject to data residency, cybersecurity, privacy, export control, sanctions, provider-neutrality, support obligations, cost limits, usage restrictions, teardown rules, and archive.
4.6.6 Equipment support. Equipment support may include sensors, drones, robotics, networking equipment, telecom equipment, field devices, laptops, cameras, lab equipment, servers, or other tools. Equipment support shall identify ownership, custody, use restrictions, safety rules, insurance or liability considerations where relevant, export-control or sanctions considerations where relevant, field-use rules, maintenance, return, donation, disposal, and archive.
4.6.7 Travel and scholarship support. Travel, accommodation, scholarships, fellowships, participation support, accessibility support, childcare support where lawful, and student support may be offered under clear eligibility rules, conflicts controls, public-safe display rules, tax or benefit considerations where applicable, and no-control rules.
4.6.8 Provider support. Provider support shall be treated as contribution without validation. Providers may contribute tools, software, cloud, compute, data, equipment, mentorship, training, APIs, dashboards, or technical support, but shall not control campaign outputs or claim product validation, preferred-vendor status, procurement advantage, financeability, public authority approval, certification, or deployment authorization.
4.6.9 Sponsor and provider correction. Campaigns shall correct sponsor or provider overclaims, including claims of endorsement, validation, preferred status, Nexus approval, public authority approval, procurement advantage, financeability, insurance approval, or deployment readiness.
4.7 Fiscal Stewardship and Payment Controls
4.7.1 Fiscal stewardship defined. Fiscal Stewardship is the governance of funds, donations, grants, sponsorships, payments, refunds, reallocations, expenditure records, support ledgers, restricted support, fiscal hosts, payment processors, and support reporting for campaigns.
4.7.2 Fiscal steward identification. Every campaign receiving funds shall identify the fiscal steward or recipient entity, payment processor, account pathway where appropriate, support terms, jurisdiction, tax or receipt status where applicable, reporting rules, conflict rules, and correction pathway.
4.7.3 Fiscal host model. Where a campaign is not directly administered by a Nexus legal entity or where national, regional, community, university, or partner stewardship is appropriate, funds may be received through a fiscal host, national entity, university, nonprofit, foundation, public-good partner, or other lawful recipient. The platform shall record who receives and administers support.
4.7.4 Nexus custody not presumed. Nexus shall not be presumed to hold, control, administer, guarantee, insure, refund, or allocate campaign funds unless a separate lawful instrument expressly establishes that role.
4.7.5 Payment processor controls. Payment processors shall be used according to applicable law, platform terms, donor terms, anti-fraud rules, sanctions screening where required, AML controls where required, consumer protection rules, tax rules, refund rules, and data protection rules.
4.7.6 Restricted use controls. Restricted funds shall be tracked by restriction, use category, permitted use, prohibited use, reporting requirement, unused balance, reallocation rule, refund rule where applicable, and archive.
4.7.7 Disbursement controls. Disbursement of campaign funds may require milestone confirmation, steward approval, fiscal host approval, documentation, eligibility verification, conflict review, support ledger update, or public-safe report depending on campaign terms.
4.7.8 Impact escrow logic. Campaigns may use milestone-based support logic under which support is pledged, held, released, reallocated, refunded, or archived according to campaign thresholds, milestones, legal conditions, support terms, fiscal host rules, or non-continuation rules. Such logic shall not create investment escrow, securities escrow, guarantee, return right, or regulated financial instrument unless separately and lawfully structured.
4.7.9 Fiscal transparency. Campaigns shall provide appropriate transparency on support received, support used, restricted support, in-kind support, fiscal steward, and corrections. Transparency shall not expose private donor data, sensitive sponsor information, public authority-sensitive information, community-sensitive information, or protected knowledge.
4.7.10 Fiscal boundary. Fiscal stewardship shall support trust and lawful support handling. It shall not create public finance allocation, investment product, deposit, stored value, security, revenue share, lender relationship, insurance product, guarantee, fiduciary status, or regulated financial activity unless separately and lawfully established.
4.8 Support Ledgers and Use-of-Support Reporting
4.8.1 Support Ledger defined. A Support Ledger is the campaign record that tracks material support received, pledged, accepted, rejected, restricted, used, reallocated, refunded where applicable, corrected, or archived.
4.8.2 Ledger contents. A Support Ledger may include:
4.8.2.1 support source class;
4.8.2.2 support source name where public or permitted;
4.8.2.3 support type;
4.8.2.4 amount or non-cash description where appropriate;
4.8.2.5 restricted or unrestricted status;
4.8.2.6 intended use;
4.8.2.7 accepted or pending status;
4.8.2.8 fiscal steward;
4.8.2.9 payment processor where applicable;
4.8.2.10 use category;
4.8.2.11 output supported;
4.8.2.12 conflict note;
4.8.2.13 public display permission;
4.8.2.14 reporting obligation;
4.8.2.15 refund or reallocation rule;
4.8.2.16 correction record;
4.8.2.17 archive status.
4.8.3 Public and controlled ledger layers. A Support Ledger may have public, contributor-only, steward-only, fiscal-host-only, controlled, confidential, or archive layers depending on privacy, sponsor terms, donor terms, payment rules, public-safe status, security, and law.
4.8.4 Use-of-support reports. Campaigns should provide use-of-support reports at appropriate intervals or milestones. Reports may identify funds or support received, in-kind support received, support used, outputs supported, volunteer support mobilized, training supported, accessibility supported, public-safe reporting supported, DICE or Foundry outputs supported, Nexus Universe participation supported, unused support, restricted support, corrections, and archive.
4.8.5 Public-good output linkage. Support reports should link support to public-good outputs where possible, including training delivered, datasets classified, public-safe summaries issued, Working Groups supported, Competence Cells activated, Foundry tasks created, builds completed, DRI dashboard candidates created, Nexus Universe outputs prepared, and corrections completed.
4.8.6 Support reporting discipline. Use-of-support reporting shall avoid inflated impact, unsupported causal claims, sponsor promotion, donor overclaim, finance language, investment language, public authority approval language, procurement language, certification language, or guaranteed outcome language.
4.8.7 Ledger correction. Support Ledgers shall be corrected where support source, amount, restriction, use, public display, output linkage, conflict, refund, reallocation, or archive status is wrong or misleading.
4.8.8 Ledger boundary. A Support Ledger records support stewardship. It shall not create audited financial statements, investment reporting, public finance reporting, official grant compliance, donor impact certification, tax advice, legal compliance assurance, or public authority approval unless separately and lawfully established.
4.9 Civic Capital Readiness Lane
4.9.1 Civic Capital Readiness Lane defined. The Civic Capital Readiness Lane is the Nexus Campaign pathway through which public-good campaign outputs, National Portfolio needs, DRF questions, resilience needs, public-good builds, data commons gaps, Nexus Universe outputs, and lawful handoff dependency records may be made more legible to capital readers, insurers, donors, development actors, public finance readers, philanthropy, National Consortium Companies, Project SPVs, and lawful downstream actors without creating a financial product, investment offer, insurance product, donor commitment, public finance allocation, or transaction.
4.9.2 Purpose. The Civic Capital Readiness Lane shall help campaign teams translate public-good needs into assumptions, dependencies, risk questions, evidence gaps, data needs, safeguard conditions, public authority dependencies, legal dependencies, finance-readiness questions, insurance-readiness questions, donor-readiness questions, public finance relevance questions, support needs, and lawful handoff conditions.
4.9.3 Readiness not finance. Civic capital readiness shall not be represented as financeability, bankability, investment readiness, valuation, investor interest, lender approval, donor approval, grant eligibility, public finance eligibility, guarantee approval, rating, solicitation, offer, or transaction readiness.
4.9.4 Insurance-readiness not insurance approval. Insurance-readiness outputs shall not be represented as insurability, underwriting acceptance, coverage decision, premium indication, actuarial conclusion, reinsurance approval, guarantee status, or risk-transfer transaction readiness.
4.9.5 Donor-readiness not donor commitment. Donor-readiness outputs shall not be represented as donor commitment, grant approval, philanthropic approval, charitable allocation, program approval, or funding decision.
4.9.6 Public finance relevance not public finance allocation. Public finance relevance outputs shall not be represented as public finance allocation, budget approval, subsidy approval, guarantee approval, fiscal commitment, sovereign approval, public procurement status, or development finance commitment.
4.9.7 Readiness records. Civic Capital Readiness may produce Finance-Readiness Notes, Insurance-Readiness Question Maps, Donor-Readiness Notes, Public Finance Relevance Notes, DRF Readiness Notes, Assumptions Registers, Dependency Registers, Diligence-Gap Registers, Evidence Sufficiency Notes, Safeguard Readiness Notes, Public Authority Dependency Notes, Legal Dependency Notes, Provider-Neutrality Notes, Sponsor Influence Notes, Handoff Support Notes, and No-Reliance Statements.
4.9.8 Readiness display. Readiness information may be displayed in public-safe, controlled, or room-specific formats. Public display shall avoid implying investor interest, donor commitment, public finance approval, insurance approval, procurement status, or implementation readiness.
4.9.9 Civic capital boundary. The Civic Capital Readiness Lane shall not conduct securities crowdfunding, investment crowdfunding, lending, deposit-taking, brokerage, insurance intermediation, underwriting, advisory, public finance allocation, valuation, rating, or transaction execution unless separately and lawfully established through competent channels.
4.10 Capital-Reader, Insurance-Reader, Donor-Reader, and Public Finance Learning Rooms
4.10.1 Reader rooms defined. Reader Rooms are controlled campaign rooms through which capital readers, insurers, reinsurers, donors, development actors, public finance readers, philanthropic actors, National Consortium Companies, Project SPVs, public authorities in learning roles, and other lawful stakeholders may review campaign outputs for learning, question formation, dependency mapping, and independent diligence preparation.
4.10.2 Capital-Reader Rooms. Capital-Reader Rooms may review campaign outputs, National Portfolio records, Foundry builds, DICE objects, GRIx records, DRI records, iVRS records, Studio workflows, assumptions registers, dependency registers, and diligence-gap registers for capital-readability questions. They shall be no-reliance, non-soliciting, non-transactional, confidentiality-aware, competition-compliant, and regulated-perimeter controlled.
4.10.3 Insurance-Reader Rooms. Insurance-Reader Rooms may review risk intelligence, exposure methods, vulnerability information, resilience indicators, scenarios, DRI records, GRIx mappings, uncertainty statements, data gaps, safeguard records, and DRF questions for insurance-readiness learning. They shall not be underwriting rooms, broker rooms, premium indication rooms, coverage decision rooms, or transaction rooms.
4.10.4 Donor-Reader Rooms. Donor-Reader Rooms may review public-good evidence, community safeguard records, capacity needs, learning pathways, public-safe summaries, National Portfolio context, Nexus Universe outputs, and implementation dependencies for donor-readiness questions. They shall not allocate grants, approve programs, create donor commitments, rank recipients, or guarantee future support.
4.10.5 Public Finance Learning Rooms. Public Finance Learning Rooms may support learning by public finance actors, development finance actors, public authorities, and public-good participants regarding public-good rationale, evidence, risks, safeguards, dependencies, readiness questions, national context, and legal boundaries. They shall not allocate public funds, approve guarantees, create procurement status, or make fiscal decisions.
4.10.6 Room records. Reader Rooms shall generate Room Records identifying participants, materials, permitted use, prohibited use, confidentiality, no-reliance status, questions generated, dependencies identified, conflicts, correction pathway, and archive.
4.10.7 Competition and confidentiality. Reader Rooms shall prevent improper information exchange, market allocation, collusion, bid manipulation, price coordination, underwriting coordination, investor coordination, procurement distortion, or misuse of confidential information.
4.10.8 Reader room boundary. Attendance or participation in a Reader Room shall not imply investment interest, lender interest, underwriting interest, donor interest, public finance interest, approval, commitment, solicitation, offer, transaction readiness, procurement status, project approval, or public authority action.
4.11 Regulated-Perimeter Controls
4.11.1 Regulated-perimeter principle. Nexus Campaigns shall maintain strict regulated-perimeter controls where campaign support, crowdfunding-like tools, public pledges, civic capital readiness, DRF, insurance-readiness, donor-readiness, public finance relevance, investment-related language, project finance, enterprise handoff, charitable solicitation, payment processing, tax status, financial promotion, securities laws, insurance laws, banking laws, lending laws, public finance rules, procurement rules, lobbying rules, political activity rules, consumer protection rules, data protection rules, youth rules, sanctions, AML, anti-bribery, or cross-border rules may be implicated.
4.11.2 Financial instrument boundary. Campaign support tools, signatures, pledges, credits, rewards, badges, support ledgers, readiness notes, iVRS records, DRI records, GRIx records, Marketplace listings, Registry entries, Studio workflows, Grid inputs, TRL evidence notes, Nexus Universe outputs, and handoff packages shall not be structured or marketed as securities, investment contracts, derivatives, commodities, payment instruments, deposits, stored value, e-money, crypto-assets, fund interests, revenue shares, lending products, insurance products, guarantees, or tradable financial instruments unless separately and lawfully established.
4.11.3 Securities and investment crowdfunding boundary. Campaigns shall not offer equity, debt, revenue share, profit share, token return, appreciation, resale rights, investment return, financial return, or enterprise finance participation through the default public-good support layer. Any such activity must be routed outside the default Nexus Campaign layer through separately lawful, regulated, and competent channels.
4.11.4 Insurance boundary. Campaigns shall not solicit insurance, bind coverage, place insurance, broker insurance, underwrite, provide premium indications, provide actuarial conclusions, issue guarantees, or represent insurance approval through campaign pages, reader rooms, readiness notes, or handoff packages.
4.11.5 Charitable solicitation and donation boundary. Donations and public support shall comply with applicable charitable solicitation, nonprofit, tax, receipt, consumer protection, payment processing, and public fundraising rules where relevant. A campaign shall not imply tax deductibility, charitable status, or official charitable purpose unless accurate and recorded.
4.11.6 Anti-bribery and public integrity. Support involving public authorities, public institutions, officials, missions, public finance actors, or state-linked entities shall be reviewed for anti-bribery, public integrity, gift, hospitality, procurement, conflict, sanctions, and political activity issues where relevant.
4.11.7 Sanctions, AML, and fraud. Campaigns receiving funds, in-kind support, equipment, compute, or cross-border support may require sanctions screening, AML controls where applicable, payment fraud controls, identity verification, source-of-funds checks where relevant, and restricted party screening.
4.11.8 Lobbying and political activity. Campaigns with policy-facing, public authority-facing, election-adjacent, legislative, regulatory, or advocacy-like components shall be reviewed for lobbying, political activity, election neutrality, public charity restrictions where relevant, campaign finance rules where relevant, and public-safe language. Nexus Campaigns shall not be used for partisan campaigns or election influence.
4.11.9 Consumer protection and advertising. Public support pages shall avoid misleading claims about outcomes, urgency, matching support, official approval, tax status, support use, sponsor support, provider validation, public authority participation, impact, finance, insurance, procurement, or implementation.
4.11.10 Regulated-perimeter archive. Decisions, reviews, restrictions, rejections, corrections, and incidents relating to regulated-perimeter controls shall be recorded and archived.
4.12 Refund, Reallocation, Non-Continuation, and Support Archive
4.12.1 Refund and reallocation rules. Campaigns that receive funds or support shall define, where applicable, what happens if the campaign target is not met, the campaign does not proceed, the campaign is paused, the output is withdrawn, the campaign is archived, a legal issue arises, support is restricted, support cannot be used as intended, or a fiscal steward changes.
4.12.2 Refund policy. A campaign may provide refunds only where permitted, operationally feasible, and governed by payment processor rules, fiscal steward rules, support terms, donor terms, local law, and campaign conditions. Absence of refund rights shall be clearly disclosed where relevant.
4.12.3 Reallocation policy. Where support cannot be used as intended, it may be reallocated only according to support terms, donor restrictions, fiscal host rules, public-good purpose, legal requirements, public-safe communication, and Support Ledger updates.
4.12.4 Non-continuation. Non-continuation shall be a valid campaign outcome. A campaign may not continue because evidence is insufficient, support is inadequate, safeguards are unresolved, public-safe risk is too high, data rights are not available, national routing is not appropriate, public authority boundary risk is high, finance boundary risk is high, procurement boundary risk is high, sponsor or provider capture risk is high, or the campaign purpose is no longer appropriate.
4.12.5 Support treatment on non-continuation. Where a supported campaign becomes non-continuing, the campaign shall follow refund, reallocation, restriction, correction, and archive rules. Public updates shall clearly distinguish support received, support used, support remaining, reallocation, refund, and archive.
4.12.6 Withdrawal and suspension. Support collection may be suspended or disabled where fraud, overclaim, legal risk, public-safe risk, data risk, sponsor capture, provider capture, payment issue, sanctions issue, AML issue where applicable, public authority issue, community harm, or platform integrity issue arises.
4.12.7 Support archive. Support records shall be archived with final support status, use status, restriction status, refund or reallocation status, correction history, fiscal steward, and non-current-use labels where applicable.
4.12.8 Support archive boundary. Archived support records preserve memory and accountability. They shall not imply current support, current donor commitment, current sponsorship, current funding availability, current campaign validity, or current authority.
4.13 Fraud Prevention and Support Integrity
4.13.1 Fraud prevention principle. Nexus Campaigns shall maintain fraud prevention, support integrity, identity protection, anti-manipulation, and public trust controls to prevent fraudulent campaigns, fake support appeals, fake endorsements, impersonation, inflated signature counts, fake matching support, payment fraud, misuse of funds, sponsor overclaim, provider validation overclaim, public authority impersonation, and false impact claims.
4.13.2 Campaign steward verification. Campaigns receiving support or collecting signatures at scale may require steward verification, organizational verification, fiscal steward verification, payment recipient verification, public-safe review, and support terms before public launch.
4.13.3 Fake campaign controls. The platform may reject, suspend, delist, restrict, or archive campaigns that impersonate public authorities, communities, Indigenous groups where applicable, universities, companies, sponsors, providers, donors, Nexus bodies, public institutions, or public figures; that misstate purpose; that misrepresent support use; or that create unsafe public meaning.
4.13.4 Payment fraud controls. Campaign payment flows may include fraud screening, duplicate transaction detection, suspicious activity review, chargeback monitoring, sanctions screening, payment processor compliance, and support source verification where required.
4.13.5 Signature integrity controls. Signature systems may include duplicate detection, bot detection, identity confirmation, domain verification, suspicious pattern review, and public count correction.
4.13.6 Support use integrity. Campaigns shall maintain records demonstrating support use according to support terms. Misuse, unsupported use, undisclosed conflicts, misleading support reporting, or improper reallocation shall trigger correction or incident response.
4.13.7 Matching support claims. Matching support, challenge grants, conditional support, or milestone support shall not be displayed unless terms, source, limit, conditions, expiry, verification status, and use rules are recorded. False or misleading matching support claims shall be prohibited.
4.13.8 Impact integrity. Campaigns shall not claim impact merely from funds raised, signatures collected, media coverage, sponsor logos, volunteer registrations, or public authority attendance. Impact claims shall be evidence-bearing, bounded, public-safe, and correctionable.
4.13.9 Abuse reporting. Users shall be able to report suspected fraud, impersonation, misinformation, support misuse, harassment, bot activity, public authority overclaim, sponsor overclaim, provider overclaim, community consent overclaim, protected knowledge exposure, or unsafe public claims.
4.13.10 Fraud incident response. Fraud or support integrity incidents may result in support suspension, payment hold where lawful, public page restriction, public-safe notice, steward review, sponsor/provider review, refund or reallocation review, lawfully required reporting, campaign delisting, archive, and platform restrictions.
4.14 Public Support Without Populism
4.14.1 Anti-populism principle. Nexus Campaigns shall mobilize public support without rewarding outrage, harassment, misinformation, humiliation, panic, coercion, discrimination, disaster exploitation, performative activism, or unsupported claims. Public support shall be organized around public-good evidence, constructive participation, learning, resilience, safeguards, correction, and lawful routing.
4.14.2 Prohibited mobilization conduct. Campaigns shall not use or encourage hate, harassment, doxxing, discriminatory targeting, public shaming, unsupported accusations, panic language, disaster exploitation, false urgency, manipulative fundraising, fake endorsements, fake public authority claims, fake matching donations, misleading images, protected knowledge exposure, or harassment of public officials, communities, providers, sponsors, or individuals.
4.14.3 Respectful public pressure. Where a campaign addresses public authorities, institutions, providers, sponsors, or other actors, language shall remain public-safe, evidence-bounded, and constructive. Campaigns may call for dialogue, learning, transparency, resilience-building, Working Group formation, or public-safe review without creating unsafe pressure, legal overclaim, or reputational attack.
4.14.4 Community dignity. Campaigns involving affected communities, disaster-affected people, youth, vulnerable groups, humanitarian contexts, disability groups, diaspora groups, or Indigenous participants where applicable shall avoid exploitative imagery, trauma extraction, disaster pornography, tokenization, public embarrassment, or unsupported claims of representation.
4.14.5 Public support boundary. Public support shall strengthen public-good mobilization. It shall not be used to force public authority decisions, bypass consultation, pressure procurement, create finance signals, manufa