17. General Assembly
17.1 Institutional Membership Authority
17.1.1 The General Assembly is the institutional membership authority of a Nexus-aligned body where the governing instrument creates, recognizes, or preserves a membership layer. It is the broad constitutional surface through which members, institutional participants, recognized constituencies, or equivalent membership classes exercise those rights, approvals, elections, confirmations, accountability functions, and legitimacy powers reserved to them by the applicable charter, bylaw, articles, statute, or adopted governance instrument.
17.1.2 The General Assembly’s authority is institutional rather than operational. It anchors the organization’s public-good character, membership legitimacy, constitutional continuity, and high-level accountability. It does not manage day-to-day operations, verify technical systems, produce evidence, issue public authority decisions, prepare finance-readiness materials, operate platforms, supervise downstream execution, or replace the Board, executive leadership, TMDs, GRF, GCRI, GRA, Helix Councils, public authorities, or lawful execution actors.
17.1.3 Institutional membership authority means that the General Assembly is the body through which members act when the matter belongs to members. Such matters may include constitutional approval, election or confirmation functions, major structural changes, receipt of annual reports, high-level mission accountability, approval of specified reserved matters, or other powers expressly assigned to the General Assembly. It does not mean that members collectively hold every power of the institution.
17.1.4 The General Assembly must therefore be understood as a bounded legitimacy organ. It is powerful because it preserves the institutional consent, continuity, and constitutional accountability of the membership. It is safe because its powers are defined by instrument, notice, quorum, voting or consensus procedure, eligibility, record, and scope. It does not gain additional authority merely because a matter is important, visible, controversial, technical, financially significant, or publicly sensitive.
17.1.5 The General Assembly’s membership authority also protects the institution from founder capture, board isolation, executive drift, sponsor influence, technical dominance, platform centrality, finance pressure, and mission dilution. Where members hold reserved powers, those powers create a constitutional check. But that check operates through formal member authority, not through informal pressure, public campaigns, personality, donor preference, or unrecorded consensus.
17.1.6 Membership authority must be exercised with role discipline. A member may vote or deliberate as a member where the governance instrument permits. A member who is also a public official does not thereby act as public authority unless recorded in that separate capacity. A member who is an expert does not thereby verify technical claims. A member who is a funder does not thereby acquire influence. A member who represents a community does not thereby provide consent for that community unless the applicable consent standard is separately met.
17.1.7 The doctrine is direct:
The General Assembly is the membership authority of the institution for matters reserved to members; it supplies constitutional legitimacy without becoming management, technical authority, public authority, finance authority, platform authority, or execution authority.
17.2 Constitutional Role
17.2.1 The constitutional role of the General Assembly is to preserve the institution’s foundational identity, public-good purpose, mission lock, membership legitimacy, constitutional continuity, and ultimate member-level accountability. It is the institutional surface through which the membership ensures that the organization remains faithful to its founding commitments and does not drift into functions, structures, claims, or forms of power inconsistent with the Nexus doctrine.
17.2.2 In Planetary Nexus Governance, constitutional role is especially important because the rail mobilizes many forms of power. Evidence power, recognition power, finance-readiness power, technical power, platform power, public authority proximity, community legitimacy, sponsor resources, and machine intelligence can all create drift. The General Assembly serves as one constitutional safeguard against the organization being quietly reshaped by those powers.
17.2.3 The General Assembly’s constitutional role may include approval of foundational instruments, amendments to articles or bylaws where member approval is required, changes to mission or purpose, changes to membership rights, election or confirmation of certain governing persons, approval of mergers or dissolutions where applicable, receipt of high-level accountability reports, and review of major mission-integrity matters. These powers must be specified in the governing instrument and exercised through proper procedure.
17.2.4 The constitutional role is not unlimited. The General Assembly does not become a universal veto over operational matters unless the governing instrument provides such authority. It does not supervise staff directly. It does not approve every partnership, technical standard, registry entry, proof pack, platform workflow, public-safe summary, or program decision. It does not intervene in confidential safeguards matters or restricted public authority records except through proper governance channels.
17.2.5 The General Assembly should act through constitutional questions, not operational substitution. Its proper questions include: Does this change preserve the public-good purpose? Does it preserve non-execution? Does it protect role separation? Does it prevent capture? Does it maintain correctionability? Does it protect members’ rights? Does it respect lawful authority and community dignity? Does it preserve the institution’s public-benefit identity? Does it avoid platform, finance, sponsor, expert, or public authority overreach?
17.2.6 The constitutional role also includes the duty to avoid constitutional overreach. A membership body may undermine governance if it attempts to decide technical matters without evidence, override public authority boundaries, pressure safeguards functions, convert popular opinion into technical truth, or force public communication beyond publication controls. Constitutional legitimacy must remain disciplined by records, competence, law, and correction.
17.2.7 The General Assembly’s constitutional function should be supported by public-safe, member-appropriate records. Members should receive enough information to exercise their rights responsibly, but sensitive evidence, protected knowledge, cyber vulnerabilities, personal data, public authority-sensitive records, and finance-sensitive materials must remain controlled. Constitutional transparency must operate with safeguards.
17.2.8 The doctrine is direct:
The General Assembly preserves the constitutional soul of the institution: mission, purpose, member legitimacy, reserved authority, and public-good identity, while refusing to become an all-purpose operating authority.
17.3 Reserved Member Matters
17.3.1 Reserved member matters are those decisions, approvals, elections, confirmations, amendments, transactions, or accountability actions that the governing instrument assigns to the General Assembly or membership. They define the boundary between member authority and board, executive, council, technical, platform, recognition, routeability, or downstream authority.
17.3.2 Reserved member matters may include, where applicable, amendment of articles or bylaws requiring member approval, alteration of membership rights, election or confirmation of directors or trustees, removal of directors or trustees where permitted, approval of fundamental changes, dissolution, amalgamation, merger, continuance, transfer of substantially all assets, approval of certain mission-lock modifications, appointment or confirmation of auditors where applicable, receipt of annual reports, and other matters expressly reserved by law or governing instrument.
17.3.3 Reserved member matters must be clearly defined. Ambiguity creates conflict. If members believe a matter is reserved but the Board treats it as operational, trust may fail. If the Board sends every difficult matter to members without need, management becomes unstable. If executives act on matters reserved to members, authority is invalid or contestable. If sponsors or public authorities pressure reserved member matters, capture risk arises.
17.3.4 A matter does not become a reserved member matter merely because it is high-profile. A technical baseline, public-safe report, GCRI evidence method, GRF registry entry, GRA proof pack, platform workflow, TMD technical finding, safeguards hold, public authority capacity note, or downstream handoff is not automatically reserved to members unless the governing instrument says so. These matters may be reported to members, but reporting is not approval authority.
17.3.5 Reserved member matters must be exercised through proper procedure. Notice must state the matter clearly. Members must know the decision question, supporting record, authority basis, effect of approval or rejection, conflicts, voting or consensus method, quorum, threshold, eligibility, proxy or remote participation rules if applicable, and correction or challenge process. Informal member sentiment is not a reserved member decision.
17.3.6 Reserved member matters should include role-boundary review where they affect the Nexus doctrine. If a proposed amendment could affect non-execution, role separation, public authority boundaries, finance-readiness boundaries, protected participation, AI governance, platform subordination, or correctionability, the member materials should identify those effects. Members should not be asked to approve constitutional changes without seeing doctrine consequences.
17.3.7 Reserved member matters may interact with public authority, legal, or regulatory approvals. Member approval may be necessary but not sufficient. A member-approved fundamental change may still require filing, court approval, regulatory approval, charitable or nonprofit compliance review, public authority notice, or other lawful step. The record must distinguish member approval from external legal effect.
17.3.8 The doctrine is direct:
Reserved member matters belong to the General Assembly because the governing instrument assigns them there; no other body may bypass them, and the General Assembly may not expand them by implication into matters assigned elsewhere.
17.4 Election or Confirmation Functions
17.4.1 The General Assembly may hold election or confirmation functions where the governing instrument gives members authority to elect, confirm, remove, or otherwise participate in the composition of the Board of Trustees, Board of Directors, member representatives, council representatives, committee members, auditors, or other governance roles. These functions are constitutional mechanisms for accountability and legitimacy.
17.4.2 Election or confirmation is not merely personnel selection. It is a governance act that shapes fiduciary oversight, mission protection, role separation, conflict discipline, public-good stewardship, and member trust. Those elected or confirmed may become guardians of institutional purpose, not representatives of narrow constituencies unless the governing instrument expressly creates constituency-based seats.
17.4.3 Election processes must be fair, transparent, accessible, and record-valid. They should define eligibility, nomination, vetting, conflicts disclosure, diversity and competence considerations, term length, voting method, quorum, threshold, campaign or communication rules, remote participation, recount or challenge procedures, and recordkeeping. A poorly governed election can become a capture pathway.
17.4.4 Confirmation functions must also be bounded. A confirmation vote may confirm appointment to a defined office or role. It does not automatically grant authority beyond that office. A confirmed director remains subject to fiduciary duties. A confirmed council member remains subject to council terms. A confirmed technical representative does not become public authority. A confirmed community representative does not automatically provide community consent.
17.4.5 Election and confirmation processes must include conflict and capture controls. Candidates or nominees should disclose relevant relationships with sponsors, donors, hosts, providers, public authorities, finance actors, national companies, project SPVs, technical vendors, communities, political bodies, or downstream execution actors. Conflicts do not always disqualify, but they must be visible and managed.
17.4.6 Elections should not become popularity contests disconnected from competence and duty. Planetary Nexus Governance requires fiduciary, technical, legal, safeguards, data, public authority, community, finance-readiness, and public-good competence across the governance system. Election rules should allow the institution to maintain necessary skill, independence, diversity, and mission alignment.
17.4.7 Member election authority must not undermine board fiduciary independence. Where members elect directors, elected directors owe duties to the institution and public-good purpose, not merely to the members, constituency, sponsor, geography, or sector that supported them. Representation does not eliminate fiduciary duty.
17.4.8 Removal or non-confirmation functions should also be governed carefully. They should not be used as retaliation for correction, safeguards escalation, technical dissent, anti-capture action, or refusal to overclaim. The system must protect those who defend public-good integrity.
17.4.9 The doctrine is direct:
The General Assembly’s election and confirmation functions create accountable governance composition, but elected or confirmed persons serve the recorded office and public-good purpose, not informal factions, sponsors, platforms, finance actors, or personality-based authority.
17.5 Member Legitimacy Without Day-to-Day Management
17.5.1 The General Assembly provides member legitimacy without day-to-day management. This separation protects both legitimacy and operational effectiveness. Members should have meaningful constitutional rights, accountability channels, deliberative opportunities, and reserved powers, but the daily operation of the rail must remain with the Board, executive leadership, Central Bureau, portfolio divisions, technical functions, safeguards functions, platforms, councils, and other designated bodies according to their roles.
17.5.2 Day-to-day management includes staffing, workplan execution, contract administration within delegation, program management, intake processing, platform administration, publication workflow, technical review scheduling, records management, budget implementation, partnership coordination, operational risk management, and routine public communications. These tasks require continuity, confidentiality, speed, technical competence, and managerial accountability. A General Assembly is not designed to perform them.
17.5.3 Member legitimacy remains essential. Members may receive reports, ask questions, elect or confirm governance persons, approve reserved matters, propose motions where permitted, raise mission concerns, and participate in high-level institutional learning. But member participation must not become operational interference. If members manage day-to-day work informally, authority becomes confused, staff accountability weakens, confidentiality may be breached, and role separation erodes.
17.5.4 The separation is especially important for sensitive matters. Safeguards cases, protected knowledge, whistleblower matters, cyber incidents, public authority-sensitive records, personnel matters, finance-sensitive materials, legal advice, controlled-room evidence, and AI incident records cannot be opened to broad member management merely because members have legitimacy interests. The proper path is controlled reporting, oversight, and correction.
17.5.5 Member legitimacy without management also protects members. Members should not be deemed responsible for operational decisions they did not make, technical findings they did not verify, public claims they did not approve, finance-readiness states they did not issue, or downstream execution they did not control. Record-based separation prevents liability confusion and reputational overclaim.
17.5.6 The General Assembly may influence strategic direction through proper channels. It may approve constitutional matters, receive strategy, provide member feedback, request accountability, and refer concerns to the Board or Stewardship Committee. But member feedback does not automatically become instruction unless the governing instrument makes it binding.
17.5.7 The system must therefore provide members with meaningful information without converting them into managers. Annual reports, maturity summaries, public-safe dashboards, correction summaries, mission-lock reports, claims-discipline reports, and governance integrity reports can support member legitimacy while preserving operational boundaries.
17.5.8 The doctrine is direct:
Members legitimate the institution through defined constitutional rights and accountability functions; they do not manage the daily rail unless a specific recorded authority grants a specific management role.
17.6 General Assembly and Helix Legitimacy
17.6.1 The General Assembly and Helix Councils are distinct legitimacy surfaces. The General Assembly expresses institutional membership legitimacy. Helix Councils express whole-of-society deliberative legitimacy. Both are necessary. Neither replaces the other.
17.6.2 Membership legitimacy arises from the institution’s formal members or equivalent constituency body. It concerns constitutional identity, governance accountability, reserved member matters, elections, member rights, and institutional continuity. Helix legitimacy arises from the structured participation of public authorities, communities, experts, civil society, industry, operators, finance-readiness actors, Indigenous and local knowledge holders, media, and other relevant actors in matter-specific deliberation.
17.6.3 A General Assembly may be broad but still incomplete as whole-of-society legitimacy. Members may not include all affected communities, public authorities, technical experts, operators, or knowledge holders relevant to a specific matter. A Helix Council may be diverse and matter-relevant but still not hold member constitutional authority. The two forms of legitimacy must interoperate without collapsing.
17.6.4 The General Assembly should not treat its membership approval as substitute for helix review where a matter requires affected-community input, public authority interface, technical expertise, or social legitimacy. Conversely, a Helix Council should not treat its deliberation as substitute for member approval where the governing instrument reserves a matter to members.
17.6.5 Where a matter affects both institutional constitution and whole-of-society legitimacy, both layers may be required. For example, a major doctrine amendment may require member approval and helix consultation. A structural change affecting public-good role separation may require Board recommendation, Stewardship Committee review, Helix input, and General Assembly approval. A public-facing legitimacy issue may require Helix deliberation and member-level accountability reporting.
17.6.6 Records must distinguish the two. A member vote is not helix consensus. A helix recommendation is not member approval. A public authority participant in a Helix Council is not a member decision. A member’s technical comment is not TMD verification. The rail must record which legitimacy surface acted and what effect followed.
17.6.7 The relationship should be mutually reinforcing. Helix Councils can inform members about broader public meaning, social legitimacy, stakeholder concerns, ecological risks, and public authority contexts. The General Assembly can ensure that the institution remains constitutionally committed to maintaining helix legitimacy rather than becoming closed or member-only.
17.6.8 The doctrine is direct:
The General Assembly supplies member legitimacy; Helix Councils supply whole-of-society deliberative legitimacy. Planetary Nexus Governance requires both, records both, and permits neither to impersonate the other.
17.7 General Assembly and Board Authority
17.7.1 The General Assembly and the Board of Trustees or Board of Directors are distinct governing bodies with different authority sources, responsibilities, and operating roles. The General Assembly exercises member-level authority on matters reserved to members. The Board exercises fiduciary governance authority over the institution, subject to law, governing instruments, member reserved powers, public-good purpose, and applicable duties.
17.7.2 The Board is responsible for oversight, strategy, risk governance, compliance, executive appointment and supervision where applicable, budget oversight, policy approval, reserved board matters, institutional integrity, mission lock, role separation, and public-good stewardship. The General Assembly is responsible for member reserved matters, elections or confirmations where applicable, constitutional approvals, and member accountability functions. The two must be aligned but not confused.
17.7.3 The Board should not bypass the General Assembly where member approval is required. It should not treat member rights as advisory if the governing instrument makes them binding. It should not structure transactions, amendments, or governance changes to avoid member approval. Member reserved matters protect constitutional legitimacy.
17.7.4 The General Assembly should not usurp Board authority where the matter belongs to the Board. It should not attempt to manage staff, approve routine contracts, issue technical findings, direct public-safe publication, intervene in confidential legal or safeguards matters, or override fiduciary judgment without lawful authority. Board authority protects institutional continuity and accountability.
17.7.5 Board-member accountability should be record-valid. The Board should provide members with annual reports, audited or reviewed financial materials where applicable, mission reports, governance integrity reports, correction summaries, conflicts summaries, public-safe risk reports, and other materials required by law or governance instrument. Members should be able to ask informed questions without receiving unsafe restricted information.
17.7.6 Where conflict arises between the Board and General Assembly, the governing instrument should define resolution procedures. These may include legal review, special meeting, mediation, independent governance review, member vote, board reconsideration, Stewardship Committee review, or court or regulatory process where required. Informal power struggles should not define authority.
17.7.7 The Board and General Assembly share responsibility for preserving the institution from capture. The Board must resist operational capture. The General Assembly must resist membership capture. Sponsors, factions, platforms, finance actors, public authorities, technical elites, or personality-based networks should not use either body to dominate the rail.
17.7.8 The doctrine is direct:
The General Assembly and Board are complementary checks: members guard constitutional legitimacy; the Board guards fiduciary governance. Each is strongest when it respects the other’s recorded authority.
17.8 General Assembly and Convergence Chamber
17.8.1 The General Assembly and Convergence Chamber are distinct but related surfaces. The General Assembly is the formal membership authority for reserved member matters. The Convergence Chamber, or GA+, is the intensified deliberative convergence surface used for complex, cross-constituency, cross-institutional, or high-consequence matters requiring structured alignment among legitimacy forms. The General Assembly anchors member authority; the Convergence Chamber supports convergence.
17.8.2 The Convergence Chamber may include members, board representatives, council representatives, public authority participants, technical experts, safeguards actors, community representatives, finance-readiness actors, regional representatives, and other relevant actors depending on matter class. Its composition is functional and legitimacy-based, not simply membership-based.
17.8.3 The Convergence Chamber may prepare a matter for General Assembly decision. For example, a constitutional amendment, major doctrine shift, institutional restructuring, or mission-lock question may be deliberated in GA+ before a formal member vote. The chamber can surface evidence, dissent, public authority implications, technical concerns, safeguards issues, regional impacts, and public claims risks so that members act with deeper understanding.
17.8.4 The Convergence Chamber may also operate where no member decision is required. A matter may require cross-helix alignment, public-safe narrative discipline, correction, or escalation, but not formal General Assembly approval. In such cases, GA+ produces convergence records or recommendations, not member resolutions.
17.8.5 The General Assembly should not treat Convergence Chamber outputs as automatic member decisions. A GA+ recommendation must be placed before members under proper notice and procedure if member approval is required. Conversely, a General Assembly vote should not be treated as having completed the convergence process where the matter still requires public authority, technical, safeguards, or community review.
17.8.6 The Convergence Chamber must preserve dissent and role capacity. Its purpose is not to manufacture consensus for members. It should provide the General Assembly with a truthful account of convergence, unresolved conflict, conditions, risks, and minority positions. Members should not be asked to ratify a false consensus.
17.8.7 The relationship is therefore sequential where needed and complementary where useful. GA+ deepens deliberation; the General Assembly formalizes member authority where required. GA+ helps the institution think across the whole system; the General Assembly acts through its constitutional membership role.
17.8.8 The doctrine is direct:
The Convergence Chamber prepares and deepens convergence; the General Assembly exercises member authority. Convergence is not approval unless the competent body records approval.
17.9 Member Rights and No Implied Authority
17.9.1 Member rights are the rights expressly granted to members by law, articles, bylaws, membership agreements, policies, or adopted governance instruments. They may include notice, attendance, voting, information access, nomination, election participation, proposal submission, inspection rights, accountability rights, participation in assemblies, or other rights defined by the governing framework. These rights are real and must be respected.
17.9.2 Member rights do not create implied authority beyond their terms. A member does not gain power to bind the institution merely by being a member. A member does not speak for the Board, GCRI, GRF, GRA, Nexus Platforms, public authorities, Helix Councils, TMDs, national desks, or downstream networks unless separately authorized. A member does not represent all members unless elected or appointed to do so. A member does not create public claims merely by expressing support.
17.9.3 No implied authority is essential because membership can be misused. A member may claim that the institution endorses a project. A member may use membership status in marketing. A member may imply access to public authorities. A member may suggest that a technical view is institutional doctrine. A member may cite participation as evidence of recognition or finance-readiness. Such claims must be prohibited unless record-valid.
17.9.4 Member information rights must be balanced with confidentiality and safeguards. Members may have rights to receive reports, financial statements, notices, and governance materials. They do not automatically have access to protected knowledge, personal data, cyber-sensitive materials, public authority-sensitive records, legal privileged material, personnel records, finance-sensitive annexes, or controlled-room evidence. Access must follow law and publication class.
17.9.5 Member participation rights must also be protected. Members should have accessible procedures for meetings, voting, proposals, questions, translation, disability accommodation, remote access where permitted, and correction of membership records. Member legitimacy depends on meaningful participation, not merely formal rights.
17.9.6 Member speech must be distinguished from institutional speech. Members may express personal or organizational views, subject to applicable rules, but may not represent those views as institutional positions unless authorized. Public claims guidance should define use of name, logo, membership status, recognition language, and prohibited overclaim.
17.9.7 Member rights may include the right to raise concerns about mission drift, capture, conflicts, role collapse, public claims misuse, or governance integrity. Such concerns should have a pathway to the Board, Stewardship Committee, Central Bureau, or appropriate body. Members should not need to rely on informal pressure to protect constitutional integrity.
17.9.8 The doctrine is direct:
Members have the rights the governance instrument gives them; they do not acquire implied authority to bind, represent, approve, recognize, certify, finance, procure, execute, or speak for the Nexus system by membership alone.
17.10 General Assembly Records
17.10.1 General Assembly records are the record-valid proof of member-level governance. They include notices, agendas, attendance records, quorum determinations, member capacity records where relevant, voting records, consensus records, resolutions, minutes, written consents, proxy records where permitted, election records, candidate disclosures, member questions, responses, reports received, reserved-matter materials, conflicts, dissent, challenges, corrections, and closeout records.
17.10.2 General Assembly records must preserve constitutional validity. If a member decision is challenged, the institution must be able to show notice, eligibility, quorum, decision question, voting or consensus method, threshold, result, authority, and record approval. Informal recollection is not sufficient. The General Assembly’s legitimacy depends on records.
17.10.3 Records must distinguish different forms of member action. Discussion is not approval. A straw poll is not a vote unless defined as such. Consensus discussion is not unanimous consent unless recorded under the proper rule. Receipt of a report is not approval of all contents unless the resolution says so. Election is not appointment to an executive role unless the governance instrument provides. Member concern is not board instruction unless properly adopted.
17.10.4 Records must also preserve dissent. Member dissent, abstention, objection, minority statement, procedural challenge, or request for correction may be important to institutional legitimacy. Minutes should not flatten contested matters into neutral unanimity where disagreement was material. Dissent does not necessarily defeat a decision, but it should be recordable.
17.10.5 Records must be publication-classified. Some General Assembly records may be public or public-safe. Others may be member-only, confidential, privileged, restricted, or protected. Election results may be public-safe while candidate disclosures remain controlled. Annual reports may be public while detailed risk annexes remain restricted. Member transparency must operate with data, privacy, safeguards, cyber, legal, and public authority constraints.
17.10.6 Records should connect to Case IDs where matters relate to ongoing governance cases. If the General Assembly approves a constitutional matter connected to a broader case, the resolution should link to the Case ID or equivalent docket record. This prevents member decisions from becoming detached from the governance rail.
17.10.7 General Assembly records must be correctable. If minutes are inaccurate, votes miscounted, capacity misstated, public authority participation overdescribed, member status wrong, or public claims exceed the record, correction procedures must exist. Corrections should show what changed, why, by whose authority, and with what effect.
17.10.8 The Central Bureau or equivalent secretariat should administer General Assembly records, but administrative control does not create substantive authority. Records staff preserve the record; members and competent bodies create the governance acts.
17.10.9 The doctrine is direct:
General Assembly authority exists through records. Without notice, quorum, authority, decision text, result, and correction path, member legitimacy cannot become record-valid governance.
17.11 General Assembly in the Planetary Governance Chain
17.11.1 The General Assembly occupies the broad institutional membership position in the planetary governance chain. It is one of the legitimacy anchors through which Nexus-aligned institutions remain accountable to their members, mission, public-good identity, and constitutional instruments. It is not the apex of all planetary authority, because Planetary Nexus Governance is not a single hierarchy. It is a role-separated rail.
17.11.2 In the full chain, the General Assembly interacts with Helix Councils, the Convergence Chamber, Board, Stewardship Committee, Central Bureau, executive management, global and regional stewardship boards, national councils, competence cells, TMDs, GCRI, GRF, GRA, Nexus Platforms, public authorities, and downstream actors. Its role is to contribute member legitimacy and reserved approvals where applicable, not to absorb all other functions.
17.11.3 The General Assembly supports planetary governance by preserving constitutional fidelity. It can ensure that institutions do not drift from public-good purpose into finance execution, platform capture, technical authority, sponsor influence, public authority laundering, community extraction, or AI overreach. Through reserved powers, elections, reports, and accountability, members can protect the mission lock.
17.11.4 The General Assembly also supports learning. It can receive public-safe annual learning records, correction summaries, maturity reports, claims-discipline reports, safeguards reports, member accountability reports, and strategic doctrine updates. It can ask whether the rail is becoming more truthful, inclusive, technically competent, finance-disciplined, and correctionable.
17.11.5 The General Assembly must itself be subject to the doctrines it helps protect. It must not overclaim authority. It must not treat member participation as whole-of-society consent. It must not treat votes as technical truth. It must not treat majority support as public authority. It must not treat member enthusiasm as finance-readiness. It must not use constitutional authority to bypass safeguards. It must remain record-valid.
17.11.6 In national, regional, or institutional adaptations, the General Assembly may take different forms depending on legal structure. Some bodies may have formal members. Some may have constituency assemblies. Some may have participant forums without legal member powers. Some may have advisory assemblies. The name matters less than the record: what authority exists, who holds it, how it is exercised, and what it does not do.
17.11.7 The General Assembly’s place in the planetary chain can be summarized as follows: it is a legitimacy root, not an operating engine; a constitutional safeguard, not a technical verifier; a membership authority, not a public authority; an accountability surface, not an execution body; a guardian of mission, not owner of the whole rail.
17.11.8 The final doctrine of this chapter is direct:
The General Assembly gives the Nexus institution a constitutional membership voice in the planetary governance chain. It strengthens legitimacy when it exercises reserved authority clearly, receives record-valid accountability, preserves mission discipline, and respects the boundaries that keep the wider rail role-separated, lawful, public-good, and correctionable.
Last updated
Was this helpful?