> For the complete documentation index, see [llms.txt](https://docs.therisk.global/organization/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.therisk.global/organization/cooperation/consortiums/model/i.-identity/1.7-membership-council-participation-and-role-based-subscription.md).

# 1.7 Membership, Council Participation, and Role-Based Subscription Logic

Identity: Membership, Council Participation, and Role-Based Subscription Logic. Nexus consortium model, read with the current model.

**Part of** [I. IDENTITY](https://docs.therisk.global/organization/cooperation/consortiums/model/i.-identity.md) · section 7 of 11 · previous: [1.6 Global Architecture, Regional Clustering, National Ownership, Project-Level Execution](https://docs.therisk.global/organization/cooperation/consortiums/model/i.-identity/1.6-global-architecture-regional-clustering-national-ownership-p.md) · next: [1.8 Consortium Membership Is Not Membership in GCRI, GRF, or GRA](https://docs.therisk.global/organization/cooperation/consortiums/model/i.-identity/1.8-consortium-membership-is-not-membership-in-gcri-grf-or-gra.md)

**Where this fits:** all six sectors ([The Model](https://docs.therisk.global/organization/model.md)) · [Nexus Universe](https://docs.therisk.global/organization/programme/universe.md), [Nexus Standards](https://docs.therisk.global/organization/programme/standards.md), [Nexus Reports](https://docs.therisk.global/organization/programme/reports.md), [Risk Academy](https://docs.therisk.global/organization/programme/academy.md) · the Nexus Consortium, stewarded by The Global Centre for Risk and Innovation (GCRI), The Global Risks Forum (GRF) and The Global Risks Alliance (GRA); global, regional, national and local layers ([Institutions](https://docs.therisk.global/organization/institutions.md)) · consortium doctrine.

**In brief.** Read against the international frameworks it serves ([UN General Assembly 2015](https://www.undrr.org/publication/sendai-framework-disaster-risk-reduction-2015-2030); [OECD 2014](https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405); [United Nations 2021](https://www.un.org/en/common-agenda)) and the [Nexus Standards](https://docs.therisk.global/organization/institutions/nexus-standards.md) that govern its records ([NS-0](https://nexustandards.com/standards/ns-0/), [NS-13](https://nexustandards.com/standards/ns-13/), [NS-10](https://nexustandards.com/standards/ns-10/)). "Nexus Consortiums are an organizing architecture, not one legal person or one membership club," and "no upper level can override a national council on a national question" (the Nexus Consortium model, as published on the GCRI and GRF sites).

{% hint style="info" %}
**Read with the current model (2026-10-21).**

* Everything this page describes is a design in formation. No national, regional or global consortium is recorded as constituted or active; the current service level is R0, information and enquiries ([Status and service levels](https://docs.therisk.global/organization/governance-in-operation/status-and-service-levels.md)). Where the text below reads as operation, read it as design.
* National Nexus is the country programme: a National Desk, a National Model, a National Portfolio and three participation pillars, the NNC (institutions, through five Helix pathways or the Financial Institutions and Regulators pathway), the NLC (leaders in a personal capacity) and the NWG (expert work, with the six CERTs). The [National Standards Council](https://docs.therisk.global/organization/governance-in-operation/national-standards-council.md) is the standards function of the NNC ([National Nexus](https://docs.therisk.global/organization/governance-in-operation/national-nexus.md)).
* The councils are the six Helix councils: SPC State and Public Authorities, IOC Industry and Operators, ARC Academia and Research, CMC Civil Society and Media, CIC Community and Indigenous, and FIR Financial Institutions and Regulators, a cross-cutting pathway led with GRA. Earlier "Helix Council" usage on this page maps to them ([Councils](https://docs.therisk.global/organization/governance-in-operation/councils.md)).
* "Competence Cells" is an earlier label. Their work is now National Working Group assignments and, by domain, the six CERTs, which are not emergency services, incident command or privileged access teams ([NWG](https://docs.therisk.global/organization/governance-in-operation/nwg.md)).
* Project vehicles and national companies are structures that competent, lawful actors may form outside the programme under their own law and licences. The programme never forms, arranges, owns or advises on them ([Lawful handoffs](https://docs.therisk.global/organization/finance-readiness/lawful-handoffs.md)).
* Ordinary participation has no fee; selection precedes payment, and a seat never buys office, a technical conclusion, public authority or procurement treatment. Paid work, internships and fellowships are separate arrangements ([NLC](https://docs.therisk.global/organization/governance-in-operation/nlc.md); [NWG](https://docs.therisk.global/organization/governance-in-operation/nwg.md)).
* Recognition, scoring and validation record what was shown under stated conditions. None is a certification, licence, rating or approval, and no country or institution is ranked.
* Systems are named by their NXS display codes (for example [NXS-RLS](https://docs.therisk.global/organization/systems/nxs-rls.md) for participants, agreements, protocols, obligations and lawful handoffs); see [Systems](https://docs.therisk.global/organization/systems.md).
  {% endhint %}

## 1.7.1 The Participation Economy

1.7.1.1 Definition of Participation Economy. The Nexus Consortium architecture operates through a structured participation economy: a disciplined system by which individuals, institutions, public authorities, companies, universities, research bodies, communities, Indigenous actors, civil society organizations, capital readers, providers, sponsors, technical experts, media actors, youth participants, hosts, operators, builders, and implementation actors enter Nexus through defined roles, recorded pathways, bounded access rights, and claims-disciplined participation surfaces. Participation is not treated as casual affiliation, social proximity, informal endorsement, conference attendance, or symbolic visibility. It is an institutional status that must be classified, recorded, governed, limited, renewed, and corrected where necessary. This is the only way a global-to-local architecture can remain open enough to mobilize broad participation while remaining disciplined enough to prevent status inflation, procurement confusion, public authority overclaim, finance overstatement, and institutional capture.

1.7.1.2 Participation as Institutional Infrastructure. In the Nexus model, participation itself becomes infrastructure. A participant is not merely “in the network”; the participant occupies a defined role within a larger operating system. That role determines what the participant may access, what it may contribute, what it may claim, what obligations it accepts, what records attach to its activity, what public visibility may be granted, what confidential information it may receive, what councils it may join, what rooms it may enter, what programs it may support, what corrections it must accept, and what boundaries it must respect. This converts participation from an unstructured relationship into a governance object.

1.7.1.3 Participation Pathways. Participation may occur through Global, Regional, or [National Nexus Consortium](https://docs.therisk.global/organization/governance-in-operation/nnc.md) membership; council subscription; institutional membership; enterprise membership; Helix Council participation; sponsorship; partnership; observer status; contributor status; public authority participation; capital-reader participation; investor council participation; provider participation; Nexus Universe participation; Nexus Acceleration participation; Nexus Standards participation; Nexus Observatory participation; NXS-RLS participation; [Risk Academy](https://docs.therisk.global/organization/institutions/risk-academy.md) participation; Competence Cell participation; AEP Passport contribution; committee service; working-group service; controlled-room access; technical contribution; public-safe reporting participation; National Model participation; Regional Cluster Program Plan participation; or program-specific participation defined by the relevant Consortium.

1.7.1.4 Differentiated Rights and Limits. Each participation pathway carries its own rights, limits, records, duties, access permissions, confidentiality obligations, claims permissions, publication status, conflict controls, renewal requirements, suspension conditions, and correction consequences. A participant’s status in one pathway shall not be presumed to confer status in another pathway unless the applicable Consortium instrument expressly provides such effect and the relevant record supports it. A global member is not automatically a national member. A council subscriber is not automatically a board member. A Nexus Universe participant is not automatically an approved provider. An AEP Passport contributor is not automatically project owner, investor, certifier, or public authority-approved actor.

1.7.1.5 No Informal Assumption of Participation. Participation shall not be assumed from informal engagement, meeting attendance, correspondence, event presence, advisory conversation, sponsorship discussion, technical contribution, public statement, social proximity, donor interest, professional reputation, public authority attendance, media coverage, or inclusion in a mailing list. Nexus participation exists only where a role, class, subscription, membership, invitation, contribution, authorization, appointment, or program status is recorded under the applicable Consortium rules. This prevents informal proximity from becoming false institutional authority.

1.7.1.6 Participation as Anti-Capture Design. The participation economy is also an anti-capture design. It ensures that no single category of participant—provider, sponsor, public authority, investor, university, technical actor, media actor, donor, or national institution—can convert participation into unchecked control. By assigning role-specific rights and limits, Nexus can welcome broad capability while preventing any participant from using visibility, funding, technical centrality, political access, or capital interest to dominate public-good records, national agenda, standards-interface outputs, public authority learning, or project handoff.

1.7.1.7 Foundation for Membership Logic. The membership logic of Nexus begins from this principle: participation is valuable because it is structured. The architecture invites broad participation while preserving institutional trust by ensuring that every participant enters through an identifiable pathway, receives only the rights attached to that pathway, accepts the corresponding obligations, remains subject to claims discipline, and may be corrected if its claims exceed the record. The goal is not to make participation narrow; the goal is to make participation reliable.

## 1.7.2 Consortium Membership

1.7.2.1 Membership in the Relevant Consortium Only. Consortium membership is membership in the relevant Global Nexus Consortium, Regional Nexus Consortium, or National Nexus Consortium only. Membership in one Nexus Consortium shall not automatically create membership in another Nexus Consortium, in a Regional Nexus Consortium, in a National Nexus Consortium, in a National Nexus Council, in a National Consortium Company, in a Project SPV, in any Nexus program, or in any founding institution unless a separate lawful instrument expressly creates that status and the applicable record supports it.

1.7.2.2 Membership as Structured Access. Consortium membership provides a structured entry point into the Nexus architecture. It may give a participant access to certain councils, directories, briefings, annual agenda processes, events, controlled publications, Nexus Universe pathways, Nexus Standards tracks, Nexus Acceleration opportunities, Nexus Observatory work, NXS-RLS workstreams, Risk Academy programs, working groups, committee eligibility, leadership pool eligibility, public-safe summaries, or other participation surfaces defined by the relevant Consortium. Membership is therefore meaningful, but its meaning is specific to the relevant level, class, and record.

1.7.2.3 Eligibility and Access Functions. Consortium membership may provide eligibility for councils, Helix Councils, leadership councils, investor councils, committees, working groups, controlled rooms, public-safe publications, member directories, Nexus Universe pathways, Nexus Acceleration processes, Nexus Standards tracks, Nexus Observatory pathways, NXS-RLS pathways, Risk Academy programs, nomination pools, annual agenda processes, AEP Passport pathways, public authority learning surfaces, capital-reader rooms, and other participation surfaces defined by the relevant Consortium. Eligibility, however, is not appointment; access is not authority; visibility is not endorsement.

1.7.2.4 Governance Rights Only Where Granted. Consortium membership does not create governance rights unless the relevant membership class expressly grants them. Voting rights, nomination rights, board eligibility, committee appointment eligibility, council access, document access, publication visibility, directory listing, speaking roles, controlled-room participation, leadership-pool eligibility, or review rights must arise from the applicable membership class, subscription tier, appointment, invitation, or governance record. Where no such right is recorded, no such right exists.

1.7.2.5 No Membership in GCRI, GRF, or GRA. Consortium membership does not create membership in [The Global Centre for Risk and Innovation](https://docs.therisk.global/organization/institutions/gcri.md) (GCRI), [The Global Risks Forum](https://docs.therisk.global/organization/institutions/grf.md) (GRF), or [The Global Risks Alliance](https://docs.therisk.global/organization/institutions/gra.md) (GRA). No member of a Nexus Consortium shall claim, imply, or permit the implication that Consortium membership makes it a member, shareholder, governor, director, fiduciary, institutional affiliate, agent, partner, officer, representative, or authorized spokesperson of GCRI, GRF, or GRA. The founding institutional arc supports the Consortium architecture; it does not transfer founding-institution membership to Consortium participants.

1.7.2.6 No Automatic Enterprise or Project Rights. Consortium membership does not create ownership, investment rights, revenue rights, contract rights, procurement rights, provider preference, SPV participation, National Consortium Company rights, public-private partnership status, concession rights, delivery rights, operator rights, or implementation rights. Those rights must arise from separate enterprise, corporate, procurement, contractual, public authority, finance, insurance, or project documents. Membership may place a participant inside a public-good architecture; it does not place the participant inside an enterprise vehicle.

1.7.2.7 Clarity and Repetition of Boundary. This rule shall be repeated wherever necessary in membership materials, onboarding records, directories, public profiles, event badges, sponsorship materials, council descriptions, Nexus Universe materials, Nexus Acceleration communications, Nexus Standards materials, AEP Passport language, National Model materials, Regional Cluster Program Plan summaries, and public-safe reports. Consortium membership is meaningful, but it is not founding-institution membership, project approval, procurement status, finance approval, certification, or public authority endorsement.

## 1.7.3 Council Subscription

1.7.3.1 Subscription Requirement. Joining councils requires subscription according to the applicable Consortium rules. Council subscription is the principal operational participation pathway through which members and eligible participants enter agenda discussions, contribute expertise, review materials, propose workstreams, support annual mandate formation, and become visible within the relevant council record. Subscription transforms interest into structured participation, but it does not transform the subscriber into a governing authority.

1.7.3.2 Council Subscription as Agenda Access. Council subscription gives access to the agenda-forming layer of the Consortium. It may allow a participant to attend council meetings, receive council materials, comment on agenda items, contribute technical or institutional input, propose workstreams, identify public authority learning needs, raise safeguard concerns, participate in consultation processes, join working groups, contribute to annual agenda notes, and become eligible for certain nomination pools. The purpose is structured contribution, not automatic control.

1.7.3.3 Council Subscription Access. Council subscription may provide access to council meetings, agenda discussions, council documents, controlled summaries, workstream proposals, working groups, consultation processes, nomination pools, leadership pipelines, annual agenda notes, participation records, and related materials designated by the relevant Consortium. Access may be public, controlled, restricted, or internal depending on subject matter, sensitivity, confidentiality, data status, public authority status, finance sensitivity, community safeguards, Indigenous protected knowledge, procurement relevance, and cybersecurity considerations.

1.7.3.4 No Automatic Board Rights. Council subscription does not automatically create board membership, voting rights, officer status, fiduciary status, committee authority, speaking authority, public representative status, procurement influence, finance rights, project rights, certification authority, public authority status, or implementation authority unless expressly provided by the applicable Consortium governance rules and recorded accordingly. A subscribed council participant may contribute to the agenda without controlling the institution.

1.7.3.5 Role-Based and Level-Specific. Council subscription is role-based and level-specific. A participant may subscribe to a global council without thereby joining a regional or national council; may participate in a technical council without joining an investor council; may participate in a Nexus Universe council without becoming a standards-interface participant; may join a national public authority learning room without obtaining investor council access; and may be invited to a controlled room without receiving broader council rights. The role, level, and record define the status.

1.7.3.6 Subscription Records. Subscription records should identify the subscribed council, participant identity, institutional affiliation where relevant, participation class, access level, subscription period, renewal status, confidentiality duties, conflict disclosures, claims permissions, publication class, public authority status where relevant, capital-reader status where relevant, sponsor or provider status where relevant, and correction status. The record should also identify whether the participant may be listed publicly, participate in nominations, join committees, or access controlled materials.

1.7.3.7 First Operational Participation Pathway. Council subscription is the first operational participation pathway in the Nexus Consortium architecture. It turns interest into recorded participation, recorded participation into agenda contribution, agenda contribution into potential leadership pools, and leadership pools into board, committee, workstream, or handoff pathways where properly authorized. It is the mechanism by which Nexus avoids both closed governance and unstructured openness.

## 1.7.4 Helix Council Participation

1.7.4.1 Institutional or Enterprise Membership Requirement. Joining Helix Councils requires institutional or enterprise membership in the relevant Consortium unless the applicable governance instrument expressly provides a different eligibility rule. Helix Council participation is a higher-trust participation surface because it is designed to balance major stakeholder classes, generate cross-sector legitimacy, and prevent capture of the Nexus agenda by any single constituency. It sits closer to agenda formation, leadership pools, and institutional legitimacy than general participation.

1.7.4.2 Purpose of Helix Councils. Helix Councils exist because systemic risk and exponential technology governance cannot be responsibly shaped by one sector alone. Public authorities understand legal mandate and public accountability. Academia and research institutions contribute evidence and independent analysis. Industry contributes capability and implementation knowledge. Civil society and communities surface legitimacy, rights, and lived impact. Capital readers identify finance-readiness questions. Media helps shape public understanding. Technical communities assess system feasibility. Youth and future-facing participants bring intergenerational perspective. Indigenous and protected-knowledge participants raise rights, knowledge, land, data, and governance considerations. Helix Councils create an institutional method for these perspectives to enter the system without collapsing their roles.

1.7.4.3 Helix Categories. Helix Councils may include public authority, academia, industry, civil society, environment / WEFH-B, capital, media, technical community, youth, community, Indigenous, public-good, and implementation interfaces. The exact Helix categories may vary by global, regional, or national level, provided that the purpose remains balanced participation, role clarity, institutional seriousness, safeguard awareness, and anti-capture. A national Helix structure may look different from a regional or global Helix structure because local legitimacy, legal context, and stakeholder systems differ.

1.7.4.4 Anti-Capture Function. Helix Councils exist to balance ecosystem perspectives and prevent capture. They ensure that public authority learning is not controlled by providers, technical evidence is not controlled by sponsors, finance-readiness is not controlled by investors alone, public-good claims are not controlled by enterprise visibility, national agendas are not set without domestic stakeholder plurality, and community or Indigenous participation is not reduced to symbolic presence. Helix Councils make capture structurally harder by requiring the agenda to pass through plural stakeholder surfaces.

1.7.4.5 Recorded and Claims-Limited Participation. Helix Council participation shall be recorded and claims-limited. Records shall identify the participant’s category, level, role, access rights, confidentiality obligations, conflicts, claims permissions, contribution status, publication status, and correction status. A participant may describe Helix Council participation only in approved language and only to the extent supported by the record. Participation shall not be described as endorsement, public authority approval, certification, procurement status, investor approval, project authorization, or founding-institution membership.

1.7.4.6 Higher-Trust Participation Surface. Helix Council participation is more serious than general council subscription because it signals deeper institutional or enterprise eligibility, greater responsibility for ecosystem balance, and closer proximity to agenda formation. It shall therefore be subject to stronger claims discipline, conflict disclosure, confidentiality, competition-law awareness, safeguard duties, participation duties, record cooperation, and correction powers. The closer a participant is to agenda formation, the higher the standard of role accuracy must be.

1.7.4.7 Helix Councils and Leadership Pools. Helix Councils may contribute to leadership pools, committee formation, board candidate identification, Nexus Universe agenda development, standards-interface priorities, acceleration topics, safeguard processes, and National Model or Regional Cluster Program Plan inputs. Participation in a Helix Council may support eligibility for consideration where governance rules allow, but it shall not itself create appointment, election, board status, fiduciary status, officer status, or governance control.

## 1.7.5 Role-Based Classes

1.7.5.1 Participant Classes. Nexus Consortium participant classes may include public authority participant, institutional member, enterprise member, provider member, manufacturer member, OEM member, university member, research institution member, civil society member, capital-reader member, investor participant, insurer participant, reinsurer participant, sponsor, partner, contributor, observer, community participant, Indigenous participant, youth participant, media participant, technical expert, builder, operator, host, national stakeholder member, regional stakeholder member, global stakeholder member, invited expert, standards-interface contributor, AEP Passport contributor, Nexus Universe participant, Nexus Acceleration participant, and project pathway participant.

1.7.5.2 Why Classes Are Necessary. Role-based classes are necessary because Nexus brings together actors whose rights, duties, risks, and public meanings differ radically. A public authority does not participate like a provider. A provider does not participate like a community. A capital reader does not participate like a sponsor. A university does not participate like a Project SPV. A national stakeholder does not participate like a global observer. If these roles were treated as interchangeable, the architecture would create false authority and false reliance. Class logic prevents that.

1.7.5.3 Defined Rights and Limits. Each class shall carry defined rights and limits. These may include eligibility for councils, Helix Councils, controlled rooms, documents, working groups, Nexus Universe pathways, Nexus Acceleration processes, standards-interface work, public-safe publication, directories, nomination pools, committee service, AEP Passport contribution, public authority learning, capital-reader rooms, technical evidence contribution, or handoff participation. No class shall be treated as open-ended authority. Every class is a defined role, not a general license.

1.7.5.4 No Status Inflation. No participant class shall imply approval, certification, financeability, bankability, insurability, procurement status, public authority endorsement, public-good endorsement, Nexus-ready status, investment status, insurance approval, standards conformance, national adoption, project authorization, public warning, official government support, or membership in GCRI, GRF, or GRA unless such status is separately and lawfully created, recorded, and authorized for public description. A class is a participation category, not a public endorsement.

1.7.5.5 Variation by Level. Participant classes may vary by global, regional, and national level. A global capital-reader member may not have national investor council rights unless accepted into the relevant national structure. A global provider member may not have national delivery rights unless separately engaged through lawful national or project-level pathways. A regional stakeholder may not speak for a national stakeholder structure. A national stakeholder member may have rights that are domestic, council-specific, or program-specific only. Level matters because legitimacy and authority are not portable by default.

1.7.5.6 Class Changes and Reclassification. Participant classes may change only through the applicable records and governance process. A sponsor may later become a contributor, a contributor may later become a member, a member may later become a council subscriber, a council subscriber may later become a committee participant, and a committee participant may later become eligible for leadership consideration. But each movement requires a record. Informal evolution of role shall not create new rights until the record is updated.

1.7.5.7 Preparation for Detailed Membership Architecture. The role-based class system prepares the detailed membership architecture of the Nexus Consortiums. It allows Nexus to be open to many types of actors while ensuring that rights, duties, access, visibility, and authority remain precise, recordable, and correctionable. A broad ecosystem becomes governable only when its participation classes are clear.

## 1.7.6 Subscription as Access, Not Authority

1.7.6.1 Subscription Defined. Subscription provides structured access, not institutional authority. A subscription may allow a participant to enter a council, receive materials, attend meetings, contribute agenda input, participate in deliberation, join working groups, be listed in participation records, receive controlled summaries, contribute to annual agenda formation, or become eligible for nomination pools, but it shall not by itself confer governance control, public authority status, enterprise rights, procurement influence, finance rights, certification power, or implementation authority.

1.7.6.2 Access Logic. The logic of subscription is access with discipline. Nexus needs a way for many actors to enter agenda formation without requiring every actor to become a governor, board member, fiduciary, owner, or institutional authority. Subscription solves this by providing a defined access pathway. The subscriber may enter the room, but the room remains governed by rules. The subscriber may contribute, but contribution remains subject to board governance, public-good discipline, and correction.

1.7.6.3 Permitted Subscription Contributions. Subscribed council participants may contribute agenda input, recommendations, evidence, technical observations, public authority learning needs, finance-readiness questions, safeguard concerns, Nexus Universe proposals, Nexus Standards issues, Nexus Acceleration pathways, Nexus Observatory needs, NXS-RLS topics, public-safe reporting considerations, National Model inputs, Regional Cluster Program Plan inputs, and nominations, subject to the applicable council rules.

1.7.6.4 No Control Unless Appointed or Elected. Subscribed participants do not control the Consortium unless elected or appointed into a defined governing role under applicable rules. Access to a room is not control of the room. Participation in a council is not control of the Consortium. Contribution to a workstream is not authority over the agenda. Nomination eligibility is not appointment. Speaking at an event is not institutional leadership. Providing technical input is not certification authority. Raising finance-readiness questions is not investment power.

1.7.6.5 No Control Over Other Bodies. Subscribed participants do not control GCRI, GRF, GRA, public authorities, National Consortium Companies, Project SPVs, providers, investors, insurers, Nexus bodies, national councils, regional Consortiums, global Consortiums, communities, Indigenous actors, or other participants except where a separate lawful governance instrument expressly provides a defined role. Subscription does not travel outside its record.

1.7.6.6 Subscription and Leadership Pathways. Subscription may support leadership pathways, but it is not leadership itself. Subscribed participation may place a participant into a candidate pool, leadership pool, committee eligibility pathway, workstream consideration process, or nomination process where governance rules allow. The next step must still be governed by eligibility checks, conflict review, appointment or election rules, role records, and acceptance of duties. Nexus uses subscription to identify contributors; it uses governance to appoint leaders.

1.7.6.7 Protection Against Subscription Overclaim. This clause prevents subscription from being mistaken for governance control. A subscribed participant may be inside the process without owning the process, influencing the agenda without controlling the agenda, contributing evidence without certifying the evidence, participating in readiness without approving implementation, and joining deliberation without acquiring authority over the Consortium. This distinction protects the credibility of open participation.

## 1.7.7 Membership Benefits and Limits

1.7.7.1 Permitted Membership Benefits. Membership benefits may include access to councils, participation records, member directories, events, briefings, Nexus Universe pathways, Nexus Standards-interface processes, Nexus Acceleration opportunities, Nexus Observatory pathways, NXS-RLS workstreams, Risk Academy programs, public-safe publications, controlled summaries, working groups, committee eligibility, nomination eligibility, leadership pool eligibility, contribution recognition, and access to approved knowledge products. These benefits should be useful enough to make membership valuable and bounded enough to keep membership trustworthy.

1.7.7.2 Benefits as Institutional Access, Not External Approval. Membership benefits should be understood as access to an institutional architecture, not external approval by that architecture. A member may gain access to learning, records, agenda formation, networking, controlled rooms, or program pathways. That access does not imply that the member’s products, projects, services, capital, public authority status, governance, data, safeguards, or claims have been approved. The membership benefit is participation in a serious process, not a public guarantee.

1.7.7.3 Accurate Description of Benefits. Benefits must be described accurately, precisely, and without inflation. Membership materials shall distinguish access from authority, participation from endorsement, visibility from approval, eligibility from appointment, contribution from selection, readiness from certification, finance-readiness from investment approval, public authority learning from public authority action, and standards-interface participation from standards conformance. Clear benefits create trust; inflated benefits create legal and reputational risk.

1.7.7.4 Excluded Benefits. Benefits shall not include guaranteed public authority access, procurement preference, investment access, capital commitment, insurance placement, certification, accreditation, public-good endorsement, Nexus-ready status, government support, regulatory comfort, standards conformance, AEP Passport approval, provider selection, SPV rights, National Consortium Company ownership, public finance allocation, or membership in GCRI, GRF, or GRA. These are not membership benefits because they require separate lawful processes, competent decisions, or independent records.

1.7.7.5 Claims Discipline for Visibility. Any member benefit involving visibility, directory listing, speaking role, event appearance, sponsorship acknowledgement, public-safe publication, logo use, badge use, Nexus Universe participation, Nexus Acceleration participation, Nexus Standards contribution, AEP Passport reference, National Model reference, or Regional Cluster Program Plan reference must be claims-disciplined. Public language shall reflect the exact class, role, level, date, status, and limitations of participation. The more visible the benefit, the stricter the claims discipline must be.

1.7.7.6 Benefit Levels and Renewal. Membership benefits may vary by level, class, subscription, renewal status, contribution status, sponsorship status, council status, or program status. Benefits may be time-limited, renewable, suspended, restricted, or withdrawn according to the applicable rules. A member whose status expires, changes, is corrected, is suspended, or is restricted may not continue to claim benefits that no longer apply. Membership is a living record, not a permanent public claim.

1.7.7.7 Trustworthy Membership Promise. The membership promise of Nexus is access to structured participation, not inflation of status. Members join because the architecture is serious, global, national, technical, public-good, finance-readable, and correctionable; they do not join to purchase authority, legitimacy, procurement advantage, certification, capital access, public authority influence, or public endorsement. This promise is more valuable because it is honest.

## 1.7.8 Membership Duties

1.7.8.1 Duties of Members and Subscribers. Members, subscribers, sponsors, partners, observers, contributors, council participants, Helix Council participants, committee members, working-group participants, Nexus Universe participants, Nexus Acceleration participants, Nexus Standards participants, Nexus Observatory participants, NXS-RLS participants, Risk Academy participants, AEP Passport contributors, public authority learning participants, capital-reader participants, and other role-based participants shall comply with the duties attached to their class, role, level, access, and record.

1.7.8.2 Core Duties. Duties include role accuracy, claims compliance, confidentiality, data protection, cybersecurity awareness, conflict disclosure, anti-capture conduct, competition-law compliance, procurement-neutral conduct, safeguard respect, community and Indigenous participation respect, protected-knowledge handling, privacy compliance, finance-boundary compliance, non-solicitation compliance where applicable, correction cooperation, records cooperation, responsible use of Nexus names, responsible use of GCRI / GRF / GRA names, and responsible use of marks, badges, references, materials, records, and public communications.

1.7.8.3 Duty of Role Accuracy. Participants must accurately describe who they are, what they do, what level they participate at, what rights they have, what rights they do not have, what records support their claims, and what limitations apply. A participant must not use ambiguity to inflate its status. Where a claim could reasonably be misunderstood, the participant must use narrower, clearer, and safer language. Role accuracy is the first duty of membership because every other duty depends on knowing what role is being performed.

1.7.8.4 Duty of Confidentiality and Data Discipline. Members and subscribers must respect confidentiality and data discipline. Controlled-room materials, public authority discussions, technical records, finance-readiness materials, community or Indigenous information, protected knowledge, cybersecurity information, infrastructure-sensitive material, procurement-sensitive material, personal data, commercially sensitive information, and internal governance records must be handled according to their publication class and access rules. Membership does not create a right to republish, commercialize, scrape, reuse, train models on, or disclose controlled Nexus information.

1.7.8.5 Duty of Conflict and Competition Discipline. Members must disclose conflicts and comply with competition, antitrust, procurement, anti-corruption, sanctions, market-integrity, and fair-participation rules where applicable. Councils, working groups, investor rooms, provider rooms, standards-interface processes, and Nexus Universe tracks must not become venues for collusion, bid-rigging, market allocation, price coordination, procurement manipulation, improper information exchange, sponsor distortion, or hidden preference formation. The openness of Nexus depends on disciplined conduct.

1.7.8.6 Duty of Safeguard Respect. Members must respect community safeguards, Indigenous rights, protected-knowledge protocols, environmental and social safeguards, privacy, cybersecurity, accessibility, inclusion, and public-safe reporting requirements. Participation shall not be used to extract data, appropriate knowledge, bypass local engagement, manufacture consent, or create public narratives that exceed the relevant records. Where communities or Indigenous actors participate, their presence shall not be converted into consent or endorsement unless the competent process expressly records that status.

1.7.8.7 No Misrepresentation. Members must not misrepresent their participation. They shall not claim endorsement, approval, certification, procurement status, investment readiness, insurance approval, public authority support, Nexus-ready status, standards conformance, national company rights, SPV rights, board status, council authority, public-good recognition, public warning authority, emergency authority, or public authority adoption beyond the applicable record. The duty is not merely to avoid false statements, but to avoid statements likely to create false reliance.

1.7.8.8 No Claim of Founding-Institution Membership. Members must not use Consortium affiliation to claim membership in GCRI, GRF, or GRA. They shall not describe themselves as members, affiliates, representatives, governors, partners, fiduciaries, agents, spokespeople, approved providers, certified entities, or authorized institutional actors of any founding institution unless a separate lawful instrument expressly creates and records that status. Consortium membership is separate from founding-institution status.

1.7.8.9 Duty to Cooperate With Correction. Members must cooperate with correction. Where a record is corrected, a claim is withdrawn, a badge is restricted, a directory entry is amended, a public statement is clarified, or participation status changes, the participant must update its own materials and cease using outdated or overstated language. Correction is not an accusation; it is a maintenance function of a trustworthy system.

1.7.8.10 Serious Membership Discipline. Membership is disciplined and serious. The value of membership depends on trust, and trust depends on accurate roles, lawful participation, appropriate conduct, controlled claims, records discipline, safeguard respect, data responsibility, conflict management, and willingness to correct overstatement when identified. Nexus membership is meaningful precisely because it carries duties as well as benefits.

## 1.7.9 Membership Records

1.7.9.1 Record Requirement. Membership and subscription records shall be maintained for each relevant Consortium, council, Helix Council, committee, working group, program, room, track, and participation surface. No participant status shall be treated as authoritative unless it can be traced to an appropriate record. In the Nexus architecture, participation is valid by record, not by announcement, reputation, logo proximity, meeting attendance, sponsorship language, or informal understanding.

1.7.9.2 Required Record Fields. Records shall identify member class, level, council access, subscription status, institutional or enterprise status, public authority status if relevant, sponsor status if relevant, partner status if relevant, contributor status if relevant, observer status if relevant, capital-reader status if relevant, provider status if relevant, community or Indigenous participation status where relevant, claims permissions, access restrictions, confidentiality obligations, conflict status, renewal status, publication class, correction status, and applicable limits on public description.

1.7.9.3 Additional Record Fields Where Needed. Records may also identify term, start date, expiry date, renewal date, geographic relevance, regional or national coverage, council category, Helix category, committee appointment, leadership-pool status, nomination status, voting status, non-voting status, observer status, controlled-room clearance, data-access level, document-access level, badge rights, directory rights, logo-use permissions, contribution history, attendance history, suspension status, termination status, and any unresolved correction or compliance issue.

1.7.9.4 Publication Classes. Records may be public, controlled, restricted, or internal depending on sensitivity, public-safe reporting requirements, privacy, cybersecurity, commercial confidentiality, public authority status, financial sensitivity, community safeguards, Indigenous protected knowledge, procurement relevance, provider sensitivity, sponsor sensitivity, and the participant’s role. Public visibility shall not be assumed merely because participation exists. Some participation is legitimate precisely because it can occur under controlled or restricted conditions.

1.7.9.5 Governance, Directory, Participation, and Correction Functions. Records shall support governance, directories, participation tracking, council access, controlled-room admission, eligibility review, nomination pools, board formation, committee formation, public-safe reporting, claims review, correction, suspension, termination, renewal, auditability, annual reporting, and historical traceability. A membership record is not merely an administrative entry; it is a governance instrument.

1.7.9.6 Record Integrity. Records must be kept current, versioned where appropriate, and corrected when outdated or inaccurate. If a participant changes status, loses eligibility, withdraws, is suspended, changes class, joins a council, leaves a council, gains or loses badge rights, receives a correction notice, or becomes subject to claims restrictions, the record should reflect that change. Outdated membership records are a risk to public trust.

1.7.9.7 Validity-by-Record. Membership logic shall align with validity-by-record. A participant is what the record says it is, within the limits of the record. Where a claim exceeds the record, the claim shall be corrected. Where a record is ambiguous, the narrower and safer interpretation shall apply until clarified. Where no record exists, the status shall not be claimed. This principle is central to the Nexus membership system.

## 1.7.10 Membership and Subscription Thesis

1.7.10.1 Section Thesis. Nexus Consortium participation is structured through membership, subscription, institutional eligibility, enterprise eligibility, role-based access, recorded duties, claims permissions, renewal logic, publication classifications, and correction pathways. The system is designed to be inclusive without becoming vague, participatory without becoming uncontrolled, and valuable without becoming inflated.

1.7.10.2 Councils and Helix Councils. Councils are the first participatory surface of the Nexus Consortium architecture. They allow members and eligible participants to contribute to agenda formation, public authority learning, standards-interface work, Nexus Universe preparation, Nexus Acceleration pathways, observability priorities, safeguard identification, finance-readiness questions, and leadership pools. Helix Councils require deeper institutional or enterprise membership because they carry greater responsibility for ecosystem balance, anti-capture, stakeholder legitimacy, and leadership-pool formation.

1.7.10.3 Access and Contribution, Not Uncontrolled Authority. Participation creates access and contribution pathways, not uncontrolled authority. A member may contribute; a subscriber may deliberate; a sponsor may support; a provider may evidence capability; a public authority may learn; a capital reader may identify finance-readiness questions; a university may contribute research; a community may raise safeguard concerns; an Indigenous actor may identify protected-knowledge or rights issues; a media participant may support public understanding. None of these roles becomes approval, execution, certification, procurement, investment, public authority action, consent, endorsement, or founding-institution membership by implication.

1.7.10.4 Governance Through Recorded Role. Nexus membership is powerful because it is precise. It gives actors a meaningful place in the architecture while protecting the architecture from role inflation, status overclaim, sponsor capture, provider dominance, capital distortion, public authority confusion, procurement misuse, finance overstatement, and public-good legitimacy drift. The recorded role is the foundation of trust.

1.7.10.5 Bridge to Full Membership System. This membership and subscription logic establishes the foundation for the full Nexus Consortium membership system: open enough to mobilize the world, disciplined enough to preserve trust, structured enough to generate councils and leadership, flexible enough to adapt across global, regional, and national levels, and bounded enough to prevent participation from becoming uncontrolled power.

1.7.10.6 Whitepaper Membership Thesis. The Nexus participation economy is not a peripheral administrative system; it is the operating logic by which Nexus transforms broad interest into governed participation, governed participation into agenda, agenda into records, records into readiness, and readiness into lawful handoff. Membership matters because it is structured. Subscription matters because it creates disciplined access. Role classes matter because they prevent confusion. Records matter because they make status verifiable. Correction matters because it keeps the system honest over time.

## Sources

1. UN General Assembly (2015). Sendai Framework for Disaster Risk Reduction 2015–2030. A/RES/69/283, 3 June 2015. <https://www.undrr.org/publication/sendai-framework-disaster-risk-reduction-2015-2030>
2. OECD (2014). Recommendation of the Council on the Governance of Critical Risks. OECD/LEGAL/0405, adopted 6 May 2014. <https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0405>
3. United Nations (2021). Our Common Agenda: Report of the Secretary-General. New York: United Nations. <https://www.un.org/en/common-agenda>
4. UN General Assembly (2024). The Pact for the Future. A/RES/79/1, adopted 22 September 2024, with the Global Digital Compact (Annex I) and the Declaration on Future Generations (Annex II). <https://undocs.org/A/RES/79/1>
5. UN Office of the Secretary-General's Envoy on Technology and UNDP (2024). Universal DPI Safeguards Framework. New York: United Nations, September 2024. <https://www.dpi-safeguards.org/>
6. Nexus Standards. NS-0: Constitution and principles. Status: PROPOSED; UNI `NXS-STD-ST-000004`. <https://nexustandards.com/standards/ns-0/>
7. Nexus Standards. NS-13: Open standards development process. Status: PROPOSED; UNI `NXS-STD-ST-000008`. <https://nexustandards.com/standards/ns-13/>
8. Nexus Standards. NS-10: Policies and clauses. Status: PROPOSED; UNI `NXS-STD-ST-000006`. <https://nexustandards.com/standards/ns-10/>
9. GCRI. How Nexus Consortium works. <https://therisk.global/consortium/>
10. GCRI. Global programme. <https://therisk.global/consortium/global/>
11. GCRI. Six programme regions. <https://therisk.global/consortium/regions/>
12. GCRI. National Nexus. <https://therisk.global/consortium/national/>
13. The Global Risks Forum. Council architecture. <https://globalriskforum.com/leadership/council-model/>
14. GCRI. Programme status. <https://therisk.global/consortium/programme-status/>
15. This documentation: [Governance in operation](https://docs.therisk.global/organization/governance-in-operation.md); [The Model](https://docs.therisk.global/organization/model.md); [historical labels](https://docs.therisk.global/organization/reference.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.therisk.global/organization/cooperation/consortiums/model/i.-identity/1.7-membership-council-participation-and-role-based-subscription.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

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