# III. Charters #### Summary This page defines the charter layer of Nexus Operations. If **II. Frameworks** explains the methodological architecture of Nexus work, **III. Charters** explains the bounded working modes through which that methodology is enacted in practice. Frameworks describe how Nexus work should move. Charters define how particular forms of work are authorized, scoped, conducted, attributed, reviewed, corrected, closed, and handed off. They are the operating instruments that prevent inquiry, collaboration, volunteering, contribution, and related working modes from becoming informal, extractive, overclaimed, or self-authorizing. The charter layer is essential because Nexus is a public-good-rooted, standards-bearing, federated, and realization-capable architecture. Its work may involve evidence, public-safe publication, Digital Public Goods, observatory outputs, public authority learning, routeability, claims discipline, Marketplace objects, Foundry packages, Studio workflows, national structures, providers, hosts, and lawful execution pathways. In such an environment, ordinary goodwill is not enough. Work must be bounded by role, record, scope, safeguards, attribution, output status, and correctionability. The current operating corpus identifies at least three core chartered working modes: **Investigation**, **Collaboration**, and **Volunteers**. These should be understood not as the only possible charters, but as the first visible charter family of Nexus Operations: inquiry, joint work, and contribution under governed conditions. *** ### 3.1 Why Charters Matter Within Operation Charters matter because complex operating systems fail not only at the level of strategy, governance, or standards. They often fail at the level where people actually work. Investigation may proceed without clear boundaries. Collaboration may expand without clarity on responsibility, attribution, decision rights, confidentiality, or output status. Volunteer contribution may become generous but invisible, useful but unsupported, or load-bearing without safeguards. Working groups may become active before their mandate is clear. Public-facing outputs may be produced before public-safe status is established. Technical contributors may become operationally central without role clarity. Platform access may be mistaken for authority. Forum participation may be mistaken for adoption. Charters prevent these failures by converting working intention into bounded institutional conduct. A charter defines the working mode. It states why the mode exists, who may participate, what may be done, how the work proceeds, what records are created, what outputs may be produced, what status those outputs carry, how safeguards are applied, how attribution is handled, how disputes or concerns are escalated, and how the work closes or transitions. Charters are therefore instruments of operating legitimacy. They ensure that Nexus can welcome participation, inquiry, and collaboration without allowing activity to become authority by implication. *** ### 3.2 What a Charter Means in Nexus Within Nexus, a charter is a governed statement of working purpose, scope, role, conduct, accountability, output discipline, safeguard obligations, and closure logic for a defined class of activity. A charter is not a ceremonial declaration. It is not a branding page. It is not a loose statement of intent. It is not a substitute for the constitutional charter of Nexus or the bylaws of any entity. It is an operating instrument below the constitutional order and above informal practice. A working charter performs several functions. First, it defines **purpose**. It explains why the working mode exists and what problem it solves in the operating system. Second, it defines **scope**. It states what belongs inside the working mode and what must be routed elsewhere. Third, it defines **roles**. It clarifies who may lead, contribute, review, observe, advise, approve, publish, or receive handoff. Fourth, it defines **conduct**. It sets expectations for professionalism, evidence handling, confidentiality, attribution, safeguards, public-safe discipline, and respect for role boundaries. Fifth, it defines **outputs**. It states what the working mode may produce and what those outputs do or do not mean. Sixth, it defines **records**. It identifies what must be documented, versioned, preserved, or transferred. Seventh, it defines **review and correction**. It explains how errors, concerns, disputes, overclaims, or changed facts are handled. Eighth, it defines **closure and transition**. It explains how work ends, pauses, escalates, becomes archived, or moves to another pathway. A charter is therefore a boundary instrument. It creates enough structure for trust and enough flexibility for work to proceed. *** ### 3.3 Why Nexus Uses Chartered Working Modes Nexus uses chartered working modes because plural systems require discipline at the point of action. Goodwill, expertise, urgency, enthusiasm, and shared mission can initiate activity. They cannot sustainably govern it. Without chartered modes, Nexus would risk hidden hierarchy, weak records, unclear authorship, overbroad claims, volunteer dependency, public-safe mistakes, contribution disputes, and informal authority. The need for chartered modes is especially strong in Nexus for several reasons. Nexus is **multi-institutional**. Contributors may come from different entities, countries, sectors, hosts, companies, universities, public authorities, communities, and technical environments. Nexus is **public-good-rooted**. Work must remain aligned to public-purpose obligations and cannot be governed only by private project conventions. Nexus is **standards-bearing**. Operational work may affect semantics, public meaning, maturity claims, conformance pathways, routeability, registries, or protocol states. Nexus is **federated**. Work may occur across global, regional, national, host, node, and platform contexts. Nexus is **realization-capable**. Even early-stage work can be overread as readiness, recognition, finance-readability, deployment approval, or public authority adoption if its status is not clear. Chartered working modes make these distinctions visible. They allow Nexus to be open without becoming vague, collaborative without becoming uncontrolled, and productive without losing accountability. *** ### 3.4 The Charter Layer in the Nexus Operating Architecture The charter layer sits between frameworks and working structures. Frameworks define the methodological logic of Nexus work. Charters define bounded working modes. Networks, working groups, competence cells, platforms, reports, media, forums, Marketplace processes, Foundry workflows, and Studio environments then carry work under those methods and modes. The charter layer should therefore be read as the practical hinge between method and activity. The current core charter family includes: * the **Investigation Charter**; * the **Collaboration Charter**; * the **Volunteers Charter**. These three modes correspond to three recurring operational realities. Nexus must inquire. Nexus must work with others. Nexus must receive and steward contribution. Each mode requires different rules. Investigation is not collaboration. Collaboration is not volunteer contribution. Volunteer contribution is not a lesser form of formal work. Each has a distinct purpose, risk profile, output logic, and safeguard requirement. The charter layer may expand over time. Future charters may be needed for working groups, public authority learning, community science, controlled rooms, data stewardship, node operations, report production, Marketplace review, Foundry contribution, Studio workflows, or provider participation. The principle is the same: where a working mode could otherwise produce ambiguity, a charter should define it. *** ### 3.5 Charter Hierarchy and Legal Position Working charters must be read within the Nexus hierarchy. They do not override constitutional instruments, entity bylaws, governance rules, standards authority, public-safe publication rules, applicable law, public authority mandates, data protection obligations, contractual duties, or protocol governance. They operate inside the architecture. They do not create the architecture. A working charter may authorize a mode of work. It does not create institutional office unless the relevant governance instrument does so. A working charter may permit contribution. It does not create governance authority. A working charter may define collaboration. It does not create partnership status beyond its terms. A working charter may allow investigation. It does not create recognition, standing, public authority finding, or finance-readiness. A working charter may classify outputs. It does not make those outputs public-safe, recognized, standardized, or execution-authorizing unless the proper process occurs. This hierarchy matters because charters are strong only when they are bounded. Their purpose is to make work safer and clearer, not to become informal constitutions of their own. *** ### 3.6 Common Anatomy of a Nexus Working Charter Every Nexus working charter should include a common anatomy, adapted to the working mode. A mature working charter should address: **Purpose.** Why the mode exists and what operating problem it solves. **Scope.** What activity is included and excluded. **Authority.** Who may initiate, approve, supervise, review, pause, close, or escalate the work. **Participants.** Who may participate, in what capacity, under what conditions. **Roles.** Who leads, contributes, reviews, observes, supports, records, or speaks. **Conduct.** What professional, ethical, public-safe, confidentiality, data, evidence, and safeguard standards apply. **Records.** What must be documented, stored, versioned, and preserved. **Outputs.** What the mode may produce and what those outputs do not imply. **Attribution.** How contribution, authorship, review, stewardship, and institutional responsibility are recorded. **Safeguards.** What protections apply to participants, communities, sensitive knowledge, public authority interfaces, data, market-sensitive information, and public claims. **Review.** What quality, technical, public-safe, governance, standards, or claims review is required. **Handoffs.** How work moves to reports, records, registries, standards review, public-safe publication, Marketplace, Foundry, Studio, consortium pathways, or lawful execution. **Correction.** How errors, overclaims, disputes, breaches, or changed facts are addressed. **Closure.** How the mode ends, pauses, archives, renews, or transitions. This common anatomy keeps the charter layer coherent even as different charters serve different purposes. *** ### 3.7 Common Principles Across All Working Charters All Nexus working charters should share common principles. #### 3.7.1 Role-Bounded Participation Participation must be meaningful but bounded. A participant’s presence does not create authority beyond the recorded role. #### 3.7.2 Validity by Record Material work should leave records appropriate to its status. Memory, enthusiasm, or informal consensus cannot substitute for records where the work has institutional consequence. #### 3.7.3 Stage Truth Chartered work must not be described as more mature, authoritative, public-safe, recognized, or execution-ready than its actual status. #### 3.7.4 Public-Safe Discipline Outputs that may affect public meaning, public authority relationships, communities, markets, or institutional trust must observe public-safe rules. #### 3.7.5 Safeguards and Non-Exploitation Participants, volunteers, communities, Indigenous and local knowledge holders, and vulnerable stakeholders must not be used as unprotected sources of labor, legitimacy, data, or narrative value. #### 3.7.6 Attribution and Stewardship Contribution should be visible and fair. Outputs should have stewards. Shared work should not become orphaned work. #### 3.7.7 No Hidden Authority Repeated presence, technical centrality, platform access, donor support, expertise, or operational importance must not create unrecorded decision authority. #### 3.7.8 Non-Execution by Default Chartered work does not become procurement, public authority action, finance execution, legal determination, investment advice, underwriting, insurance approval, or deployment authorization by default. #### 3.7.9 Correctionability Chartered work must be correctable. Errors, overclaims, ambiguity, and changed facts must have pathways for correction or supersession. #### 3.7.10 Most-Restrictive Reading Where a charter can be read narrowly or broadly, the reading that preserves stronger role boundaries, narrower claims, lower maturity implication, stricter public-safe interpretation, and stronger non-execution discipline should apply unless competent authority records otherwise. *** ### 3.8 The Investigation Charter The Investigation Charter governs inquiry within Nexus. Investigation is not merely research by another name. It is a bounded working mode that may involve evidence gathering, issue development, structured questioning, verification, analytical inquiry, risk interpretation, exploratory synthesis, or pre-decisional understanding. Because investigative work can influence institutional meaning, public interpretation, standards questions, routeability, public authority learning, or later realization pathways, it must be conducted with discipline. The Investigation Charter exists to allow serious inquiry without premature implication. It protects Nexus from two opposite failures: under-governed inquiry and overclaimed conclusions. Under-governed inquiry creates weak evidence, unclear sources, unreviewed assumptions, and uncontrolled narratives. Overclaimed conclusions convert investigation into determination before the proper process has occurred. The Investigation Charter makes inquiry possible while preserving status truth. *** ### 3.9 Purpose of Investigation The purpose of investigation in Nexus is to create disciplined, reviewable, and bounded inquiry into matters relevant to the architecture, its domains, its signals, its risks, its implementation pathways, or its institutional and ecosystem context. Investigation may be used to clarify a question, develop an issue, structure evidence, examine a signal, prepare a report, test an assumption, identify a risk, support public-safe understanding, inform a working group, or determine whether a matter should be routed to another pathway. Investigation exists to clarify. It does not by itself create standing, recognition, maturity, routeability, public authority determination, finance-readiness, conformance, Marketplace status, Foundry readiness, Studio authorization, or execution commitment. The investigative posture is therefore disciplined curiosity under record. *** ### 3.10 Scope of Investigation The Investigation Charter should distinguish several levels of inquiry. **Informal analysis** may occur as ordinary thinking, discussion, or background review. **Exploratory inquiry** may gather context without creating institutional conclusions. **Structured investigation** may create records, evidence briefs, interview notes, issue logs, analysis memoranda, or internal findings. **Public-facing investigation** may produce outputs that require editorial, public-safe, claims, methods, legal, or governance review. **Routeability-relevant investigation** may inform later readiness, recognition, finance-readable, standards, Marketplace, Foundry, Studio, or consortium pathways. Not every question should become a formal investigation. Not every investigation should become public. Not every investigative output should become a report. Not every report should become recognition. Scope rules prevent investigation from becoming inflated. They also prevent serious inquiry from being dismissed as informal merely because it began small. *** ### 3.11 Conduct of Investigation Investigation must be conducted under standards of evidence handling, source discipline, attribution, traceability, confidentiality, public-safe awareness, and safeguards. Investigators should distinguish facts, assumptions, hypotheses, interpretations, uncertainties, and recommendations. Sources should be recorded where appropriate. Sensitive information should be handled under the applicable classification. Public authority information should not be overread. Community knowledge should not be extracted or published without safeguards. Market-sensitive, procurement-sensitive, security-sensitive, data-sensitive, or protected information must be controlled. Investigation should also preserve fairness. Where a matter concerns identifiable institutions, communities, partners, providers, public authorities, or contributors, the investigation should avoid careless claims, reputational harm, or premature public framing. A disciplined investigation is not merely thorough. It is bounded, fair, traceable, and correctable. *** ### 3.12 Investigation and Role Separation Investigation must preserve role separation. Investigators do not automatically become validators. Analysts do not automatically become institutional spokespersons. Evidence gatherers do not automatically become standards authorities. Technical reviewers do not automatically become public authority decision-makers. Community interviewers do not automatically acquire rights to publish protected knowledge. A working group investigation does not automatically become GRF recognition. A GCRI methods inquiry does not automatically become GRA routeability. A GRA routeability inquiry does not become investment advice. A provider-supported investigation does not become provider endorsement. Investigation may inform later pathways, but it does not collapse into them. The rule is: **Inquiry may support authority; it does not become authority by itself.** *** ### 3.13 Investigation Output Discipline Investigative outputs must be classified clearly. They may include: * intake notes; * issue logs; * source lists; * evidence briefs; * interview summaries; * analytical notes; * internal memoranda; * risk notes; * technical observations; * public-safe summaries; * draft reports; * recommendation notes; * escalation dockets; * correction notes. Each output should state its status, scope, limits, intended audience, review state, and non-effect where appropriate. An evidence brief is not a determination. An investigation note is not a report. A draft report is not a public publication. A public-safe summary is not the full record. A recommendation note is not approval. An escalation docket is not a final conclusion. Output discipline allows investigation to feed the operating system without distorting public meaning. *** ### 3.14 Investigation Closure and Correction Investigations should conclude in structured form. Closure may take several forms: * no further action; * archive; * route to report; * route to governance review; * route to standards review; * route to GRF public-safe or recognition pathway; * route to GCRI methods review; * route to GRA routeability review; * route to Marketplace, Foundry, or Studio assessment; * route to safeguards review; * route to public authority capacity clarification; * route to correction or supersession. Closure should identify what was learned, what remains uncertain, what records exist, what outputs were produced, what status they hold, and what pathway follows. Investigation must also remain correctable. New evidence may change prior understanding. Errors may be identified. Overclaims may need narrowing. Outputs may require correction, supersession, withdrawal, or archival. An investigation that cannot close becomes operational sprawl. An investigation that cannot correct becomes institutional risk. *** ### 3.15 Investigation as a Safeguard Against Narrative Inflation A distinctive value of the Investigation Charter is that it protects Nexus against narrative inflation. In complex systems, interesting findings can acquire rhetorical force before they acquire stable institutional meaning. Urgent issues can become public claims before they become reviewed evidence. Preliminary analysis can be treated as conclusion. A promising signal can be described as maturity. A local observation can be generalized into system-wide claim. The Investigation Charter interrupts that pattern. It ensures that evidence remains evidence. Inquiry remains inquiry. Provisional synthesis remains provisional. A finding remains bounded by its method and scope. A recommendation remains a recommendation. A public-safe summary remains limited to what can safely be said. This is especially important in domains touching sovereign infrastructure, public authority, public risk, standards-bearing interpretation, community knowledge, market-sensitive information, and routeability. The more consequential the field, the more valuable a disciplined investigation mode becomes. *** ### 3.16 The Collaboration Charter The Collaboration Charter governs multi-actor work within Nexus. Collaboration is one of the operating conditions of the system. Nexus requires work across institutions, sectors, domains, geographies, hosts, technical systems, public authorities, companies, universities, communities, sponsors, providers, and contributors. But collaboration without visible boundaries is one of the most common sources of ambiguity in authorship, accountability, decision rights, public claims, and maintenance responsibility. The Collaboration Charter ensures that working together strengthens the architecture rather than diffusing responsibility. It governs how actors co-produce, advise, review, coordinate, host, contribute, and steward outputs without collapsing their roles. It makes collaboration a governed strength rather than a vague virtue. *** ### 3.17 Purpose of Collaboration The purpose of collaboration in Nexus is to enable structured multi-actor production, learning, coordination, review, and alignment in ways consistent with the constitutional, operational, and standards-bearing order of Nexus. Collaboration may support reports, research, Digital Public Goods, working groups, competence cells, public authority learning, observatory work, Marketplace development, Foundry preparation, Studio workflow design, node operations, Academy pathways, campaigns, forums, media, standards interpretation, or realization preparation. Collaboration exists to allow actors to work together without creating hidden authority, unclear ownership, unmanaged reliance, or public-facing overclaim. The purpose is not merely to gather people. It is to organize joint work responsibly. *** ### 3.18 Modes of Collaboration A Collaboration Charter should distinguish among collaboration modes. Modes may include: * co-authoring; * advisory participation; * technical contribution; * working-group coordination; * peer review; * public-safe review support; * hosted collaboration; * research collaboration; * data collaboration; * community collaboration; * provider collaboration; * public authority learning collaboration; * Marketplace collaboration; * Foundry collaboration; * Studio workflow collaboration; * domain or guild-based collaboration; * regional or national consortium collaboration. Not all collaboration carries the same responsibilities or implications. A reviewer is not automatically an author. An adviser is not automatically a decision-maker. A host is not automatically a steward. A provider is not automatically endorsed. A public authority participant is not automatically adopting. A sponsor is not automatically controlling. Clear collaboration modes prevent confusion before it appears. *** ### 3.19 Role Clarity in Collaboration The Collaboration Charter should specify who leads, who contributes, who reviews, who records, who decides, who publishes, who maintains, who speaks for an output, and who may not speak beyond their role. This is essential because collaboration often blurs boundaries through repeated interaction. A contributor may help produce a document without owning its institutional meaning. A technical participant may provide expertise without approving the output. A public authority participant may provide learning input without issuing public authority decision. A provider may contribute implementation insight without becoming preferred vendor. A sponsor may support collaboration without influencing claims or recognition. A platform administrator may enable collaboration without deciding output status. Role clarity protects contributors and institutions alike. It allows collaboration to be open, serious, and bounded. *** ### 3.20 Attribution, Stewardship, and Maintenance Collaborative outputs require attribution and stewardship. Attribution records who contributed, authored, reviewed, advised, translated, supported, or maintained a work product. Stewardship records who is responsible for the output after production. Maintenance records who updates, corrects, archives, or supersedes the output. Without these distinctions, collaboration produces orphaned outputs. An orphaned output is dangerous because no one knows who may update it, correct it, defend it, retire it, or explain its status. The Collaboration Charter should therefore require clear attribution and stewardship rules, especially for reports, public-facing materials, Digital Public Goods, software packages, data products, training modules, Marketplace listings, Foundry packages, Studio workflows, playbooks, templates, and public-safe summaries. Shared work must not become unowned work. *** ### 3.21 Collaboration and Boundary Preservation Collaboration must not erase institutional differentiation. The Global Centre for Risk and Innovation (GCRI), The Global Risks Forum (GRF), The Global Risks Alliance (GRA), the Nexus Standards Foundation (NSF) or applicable protocol authority, national structures, regional structures, hosts, providers, public authorities, sponsors, universities, communities, and contributors may collaborate. But they do not become one another. A GCRI-led methods collaboration does not become GRF recognition by default. A GRF-reviewed public-safe output does not become GRA finance-readiness by default. A GRA routeability collaboration does not become finance execution. A standards collaboration does not become public authority law. A provider collaboration does not become provider control. A host collaboration does not become host sovereignty. A sponsor collaboration does not become sponsor authority. The strength of collaboration depends on preserving the difference among roles. *** ### 3.22 Escalation and Dispute Handling in Collaboration Collaboration will sometimes produce disagreement. Disputes may concern authorship, attribution, scope, confidentiality, public-safe release, technical approach, evidence interpretation, data handling, community safeguards, provider role, sponsor influence, public authority capacity, Marketplace status, Foundry readiness, Studio workflow use, or public claims. The Collaboration Charter should define how these issues are escalated. Some matters may be resolved by the workstream lead. Some may require public-safe review. Some may require governance review. Some may require standards review. Some may require safeguards review. Some may require legal, data, privacy, procurement, market-sensitivity, or public authority capacity review. Disputes should not be resolved by reputation, seniority, funding, technical control, platform access, or informal pressure. A governed collaboration system should have pathways for disagreement that preserve trust. *** ### 3.23 Collaboration and the Problem of Hidden Authority One of the greatest risks in collaborative systems is hidden authority. Hidden authority occurs when repeated involvement, technical centrality, platform access, donor support, public visibility, or social proximity begins to substitute for explicit mandate. A collaborator may be assumed to hold decision rights they were never given. A technical contributor may become de facto approver. A host may become informal owner. A provider may become standard-setter by implementation gravity. A sponsor may influence direction through support. A public authority participant may be overread as endorsing. The Collaboration Charter must interrupt this explicitly. Collaboration does not by itself create governance standing. Contribution does not by itself confer authorship over institutional meaning. Review does not by itself confer approval authority. Operational centrality does not by itself confer constitutional privilege. The charter does not weaken collaboration by saying this. It strengthens it. Clear boundaries make trust possible. *** ### 3.24 The Volunteers Charter The Volunteers Charter governs voluntary contribution within Nexus. Volunteer contribution can be a major source of intelligence, energy, goodwill, field knowledge, translation, civic legitimacy, and ecosystem depth. It can also become a source of hidden dependency, unfair burden, unclear attribution, weak support, role confusion, and ethical risk if it is not governed carefully. The Volunteers Charter recognizes that volunteer contribution should neither be romanticized as free surplus nor marginalized as peripheral help. If volunteer work matters, it must be governed. If it becomes load-bearing, that fact must be visible. If it requires skill, training must be provided. If it creates value, contribution should be recognized. If it creates risk, safeguards must apply. The Volunteers Charter is therefore part of the ethical and structural seriousness of Nexus Operations. *** ### 3.25 Purpose of Volunteer Pathways Volunteer pathways exist to create meaningful, bounded, protected, and recognized forms of contribution aligned with Nexus public-good purpose and operating needs. Volunteering may support research, translation, events, community science, documentation, learning, media, outreach, platform support, report assistance, data cleanup, public-safe review support, Academy activity, working group participation, or local node activity, subject to role and safeguard rules. Volunteer contribution should be useful to Nexus and meaningful to the contributor. It should not be unmanaged labor. It should not be treated as unlimited availability. It should not be used to fill essential roles without support. It should not be used to create public legitimacy without real participation. A serious volunteer pathway respects the contributor and the architecture. *** ### 3.26 Scope of Volunteer Roles The Volunteers Charter should define what volunteer roles may include and what they may not include. Volunteer roles may include bounded support, research assistance, translation, event assistance, documentation support, community engagement support, training participation, working group contribution, local knowledge support where safeguarded, platform testing, or Digital Public Good support under supervision. Volunteer roles should not include unsupervised authority over sensitive data, public-safe publication, recognition decisions, standards approval, finance-readable claims, public authority determinations, procurement influence, high-risk technical operations, or uncontrolled public speaking on behalf of Nexus. Where volunteer contribution becomes significant, recurring, specialized, sensitive, or load-bearing, it should be reviewed for transition into a more formal role, credentialed pathway, contract, staff position, fellowship, provider arrangement, or other structured status. The boundary is ethical as well as operational. *** ### 3.27 Volunteer Accountability and Support Volunteer work should have supervision, orientation, role clarity, records, support, and feedback. A volunteer should know: * what role they hold; * who supports them; * what they may do; * what they may not do; * what tools they may use; * what records they should create; * what confidentiality applies; * how their contribution will be attributed; * how they may ask questions; * how they may raise concerns; * how they may exit or transition. A system that welcomes volunteers without support is not open. It is careless. The Volunteers Charter should therefore make support a responsibility of Nexus, not a favor. *** ### 3.28 Volunteer Safeguards and Non-Exploitation Volunteer safeguards are essential. Nexus should not use mission language to obscure labor expectations, emotional burden, safety risks, community exposure, or uncompensated dependency. Volunteer safeguards should address orientation, reasonable workload, role limits, supervision, protected participation, grievance pathways, confidentiality, data handling, public-safe limits, safeguarding, anti-retaliation, accessibility, and respectful exit. Volunteers should not be pressured to perform beyond their role. Volunteers should not be asked to handle sensitive material without training and authorization. Volunteers should not be used as substitutes for qualified professional, legal, technical, public-safe, finance, procurement, or public authority roles. Volunteers should not become invisible infrastructure. The rule is: **Volunteer contribution must be meaningful, bounded, supported, and non-extractive.** *** ### 3.29 Volunteer Recognition, Learning, and Progression Volunteer contribution should be capable of becoming visible learning and recognized value. Recognition may include attribution, contribution records, learning records, Academy pathways, Integrated Learning Account entries, credits or reward systems where applicable, references, certificates of participation, progression opportunities, fellowships, role-readiness pathways, or transition into more formal contribution. Recognition should be scoped and truthful. A volunteer contribution record is not a credential unless it meets credential requirements. A volunteer role is not employment unless a proper employment relationship exists. A volunteer contribution is not governance authority. A volunteer’s public association with Nexus is not authorization to speak for Nexus beyond recorded role. Recognition should respect contribution without inflating status. *** ### 3.30 Volunteer Exit and Transition Volunteer pathways should include exit and transition rules. A volunteer should be able to leave without penalty, retaliation, or reputational harm. Their work should be closed, transferred, attributed, archived, or continued appropriately. Where appropriate, a volunteer may transition into deeper participation through membership, guilds, Academy pathways, working groups, competence cells, internships, fellowships, contracts, staff roles, provider arrangements, or other structured forms. Exit matters because unmanaged departure can create records gaps, maintenance gaps, public confusion, or contributor harm. Transition matters because serious volunteer contribution can become a pathway into durable capability. The Volunteers Charter should make both visible. *** ### 3.31 Volunteer Contribution as an Institutional Responsibility A public-good system has a special obligation to treat volunteer contribution responsibly. It must not extract energy while withholding structure. It must not use purpose language to blur labor, expectation, and recognition. It must not allow essential functions to be carried in shadow form by people without corresponding support or visibility. It must not celebrate openness while ignoring the conditions that make participation safe and meaningful. The Volunteers Charter allows Nexus to avoid those failures. It provides a way to welcome broad contribution while preserving dignity, traceability, boundaries, and progression. A resilient operating system does not merely attract participation. It knows how to hold participation responsibly. *** ### 3.32 Chartering Additional Working Modes Investigation, Collaboration, and Volunteers are the first visible chartered modes, but the charter layer should remain extensible. Additional charters may be required where a working mode becomes recurring, sensitive, public-facing, technically consequential, or operationally important. Possible future charters may include: * Working Group Charter; * Nexus Competence Cell Charter; * Public Authority Learning Charter; * Community Science Charter; * Protected Knowledge Charter; * Controlled Room Charter; * Data Stewardship Charter; * Report Production Charter; * Media Production Charter; * Forum Convening Charter; * Marketplace Review Charter; * Foundry Contribution Charter; * Studio Workflow Charter; * Node Operations Charter; * Qualified Enterprise Provider Charter; * Sponsor Support Charter; * Campaign Charter. The test is practical: if a mode of work could create confusion about scope, role, output, authority, public-safe status, attribution, safeguards, or handoff, it should be chartered. Chartering does not make work rigid. It makes work trustworthy. *** ### 3.33 Charters and Public-Safe Discipline Charters must embed public-safe discipline. Chartered work may produce outputs that later become reports, media, platform entries, dashboards, public-safe summaries, Marketplace descriptions, Foundry documentation, Studio workflows, training materials, registry entries, public authority learning materials, or campaign outputs. Each charter should therefore state when public-safe review is required. Public-safe discipline should apply where outputs may affect: * public understanding; * community safety; * protected knowledge; * public authority relationships; * market behavior; * procurement sensitivity; * security; * institutional reputation; * maturity claims; * recognition; * routeability; * finance-readable readiness. A chartered output should not become public merely because the work is complete. Completion is not publication. Publication is not recognition. Recognition is not execution. Public-safe discipline preserves these distinctions. *** ### 3.34 Charters and Validity by Record Charters must preserve validity by record. A chartered activity should produce records proportionate to its significance. Records may include intake notes, participant lists, role assignments, scope notes, meeting notes, evidence logs, source lists, version histories, output drafts, review notes, public-safe clearance records, attribution records, correction logs, handoff records, and closure records. Records do not exist for bureaucracy alone. They preserve institutional memory, attribution, accountability, correctionability, and handoff clarity. Without records, chartered activity becomes social memory. With records, chartered activity becomes operating capacity. Validity by record also protects contributors. It shows what they did, what they did not do, what role they held, and how their contribution should be understood. *** ### 3.35 Charters and Operational Handoffs Charters must define handoff pathways. A chartered investigation may hand off to a report, public-safe review, standards interpretation, GRF recognition pathway, GCRI methods process, GRA routeability review, governance escalation, or archival record. A collaboration may hand off to a joint output, maintained asset, Digital Public Good, Marketplace object, Foundry package, Studio workflow, Academy module, public-safe publication, or consortium pathway. A volunteer contribution may hand off to an output, learning record, attribution record, Academy progression, working group pathway, formal role, or archive. Handoffs should state: * what is being transferred; * who receives it; * what status it holds; * what review remains; * what reliance limits apply; * what authority is not implied; * what correction pathway applies. Handoffs are where overclaim often occurs. Charters must make them explicit. *** ### 3.36 Charters and the Public-Good / Enterprise Interface Charters are especially important where public-good work touches enterprise or execution pathways. Investigation may identify an implementation opportunity. Collaboration may involve a provider. Volunteer contribution may support a Digital Public Good later packaged through Foundry. A working group may produce materials that become Marketplace-visible. A report may support routeability or finance-readable readiness. A Studio workflow may emerge from collaborative design. A national pathway may move from public-good inquiry toward National Consortium Company or SPV structuring. These transitions are legitimate, but they must preserve the public-good / enterprise distinction. A chartered public-good process should not become a provider sales channel. A volunteer contribution should not be converted into private value without clear terms. A collaboration with a company should not become endorsement by default. A report should not become investment advice. A Marketplace pathway should not become recognition. A Foundry handoff should not become deployment authorization. Charters protect the interface by defining role, rights, outputs, attribution, licensing, public claims, and handoff limits. *** ### 3.37 Charters and Safeguards Channels Every chartered working mode should identify safeguards channels. Safeguards channels may address: * protected participation; * contributor wellbeing; * volunteer safety; * community concerns; * Indigenous and local knowledge; * sensitive geography; * data privacy; * cybersecurity; * confidentiality; * conflicts of interest; * grievance; * retaliation; * procurement sensitivity; * market sensitivity; * public authority sensitivity; * unsafe public claims. Participants should know how to raise concerns and where concerns will be handled. Safeguards should not be hidden in general policy. They should be available at the level where work occurs. This is especially important for volunteer, community, investigative, and multi-actor collaboration contexts. *** ### 3.38 Charters and External Organizations The charter layer is also a resource for external organizations. A public authority can use charters to understand how inquiry, consultation, learning, working group participation, and public-safe outputs occur without implying official adoption or lawful public action. A company can use charters to understand collaboration boundaries, provider participation, public-good / enterprise separation, attribution, licensing, and claims limits. A university can use charters to structure research collaboration, student contribution, competence cells, community engagement, and report production. A sponsor can use charters to support work without acquiring influence over claims, standards, recognition, or outputs. A community or Indigenous actor can use charters to understand safeguards, protected knowledge, consent, public-safe pathways, and correction rights. A national group can use charters to move from informal collaboration to working groups, consortium formation, and later lawful execution structures. A volunteer can use charters to understand role, rights, support, recognition, and exit. Charters make Nexus easier to join because they make participation safer and clearer. *** ### 3.39 Charter Failure Modes Nexus should be explicit about charter failure modes. **Unchartered activity** occurs when recurring or consequential work proceeds without a defined working mode. **Charter theatre** occurs when a charter exists but is ignored in practice. **Scope creep** occurs when work expands beyond its charter without review. **Role inflation** occurs when participants infer authority from involvement. **Hidden authority** occurs when repeated presence, expertise, funding, hosting, or technical control becomes de facto decision power. **Volunteer extraction** occurs when unpaid contribution becomes load-bearing without support, recognition, or transition. **Collaboration ambiguity** occurs when authorship, stewardship, or decision rights are unclear. **Investigation overclaim** occurs when inquiry is presented as determination. **Output orphaning** occurs when outputs are produced without maintenance or correction responsibility. **Safeguard bypass** occurs when work proceeds without appropriate public-safe, community, data, or participant protection. **Handoff distortion** occurs when work changes meaning as it moves to another pathway. **Public claim drift** occurs when chartered work is communicated beyond its status. Charters exist to prevent these failures by making work bounded, visible, fair, and correctable. *** ### 3.40 Final Statement on Charters Charters are the bounded working constitutions of the Nexus operating system. They give form to the major modes through which work occurs and ensure that investigation, collaboration, volunteer contribution, and future chartered working modes remain governed, fair, traceable, public-safe, and architecturally aligned. They matter because public-purpose architectures do not become serious by principle alone. They become serious when the conditions of work itself are explicit. In Nexus, charters prevent activity from becoming authority, contribution from becoming extraction, inquiry from becoming overclaim, collaboration from becoming hidden control, and output from becoming public meaning without review. They make participation safer. They make work clearer. They make outputs more trustworthy. They make handoffs more disciplined. They make correction possible. Through charters, Nexus converts working modes into institutional integrity. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.therisk.global/organization/introduction/operations/iii.-charters.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.