> 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/organization/governance/charter-us/x.-councils.md).

# X. Councils

### 219. Purpose, Constitutional Function, and Governing Rule&#x20;

#### 219.1 Purpose

Part X establishes the constitutional framework for the Helix Councils and Council Operating System of GCRI US. It governs how the Corporation structures plural participation, domain deliberation, stakeholder intelligence, expert review, council outputs, cross-council coordination, consultation, safeguards, records, controlled-room deliberation, and council accountability. It translates broad participation into disciplined institutional input without allowing participation to become corporate control, executive authority, market endorsement, regulatory standing, or informal governance.

Part X shall apply to:

a) all standing Helix Councils;\
b) any council bureau, chair, vice-chair, rapporteur, portfolio lead, or procedural officer;\
c) council committees, working parties, drafting groups, expert panels, red teams, replication teams, and special rapporteurs;\
d) council delegates, alternates, advisers, observers, invited experts, and guests;\
e) Secretariat support functions serving council operations;\
f) council output pathways, consultation processes, minutes, records, dockets, and decision packs; and\
g) all public descriptions of council participation, council outputs, council roles, and council status.

Part X is therefore the operating constitution for structured participation. It enables GCRI US to benefit from public authorities, industry operators, academia, civil society, media, communities, and Indigenous knowledge systems while preserving corporate law discipline, nonprofit integrity, anti-capture controls, safeguards, and the strict non-execution boundary.

#### 219.2 Relationship of Part X to Mission Lock, Membership Architecture, Corporate Governance, and Safeguards

Part X shall be read subject to the mission lock, nonprofit public-benefit purpose, membership architecture, Board fiduciary authority, corporate governance rules, financial controls, records discipline, conflict rules, safeguards obligations, protected participation, security requirements, public-claims controls, and non-execution boundary of GCRI US. Councils strengthen participation and intelligence. They do not weaken constitutional controls.

Accordingly, no council, bureau, committee, working party, expert panel, delegate, chair, rapporteur, or Secretariat-supported council process may:

a) bind GCRI US externally without express authority;\
b) approve Board reserved matters;\
c) create membership rights, service authority, badges, recognitions, certifications, or conformance states;\
d) grant access to restricted systems, repositories, controlled rooms, or sensitive materials outside approved access rules;\
e) represent member participation as endorsement, adoption, certification, routeability, government mandate, Indigenous consent, or market validation;\
f) conduct procurement, contracting, underwriting, lending, insurance, settlement, market operation, investment, brokerage, custody, or other execution-side activity;\
g) override safeguards, whistleblowing, protected participation, privacy, security, or records controls; or\
h) operate as an informal governance organ outside recorded mandate.

Council work shall be aligned with corporate governance. Where council recommendations require institutional adoption, they must move through the proper adoption pathway, decision pack, authority map, review gate, and record.

#### 219.3 Helix Councils as Permanent Institutional Organs of Structured Plural Participation

GCRI US may constitute Helix Councils as permanent institutional organs of structured plural participation. Their purpose is to organize the intelligence, critique, legitimacy, expertise, and practical knowledge needed for public-good work across systemic risk, resilience, sustainability, evidence, technology, policy, standards, governance, and social trust.

The Helix Council model shall recognize that no single constituency can safely define systemic risk or resilience alone. Public authorities bring lawful public-purpose context and institutional constraints. Industry and operators bring operational feasibility and infrastructure realism. Academia and research communities bring method, epistemic discipline, peer challenge, and evidence quality. Civil society and media bring public reason, transparency, accountability, and social trust. Communities and Indigenous participants bring lived context, rights-sensitive knowledge, local truth, place-based risk intelligence, and safeguards insight.

The Councils shall therefore operate as structured channels for:

a) plural intelligence;\
b) contestability;\
c) early warning;\
d) quality review;\
e) public-interest challenge;\
f) safeguards visibility;\
g) participation legitimacy;\
h) implementation realism; and\
i) institutional learning.

They shall not be symbolic advisory boards. They shall be organized, recorded, output-producing, safeguarded, and accountable deliberative organs within the GCRI US public-good architecture.

#### 219.4 Councils as Deliberative, Advisory, and Structured-Output Surfaces Rather Than Corporate Owners or Executive Authorities

Councils shall be deliberative, advisory, review, challenge, consultation, and structured-output surfaces. They shall not be corporate owners, fiduciary authorities, executive authorities, statutory member bodies, procurement bodies, delivery bodies, certification bodies, market bodies, or regulated actors.

Councils may, within recorded mandate:

a) deliberate on defined questions;\
b) review draft materials;\
c) identify risks, blind spots, and externalities;\
d) propose recommendations;\
e) produce advisory notes, warnings, method comments, participation reviews, or consultation summaries;\
f) escalate concerns to the Board, Secretariat, safeguards, integrity, legal, security, or management channels;\
g) support contestability and dissent preservation; and\
h) contribute structured inputs to adoption-ready decision packs.

Councils may not, unless expressly and lawfully authorized:

i) approve corporate strategy;\
ii) approve budgets;\
iii) bind the Corporation;\
iv) sign contracts;\
v) speak as the Corporation;\
vi) issue final institutional positions;\
vii) certify persons, institutions, products, standards, platforms, or methods;\
viii) create public-authority, regulatory, procurement, or market effect; or\
ix) replace Board, officer, executive, legal, safeguards, security, or records functions.

A council output may be influential. It is not self-executing authority.

#### 219.5 Councils as a Legitimacy, Intelligence, and Quality Architecture Within the Wider GCRI System

The Helix Councils shall function as legitimacy, intelligence, and quality architecture within the wider GCRI US system. Their value lies in disciplined plurality. They create a structured way for diverse sectors and knowledge communities to test institutional work before it hardens into public outputs, standards, programs, reports, policy positions, technical releases, or public-good infrastructure.

The Councils shall support:

a) legitimacy, by ensuring that multiple forms of knowledge and public-interest concern can be heard through recorded process;\
b) intelligence, by enabling early identification of emerging risks, institutional blind spots, implementation constraints, and stakeholder harms;\
c) quality, by exposing outputs to challenge, peer review, operational realism, social-trust review, and safeguards analysis;\
d) contestability, by preserving dissent and minority views instead of forcing artificial consensus;\
e) resilience, by preventing institutional knowledge from being concentrated in one office, discipline, donor, or technical team; and\
f) accountability, by creating traceable records of advice, warnings, responses, and unresolved disagreement.

In the GCRI US model, legitimacy is not achieved by inviting many names into a room. Legitimacy is achieved when participation is structured, safe, role-bounded, recorded, balanced, and capable of influencing institutional learning through proper authority pathways.

#### 219.6 Binding Effect of Part X Across All Councils, Bureaus, Committees, Working Parties, Expert Bodies, and Secretariat Support Functions

Part X shall bind every Helix Council, bureau, committee, working party, drafting group, expert mechanism, review body, consultation process, Secretariat support function, and council-related participant operating under GCRI US authority or public description. No council-related body may avoid this Part by calling itself informal, exploratory, thematic, temporary, expert-led, community-led, technical, public, confidential, implementation-focused, or external-facing where it performs a council-like function for GCRI US.

The binding effect includes:

a) constituting instruments;\
b) membership and seat allocation;\
c) delegate authority;\
d) meeting procedures;\
e) voting, consensus, dissent, and quorum rules;\
f) bureau and procedural leadership;\
g) working-party mandates;\
h) expert review mechanisms;\
i) Secretariat docketing and forms-first operations;\
j) consultation and comment-handling;\
k) records, minutes, Gazette or notice integration;\
l) controlled-room deliberation;\
m) competition safety, anti-capture, and conflict controls;\
n) performance governance;\
o) lifecycle review and reconstitution; and\
p) public description of council outputs and authority.

Any body that functions like a council shall be brought within the discipline of Part X or shall be prohibited from representing itself as part of GCRI US council architecture.

#### 219.7 Governing Rule of Part X

The governing rule of Part X is as follows: GCRI US Councils exist to structure plural participation, deliberation, challenge, consultation, and expert input through recorded, safeguarded, competition-safe, role-bounded, and forms-first processes, without creating corporate ownership, fiduciary authority, executive authority, regulated execution, public-authority mandate, certification, endorsement, or hidden institutional effect.

Accordingly:

a) council authority must be written and scoped;\
b) council outputs must be classified and effect-coded;\
c) council participants must act within role and mandate;\
d) council records must be complete enough for institutional reliance;\
e) dissent and minority views must be preserved where material;\
f) conflicts, competition sensitivity, and capture risks must be controlled;\
g) public descriptions must not overstate council effect;\
h) adoption-ready outputs must pass required review gates; and\
i) ambiguity resolves toward narrower council authority and stronger participation protection.

#### 219.8 Interpretive Rule for Purpose, Constitutional Function, and Governing Rule of Part X

This Section shall be interpreted to preserve a controlling proposition: Part X enables GCRI US to institutionalize plural participation through Helix Councils while preserving corporate governance, fiduciary authority, records validity, safeguards, anti-capture discipline, non-execution boundaries, and truthful public meaning.

Where ambiguity exists, the interpretation that better preserves council role-bounding, Board primacy, safe participation, deliberative quality, public-interest legitimacy, controlled outputs, records-first operation, competition safety, and non-substitution for corporate authority shall prevail unless a contrary result is required by law.

### 220. Foundational Council Doctrine (GCRI United States)

#### 220.1 Councils Exist to Structure Plural Participation Without Role Collapse

The Helix Councils of GCRI US shall exist to structure plural participation without collapsing roles, authorities, mandates, legal capacities, or institutional responsibilities. They are designed to bring multiple forms of knowledge into disciplined institutional deliberation while ensuring that each participant remains within the capacity in which they are admitted, seated, heard, recorded, and relied upon.

Council participation shall therefore be structured around clear role distinction. A public authority participant may provide public-sector perspective but shall not be treated as binding the government or agency they are associated with unless a separate lawful mandate exists. An industry participant may provide operational realism but shall not receive procurement advantage or product endorsement. An academic participant may provide methodological critique but shall not create conclusive institutional validation by presence alone. A civil-society or media participant may provide public-interest scrutiny and communications insight but shall not convert the Council into a political advocacy platform. A community or Indigenous participant may provide rights-sensitive, lived-context, place-based, or community-relevant knowledge but shall not be instrumentalized as universal consent, representation, or approval beyond the recorded scope of participation.

The Council system shall prevent role collapse by requiring:

a) recorded mandates for each Council;\
b) clear participant categories;\
c) defined speech, proposal, drafting, review, and voting rights;\
d) controlled output vocabulary;\
e) publication-class discipline;\
f) conflict, recusal, and safeguards controls;\
g) clear routing of Council outputs to the proper authority; and\
h) public-description rules preventing overclaim.

This doctrine is central to GCRI US because the Corporation operates in fields where expertise, power, money, public authority, technology, social trust, and community harm can intersect. The Councils allow these perspectives to meet without allowing any one perspective to absorb the others or convert deliberation into control.

#### 220.2 Councils Are Distinct From the Board, Secretariat, Executive Management, and External Networks

The Helix Councils shall remain distinct from the Board, the Secretariat, executive management, committees of the Board, membership authority, governance-spine functions, technical teams, program teams, public campaigns, and external networks. A Council may interact with these surfaces, but it shall not become any of them.

The Board is the fiduciary authority. The Secretariat supports process, docketing, records, notices, and validity. Executive management operates within delegated authority. Governance-spine functions protect records, safeguards, finance, security, compliance, and integrity. Councils provide structured deliberation, review, challenge, consultation, and plural intelligence. Each function has a separate constitutional role.

Accordingly:

a) a Council recommendation shall not substitute for Board approval;\
b) Secretariat preparation shall not substitute for Council deliberation;\
c) management preference shall not control Council outputs;\
d) Council participation shall not create membership rights unless separately granted;\
e) a Council chair shall not become an officer of the Corporation unless separately appointed;\
f) an external network shall not be represented as a Council unless formally constituted; and\
g) Council outputs shall not become institutional positions unless adopted through the required pathway.

This separation shall be especially important where GCRI US collaborates with GCRI Canada, GRF, GRA, protocol authorities, host institutions, universities, public authorities, donors, and technical communities. Cross-institutional alignment may strengthen mission delivery, but it shall not erase the distinction between deliberative participation and corporate authority.

#### 220.3 Councils Are Institutional Deliberation Surfaces, Not Informal Communities of Interest

The Councils shall be institutional deliberation surfaces. They are not informal communities of interest, social networks, stakeholder clubs, donor salons, reputation circles, open discussion groups, or unrecorded advisory communities. Council deliberation shall occur through a recorded mandate, a defined docket, a constituted membership or participant list, approved procedure, classified materials, minutes, outputs, and closure records.

This means that Council work shall have institutional discipline. A Council item shall identify:

a) the question before the Council;\
b) the Council or Councils competent to consider it;\
c) the materials provided;\
d) the classification and handling requirements;\
e) the expected output type;\
f) the decision clock or consultation period;\
g) the conflict and recusal rules;\
h) the record owner; and\
i) the route by which the output may be escalated, adopted, archived, or closed.

Informal conversation may help develop ideas, but it shall not be represented as Council action. If a matter is intended to have Council effect, it must enter the Council Operating System. No person may later characterize an informal discussion as a Council position, Council warning, Council approval, Council endorsement, or Council consensus unless the applicable records support that characterization.

#### 220.4 Councils Do Not Replace Scientific Method, Safeguards Review, or Fiduciary Governance

The Councils shall not replace scientific method, safeguards review, legal review, fiduciary governance, financial controls, security review, privacy review, publication review, or executive accountability. They may contribute to these processes, improve their quality, identify gaps, and challenge assumptions, but they do not become substitutes for the competent functions.

In the GCRI US model, this rule has practical effect:

a) an Academia and Research Council comment may strengthen methodology, but it does not replace formal research governance, peer review, reproducibility checks, or evidence-quality controls;\
b) a Community and Indigenous Council discussion may identify rights-sensitive concerns, but it does not replace safeguards review, consent protocols, grievance channels, or protected-participation procedures;\
c) an Industry and Operators Council feasibility note may improve implementation realism, but it does not replace procurement controls, vendor due diligence, or security review;\
d) a Public Authorities Council discussion may clarify public-sector constraints, but it does not replace lawful public authority, legal mandate, or regulatory decision-making;\
e) a Civil Society and Media Council review may strengthen legibility and transparency, but it does not replace communications approval, public-claims control, or Board adoption; and\
f) a cross-council concurrence note may support institutional learning, but it does not replace Board approval where a matter is reserved.

Councils are powerful because they generate structured inputs. They become dangerous if their inputs are overclaimed as final authority. GCRI US shall therefore maintain a clear distinction between deliberative input, technical review, safeguards review, fiduciary decision, and institutional adoption.

#### 220.5 Councils Do Not Confer Recognition, Routeability, Regulatory Standing, or Execution Authority

Council participation, Council review, Council attendance, Council contribution, Council membership, Council chairing, or Council output shall not confer recognition, routeability, regulatory standing, certification, accreditation, public authority, procurement preference, market validation, investment readiness, insurance readiness, execution authority, or endorsement by GCRI US.

No participant may state or imply that because they participated in a Council:

a) their institution, product, method, platform, service, model, policy, or project is approved by GCRI US;\
b) they are preferred for procurement, partnership, funding, or implementation;\
c) they have achieved conformance, certification, recognition, or routeability;\
d) a regulator, government, Indigenous institution, public authority, university, community, or media body has endorsed them;\
e) they have access to execution-side opportunities; or\
f) they are authorized to speak for GCRI US.

Council outputs shall carry effect statements. A Council note may say that a topic was discussed, reviewed, challenged, recommended, or escalated. It shall not state or imply institutional recognition unless an entirely separate authority has lawfully granted that effect and the record supports it.

This rule protects GCRI US from reputational laundering, market misuse, donor overclaim, vendor capture, and public misunderstanding.

#### 220.6 Councils Must Remain Competition-Safe, Rights-Respecting, and Public-Interest Aligned

All Council activity shall remain competition-safe, rights-respecting, and public-interest aligned. Councils may bring together actors from sectors that normally compete, regulate, report on, fund, critique, or serve one another. That makes Council design valuable, but it also creates risk.

Competition-safe operation shall prohibit:

a) price coordination;\
b) market allocation;\
c) bid coordination;\
d) vendor exclusion;\
e) competitively sensitive information exchange;\
f) procurement signaling;\
g) preferential treatment of member firms;\
h) coordinated lobbying through improper channels; and\
i) use of Council access for commercial advantage.

Rights-respecting operation shall require:

i) protected participation;\
ii) safe handling of sensitive identity and community information;\
iii) non-retaliation;\
iv) dignity in deliberation;\
v) avoidance of extractive participation;\
vi) safeguards review for rights-bearing issues;\
vii) accessibility and inclusion; and\
viii) respect for Indigenous, community, and local-context boundaries.

Public-interest alignment shall require Councils to remain focused on mission, evidence, resilience, risk governance, sustainability, public-good infrastructure, and institutional learning. Councils shall not become platforms for private positioning, partisan messaging, vendor marketing, public relations, donor influence, or sectoral bargaining.

#### 220.7 Most-Restrictive Reading Where Council Activity Could Be Misread as Binding External Authority or Hidden Execution

Where Council activity could reasonably be misread as binding external authority, public mandate, government position, Indigenous consent, certification, market validation, procurement preference, routeability, or execution-side commitment, the most-restrictive reading shall apply until the competent authority clarifies the matter.

This rule shall apply where ambiguity exists concerning:

a) whether a Council output is advisory or adopted;\
b) whether a Council participant speaks personally, institutionally, or officially;\
c) whether a Council recommendation has been approved by the Board;\
d) whether a public authority participant has mandate to bind an agency;\
e) whether a community or Indigenous participant is speaking for a wider collective;\
f) whether a technical review implies certification;\
g) whether an industry feasibility comment implies vendor preference;\
h) whether a cross-council note implies institutional consensus;\
i) whether a Council process creates public reliance; and\
j) whether Council work is drifting toward regulated execution.

In each case, GCRI US shall narrow the claim, add disclaimers, route the matter for review, hold publication, revise the output type, or require formal adoption before any stronger claim is made.

#### 220.8 Councils Must Preserve Contestability, Not Manufacture Consensus

Councils shall preserve contestability. Their function is not to manufacture neat consensus for public narrative. Their function is to make institutional thinking stronger by exposing it to informed disagreement, methodological challenge, operational friction, rights-sensitive concern, and public-interest scrutiny.

Consensus may be useful where it emerges honestly. It shall not be forced. A Council process that suppresses dissent in order to present alignment undermines the purpose of the Helix model.

The Council system shall therefore allow:

a) dissent notes;\
b) minority reports;\
c) unresolved-issue registers;\
d) method-challenge notes;\
e) safeguards objections;\
f) public-interest warnings;\
g) competing interpretations; and\
h) escalation of unresolved disagreement.

Dissent shall be disciplined, relevant, respectful, and classified appropriately. It shall not be used for obstruction, personal attack, disclosure of restricted information, or reputational harm. But principled disagreement must remain visible to the institution.

#### 220.9 Councils Must Operate Through Forms-First and Records-First Discipline

Council activity shall operate through forms-first and records-first discipline. No material Council action shall rely solely on email chains, meeting memory, informal calls, chat threads, personal notes, or undocumented understanding. Material Council work must be docketed, classified, assigned, reviewed, recorded, and closed.

The Council Operating System shall support:

a) intake forms;\
b) case IDs;\
c) matter classification;\
d) Council assignment;\
e) participant and conflict checks;\
f) meeting notices;\
g) agendas;\
h) minutes;\
i) output templates;\
j) consultation logs;\
k) dissent capture;\
l) decision packs;\
m) escalation records; and\
n) closure memoranda.

Records-first discipline allows the Corporation to know what Councils actually considered, what they recommended, what they did not decide, what risks were identified, and what adoption pathway remains required. Without records, Council legitimacy becomes unverifiable.

#### 220.10 Councils Must Remain Balanced Against Capture, Symbolism, and Tokenism

Councils shall be designed to resist capture, symbolism, and tokenism. Capture occurs when one constituency, funder, sector, vendor, public authority, technical community, or personality dominates Council work. Symbolism occurs when Council existence is used for legitimacy without meaningful deliberation. Tokenism occurs when participants, especially community, Indigenous, civil-society, youth, or under-resourced actors, are included for appearance but not protected, heard, resourced, or reflected in outputs.

GCRI US shall therefore monitor:

a) seat concentration;\
b) repeated dominance of agenda or outputs;\
c) donor or sponsor influence;\
d) vendor or industry bloc behavior;\
e) public-authority overclaim;\
f) underrepresentation of affected communities;\
g) participation barriers;\
h) failure to record dissent;\
i) patterns of ignored comments; and\
j) Council outputs that systematically favor one constituency.

Corrective measures may include seat recalibration, rotation, chair replacement, facilitation reform, safeguards intervention, consultation redesign, funding support for under-resourced participants, public-description correction, or suspension and reconstitution of a Council.

#### 220.11 Councils Must Support the GCRI US Public-Good and Nexus-Aligned Operating Model Without Becoming Execution Infrastructure

The Councils may support GCRI US’s public-good and Nexus-aligned operating model by strengthening evidence quality, standards literacy, public-interest legitimacy, resilience intelligence, technical realism, and rights-sensitive governance. They may help identify risks, refine methods, test assumptions, improve consultation, and make outputs more robust.

However, Councils shall not become execution infrastructure. They shall not route transactions, allocate capital, choose vendors, approve financial products, certify insurance or investment readiness, control procurement, endorse technologies, or operate as market committees. Any finance-adjacent or implementation-adjacent discussion shall be carefully framed as public-good learning, standards input, evidence-quality review, or policy consultation, not execution.

Where Council work touches the Nexus evidence-to-capital environment, the record shall state:

a) the Council’s role is advisory or review-based;\
b) GCRI US does not execute regulated transactions;\
c) downstream delivery, if any, is outside GCRI US and subject to separate lawful actors;\
d) no Council output creates routeability or investability by itself; and\
e) any adoption, recognition, certification, or external effect requires separate authority.

This rule preserves the public-good value of Council deliberation while protecting the Corporation from regulated-perimeter confusion.

#### 220.12 Interpretive Rule for Foundational Council Doctrine

This Section shall be interpreted to preserve a controlling proposition: the Helix Councils of GCRI US are structured, safeguarded, competition-safe, records-based deliberation organs that generate plural intelligence, challenge, legitimacy, and quality inputs without collapsing roles, replacing fiduciary governance, conferring recognition, creating execution authority, or manufacturing false consensus.

Where ambiguity exists, the interpretation that better preserves:

a) role distinction;\
b) Board and officer authority;\
c) Council mandate discipline;\
d) safeguards and protected participation;\
e) competition safety;\
f) public-interest alignment;\
g) dissent preservation;\
h) forms-first and records-first operation;\
i) anti-capture and anti-tokenism controls; and\
j) non-execution public-good boundaries

shall prevail unless a contrary result is required by law.

### 221. Constitution of the Helix Council System (GCRI United States)

#### 221.1 Establishment of the Helix Council System as a Standing Governance Architecture

GCRI US may establish the Helix Council System as a standing governance architecture for structured plural participation, deliberation, consultation, challenge, review, and institutional learning. The Helix Council System shall be constituted as part of the Corporation’s public-benefit operating model, not as an informal stakeholder network, promotional advisory board, donor-facing council, or prestige roster.

The Helix Council System shall be designed to give GCRI US a disciplined way to receive, test, organize, and preserve knowledge from multiple institutional and social vantage points. It shall support the Corporation’s work on systemic risk, resilience, sustainability, evidence quality, technology governance, public-good infrastructure, risk intelligence, standards literacy, and cross-sector coordination.

The Helix Council System shall operate as a standing architecture only where it is formally created by Board-approved instrument, bylaw schedule, Council Charter, or other recorded authority. The establishment instrument shall identify:

a) the Council system’s purpose;\
b) the Councils initially constituted;\
c) the authority under which they are established;\
d) their relationship to the Board, officers, Secretariat, management, membership architecture, and governance-spine functions;\
e) their permitted outputs;\
f) their prohibited acts;\
g) their records and publication rules;\
h) their safeguards and competition controls;\
i) their review cycle; and\
j) the process for amendment, suspension, reconstitution, or dissolution.

The Helix Council System shall not be treated as separate from corporate governance. It shall be a controlled participation layer operating within corporate governance.

#### 221.2 Councils as Institutional Rather Than Personal Bodies

Each Helix Council shall be constituted as an institutional body of GCRI US, not as a personal circle of a founder, officer, trustee, executive, chair, donor, sponsor, partner, or public figure. Council legitimacy shall arise from recorded mandate, balanced composition, clear procedure, protected participation, quality of deliberation, and faithful records, not from the personal stature of participants alone.

This rule shall apply in several ways:

a) Council seats shall be created by institutional design, not personal invitation alone;\
b) Council participation shall be linked to role, class, expertise, mandate, or institutional contribution, not personal proximity;\
c) Council chairs and bureau members shall hold procedural authority only within recorded scope;\
d) Council records shall be held by the Corporation, not by individual conveners;\
e) Council outputs shall belong to the relevant institutional process, subject to publication and records rules; and\
f) Council continuity shall not depend on one person’s relationships, memory, or private files.

A distinguished participant may enrich a Council. They shall not own it. A founding convener may help create the Council. They shall not personally control its authority. A donor may support Council operations. They shall not determine Council agenda, membership, outputs, or conclusions.

The institutional nature of Councils is essential for GCRI US because the Corporation’s public-good role requires continuity beyond personalities.

#### 221.3 Councils as Multi-Stakeholder but Role-Bounded Organs

The Helix Councils shall be multi-stakeholder organs, but every participant shall remain role-bounded. Multi-stakeholder design does not mean open-ended authority, merged identities, informal consensus, or unlimited representation. It means that diverse institutional and knowledge communities are structured into a disciplined system where each contribution is heard within its proper capacity.

Role-bounding shall require clear distinctions among:

a) Council members;\
b) institutional delegates;\
c) alternates and deputies;\
d) advisers and technical experts;\
e) observers;\
f) invited guests;\
g) rapporteurs;\
h) Secretariat support persons;\
i) Board or officer liaisons; and\
j) external reviewers.

Each role shall specify whether the person may attend, speak, submit comments, propose text, draft outputs, vote where applicable, join a working party, access restricted materials, receive controlled-room information, or be publicly named.

Role-bounded multi-stakeholder design shall protect the Corporation from three risks:

a) authority inflation, where participants assume rights beyond their role;\
b) representation overclaim, where one person is treated as speaking for an institution, public authority, community, or constituency beyond mandate; and\
c) capture, where powerful actors use the appearance of multi-stakeholder process to control outcomes.

The Council system shall be plural, but not uncontrolled.

#### 221.4 Formal Constituting Instruments and Their Required Minimum Contents

Each Helix Council shall be established through a formal constituting instrument or Council Charter. No Council shall exist merely because meetings have occurred, a name has been used, a public page has been created, or participants have been invited.

A Council constituting instrument shall include, at minimum:

a) Council name and short code;\
b) purpose and constitutional position;\
c) authority source;\
d) scope of deliberation;\
e) matters excluded from Council authority;\
f) relationship to Board, officers, Secretariat, management, membership, and governance-spine functions;\
g) participant categories and eligibility;\
h) seat allocation and balance rules;\
i) term, renewal, rotation, and vacancy rules;\
j) bureau or procedural leadership structure;\
k) meeting, quorum, voting, consensus, and dissent rules;\
l) output taxonomy and effect coding;\
m) consultation and comment-handling rules;\
n) conflict, recusal, competition, and anti-capture controls;\
o) safeguards, protected participation, and non-retaliation rules;\
p) security, privacy, controlled-room, and publication-class rules;\
q) records, minutes, case ID, repository, and Gazette or notice-linkage rules;\
r) escalation pathways;\
s) performance review and annual reporting duties; and\
t) amendment, suspension, reconstitution, sunset, or dissolution procedure.

The constituting instrument shall be written in precise language. It shall not use vague phrases such as “advisory authority,” “strategic leadership,” “recognition platform,” or “official partner council” without defining the legal and institutional effect.

#### 221.5 No Council Exists Without Recorded Constitution, Mandate, and Scope

No Council shall exist, operate, convene, publish, advise, deliberate, or be publicly described as a GCRI US Council unless it has a recorded constitution, mandate, and scope. A Council name shall not be used in public materials until the relevant authority has approved the Council’s constitution or interim charter.

Where a body is being explored before formal constitution, it shall be described only as a scoping group, preparatory group, consultation group, or proposed Council, and the public-description language shall avoid implying current constitutional status.

A valid Council record shall identify:

a) date of constitution;\
b) approving authority;\
c) current charter version;\
d) Council scope;\
e) seat structure;\
f) leadership structure;\
g) participants or initial recruitment process;\
h) Secretariat support;\
i) records repository;\
j) first review date; and\
k) public-description status.

If a Council’s mandate expires, is suspended, or is superseded, it shall cease acting unless reconstituted. Stale Council names shall be removed from public and internal operational use.

#### 221.6 No Shadow Councils, Unrecorded Taskforces, or Parallel Deliberative Bodies With Implied Authority

GCRI US shall prohibit shadow Councils, unrecorded taskforces, informal expert circles, donor working groups, founder-led advisory loops, closed messaging groups, or parallel deliberative bodies that claim, imply, or exercise Council-like authority without constitution under Part X.

A shadow Council may exist where:

a) a group repeatedly reviews institutional outputs without mandate;\
b) a donor or sponsor group influences Council agenda outside records;\
c) technical experts make Council-style determinations without charter;\
d) informal calls are described as Council consensus;\
e) external partners are treated as a standing advisory body without approval;\
f) program staff create a “council” label for legitimacy; or\
g) public materials imply structured participation where no formal body exists.

Such bodies shall either be formally constituted, reclassified as informal input with no Council status, or discontinued. GCRI US shall not permit hidden participation structures to influence public-good outputs without records, safeguards, conflict checks, and authority limits.

#### 221.7 Council Acts Valid Only Within Recorded Mandate, Procedure, and Classification Rules

A Council act shall be valid only where it is within the Council’s recorded mandate, follows required procedure, observes classification rules, and is recorded in the Council Operating System. A Council act outside mandate shall have no institutional effect unless separately adopted through competent authority.

A valid Council act requires:

a) a matter properly docketed or admitted;\
b) correct Council assignment;\
c) required participant eligibility and quorum, where applicable;\
d) conflict and recusal controls;\
e) competition and handling controls;\
f) proper notice and agenda;\
g) minutes or record of deliberation;\
h) output type assigned under controlled vocabulary;\
i) effect statement;\
j) dissent or minority views preserved where material;\
k) escalation or adoption route identified; and\
l) closure record.

Council action shall not be valid if it relies on private notes, unclassified materials, undisclosed conflicts, improper participant dominance, unrecorded consensus, or output language exceeding Council authority.

#### 221.8 Council System as a Structured Intelligence and Challenge Layer for GCRI US Outputs

The Council System shall function as a structured intelligence and challenge layer for GCRI US outputs. Its role is to make institutional outputs stronger, more legitimate, more realistic, more rights-aware, and more publicly understandable before they are adopted, published, escalated, or archived.

Council input may improve:

a) risk assessments;\
b) public-good standards;\
c) research agendas;\
d) evidence frameworks;\
e) consultation papers;\
f) public narratives;\
g) policy positions;\
h) safeguards protocols;\
i) technical architectures;\
j) membership and participation models;\
k) national or regional engagement strategies; and\
l) Nexus-aligned public-good infrastructure.

Council input shall be structured as input. It shall not become final institutional output unless the adoption process says so. Where a Council contribution is incorporated into a report, standard, policy, or public statement, the final output shall identify the adoption authority, not merely the Council that contributed.

#### 221.9 Formal Relationship Between Councils and the Council Operating System

The Helix Council System shall operate through a Council Operating System that provides the procedural infrastructure for intake, docketing, classification, agenda formation, meeting management, consultation, comment handling, output drafting, dissent capture, escalation, records, and closure.

The Council Operating System shall ensure:

a) no material Council act occurs without a case ID;\
b) each matter has a classification and handling state;\
c) each matter has a responsible Council or cross-Council route;\
d) conflicts are identified early;\
e) decision clocks and consultation windows are tracked;\
f) outputs use standardized forms and vocabulary;\
g) dissent, uncertainty, and limitations are recorded;\
h) escalation routes are clear;\
i) Council records link to corporate records where needed; and\
j) closed matters are archived with final status.

This operating system shall prevent Council work from becoming dispersed across emails, chats, meeting memory, and untracked documents. It shall make Council legitimacy auditable.

#### 221.10 Council Constitution and the GCRI US Public-Good Model

The constitution of Councils shall reflect the GCRI US public-good model. GCRI US is not creating Councils merely to show stakeholder engagement. It is creating a structured civic, scientific, operational, public-sector, and community intelligence architecture capable of improving resilience governance and evidence quality.

Therefore, Council constitution shall be guided by:

a) public-benefit purpose;\
b) plural knowledge systems;\
c) independence from capture;\
d) safeguards and protected participation;\
e) correctionability;\
f) transparency with controlled handling;\
g) institutional learning;\
h) cross-sector legitimacy;\
i) non-execution discipline; and\
j) fidelity to GCRI US’s nonprofit status.

In the Nexus-aligned environment, Councils may discuss issues connected to risk intelligence, evidence rails, standards, resilience finance interfaces, public-good technology, and national-system readiness. But Council constitution shall make clear that Councils do not execute finance, allocate capital, certify market instruments, or operate delivery stacks. They strengthen public-good intelligence and governance.

#### 221.11 Council Constitution Review, Activation, and Staged Implementation

The Board may authorize staged implementation of the Helix Council System. A Council may move through scoping, provisional constitution, pilot operation, full activation, review, redesign, suspension, or sunset. Each stage shall be recorded and publicly described accurately.

A staged implementation model may include:

a) Scoping Stage, where purpose, seat design, safeguards, and mandate are tested;\
b) Provisional Stage, where a time-bound charter permits limited deliberation and recruitment;\
c) Pilot Stage, where procedures, forms, and outputs are tested on selected dockets;\
d) Activation Stage, where the Council becomes a standing organ under full charter;\
e) Review Stage, where performance, composition, and mandate are assessed;\
f) Redesign Stage, where scope, seats, procedures, or outputs are revised; and\
g) Sunset Stage, where the Council is dissolved, merged, or suspended with records preserved.

During provisional or pilot stages, public claims shall be especially careful. A pilot Council shall not be described as fully constituted unless that is true. A scoping group shall not be described as a Council.

#### 221.12 Interpretive Rule for Constitution of the Helix Council System

This Section shall be interpreted to preserve a controlling proposition: the Helix Council System of GCRI US exists only through recorded constitution, mandate, scope, participant rules, procedures, safeguards, records, and operating-system discipline, and no Council-like body may claim authority, legitimacy, or institutional effect outside those controls.

Where ambiguity exists, the interpretation that better preserves:

a) formal Council establishment;\
b) institutional rather than personal Council identity;\
c) role-bounded multi-stakeholder participation;\
d) mandatory Council charters;\
e) no shadow Councils;\
f) mandate-limited validity;\
g) structured intelligence and challenge functions;\
h) Council Operating System discipline;\
i) public-good and non-execution alignment; and\
j) staged activation with accurate public description

shall prevail unless a contrary result is required by law.

### 222. Role of Helix Councils Within GCRI United States

#### 222.1 Councils as Deliberative and Generative Bodies for Public-Interest Intelligence and Institutional Learning

The Helix Councils shall operate as deliberative and generative bodies for public-interest intelligence and institutional learning within GCRI US. Their role is to help the Corporation understand complex risk, resilience, sustainability, governance, technology, evidence, social trust, and implementation questions through structured participation by multiple knowledge communities. The Council system shall therefore be designed to generate better institutional judgment, not to decorate decisions already made.

The Councils shall support GCRI US by:

a) identifying emerging risks, blind spots, weak signals, externalities, and second-order effects;\
b) testing assumptions embedded in research, standards, policy, technical, membership, and public-good infrastructure work;\
c) surfacing practical constraints that may not be visible from the Board, Secretariat, technical teams, or executive management alone;\
d) providing structured challenge before outputs are finalized;\
e) preserving dissent, uncertainty, and alternative interpretations;\
f) strengthening the legitimacy of public-benefit work through accountable participation; and\
g) converting fragmented stakeholder knowledge into traceable institutional learning.

For GCRI US, Councils shall be especially important because the Corporation’s work sits at the intersection of global risk, public-good infrastructure, AI-enabled intelligence, resilience finance interfaces, climate and systemic shocks, standards development, and institutional trust. No single discipline or constituency can safely govern that complexity alone. The Councils shall therefore function as the Corporation’s structured listening, challenge, and learning architecture.

#### 222.2 Councils as Quality and Legitimacy Inputs to GCRI US Outputs

The Councils shall serve as quality and legitimacy inputs to GCRI US outputs. They may review, challenge, refine, and strengthen draft outputs, including research notes, policy papers, standards proposals, consultation submissions, public-good frameworks, technical concepts, capacity-building materials, risk taxonomies, safeguards procedures, membership models, and Nexus-aligned public-good instruments.

Council input may improve output quality by ensuring that:

a) evidence is not overstated;\
b) uncertainty is disclosed;\
c) technical feasibility is tested;\
d) affected communities are not ignored;\
e) public-sector constraints are understood;\
f) civil-society and media legibility concerns are addressed;\
g) operator realities are reflected;\
h) methodological weaknesses are challenged;\
i) safeguards and rights implications are examined; and\
j) public claims remain accurate and bounded.

Council input may improve legitimacy by ensuring that outputs are not developed solely through internal staff, technical experts, donors, or leadership circles. However, Council involvement shall not itself make an output final, adopted, endorsed, certified, or binding. A Council may strengthen an output’s evidentiary and participatory basis, but final institutional adoption shall occur only through the competent authority and recorded process.

#### 222.3 Councils as Structured Surfaces for Domain Knowledge, Contestability, and Challenge

The Helix Councils shall provide structured surfaces for domain knowledge, contestability, and challenge. Each Council shall bring a distinct form of institutional intelligence to GCRI US:

a) public-authority intelligence concerning governance feasibility, public-sector constraints, administrative law sensitivity, sovereignty, public finance, regulatory perception, and institutional adoption pathways;\
b) industry and operator intelligence concerning operational feasibility, infrastructure constraints, deployment realism, security, reliability, cost, supportability, procurement risks, and implementation dependencies;\
c) academic and research intelligence concerning method, evidence quality, reproducibility, epistemic uncertainty, peer review, conceptual clarity, and intellectual integrity;\
d) civil-society and media intelligence concerning transparency, public trust, accountability, narrative risk, social legitimacy, rights, and public reason; and\
e) community and Indigenous intelligence concerning lived context, place-based risk, rights-sensitive knowledge, local legitimacy, dignity, consent boundaries, and safeguards.

Contestability shall be a design principle. Council participants shall be permitted and expected to ask difficult questions, identify weak assumptions, challenge premature conclusions, and record unresolved concerns. GCRI US shall not use Councils merely to validate internal preferences. A Council process that only confirms what leadership already believes shall be considered weak.

#### 222.4 Councils as Participation and Consultation Engines Under Formal Governance Discipline

The Councils shall function as participation and consultation engines under formal governance discipline. They may support consultation on draft outputs, policy positions, standards, frameworks, public-benefit programs, safeguards procedures, technical architectures, and membership or ecosystem designs. Such consultation shall be structured, time-bounded, accessible, recorded, and capable of producing clear disposition of comments.

Council-supported consultation shall include:

a) clear consultation question;\
b) defined participant group;\
c) accessible consultation materials;\
d) classification and handling rules;\
e) submission channels;\
f) comment log;\
g) disposition of comments;\
h) dissent or unresolved-issue capture;\
i) safeguards review where participation risk exists; and\
j) closure note or consultation summary.

The Councils shall not conduct open-ended consultation without purpose or record. Consultation shall not become performative. Where GCRI US asks for input, it shall record what was received, how it was considered, what was accepted, what was rejected, and why. This is essential for institutional trust.

#### 222.5 Councils as Early Warning, Risk-Sensing, and Escalation Surfaces Where Appropriate

The Councils may serve as early warning, risk-sensing, and escalation surfaces where appropriate. Because Council participants may sit closer to public systems, infrastructure operations, research communities, civil society, media, local communities, or affected populations, they may detect risks before they appear in formal Board reports or management dashboards.

Councils may identify and escalate:

a) emerging systemic risks;\
b) public-trust concerns;\
c) safeguards or participation harms;\
d) evidence-quality weaknesses;\
e) implementation constraints;\
f) public-authority sensitivities;\
g) security, privacy, or data-governance concerns;\
h) donor, sponsor, vendor, or sector capture signals;\
i) public-claims overreach;\
j) community or Indigenous concerns; and\
k) non-execution boundary drift.

Escalation shall follow defined routes. Councils shall not attempt to solve every issue themselves. A Council may route a concern to the Board, relevant committee, Secretariat, safeguards function, integrity function, security function, legal review, management, or another Council. The record shall identify what was escalated, why, to whom, and what follow-up is required.

#### 222.6 Councils as Distinct From Delivery, Execution, Procurement, or Market Operations

The Councils shall remain distinct from delivery, execution, procurement, market operations, regulated financial activity, and commercial implementation. They may discuss feasibility, risks, standards, evidence, governance, public-benefit design, and implementation constraints. They shall not select vendors, allocate contracts, approve financial instruments, certify platforms, route transactions, endorse procurement outcomes, or operate delivery systems.

This distinction is especially important for the GCRI US model because the Corporation may engage in work that is adjacent to resilience finance, development finance, risk evidence, insurance and capital-market concepts, public-sector readiness, and Nexus-aligned evidence-to-capital infrastructure. Council discussions in these areas shall remain public-good, governance, standards, evidence, and learning functions.

A Council shall not:

a) recommend a vendor as preferred supplier;\
b) approve a financial product or transaction;\
c) determine eligibility for capital, insurance, guarantees, or procurement;\
d) provide investment, insurance, legal, or regulatory advice;\
e) grant execution authority to any participant;\
f) convert operational feasibility review into procurement scoring; or\
g) allow members to use Council participation for commercial advantage.

Where Council discussion touches commercially sensitive or market-adjacent matters, competition-safe and non-execution controls shall apply.

#### 222.7 Councils as Inputs to Institutional Outputs, Not Self-Grounding Authorities

Council outputs shall be inputs to institutional outputs, not self-grounding authorities. A Council may produce a recommendation, warning, consultation summary, technical note, method challenge, dissent statement, feasibility review, safeguards note, or public-interest memorandum. Such outputs shall have only the effect assigned to them by the Council Charter and output taxonomy.

A Council output shall not become:

a) a Board decision;\
b) a corporate policy;\
c) a public institutional position;\
d) a certification;\
e) a recognition;\
f) a member right;\
g) a procurement determination;\
h) a regulatory or government statement;\
i) a routeability decision; or\
j) an execution mandate.

Where a Council output is intended to support adoption, it shall be included in an adoption-ready decision pack with authority mapping, evidence lineage, uncertainty statement, safeguards review, public-claims boundary, dissent record, and required approvals. Until adoption occurs, it remains a Council output with bounded effect.

#### 222.8 Councils as Corrective Intelligence Against Internal Overconfidence

The Councils shall serve as corrective intelligence against internal overconfidence. Institutions working on high-ambition public-good systems can become vulnerable to internal language, technical enthusiasm, donor pressure, founder conviction, strategic urgency, and narrative momentum. The Council system shall counterbalance that tendency by bringing structured external and plural challenge into the Corporation.

Councils shall be encouraged to ask:

a) What assumptions are not proven?\
b) Who may be harmed or excluded?\
c) What would fail in implementation?\
d) What is being overstated?\
e) What does the public not understand?\
f) What would a regulator, public authority, or affected community worry about?\
g) What information is missing?\
h) What conflicts or incentives may distort the output?\
i) What should not be published yet?\
j) What requires Board, legal, safeguards, or security review?

This function is essential to GCRI US’s credibility. A public-good institution must be able to challenge itself before the public, regulators, funders, members, or affected communities do so under crisis conditions.

#### 222.9 Councils as Participation Bridges Between National, Regional, and Global Contexts

The Councils may serve as participation bridges between national, regional, and global contexts, provided that legal separateness, mandate limits, jurisdictional sensitivities, and public-description rules are respected. GCRI US may draw on U.S.-based expertise while contributing to broader global public-good learning across aligned institutions and Nexus-related work.

Council participation may help GCRI US understand:

a) U.S. institutional and legal context;\
b) transatlantic and global standards alignment;\
c) public-sector and philanthropic expectations;\
d) academic and research collaboration pathways;\
e) technology and open-source governance implications;\
f) civil-society legitimacy concerns;\
g) community and Indigenous rights-sensitive participation; and\
h) how U.S. public-good stewardship can align with but remain legally distinct from GCRI Canada, GRF, GRA, and other bodies.

Councils may contribute to interoperability, but they shall not create cross-entity authority. A GCRI US Council output does not bind another entity. Another entity’s Council or equivalent body does not bind GCRI US unless adopted through proper GCRI US authority.

#### 222.10 Councils as Training Ground for Institutional Leadership Without Creating Office

The Council system may serve as a training ground for future institutional leadership, expert participation, committee service, public-good stewardship, and responsible membership. Participants may develop literacy in GCRI US mission, governance, evidence, safeguards, public-claims discipline, and non-execution boundaries.

However, Council service shall not create automatic entitlement to Board office, officer roles, employment, membership rights, procurement advantage, public recognition, or institutional authority. Council service may be considered as one factor in future suitability review, but it shall not replace fit-and-proper assessment, conflict review, appointment process, or Board approval.

This distinction protects both the Corporation and participants. It allows Councils to build leadership capacity without turning participation into an informal ladder of entitlement.

#### 222.11 Council Role in Building Public Trust Through Recorded Responsiveness

The Councils shall help GCRI US build public trust through recorded responsiveness. Trust is strengthened when the Corporation can show that it considered relevant perspectives, recorded concerns, responded to serious objections, and corrected outputs when warranted.

Council responsiveness shall be demonstrated through:

a) consultation summaries;\
b) comment disposition logs;\
c) dissent records;\
d) issue trackers;\
e) revised drafts;\
f) safeguards notes;\
g) public-safe explanations of changes;\
h) escalation records; and\
i) closure memoranda.

The Corporation shall not claim broad participation without being able to show how participation affected institutional work. Participation without responsiveness is performative. Responsiveness without records is unverifiable.

#### 222.12 Interpretive Rule for Role of Helix Councils Within GCRI US

This Section shall be interpreted to preserve a controlling proposition: the Helix Councils of GCRI US exist to provide structured deliberation, plural intelligence, quality review, consultation, early warning, contestability, and legitimacy inputs to institutional work, while remaining distinct from delivery, execution, procurement, Board authority, public authority, and final corporate adoption.

Where ambiguity exists, the interpretation that better preserves:

a) Council deliberative role;\
b) quality and legitimacy input;\
c) structured domain knowledge;\
d) formal consultation discipline;\
e) early warning and escalation;\
f) separation from execution and procurement;\
g) adoption-pathway discipline;\
h) corrective intelligence;\
i) national-regional-global role clarity; and\
j) recorded responsiveness

shall prevail unless a contrary result is required by law.

### 223. The Five Helix Councils — System Topology (GCRI United States)

#### 223.1 Five-Council Topology as the Standard Participation Architecture

GCRI US shall organize its standing Helix Council System around five primary Councils unless the Board lawfully amends the Council architecture through the procedures set out in this Part. The five-Council topology shall provide the standard participation architecture for structured plural deliberation, institutional learning, public-interest challenge, and quality review across the Corporation’s work.

The five Councils shall be:

a) Public Authorities Council (PAC);\
b) Industry and Operators Council (IOC);\
c) Academia and Research Council (ARC);\
d) Civil Society and Media Council (CMC); and\
e) Community and Indigenous Council (CIC).

This topology is designed to ensure that GCRI US does not rely on a single knowledge class, sector, authority source, or legitimacy pathway. It recognizes that systemic risk, resilience, sustainability, public-good technology, evidence governance, and national readiness require plural intelligence. Public authorities understand mandate, law, public finance, administrative feasibility, and sovereign sensitivity. Operators understand infrastructure, implementation, maintenance, continuity, cost, and system reliability. Researchers understand method, uncertainty, reproducibility, and evidence quality. Civil society and media understand transparency, accountability, public trust, social interpretation, and communications integrity. Communities and Indigenous participants understand lived consequences, place-based risk, rights-sensitive context, dignity, and the limits of extractive consultation.

The five-Council topology shall be treated as a coherence architecture. It is not a collection of unrelated advisory groups. Each Council contributes a distinct form of knowledge, and the Council Operating System shall ensure that their outputs can be compared, routed, reconciled, escalated, and preserved.

#### 223.2 Public Authorities Council (PAC — GCRI US Edition)

The Public Authorities Council shall provide a structured surface for public-sector, public-law, regulatory, institutional, policy, intergovernmental, and public-administration perspectives relevant to GCRI US’s nonprofit public-good mission. It may include, subject to eligibility and representation rules, persons with experience in federal, state, local, tribal, territorial, regulatory, public finance, emergency management, resilience, infrastructure, development, standards, science-policy, public health, environmental, or related public institutions.

The PAC shall help GCRI US understand:

a) public-sector constraints and responsibilities;\
b) public-law and administrative feasibility;\
c) sovereignty, federalism, and jurisdictional sensitivities;\
d) public finance and budget-cycle realities;\
e) emergency management and resilience governance needs;\
f) regulatory perception and perimeter concerns;\
g) public procurement and public-integrity risks;\
h) intergovernmental coordination challenges;\
i) public records, ethics, gifts, lobbying, and conflict constraints; and\
j) how GCRI US outputs may be read by public authorities and the public.

The PAC shall not be treated as a public authority. It shall not speak for the United States Government, any state, any regulator, any public agency, any tribal government, any municipality, or any public institution unless an explicit lawful mandate and approved record exist. PAC participation shall not imply government endorsement, policy adoption, regulatory comfort, procurement eligibility, or official mandate.

PAC outputs shall be framed as public-authority perspective, policy feasibility input, public-law sensitivity note, administrative-risk warning, or consultation contribution unless formally adopted through a separate GCRI US authority pathway. No PAC note shall be publicized as state position, government approval, or regulatory position without independent lawful basis.

#### 223.3 Industry and Operators Council (IOC — GCRI US Edition)

The Industry and Operators Council shall provide a structured surface for operational, infrastructure, technology, enterprise, service-delivery, cyber, engineering, resilience, data, finance-adjacent, insurance-adjacent, logistics, utilities, platform, and implementation perspectives relevant to GCRI US’s public-good work. Its role is to test whether concepts, standards, tools, evidence processes, and public-good infrastructure can work under real-world operational constraints.

The IOC may help assess:

a) feasibility of implementation;\
b) operational supportability;\
c) infrastructure dependency;\
d) cybersecurity and resilience requirements;\
e) vendor-lock-in and interoperability risks;\
f) data pipeline and integration constraints;\
g) cost, staffing, maintenance, and lifecycle issues;\
h) business continuity and incident response realities;\
i) operational risks in public-good technology release; and\
j) whether proposed frameworks can be implemented without creating hidden execution activity.

The IOC shall be subject to strict competition, antitrust, procurement, confidentiality, and anti-capture controls. Participants shall not exchange competitively sensitive information, coordinate prices, divide markets, signal bids, influence procurement, exclude competitors, or use the Council as a vendor-positioning platform.

No IOC output may create procurement preference, vendor endorsement, technical certification, product validation, operational approval, market routeability, execution authority, or commercial advantage. An IOC feasibility note may identify implementation risks or operational considerations. It shall not select providers or approve products.

#### 223.4 Academia and Research Council (ARC — GCRI US Edition)

The Academia and Research Council shall provide a structured surface for scientific, methodological, epistemic, research, educational, and scholarly perspectives relevant to GCRI US’s public-good mission. It may include participants from universities, research institutes, independent research bodies, scientific networks, technical communities, standards communities, and relevant epistemic fields.

The ARC shall help GCRI US strengthen:

a) methodological soundness;\
b) evidence quality;\
c) reproducibility and replication;\
d) uncertainty disclosure;\
e) model-risk awareness;\
f) data provenance and lineage;\
g) literature grounding;\
h) peer challenge and dissent preservation;\
i) research integrity and publication discipline; and\
j) the distinction between hypothesis, evidence, interpretation, recommendation, and adopted institutional position.

The ARC shall not replace formal research governance, ethics review, peer review, institutional review board requirements where applicable, data-governance review, safeguards review, or Board adoption. An ARC method note may strengthen the evidentiary basis of a GCRI US output, but it shall not convert a draft into a final institutional position.

No ARC output may be treated as conclusive recognition, certification, validation, endorsement, final evidence determination, or public-good standard unless the competent authority has adopted it through the required process. Academic prestige shall not substitute for institutional authority.

#### 223.5 Civil Society and Media Council (CMC — GCRI US Edition)

The Civil Society and Media Council shall provide a structured surface for civil-society, public-reason, accountability, transparency, communications integrity, social trust, journalistic, civic, philanthropic, and public-interest perspectives. Its role is to help GCRI US understand how its work is perceived, whether it is legible, whether it protects public trust, and whether its narratives, participation models, and outputs are socially accountable.

The CMC may review:

a) public legibility of GCRI US outputs;\
b) risks of overclaim, jargon, ambiguity, or public confusion;\
c) transparency and accountability expectations;\
d) safeguards and participation concerns;\
e) communications integrity;\
f) social trust implications;\
g) media-risk and misinformation concerns;\
h) accessibility of consultation materials;\
i) public-interest externalities; and\
j) whether institutional claims match the authoritative record.

The CMC shall not become a political advocacy organ of GCRI US. It shall not issue political endorsements, media endorsements, campaign positions, partisan statements, or public mandates in the name of GCRI US unless the Corporation separately authorizes a lawful institutional position through proper governance.

No CMC output may be treated as public mandate, media endorsement, civil-society consensus, political position, or authorization to speak publicly for GCRI US. Its function is to test transparency, public reason, communications integrity, and social trust.

#### 223.6 Community and Indigenous Council (CIC — GCRI US Edition)

The Community and Indigenous Council shall provide a structured surface for community, Indigenous, local, place-based, rights-sensitive, lived-experience, and affected-population perspectives. It is a safeguards-heavy Council whose legitimacy depends on dignity, careful representation, non-extractive participation, protected handling, and strict limits against overclaim.

The CIC may help GCRI US understand:

a) lived experience of systemic risk, disaster, infrastructure fragility, climate stress, digital harm, health disruption, food-water-energy insecurity, and institutional exclusion;\
b) place-based and local-truth considerations;\
c) Indigenous rights, knowledge-protection, sovereignty, and consent boundaries;\
d) community trust, participation burden, and consultation fatigue;\
e) safeguards risks and dignity concerns;\
f) grievance pathways and remedy expectations;\
g) unintended consequences of public-good frameworks;\
h) accessibility and participation barriers; and\
i) whether outputs risk extracting legitimacy from communities without reciprocal benefit.

The CIC shall not be used to imply Indigenous consent, community consent, affected-population approval, or social license beyond the precise recorded scope of participation. No participant shall be treated as representing an entire people, nation, tribe, community, geography, or rights-holder group unless a clear mandate exists and the record supports that representation.

CIC outputs shall be handled with particular care. Some outputs may require restricted publication, anonymization, role-marker treatment, or safeguards review before circulation. GCRI US shall not appropriate community or Indigenous knowledge into public materials without consent, context, and safeguards.

#### 223.7 Cross-Council Integrity, Coherence, and Shared Semantics

The five Councils shall operate with distinct mandates, but they shall share common semantics, records discipline, output taxonomy, conflict rules, safeguards rules, publication classes, and escalation pathways. Cross-Council coherence is essential because many matters before GCRI US will not fall neatly into one knowledge domain.

For example:

a) a risk-intelligence framework may require ARC method review, IOC feasibility review, CMC public-legibility review, PAC public-authority sensitivity review, and CIC safeguards review;\
b) a public-good technology release may require IOC operational review, ARC methodology review, security review, and public-claims review;\
c) a resilience policy paper may require PAC, ARC, CMC, and CIC input;\
d) a consultation process may require CMC accessibility review and CIC participation-safety review; and\
e) a Nexus-aligned evidence framework may require all Councils to examine separate risks before adoption.

Shared semantics shall ensure that “recommendation,” “warning,” “review,” “consultation summary,” “concurrence,” “dissent,” “adoption-ready,” “restricted,” “public-safe,” and “escalated” mean the same thing across Councils. Without shared semantics, Council outputs become difficult to compare and easy to overclaim.

#### 223.8 No Additional Council May Be Created Without Formal Constitutional and Operating Review

No additional standing Council may be created without formal constitutional and operating review by the Board or competent authority. New Councils may be useful as the Corporation grows, but additional Councils can also create fragmentation, duplication, public confusion, capture risk, and mandate overlap.

Before creating any additional Council, GCRI US shall review:

a) mission need;\
b) gap in the existing five-Council topology;\
c) whether the matter can be handled by a working party, expert panel, committee, or cross-Council session instead;\
d) proposed mandate and exclusions;\
e) relationship to existing Councils;\
f) participant categories and seat allocation;\
g) safeguards and competition risks;\
h) records and Secretariat capacity;\
i) public-description implications;\
j) resource requirements; and\
k) sunset or review provisions.

No new Council shall be created for prestige, donor preference, public relations, sector appeasement, or to give a powerful constituency a permanent influence channel. Any new Council must strengthen the public-good architecture and remain within Part X.

#### 223.9 Temporary and Thematic Council-Like Constructs Only Under Explicit Time-Bound Charter

GCRI US may create temporary or thematic council-like constructs, such as task councils, thematic forums, advisory circles, listening panels, expert roundtables, or issue-specific consultation groups, only under explicit time-bound charter. These bodies may be useful for urgent, emerging, or specialized topics that do not justify a permanent standing Council.

A temporary or thematic construct shall have:

a) specific purpose;\
b) limited scope;\
c) defined participants;\
d) start and end date;\
e) output type;\
f) relationship to standing Councils;\
g) records requirements;\
h) safeguards and conflict controls;\
i) public-description limits; and\
j) closure or handoff process.

Such constructs shall not become shadow Councils or permanent influence surfaces through repeated renewal. If they prove necessary as standing bodies, they must undergo formal constitutional review.

#### 223.10 Council Topology and Anti-Capture Balance

The five-Council topology shall be administered as an anti-capture balance. Each Council exists partly to check the blind spots of the others. Public authority without community input may become technocratic or state-centric. Industry without competition controls may become vendor capture. Academia without operational reality may become abstract. Civil society without method discipline may become purely narrative. Community and Indigenous participation without safeguards may become extractive or overclaimed.

The Council system shall therefore maintain balance by:

a) preventing one Council from dominating institutional outputs;\
b) requiring cross-Council review where a matter has multi-domain consequences;\
c) preserving dissent across Councils;\
d) ensuring that under-resourced voices can participate safely;\
e) preventing donor or sponsor influence over Council topology;\
f) monitoring sectoral concentration; and\
g) recalibrating Council composition where imbalance appears.

A balanced Council topology is not merely fair. It improves the quality, legitimacy, and resilience of GCRI US outputs.

#### 223.11 Public Description of the Five-Council System

Public description of the five-Council system shall be accurate, bounded, and non-misleading. GCRI US may describe the Councils as structured deliberative and advisory organs for plural participation, review, consultation, and institutional learning. It shall not describe them as governing bodies, certification bodies, regulatory bodies, procurement authorities, execution committees, or official representatives of all sectors named.

Public materials shall state, where appropriate, that:

a) Council participation does not imply endorsement by GCRI US;\
b) Council outputs are advisory unless adopted through proper authority;\
c) public-authority participation does not equal government mandate;\
d) Indigenous or community participation does not equal broad consent beyond recorded scope;\
e) industry participation does not create vendor preference;\
f) academic participation does not create conclusive validation; and\
g) civil-society or media participation does not create public mandate.

The Corporation shall correct any public use of Council status that overstates authority, participation, representation, endorsement, or effect.

#### 223.12 Interpretive Rule for the Five Helix Councils — System Topology

This Section shall be interpreted to preserve a controlling proposition: GCRI US’s five-Council topology is a balanced public-good architecture for structured public-authority, operator, research, civil-society, media, community, and Indigenous input, and no Council may dominate, overclaim, certify, execute, govern, or create external authority beyond its recorded mandate.

Where ambiguity exists, the interpretation that better preserves:

a) the five-Council topology;\
b) distinct Council mandates;\
c) cross-Council coherence;\
d) shared semantics;\
e) public-description discipline;\
f) anti-capture balance;\
g) safeguards-heavy CIC treatment;\
h) competition-safe IOC treatment;\
i) public-authority non-overclaim in PAC; and\
j) formal review before any new standing Council is created

shall prevail unless a contrary result is required by law.

### 224. Public Authorities Council (PAC) (GCRI United States)

#### 224.1 PAC Purpose and Constitutional Position

The Public Authorities Council, or PAC, shall be the Helix Council through which GCRI US receives structured public-sector, public-law, regulatory, public finance, emergency management, infrastructure, resilience, science-policy, and institutional governance input. The PAC shall exist to help the Corporation understand how its public-good research, evidence systems, standards work, risk-governance frameworks, technical concepts, consultation outputs, and Nexus-aligned public-good architecture may interact with public institutions, public mandates, administrative constraints, public trust, and legal accountability.

The PAC shall be a deliberative and advisory Council. It shall not be a government body, regulatory body, public authority, statutory forum, procurement body, intergovernmental organization, or official public-sector decision-making mechanism. Its constitutional position within GCRI US shall be limited to structured input, review, challenge, consultation, and escalation within its recorded mandate.

The PAC shall help ensure that GCRI US does not design public-good tools, standards, evidence frameworks, or resilience concepts in a way that ignores the realities of:

a) public administration;\
b) federal, state, tribal, territorial, and local governance;\
c) emergency powers and continuity of government;\
d) public finance and budget cycles;\
e) public procurement and conflict rules;\
f) regulatory interpretation and regulated-perimeter sensitivity;\
g) public records, ethics, gifts, lobbying, and transparency obligations;\
h) public-sector cybersecurity, privacy, and data-handling duties;\
i) interagency coordination and institutional accountability; and\
j) public legitimacy in crisis, risk, and resilience contexts.

The PAC shall be especially important for GCRI US because the Corporation’s public-good work may be read by public authorities, policymakers, funders, public institutions, and regulated entities. The PAC shall help the Corporation design with public-sector reality in mind while preventing any public-sector interaction from being overclaimed as official endorsement, adoption, mandate, regulatory approval, or procurement preference.

#### 224.2 Scope of Public-Sector, Sovereign, Regulatory, and Institutional Input

The PAC may consider matters involving public-sector feasibility, public-law sensitivity, regulatory perception, public administration, resilience policy, national preparedness, public finance, public infrastructure, disaster-risk governance, emergency management, public data governance, public-interest technology, standards adoption, public accountability, and institutional trust.

Within its mandate, the PAC may provide input on:

a) how GCRI US public-good outputs may be interpreted by public institutions;\
b) whether proposed frameworks align with public-sector operating realities;\
c) whether policy recommendations require clearer legal, institutional, or implementation language;\
d) whether public authorities may need different materials than academic, technical, civil-society, community, or private-sector audiences;\
e) whether public-benefit claims could be misread as official government position;\
f) whether consultation processes should include specific public-sector stakeholders;\
g) whether emergency, resilience, or infrastructure concepts create public-law implications;\
h) whether data, AI, risk-intelligence, or evidence systems raise public-sector privacy, security, or records concerns;\
i) whether financial-resilience, development-finance, or risk-transfer discussions risk implying regulated public commitments; and\
j) whether GCRI US materials should include stronger disclaimers, definitions, or adoption-pathway language.

The PAC may also support structured dialogue with public-sector-adjacent participants, including former public officials, public administrators, policy experts, emergency-management professionals, public finance specialists, regulators in personal or non-binding capacity, standards professionals, and institutional resilience practitioners, subject to conflict, ethics, public-description, and participation rules.

The PAC’s scope shall be broad enough to improve public-sector usability and narrow enough to prevent public-authority confusion.

#### 224.3 Limits of PAC Authority and No Substitution for Competent Public Authority

The PAC shall not substitute for any competent public authority. It shall not exercise governmental power, regulatory power, public procurement authority, public finance authority, emergency authority, administrative authority, licensing authority, or public-law decision-making authority. It shall not approve public policy on behalf of any government or agency. It shall not certify that a GCRI US output is accepted by any public institution unless such acceptance has been separately recorded by that institution through its lawful process.

The PAC shall not:

a) bind any federal, state, tribal, territorial, local, municipal, regulatory, or public institution;\
b) issue statements in the name of a public authority unless expressly authorized by that authority;\
c) create or imply government endorsement of GCRI US, its members, outputs, programs, standards, technology, or partners;\
d) grant procurement eligibility, preferred-provider status, or public-sector approval;\
e) create regulatory comfort, no-action assurance, supervisory acceptance, or compliance equivalence;\
f) approve public funding, public finance, emergency funds, resilience funds, grants, insurance, guarantees, or risk-transfer mechanisms;\
g) act as an intergovernmental forum or public-policy negotiating body; or\
h) authorize execution-side, market-facing, financial, insurance, securities, lending, custody, settlement, or transaction-routing activity.

Where a PAC output comments on public-sector feasibility, it shall be framed as advisory input to GCRI US, not as public authority determination. Where public authority confirmation is needed, it must be obtained separately through the lawful channel of the relevant public body.

#### 224.4 Public-Law, Administrative, and Sovereignty-Sensitive Deliberation Rules

PAC deliberation shall be conducted with heightened care for public-law, administrative, sovereignty-sensitive, ethics, procurement, and institutional-accountability considerations. Participants associated with public authorities may be subject to laws, policies, professional obligations, disclosure requirements, conflict rules, lobbying restrictions, gift rules, public-records rules, procurement restrictions, confidentiality obligations, or limits on official capacity.

Before seating a PAC participant, GCRI US shall clarify, where relevant:

a) whether the participant acts in personal, professional, observer, institutional, official, or former-office capacity;\
b) whether the participant has authority to speak for an institution;\
c) whether the participant is subject to public-law, ethics, lobbying, gifts, procurement, or disclosure restrictions;\
d) whether participation may require employer or agency approval;\
e) whether public naming is permitted;\
f) whether meeting materials may be received;\
g) whether restricted or controlled-room access is appropriate; and\
h) whether recusal is required for matters involving procurement, funding, regulation, public contracts, or institutional interests.

PAC materials shall avoid language that places participants in a position of implied endorsement. Meeting agendas, minutes, and public summaries shall not identify public-sector participants in a manner that implies official approval unless the record supports it. Where necessary, participants may be described by role marker, sector category, or anonymized capacity.

Sovereignty-sensitive deliberation shall be especially controlled where matters touch tribal, territorial, federal, state, cross-border, Indigenous, public safety, critical infrastructure, emergency management, national security, sanctions, or public-finance concerns.

#### 224.5 Public-Authority Participation Safety, Handling, and Representation Controls

Public-authority participation in the PAC shall be subject to safety, handling, and representation controls. These controls protect participants, their institutions, the Corporation, and the public from misunderstanding or misuse.

The PAC shall maintain representation controls ensuring that:

a) a participant does not appear to represent a public authority unless formally authorized;\
b) former officials are not described as current officials;\
c) personal expertise is not presented as agency position;\
d) observer participation is not described as institutional participation;\
e) public-sector attendance is not converted into endorsement;\
f) public officials are not placed into conflict with procurement, ethics, or lobbying rules; and\
g) public materials do not create false impressions of governmental sponsorship.

Handling controls may include restricted attendance, controlled minutes, role-marker participation, approval of attribution, public-description review, no-record portions where lawful and appropriate, controlled-room segmentation, and legal or ethics review before publication.

Where a public authority participant identifies a concern that publication could create legal, employment, security, public-records, procurement, or sovereignty risk, GCRI US shall evaluate the concern before release. Transparency shall be balanced with safety, legality, and accurate public meaning.

#### 224.6 PAC Output Types, Review Surfaces, and Escalation Functions

The PAC may produce output types assigned by the Council Operating System. Such outputs shall be advisory unless adopted by the competent authority. PAC output types may include:

a) public-sector feasibility note;\
b) public-law sensitivity memorandum;\
c) administrative-implementation warning;\
d) public-finance or budget-cycle observation;\
e) regulatory-perimeter caution;\
f) public-procurement risk note;\
g) emergency-management relevance note;\
h) public records, ethics, or disclosure-risk observation;\
i) intergovernmental coordination note;\
j) public-trust and legitimacy concern;\
k) public-authority consultation summary; and\
l) escalation memorandum to the Board, Secretariat, legal function, safeguards function, or another Council.

PAC review surfaces may include draft policy papers, consultation submissions, standards proposals, public-good infrastructure frameworks, public-sector engagement plans, national-readiness models, risk-governance frameworks, emergency or resilience concepts, AI and data governance proposals, and public communications that may be interpreted by public institutions.

Where PAC identifies a material risk, it may escalate the matter to:

a) the Board;\
b) Governance Committee;\
c) Audit and Risk Committee;\
d) legal or compliance function;\
e) Secretary and records function;\
f) public-claims function;\
g) safeguards or security function;\
h) relevant Council; or\
i) executive management for operational correction.

Escalation shall be recorded with matter ID, risk type, urgency, recommended routing, and any publication or handling restrictions.

#### 224.7 No PAC Output May Be Presented as State Position or Government Mandate Without Explicit Lawful Basis

No PAC output, deliberation, meeting, participant comment, concurrence note, public-sector feasibility observation, or consultation summary may be presented as a state position, government mandate, agency approval, regulator comfort, public-sector endorsement, official policy, procurement signal, funding commitment, or public authority adoption unless there is explicit lawful basis and an authoritative record from the relevant public authority.

This rule shall apply even where:

a) public officials participated;\
b) senior former officials contributed;\
c) public institutions were represented as observers;\
d) the PAC reached consensus;\
e) the output concerns public policy;\
f) the output was shared with public authorities;\
g) public authorities did not object; or\
h) a public-sector participant helped draft the output.

Silence is not endorsement. Attendance is not adoption. Comment is not approval. Review is not mandate.

Any public communication referencing PAC work shall use controlled language such as “public-sector feasibility input,” “public-authority-sensitive consultation,” “public administration perspective,” or “PAC advisory note,” unless stronger language is supported by lawful public-authority record.

#### 224.8 PAC Role in U.S. Federalism, Tribal, State, Local, and Cross-Border Sensitivities

Because GCRI US is a United States nonprofit operating in a federal system and in a global Nexus-aligned context, the PAC shall pay particular attention to U.S. federalism, tribal sovereignty, state and local authority, territorial governance, cross-border cooperation, and public-sector jurisdictional limits.

PAC deliberations shall recognize that:

a) federal, state, tribal, territorial, and local authorities have distinct mandates;\
b) public authority in one jurisdiction does not imply authority in another;\
c) tribal sovereignty and Indigenous governance require distinct safeguards and representation discipline;\
d) emergency management, public health, infrastructure, environment, energy, water, and finance responsibilities may be distributed across multiple levels of government;\
e) public-sector adoption pathways may require statutory, administrative, procurement, budgetary, or interagency processes; and\
f) U.S. participation in global public-good discussions must preserve legal and institutional separateness.

The PAC may help GCRI US avoid one-size-fits-all public-sector language. It may recommend differentiated wording, jurisdictional disclaimers, public-safe summaries, or routing to specialized review where a matter touches tribal, state, local, or federal authority.

#### 224.9 PAC Role in Public-Sector Readiness, Resilience, and Evidence-to-Decision Interfaces

The PAC may provide structured input on public-sector readiness, resilience governance, and evidence-to-decision interfaces. GCRI US may develop public-good frameworks that help institutions understand risk, verify evidence, prepare resilience actions, or evaluate readiness. The PAC can help test whether such frameworks are usable by public institutions without implying that GCRI US executes government programs.

PAC input may examine:

a) whether evidence packs are understandable to public decision-makers;\
b) whether decision records align with public accountability needs;\
c) whether risk taxonomies match public-sector planning cycles;\
d) whether resilience frameworks align with emergency management practice;\
e) whether safeguards and public consultation are adequate;\
f) whether public-sector data handling is realistic;\
g) whether implementation language avoids procurement or regulatory overclaim; and\
h) whether outputs can be used as public-good learning tools without becoming unauthorized public instruments.

PAC input shall remain advisory. Public-sector readiness language shall not imply public-sector adoption unless separately approved by competent public authorities.

#### 224.10 PAC Role in Regulatory Perimeter and Non-Execution Protection

The PAC shall support regulatory-perimeter awareness and non-execution protection. Because GCRI US may work on risk, resilience, standards, evidence, and finance-adjacent topics, public authorities and regulated actors may misread outputs as approval, compliance comfort, market readiness, insurance readiness, investment readiness, or official framework endorsement.

The PAC may identify where wording should be narrowed to avoid implying:

a) regulated financial advice;\
b) insurance, securities, lending, banking, custody, settlement, or payment authority;\
c) public-sector guarantee or fiscal commitment;\
d) regulatory acceptance or supervisory approval;\
e) procurement eligibility;\
f) certification or conformance status;\
g) governmental endorsement of a private actor; or\
h) execution-side role for GCRI US.

Where perimeter risk is identified, PAC shall route the matter for legal, Board, or public-claims review. No PAC participant shall provide regulatory interpretation on behalf of a regulator unless formally authorized.

#### 224.11 PAC Records, Minutes, Attribution, and Public-Safe Summaries

PAC records shall be accurate, classified, and attribution-controlled. Public authority-related discussions can be sensitive even when not confidential. Minutes shall record deliberation sufficiently for institutional learning while avoiding unnecessary attribution that could imply official position or expose participants to public-law, employment, or political consequences.

PAC minutes shall include:

a) meeting identifier and date;\
b) agenda and matter IDs;\
c) participant categories and capacity where safe;\
d) materials reviewed;\
e) conflicts, recusals, and handling restrictions;\
f) key public-sector feasibility points;\
g) unresolved concerns;\
h) outputs produced;\
i) escalation actions; and\
j) publication class.

Public-safe summaries may describe the nature of public-sector considerations without naming participants or institutions unless attribution has been approved. Where attribution is permitted, it shall state capacity accurately.

#### 224.12 Interpretive Rule for Public Authorities Council

This Section shall be interpreted to preserve a controlling proposition: the PAC provides structured public-sector, public-law, regulatory, institutional, public-finance, emergency-management, and administrative feasibility input to GCRI US, but it shall never be presented as a government body, public mandate, regulatory approval, procurement signal, public-sector endorsement, or substitute for competent public authority.

Where ambiguity exists, the interpretation that better preserves:

a) public-authority non-overclaim;\
b) public-law and ethics sensitivity;\
c) correct participant capacity;\
d) federal, tribal, state, local, and cross-border nuance;\
e) advisory-only PAC outputs;\
f) regulatory perimeter discipline;\
g) public-safe attribution;\
h) records integrity; and\
i) non-execution public-good boundaries

shall prevail unless a contrary result is required by law.

### 225. Industry and Operators Council (IOC) (GCRI United States)

#### 225.1 IOC Purpose and Constitutional Position

The Industry and Operators Council, or IOC, shall be the Helix Council through which GCRI US receives structured operator, infrastructure, enterprise, technology, implementation, cybersecurity, systems-engineering, service-delivery, and operational-resilience input. The IOC shall exist to test whether GCRI US public-good concepts, evidence frameworks, standards proposals, technical architectures, consultation outputs, resilience models, and Nexus-aligned operating ideas are practical, supportable, interoperable, secure, and capable of real-world use without compromising nonprofit status, public-interest neutrality, competition safety, or the non-execution boundary.

The IOC shall be a deliberative, advisory, and operational-realism Council. It shall not be a procurement body, vendor forum, commercial steering committee, product-certification body, market-access committee, execution committee, standards-capture channel, or delivery-stack authority. Its role is to inform GCRI US about implementation realities; it shall not choose implementers, allocate opportunities, endorse providers, or turn participation into commercial advantage.

The IOC shall help GCRI US understand:

a) whether proposed frameworks can be implemented by real institutions;\
b) whether infrastructure, software, data, identity, security, or operational assumptions are credible;\
c) whether maintenance, support, training, cost, and lifecycle burdens are realistic;\
d) whether open public-good architecture is at risk of vendor lock-in;\
e) whether technical design creates hidden dependency, security weakness, or operational fragility;\
f) whether implementation language could be misread as procurement preference or execution authority;\
g) whether sector participants are exchanging information in a competition-sensitive way; and\
h) whether public-good standards and tools can remain neutral, interoperable, and usable across institutions.

The IOC is therefore a realism and resilience function inside the Council system. It protects GCRI US from producing elegant but unbuildable frameworks, overly abstract standards, unsafe technical releases, or public-good designs that ignore the cost and complexity of operations.

#### 225.2 Scope of Operator, Technical, Infrastructure, and Applied-Implementation Input

The IOC may consider matters involving infrastructure, operations, technical deployment, interoperability, service reliability, cybersecurity, supply chain, data integration, cloud and edge systems, open-source maintainability, enterprise adoption, continuity, critical infrastructure, implementation support, and operational readiness.

Within its mandate, the IOC may provide input on:

a) operational feasibility of proposed GCRI US frameworks;\
b) implementation constraints faced by public institutions, utilities, enterprises, universities, civil-society infrastructure, and technology operators;\
c) reliability and resilience requirements for public-good technical systems;\
d) data pipeline, API, schema, identity, repository, and integration considerations;\
e) cybersecurity, access-control, incident-response, and secure-release considerations;\
f) cloud, compute, storage, continuity, and vendor-dependency risks;\
g) operational costs, staffing models, support models, and maintenance responsibilities;\
h) deployment sequencing and maturity-level assumptions;\
i) compatibility with open standards, open-source approaches, and interoperability commitments;\
j) risks of implementation burden shifting to under-resourced institutions; and\
k) risks that operational models could drift into regulated execution, procurement influence, or vendor preference.

IOC input may be especially relevant where GCRI US develops or reviews public-good architectures connected to risk intelligence, evidence rails, resilience data systems, technical reference models, AI governance workflows, standards implementation playbooks, digital public infrastructure patterns, and Nexus-aligned readiness tooling.

#### 225.3 Limits of IOC Authority and No Capture by Vendors, OEMs, Platforms, or Corporate Blocs

The IOC shall be subject to strict limits designed to prevent capture by vendors, original equipment manufacturers, platform providers, cloud providers, software firms, infrastructure companies, insurers, financial institutions, consulting firms, technology integrators, data providers, or corporate blocs. The IOC may receive operational knowledge from such actors, but it shall not become a channel through which commercial actors shape GCRI US outputs for private advantage.

The IOC shall not:

a) endorse any vendor, product, platform, model, tool, service, infrastructure provider, insurer, financial product, data provider, or implementation partner;\
b) create preferred-provider status;\
c) influence procurement outcomes;\
d) grant privileged access to GCRI US public-good assets;\
e) allow a participant to steer standards toward its proprietary systems;\
f) allow sponsor-funded technical preferences to become institutional architecture;\
g) convert operational feasibility review into commercial validation;\
h) allow corporate participants to dominate agenda, drafting, or outputs; or\
i) permit participants to use IOC status as evidence of GCRI US approval.

Where a participant has commercial interest in a matter, the participant shall disclose the interest and may be subject to recusal, limited access, no-drafting rules, or public-description restrictions. If the IOC cannot deliberate without material capture risk, the matter shall be routed to independent expert review, red-team review, Board review, or a conflict-managed working party.

#### 225.4 Competition, Antitrust, and Sensitive-Information Controls in IOC Context

The IOC shall operate under strict competition, antitrust, and sensitive-information controls. The Corporation recognizes that bringing operators, infrastructure providers, technology firms, financial institutions, insurers, consultancies, data providers, and sector participants into the same deliberative space can create competition-law and market-integrity risk. The IOC shall therefore maintain a competition-safe operating protocol.

IOC participants shall not discuss, exchange, coordinate, or signal:

a) prices, fees, rates, premiums, margins, discounts, or commercial terms;\
b) bids, procurement strategies, tenders, or award expectations;\
c) customer allocation, market allocation, geographic allocation, or service allocation;\
d) production capacity, supply constraints, commercial roadmaps, or confidential business plans where competitively sensitive;\
e) vendor exclusion, boycotts, refusal-to-deal strategies, or coordinated market conduct;\
f) confidential customer, client, insured, investor, borrower, or counterparty information;\
g) commercially sensitive data not necessary for the public-good purpose; or\
h) future market behavior.

Agendas shall be reviewed for competition sensitivity. Meetings may include an antitrust reminder. Minutes shall avoid recording competitively sensitive detail. The chair, Secretariat, or legal function may stop discussion, remove an item, require recusal, or close a meeting segment where competition risk arises.

The IOC may discuss general public-good standards, interoperability, security, implementation barriers, resilience needs, and non-confidential operational lessons. It shall not become a forum for market coordination.

#### 225.5 Operational Feasibility, Supportability, and Deployment-Realism Functions

The IOC shall provide operational feasibility, supportability, and deployment-realism functions. GCRI US outputs shall be tested against practical implementation realities before being overclaimed as usable, scalable, or deployment-ready.

The IOC may examine:

a) whether a proposed framework can be implemented by a small institution as well as a large one;\
b) whether technical requirements are proportionate;\
c) whether security controls are realistic and not merely aspirational;\
d) whether data requirements are lawful, available, and maintainable;\
e) whether open-source components have sustainable maintenance paths;\
f) whether staff training requirements are credible;\
g) whether operational timelines are realistic;\
h) whether dependencies on vendors, clouds, APIs, models, or data sources create fragility;\
i) whether systems can degrade safely during outage;\
j) whether incident response and recovery are adequately specified; and\
k) whether the proposed model shifts costs or risks to less-resourced participants.

This function is essential to GCRI US’s public-good credibility. A public-good framework that cannot be operated safely may create false confidence. The IOC shall help prevent such false confidence.

#### 225.6 IOC Output Types, Technical Review Surfaces, and Readiness Inputs

The IOC may produce bounded outputs within the Council Operating System. Such outputs shall be advisory unless adopted through the competent GCRI US authority pathway.

IOC output types may include:

a) operational feasibility note;\
b) implementation-risk review;\
c) interoperability assessment;\
d) cybersecurity and resilience concern;\
e) deployment-readiness observation;\
f) lifecycle and maintenance note;\
g) supportability memorandum;\
h) vendor-lock-in warning;\
i) infrastructure-dependency map;\
j) data-integration constraint note;\
k) field-implementation lesson;\
l) market-sensitivity or competition-risk alert; and\
m) escalation memorandum to the Board, Secretariat, security function, legal function, public-claims function, or another Council.

IOC review surfaces may include draft standards, risk frameworks, technical architectures, AI governance templates, evidence-to-decision workflows, open-source repository release plans, public-good tooling concepts, implementation playbooks, capacity-building materials, and consultation outputs that contain operational claims.

Where an IOC output is used in an adoption-ready decision pack, the pack shall state the IOC output’s effect. It shall not imply IOC approval unless approval is an expressly defined and authorized output type. The correct formulation will usually be that IOC reviewed feasibility, identified implementation considerations, or recommended risk controls.

#### 225.7 No IOC Output May Create Procurement Preference, Vendor Endorsement, or Execution Authority

No IOC output shall create procurement preference, vendor endorsement, product approval, platform certification, service recommendation, technical accreditation, commercial routeability, execution authority, or market advantage. This rule shall apply even where the IOC strongly agrees that a tool, vendor, approach, or platform appears technically strong.

The IOC may say, where properly supported, that a design pattern appears more interoperable, a technical risk requires mitigation, a proprietary dependency should be avoided, or a deployment assumption is unrealistic. It shall not say or imply that a named vendor should be selected, a product should be purchased, a platform is approved by GCRI US, or an operator is preferred for implementation.

Public descriptions shall not state:

a) “IOC-approved vendor”;\
b) “GCRI US operator-endorsed”;\
c) “Council-certified solution”;\
d) “preferred technology partner”;\
e) “procurement-ready by IOC review”;\
f) “market-validated by GCRI US”; or\
g) similar language suggesting commercial endorsement.

If a participant attempts to use IOC participation for marketing, procurement, investor, regulatory, or customer-facing claims, GCRI US may require correction, impose restrictions, suspend participation, or refer the matter to integrity review.

#### 225.8 IOC Role in Open Architecture, Interoperability, and Vendor-Neutral Public Goods

The IOC shall help GCRI US preserve open architecture, interoperability, portability, vendor neutrality, and public-good independence. Its technical and operational input shall be used to identify where frameworks may unintentionally favor one vendor, platform, data model, cloud provider, or proprietary implementation path.

The IOC may review whether:

a) standards are implementable by multiple actors;\
b) schemas and APIs avoid unnecessary proprietary dependency;\
c) reference architectures can be implemented in different environments;\
d) open-source components have clear license and maintenance rules;\
e) data portability and exit are preserved;\
f) security requirements are vendor-neutral;\
g) procurement specifications avoid hidden bias;\
h) technical documentation is sufficiently clear for independent implementation; and\
i) smaller institutions can participate without being locked into expensive or closed systems.

This role is fundamental to GCRI US’s public-good mandate. Public-good architecture shall not become a disguised sales funnel or closed platform. IOC participation shall help reveal and prevent that risk.

#### 225.9 IOC Role in Cybersecurity, Operational Resilience, and Secure Release Discipline

The IOC shall provide structured input on cybersecurity, operational resilience, secure release, system dependency, and failure-mode analysis. Where GCRI US develops public-good technical assets, reference models, repositories, data schemas, AI workflows, or risk intelligence tools, the IOC may help identify security and operational risks before release.

IOC review may consider:

a) threat model completeness;\
b) identity and access requirements;\
c) least-privilege design;\
d) logging, monitoring, and auditability;\
e) secure software development lifecycle considerations;\
f) dependency and supply-chain risk;\
g) incident response and disclosure discipline;\
h) disaster recovery and continuity;\
i) data minimization and privacy-by-design;\
j) AI model, prompt, retrieval, and tool-use risks;\
k) resilience under outage, degraded connectivity, or hostile conditions; and\
l) safe handling of restricted, community-sensitive, sovereign-sensitive, or public-authority-sensitive materials.

IOC security input shall not replace formal security review, privacy review, legal review, or Board approval where required. It shall strengthen those processes by providing operational intelligence and field realism.

#### 225.10 IOC Role in Implementation Burden, Equity, and Institutional Capacity

The IOC shall consider implementation burden and equity. Public-good systems often fail when designed for well-resourced institutions while claiming universal applicability. The IOC shall help GCRI US identify whether operational requirements exclude smaller nonprofits, community institutions, local governments, universities, under-resourced public agencies, or lower-capacity partners.

The IOC may examine:

a) staffing requirements;\
b) technology costs;\
c) cloud and compute costs;\
d) cybersecurity maturity requirements;\
e) training burden;\
f) reporting burden;\
g) maintenance and support expectations;\
h) data availability;\
i) accessibility and language issues;\
j) local infrastructure constraints; and\
k) dependence on external consultants.

Where implementation burden is excessive, the IOC may recommend simplified models, staged maturity levels, shared infrastructure, open tooling, training supports, or safeguards to prevent exclusion. This aligns with GCRI US’s public-benefit function and WDR-aligned concern that development and institutional transformation require practical capability, not abstract aspiration.

#### 225.11 IOC Handling of Sensitive Operational, Security, and Commercial Information

IOC deliberations may involve sensitive operational, security, infrastructure, or commercial information. Such information shall be handled under classification and need-to-know rules. The Corporation shall not require participants to disclose confidential business information, security vulnerabilities, customer information, proprietary trade secrets, regulated information, or critical-infrastructure details unless the need is clear, lawful, and controlled.

Sensitive IOC material may require:

a) restricted agenda segmentation;\
b) controlled-room treatment;\
c) anonymized examples;\
d) aggregation of lessons learned;\
e) no-record or limited-record handling where appropriate and lawful;\
f) legal or security review before circulation;\
g) exclusion of conflicted competitors;\
h) sanitized output language; and\
i) publication limits.

GCRI US shall prefer public-good lessons and generalized operational patterns over unnecessary disclosure of proprietary or sensitive operational data. The goal is institutional learning, not extraction of commercially or security-sensitive information.

#### 225.12 IOC Relationship to Members, Sponsors, Vendors, and Strategic Partners

The IOC shall maintain disciplined boundaries with members, sponsors, vendors, and strategic partners. A member or sponsor may participate in the IOC only under the same role-bounded rules as others. Sponsorship shall not increase speaking rights, drafting control, output influence, agenda-setting authority, or public-claim privileges unless expressly permitted and safe, and never where it creates capture or private benefit.

The IOC shall ensure that:

a) sponsor status is disclosed where relevant;\
b) vendor interests are declared before technical review;\
c) related-party conflicts are recorded;\
d) participants do not shape outputs for commercial advantage;\
e) member companies do not dominate Council work;\
f) strategic partners do not receive hidden endorsement; and\
g) public communications distinguish participation from approval.

Where a vendor, sponsor, or partner is the subject of discussion, it may be excluded from deliberation, allowed to provide factual information only, or subjected to recusal and no-drafting restrictions.

#### 225.13 IOC Role in Nexus-Aligned Non-Execution Discipline

The IOC may discuss operational feasibility of Nexus-aligned public-good systems, such as evidence rails, risk intelligence workflows, readiness frameworks, data interoperability, secure repositories, and public-sector resilience tools. However, IOC discussion shall remain within GCRI US’s public-good perimeter.

The IOC shall not:

a) route transactions;\
b) select financial intermediaries;\
c) evaluate investment products for market use;\
d) approve insurers, banks, funds, exchanges, brokers, custodians, payment providers, or execution partners;\
e) recommend capital allocation;\
f) approve claims, payouts, triggers, settlement mechanisms, or financial instruments; or\
g) create operational authority for regulated delivery stacks.

Where a discussion concerns how public-good evidence could be usable downstream by licensed actors, the record shall state that downstream execution, if any, belongs to separate lawful actors and is not performed or approved by GCRI US. The IOC may help ensure evidence or standards are operationally coherent; it shall not make them execution-ready in a legal or market sense.

#### 225.14 Interpretive Rule for Industry and Operators Council

This Section shall be interpreted to preserve a controlling proposition: the IOC provides structured operator, infrastructure, technology, implementation, cybersecurity, and deployment-realism input to GCRI US, but it shall not become a vendor-capture forum, procurement channel, commercial endorsement body, market coordination surface, or execution authority.

Where ambiguity exists, the interpretation that better preserves:

a) operational realism without commercial preference;\
b) competition and antitrust safety;\
c) vendor-neutral public-good architecture;\
d) secure and resilient implementation;\
e) no procurement or product endorsement;\
f) protection of sensitive operational information;\
g) disclosure and recusal of commercial interests;\
h) implementation equity and capacity realism; and\
i) non-execution discipline

shall prevail unless a contrary result is required by law.

### 226. Academia and Research Council (ARC) (GCRI United States)

#### 226.1 ARC Purpose and Constitutional Position

The Academia and Research Council, or ARC, shall be the Helix Council through which GCRI US receives structured scientific, scholarly, methodological, epistemic, educational, research-integrity, data-quality, and evidence-review input. The ARC shall exist to strengthen the Corporation’s public-good work by testing whether its outputs are intellectually coherent, methodologically defensible, transparent about uncertainty, reproducible where appropriate, and aligned with the standards of serious research and public-interest knowledge production.

The ARC shall be a deliberative, advisory, and methodological-review Council. It shall not be a university senate, institutional review board, academic publisher, certification body, peer-review substitute, ethics board, grant-awarding body, scientific academy, or final authority over GCRI US institutional positions. Its constitutional role is to provide research-quality input and structured method challenge within the Council Operating System.

The ARC shall support GCRI US by helping the Corporation:

a) distinguish evidence from interpretation, inference, scenario, hypothesis, advocacy, and institutional position;\
b) identify methodological weakness before publication or adoption;\
c) preserve uncertainty, confidence levels, limitations, and dissent;\
d) improve reproducibility, replication, and auditability of evidence claims;\
e) test conceptual frameworks against relevant literature and practice;\
f) prevent overclaim in public-good research and standards work;\
g) strengthen data lineage, provenance, and quality discipline;\
h) ensure that AI-assisted, model-based, or intelligence-derived outputs remain reviewable; and\
i) protect GCRI US from reputational harm arising from weak, exaggerated, or non-replicable knowledge claims.

The ARC is therefore a knowledge-integrity organ inside the Council system. It improves the Corporation’s ability to produce work that can be trusted by public authorities, universities, civil society, communities, funders, technical actors, and other institutions without converting academic participation into institutional certification.

#### 226.2 Scope of Scientific, Methodological, Epistemic, and Research Input

The ARC may consider matters involving scientific method, evidence quality, research design, data provenance, model risk, uncertainty, reproducibility, ontology, taxonomy, systems analysis, AI-enabled research, risk intelligence, resilience metrics, public-good standards, policy evidence, and educational or capacity-building materials.

Within its mandate, the ARC may provide input on:

a) whether a research claim is supported by adequate evidence;\
b) whether uncertainty, limitations, and assumptions are disclosed;\
c) whether data sources, methods, and analytical steps are traceable;\
d) whether evidence has been generalized beyond its valid scope;\
e) whether a model or index requires validation, calibration, sensitivity testing, or independent replication;\
f) whether a taxonomy or ontology is internally coherent and interoperable;\
g) whether a public-good standard is conceptually mature enough for consultation;\
h) whether a policy paper distinguishes descriptive analysis from normative recommendation;\
i) whether AI-assisted outputs require additional verification, red teaming, or audit logs; and\
j) whether publication language creates a false impression of scientific consensus.

The ARC may review draft research reports, standards drafts, policy papers, consultation submissions, risk frameworks, evidence pack templates, technical-method notes, AI governance materials, public-good architecture papers, training curricula, and Nexus-aligned resilience or evidence frameworks. Its review shall focus on knowledge integrity, not corporate approval.

#### 226.3 Limits of ARC Authority and No Replacement of Formal Research Governance

The ARC shall not replace formal research governance, research ethics review, data-protection review, human-subjects review, peer review, journal review, university approval, grant compliance, legal review, safeguards review, security review, or Board adoption. ARC participation may strengthen these processes but shall not substitute for them where they are required.

The ARC shall not:

a) grant research ethics approval;\
b) approve use of personal, sensitive, Indigenous, community, sovereign, controlled, or restricted data outside applicable governance;\
c) certify that a method is scientifically final or universally valid;\
d) represent that academic participants endorse a GCRI US output unless they have expressly done so in an approved capacity;\
e) create university approval, institutional adoption, or scholarly consensus by participation alone;\
f) approve public-good standards as final corporate standards;\
g) certify evidence packs, indices, models, algorithms, AI systems, or technical methods unless a separate authority grants that function;\
h) override safeguards concerns on the basis of academic interest; or\
i) convert research advice into corporate policy without adoption.

Where formal research governance is required, GCRI US shall obtain it through the appropriate channel. Where ARC identifies that such governance is required, the matter shall be escalated before publication or use.

#### 226.4 Peer Review, Reproducibility, Method Challenge, and Evidence Quality Functions

The ARC shall provide structured peer-review-like challenge, reproducibility review, method challenge, and evidence quality input, while preserving the distinction between ARC review and formal external peer review. The ARC may help GCRI US identify what would need to be true for a claim to be reliable, what assumptions must be disclosed, and what additional testing is needed before stronger institutional claims are made.

ARC review may include:

a) methodological logic review;\
b) literature-grounding review;\
c) data-source and provenance review;\
d) uncertainty and confidence-level review;\
e) replication and reproducibility assessment;\
f) sensitivity and robustness review;\
g) bias and measurement-error review;\
h) model-risk and validation review;\
i) scenario and counterfactual review;\
j) ontology and taxonomy review;\
k) evidence-to-recommendation traceability review; and\
l) review of whether public language accurately reflects the strength of evidence.

The ARC may recommend that a draft be strengthened, narrowed, revised, independently reviewed, held for further evidence, subjected to replication, routed to safeguards review, or released only with limitations. Such recommendation shall be recorded, but final adoption remains with the competent authority.

#### 226.5 Research Integrity, Uncertainty Discipline, and Dissent Preservation in ARC

The ARC shall preserve research integrity, uncertainty discipline, and dissent. GCRI US shall not present contested research, early-stage models, expert speculation, or scenario-based conclusions as settled truth. The ARC shall help enforce epistemic humility and prevent the Corporation from overclaiming knowledge in areas of uncertainty.

ARC processes shall require:

a) disclosure of evidence limits;\
b) separation of facts, assumptions, interpretations, and recommendations;\
c) preservation of minority methodological views;\
d) identification of unresolved research questions;\
e) explanation of confidence levels where relevant;\
f) acknowledgment of data gaps;\
g) identification of possible bias or measurement problems;\
h) clarity on whether a method is exploratory, provisional, validated, or mature; and\
i) documentation of dissenting scientific or methodological views.

Dissent shall not be suppressed for narrative neatness, donor confidence, publication timing, or strategic messaging. A serious scientific objection is a value to the Corporation. It may delay output, but it improves trust.

#### 226.6 ARC Output Types, Method Notes, Validity Reviews, and Escalation Functions

The ARC may produce bounded outputs within the Council Operating System. ARC outputs shall be advisory unless adopted through the competent GCRI US authority pathway.

ARC output types may include:

a) methodological review note;\
b) evidence-quality assessment;\
c) reproducibility note;\
d) uncertainty statement;\
e) literature-grounding memorandum;\
f) data-lineage concern;\
g) model-risk warning;\
h) validity review;\
i) replication recommendation;\
j) research-integrity escalation;\
k) dissent or minority method note;\
l) publication-readiness observation; and\
m) escalation memorandum to the Board, Secretariat, safeguards function, security function, legal function, or another Council.

ARC outputs shall include effect coding. A method note may mean “reviewed for methodological considerations,” not “scientifically approved.” A validity review may mean “limitations identified,” not “validated.” An evidence-quality assessment may mean “evidence appears sufficient for consultation,” not “evidence is conclusive.”

Where ARC outputs are included in an adoption-ready decision pack, the pack shall identify the precise role played by ARC and any unresolved caveats.

#### 226.7 No ARC Output May Be Misread as Conclusive Recognition, Binding Certification, or Final Institutional Position Absent Proper Adoption

No ARC output, meeting, concurrence note, review, method memorandum, or participant comment may be presented as conclusive recognition, binding certification, final scientific validation, university endorsement, academic consensus, or final institutional position unless the competent authority has separately adopted that position and the record supports the claim.

This rule applies even where:

a) senior academics participated;\
b) the ARC reached consensus;\
c) a university-affiliated participant helped draft the text;\
d) the method was discussed over multiple sessions;\
e) no participant objected;\
f) the output was circulated publicly; or\
g) the ARC recommended publication.

Academic participation strengthens review. It does not automatically create final authority. GCRI US shall use careful language such as “ARC method note,” “research review input,” “evidence-quality observation,” “methodological concerns identified,” or “ARC advisory recommendation,” unless stronger language has been lawfully authorized.

#### 226.8 ARC Role in AI, Data, Ontology, and Intelligence-Derived Knowledge

The ARC shall have a special role in reviewing AI-assisted, data-driven, ontology-based, model-based, and intelligence-derived knowledge used or produced by GCRI US. Such outputs can appear precise even when they depend on uncertain data, opaque models, weak assumptions, biased sources, or incomplete inference chains.

ARC review in this area may consider:

a) source provenance;\
b) data lineage;\
c) training, retrieval, or input limitations where known;\
d) prompt, model, or analytical reproducibility;\
e) bias and representativeness;\
f) hallucination or inference risk;\
g) ontology coherence;\
h) validation and benchmarking;\
i) human review requirements;\
j) audit-log adequacy;\
k) explainability and contestability; and\
l) conditions under which the output may be cited, published, or relied upon.

The ARC may recommend that AI-assisted outputs be labeled, independently verified, restricted, revised, or excluded from adoption-ready materials until quality gates are met. AI-generated or AI-assisted analysis shall not be treated as evidence merely because it is fluent, quantitative, or technically sophisticated.

#### 226.9 ARC Role in WDR-Aligned Institutional Learning and Development-Relevant Evidence

GCRI US may use the ARC to strengthen development-relevant evidence, institutional learning, resilience analysis, and public-good standards in ways aligned with the broader discipline of development effectiveness, institutional capability, and long-horizon transformation. The ARC shall help ensure that GCRI US outputs do not treat development, resilience, risk, technology, or institutional reform as abstract concepts detached from local capacity, implementation constraints, and evidence quality.

ARC review may ask:

a) whether evidence is context-specific or generalizable;\
b) whether proposed standards assume capacity that many institutions do not possess;\
c) whether metrics reflect actual institutional change or only reporting activity;\
d) whether resilience claims are supported by observable mechanisms;\
e) whether proposed interventions may create dependency, exclusion, or measurement distortion;\
f) whether social, institutional, and technical systems are treated together; and\
g) whether learning loops, correction mechanisms, and evidence updates are built into the model.

The ARC’s role is not to quote development literature. Its role is to ensure that GCRI US’s work reflects serious development-relevant reasoning: context matters, institutions matter, evidence quality matters, and correctionability matters.

#### 226.10 ARC Role in Education, Curriculum, and Capacity-Building Quality

The ARC may review educational, Academy, training, fellowship, curriculum, and capacity-building materials developed by or for GCRI US. This review shall ensure that learning materials are accurate, proportionate, pedagogically coherent, evidence-based, and appropriate to the intended audience.

ARC input may address:

a) learning objectives;\
b) conceptual clarity;\
c) technical accuracy;\
d) evidence basis;\
e) sequencing and progression;\
f) assessment methods;\
g) accessibility of language;\
h) handling of uncertainty;\
i) avoidance of credential overclaim; and\
j) distinction between training completion, competence, certification, and authority.

ARC review of curriculum shall not create academic accreditation, university credit, professional licensure, or formal certification unless separately authorized by competent bodies. GCRI US training may build capacity, but it shall not mislead participants about the status or legal effect of credentials.

#### 226.11 ARC Role in Publication Integrity and Retraction / Correction Discipline

The ARC may support publication integrity by reviewing whether draft publications meet evidence, method, uncertainty, citation, and claim-boundary standards. It may also support correction, clarification, retraction, or supersession where a published output is found to contain methodological error, evidence weakness, overclaim, or materially misleading interpretation.

Publication integrity review may consider:

a) whether claims exceed evidence;\
b) whether citations or sources support key statements;\
c) whether data limitations are disclosed;\
d) whether models or indices are explained;\
e) whether uncertainty is properly framed;\
f) whether dissent or caveats were omitted;\
g) whether public summaries distort technical findings; and\
h) whether correction is required after new evidence emerges.

Where ARC recommends correction, the matter shall be routed to the publication authority, Secretary, Board, legal function, communications function, or relevant committee depending on materiality. Correction is not failure. It is an essential element of public-good knowledge stewardship.

#### 226.12 ARC Safeguards, Research Ethics, and Community Knowledge Boundaries

ARC deliberation shall respect safeguards, research ethics, community knowledge boundaries, Indigenous knowledge protections, privacy, and dignity. Academic interest shall not override rights, consent, confidentiality, or harm prevention.

The ARC shall be especially cautious where research involves:

a) Indigenous knowledge;\
b) community narratives;\
c) vulnerable populations;\
d) personal data;\
e) sensitive geospatial data;\
f) sovereign-sensitive information;\
g) public-authority-sensitive data;\
h) crisis, disaster, conflict, or trauma contexts;\
i) AI analysis of sensitive material; or\
j) publication of findings that may expose persons or communities to harm.

Where needed, ARC shall route the matter to CIC, safeguards, legal, security, privacy, or controlled-room review. Methodological strength does not justify unsafe use of knowledge.

#### 226.13 ARC Records, Attribution, and Academic Independence

ARC records shall preserve review integrity while respecting confidentiality, academic independence, and participant capacity. Minutes shall identify the matter reviewed, key methodological concerns, evidence limitations, dissent, recommendations, and escalation actions. Attribution shall be handled carefully so that academic participants are not misrepresented as endorsing final corporate outputs unless they expressly agree and the record supports that statement.

ARC records shall distinguish:

a) individual expert comment;\
b) working-party note;\
c) Council-level output;\
d) minority view;\
e) unresolved methodological issue;\
f) recommendation for further review; and\
g) adopted corporate position.

Academic independence shall be protected. Participants shall not be pressured to endorse outputs, suppress critique, accelerate review beyond responsible limits, or allow their institutional affiliations to be used for credibility beyond their actual contribution.

#### 226.14 Interpretive Rule for Academia and Research Council

This Section shall be interpreted to preserve a controlling proposition: the ARC provides structured scientific, methodological, epistemic, research-integrity, evidence-quality, data, AI, ontology, publication, and learning input to GCRI US, but it shall not replace formal research governance, safeguards review, peer review, Board adoption, or create final validation, certification, institutional position, or academic endorsement by implication.

Where ambiguity exists, the interpretation that better preserves:

a) research integrity;\
b) uncertainty discipline;\
c) reproducibility and method challenge;\
d) evidence-quality control;\
e) AI and data auditability;\
f) publication correctionability;\
g) safeguards and community knowledge protection;\
h) academic independence;\
i) bounded ARC output effect; and\
j) final adoption by competent authority

shall prevail unless a contrary result is required by law.

### 227. Civil Society and Media Council (CMC) (GCRI United States)

#### 227.1 CMC Purpose and Constitutional Position

The Civil Society and Media Council, or CMC, shall be the Helix Council through which GCRI US receives structured civil-society, media, public-reason, transparency, accountability, communications-integrity, civic-trust, democratic-resilience, public-interest, and social-legitimacy input. The CMC shall exist to ensure that the Corporation’s public-good work remains understandable, contestable, accountable, and socially trustworthy, especially where GCRI US develops outputs touching systemic risk, resilience, sustainability, technology governance, AI-enabled intelligence, public-sector readiness, standards, evidence systems, and Nexus-aligned public-good infrastructure.

The CMC shall be a deliberative, advisory, and public-trust Council. It shall not be a political advocacy organ, campaign committee, media endorsement body, public-relations department, editorial board, activist coalition, lobbying platform, or public mandate mechanism. Its constitutional role is to test public meaning, transparency, accessibility, legitimacy, narrative accuracy, safeguards visibility, and social accountability within the Council Operating System.

The CMC shall help GCRI US ensure that its work can withstand public scrutiny by asking whether:

a) the public can understand what GCRI US is and is not doing;\
b) institutional claims are precise, verifiable, and not overstated;\
c) consultation processes are accessible and meaningful;\
d) affected groups can see their concerns reflected or reasonably answered;\
e) technical and policy materials are legible without losing accuracy;\
f) public-good outputs could be misused for reputation laundering, political signaling, vendor marketing, or institutional overclaim;\
g) safeguards, grievance, and accountability routes are visible; and\
h) public narratives remain aligned with the authoritative record.

The CMC’s value lies in disciplined public-interest challenge. It protects GCRI US from becoming technically sophisticated but publicly illegible, ambitious but socially unaccountable, or visible but imprecise.

#### 227.2 Scope of Civil Society, Public Reason, Communications Integrity, and Transparency Input

The CMC may consider matters involving civil-society participation, public accountability, transparency, communications integrity, media interpretation, public trust, civic legitimacy, social-risk perception, accessibility, consultation design, public-interest externalities, misinformation risk, stakeholder understanding, and narrative discipline.

Within its mandate, the CMC may provide input on:

a) whether public-facing materials are clear, accurate, and proportionate;\
b) whether GCRI US descriptions distinguish nonprofit stewardship from execution-side activity;\
c) whether membership, Council participation, partnerships, funding, or public-authority engagement are described without overclaim;\
d) whether consultation materials are accessible to non-specialist audiences;\
e) whether public-good claims are supported by record and evidence;\
f) whether communications could mislead donors, members, public authorities, communities, media, or the public;\
g) whether transparency is sufficient without exposing protected information;\
h) whether public narratives respect safeguards, dignity, and participation boundaries;\
i) whether technical terms require plain-language explanation;\
j) whether the Corporation’s outputs could be misunderstood as certification, endorsement, regulatory approval, or market validation; and\
k) whether public trust would be strengthened by correction, clarification, dissent disclosure, or more careful framing.

The CMC may review public reports, consultation submissions, policy papers, website language, membership materials, Council summaries, public announcements, annual reports, campaign narratives, event descriptions, public-good framework summaries, and adoption-ready decision packs where public meaning is material.

#### 227.3 Limits of CMC Authority and No Conversion Into Political Advocacy Surface

The CMC shall not convert GCRI US into a political advocacy surface or partisan platform. The Corporation may engage in lawful public-benefit policy education, consultation, research communication, standards literacy, and public-good dialogue, but the CMC shall not use its position to issue partisan endorsements, campaign positions, electoral statements, lobbying directives, media campaigns, or political mandates unless separately lawful, Board-approved, and consistent with nonprofit restrictions.

The CMC shall not:

a) speak for GCRI US unless expressly authorized;\
b) issue political endorsements or opposition statements;\
c) claim to represent civil society as a whole;\
d) treat media participation as media endorsement;\
e) treat civil-society participation as public mandate;\
f) override Board-approved communications controls;\
g) direct public campaigns outside authority;\
h) publish statements that expose protected persons or sensitive records;\
i) convert Council deliberation into advocacy pressure against trustees, officers, staff, members, or external parties; or\
j) use GCRI US channels for factional, partisan, or private campaigns.

The CMC may critique public meaning, transparency, and accountability. It may recommend stronger language, narrower claims, more accessible summaries, corrected statements, or greater public explanation. It may not substitute its preferences for corporate authority, legal review, Board judgment, safeguards protection, or records discipline.

#### 227.4 Participation Integrity, Accessibility, and Contestability Functions

The CMC shall help GCRI US maintain participation integrity, accessibility, and contestability in public-facing and Council-facing processes. Participation integrity means that people and institutions asked to provide input understand the purpose, scope, use, limits, risks, and effect of their participation. Accessibility means that materials and processes are usable by the intended audiences. Contestability means that participants can question assumptions, submit objections, and see how concerns are handled.

The CMC may review whether consultation and participation processes:

a) state the question clearly;\
b) identify what is open for comment and what is not;\
c) provide sufficient background without unnecessary jargon;\
d) disclose how input will be used;\
e) include meaningful comment periods;\
f) provide accessible formats where feasible;\
g) support multilingual or plain-language needs where appropriate;\
h) protect participants from retaliation or public exposure;\
i) include under-resourced or affected voices;\
j) preserve dissent and unresolved concerns; and\
k) provide comment disposition or reasoned response.

The CMC shall not treat volume of participation as proof of legitimacy. A thousand superficial responses may be less useful than a small number of well-handled, representative, rights-sensitive, and carefully recorded contributions. The Council shall focus on quality, fairness, safety, and responsiveness.

#### 227.5 Public Narrative, Legibility, Safeguards, and Social Trust Review Functions

The CMC shall provide public narrative, legibility, safeguards, and social trust review. This function is particularly important where GCRI US develops advanced concepts that may be misunderstood by public audiences, including evidence rails, risk intelligence, AI-supported knowledge systems, standards frameworks, resilience finance interfaces, national-readiness models, public-good technology, and Nexus-aligned institutional architecture.

The CMC may review whether public materials:

a) explain the Corporation’s public-benefit purpose in plain and accurate language;\
b) avoid unexplained internal terminology;\
c) state what GCRI US does not do;\
d) clearly separate public-good stewardship from regulated execution;\
e) distinguish pilots, proposals, drafts, adopted policies, and operational systems;\
f) avoid inflated language about scale, adoption, funding, or authority;\
g) describe safeguards, complaints, correction, and accountability pathways;\
h) avoid instrumentalizing vulnerable, community, Indigenous, civil-society, media, or public-sector participation;\
i) avoid implying consensus where dissent exists; and\
j) preserve trust by being precise rather than promotional.

Social trust review shall ask whether a reasonable public reader would understand the status of a claim. If the answer is no, the claim shall be revised, qualified, or routed for public-claims review before publication.

#### 227.6 CMC Output Types, Participation Reviews, and Escalation of Public-Interest Risks

The CMC may produce bounded outputs within the Council Operating System. Such outputs shall be advisory unless adopted by the competent GCRI US authority.

CMC output types may include:

a) public-legibility note;\
b) communications-integrity review;\
c) transparency recommendation;\
d) participation-integrity review;\
e) consultation-accessibility note;\
f) public-trust risk warning;\
g) social-license overclaim warning;\
h) misinformation or misinterpretation risk note;\
i) public-summary improvement memorandum;\
j) safeguards visibility recommendation;\
k) civil-society concern note;\
l) media-risk observation;\
m) dissent or public-interest objection; and\
n) escalation memorandum to the Board, Secretariat, communications function, safeguards function, legal function, records function, or another Council.

The CMC shall escalate public-interest risks where public communication may mislead, where participation is being overclaimed, where civil-society or media involvement is being used as endorsement, where consultation has become performative, where safeguards are not visible, where affected voices are absent, or where the Corporation’s narrative is drifting away from the authoritative record.

Escalation shall identify the specific claim, material, process, or public risk; why it matters; what correction or review is recommended; and whether publication should be paused pending review.

#### 227.7 No CMC Output May Be Treated as Public Mandate, Media Endorsement, or Political Position of GCRI US

No CMC output, meeting, participant comment, consultation summary, public-legibility note, civil-society concern, media-risk observation, or CMC recommendation may be treated as a public mandate, media endorsement, civil-society endorsement, political position, campaign authorization, or final institutional statement of GCRI US unless the competent authority separately adopts such position through proper procedure.

This rule applies even where:

a) journalists, editors, civil-society leaders, nonprofit executives, advocates, or communications experts participated;\
b) the CMC reached consensus;\
c) the output concerns public messaging;\
d) a public-facing summary was drafted;\
e) participants did not object to publication; or\
f) the topic is urgent or publicly salient.

Participation is not endorsement. Review is not adoption. Public-interest concern is not political mandate. The CMC shall use controlled language such as “CMC advisory note,” “public-legibility review,” “civil-society input,” “communications-integrity concern,” or “public-trust risk observation,” unless stronger language is formally authorized.

#### 227.8 CMC Role in Preventing Institutional Overclaim and Reputation Laundering

The CMC shall have a special function in preventing institutional overclaim and reputation laundering. GCRI US’s public-good role, Council architecture, global-risk language, and Nexus-aligned institutional ambition may attract participants who seek reputational benefit from association. The CMC shall help ensure that association is not misused.

The CMC may identify and escalate overclaim where a person or institution suggests that:

a) participation equals partnership;\
b) attendance equals endorsement;\
c) Council membership equals certification;\
d) consultation equals approval;\
e) media participation equals media support;\
f) civil-society involvement equals social license;\
g) public-sector discussion equals government backing;\
h) draft review equals adoption; or\
i) GCRI US has recognized a person, product, standard, platform, institution, or initiative without record.

The CMC may recommend public-claims correction, participant notice, website clarification, marks-control action, membership discipline, Council-status restriction, or integrity escalation. This function protects the Corporation from being used as a credibility wrapper for external agendas.

#### 227.9 CMC Role in Transparency Without Unsafe Disclosure

The CMC shall help GCRI US calibrate transparency without unsafe disclosure. Public trust requires transparency, but not every record can be public. The Corporation must protect whistleblowers, personal information, Indigenous and community-sensitive knowledge, security information, legal privilege, personnel matters, controlled-room materials, donor confidentiality where appropriate, and unfinished deliberation.

The CMC may advise on:

a) what should be public;\
b) what should be summarized;\
c) what should be redacted;\
d) what should remain internal or controlled;\
e) what minimum transparency is necessary;\
f) how to explain non-disclosure without creating suspicion;\
g) how to publish dissent or consultation outcomes safely; and\
h) how to correct public misunderstanding without exposing protected information.

The CMC shall not demand full disclosure where disclosure would harm persons, breach law, compromise security, destroy privilege, or violate safeguards. Its role is disciplined transparency, not uncontrolled publication.

#### 227.10 CMC Role in Countering Misinformation, Misinterpretation, and Narrative Drift

The CMC may support GCRI US in identifying misinformation, misinterpretation, and narrative drift affecting the Corporation’s work. Narrative drift occurs when repeated shorthand, public excitement, partner language, media summaries, or internal jargon causes the public meaning of GCRI US activity to depart from the authoritative record.

The CMC may review and recommend correction where public materials misstate:

a) the Corporation’s legal status;\
b) its nonprofit and non-execution role;\
c) its relationship with GCRI Canada, GRF, GRA, or other entities;\
d) the status of Councils, members, partners, or participants;\
e) the adoption state of standards or frameworks;\
f) the maturity of public-good technology;\
g) the meaning of evidence outputs;\
h) the existence of funding, endorsement, or government support; or\
i) the status of pilots, proposals, or programs.

The CMC may recommend a clarification note, FAQ, public correction, internal communications guidance, revised terminology, or publication hold. It shall not engage in reactive public disputes without authorization. The goal is correctionable truth, not reputational combat.

#### 227.11 CMC Role in Public-Facing Language for High-Complexity Nexus and Risk Concepts

The CMC shall help translate high-complexity concepts into public-facing language without distorting their substance. GCRI US may work with concepts such as systemic risk, anticipatory governance, resilience intelligence, evidence rails, AI-enabled analysis, public-good infrastructure, standards interoperability, national readiness, and Nexus-aligned development finance interfaces. These concepts can become exclusionary or misleading if explained poorly.

The CMC may recommend:

a) plain-language definitions;\
b) public-safe diagrams or summaries;\
c) disclaimers for non-execution and non-certification;\
d) distinctions between research, consultation, adoption, and deployment;\
e) explanations of uncertainty and limitations;\
f) FAQs addressing likely public confusion;\
g) language suitable for non-specialist audiences;\
h) avoidance of inflated or militarized terminology where unnecessary; and\
i) accessible explanations of safeguards and accountability.

The Council shall not dilute technical meaning to the point of inaccuracy. Its role is to improve legibility while preserving precision.

#### 227.12 CMC Role in Media Participation and Journalistic Independence

Where media professionals participate in the CMC, GCRI US shall respect journalistic independence and avoid any implication that media participants endorse, promote, or represent the Corporation. Media participation may help the Corporation understand public interpretation, misinformation risk, transparency expectations, and narrative clarity. It shall not be used to secure favorable coverage, suppress scrutiny, or imply press endorsement.

Media-related controls shall ensure that:

a) media participants’ capacity is clear;\
b) off-record, background, embargo, or attribution rules are explicit where used;\
c) participation does not compromise journalistic independence;\
d) GCRI US does not use journalists’ names for credibility without consent;\
e) Council participation is not conditioned on favorable coverage;\
f) sensitive information is handled under agreed classification; and\
g) media input is recorded without converting it into editorial support.

The CMC may include media expertise, but it shall not become a communications channel for unmanaged leaks or reputational leverage.

#### 227.13 CMC Records, Attribution, and Public-Safe Summaries

CMC records shall preserve transparency review, public-legibility concerns, participation-integrity findings, communications-risk warnings, dissent, and escalation actions. Records shall be detailed enough to prove that public-interest concerns were considered, but careful enough to protect participants, sensitive comments, and unfinished deliberation.

CMC records shall identify:

a) matter reviewed;\
b) public-facing material or process assessed;\
c) participant capacity where appropriate;\
d) public-claims issues identified;\
e) consultation and accessibility concerns;\
f) dissent or unresolved public-interest issues;\
g) recommendations;\
h) publication or correction requests;\
i) escalation route; and\
j) classification of output.

Attribution shall be controlled. Civil-society or media participants shall not be named in public summaries as endorsers unless they have expressly approved that use. Public-safe summaries shall focus on the issue and recommendation, not on prestige of participants.

#### 227.14 Interpretive Rule for Civil Society and Media Council

This Section shall be interpreted to preserve a controlling proposition: the CMC provides structured civil-society, media, public-reason, transparency, communications-integrity, accessibility, safeguards-visibility, and social-trust input to GCRI US, but it shall not become a political advocacy organ, media endorsement body, public mandate mechanism, or public-relations substitute for corporate authority and record integrity.

Where ambiguity exists, the interpretation that better preserves:

a) public-claims accuracy;\
b) civil-society and media independence;\
c) transparency without unsafe disclosure;\
d) accessible consultation;\
e) public-legibility discipline;\
f) safeguards visibility;\
g) no political or media overclaim;\
h) prevention of reputation laundering;\
i) correction of misinformation and narrative drift; and\
j) adoption only through competent authority

shall prevail unless a contrary result is required by law.

### 228. Community and Indigenous Council (CIC) (GCRI United States)

#### 228.1 CIC Purpose and Constitutional Position

The Community and Indigenous Council, or CIC, shall be the Helix Council through which GCRI US receives structured community, Indigenous, local, place-based, lived-context, rights-sensitive, dignity-centered, and affected-population input. The CIC shall exist to ensure that the Corporation’s public-good work is not designed only from institutional, technical, financial, policy, academic, or media vantage points, but is tested against the realities of people and communities who experience systemic risk directly.

The CIC shall be a safeguards-heavy deliberative and advisory Council. It shall not be a substitute for Indigenous government, tribal authority, community consent, rights-holder consent, public consultation required by law, social license, treaty process, government-to-government process, research ethics approval, grievance process, or community approval mechanism. Its constitutional role is to provide protected, structured, and carefully bounded input into GCRI US work, while preventing the instrumentalization of community and Indigenous participation.

The CIC shall support GCRI US by helping the Corporation understand:

a) how systemic risks are experienced locally and unevenly;\
b) how climate, water, energy, food, health, biodiversity, infrastructure, digital, and institutional risks interact at community level;\
c) how public-good frameworks may unintentionally create exclusion, surveillance, extraction, displacement, stigma, or administrative burden;\
d) how community trust is built or lost;\
e) how Indigenous knowledge, land relationships, cultural context, and sovereignty-sensitive concerns must be protected;\
f) how consultation can become extractive if participation is requested without respect, benefit, feedback, protection, or remedy;\
g) how technical systems, AI, data, evidence, or standards may affect lived realities; and\
h) how GCRI US can preserve dignity, correctionability, and accountability in its public-benefit work.

The CIC exists because public-good legitimacy cannot be built only through high-level institutions. It must also be tested against place, memory, harm, trust, rights, and lived consequence.

#### 228.2 Scope of Community, Indigenous, Local-Truth, and Lived-Context Input

The CIC may consider matters involving community impact, Indigenous knowledge boundaries, local risk perception, lived experience, place-based resilience, disaster experience, infrastructure fragility, environmental stress, public health disruption, food and water insecurity, digital exclusion, institutional distrust, civic vulnerability, social protection, cultural continuity, land-sensitive concerns, and participation safety.

Within its mandate, the CIC may provide input on:

a) whether GCRI US outputs reflect lived realities rather than only institutional models;\
b) whether risk frameworks account for compound harms across water, energy, food, health, biodiversity, infrastructure, climate, and digital systems;\
c) whether proposed evidence systems risk extracting data without reciprocal benefit;\
d) whether community participation is meaningful, safe, compensated where appropriate, and not merely symbolic;\
e) whether Indigenous knowledge or community-sensitive information is being generalized or appropriated;\
f) whether consultation materials are understandable and accessible to intended participants;\
g) whether outputs may increase surveillance, exclusion, stigma, or administrative burden;\
h) whether grievance and correction pathways are visible and credible;\
i) whether public narratives use communities as proof of legitimacy without recorded basis; and\
j) whether safeguards, remedy, and non-retaliation measures are adequate.

The CIC may review policy papers, standards concepts, risk frameworks, public-good technical designs, consultation plans, Academy materials, evidence templates, public narratives, safeguards protocols, community-engagement tools, and any adoption-ready output with material community or Indigenous implications.

#### 228.3 Limits of CIC Authority and No Instrumentalization of Community or Indigenous Participation

The CIC shall not be used to imply community consent, Indigenous consent, tribal approval, affected-population endorsement, local mandate, or social license beyond the precise recorded scope of participation. Participation by one person, group, organization, community representative, Indigenous knowledge-holder, or local actor shall not be generalized to a whole people, nation, tribe, community, region, demographic, or affected population unless an explicit lawful or customary mandate exists and is recorded.

The CIC shall not:

a) bind any Indigenous government, tribal nation, community, local organization, or affected population;\
b) replace government-to-government engagement where required;\
c) replace free, prior, and informed consent processes where applicable;\
d) provide social license for projects, technologies, data systems, financial mechanisms, public-sector actions, or corporate initiatives;\
e) authorize use of Indigenous knowledge, cultural material, local data, or community narratives outside recorded permissions;\
f) approve research involving communities where formal ethics, consent, or safeguards review is required;\
g) validate public claims of community endorsement;\
h) permit community stories to be used as fundraising, branding, or legitimacy assets without consent and context; or\
i) allow powerful institutions to use CIC participation to neutralize criticism.

The CIC’s legitimacy depends on restraint. Its purpose is to protect participation and improve institutional learning, not to convert participation into blanket approval.

#### 228.4 Safeguards, Protected Participation, and Dignity Protections in CIC Processes

CIC processes shall operate under enhanced safeguards, protected participation, and dignity protections. Community and Indigenous participation may involve unequal power, historical harm, trauma, cultural sensitivity, local political risk, public exposure risk, employment risk, social retaliation, or mistrust of institutions. GCRI US shall therefore design CIC participation as a protected process, not a casual consultation.

CIC safeguards shall include, as appropriate:

a) clear explanation of purpose, scope, risks, and use of input;\
b) voluntary participation and withdrawal options;\
c) informed consent for attribution, recording, publication, and quotation;\
d) role-marker or anonymized participation where needed;\
e) protection against retaliation or public exposure;\
f) accessible materials and participation formats;\
g) reasonable accommodation and language support where feasible;\
h) compensation, honoraria, travel support, or participation support where appropriate and lawful;\
i) trauma-informed facilitation where sensitive harms are discussed;\
j) safeguards review before publication of community-sensitive outputs;\
k) grievance and correction pathways; and\
l) restrictions on reuse of sensitive input outside the matter for which it was provided.

Dignity protections shall require respectful process, non-extractive listening, no tokenization, no symbolic naming without consent, no coercive consensus, and no use of community participation as institutional decoration.

#### 228.5 Rights-Sensitive, Land-Sensitive, and Community-Sensitive Deliberation Rules

The CIC shall apply rights-sensitive, land-sensitive, and community-sensitive deliberation rules where matters involve Indigenous rights, tribal sovereignty, land, territory, water, biodiversity, cultural heritage, local livelihoods, displacement, infrastructure siting, environmental harm, health risk, digital surveillance, policing, emergency powers, community data, or other sensitive contexts.

Such deliberation shall consider:

a) who is affected;\
b) who has authority to speak;\
c) whose knowledge is being used;\
d) what consent or permission is required;\
e) what harms may result from disclosure;\
f) whether knowledge is sacred, confidential, restricted, culturally sensitive, or community-held;\
g) whether publication could expose persons or places to harm;\
h) whether risk maps, geospatial data, or evidence outputs could be misused;\
i) whether community concerns require safeguards, legal, privacy, security, or Board review; and\
j) whether the matter should be handled in a controlled room or through a separate engagement protocol.

The CIC shall not pressure participants to disclose knowledge that should remain protected. GCRI US shall respect that some knowledge is not for institutional extraction, publication, modelling, or standardization.

#### 228.6 CIC Output Types, Challenge Pathways, and Grievance-Linked Functions

The CIC may produce bounded outputs within the Council Operating System. Such outputs shall be advisory unless adopted through the competent GCRI US authority pathway and shall be subject to enhanced handling where needed.

CIC output types may include:

a) community-impact note;\
b) Indigenous knowledge boundary note;\
c) lived-context memorandum;\
d) participation-safety review;\
e) dignity and non-extraction warning;\
f) accessibility and inclusion recommendation;\
g) local-risk observation;\
h) rights-sensitive concern;\
i) land-sensitive or place-sensitive warning;\
j) grievance-linked escalation;\
k) safeguards referral;\
l) community consultation summary;\
m) dissent or objection note; and\
n) public-safe summary recommendation.

The CIC may also identify matters requiring grievance intake, safeguards review, Board escalation, legal review, privacy review, security review, controlled-room handling, public-claims correction, or consultation redesign.

Where a CIC concern relates to harm, misuse of participation, unsafe disclosure, retaliation, community misrepresentation, Indigenous overclaim, or unaddressed grievance, it shall be routed through protected escalation. GCRI US shall not treat such concerns as ordinary editorial comments.

#### 228.7 No CIC Output May Be Appropriated, Generalized, or Overclaimed Outside Recorded Scope and Safeguards Basis

No CIC output, participant comment, community narrative, Indigenous knowledge contribution, local-risk observation, consultation summary, grievance-linked note, or lived-context memorandum may be appropriated, generalized, published, quoted, commercialized, transformed into public claim, or used as institutional endorsement outside the recorded scope and safeguards basis.

This rule applies even where:

a) the participant gave useful input;\
b) the output is powerful for public narrative;\
c) the comment supports GCRI US’s position;\
d) the matter is urgent;\
e) the participant did not object during the meeting;\
f) a staff member believes the content is already public; or\
g) the Corporation intends to use the content for public-good purposes.

Before using CIC-derived input publicly, GCRI US shall confirm:

i) consent or permission;\
ii) attribution preference;\
iii) publication class;\
iv) community or Indigenous knowledge boundaries;\
v) harm risk;\
vi) context required to avoid distortion;\
vii) whether anonymization is needed; and\
viii) whether safeguards review is required.

Community and Indigenous input is not raw material for institutional messaging. It is entrusted knowledge.

#### 228.8 CIC Role in Preventing Extractive Consultation and Tokenistic Legitimacy

The CIC shall have a special role in preventing extractive consultation and tokenistic legitimacy. Extractive consultation occurs when an institution seeks community input to improve legitimacy, fundraising, design, or public narrative without meaningful reciprocity, protection, response, or benefit. Tokenistic legitimacy occurs when participant names, identities, communities, or stories are used to signal inclusion while actual decision-making remains unchanged.

The CIC may identify extractive or tokenistic patterns, including:

a) repeated requests for community input without feedback;\
b) use of community stories without consent or remedy;\
c) consultation after decisions are already made;\
d) inaccessible or overly technical materials;\
e) no compensation or support where participation burden is substantial;\
f) failure to explain how input was used;\
g) public naming of participants without consent;\
h) pressure to agree with institutional framing;\
i) erasure of dissent; and\
j) use of Indigenous or community language for credibility without governance substance.

Where such patterns appear, the CIC may recommend redesign, pause, additional consultation, safeguards intervention, public-claims correction, or Board escalation.

#### 228.9 CIC Role in Community Data, AI, Geospatial, and Evidence Governance

The CIC shall provide input on community data, AI, geospatial, and evidence governance where outputs may affect communities or Indigenous peoples. Risk intelligence, evidence systems, remote sensing, AI analysis, and geospatial tools can produce public value, but they can also expose communities to surveillance, misclassification, stigma, extraction, land conflict, insurance exclusion, policing risk, or other harm.

The CIC may review whether:

a) community data is necessary and proportionate;\
b) consent and lawful basis are adequate;\
c) geospatial outputs could expose sensitive locations;\
d) AI analysis may misclassify or stereotype communities;\
e) data governance respects Indigenous data sovereignty principles where relevant;\
f) community-sensitive findings require controlled publication;\
g) public maps or dashboards could be misused;\
h) evidence packs include context and limitations;\
i) affected communities have challenge or correction pathways; and\
j) benefits and risks are fairly distributed.

Where data or AI risks are material, CIC input shall be coordinated with ARC, IOC, CMC, security, privacy, safeguards, and legal functions as appropriate.

#### 228.10 CIC Role in Water, Energy, Food, Health, Biodiversity, and Infrastructure Nexus Realities

The CIC shall help GCRI US understand the lived nexus realities of water, energy, food, health, biodiversity, housing, mobility, digital access, and critical infrastructure. These systems are often experienced as one combined daily resilience condition, even where institutions govern them separately.

The CIC may identify how disruptions interact:

a) water insecurity affecting health and food;\
b) energy outages affecting medical devices, refrigeration, communications, and heat safety;\
c) food insecurity interacting with income, transport, and public health;\
d) biodiversity and land degradation affecting livelihoods and cultural continuity;\
e) flooding, wildfire, heat, storms, and drought affecting local infrastructure;\
f) digital outages affecting access to benefits, warning systems, education, and emergency response; and\
g) administrative fragmentation forcing communities to navigate multiple systems during crisis.

This input shall help GCRI US produce more realistic public-good frameworks. A risk model that separates systems on paper may fail communities in practice. CIC input helps prevent that failure.

#### 228.11 CIC Relationship to Tribal Sovereignty, Indigenous Governance, and U.S. Legal Context

In the United States context, the CIC shall be especially careful where participation involves tribal sovereignty, Indigenous governance, Native nations, Indigenous organizations, Native communities, or Indigenous knowledge holders. GCRI US shall not collapse Indigenous participation into generic community consultation.

The Corporation shall recognize that:

a) tribal nations may have sovereign governmental status;\
b) Indigenous organizations and individuals may not speak for tribal governments unless authorized;\
c) Indigenous knowledge may have cultural, spiritual, land-based, or collective dimensions not reducible to ordinary data;\
d) consent and representation rules may vary by nation, community, and context;\
e) public disclosure may create cultural, legal, economic, or physical harm; and\
f) Indigenous participation should be handled with respect for self-determination, dignity, and record accuracy.

Where matters require government-to-government engagement, the CIC shall not substitute for that process. Where matters involve Indigenous knowledge or data, special handling and permission rules shall apply.

#### 228.12 CIC Role in Remedy, Correction, and Feedback Loops

The CIC shall support remedy, correction, and feedback loops where community or Indigenous input identifies harm, misunderstanding, exclusion, misrepresentation, or unsafe process. The Council shall not merely receive concerns; it shall help route them into institutional correction.

Possible correction routes include:

a) revision of public materials;\
b) correction of community or Indigenous overclaim;\
c) withdrawal of unsafe language;\
d) additional consultation;\
e) safeguards review;\
f) controlled-room treatment;\
g) grievance intake;\
h) Board escalation;\
i) public-safe correction;\
j) modification of data or AI use; and\
k) closure note explaining what changed.

The CIC shall insist that communities and Indigenous participants are not asked to repeat the same concerns without response. Feedback loops shall demonstrate that input mattered, even where GCRI US cannot accept every recommendation.

#### 228.13 CIC Records, Attribution, Confidentiality, and Public-Safe Summaries

CIC records shall be handled with enhanced confidentiality, attribution control, and safeguards review. Records shall preserve institutional learning while preventing exposure, appropriation, or misuse of community-sensitive information.

CIC records shall distinguish:

a) individual comment;\
b) community organization input;\
c) Indigenous knowledge contribution;\
d) authorized representative statement;\
e) personal lived-experience testimony;\
f) general community-impact observation;\
g) restricted or non-public knowledge;\
h) grievance-linked information;\
i) public-safe summary; and\
j) material requiring controlled-room handling.

Attribution shall require explicit consent. Public summaries shall be sanitized and contextualized. Where a participant requests anonymity or role-marker attribution, the Corporation shall respect that request unless law requires otherwise.

The CIC shall not allow meeting minutes to become a repository of sensitive community knowledge available to persons without need to know.

#### 228.14 Interpretive Rule for Community and Indigenous Council

This Section shall be interpreted to preserve a controlling proposition: the CIC provides structured community, Indigenous, local, lived-context, rights-sensitive, and safeguards-heavy input to GCRI US, but it shall never be used to imply broad consent, community mandate, Indigenous approval, social license, data permission, or public legitimacy beyond recorded scope, consent, and safeguards basis.

Where ambiguity exists, the interpretation that better preserves:

a) dignity and protected participation;\
b) Indigenous and community knowledge boundaries;\
c) no overclaim of consent or representation;\
d) non-extractive consultation;\
e) local and lived-context intelligence;\
f) community data and AI safeguards;\
g) rights-sensitive and land-sensitive handling;\
h) grievance and remedy pathways;\
i) attribution control; and\
j) public-safe, non-appropriative use of input

shall prevail unless a contrary result is required by law.

### 229. Cross-Council Joint Sessions and Shared Deliberation (GCRI United States)

#### 229.1 Circumstances Justifying Joint Sessions

Cross-Council joint sessions may be convened where a matter before GCRI US requires structured deliberation across more than one Helix Council because the matter has public-authority, operational, scientific, civil-society, media, community, Indigenous, safeguards, security, or public-interest implications that cannot be responsibly reviewed through a single Council alone.

Joint sessions may be appropriate where a matter concerns:

a) systemic risk frameworks affecting public institutions, operators, communities, researchers, and civil society;\
b) public-good technical architecture with legal, operational, public-trust, and community implications;\
c) evidence systems, AI tools, risk intelligence, or geospatial outputs that combine method, data, implementation, public-claims, and safeguards concerns;\
d) standards proposals that may affect public authorities, industry operators, academic credibility, civil-society legitimacy, and community rights;\
e) resilience frameworks involving water, energy, food, health, biodiversity, infrastructure, climate, digital systems, or emergency governance;\
f) consultation outputs requiring public-sector feasibility, research quality, social trust, and community-sensitive review;\
g) public narratives that may be technically accurate but socially unclear, politically sensitive, or at risk of overclaim; and\
h) unresolved disagreement between Councils requiring structured reconciliation.

A joint session shall not be convened merely for visibility, ceremony, public relations, stakeholder optics, or convenience. Joint deliberation increases procedural complexity and must be justified by the substance of the matter. Where a single Council can review a matter adequately, the matter should remain within that Council’s ordinary pathway.

#### 229.2 Cross-Council Agenda Formation and Routing Discipline

A cross-Council agenda shall be formed through the Council Operating System and shall identify the precise matter, Councils involved, reason for joint treatment, questions to be addressed, expected output, classification, handling rules, and routing after deliberation. Joint sessions shall not become open-ended plenaries in which every issue is discussed without docket discipline.

The cross-Council agenda shall specify:

a) the matter ID or case ID;\
b) the originating Council or function;\
c) the Councils invited;\
d) the decision or review question;\
e) the materials to be reviewed;\
f) the classification and handling class;\
g) the expected output type;\
h) the chairing and rapporteur arrangements;\
i) conflict, recusal, and competition-safety instructions;\
j) whether dissent or separate Council notes will be accepted; and\
k) the route for escalation, adoption, revision, or closure.

The Secretariat or designated Council support function shall ensure that joint session materials are distributed only to eligible participants, with appropriate classification. Where different Councils require different levels of access, materials shall be segmented. Joint deliberation shall not become a reason to widen access to sensitive information beyond need-to-know.

#### 229.3 Preservation of Council-Specific Mandates Within Joint Sessions

Each Council shall preserve its own mandate within joint sessions. Joint deliberation shall not erase the distinct constitutional function of the PAC, IOC, ARC, CMC, or CIC. Each Council contributes a different kind of intelligence, and those differences must remain visible in the record.

Accordingly:

a) PAC input shall remain public-authority, public-law, administrative, public-finance, and institutional feasibility input;\
b) IOC input shall remain operational, implementation, infrastructure, cybersecurity, interoperability, and supportability input;\
c) ARC input shall remain methodological, scientific, epistemic, evidence-quality, AI, data, and research-integrity input;\
d) CMC input shall remain public-trust, transparency, communications-integrity, accessibility, civil-society, media, and public-reason input; and\
e) CIC input shall remain community, Indigenous, lived-context, rights-sensitive, safeguards, dignity, and local-truth input.

A joint session shall not collapse these voices into a generic stakeholder consensus. If PAC identifies public-law risk, IOC identifies implementation risk, ARC identifies evidence uncertainty, CMC identifies public-overclaim risk, and CIC identifies community harm risk, those observations shall be preserved as distinct contributions rather than merged into vague agreement.

#### 229.4 Conflict, Recusal, and Handling Controls in Cross-Council Deliberation

Cross-Council sessions shall apply heightened conflict, recusal, competition, safeguards, security, and handling controls because multiple constituencies and knowledge systems are present at once. A participant may be eligible to participate in one Council’s review but conflicted or restricted in another aspect of the matter.

Before a joint session, the Council Operating System shall review:

a) participant affiliations;\
b) donor, sponsor, vendor, member, public-authority, academic, media, community, Indigenous, and execution-side conflicts;\
c) commercially sensitive information;\
d) public-law and procurement sensitivity;\
e) controlled-room or restricted-access needs;\
f) personal, community, Indigenous, or rights-sensitive information;\
g) research integrity or publication conflicts; and\
h) whether any participant should be excluded from a segment, limited to factual input, or recused from drafting.

Where competition-sensitive industry participation is present, the meeting shall avoid market conduct, pricing, bids, procurement preferences, client information, or confidential business strategy. Where CIC-sensitive material is discussed, attribution, consent, and knowledge-boundary controls shall apply. Where PAC-sensitive material is discussed, public-authority capacity and public-description controls shall apply. Where ARC-sensitive material is discussed, uncertainty and evidence limitations shall be preserved. Where CMC-sensitive material is discussed, public-claims discipline shall apply.

#### 229.5 Joint Outputs, Concurrence Notes, Dissent Capture, and Resolution of Disagreement

Joint sessions may produce joint outputs only where the involved Councils agree on the output type, effect, and wording under the Council Operating System. A joint output shall not be presumed merely because multiple Councils met together. If the Councils reach different conclusions, those differences shall be recorded.

Joint outputs may include:

a) cross-Council advisory note;\
b) concurrence note;\
c) issue map;\
d) unresolved-risk register;\
e) safeguards and public-claims warning;\
f) adoption-readiness condition list;\
g) multi-domain review memorandum;\
h) consultation synthesis;\
i) escalation memorandum; or\
j) recommendation for further review, redrafting, controlled-room handling, or Board consideration.

Where disagreement remains, the record shall identify:

i) the point of disagreement;\
ii) the Council or participants raising it;\
iii) the reason for disagreement;\
iv) whether the disagreement concerns evidence, feasibility, public law, safeguards, public meaning, or authority;\
v) whether further review is required; and\
vi) whether the matter may proceed despite the disagreement.

Dissent shall not be erased to manufacture cross-Council unity. A cross-Council process that honestly preserves unresolved disagreement is stronger than one that hides disagreement to accelerate publication.

#### 229.6 No Joint Session May Erase Council Distinctions or Create Hidden Plenary Authority

No joint session may erase Council distinctions or create hidden plenary authority. A joint session is a procedural mechanism for shared deliberation, not a new corporate organ, super-Council, plenary assembly, Board substitute, General Assembly substitute, or executive authority.

A joint session shall not:

a) bind GCRI US;\
b) approve Board reserved matters;\
c) issue final institutional positions;\
d) create certification, recognition, routeability, procurement preference, or endorsement;\
e) overrule a Council’s own mandate or dissent;\
f) create permanent cross-Council authority;\
g) amend Council charters;\
h) bypass safeguards, legal, security, or records review; or\
i) convert advisory output into adopted policy.

If a cross-Council structure is needed on a continuing basis, it shall be separately chartered as a coordination mechanism, working party, or standing process under this Part. It shall not emerge through repeated joint meetings without authority.

#### 229.7 Public Description and Publication Rules for Cross-Council Work

Public description of cross-Council work shall be accurate, bounded, and classification-aware. GCRI US may describe that a matter received cross-Council review where the record supports that statement. It shall not describe cross-Council review as approval, adoption, endorsement, certification, public mandate, government mandate, industry validation, academic consensus, civil-society support, media endorsement, community consent, or Indigenous approval unless a separate lawful record supports that precise claim.

Public summaries shall state, where appropriate:

a) which Councils reviewed the matter;\
b) the nature of review;\
c) whether the output is advisory or adoption-ready;\
d) whether dissent or unresolved issues remain;\
e) whether sensitive details are withheld for safeguards, security, privacy, legal, or public-authority reasons; and\
f) what authority, if any, has adopted the output.

Where CIC input is included, public summaries shall be reviewed for consent, context, attribution, and non-appropriation. Where PAC input is included, public summaries shall avoid implying government endorsement. Where IOC input is included, public summaries shall avoid vendor or procurement implications. Where ARC input is included, public summaries shall avoid overstating scientific certainty. Where CMC input is included, public summaries shall distinguish public-trust review from public mandate.

#### 229.8 Cross-Council Review as Adoption-Readiness Gate

Certain high-consequence outputs may require cross-Council review before they are treated as adoption-ready. The Board, Secretariat, Council Charter, or Council Operating System may classify an output as requiring cross-Council review where it has multi-domain impact.

Cross-Council review may be required for:

a) major public-good standards;\
b) systemic risk frameworks;\
c) national readiness models;\
d) AI or data governance frameworks;\
e) public-facing Nexus-aligned architecture papers;\
f) community-sensitive risk intelligence outputs;\
g) public-sector engagement frameworks;\
h) major consultation submissions;\
i) membership or participation models with public legitimacy implications; and\
j) outputs likely to be cited externally as authoritative.

Where cross-Council review is required, an output shall not advance to adoption-ready status until the required review has been completed, waived by competent authority with recorded reasons, or converted into a lower-effect output. A missing Council review shall be treated as an adoption-readiness defect, not a minor drafting issue.

#### 229.9 Cross-Council Reconciliation and Escalation Where Councils Disagree

Where Councils disagree on a material matter, the Council Operating System shall provide a reconciliation and escalation pathway. Disagreement may concern method, public-law feasibility, operational realism, safeguards, public meaning, community impact, or institutional authority. Each kind of disagreement may require a different resolution route.

Reconciliation may include:

a) revised question framing;\
b) additional evidence gathering;\
c) expert panel review;\
d) controlled-room session;\
e) safeguards review;\
f) legal or compliance review;\
g) security or privacy review;\
h) public-claims review;\
i) separate Council annexes;\
j) minority report; or\
k) escalation to the Board or relevant committee.

Where disagreement cannot be resolved, the output may still proceed if the competent authority determines that the disagreement is recorded, understood, and not fatal to the output’s purpose. However, the disagreement shall remain visible in the decision pack. No authority shall approve an output under the false impression that cross-Council consensus exists.

#### 229.10 Cross-Council Protection Against Capture and Dominance

Joint sessions shall be designed to prevent dominance by the most powerful, best-resourced, most technical, most public, most senior, or most rhetorically forceful participants. Cross-Council deliberation can create imbalance because some sectors are more accustomed to institutional meetings than others. GCRI US shall therefore use facilitation, agenda design, time discipline, and safeguards to prevent capture.

Controls may include:

a) balanced speaking order;\
b) separate Council caucus before joint session;\
c) written submissions before meeting;\
d) structured question rounds;\
e) safeguards facilitator for CIC-sensitive matters;\
f) independent chair where conflicts exist;\
g) separate dissent capture;\
h) no-dominance rules;\
i) accessible materials; and\
j) post-meeting correction window.

Where the CIC or CMC raises participation-safety or public-interest concerns, those concerns shall not be dismissed as less technical. Where the ARC raises uncertainty, it shall not be dismissed because operators want speed. Where the IOC raises operational infeasibility, it shall not be dismissed because policy language is elegant. Where the PAC raises public-law risk, it shall not be dismissed because strategic ambition is strong. Each Council’s contribution must be weighed in its own domain.

#### 229.11 Cross-Council Records, Case Linkage, and Institutional Learning

Cross-Council work shall be recorded through case linkage so that future users can understand how a matter moved through the Council system. The record shall show which Councils reviewed the matter, what each Council contributed, what disagreements emerged, what output was produced, what was escalated, and whether the matter was adopted, revised, held, or closed.

The cross-Council record shall include:

a) case ID;\
b) originating Council or function;\
c) Councils participating;\
d) agenda and materials;\
e) participant categories and recusals;\
f) classification and handling rules;\
g) domain-specific findings;\
h) joint findings;\
i) dissent or minority notes;\
j) unresolved issues;\
k) escalation route;\
l) final output status; and\
m) closure or adoption record.

This record shall support institutional learning. GCRI US should be able to look back and see whether public-law concerns were ignored, implementation risks were later confirmed, methodological warnings were valid, public-trust concerns affected uptake, or community-sensitive concerns were addressed. Cross-Council records create learning loops, not only compliance evidence.

#### 229.12 Interpretive Rule for Cross-Council Joint Sessions and Shared Deliberation

This Section shall be interpreted to preserve a controlling proposition: cross-Council joint sessions allow GCRI US to deliberate on multi-domain matters through structured shared review while preserving Council-specific mandates, safeguards, competition safety, records discipline, dissent, and the advisory nature of Council outputs.

Where ambiguity exists, the interpretation that better preserves:

a) justified use of joint sessions;\
b) docketed agenda formation;\
c) distinct Council mandates;\
d) heightened conflict and handling controls;\
e) honest dissent and disagreement capture;\
f) no hidden plenary authority;\
g) accurate public description;\
h) adoption-readiness gates;\
i) anti-capture facilitation; and\
j) cross-case learning

shall prevail unless a contrary result is required by law.

### 230. Council Constituting Instruments and Charter Requirements (GCRI United States)

#### 230.1 Mandatory Charter or Constituting Instrument for Each Council

Each Helix Council of GCRI US shall operate only under a written Council Charter or constituting instrument approved by the competent corporate authority. No Council shall be recognized, convened, described publicly, assigned a docket, seated with participants, or permitted to issue outputs unless its mandate, scope, authority, limits, membership structure, procedures, safeguards, records, and publication rules have been formally recorded.

A Council Charter shall be mandatory for:

a) the Public Authorities Council;\
b) the Industry and Operators Council;\
c) the Academia and Research Council;\
d) the Civil Society and Media Council;\
e) the Community and Indigenous Council;\
f) any temporary or thematic Council-like body;\
g) any cross-Council mechanism with continuing function; and\
h) any Council bureau, committee, working party, expert mechanism, or special review body requiring delegated process.

The Charter shall be the Council’s controlling authority map. It shall identify what the Council may do, what it may not do, who may participate, how participation is recorded, how outputs are created, how dissent is preserved, how sensitive matters are handled, and how outputs move from deliberation into adoption-ready pathways where applicable.

No Council may rely on inherited practice, informal precedent, invitation letters, website descriptions, event agendas, public announcements, or participant expectations as substitute authority. A Council exists through its Charter and operates within that Charter.

#### 230.2 Minimum Clauses for Council Charters

Each Council Charter shall contain minimum clauses sufficient to make the Council lawful, usable, bounded, and auditable. The Charter shall be drafted in precise governance language and shall avoid vague phrases that could create implied authority, false endorsement, or role confusion.

At minimum, each Council Charter shall include:

a) Council name, abbreviation, and institutional status;\
b) authority source and approval record;\
c) purpose and public-benefit rationale;\
d) scope of subject-matter competence;\
e) exclusions and prohibited acts;\
f) relationship to the Board, officers, Secretariat, executive management, membership authority, governance-spine functions, and other Councils;\
g) participant categories, eligibility, seating rules, and representation controls;\
h) leadership structure, bureau roles, rapporteur functions, and succession rules;\
i) meeting cadence, notice, agenda, quorum, voting, consensus, and dissent rules;\
j) output taxonomy, effect coding, and adoption pathways;\
k) consultation and comment-handling rules;\
l) conflict-of-interest, recusal, competition-safety, and anti-capture controls;\
m) safeguards, protected participation, dignity, accessibility, and non-retaliation rules;\
n) security, privacy, controlled-room, clean-room, and handling rules;\
o) records, minutes, case IDs, registers, repositories, and Gazette or notice integration;\
p) escalation pathways to the Board, committees, officers, legal, safeguards, security, integrity, or management channels;\
q) public-description, attribution, marks-use, and communications rules;\
r) performance review, reporting, and accountability requirements; and\
s) amendment, suspension, reconstitution, sunset, and dissolution procedure.

Where a Council’s subject matter is high-risk, the Charter shall include additional clauses for legal review, special handling, controlled access, independent facilitation, expert review, or Board oversight.

#### 230.3 Purpose, Scope, Authority, Exclusions, Outputs, and Escalation Lanes

Each Council Charter shall state the Council’s purpose, scope, authority, exclusions, output types, and escalation lanes. These clauses shall be written together so that the Council’s institutional effect is clear.

The purpose clause shall state why the Council exists. It shall link the Council to GCRI US’s public-benefit mission, structured participation model, and knowledge domain. It shall not describe the Council as a governing body unless the governing instruments expressly make it one.

The scope clause shall define what the Council may consider. It shall identify relevant domains, such as public authority, industry operations, research method, civil-society transparency, media legibility, community lived context, Indigenous knowledge boundaries, safeguards, or cross-domain risks.

The authority clause shall state that the Council may deliberate, review, advise, challenge, consult, recommend, warn, escalate, and produce bounded outputs within mandate. It shall also state that the Council does not bind GCRI US unless the Board or another competent authority expressly adopts a matter through proper process.

The exclusions clause shall state that the Council may not:

a) approve Board reserved matters;\
b) bind the Corporation;\
c) create contracts or financial commitments;\
d) grant certification, recognition, routeability, endorsement, or public authority;\
e) create membership rights or privileged access;\
f) conduct procurement or market activity;\
g) replace legal, safeguards, security, privacy, research, or fiduciary review; or\
h) perform execution-side activity.

The output clause shall identify permitted output types and their effect. The escalation clause shall identify where serious matters go, including Board, committee, Secretariat, legal, security, safeguards, integrity, records, communications, or management lanes.

#### 230.4 Membership and Representation Structure

Each Council Charter shall define membership and representation structure. The Charter shall distinguish institutional seats, individual expert seats, observer seats, invited expert roles, rapporteur roles, Secretariat support roles, Board liaison roles, management liaison roles, and guest participation.

The Charter shall state:

a) eligibility requirements;\
b) appointment or selection process;\
c) seat allocation principles;\
d) balance and anti-capture controls;\
e) term and renewal rules;\
f) substitution and alternate rules;\
g) attendance and participation expectations;\
h) good-standing requirements;\
i) conflict and disclosure duties;\
j) public-description limits; and\
k) removal, suspension, or challenge procedures.

Where a participant represents an institution, the Charter shall require proof of authorization or a clear statement of non-representative capacity. Where a participant contributes as an individual expert, the record shall not imply institutional endorsement. Where a participant is from a public authority, media organization, Indigenous body, community organization, or regulated entity, special capacity and attribution rules shall apply.

The Charter shall prevent role inflation. A participant seated as observer shall not become a voting member by repeated attendance. A technical adviser shall not become a Council delegate by drafting text. A funder shall not become a member by financial support. A guest shall not become a continuing participant by public association.

#### 230.5 Bureau, Committee, and Secretariat Support Mapping

Each Council Charter shall map the Council’s bureau, committees, working bodies, and Secretariat support arrangements. The Charter shall identify who chairs the Council, who supports agenda formation, who records minutes, who manages the docket, who preserves dissent, who certifies outputs, who handles controlled materials, and who coordinates escalation.

Bureau mapping shall include, as applicable:

a) Council Chair or President;\
b) Vice-Chair or Deputy Chair;\
c) Rapporteur-General or lead drafter;\
d) portfolio leads;\
e) safeguards liaison;\
f) integrity or conflict liaison;\
g) Secretariat coordinator; and\
h) Board or officer liaison where appropriate.

Committee mapping shall identify any standing or temporary Council committees, including credentials, rules, drafting, consultations, safeguards, nominations, expert review, or participation committees.

Secretariat mapping shall identify administrative support for:

i) intake;\
ii) docketing;\
iii) case IDs;\
iv) scheduling;\
v) materials circulation;\
vi) access control;\
vii) meeting minutes;\
viii) output templates;\
ix) consultation logs;\
x) publication coordination; and\
xi) repository and records preservation.

The Secretariat shall support Council validity. It shall not substitute for Council judgment or Board authority.

#### 230.6 Publication Class, Handling, and Controlled-Room Rules

Each Council Charter shall include publication class, handling, and controlled-room rules. Council work may range from public-safe consultation to highly sensitive deliberation involving public authorities, security, Indigenous knowledge, community-sensitive information, personal data, research drafts, commercially sensitive information, legal issues, or whistleblower matters. The Charter must provide a practical classification system.

The Charter shall define:

a) public outputs;\
b) internal outputs;\
c) restricted outputs;\
d) confidential deliberation records;\
e) privileged or legally sensitive materials;\
f) controlled-room materials;\
g) clean-room or need-to-know materials;\
h) public-safe summaries; and\
i) redaction rules.

Controlled-room rules shall specify triggers, access approval, attendance restrictions, device controls, note-taking limits, attribution rules, secure minutes, repository requirements, and publication restrictions. Controlled-room use shall protect sensitive material but shall not be used to hide ordinary disagreement, suppress dissent, avoid transparency, or shield leadership from accountability.

Publication class shall be assigned at intake and reviewed before output release. A Council shall not publish or circulate beyond its classification.

#### 230.7 Review, Amendment, Sunset, and Reconstitution Procedures

Each Council Charter shall include review, amendment, sunset, and reconstitution procedures. A Council may become ineffective, imbalanced, captured, underused, overextended, duplicative, unsafe, or misaligned with GCRI US’s mission. The Charter shall therefore require periodic review.

Review shall assess:

a) whether the Council remains necessary;\
b) whether mandate and scope remain appropriate;\
c) whether composition is balanced;\
d) whether participation is meaningful and safe;\
e) whether outputs are useful and properly bounded;\
f) whether conflicts and capture risks are controlled;\
g) whether records and minutes are adequate;\
h) whether public descriptions are accurate;\
i) whether Secretariat support is sufficient; and\
j) whether Council performance justifies continuation, redesign, or sunset.

Amendments shall require the authority specified in the Charter and shall be recorded. Material amendments affecting mandate, authority, membership, output effect, safeguards, public description, or relationship to the Board shall require Board review.

Sunset or reconstitution shall include records preservation, closure of open dockets, transfer of pending matters, public-description correction, and revocation of expired authorities.

#### 230.8 No Council Charter May Contradict the Bylaw, Mission Lock, or Non-Execution Boundary

No Council Charter may contradict these Bylaws, the Articles, mission lock, nonprofit public-benefit purpose, Board reserved matters, membership rights, safeguards obligations, conflict rules, records discipline, financial controls, legal compliance, public-claims controls, or the non-execution boundary.

A Council Charter shall be void, voidable, severed, revised, or superseded to the extent it purports to:

a) grant corporate authority inconsistent with the Bylaws;\
b) bind GCRI US externally without competent approval;\
c) create execution-side activity;\
d) grant certification, recognition, routeability, or endorsement authority not otherwise authorized;\
e) weaken safeguards or protected participation;\
f) permit public overclaim;\
g) bypass Board reserved matters;\
h) create member rights not approved through proper authority;\
i) allow donor, sponsor, vendor, public-authority, or sector capture; or\
j) override records-first validity rules.

If a Charter conflicts with a higher governing instrument, the higher instrument controls. The Charter shall be corrected promptly.

#### 230.9 Interim Charters for Provisional Councils and Pilot Operations

Where GCRI US is not yet ready to activate a full Council, the Board or competent authority may approve an interim Charter for a provisional Council, pilot Council, scoping group, or time-bound consultation body. An interim Charter shall be narrower than a full Charter and shall clearly state that the body is provisional.

An interim Charter shall include:

a) provisional status;\
b) limited purpose;\
c) duration;\
d) scope of permitted activity;\
e) participant categories;\
f) prohibited public claims;\
g) output limits;\
h) review date;\
i) pathway to full activation or closure; and\
j) records and publication rules.

Public materials shall not describe a provisional body as a fully constituted Council. Interim structures shall not become permanent by inertia. If a provisional body is renewed repeatedly, it shall be reviewed for full constitution, redesign, or termination.

#### 230.10 Charter Controls for Council-Like External Partnerships

GCRI US may participate in external networks, coalitions, roundtables, university partnerships, public-sector consultations, civil-society convenings, community dialogues, or technical working groups. These external structures shall not be described as GCRI US Councils unless formally constituted under this Part.

Where an external partnership performs a Council-like role for GCRI US, the Corporation shall adopt a written interface instrument stating:

a) the external body is not a GCRI US Council unless so constituted;\
b) what input GCRI US may receive;\
c) how the input may be used;\
d) attribution and publication rules;\
e) conflicts and safeguards controls;\
f) records requirements;\
g) public-description limits; and\
h) no binding authority unless separately approved.

This prevents external networks from becoming unrecorded Council substitutes and prevents GCRI US from overclaiming external participation.

#### 230.11 Charter Repository, Public Summaries, and Authoritative Copy Discipline

All Council Charters shall be maintained in an authoritative repository by the Secretary or designated governance function. Current, approved Charters shall be clearly distinguished from drafts, superseded versions, public summaries, redacted versions, and working documents.

The Charter repository shall include:

a) current Charter;\
b) approval record;\
c) effective date;\
d) version history;\
e) superseded versions;\
f) public summary, if any;\
g) related Council operating forms;\
h) seat and participant records;\
i) output taxonomy links;\
j) amendment history; and\
k) review schedule.

Public summaries of Council Charters may be issued where useful, but they shall not replace the authoritative Charter. Public summaries shall describe the Council’s advisory and deliberative nature, limits on authority, and non-execution boundary.

#### 230.12 Interpretive Rule for Council Constituting Instruments and Charter Requirements

This Section shall be interpreted to preserve a controlling proposition: every Council and Council-like body within GCRI US must be constituted by a written, approved, recorded, bounded, and reviewable Charter that defines purpose, scope, authority, exclusions, participation, outputs, safeguards, handling, records, and lifecycle controls.

Where ambiguity exists, the interpretation that better preserves:

a) mandatory Charter discipline;\
b) minimum clause completeness;\
c) clear authority and exclusion language;\
d) role-bounded membership;\
e) bureau and Secretariat mapping;\
f) publication-class and controlled-room rules;\
g) review and sunset discipline;\
h) consistency with mission lock and non-execution;\
i) accurate treatment of provisional bodies; and\
j) authoritative-copy control

shall prevail unless a contrary result is required by law.

### 231. Council Authority Surfaces and Limits (GCRI United States)

#### 231.1 Councils May Deliberate, Propose, Review, Advise, Challenge, and Escalate Within Scope

Each Helix Council of GCRI US may deliberate, propose, review, advise, challenge, and escalate matters within its recorded mandate. Council authority shall be understood as structured institutional input authority, not corporate decision authority. The Councils exist to improve the quality, legitimacy, contestability, and public-interest discipline of GCRI US work by providing organized perspectives from public authorities, operators, researchers, civil society, media, communities, Indigenous participants, and other approved contributors.

Within their respective mandates, Councils may:

a) receive docketed questions from the Board, Secretariat, executive management, committees, officers, governance-spine functions, or other Councils;

b) review draft outputs, frameworks, consultation papers, public-good technical materials, research concepts, standards proposals, participation models, safeguards materials, and public-facing narratives;

c) identify risks, omissions, weak assumptions, public-claims concerns, safeguards concerns, implementation constraints, methodological weaknesses, or stakeholder externalities;

d) propose improvements, conditions, cautions, classifications, escalation routes, or additional review steps;

e) produce advisory notes, warnings, method comments, public-legibility reviews, community-impact observations, public-sector feasibility notes, implementation-readiness observations, and consultation summaries;

f) preserve dissent, unresolved issues, minority views, and alternative interpretations;

g) recommend that a matter proceed, pause, narrow, be revised, be escalated, be held for further evidence, be subjected to safeguards review, or be referred to the Board or another competent authority; and

h) support institutional learning through recorded deliberation and closure.

Council authority shall be strongest when it is precise. A Council may say, for example, that a draft policy paper has public-claims risks, that an evidence model lacks reproducibility, that a community consultation process is unsafe, that a technical architecture is operationally fragile, or that a public-sector implementation pathway is unclear. It may not convert those observations into final corporate action unless the competent authority adopts them.

#### 231.2 Councils May Not Bind the Corporation Externally Absent Express Authority

No Council may bind GCRI US externally unless the Board or another competent authority expressly grants such authority in a written instrument, and unless the act is lawful, mission-aligned, within nonprofit purpose, and consistent with these Bylaws. Council deliberation, consensus, minutes, recommendations, public summaries, participant comments, and Council outputs shall not create contractual, financial, legal, fiduciary, public, regulatory, or execution obligations for the Corporation.

A Council shall not, without express recorded authority:

a) sign or approve contracts, memoranda, grant agreements, sponsorship arrangements, statements of work, partnership instruments, data-sharing agreements, or public commitments;

b) authorize expenditures, reimbursements, funding offers, in-kind commitments, procurement steps, or resource allocations;

c) issue official statements, press releases, institutional positions, consultation submissions, public notices, policy positions, or public commitments in the name of GCRI US;

d) create obligations to members, donors, sponsors, vendors, public authorities, communities, Indigenous bodies, universities, partners, or other entities;

e) approve public use of GCRI US name, marks, Council status, participant status, or institutional affiliation;

f) commit GCRI US to deliver programs, technical infrastructure, publications, training, events, evidence products, standards, or services; or

g) represent that a Council recommendation has been adopted as GCRI US policy.

Any external communication from a Council shall be routed through the approved public communications, records, and authority process. Where a Council output is intended for external release, it shall carry effect coding and public-claims limitations.

#### 231.3 Councils May Not Create Fiduciary Commitments, Public Obligations, or Execution Commitments

The Councils may not create fiduciary commitments, public obligations, legal reliance, operational obligations, financial obligations, or execution commitments. These matters belong to the Board, officers, executive management, or other competent authorities under the governance framework.

A Council may recommend that GCRI US consider a program, revise a standard, publish a note, consult affected participants, or improve a technical framework. It may not commit GCRI US to do so. A Council may identify a risk that should be escalated. It may not independently assume responsibility to resolve it unless authorized. A Council may identify public-interest urgency. It may not create emergency authority.

Councils shall not create:

a) fiduciary duties for trustees beyond those created by law and governing instruments;

b) commitments to fund, compensate, reimburse, support, or resource participants except through approved policy;

c) commitments to publish, adopt, certify, recognize, endorse, or withdraw materials;

d) commitments to engage with a public authority, community, Indigenous body, funder, university, vendor, or member;

e) commitments to implement technical systems, evidence frameworks, risk tools, or public-good infrastructure;

f) execution commitments involving finance, insurance, securities, lending, custody, settlement, payment, routing, procurement, or market activity; or

g) reliance commitments suggesting that external actors may act on Council outputs as authoritative.

Council language shall therefore avoid phrases such as “approved,” “authorized,” “certified,” “recognized,” “mandated,” “committed,” “endorsed,” “procurement-ready,” “execution-ready,” or “officially adopted” unless the competent authority has granted that effect and the record supports it.

#### 231.4 Councils May Not Issue Institutional Positions Outside Approved Output Pathways

No Council may issue institutional positions outside approved output pathways. Council outputs must pass through the Council Operating System, use approved output taxonomy, include effect coding, preserve dissent and limitations where required, and follow publication-class rules. Where a Council output is intended to become a GCRI US institutional position, it must be routed to the proper adoption authority.

A Council output may be:

a) internal advisory input;

b) restricted review note;

c) consultation summary;

d) public-safe Council note;

e) issue warning;

f) dissent or minority note;

g) adoption-ready recommendation;

h) escalation memorandum; or

i) archived deliberation record.

Only the competent corporate authority may convert a Council output into institutional position, policy, public statement, adopted standard, published framework, official consultation submission, or Board-approved action. Until then, the output remains Council-level input.

This rule shall apply even where a Council reaches consensus, where participants are senior, where the output is urgent, where the output is well drafted, where the public would benefit from release, or where external stakeholders expect a position. Quality of drafting does not equal authority.

#### 231.5 Councils May Not Reassign Reserved Matters of the Board or Member Authority

No Council may reassign, absorb, influence improperly, or bypass reserved matters of the Board or member authority. Reserved matters remain reserved even if a Council has subject-matter expertise, strong consensus, or high public legitimacy.

Councils shall not decide or control:

a) amendments to Articles, Bylaws, Council Charters where Board approval is required, or constitutional instruments;

b) Board composition, trustee election, trustee removal, officer appointment, or executive compensation;

c) annual budget, reserves, financial controls, restricted-fund use, or material funding arrangements;

d) major contracts, related-party transactions, inter-entity agreements, or shared-service arrangements;

e) dissolution, wind-down, merger, asset transfer, or successor stewardship;

f) public-good asset transfer, repository governance at constitutional level, or intellectual-property disposition;

g) membership rights, classes, dues, sanctions, or recognition states where reserved;

h) risk appetite, emergency governance, or stop-the-line authority where reserved; or

i) any matter expressly reserved by law, Articles, Bylaws, Board resolution, policy, or delegation matrix.

Councils may provide input into reserved matters only when asked or when their mandate permits advisory escalation. Their input must be framed as input, not decision.

#### 231.6 Councils May Not Bypass Secretariat, Forms-First, or Records-Validity Rules

Councils shall operate through Secretariat-supported, forms-first, records-first procedures. No Council act shall have institutional effect if it bypasses docketing, case identification, agenda control, minutes, output templates, classification, conflict checks, consultation logs, or required closure records.

Councils shall not conduct material governance by:

a) unmanaged email chains;

b) private chat groups;

c) unrecorded calls;

d) personal notes;

e) undocumented side meetings;

f) informal consensus outside a meeting;

g) post-meeting reinterpretation by a chair or rapporteur;

h) staff-drafted “Council positions” not approved through procedure; or

i) public statements issued before record finalization.

The Council Operating System exists to ensure that GCRI US can prove what was asked, who participated, what was reviewed, what was said, what was decided, what was not decided, what dissent existed, what output was produced, and what adoption path remains required. Without that record, Council work may be informative but shall not be relied upon as Council action.

#### 231.7 Councils May Not Create De Facto Membership Classes, Badges, or Recognition States Without Formal Authority

Councils may not create de facto membership classes, badges, recognitions, titles, credentials, participation tiers, partner statuses, expert statuses, institutional rankings, approved lists, certification marks, or recognition states without formal authority. Council participation shall not become a parallel membership system.

A Council shall not create or imply:

a) “PAC-recognized institution”;

b) “IOC-approved operator”;

c) “ARC-validated method”;

d) “CMC-endorsed public-interest partner”;

e) “CIC-recognized community representative”;

f) “Council-certified expert”;

g) “Council-approved vendor”;

h) “GCRI US recognized participant”;

i) “Helix Council badge”; or

j) any equivalent title that suggests institutional status.

Where GCRI US wishes to create membership categories, participation statuses, credentials, public-good badges, or recognition states, such instruments must be created through the proper governance pathway, with Board approval where required, conflict controls, standards, revocation rules, public-claims limits, and records discipline.

Council service may be acknowledged accurately, but acknowledgment shall not imply endorsement, certification, authority, or continuing role.

#### 231.8 Councils May Not Grant Access Rights Outside Approved Security and Handling Rules

Councils may not grant access to restricted information, controlled-room materials, repositories, member data, community-sensitive information, Indigenous knowledge, personal data, public-authority-sensitive information, security materials, privileged materials, draft standards, technical systems, or internal records outside approved security and handling rules.

Council access shall be:

a) role-based;

b) need-to-know;

c) matter-specific;

d) time-bounded where appropriate;

e) classified;

f) logged where required;

g) revocable; and

h) conditioned on confidentiality, conflict, and handling attestations where needed.

A Council chair, rapporteur, participant, working party lead, or Secretariat support person shall not grant access merely because a participant is senior, trusted, useful, affiliated with a donor, affiliated with a public authority, or technically important. Access authority must be separate from deliberative participation authority.

Where a matter involves CIC-sensitive knowledge, PAC public-authority-sensitive material, IOC commercially sensitive material, ARC unpublished research material, or CMC media-sensitive information, access shall be narrowed and controlled.

#### 231.9 Councils May Not Use Participation to Create Apparent Endorsement or External Reliance

Councils shall not permit participation to create apparent endorsement or external reliance. Participants may use accurate descriptions of their role only within public-description rules. They shall not suggest that GCRI US, a Council, or other participants endorse their institution, product, views, project, publication, policy, technology, or initiative because of Council participation.

The Corporation may require participants to avoid statements such as:

a) “selected by GCRI US as a partner” where they are only a Council participant;

b) “endorsed through Helix Council review” where no endorsement exists;

c) “recognized by GCRI US” where no recognition exists;

d) “government-backed through PAC” where no public mandate exists;

e) “community-approved through CIC” where no community consent exists;

f) “scientifically validated through ARC” where no validation exists;

g) “operator-approved through IOC” where no procurement or technical certification exists; or

h) “publicly supported through CMC” where no public mandate exists.

Misuse of Council status may result in correction, suspension, access restriction, removal, public clarification, or integrity review.

#### 231.10 Councils May Not Operate as Shadow Standards, Certification, or Assurance Bodies

Councils shall not operate as shadow standards, certification, or assurance bodies. They may review standards concepts, evidence frameworks, participation procedures, technical assumptions, and public-good outputs, but they shall not create final standards, issue assurance opinions, certify compliance, accredit participants, or determine conformance unless a separate formal standards or assurance process grants that authority.

This is particularly important where GCRI US contributes to Nexus-aligned public-good infrastructure. Council review may help determine whether a framework is understandable, feasible, evidence-informed, rights-aware, and public-safe. It shall not determine that a system conforms to a protocol, that an instrument is finance-ready, that a public authority may rely on it, or that an execution-side actor may use it for regulated activity.

Where standards, assurance, certification, or conformance mechanisms are later created, they must be separated from Council deliberation, governed by their own instruments, and protected from conflicts of interest. Councils may supply input to those mechanisms, but they do not become those mechanisms.

#### 231.11 Councils May Not Override Safeguards, Legal, Security, Privacy, Finance, or Research Controls

Councils may not override safeguards, legal, security, privacy, finance, research, publication, or records controls. Council enthusiasm, consensus, urgency, expertise, or public-interest framing shall not authorize bypass of required review.

A Council output shall be held, revised, escalated, or restricted where:

a) safeguards review is required;

b) protected participation may be affected;

c) legal review is required;

d) personal, community-sensitive, Indigenous, public-authority-sensitive, or controlled information is involved;

e) security or privacy review is required;

f) research ethics or method review is incomplete;

g) financial or donor conditions are implicated;

h) conflicts are unresolved;

i) public-claims controls are not satisfied; or

j) Board reserved matters are involved.

This rule protects Councils themselves. Councils should not be asked to carry legal, safeguards, or security risks that belong to specialized functions.

#### 231.12 Interpretive Rule for Council Authority Surfaces and Limits

This Section shall be interpreted to preserve a controlling proposition: the Helix Councils of GCRI US may deliberate, review, advise, challenge, recommend, and escalate within recorded mandate, but may not bind the Corporation, create external reliance, issue institutional positions, reassign reserved matters, bypass records rules, create recognition states, grant access, endorse participants, or operate as execution, procurement, standards, certification, or assurance bodies.

Where ambiguity exists, the interpretation that better preserves:

a) advisory Council authority;

b) Board and member reserved matters;

c) no external binding effect;

d) no execution or procurement authority;

e) forms-first and records-first validity;

f) no de facto recognition or membership classes;

g) access-control discipline;

h) public-claims restraint;

i) non-substitution for safeguards, legal, security, finance, privacy, research, and records controls; and

j) adoption only through competent authority

shall prevail unless a contrary result is required by law.

### 232. Council Output Types and Controlled Vocabulary (GCRI United States)

#### 232.1 Standardized Output Taxonomy for Council Work

GCRI US shall maintain a standardized output taxonomy for all Helix Council work. No Council output shall be released, relied upon, circulated for adoption, archived as final, or described publicly unless it is assigned an approved output type and effect code. The purpose of this taxonomy is to prevent Council work from being misread as institutional approval, certification, recognition, public mandate, regulatory comfort, procurement preference, or execution authority.

The Council output taxonomy shall distinguish, at minimum:

a) discussion record, documenting that a matter was discussed without creating recommendation or position;

b) advisory note, providing bounded advice within a Council’s mandate;

c) review memorandum, assessing a draft, method, process, framework, or proposal;

d) recommendation, proposing a course of action for consideration by a competent authority;

e) warning, identifying a material risk, defect, overclaim, safeguards issue, or boundary concern;

f) dissent or minority note, preserving principled disagreement or unresolved concern;

g) consultation summary, recording inputs received through a structured consultation;

h) comment disposition log, identifying how comments were accepted, rejected, deferred, or escalated;

i) escalation memorandum, routing a matter to Board, committee, Secretariat, legal, safeguards, security, integrity, records, finance, or management channels;

j) adoption-ready package input, forming part of a decision pack for possible adoption by competent authority; and

k) public-safe summary, communicating Council work externally without overclaim or unsafe disclosure.

The taxonomy shall be mandatory. A Council shall not invent informal labels such as “approved,” “certified,” “validated,” “endorsed,” “recognized,” “cleared,” “official,” “government-backed,” “community-approved,” “industry-approved,” or “market-ready” unless such status is expressly authorized by a separate governing instrument and recorded through competent authority.

#### 232.2 Opinions, Notes, Recommendations, Warnings, Reviews, Memoranda, and Consultation Outputs

Council outputs may take several forms, each with a distinct institutional effect. The form selected shall match the Council’s authority, the matter reviewed, the evidence available, the level of agreement, and the intended use of the output.

An opinion may express a Council’s reasoned view on a question within mandate, but it shall remain advisory unless adopted. A note may record observations, limitations, risks, or practical considerations. A recommendation may propose action, but it shall not authorize action. A warning may require escalation, hold, correction, or further review, but it shall not itself impose final corporate action unless tied to approved stop-the-line authority. A review memorandum may assess a draft or process, but it shall not certify the subject reviewed. A consultation output may summarize comments and public-interest concerns, but it shall not convert participation into consent, endorsement, or public mandate.

Council outputs shall be drafted in full sentences and shall state:

a) the Council or Councils issuing the output;

b) the matter reviewed;

c) the output type;

d) the authority and mandate under which the output is issued;

e) the evidence, materials, or consultation inputs considered;

f) the conclusions, observations, or recommendations;

g) any uncertainty, limitation, dissent, conflict, or unresolved issue;

h) the intended recipient or escalation lane;

i) the effect code; and

j) the publication class.

This structure ensures that every Council output can be read by future trustees, officers, auditors, counsel, staff, members, funders, public authorities, communities, and partners without guessing what the Council meant or what authority it had.

#### 232.3 Distinction Between Advisory, Internal, Consultation, and Adoption-Ready Outputs

Council outputs shall be classified by institutional effect. At minimum, GCRI US shall distinguish advisory outputs, internal outputs, consultation outputs, and adoption-ready outputs.

An advisory output provides Council advice to another organ or function. It may influence Board, committee, management, Secretariat, or publication decisions, but it does not bind them.

An internal output is prepared for internal institutional learning, risk management, draft improvement, or controlled deliberation. It may be restricted from publication because it includes sensitive information, unresolved debate, early-stage analysis, or protected input.

A consultation output records participation, comments, objections, concerns, and disposition of input. It may support transparency and legitimacy, but it does not create consent or endorsement unless the consultation process was expressly designed and lawfully authorized to do so.

An adoption-ready output is a Council output prepared for possible adoption by the Board, officer, committee, executive function, or other competent authority. Adoption-ready status does not mean adoption has occurred. It means the output is sufficiently complete to be considered by the competent authority, subject to all required review gates.

Adoption-ready outputs shall include:

a) authority map;

b) evidence and materials reviewed;

c) safeguards and rights assessment;

d) public-claims boundary;

e) conflict and recusal record;

f) dissent or minority note where material;

g) legal, security, privacy, finance, or research review status where applicable;

h) recommended adoption language; and

i) effect statement if adopted.

No Council shall publicly describe an output as adopted merely because it is adoption-ready.

#### 232.4 Mandatory Effect Coding and Claims Boundary for Each Output Type

Each Council output shall include an effect code and claims boundary. The effect code shall state what the output does and does not do. The claims boundary shall prevent misuse of the output in public communications, fundraising, partnership discussions, member claims, procurement, market activity, academic representation, public-authority engagement, or community representation.

Effect codes may include:

a) For Discussion Only — no recommendation or decision effect;

b) Advisory Input — may inform competent authority, no binding effect;

c) Internal Review — restricted institutional learning, not for public reliance;

d) Consultation Record — records participation and comments, no consent or endorsement effect unless separately stated by lawful authority;

e) Risk Warning — identifies risk and may require escalation or hold under applicable procedure;

f) Adoption-Ready Recommendation — ready for competent authority review, not yet adopted;

g) Escalated Matter — referred to a competent authority or function for action;

h) Public-Safe Summary — externally shareable summary with limited effect; and

i) Closed Without Adoption — archived, no further effect unless reopened.

Claims boundaries shall state, as appropriate, that the output:

i) is not a Board decision;

ii) is not a corporate policy;

iii) is not legal, investment, insurance, regulatory, procurement, or technical certification advice;

iv) does not create member rights;

v) does not certify or recognize any participant;

vi) does not imply government, community, Indigenous, academic, media, industry, or civil-society endorsement;

vii) does not authorize execution-side activity; and

viii) may not be quoted or used outside its publication class.

#### 232.5 Controlled Vocabulary for Council Acts, Statuses, and Lifecycles

GCRI US shall maintain a controlled vocabulary for Council acts, statuses, and lifecycles. The controlled vocabulary shall prevent ambiguity and ensure that terms have consistent meaning across all Councils.

Council act terms may include:

a) docketed — entered into the Council Operating System;

b) admitted — accepted for Council consideration;

c) assigned — routed to a Council, committee, working party, or expert body;

d) under review — active review is underway;

e) consultation open — comments are being received;

f) consultation closed — comments period has ended;

g) draft output — not approved or finalized;

h) Council-approved output — approved by the Council within its advisory authority only;

i) escalated — referred to a competent authority;

j) adoption-ready — complete enough for competent authority review;

k) adopted — adopted only by the competent authority, not by Council alone unless Council has that authority;

l) superseded — replaced by a later output;

m) withdrawn — removed from reliance;

n) closed — no further action pending; and

o) reopened — reactivated under recorded basis.

The term “approved” shall be used carefully. A Council may approve its own advisory output, but that does not mean GCRI US has approved the underlying matter. Public-facing language shall avoid the word “approved” unless the approving authority and effect are clear.

#### 232.6 Invalidity or Non-Operability of Outputs That Do Not Conform to Controlled Vocabulary

A Council output that does not conform to the controlled vocabulary, output taxonomy, effect coding, classification, or records requirements shall be non-operable for institutional reliance until corrected. It may be treated as draft, informal input, or incomplete material, but it shall not be used as a Council output with effect.

Non-conforming outputs may include:

a) outputs without case ID;

b) outputs without issuing Council identified;

c) outputs without output type;

d) outputs without effect code;

e) outputs without classification;

f) outputs using prohibited language such as “certified,” “approved,” or “endorsed” without authority;

g) outputs lacking dissent or limitation records where required;

h) outputs created outside Council procedure;

i) outputs circulated publicly before review; and

j) outputs inconsistent with Council mandate.

Correction may require redrafting, reclassification, reapproval, withdrawal, public correction, or escalation to the Secretariat, Secretary, Board, legal function, safeguards function, or communications-integrity function. Where an output has already been used externally, GCRI US shall consider whether a public-safe correction is required.

#### 232.7 No Council Output May Imply Recognition, Designation, Protocol Effect, or External Approval Without Explicit Authority and Record

No Council output may imply recognition, designation, protocol effect, conformance, certification, routeability, external approval, public authority, community consent, Indigenous consent, academic validation, media endorsement, civil-society mandate, industry endorsement, procurement preference, or market readiness without explicit authority and authoritative record.

This rule shall apply to all Council output language, including titles, subtitles, headings, executive summaries, public summaries, certificates, letters, email cover notes, website descriptions, social media posts, event slides, consultation materials, and partner communications.

A Council output shall not state or imply that:

a) a person or institution is recognized by GCRI US;

b) a method has been certified;

c) a technology has been approved;

d) a public authority supports a position;

e) a community or Indigenous group has consented;

f) a vendor is preferred;

g) a framework is market-ready;

h) a standard has protocol effect;

i) a participant has earned a credential; or

j) an output is binding on external actors.

Where an output may be misunderstood, it shall include a limitation statement. Where limitation language would make the output less attractive for public narrative, that is not a reason to omit it. Truthful limitation is a core discipline of the Council system.

#### 232.8 Council Output Drafting Standards and Legal-Meaning Discipline

Council outputs shall be drafted with legal-meaning discipline. Words that create reliance, status, endorsement, or authority shall be avoided unless intended and authorized. The drafting standard shall be precise, non-promotional, accurate, and suitable for future audit.

Council outputs shall distinguish:

a) observation from finding;

b) concern from determination;

c) recommendation from approval;

d) consultation from consent;

e) participation from endorsement;

f) review from validation;

g) feasibility input from procurement preference;

h) methodological comment from peer-reviewed conclusion;

i) public-sector perspective from government position;

j) community input from community mandate; and

k) adoption-ready from adopted.

Outputs shall avoid inflationary wording. The stronger the public meaning of a word, the stronger the authority record required to use it.

#### 232.9 Council Output Version Control, Supersession, and Withdrawal

Every material Council output shall be version-controlled. The record shall identify whether the output is draft, final Council output, adoption-ready, adopted by another authority, superseded, withdrawn, or archived.

Version control shall include:

a) output title;

b) output type;

c) case ID;

d) Council or Councils involved;

e) draft number or version number;

f) date;

g) authoring or rapporteur function;

h) approval or finalization record;

i) classification;

j) public release status;

k) supersession relationship; and

l) correction or withdrawal history.

Where an output is superseded, the prior version shall be marked accordingly. Where an output is withdrawn, the withdrawal record shall state whether withdrawal is due to error, changed facts, procedural defect, public-claims risk, safeguards concern, authority defect, or other reason.

No person shall rely on a superseded or withdrawn Council output as current.

#### 232.10 Council Outputs in Adoption-Ready Decision Packs

Where a Council output is used in an adoption-ready decision pack, the pack shall preserve the output’s exact effect and limitations. A Council recommendation shall not be rewritten as a finding. A warning shall not be softened into a note. Dissent shall not be removed for readability. A limitation shall not be omitted because it complicates adoption.

The decision pack shall identify:

a) Council output type;

b) Council mandate;

c) materials reviewed;

d) summary of Council input;

e) effect code;

f) unresolved issues;

g) dissent or minority views;

h) required follow-up;

i) whether public release is permitted; and

j) whether the competent authority is asked to adopt, note, reject, defer, or return the output.

The competent authority may accept, reject, modify, or defer a Council output, but it shall not mischaracterize it. Where the competent authority departs from a material Council warning, the decision record should explain why.

#### 232.11 Public Use, Quotation, and Attribution of Council Outputs

Public use, quotation, and attribution of Council outputs shall be controlled. A Council output may be quoted publicly only if its publication class permits, its effect code is preserved, its limitations are not omitted, and its attribution rules are satisfied.

Public use shall not:

a) excerpt language in a misleading way;

b) remove limitations;

c) omit dissent where material;

d) imply adoption where none occurred;

e) use participant names without consent;

f) imply endorsement by a participant’s institution;

g) imply public authority, community, Indigenous, media, academic, or industry support;

h) use restricted outputs as public materials; or

i) use Council outputs for marketing, fundraising, procurement, investor, or regulatory claims beyond authority.

Where Council outputs are referenced externally, GCRI US shall prefer public-safe summaries over full release where sensitive information is involved.

#### 232.12 Interpretive Rule for Council Output Types and Controlled Vocabulary

This Section shall be interpreted to preserve a controlling proposition: every Council output of GCRI US shall be assigned an approved output type, effect code, controlled vocabulary status, classification, authority boundary, and records trail so that Council work can inform the Corporation without being misused as adoption, endorsement, certification, recognition, public mandate, protocol effect, or execution authority.

Where ambiguity exists, the interpretation that better preserves:

a) standardized output taxonomy;

b) precise legal meaning;

c) advisory-effect boundaries;

d) adoption-ready distinction from adoption;

e) controlled vocabulary discipline;

f) non-operability of defective outputs;

g) no implied recognition or external approval;

h) version control and withdrawal discipline;

i) faithful use in decision packs; and

j) public quotation and attribution controls

shall prevail unless a contrary result is required by law.

### 233. Council Composition and Seat Allocation (GCRI United States)

#### 233.1 Institutional Representation Principle for Councils

Council composition shall be designed around institutional representation, expertise, affected-context knowledge, and public-benefit contribution, not prestige aggregation, donor preference, private influence, informal networks, or symbolic inclusion. Each Council shall be composed to serve its constitutional purpose within the GCRI US Helix Council System and shall be calibrated to produce disciplined, balanced, and usable input for the Corporation.

The institutional representation principle shall require that each Council’s composition reflects the kind of knowledge the Council is meant to provide. The PAC shall be composed to understand public authority, administrative feasibility, public-law sensitivity, and public-sector accountability. The IOC shall be composed to understand infrastructure, operations, deployment, cybersecurity, and supportability without vendor capture. The ARC shall be composed to understand research integrity, method, evidence, data, AI, uncertainty, and publication discipline. The CMC shall be composed to understand transparency, public reason, communications integrity, civil-society legitimacy, and media interpretation. The CIC shall be composed to understand community, Indigenous, local, lived-context, rights-sensitive, and safeguards-heavy concerns.

Council composition shall therefore be based on:

a) relevance to Council mandate;\
b) contribution to plural intelligence;\
c) independence and conflict profile;\
d) ability to participate safely and constructively;\
e) capacity to respect confidentiality, safeguards, and records rules;\
f) ability to distinguish personal, institutional, official, and advisory capacities;\
g) absence of disqualifying capture or prohibited overlap; and\
h) commitment to GCRI US’s nonprofit public-good purpose and non-execution boundary.

No seat shall be treated as property of a person, donor, sponsor, institution, sector, public office, community, or network unless a governing instrument expressly creates such seat right. Council seats are entrusted participation positions within GCRI US’s public-benefit architecture.

#### 233.2 Eligibility of Institutions by Class, Standing, and Scope Relevance

Institutional eligibility for Council participation shall be determined by class, standing, scope relevance, integrity profile, and capacity to contribute to the Council’s purpose. Institutions may include, as appropriate, public agencies, universities, research institutions, civil-society organizations, media organizations, community organizations, Indigenous institutions, standards bodies, infrastructure operators, technology organizations, professional associations, philanthropic bodies, and other mission-relevant entities.

Eligibility review shall consider:

a) whether the institution’s purpose is relevant to the Council mandate;\
b) whether the institution is in good legal or operating standing where such review is applicable;\
c) whether the institution’s participation creates conflicts, procurement risk, public-law risk, competition risk, safeguards risk, or reputational risk;\
d) whether the institution has appropriate authorization to designate a representative;\
e) whether the institution’s participation could be misread as endorsement, adoption, certification, public mandate, or market validation;\
f) whether the institution has interests that require recusal, disclosure, or limited participation;\
g) whether the institution can comply with confidentiality, handling, and public-description rules; and\
h) whether participation would strengthen Council quality rather than merely expand optics.

For public authorities, eligibility shall include capacity clarification and public-description safeguards. For operators and industry participants, eligibility shall include competition-safety and vendor-capture review. For academic institutions, eligibility shall include research-integrity and attribution rules. For civil-society and media institutions, eligibility shall include independence and public-claims discipline. For community and Indigenous institutions, eligibility shall include representation, consent, dignity, and knowledge-boundary controls.

#### 233.3 Seat Allocation Rules, Balance Requirements, and Concentration Controls

Each Council Charter shall establish seat allocation rules, balance requirements, and concentration controls. Seat allocation shall be designed to prevent dominance by any single institution, sector, donor, sponsor, geography, ideology, professional class, technical community, or network. Balance does not require artificial equality in every circumstance, but it does require that the Council remain capable of independent, plural, and credible deliberation.

Seat allocation rules may address:

a) number of seats;\
b) institutional seat categories;\
c) individual expert seats;\
d) observer seats;\
e) community or Indigenous participation seats;\
f) public-authority or former-public-authority seats;\
g) academic and research seats;\
h) operator and infrastructure seats;\
i) civil-society and media seats;\
j) geographic, demographic, disciplinary, and functional diversity considerations;\
k) maximum seats held by related entities;\
l) maximum seats connected to one donor, sponsor, vendor, platform, or network; and\
m) rotation requirements.

Concentration controls shall apply where a Council risks being controlled by one sector. In the IOC, no group of vendors, operators, sponsors, or execution-side actors shall dominate. In the PAC, no single public authority category shall be presented as representative of public authority as a whole. In the ARC, no school of thought or research institution shall control methodological conclusions. In the CMC, no advocacy bloc or media affiliation shall define public interest alone. In the CIC, no participant shall be used to overclaim community or Indigenous consent.

Where concentration risk emerges, the Council may be rebalanced, certain seats may be converted to observer status, new participants may be recruited, recusal rules may be imposed, or the Council may be reconstituted.

#### 233.4 Terms of Service, Seat Continuity, and Replacement Procedures

Council seats shall have defined terms of service, continuity rules, and replacement procedures. Participation shall not continue indefinitely by custom, courtesy, relationship, donor preference, or failure to update records. Term discipline is essential to prevent capture, maintain vitality, and ensure that the Council system reflects current institutional needs.

Council term rules shall specify:

a) term length;\
b) effective date;\
c) renewal eligibility;\
d) maximum renewals where applicable;\
e) review cycle;\
f) attendance expectations;\
g) good-standing requirements;\
h) conflict update requirements;\
i) resignation procedure;\
j) replacement procedure;\
k) interim or alternate participation; and\
l) expiry and public-description consequences.

Where an institution holds a seat, the institution may designate a replacement representative only if the Charter permits and the replacement satisfies eligibility, conflict, confidentiality, safeguards, and authorization requirements. Where a person holds an individual expert seat, the seat shall not automatically transfer to an employer, successor, colleague, or affiliated institution.

Seat continuity shall be balanced with renewal. Some continuity is necessary for institutional memory. Too much continuity creates closed culture, insider dominance, and stale assumptions. The Council Operating System shall track terms, renewals, vacancies, and succession.

#### 233.5 Observer Seats, Non-Voting Participants, and Expert Guests

Council Charters may permit observer seats, non-voting participants, invited experts, temporary guests, rapporteurs, technical specialists, public authority observers, Board liaisons, Secretariat support persons, and management liaisons. These roles shall be clearly distinguished from Council membership or voting participation.

Observer and guest roles shall be used where input is valuable but full Council membership would be unnecessary, premature, conflicted, sensitive, or inappropriate. For example:

a) a regulator may observe without creating official position;\
b) a vendor may provide factual technical information without participating in deliberation;\
c) a community participant may join a specific matter without becoming a standing member;\
d) a researcher may brief the ARC on a method without joining the Council;\
e) a journalist may advise on public legibility without endorsing the Corporation; and\
f) a Board liaison may listen for governance issues without controlling Council deliberation.

The record shall state whether observers and guests may speak, submit written comments, access materials, join controlled-room segments, be named publicly, or contribute to outputs. Observers and guests shall not vote unless the Charter expressly grants voting rights. Repeated guest attendance shall not create membership.

#### 233.6 No Single Constituency May Dominate a Council by Default or by Aggregation

No single constituency may dominate a Council by default or by aggregation. Domination may occur directly, where one group holds too many seats, or indirectly, where related institutions, sponsors, vendors, donors, public bodies, networks, or ideological blocs act in alignment. The Council system shall monitor both forms.

Domination may be indicated by:

a) one sector setting most agenda items;\
b) one donor or sponsor shaping participation;\
c) one vendor or platform influencing technical recommendations;\
d) one research network controlling method conclusions;\
e) one public authority category being treated as representative of all public-sector views;\
f) one advocacy position suppressing dissent;\
g) one community voice being used as universal legitimacy;\
h) repeated drafting control by the same participants;\
i) minority views being excluded from records; or\
j) meeting dynamics that deter less powerful participants from speaking.

Where dominance occurs, the Secretariat, Council chair, relevant committee, or Board may impose corrective measures, including seat recalibration, facilitation redesign, agenda controls, recusal, rotation, independent review, additional recruitment, restricted drafting authority, or temporary suspension of the Council.

#### 233.7 Review and Recalibration of Composition Where Capture, Imbalance, or Dead Zones Emerge

Council composition shall be reviewed periodically and whenever capture, imbalance, missing expertise, participation harm, legitimacy deficit, or dead zones emerge. A dead zone exists where a Council lacks the perspectives necessary to perform its mandate, even if it appears numerically full.

Composition review shall consider:

a) whether the Council has the right mix of expertise and lived context;\
b) whether participation is active or nominal;\
c) whether certain seats are ceremonial;\
d) whether under-resourced voices are absent or unable to participate effectively;\
e) whether public-authority participation is overclaimed or under-defined;\
f) whether industry participation creates vendor capture or antitrust risk;\
g) whether academic participation is too narrow or disconnected from implementation;\
h) whether civil-society or media participation reflects public-interest challenge rather than communication optics;\
i) whether community and Indigenous participation is safe, respectful, and non-extractive; and\
j) whether new risk domains require temporary experts or new seats.

Recalibration may include adding seats, retiring seats, changing seat categories, narrowing participation rights, converting members to observers, creating working parties, adding safeguards support, revising charters, or reconstituting the Council. Recalibration shall be recorded and publicly described where necessary to avoid confusion.

#### 233.8 Seat Eligibility for GCRI US Members, Non-Members, and External Participants

Council participation may include GCRI US members, non-members, institutional representatives, external experts, public-interest participants, and invited guests, subject to Council Charter rules. Membership in GCRI US may be relevant to eligibility but shall not automatically entitle a person or institution to a Council seat. Likewise, non-members may be eligible where their expertise, public-interest role, lived context, or institutional knowledge is necessary.

The Charter shall state whether a Council seat requires:

a) membership in good standing;\
b) institutional affiliation;\
c) subject-matter expertise;\
d) public-interest role;\
e) lived-context knowledge;\
f) Indigenous or community mandate;\
g) independence;\
h) conflict clearance;\
i) confidentiality attestation; and\
j) participation training.

Council seats shall not become a hidden membership premium, sponsor benefit, donor benefit, or commercial access channel. Where members receive participation opportunities, the Corporation shall ensure that such opportunities remain consistent with nonprofit purpose, anti-capture controls, and public-description limits.

#### 233.9 Fit-and-Proper Review for Council Participants

Council participants may be subject to fit-and-proper review proportionate to the role, access level, Council mandate, and risk profile. A participant who will access sensitive materials, influence outputs, chair meetings, draft text, participate in controlled-room deliberation, represent an institution, or hold a voting seat shall undergo more rigorous review than a public observer or one-time guest.

Fit-and-proper review may consider:

a) identity and role verification;\
b) institutional authorization;\
c) relevant expertise or lived-context basis;\
d) conflicts of interest;\
e) related-party relationships;\
f) donor, sponsor, vendor, public-authority, media, academic, or community affiliation;\
g) competition-safety risk;\
h) safeguards and conduct history where relevant and lawful;\
i) ability to comply with confidentiality and handling rules;\
j) public-claims and reputation risk; and\
k) compatibility with GCRI US mission and non-execution boundaries.

Fit-and-proper review shall not be used to exclude dissenters or uncomfortable perspectives merely because they may challenge the Corporation. The purpose is integrity and safety, not ideological control.

#### 233.10 Public Description of Council Composition and Participant Capacity

Public description of Council composition shall be accurate, current, and careful. GCRI US may publish Council composition where appropriate, but shall do so only in a manner consistent with participant consent, public-authority rules, media independence, community and Indigenous safeguards, privacy, security, and public-claims discipline.

Public descriptions shall distinguish:

a) Council member;\
b) institutional representative;\
c) individual expert;\
d) observer;\
e) invited guest;\
f) rapporteur;\
g) Secretariat support;\
h) Board liaison;\
i) former participant; and\
j) provisional participant.

Where institutional affiliation is listed, the record shall state whether the person represents the institution or is participating in personal/professional capacity. Public authority participants shall not be listed in a way that implies official endorsement unless authorized. Indigenous and community participants shall not be named without consent and context. Media participants shall not be presented as media endorsers. Industry participants shall not be presented as approved vendors.

#### 233.11 Seat Suspension, Conditional Seating, and Removal for Integrity Reasons

A Council participant or institution may be suspended, conditionally seated, restricted, converted to observer status, removed, or not renewed where integrity, safeguards, conflict, public-claims, competition, security, participation, or mandate concerns require it.

Grounds may include:

a) undisclosed conflict;\
b) misuse of Council status;\
c) breach of confidentiality;\
d) retaliation or harassment;\
e) competition-law concern;\
f) public-authority overclaim;\
g) community or Indigenous representation overclaim;\
h) vendor or sponsor capture behavior;\
i) failure to attend or contribute;\
j) persistent obstruction or abuse of process;\
k) unauthorized public statements;\
l) security or controlled-room breach; or\
m) conduct inconsistent with GCRI US public-benefit mission.

Conditional seating may impose limits on access, voting, drafting, public attribution, or participation in certain matters. Removal shall be recorded and handled with fairness, confidentiality, and due process proportionate to the issue.

#### 233.12 Interpretive Rule for Council Composition and Seat Allocation

This Section shall be interpreted to preserve a controlling proposition: Council composition in GCRI US shall be institutionally designed, balanced, role-bounded, periodically reviewed, and protected against capture, tokenism, overclaim, and dominance, so that each Council can provide credible plural intelligence within its mandate.

Where ambiguity exists, the interpretation that better preserves:

a) institutional representation discipline;\
b) eligibility by mandate relevance;\
c) balanced seat allocation;\
d) term and replacement control;\
e) observer and guest distinction;\
f) anti-dominance controls;\
g) periodic recalibration;\
h) fit-and-proper review;\
i) accurate public description; and\
j) suspension or removal for integrity reasons

shall prevail unless a contrary result is required by law.

### 234. Delegate Roles Within Councils (GCRI United States)

#### 234.1 Primary Representative Role in Council Context

Each Council seat held by an institution, organization, public body, academic body, civil-society organization, media organization, operator, community organization, Indigenous institution, or other approved participant may be exercised through a primary representative where the Council Charter permits institutional representation. The primary representative shall be the principal person authorized to participate in Council deliberation on behalf of the seat-holder or in the capacity recorded for that seat.

The primary representative role shall be role-bounded. It shall not automatically confer authority to bind the seat-holder, bind GCRI US, speak publicly for the Council, approve outputs, access controlled materials, or represent a whole constituency beyond the recorded mandate. The primary representative shall act within:

a) the Council Charter;\
b) the seat-holder authorization;\
c) GCRI US confidentiality, safeguards, and public-description rules;\
d) conflict, recusal, and competition-safety rules;\
e) classification and handling rules;\
f) the Council output taxonomy; and\
g) any specific restrictions attached to the matter under review.

Where a primary representative participates in personal or professional capacity rather than formal institutional capacity, the record shall say so. Where a primary representative participates on behalf of an institution, the record shall identify the authorization source and any limits. Where a public authority, Indigenous institution, community organization, or media organization is involved, the capacity statement shall be especially precise so that participation is not misread as official mandate, consent, endorsement, or public position.

#### 234.2 Deputy and Alternate Representation

Council Charters may permit deputy or alternate representatives to ensure continuity when the primary representative is unavailable, conflicted, recused, incapacitated, or unable to attend. Deputies and alternates shall not participate merely by informal substitution. Their authority must be recorded, verified, and accepted under the applicable Council rules.

A deputy or alternate representative may participate only where:

a) the Council Charter permits deputies or alternates;\
b) the seat-holder has designated the person through an approved process;\
c) the person satisfies eligibility, confidentiality, conflict, safeguards, and handling requirements;\
d) the substitution is recorded for the relevant meeting or period;\
e) the deputy or alternate understands the scope and limits of the role; and\
f) the substitution does not create conflict, competition, public-description, or representation risk.

A deputy or alternate shall not have greater authority than the primary representative. If the primary representative is restricted, conflicted, or denied access to a matter, the deputy or alternate shall not be used to bypass that restriction unless the restriction is personal to the primary representative and the competent authority confirms that substitution is proper.

Repeated alternate participation may require formal role review. A person who regularly participates as an alternate may need onboarding, certification, public-description review, and term tracking similar to a primary representative.

#### 234.3 Advisers, Technical Experts, Rapporteurs, and Invited Specialists

Councils may include advisers, technical experts, rapporteurs, and invited specialists where their participation improves the quality of deliberation, drafting, evidence review, facilitation, or specialized analysis. Such persons shall be admitted under defined roles and shall not acquire Council membership or voting rights unless the Council Charter expressly provides.

An adviser may provide strategic, legal, policy, safeguards, technical, financial, community, or operational input within a defined matter. A technical expert may explain a method, system, risk, tool, dataset, model, or operational constraint. A rapporteur may support text discipline, minutes, synthesis, dissent capture, and output preparation. An invited specialist may contribute knowledge on a particular issue without becoming a continuing participant.

These roles shall be governed by:

a) purpose of invitation;\
b) matter or docket covered;\
c) access level;\
d) confidentiality obligations;\
e) conflict disclosure;\
f) permitted speech or drafting role;\
g) voting status, if any;\
h) attribution rules;\
i) term or session limit; and\
j) record requirements.

Advisers, experts, rapporteurs, and specialists shall not be used as shadow decision-makers. Their function is to support Council judgment, not replace it. Where such persons have commercial, public-authority, academic, donor, media, community, Indigenous, or execution-side interests in the matter, those interests shall be disclosed and managed.

#### 234.4 Observers and Structured Non-Voting Roles

Councils may admit observers and structured non-voting participants where appropriate. Observer roles may be useful for learning, transparency, inter-council coordination, public-authority sensitivity, Board liaison, Secretariat support, donor-safe visibility, or limited participation by a person who should not hold voting or drafting rights.

Observer status shall be carefully defined. An observer may be permitted to attend and listen, but may be restricted from speaking, proposing text, voting, joining controlled-room segments, accessing materials, participating in working parties, or being publicly listed. The Council Charter or meeting notice shall specify the observer’s permissions.

Structured non-voting roles may include:

a) Board liaison;\
b) Secretariat support;\
c) legal or safeguards observer;\
d) public-authority observer;\
e) student or fellow observer;\
f) technical demonstration participant;\
g) community support person;\
h) interpreter or accessibility support person; and\
i) external reviewer attending for a defined segment.

Observers shall not be described as Council members. Attendance by an observer shall not imply endorsement, approval, institutional representation, or adoption. Where observers are present for transparency, the record shall still protect restricted deliberation, personal information, community-sensitive input, Indigenous knowledge boundaries, public-authority sensitivities, and commercial or security-sensitive material.

#### 234.5 Scope of Speech, Proposal, Drafting, and Vote Rights by Role

Each Council Charter shall define the scope of speech, proposal, drafting, and vote rights by participant role. GCRI US shall not rely on informal meeting culture to determine who may shape Council outputs. Participation rights must be clear before deliberation begins.

The Charter shall identify, for each role, whether the person may:

a) receive meeting materials;\
b) attend all or part of meetings;\
c) speak during deliberation;\
d) submit written comments;\
e) propose agenda items;\
f) propose output language;\
g) join drafting groups;\
h) serve as rapporteur;\
i) participate in consensus testing;\
j) vote where voting applies;\
k) submit dissent or minority notes;\
l) access controlled-room materials; and\
m) be named in public outputs.

Speech rights may be broad while vote rights remain narrow. Drafting rights may be restricted where conflicts exist. Public authority participants may speak in personal capacity but not vote on matters that may imply public position. Industry participants may provide feasibility input but be excluded from drafting where vendor preference risk exists. CIC participants may set attribution and use limits for their own contributions. CMC participants may advise on public legibility but not release public statements without authority.

#### 234.6 No Role Inflation by Custom, Repetition, or Prestige

No Council role shall inflate by custom, repetition, prestige, seniority, public reputation, donor support, technical expertise, founder relationship, or continued attendance. A person invited as a guest does not become a member through repeated attendance. A rapporteur does not become a Council decision-maker by drafting text. A technical expert does not become a Council officer by being indispensable. A donor representative does not become a bureau member by funding the Council. A public authority observer does not become an official endorser by remaining in the room.

Role inflation shall be treated as a governance risk because it creates unrecorded authority and public-claims confusion. The Council Operating System shall therefore track:

a) participant role;\
b) access rights;\
c) speaking rights;\
d) drafting rights;\
e) voting rights;\
f) term or session limit;\
g) public-description permissions; and\
h) restrictions or recusals.

Where repeated practice suggests that a role has changed, the Council shall pause and regularize the role through proper authority or correct the practice. Silence shall not be treated as approval of expanded authority.

#### 234.7 Delegate Removal, Substitution, and Challenge Processes

Council Charters shall include processes for removal, substitution, challenge, suspension, or restriction of delegates and other participants. These processes shall protect Council integrity while providing fairness proportionate to the role and issue.

A delegate or participant may be challenged or restricted where there is concern about:

a) lack of authorization;\
b) misrepresentation of capacity;\
c) undisclosed conflict;\
d) prohibited overlap;\
e) breach of confidentiality;\
f) misuse of Council status;\
g) retaliation, harassment, intimidation, or unsafe conduct;\
h) competition-law or procurement risk;\
i) public-authority, community, Indigenous, media, or academic overclaim;\
j) repeated non-attendance or non-performance;\
k) unauthorized disclosure or publication;\
l) security or controlled-room breach; or\
m) conduct inconsistent with GCRI US’s public-benefit mission.

Possible measures may include clarification, warning, recusal, access restriction, conversion to observer status, temporary suspension, replacement request to the seat-holder, removal from a working party, removal from the Council, public-description correction, or referral to safeguards, integrity, legal, or Board review.

Where a seat is institutional, the institution may be asked to nominate a replacement. Where the integrity concern relates to the institution itself, the seat may be suspended or revoked.

#### 234.8 Capacity Statements and Representation Declarations

Each Council participant shall provide a capacity statement or representation declaration where required by the Council Charter. This statement shall clarify whether the person participates:

a) as an authorized institutional representative;\
b) as an individual expert;\
c) as a public authority participant in official, personal, observer, former-office, or technical capacity;\
d) as a community or Indigenous representative with defined mandate;\
e) as a member of civil society or media in independent capacity;\
f) as an operator, vendor, funder, sponsor, or industry participant;\
g) as a Board, Secretariat, management, or staff liaison; or\
h) as an invited guest or technical specialist.

The capacity statement shall also identify limits. If the person cannot speak for their institution, the record shall say so. If the person can provide technical input but not endorse outputs, the record shall say so. If community or Indigenous representation is limited to a specific organization, geography, mandate, or consultation, the record shall say so.

Capacity statements are essential to public-claims discipline. They prevent the Corporation from mistakenly converting personal expertise into institutional endorsement.

#### 234.9 Delegate Duties of Confidentiality, Good Faith, and Institutional Discipline

Council delegates and participants shall owe duties of confidentiality, good faith, and institutional discipline appropriate to their role. These duties are not identical to trustee fiduciary duties, but they are binding participation obligations.

Participants shall:

a) respect confidentiality and classification;\
b) use information only for approved Council purposes;\
c) disclose conflicts and changes in role;\
d) avoid misuse of Council status;\
e) refrain from unauthorized public statements;\
f) respect safeguards and dignity rules;\
g) avoid retaliation or intimidation;\
h) comply with competition-safety rules;\
i) preserve records by using approved channels;\
j) participate honestly and constructively; and\
k) observe non-execution and public-claims boundaries.

Council participation is a public-good trust. A participant may disagree strongly, but must do so within the rules of safety, respect, confidentiality, and truthfulness.

#### 234.10 Delegate Role in Dissent, Minority Notes, and Correction

Delegates shall have structured rights and responsibilities concerning dissent, minority notes, and correction. A delegate may submit dissent where they believe a Council output misstates the record, omits a material concern, overstates consensus, ignores a safeguards issue, weakens evidence discipline, creates public-claims risk, or exceeds Council authority.

The Council Operating System shall provide a path for delegates to:

a) request correction of minutes;\
b) request notation of dissent;\
c) submit a minority note;\
d) identify conflict or recusal concerns;\
e) raise public-claims concerns;\
f) request safeguards review;\
g) request legal, security, or research review; and\
h) escalate unresolved procedural concerns.

Dissent shall be relevant, respectful, timely, and classified appropriately. It shall not be used for personal attack, confidential disclosure, commercial positioning, or obstruction. However, principled dissent is protected and shall not be treated as disloyalty.

#### 234.11 Delegate Public Description, Biography, and Use of Council Affiliation

Delegates and participants may describe their Council role only in accordance with public-description rules. Public description shall be accurate, current, capacity-specific, and non-misleading.

Permitted descriptions may include, where approved:

a) “member of the GCRI US \[Council name] in personal expert capacity”;\
b) “institutional representative to the GCRI US \[Council name]”;\
c) “observer to the GCRI US \[Council name]”;\
d) “rapporteur for \[specific Council or working party]”; or\
e) “invited specialist for \[specific matter]”.

Prohibited descriptions include language suggesting certification, endorsement, partnership, Board authority, officer authority, public mandate, government approval, community consent, Indigenous approval, vendor preference, academic validation, media endorsement, or execution authority.

Council affiliation shall not be used in sales materials, investor materials, procurement bids, regulatory submissions, fundraising materials, political materials, or public campaigns in a way that implies GCRI US approval. Misuse may trigger correction, suspension, or removal.

#### 234.12 Interpretive Rule for Delegate Roles Within Councils

This Section shall be interpreted to preserve a controlling proposition: Council delegates and participants in GCRI US shall hold only the speech, access, drafting, voting, representation, attribution, and public-description rights expressly assigned to their recorded role, and no role may inflate into authority by custom, repetition, prestige, affiliation, or convenience.

Where ambiguity exists, the interpretation that better preserves:

a) primary representative role clarity;\
b) controlled deputy and alternate substitution;\
c) bounded adviser, expert, rapporteur, and guest roles;\
d) observer and non-voting distinction;\
e) role-specific participation rights;\
f) prevention of role inflation;\
g) fair removal and challenge processes;\
h) capacity declarations;\
i) confidentiality and good-faith participation;\
j) protected dissent and correction; and\
k) accurate public description

shall prevail unless a contrary result is required by law.

### 235. Voting Rights, Quorum, and Thresholds in Councils (GCRI United States)

#### 235.1 Quorum Rules by Council and Meeting Type

Each Helix Council shall operate under quorum rules established in its Council Charter, this Part, and the Council Operating System. Quorum shall be the minimum participation condition required for a Council to deliberate formally, approve a Council output, record a Council position within its advisory authority, escalate a matter as Council action, or take any other procedural step requiring Council validity.

Quorum shall be designed to protect legitimacy, balance, and role integrity. It shall not be treated as a mere headcount. For GCRI US Councils, quorum shall consider whether the proper participant categories are present, whether conflicted participants have been excluded, whether under-represented voices have been displaced, whether controlled-room access has narrowed participation, and whether the Council can deliberate responsibly on the matter before it.

A Council Charter may establish different quorum rules for:

a) ordinary meetings;\
b) special meetings;\
c) emergency or time-sensitive meetings;\
d) controlled-room sessions;\
e) consultation review meetings;\
f) output-approval meetings;\
g) bureau meetings;\
h) committee or working-party meetings;\
i) cross-Council joint sessions; and\
j) adoption-ready decision-pack review sessions.

Quorum for ordinary Council deliberation may be lower than quorum for approval of an adoption-ready recommendation, escalation memorandum, warning, public-safe summary, or output that may materially influence Board, public, member, funder, community, or institutional reliance. The more consequential the output, the stronger the quorum requirement should be.

#### 235.2 Constituency-Sensitive Quorum and Balance Protection

Where the subject matter requires plural participation, quorum shall include constituency-sensitive balance requirements. A Council may be numerically present but substantively incomplete if the participants necessary for the matter are absent. For example, a Community and Indigenous Council session addressing community-sensitive input shall not proceed to finalize output if affected-perspective participation is absent without recorded waiver. An Industry and Operators Council session addressing implementation feasibility should not finalize a note if only vendors with commercial interest are present. A Public Authorities Council session should not imply public-sector feasibility if only former officials or observers without mandate participated.

Council quorum rules may therefore require:

a) minimum number of active members;\
b) presence of Council chair or authorized acting chair;\
c) presence of rapporteur or records support;\
d) presence of at least one independent or non-conflicted participant where required;\
e) presence of protected-participation or safeguards support for sensitive matters;\
f) presence of a defined participant class where the matter affects that class;\
g) absence or recusal of conflicted participants from quorum calculation where required; and\
h) confirmation that no single bloc controls the meeting.

Where constituency-sensitive quorum is not met, the Council may discuss the matter for information but shall not finalize a formal output requiring quorum unless the Charter permits a recorded waiver. Any waiver shall state why the missing perspective is not fatal, what compensating process will occur, and whether later consultation is required.

#### 235.3 Simple Majority, Qualified Majority, and Consensus-Seeking Rules

Council Charters may provide for simple majority, qualified majority, consensus-seeking, supermajority, or no-vote advisory procedures depending on the Council’s purpose and the type of output. Voting rules shall be matched to the nature of Council authority. Because Councils are advisory and deliberative bodies, the primary goal is not majoritarian control but reliable, balanced, and well-recorded institutional input.

A simple majority may be appropriate for ordinary procedural matters, approval of routine minutes, scheduling, administrative motions, or low-risk internal notes. A qualified majority may be required for formal Council recommendations, warnings, adoption-ready outputs, public-safe summaries, or escalation memoranda. Consensus-seeking may be required where outputs depend on legitimacy across participant groups, especially in cross-Council, CIC-sensitive, or public-facing contexts.

Consensus-seeking shall mean that the Council makes a good-faith effort to identify a formulation that most participants can accept or live with. It shall not mean that one participant may veto the process for unrelated or obstructive reasons. It shall also not mean that serious dissent is hidden behind artificial consensus.

Where a vote is taken, the record shall identify:

a) the motion or output text;\
b) eligible voters;\
c) quorum;\
d) threshold required;\
e) votes for, against, and abstaining;\
f) recusals and excluded votes;\
g) dissent or minority note requests;\
h) whether the motion passed; and\
i) any conditions or follow-up actions.

#### 235.4 Consent-Gated Questions and Heightened Thresholds

Certain Council matters shall be consent-gated or subject to heightened thresholds because they affect rights, dignity, public meaning, controlled information, community or Indigenous knowledge, public-authority sensitivities, publication risk, or institutional reliance. A consent-gated question is one that may not proceed unless the relevant participant, participant class, safeguards function, or competent authority confirms that the process may continue.

Consent-gated questions may include:

a) attribution of a community, Indigenous, public-authority, media, academic, or institutional participant;\
b) publication of sensitive participant contributions;\
c) use of community stories, lived-experience testimony, or Indigenous knowledge;\
d) conversion of consultation input into public summary;\
e) use of Council output in public-facing materials;\
f) release of controlled-room summary;\
g) disclosure of sensitive operational, security, or commercial information;\
h) publication of dissent where attribution may create risk; and\
i) escalation of a matter involving protected reporting or safeguards concern.

Heightened thresholds may be required for:

i) Council recommendation to publish;\
ii) adoption-ready recommendation;\
iii) Council warning with public-claims implications;\
iv) cross-Council concurrence note;\
v) recommendation to suspend, reconstitute, or redesign a Council process;\
vi) public-safe summary of sensitive deliberation; and\
vii) any output that may be relied upon by the Board, members, public authorities, funders, communities, or external actors.

Where consent is required and not granted, the output shall be revised, restricted, anonymized, held, or escalated. The absence of objection shall not equal consent where express consent is required.

#### 235.5 Abstentions, Recusals, and Disqualified Participation

Council voting and deliberation shall distinguish abstentions, recusals, and disqualified participation. These categories have different meanings and different effects.

An abstention occurs where an eligible participant is present and entitled to participate but chooses not to vote for or against a motion. A recusal occurs where a participant is excluded from deliberation, drafting, voting, access, or some combination because of conflict, sensitivity, role limitation, or other restriction. Disqualified participation occurs where the person is not entitled to participate in the matter because of Charter limits, expired status, lack of authorization, conflict, access restriction, or other rule.

The record shall state:

a) who abstained;\
b) who was recused;\
c) who was disqualified or excluded;\
d) whether the person received materials;\
e) whether the person joined discussion;\
f) whether the person left the room or digital session;\
g) whether the person’s vote was excluded;\
h) whether quorum was affected; and\
i) the basis for the restriction where safe to record.

A participant with a conflict shall not avoid recusal merely by abstaining at the final vote if they influenced deliberation, drafting, or agenda formation. Recusal may require removal from the entire decision chain, not only from the vote.

#### 235.6 Remote Voting and Auditable Verification

Councils may conduct remote voting where permitted by the Charter and Council Operating System. Remote voting shall be auditable, secure, identity-verified, and classification-aware. The Corporation shall not use informal chats, unmanaged polls, private text messages, or unverified email replies for material Council votes unless the Council Operating System expressly permits and preserves an adequate audit trail.

Remote voting procedures shall ensure:

a) voter identity verification;\
b) voting eligibility confirmation;\
c) conflict and recusal screening;\
d) clear motion text;\
e) voting deadline;\
f) secure submission channel;\
g) vote receipt confirmation;\
h) audit log;\
i) tally certification;\
j) preservation of abstentions and dissent requests; and\
k) correction procedure for technical defects.

For sensitive matters, remote voting may require additional safeguards, such as controlled portal access, encrypted submission, Secretariat certification, independent teller, legal or safeguards observer, or post-vote confirmation.

Where technical failure, identity uncertainty, access problem, or classification breach affects the vote, the result shall be held, corrected, re-run, or escalated. Convenience shall not override vote integrity.

#### 235.7 Loss of Quorum and Continuation Restrictions

If quorum is lost during a Council meeting, the Council shall not continue to take formal action requiring quorum. The chair, rapporteur, or Secretariat support shall identify the loss of quorum and record the time, reason, and matters affected.

Upon loss of quorum, the Council may:

a) continue discussion for information only if permitted;\
b) defer the matter;\
c) adjourn and reconvene;\
d) route the matter to written procedure;\
e) convert the session into a consultation or listening session; or\
f) escalate urgent matters through an emergency or protective route where applicable.

The Council shall not finalize recommendations, approve outputs, issue warnings as Council acts, certify minutes, approve public-safe summaries, or adopt adoption-ready materials after quorum is lost unless the Charter permits a specific reduced-quorum procedure and the record supports its use.

Where action is mistakenly taken after quorum is lost, the act shall be treated as defective and subject to correction, ratification where permitted, re-approval, withdrawal, or reclassification as informal input.

#### 235.8 Challenge Windows and Correction of Procedural Errors

Council voting, quorum, and threshold decisions shall be subject to challenge and correction procedures. A participant, chair, rapporteur, Secretariat support person, officer, governance-spine function, or competent authority may raise a challenge where a procedural defect may affect validity or public meaning.

Grounds for challenge may include:

a) defective notice;\
b) wrong Council assignment;\
c) quorum failure;\
d) wrong voting threshold;\
e) ineligible voter;\
f) improper exclusion of eligible participant;\
g) failure to recuse conflicted participant;\
h) unauthorized alternate participation;\
i) remote voting defect;\
j) lack of required consent;\
k) missing dissent record;\
l) output text not matching approved motion;\
m) publication before finalization; or\
n) failure to observe classification rules.

A challenge window shall be specified by Charter, meeting notice, output template, or Council Operating System. Material defects shall be addressed before publication, adoption-ready routing, or external reliance. Correction may include supplemental record, corrected minutes, re-vote, re-notice, reclassification, withdrawal, public-safe correction, or escalation to Board, Secretariat, legal, safeguards, or integrity review.

#### 235.9 Voting Rights by Participant Role and Council Type

Council Charters shall specify voting rights by participant role and Council type. Voting rights shall not be assumed from attendance. A participant’s ability to speak, submit comments, draft text, or advise does not necessarily include voting rights.

Voting eligibility may differ among:

a) standing Council members;\
b) institutional representatives;\
c) individual expert members;\
d) alternates and deputies;\
e) observers;\
f) invited experts;\
g) rapporteurs;\
h) Secretariat support persons;\
i) Board liaisons;\
j) management liaisons; and\
k) participants in controlled-room or cross-Council sessions.

The Charter may provide that only formal Council members vote, that certain categories vote only on procedural matters, that observers never vote, that conflicted industry participants may not vote on vendor-sensitive matters, that public authority observers may not vote where official capacity concerns arise, or that CIC-sensitive matters require consent rather than ordinary vote.

Voting rights shall be recorded and visible to the Secretariat before each meeting. Ambiguity shall be resolved against counting the vote until clarified.

#### 235.10 Council Voting as Advisory Determination Only

A Council vote, even where valid, shall constitute only an advisory Council determination unless the Council has been expressly granted a different effect by competent authority. A Council vote may approve a Council output, authorize escalation, adopt minutes, approve a consultation summary, or recommend action. It shall not make the underlying matter a corporate act.

This rule applies to:

a) Council recommendations;\
b) Council warnings;\
c) Council review memoranda;\
d) cross-Council concurrence notes;\
e) adoption-ready outputs;\
f) public-safe summaries; and\
g) consultation summaries.

Where a Council output is later adopted by the Board or another competent authority, the adoption authority shall be identified separately. Public materials shall not state that GCRI US “approved” a matter merely because a Council voted to recommend it.

Council voting is part of deliberative discipline. It is not a substitute for corporate approval.

#### 235.11 Anti-Manipulation and Anti-Bloc Voting Controls

Council voting shall be protected from manipulation, bloc voting, coercion, retaliation, donor pressure, sponsor pressure, employer pressure, public authority pressure, vendor pressure, political pressure, or community pressure. A Council vote should reflect reasoned participation within role, not external command.

Anti-manipulation controls may include:

a) conflict disclosure before vote;\
b) prohibition on vote-buying or inducements;\
c) restrictions on coordinated bloc voting where it undermines Council purpose;\
d) no retaliation for dissent or abstention;\
e) secret ballot where needed for participant safety;\
f) independent tally for sensitive votes;\
g) separate recording of participant classes;\
h) review of unusual voting patterns;\
i) challenge procedures; and\
j) Board or integrity escalation where manipulation is suspected.

The Corporation shall distinguish legitimate alignment from improper coordination. Participants may agree because they share evidence or reasoning. They may not coordinate votes to secure private advantage, suppress concern, or capture Council output.

#### 235.12 Interpretive Rule for Voting Rights, Quorum, and Thresholds in Councils

This Section shall be interpreted to preserve a controlling proposition: Council voting, quorum, and threshold rules in GCRI US exist to make advisory Council outputs legitimate, balanced, auditable, conflict-managed, and procedurally reliable, without converting Council votes into corporate approval, external authority, certification, endorsement, or execution mandate.

Where ambiguity exists, the interpretation that better preserves:

a) quorum integrity;\
b) constituency-sensitive balance;\
c) appropriate thresholds;\
d) consent-gated protection;\
e) recusal and disqualified-vote discipline;\
f) secure remote voting;\
g) loss-of-quorum controls;\
h) procedural challenge and cure;\
i) role-specific voting rights;\
j) advisory-only effect; and\
k) anti-manipulation protections

shall prevail unless a contrary result is required by law.

### 236. Consensus, Dissent, and Minority Protections (GCRI United States)

#### 236.1 Consensus-First as a Discipline, Not a Veto System

The Helix Councils of GCRI US shall operate, wherever practicable, on a consensus-first basis. Consensus-first means that Councils shall seek reasoned convergence through structured deliberation, careful listening, evidence review, safeguards attention, and fair treatment of materially different viewpoints. It does not mean unanimity at all costs. It does not mean that any one participant, institution, donor, sector, public authority, vendor, academic school, media actor, civil-society bloc, community organization, or Indigenous participant may exercise an unlimited veto over Council work.

Consensus-first shall be understood as a deliberative discipline with the following purposes:

a) to improve the quality of Council outputs before they are escalated, published, archived, or routed for adoption;

b) to reveal assumptions, uncertainty, disagreement, and blind spots before institutional positions are formed;

c) to reduce false polarization by requiring participants to engage the strongest version of competing views;

d) to protect less powerful participants from being overridden by the most resourced, technical, senior, or commercially motivated actors;

e) to distinguish genuine agreement from silence, fatigue, intimidation, or procedural exclusion;

f) to improve legitimacy by showing that material concerns were considered rather than merely outvoted; and

g) to preserve institutional learning where agreement cannot be reached.

Consensus-first shall not be used to delay indefinitely, extract concessions unrelated to the matter, block outputs for private advantage, suppress necessary warnings, or force vulnerable participants to agree to unsafe language. Where consensus cannot be reached, the Council may proceed through the voting, dissent, escalation, or minority-report mechanisms provided in this Part, provided that the absence of consensus is clearly recorded.

#### 236.2 Duty to Preserve Structured Dissent and Minority Views

Each Council shall preserve structured dissent and minority views where disagreement is material to the output, the risks, the evidence, the safeguards, the public meaning, the authority boundary, or the legitimacy of the process. Dissent shall not be treated as embarrassment, disloyalty, inefficiency, or communications inconvenience. In GCRI US’s Council system, dissent is part of knowledge quality and institutional resilience.

Structured dissent may be necessary where:

a) a participant believes the evidence is insufficient, overstated, incomplete, or methodologically weak;

b) a community or Indigenous participant believes participation, attribution, or public use is unsafe or overclaimed;

c) a public-authority participant identifies legal, public-law, administrative, procurement, sovereignty, or regulatory concerns;

d) an operator identifies implementation, cybersecurity, continuity, or vendor-lock-in risk;

e) a civil-society or media participant identifies public-claims risk, transparency weakness, or social-trust concern;

f) a participant believes a Council output exceeds the Council’s mandate;

g) a participant believes a conflict, recusal, or competition issue has not been properly handled;

h) a participant believes a matter should be escalated to the Board, legal, safeguards, security, privacy, finance, or integrity review; or

i) a participant believes the output should not proceed to adoption-ready status.

Structured dissent shall be recorded with enough specificity to preserve meaning, but with handling controls sufficient to protect confidentiality, safety, and lawful process. A dissent record may be public, internal, restricted, anonymized, role-marked, or controlled, depending on the nature of the issue.

#### 236.3 Minority Report and Objection Submission Pathways

Council Charters and the Council Operating System shall provide clear pathways for minority reports and formal objections. A minority report may be submitted by one or more participants, by a participant class, by a Council committee, by a rapporteur noting unresolved issues, or by a Council whose position differs from another Council in a cross-Council process.

A minority report shall include, where appropriate:

a) the matter or case ID;

b) the output or decision being challenged;

c) the participant or group submitting the report, subject to attribution rules;

d) the nature of disagreement;

e) the evidence, safeguard, legal, methodological, public-interest, operational, community, Indigenous, or authority basis for the disagreement;

f) whether the concern affects publication, adoption-readiness, public claims, safeguards, or external reliance;

g) recommended correction, limitation, further review, escalation, or hold;

h) classification and attribution instructions; and

i) whether the submitter requests inclusion in the decision pack, minutes, consultation summary, or restricted record.

A formal objection may be shorter than a minority report and may be used where timing is urgent or where a participant needs to preserve a concern before finalization. The Council Operating System shall allow objections to be submitted before, during, or shortly after a meeting, subject to reasonable deadlines.

Minority reports shall not be edited to change their substance without the submitter’s consent. They may be summarized for public-safe release, but the authoritative version shall be preserved.

#### 236.4 No Suppression of Principled Disagreement for Narrative Neatness

No trustee, officer, Council chair, bureau member, rapporteur, Secretariat staff member, executive, donor, sponsor, partner, communications function, or participant may suppress principled disagreement for narrative neatness, public-relations convenience, donor comfort, publication speed, partner diplomacy, or institutional image management.

Suppression may include:

a) omitting material dissent from minutes;

b) describing contested outputs as consensus;

c) pressuring participants to withdraw objections;

d) delaying or refusing to circulate dissent notes;

e) excluding dissenters from drafting or review without cause;

f) using confidentiality rules to conceal disagreement rather than protect legitimate interests;

g) reframing objections as personal conflict when they concern substance;

h) failing to include unresolved issues in adoption-ready decision packs;

i) publishing public summaries that imply unity where material disagreement exists; or

j) retaliating against participants who record dissent.

Where suppression is alleged, the matter may be escalated to the Secretariat, Secretary, Council bureau, relevant committee, safeguards function, integrity function, Board, or other competent authority. Suppression of material dissent shall be treated as a records and integrity issue, not merely a meeting-management problem.

#### 236.5 Escalation of Unresolved Disagreement to Appropriate Organs or Processes

Where disagreement cannot be resolved within a Council, the matter shall be escalated to the appropriate organ or process. Escalation shall be based on the nature of the disagreement, not on the seniority of the participants or the political convenience of the issue.

Unresolved disagreement may be routed as follows:

a) methodological or evidence-quality disagreement may be routed to ARC, an expert panel, replication review, research-integrity review, or publication review;

b) operational, cybersecurity, interoperability, or deployment disagreement may be routed to IOC, security review, technical review, or implementation-risk review;

c) public-law, public-authority, procurement, regulatory, or sovereignty-sensitive disagreement may be routed to PAC, legal review, or Board review;

d) public-claims, transparency, accessibility, communications, or civil-society legitimacy disagreement may be routed to CMC, communications-integrity review, or public-claims control;

e) community, Indigenous, rights-sensitive, grievance, dignity, or participation-safety disagreement may be routed to CIC, safeguards review, controlled-room process, or protected escalation;

f) conflict, recusal, capture, or integrity disagreement may be routed to the ethics, integrity, governance, or Board process;

g) authority, reserved-matter, or adoption-pathway disagreement may be routed to the Secretary, Board, legal function, or Governance Committee; and

h) urgent risk may trigger stop-the-line or emergency governance procedures where applicable.

Escalation records shall state the issue, why Council resolution was not possible, what authority is asked to review, whether publication or adoption should be paused, and whether any interim protective measure is required.

#### 236.6 Publication and Handling Rules for Dissenting Views

Dissenting views shall be handled and published only according to classification, consent, safety, and legal rules. Some dissent should be public because public trust requires transparency about contested matters. Some dissent must remain restricted because it contains sensitive security, personal, community, Indigenous, public-authority, legal, commercial, or protected-reporting information.

Publication and handling rules shall distinguish:

a) public dissent, which may be included in public summaries or annexes;

b) internal dissent, which informs institutional decision-making but is not released publicly;

c) restricted dissent, which is limited to persons with need to know;

d) anonymized dissent, where identity protection is required;

e) role-marker dissent, where the perspective is identified by role but not by name;

f) controlled-room dissent, where the subject matter requires restricted handling; and

g) privileged or legally sensitive dissent, where counsel or legal process controls disclosure.

Public summaries of dissent shall not distort the substance, omit material limitations, or identify participants without consent. Where dissent is not published, the output may state that dissent or unresolved concerns exist if such statement is safe and accurate.

#### 236.7 Distinction Between Legitimate Dissent and Obstructive Abuse of Process

GCRI US shall distinguish legitimate dissent from obstructive abuse of process. Legitimate dissent raises substantive, procedural, ethical, legal, safeguards, evidence, public-interest, authority, or implementation concerns in good faith. Obstructive abuse uses the language of dissent to delay, harass, intimidate, extract unrelated concessions, protect private interests, disclose restricted information, manipulate process, or prevent the Council from functioning.

Legitimate dissent may be strong, persistent, inconvenient, and critical. It may challenge leadership, donors, technical teams, public authorities, or dominant views. It remains protected where it is made in good faith and relates to the matter.

Obstructive abuse may include:

a) repeated refusal to engage the docketed question;

b) introduction of irrelevant demands to block progress;

c) bad-faith accusations without factual basis;

d) repeated disclosure of restricted information;

e) personal attacks or harassment;

f) intimidation of other participants;

g) use of dissent to advance commercial, political, donor, or factional interest;

h) refusal to follow procedural rulings after fair opportunity to object;

i) strategic submission of late objections to prevent closure without cause; or

j) coordinated disruption by an external bloc.

Where abuse is suspected, the Council chair, bureau, Secretariat, safeguards function, or integrity function may impose time limits, require written submissions, separate issues, restrict conduct, refer the matter for review, or recommend participant removal. The response shall be proportionate and recorded. Process discipline shall not become retaliation against genuine dissent.

#### 236.8 Consensus Documentation and Statement of Remaining Differences

Where a Council reaches consensus, the record shall describe the consensus accurately and shall not overstate it. Consensus may be full, partial, conditional, procedural, or limited to a narrow proposition. The output shall state the scope of agreement and any remaining differences.

A consensus record may identify:

a) the proposition agreed;

b) participants or participant classes involved, subject to attribution rules;

c) whether agreement is full or limited;

d) conditions attached to agreement;

e) unresolved issues;

f) known dissent or abstention;

g) whether the consensus is advisory only;

h) whether further review is required; and

i) whether the output is public, internal, restricted, or adoption-ready.

Where consensus is partial, the output shall not describe the entire matter as resolved. Where participants agree on a warning but disagree on remedy, that distinction shall be preserved. Where participants agree on publication but disagree on wording, that distinction shall be preserved. Where a participant chooses not to object because of fatigue, power imbalance, or safety concern, the process should not rush to claim consensus.

#### 236.9 Minority Protections for Under-Resourced, Community, Indigenous, and Rights-Sensitive Participants

The Council system shall include heightened minority protections for under-resourced participants, community participants, Indigenous participants, rights-sensitive participants, affected persons, whistleblowers, and participants whose institutional position makes dissent risky. Formal equality of speaking time may not be enough where power imbalance affects participation.

Protections may include:

a) pre-meeting briefings;

b) accessible materials;

c) separate caucus or preparation sessions;

d) role-marker or anonymous submission;

e) independent facilitation;

f) trauma-informed meeting design where appropriate;

g) no-retaliation assurances;

h) safe dissent submission pathways;

i) translation, interpretation, or accessibility support where feasible;

j) participation support or honoraria where lawful and appropriate;

k) controlled handling of sensitive input; and

l) opportunity to review public summaries before release where their input is used.

These protections do not give any participant unlimited veto. They ensure that the Council record does not falsely reflect agreement where silence resulted from power imbalance, confusion, fear, or lack of access.

#### 236.10 Dissent in Adoption-Ready Decision Packs

Any adoption-ready decision pack that relies on Council work shall include material dissent, unresolved issues, conditions, warnings, or minority views. The competent authority considering adoption must know whether the Council output is contested and why.

The decision pack shall state:

a) whether the Council output was unanimous, consensus-based, majority-supported, or contested;

b) whether dissent relates to evidence, method, public authority, implementation, safeguards, public claims, community impact, Indigenous knowledge, conflict, or authority;

c) whether dissent was resolved, partly resolved, or unresolved;

d) whether dissent affects publication, adoption, reliance, or implementation;

e) whether further review was requested;

f) whether the authority is being asked to proceed despite dissent; and

g) reasons for accepting, rejecting, deferring, or conditioning adoption despite dissent.

A competent authority may adopt an output despite dissent, but it shall do so knowingly and with recorded reasons where dissent is material. This rule protects the Board, the Council, and the public.

#### 236.11 Dissent, Confidentiality, and Non-Retaliation

Participants who submit dissent, objections, minority reports, or procedural concerns in good faith shall be protected from retaliation. Retaliation includes removal, non-renewal, exclusion, reputational attack, public naming without consent, loss of access, donor pressure, employer pressure, community pressure, or denial of future participation because of good-faith dissent.

Confidentiality rules shall protect dissent where disclosure may create harm, but shall not be used to suppress dissent from the decision-makers who need to see it. The Council Operating System shall route dissent to the correct level of visibility.

Any retaliation concern shall be escalated to safeguards, integrity, Board, or other protected channels. The Corporation shall treat retaliation for dissent as a serious breach of Council integrity.

#### 236.12 Interpretive Rule for Consensus, Dissent, and Minority Protections

This Section shall be interpreted to preserve a controlling proposition: GCRI US Councils shall seek consensus through disciplined deliberation while preserving material dissent, minority views, unresolved concerns, and protected objections as essential components of knowledge quality, legitimacy, safeguards, and institutional accountability.

Where ambiguity exists, the interpretation that better preserves:

a) consensus-first discipline without veto abuse;

b) structured dissent;

c) minority report pathways;

d) no suppression for narrative convenience;

e) escalation of unresolved disagreement;

f) safe publication and handling of dissent;

g) distinction between legitimate dissent and abuse;

h) accurate consensus documentation;

i) heightened protection for under-resourced and rights-sensitive participants;

j) inclusion of dissent in adoption-ready decision packs; and

k) non-retaliation for good-faith objection

shall prevail unless a contrary result is required by law.

### 237. Council Bureau and Procedural Leadership (GCRI United States)

#### 237.1 Bureau as the Procedural Leadership Surface of Each Council

Each Helix Council may maintain a Council Bureau as its procedural leadership surface. The Bureau shall exist to support orderly Council operation, not to replace the Council, the Board, the Secretariat, or executive management. Its function is to help the Council convene, prepare agendas, maintain procedural fairness, route matters, preserve records, manage time, protect dissent, support output discipline, and ensure that Council work remains within mandate.

The Bureau may assist with:

a) agenda formation and meeting preparation;\
b) docket triage and matter prioritization;\
c) confirmation that materials are complete before Council review;\
d) time management and orderly deliberation;\
e) identification of conflict, recusal, safeguards, or handling issues;\
f) preservation of dissent and minority views;\
g) coordination with the Secretariat and rapporteur;\
h) preparation of draft outputs for Council consideration;\
i) referral of urgent issues to appropriate escalation lanes; and\
j) follow-up on actions assigned by the Council.

The Bureau shall not become a small inner Council. It shall not decide matters reserved to the full Council, suppress inconvenient views, control outputs for narrative convenience, privately negotiate Council positions, or convert procedural leadership into substantive authority. The Bureau exists to make Council deliberation fair, efficient, and auditable.

#### 237.2 Council President or Chair

Each Council may have a Council President, Chair, or equivalent procedural leader appointed or elected according to the Council Charter. The Chair shall be responsible for convening and conducting Council meetings within the Council’s mandate, ensuring agenda discipline, maintaining orderly participation, protecting fair access to deliberation, and ensuring that Council outputs reflect the procedure followed.

The Council Chair shall:

a) open, conduct, suspend, and close meetings according to the Charter;\
b) confirm quorum and meeting validity with the Secretariat or rapporteur;\
c) ensure that conflicts, recusals, handling rules, and controlled-room restrictions are observed;\
d) invite balanced participation and prevent domination by senior, technical, commercial, donor, public-authority, or majority voices;\
e) distinguish discussion, recommendation, warning, dissent, consultation, and adoption-ready output;\
f) ensure that no Council statement is presented as corporate authority;\
g) route unresolved or high-risk matters to the appropriate authority;\
h) protect minority views and dissent; and\
i) ensure that minutes and outputs are corrected where they misstate the record.

The Council Chair shall not be a corporate officer merely by holding Council office. The Chair shall not bind GCRI US, approve institutional positions, sign contracts, create member rights, grant access, certify participants, speak publicly for the Corporation, or override the Council Charter unless separate authority exists.

#### 237.3 Vice-Chair or Deputy Leadership Roles

Each Council may have a Vice-Chair, Deputy Chair, or equivalent deputy leadership role to support continuity, workload management, succession, and conflict handling. The Vice-Chair may act where the Chair is absent, unavailable, recused, conflicted, incapacitated, or otherwise unable to perform procedural duties.

A Vice-Chair may:

a) chair a meeting or agenda item where authorized;\
b) support agenda preparation;\
c) assist in docket triage;\
d) coordinate with working parties or committees;\
e) support dissent and minority-report handling;\
f) support continuity where the Chair transitions out; and\
g) perform other procedural duties assigned by the Council Charter.

The Vice-Chair shall not automatically inherit the full authority of the Chair unless the Charter provides. Acting authority shall be recorded, limited, and linked to a defined trigger. The Vice-Chair shall not use temporary acting authority to change Council direction, suppress dissent, approve outputs not ready for approval, or make public statements outside authority.

#### 237.4 Rapporteur-General or Equivalent Text and Record Custodian Roles

Each Council may appoint a Rapporteur-General, lead rapporteur, text custodian, or equivalent role to support minutes, output drafting, synthesis, dissent capture, consultation summaries, and records discipline. The rapporteur function is central to Council integrity because Council authority is only as reliable as its record.

The rapporteur may be responsible for:

a) preparing draft minutes or meeting summaries;\
b) tracking motions, recommendations, warnings, dissent, and unresolved issues;\
c) ensuring that output types and effect codes are used correctly;\
d) preserving minority views and limitations;\
e) preparing draft advisory notes, memoranda, consultation summaries, or public-safe summaries;\
f) linking outputs to case IDs and docket records;\
g) coordinating corrections with the Secretariat; and\
h) ensuring that text does not exceed Council authority.

The rapporteur shall not rewrite disagreement into consensus, soften warnings without Council approval, omit safeguards concerns, remove limitations for readability, or convert Council discussion into institutional position. Drafting power is not decision power. The rapporteur must preserve meaning, not manufacture alignment.

#### 237.5 Additional Bureau Members and Portfolio Leads

A Council Charter may create additional Bureau roles or portfolio leads where necessary for effective Council operation. These roles may include safeguards lead, consultation lead, method lead, public-claims lead, participation lead, controlled-room lead, technical lead, community liaison, public-authority liaison, or working-party coordinator.

Additional Bureau roles shall be created only where they serve a defined procedural or stewardship need. Each role shall have a written mandate specifying:

a) title and purpose;\
b) appointment or election process;\
c) scope of authority;\
d) relationship to the Chair, Vice-Chair, rapporteur, Secretariat, and Council;\
e) access rights;\
f) reporting duties;\
g) conflict and recusal rules;\
h) term and review date; and\
i) public-description limits.

A portfolio lead may organize work in their area, but shall not control Council decisions. For example, a safeguards lead may flag participation risks and recommend review, but cannot unilaterally decide every safeguards matter unless separately authorized. A technical lead may coordinate technical review, but cannot certify a system. A public-claims lead may recommend revised wording, but cannot issue public statements.

#### 237.6 Bureau Election, Appointment, and Challenge Rules

Council Bureau members shall be elected, appointed, confirmed, renewed, challenged, suspended, or removed according to the Council Charter. Bureau selection shall be based on competence, integrity, neutrality, availability, role fitness, conflict profile, and ability to protect the Council’s mandate.

Bureau selection shall avoid:

a) automatic control by founders, donors, sponsors, vendors, public authorities, or dominant institutions;\
b) appointment for prestige without operational capacity;\
c) selection of persons with unresolved conflicts in the Council’s core subject matter;\
d) repeated appointment without review;\
e) capture by one constituency or institution; and\
f) appointment of persons unable to preserve dissent or safe participation.

A Bureau member may be challenged where there is concern about conflict, bias, suppression of dissent, role overreach, confidentiality breach, public overclaim, unsafe conduct, repeated non-performance, capture, or misuse of Council status. Challenge procedures shall be fair, recorded, and proportionate. Interim restriction may be imposed where necessary to protect the Council, participants, records, or public meaning.

#### 237.7 Bureau Powers, Limits, and Non-Substitution for Full Council Authority

The Bureau may exercise procedural powers assigned by the Council Charter. These may include agenda preparation, docket screening for completeness, scheduling, meeting coordination, output formatting, referral of urgent matters, and preparation of draft materials. The Bureau may not exercise full Council authority unless expressly authorized by the Charter for a narrow procedural matter.

The Bureau shall not:

a) approve Council outputs requiring full Council review;\
b) suppress or reject dissent without process;\
c) decide substantive recommendations unless expressly authorized;\
d) convert internal draft text into final Council output;\
e) make public statements on behalf of the Council or GCRI US without authority;\
f) exclude eligible participants for convenience;\
g) bypass conflict, safeguards, or controlled-room rules;\
h) grant recognition, certification, endorsement, or public status;\
i) approve adoption-ready outputs without required Council process; or\
j) bind the Corporation.

Bureau action shall be transparent to the Council. Where the Bureau screens a matter, defers an item, returns an incomplete submission, or routes a concern elsewhere, the action shall be recorded. Procedural efficiency shall not become hidden substantive control.

#### 237.8 Bureau Continuity, Temporary Acting Roles, and Succession

Each Council Charter shall provide continuity and succession rules for Bureau roles. The Council must be able to operate if a Chair, Vice-Chair, rapporteur, portfolio lead, or other Bureau member resigns, becomes unavailable, is conflicted, is removed, or is unable to continue.

Continuity rules shall address:

a) acting Chair order;\
b) acting rapporteur appointment;\
c) temporary assignment of agenda duties;\
d) access to Council records and dockets;\
e) handover of pending outputs;\
f) preservation of minutes and draft materials;\
g) public-description correction;\
h) term limits and replacement timetable; and\
i) emergency procedure where no Bureau member is available.

Temporary acting roles shall be time-limited and recorded. They shall not become permanent through inertia. Where a Bureau role is vacant for an extended period, the Council shall initiate replacement or reconstitution review.

#### 237.9 Bureau Neutrality, Fairness, and Anti-Dominance Duties

Bureau members shall owe heightened duties of neutrality, fairness, and anti-dominance. Because Bureau members influence agenda, meeting flow, drafting, time allocation, and output framing, they must not use procedural control to favor their own institution, sector, donor, sponsor, ideology, technical approach, public authority, community position, or personal view.

Bureau members shall:

a) treat participants fairly within role;\
b) ensure that under-resourced and less powerful participants can contribute;\
c) prevent repeated dominance by any participant or bloc;\
d) protect dissent and minority reports;\
e) ensure that conflicts are surfaced;\
f) maintain respectful deliberation;\
g) avoid selective circulation of materials;\
h) avoid private side-deals on Council outputs;\
i) preserve classification and handling rules; and\
j) ensure that final text reflects the record.

Bureau neutrality does not mean absence of expertise or opinion. It means that procedural power is not used to predetermine the outcome.

#### 237.10 Bureau Role in Safeguards, Controlled Rooms, and Sensitive Deliberation

The Bureau shall support safeguards, controlled-room discipline, and sensitive deliberation where applicable. The Bureau shall help identify matters requiring restricted handling, participant protection, attribution control, confidentiality, legal review, security review, privacy review, or community and Indigenous safeguards.

Bureau duties may include:

a) flagging sensitive agenda items;\
b) ensuring access restrictions are applied;\
c) confirming that participants understand handling rules;\
d) arranging separate sessions where necessary;\
e) protecting CIC-sensitive or public-authority-sensitive material;\
f) ensuring that dissent can be submitted safely;\
g) preventing unauthorized recording or distribution;\
h) coordinating with safeguards, security, or legal functions; and\
i) ensuring that public-safe summaries are properly reviewed.

The Bureau shall not use controlled-room classification to avoid accountability, hide ordinary disagreement, or keep matters from eligible participants without justification. Sensitive handling must protect legitimate interests, not shield power.

#### 237.11 Bureau Role in Public Claims and External Communications Discipline

The Bureau shall help prevent public overclaim concerning Council work. Bureau members shall ensure that public summaries, meeting notices, participant lists, and output descriptions do not misstate Council authority or participant meaning.

The Bureau shall prevent statements implying that:

a) a Council has adopted corporate policy;\
b) GCRI US has approved a recommendation when it has not;\
c) public authorities have endorsed an output;\
d) industry participants have validated a product or vendor;\
e) academic participants have certified a method;\
f) civil society or media have granted public mandate;\
g) community or Indigenous participants have provided consent; or\
h) Council participation creates membership, badge, or recognition status.

Bureau members shall not speak publicly for the Council or GCRI US unless authorized. Where public description errors occur, the Bureau shall support correction through the Secretariat, communications function, Secretary, or other competent authority.

#### 237.12 Bureau Records, Handover, and Auditability

Bureau work shall be recorded sufficiently to support auditability and continuity. Bureau meetings, docket triage decisions, agenda decisions, output-routing decisions, dissent-handling decisions, and sensitive handling decisions shall be recorded at a level appropriate to the matter.

Bureau records may include:

a) agenda planning notes;\
b) docket triage records;\
c) completeness review results;\
d) conflict and recusal flags;\
e) sensitive-handling flags;\
f) draft output routing;\
g) dissent or minority-report tracking;\
h) escalation decisions;\
i) handover notes; and\
j) closure records.

Where a Bureau member leaves office, handover shall preserve pending matters, draft outputs, unresolved dissent, access status, controlled-room restrictions, and upcoming deadlines. No Bureau member shall retain exclusive control of Council records.

#### 237.13 Removal, Restriction, or Replacement of Bureau Members

A Bureau member may be removed, restricted, replaced, suspended, or not renewed where they fail to perform duties, exceed authority, suppress dissent, misuse Council status, mishandle conflicts, breach confidentiality, create public overclaim, act unfairly, permit capture, mishandle sensitive information, retaliate, or otherwise undermine Council integrity.

Corrective measures may include:

a) role clarification;\
b) warning;\
c) facilitation support;\
d) co-chairing requirement;\
e) recusal from a matter;\
f) access restriction;\
g) removal from drafting control;\
h) replacement as chair or rapporteur;\
i) suspension from Bureau;\
j) removal from Council; or\
k) referral to safeguards, integrity, legal, or Board review.

Bureau accountability is essential because procedural leadership can shape outcomes without appearing to make decisions. GCRI US shall not allow procedural power to become unaccountable influence.

#### 237.14 Interpretive Rule for Council Bureau and Procedural Leadership

This Section shall be interpreted to preserve a controlling proposition: Council Bureaus and procedural leaders in GCRI US exist to support fair, orderly, recorded, safeguarded, and mandate-compliant Council deliberation, and may not substitute themselves for the Council, Board, Secretariat, executive management, or competent corporate authority.

Where ambiguity exists, the interpretation that better preserves:

a) Bureau as procedural support rather than substantive authority;\
b) Chair neutrality and meeting discipline;\
c) limited Vice-Chair acting authority;\
d) rapporteur fidelity to the record;\
e) portfolio-lead mandate clarity;\
f) fair Bureau selection and challenge rules;\
g) non-substitution for full Council authority;\
h) continuity and succession;\
i) anti-dominance and safeguards duties;\
j) public-claims restraint; and\
k) Bureau auditability

shall prevail unless a contrary result is required by law.

### 238. Council Officers and Role-Specific Duties (GCRI United States)

#### 238.1 Procedural Leadership Duties

Council officers of GCRI US shall serve as procedural stewards of Council integrity. They shall not be corporate officers merely by holding Council office, and they shall not possess authority to bind the Corporation unless separately appointed and authorized under the Bylaws, delegation matrix, or Board-approved instrument. Council officer status is a Council-operating role, not a corporate-governance office.

Council officers may include:

a) Council Chair or President;\
b) Vice-Chair or Deputy Chair;\
c) Rapporteur-General or lead rapporteur;\
d) committee chairs;\
e) working-party leads;\
f) consultation leads;\
g) safeguards or participation leads;\
h) rules or procedure leads;\
i) drafting leads; and\
j) other role-specific officers created by Council Charter.

Each Council officer shall operate under written mandate, defined term, recorded appointment or election, conflict disclosure, confidentiality undertaking, and public-description limits. Their core duty is to make the Council usable, fair, safe, documented, and mandate-compliant. They shall ensure that Council work moves through proper intake, deliberation, review, dissent capture, output coding, escalation, and closure.

Council officers shall not use procedural office to shape outcomes for personal, institutional, donor, sponsor, political, academic, public-authority, vendor, media, or community advantage. Procedural leadership is a trust function. It must protect the process before it protects any preferred conclusion.

#### 238.2 Agenda Management and Time Discipline

Council officers shall support agenda management and time discipline. Agenda management shall be performed through the Council Operating System and shall not be controlled informally by personal preference, external pressure, donor interest, sponsor priority, media attention, or the urgency of a participant’s institution.

Agenda discipline shall require:

a) docketed matter or approved agenda item;\
b) clear Council jurisdiction;\
c) identification of the question to be considered;\
d) sufficient materials;\
e) classification and handling review;\
f) conflict and recusal screening;\
g) expected output type;\
h) time allocation;\
i) decision or escalation pathway; and\
j) record owner.

Council officers shall ensure that agenda items are neither buried nor rushed where the matter is high consequence. A public-claims risk, safeguards concern, controlled-room issue, public-authority sensitivity, community or Indigenous concern, security issue, or non-execution boundary issue shall not be placed at the end of an agenda merely to avoid discussion.

Time discipline shall protect both efficiency and fairness. A Council officer may limit repetition, redirect irrelevant discussion, require written submissions, or defer unresolved issues. However, time discipline shall not be used to silence dissent, marginalize less powerful participants, or prevent protected escalation.

#### 238.3 Fairness, Neutrality, and Order Maintenance

Council officers shall maintain fairness, neutrality, and order. Their role is to protect the deliberative conditions under which Councils can generate reliable institutional input. They may hold views, expertise, and affiliations, but they shall not use office to predetermine results.

Fairness requires that Council officers:

a) apply rules consistently;\
b) recognize different participant roles accurately;\
c) allow relevant perspectives to be heard;\
d) prevent domination by one person, institution, sector, donor, sponsor, vendor, or bloc;\
e) protect under-resourced, community, Indigenous, civil-society, and dissenting participants from procedural exclusion;\
f) enforce confidentiality and classification rules evenly;\
g) ensure that conflicted persons do not shape matters from which they should be recused; and\
h) permit reasonable procedural challenge.

Neutrality requires that Council officers distinguish facilitation from advocacy. They may guide the Council toward a complete output, but they shall not force the Council toward a preferred answer. They may test whether views are supported, but they shall not dismiss a view because it is inconvenient, technically challenging, politically sensitive, or uncomfortable for leadership.

Order maintenance requires respectful process. Council officers may intervene against harassment, intimidation, personal attack, retaliation, disclosure of restricted information, competition-sensitive discussion, public-authority overclaim, or community and Indigenous overclaim. Such intervention shall be recorded where material.

#### 238.4 Docket Triage Assistance and Completeness Review Functions

Council officers may assist with docket triage and completeness review. This function ensures that matters brought to Councils are ready for deliberation and properly routed. Docket triage is procedural; it is not substantive approval.

Council officers may help determine whether:

a) the matter belongs before the Council;\
b) another Council or cross-Council process is required;\
c) required materials are complete;\
d) the output type is appropriate;\
e) legal, safeguards, security, privacy, finance, research, public-claims, or Board review is required before Council consideration;\
f) conflicts or recusals must be addressed;\
g) consultation is required;\
h) controlled-room treatment is necessary;\
i) the matter is urgent; and\
j) the matter should be returned for clarification before being placed on the agenda.

A completeness review shall not become censorship. A Council officer may return an incomplete submission, request more information, or recommend rerouting. They may not reject a matter merely because it is critical of leadership, donors, public authorities, vendors, Council members, or GCRI US assumptions. Where a matter alleges misconduct, retaliation, public overclaim, safeguards failure, or boundary breach, it shall be routed to the proper protected channel rather than filtered out.

#### 238.5 Dissent Preservation and Conflict Handling Duties

Council officers shall have affirmative duties to preserve dissent and handle conflicts. They shall not treat dissent or conflict as inconvenience. Both are central to Council legitimacy.

Dissent preservation duties include:

a) inviting dissent before output finalization;\
b) ensuring minority notes may be submitted;\
c) ensuring minutes do not falsely state consensus;\
d) ensuring unresolved issues are included in decision packs;\
e) protecting dissenters from retaliation;\
f) preserving classification and attribution preferences; and\
g) ensuring that dissent is routed to the proper authority where material.

Conflict handling duties include:

i) reminding participants of disclosure duties;\
ii) identifying apparent conflicts;\
iii) requesting recusal review where needed;\
iv) excluding conflicted participants from deliberation, drafting, voting, or access where required;\
v) ensuring conflict records are made; and\
vi) escalating unresolved or high-risk conflicts to the Secretariat, ethics function, Board, or appropriate committee.

A Council officer who knowingly permits conflicted participants to dominate a matter, or knowingly suppresses dissent to create artificial consensus, shall be subject to removal, restriction, or integrity review.

#### 238.6 No Unilateral Conversion of Deliberation Into Binding Act

No Council officer may unilaterally convert deliberation into a binding act, adopted position, public statement, institutional approval, certification, recognition, endorsement, public mandate, community consent, Indigenous consent, government position, procurement preference, or execution authority. This prohibition applies to chairs, vice-chairs, rapporteurs, committee chairs, drafting leads, consultation leads, and any officer-like Council role.

A Council officer shall not:

a) declare that GCRI US has adopted a Council recommendation unless the competent authority has done so;\
b) issue public statements using Council title without authority;\
c) sign letters as if the Council binds the Corporation;\
d) certify that a participant, institution, method, tool, standard, or platform has been approved;\
e) describe public-authority attendance as government support;\
f) describe community or Indigenous input as consent;\
g) describe academic review as scientific validation;\
h) describe operator review as vendor or procurement approval;\
i) describe civil-society or media review as public endorsement; or\
j) treat Council consensus as Board decision.

Where a Council officer believes urgent public communication is required, the matter shall be routed through the communications, legal, Secretary, Board, or emergency governance pathway. Urgency shall not create unilateral authority.

#### 238.7 Role-Specific Conduct, Integrity, and Removal Standards

Council officers shall comply with heightened conduct and integrity standards. Their procedural authority affects participation, records, public meaning, and institutional trust. They shall be removable, restrictable, or replaceable where they fail to meet those standards.

Council officer misconduct may include:

a) misuse of title or public status;\
b) suppression of dissent;\
c) mishandling of conflicts or recusals;\
d) favoritism toward donor, sponsor, vendor, institution, public authority, or personal network;\
e) unauthorized disclosure of restricted information;\
f) retaliation or intimidation;\
g) public overclaim of Council authority;\
h) failure to preserve minutes, outputs, or records;\
i) misclassification of sensitive material;\
j) repeated procedural unfairness;\
k) conversion of procedural role into substantive control;\
l) failure to escalate safeguards, security, legal, or boundary concerns; or\
m) failure to comply with Council Charter and Bylaws.

Corrective measures may include role clarification, warning, training, co-chairing requirement, recusal, access restriction, removal from drafting duties, suspension from Bureau, removal from Council office, removal from Council participation, public correction, or referral to safeguards, integrity, legal, or Board review.

Removal shall be recorded and conducted with fairness proportionate to the issue. Where immediate harm is possible, interim protective restriction may be imposed pending review.

#### 238.8 Council Chair Duties by Council Type

Council Chair duties shall be adapted to the nature of each Council. A single procedural template shall apply across the system, but each Chair must understand the specific risks of their Council.

The PAC Chair shall maintain public-authority capacity discipline and prevent government-overclaim, regulatory-overclaim, procurement signaling, or public-law confusion. The IOC Chair shall maintain competition safety, vendor-neutrality, antitrust discipline, and operational realism without commercial endorsement. The ARC Chair shall protect uncertainty discipline, method challenge, research integrity, academic independence, and no false validation. The CMC Chair shall protect public-claims accuracy, transparency, accessibility, media independence, and no political mandate. The CIC Chair shall protect dignity, Indigenous and community knowledge boundaries, consent, safe participation, non-extraction, and no generalized community or Indigenous approval.

Every Chair shall know when to stop discussion and route a matter to another authority. A Chair who allows a Council to drift into prohibited authority, unsafe publication, competition-sensitive exchange, public-authority overclaim, or community overclaim fails the role.

#### 238.9 Rapporteur Duties in Text Integrity, Output Coding, and Institutional Memory

Rapporteurs shall preserve text integrity, output coding, and institutional memory. They shall ensure that the written record reflects what occurred and does not inflate, sanitize, or distort the Council’s work.

A rapporteur shall ensure that Council outputs:

a) carry the correct title and output type;\
b) include case ID and version number;\
c) identify issuing Council or Councils;\
d) identify materials reviewed;\
e) state effect code and claims boundary;\
f) include limitations, dissent, minority views, or unresolved issues where material;\
g) distinguish observation, recommendation, warning, and escalation;\
h) preserve classification and attribution rules;\
i) identify next route or closure status; and\
j) avoid unauthorized words of approval, certification, recognition, endorsement, or adoption.

Rapporteurs shall not act as ghost decision-makers. Drafting is service to the record. Where the rapporteur is conflicted, contested, or materially involved in the substance, a co-rapporteur or independent text reviewer may be appointed.

#### 238.10 Consultation Lead and Participation Lead Duties

Where a Council appoints a consultation lead or participation lead, that person shall help ensure that consultation processes are accessible, fair, safe, documented, and meaningful. The role is particularly important where GCRI US seeks input from public authorities, civil society, media, communities, Indigenous participants, under-resourced organizations, technical experts, or affected groups.

The consultation or participation lead shall support:

a) consultation planning;\
b) identification of relevant participant groups;\
c) accessibility review;\
d) comment intake and logging;\
e) disposition tracking;\
f) participation-safety review;\
g) non-retaliation controls;\
h) consent and attribution rules;\
i) public-safe summary preparation; and\
j) feedback to participants where appropriate.

The consultation lead shall not decide substantive outcomes or overclaim consultation as consent. Their duty is to make the consultation process honest, recorded, safe, and responsive.

#### 238.11 Safeguards and Integrity Lead Duties

Where a Council appoints a safeguards lead, integrity lead, or equivalent role, that person shall support identification of participation harm, conflicts, retaliation risk, dignity concerns, public overclaim, knowledge appropriation, unsafe attribution, and process abuse. The role shall be especially important in CIC-sensitive, CMC-sensitive, public-authority-sensitive, and controlled-room contexts.

The safeguards or integrity lead may:

a) flag unsafe participation conditions;\
b) request classification or controlled-room review;\
c) recommend anonymization or role-marker attribution;\
d) identify retaliation risk;\
e) escalate grievances or protected reports;\
f) request conflict review;\
g) recommend pause of publication;\
h) support safe dissent pathways; and\
i) coordinate with the Corporation’s safeguards or integrity function.

The safeguards or integrity lead shall not replace formal safeguards or integrity processes. They are an early-warning and routing function within Council operations.

#### 238.12 Council Officer Training and Certification of Readiness

Council officers shall receive onboarding and training appropriate to their role before exercising material procedural authority. Training shall cover:

a) Council Charter and Part X;\
b) Council output taxonomy;\
c) records and minutes discipline;\
d) conflict and recusal rules;\
e) competition and antitrust safety;\
f) safeguards and protected participation;\
g) public-claims controls;\
h) controlled-room and classification rules;\
i) non-execution boundary;\
j) public-authority, community, Indigenous, media, academic, and industry overclaim risks; and\
k) escalation pathways.

The Council Operating System may require officer readiness certification, especially for Chairs, rapporteurs, consultation leads, safeguards leads, and working-party chairs. A person who has not completed required onboarding may serve only in provisional or supervised capacity unless waived by competent authority for recorded reasons.

#### 238.13 Council Officer Public Description and Use of Title

Council officers may use their Council title only in approved form. The title shall not imply corporate office, fiduciary authority, employment, partnership, certification authority, public-authority role, or capacity to bind GCRI US.

Approved public descriptions may include:

a) “Chair, \[Council Name], GCRI US Helix Council System”;\
b) “Rapporteur, \[Council Name]”;\
c) “Vice-Chair, \[Council Name]”; or\
d) “Working Party Lead, \[specific working party], \[Council Name].”

Such descriptions shall be accompanied by limitations where needed. Prohibited descriptions include language suggesting “Director of GCRI US,” “Officer of GCRI US,” “authorized representative of GCRI US,” “certification authority,” “official government liaison,” “approved standards authority,” or any title that implies authority not granted.

Upon term expiry, removal, resignation, or suspension, the officer shall stop using the title except in dated historical form where accurate and permitted.

#### 238.14 Interpretive Rule for Council Officers and Role-Specific Duties

This Section shall be interpreted to preserve a controlling proposition: Council officers in GCRI US are procedural stewards whose duties are to maintain fair, safe, recorded, role-bounded, and mandate-compliant Council operations, and they may not convert procedural leadership, drafting control, consultation management, or Council title into corporate authority, public endorsement, certification, or execution effect.

Where ambiguity exists, the interpretation that better preserves:

a) procedural leadership without corporate authority;\
b) disciplined agenda and time management;\
c) fairness and neutrality;\
d) proper docket triage;\
e) dissent and conflict handling;\
f) no unilateral binding effect;\
g) officer accountability and removal;\
h) Council-specific risk awareness;\
i) rapporteur text integrity;\
j) consultation and safeguards leadership;\
k) officer training; and\
l) accurate public use of title

shall prevail unless a contrary result is required by law.

### 239. Standing Committees of Councils (GCRI United States)

#### 239.1 Authority to Create Standing Committees

Each Helix Council may create standing committees only where authorized by its Council Charter, this Part, or a Board-approved Council Operating System. Standing committees shall exist to support recurring procedural, technical, participation, safeguards, drafting, credentials, or succession functions within the Council. They shall not exist as informal sub-councils, private influence rooms, donor channels, expert clubs, or parallel decision bodies.

A standing committee may be created where the Council requires continuous capacity for:

a) credentials, eligibility, and fit-and-proper review;\
b) rules, procedure, quorum, voting, and meeting discipline;\
c) drafting, text integrity, controlled vocabulary, and output coding;\
d) consultations, comment handling, and participation accessibility;\
e) safeguards, protected participation, dignity, and non-retaliation;\
f) nominations, succession, bureau continuity, and leadership pipeline;\
g) expert review coordination, where authorized;\
h) cross-Council coherence and output harmonization; and\
i) records, minutes, repository discipline, and case-linkage support.

No standing committee shall be created unless its purpose, membership, chair, mandate, authority limits, reporting line, records duties, term, review date, and public-description rules are recorded. A Council committee shall support Council readiness. It shall not reduce transparency, bypass full Council review, or concentrate substantive influence in a smaller group.

#### 239.2 Credentials and Fit-and-Proper Committee

A Council may establish a Credentials and Fit-and-Proper Committee to support participant eligibility, role verification, institutional authorization, capacity statements, conflict screening, good-standing review, and seating discipline. This committee shall help ensure that Council participation is credible, safe, balanced, and accurately described.

The committee may review:

a) whether a proposed participant is eligible under the Council Charter;\
b) whether institutional representatives have authority to participate in the capacity claimed;\
c) whether public-authority participants are acting personally, officially, technically, as observers, or in another bounded capacity;\
d) whether community or Indigenous participants have a recorded mandate, consent basis, or clearly limited personal/lived-context role;\
e) whether industry, vendor, sponsor, or operator participants present competition, procurement, or capture risk;\
f) whether academic participants’ affiliations create research, IP, publication, or attribution issues;\
g) whether media and civil-society participants require independence, attribution, or public-description safeguards; and\
h) whether any participant requires restricted access, observer status, recusal, conditional seating, or further review.

The committee shall not use credentials review to exclude difficult voices, critics, minority views, affected communities, or inconvenient public-interest participants. Its function is integrity, not gatekeeping for comfort. Where the committee recommends refusal, restriction, or conditional seating, the record shall state the basis and any review pathway.

#### 239.3 Rules and Procedure Committee

A Council may establish a Rules and Procedure Committee to support the Council’s procedural integrity. This committee shall help ensure that Council meetings, joint sessions, votes, quorum, consensus processes, dissent pathways, controlled-room procedures, and output approvals follow the Council Charter and this Part.

The committee may advise on:

a) meeting procedure and order;\
b) quorum and threshold questions;\
c) agenda admissibility;\
d) role rights, including speech, drafting, voting, observer, and guest rights;\
e) remote participation and remote voting integrity;\
f) controlled-room procedure;\
g) procedural challenge windows;\
h) correction of procedural defects;\
i) cross-Council joint session procedure; and\
j) emergency or time-sensitive procedure.

The Rules and Procedure Committee shall not decide substantive outcomes. It may recommend whether a process is procedurally ready, defective, incomplete, or subject to cure. Where a procedural question affects legal authority, public claims, safeguards, conflict, or Board reserved matters, the committee shall escalate to the Secretariat, Secretary, legal function, safeguards function, or Board as appropriate.

#### 239.4 Drafting and Text Discipline Committee

A Council may establish a Drafting and Text Discipline Committee to support high-quality Council outputs, decision packs, consultation summaries, dissent records, public-safe summaries, and adoption-ready recommendations. This committee shall ensure that Council text is accurate, mandate-bound, effect-coded, classified, and faithful to the deliberation record.

The committee may review:

a) whether output language exceeds Council authority;\
b) whether the correct output type and effect code are used;\
c) whether limitations, uncertainty, dissent, and minority views are preserved;\
d) whether public-claims boundaries are clear;\
e) whether terms such as “approved,” “validated,” “recognized,” “endorsed,” “certified,” “adopted,” “public mandate,” or “consent” are used only where authorized;\
f) whether attribution is accurate and consent-based;\
g) whether summaries distort technical, public-law, community, Indigenous, media, or civil-society meaning; and\
h) whether the output is ready for internal use, public-safe release, escalation, or adoption-ready routing.

The committee shall not rewrite Council outputs to soften material warnings, conceal disagreement, or make language more marketable. Drafting discipline is not communications polishing. It is legal-meaning control and institutional memory protection.

#### 239.5 Consultations and Participation Committee

A Council may establish a Consultations and Participation Committee to support consultation design, participant access, comment logging, comment disposition, public-facing materials, accessibility, participation safety, and feedback loops. This committee shall help ensure that Council-led or Council-supported consultation is meaningful, not performative.

The committee may support:

a) consultation scoping;\
b) identification of relevant participant groups;\
c) preparation of consultation packages;\
d) plain-language summaries;\
e) accessibility and inclusion review;\
f) comment intake and logging;\
g) comment disposition matrices;\
h) tracking of unresolved issues;\
i) participant feedback and closure notes; and\
j) coordination with CMC, CIC, safeguards, communications, and records functions.

Where consultation involves under-resourced participants, affected communities, Indigenous knowledge, public-authority-sensitive matters, or rights-sensitive issues, the committee shall coordinate with safeguards and controlled-handling functions. Consultation shall not be described as consent, endorsement, public mandate, or adoption unless the governing process expressly creates that effect and the record supports it.

#### 239.6 Safeguards and Integrity Committee

A Council may establish a Safeguards and Integrity Committee to support protected participation, conflict discipline, dignity, non-retaliation, grievance routing, public-claims integrity, anti-capture controls, sensitive handling, and conduct standards within Council work. This committee shall serve as a first-line Council integrity mechanism and a routing surface to formal safeguards or integrity functions where needed.

The committee may identify and escalate:

a) retaliation, intimidation, harassment, or unsafe participation;\
b) misuse of Council status;\
c) community or Indigenous overclaim;\
d) public-authority overclaim;\
e) media or civil-society endorsement overclaim;\
f) vendor, donor, sponsor, or sector capture;\
g) undisclosed conflicts or prohibited overlaps;\
h) breach of confidentiality or controlled-room rules;\
i) suppression of dissent;\
j) participation extraction or tokenism; and\
k) public-claims drift.

The Safeguards and Integrity Committee shall not replace formal Board-level, legal, employment, whistleblower, or grievance processes. It shall identify, triage, protect, and route. Where a matter involves serious harm, senior leadership, retaliation, financial irregularity, security breach, or Board-level integrity risk, it shall be escalated through protected channels.

#### 239.7 Nominations and Succession Committee

A Council may establish a Nominations and Succession Committee to support Council composition, seat renewal, leadership pipeline, bureau continuity, chair succession, rapporteur succession, committee membership, and balanced representation. This committee shall help prevent Council dependency on a single chair, founder, donor-linked person, technical expert, public figure, or institutional network.

The committee may review:

a) upcoming seat expiries;\
b) renewal eligibility;\
c) attendance and contribution;\
d) balance and concentration risks;\
e) missing perspectives or dead zones;\
f) suitability of bureau candidates;\
g) committee leadership needs;\
h) succession for chair, vice-chair, rapporteur, and working-party leads;\
i) need for new observers, experts, or temporary participants; and\
j) removal or non-renewal recommendations where integrity or performance requires.

The committee shall not become a patronage body. It shall not reward loyalty, donor value, public profile, or internal alliance. Its task is to keep the Council competent, balanced, diverse in knowledge, and institutionally resilient.

#### 239.8 Additional Committees Only Where Formally Chartered and Recorded

Additional Council committees may be created only where formally chartered and recorded. A Council shall not create standing committees by recurring practice, informal working calls, long-running email groups, private drafting circles, or repeated task assignment. If a recurring function becomes material, it shall be chartered or discontinued.

Any additional committee shall have:

a) name and purpose;\
b) authority source;\
c) term or review date;\
d) membership and chair;\
e) permitted functions;\
f) prohibited acts;\
g) reporting line;\
h) records requirements;\
i) conflict and recusal rules;\
j) classification and handling rules; and\
k) closure, renewal, or sunset procedure.

Additional committees may include technical review coordination, public-claims review, controlled-room operations, cross-Council harmonization, accessibility, or expert roster coordination. No additional committee shall create certification, recognition, procurement, endorsement, or execution authority unless separately authorized through a governing instrument.

#### 239.9 Committee Limits, Reporting Lines, and Recordkeeping Obligations

Council committees shall remain subordinate to the Council Charter, the full Council, the Council Operating System, and these Bylaws. They may prepare, review, recommend, coordinate, and escalate. They shall not make final Council decisions where full Council action is required, nor may they bind GCRI US.

Each Council committee shall report to:

a) the full Council;\
b) the Council Bureau;\
c) the Secretariat support function;\
d) another committee or function, where expressly assigned; or\
e) the Board or governance-spine function, where escalation is required.

Committee records shall include agendas, attendance, conflicts, recusals, materials reviewed, recommendations, dissent, decisions within delegated procedural authority, escalation notes, and closure records. Committee records shall be linked to the relevant case ID or Council docket.

A committee that fails to maintain records, exceeds authority, suppresses dissent, becomes captured, or operates as a shadow decision body may be suspended, reconstituted, or dissolved.

#### 239.10 Cross-Council Committee Use and Joint Committee Controls

Where a matter requires continuing coordination across Councils, GCRI US may authorize a joint Council committee or cross-Council committee. Such committee shall be carefully chartered because cross-Council committees can easily become hidden plenary authorities if not controlled.

A joint committee shall specify:

a) participating Councils;\
b) purpose and mandate;\
c) authority limits;\
d) chairing arrangement;\
e) representation balance;\
f) output types;\
g) handling rules;\
h) reporting route to each Council;\
i) dissent preservation; and\
j) sunset date.

A joint committee shall not erase Council distinctions. It shall not issue outputs suggesting full Council concurrence unless each participating Council has approved the output through its own procedure or the joint committee has express authority to speak within a defined advisory scope.

#### 239.11 Committee Role in Adoption-Ready Outputs

Council committees may help prepare adoption-ready outputs, but shall not convert materials into adopted institutional positions. Where a committee supports an adoption-ready package, it shall ensure that the package identifies:

a) Council mandate and scope;\
b) committee role;\
c) materials reviewed;\
d) output type and effect code;\
e) unresolved issues;\
f) dissent or minority views;\
g) safeguards, legal, security, privacy, finance, research, and public-claims review status;\
h) required Council or Board approvals; and\
i) publication class.

A committee may recommend that a matter is complete enough for full Council review or competent authority review. It may not state that the matter has been adopted unless the competent authority has acted.

#### 239.12 Annual Review of Council Committees

Each standing Council committee shall be reviewed at least annually, or more frequently where risk requires. The review shall determine whether the committee remains necessary, effective, balanced, properly scoped, and adequately recorded.

The annual review shall consider:

a) whether the committee fulfilled its mandate;\
b) whether its outputs were useful;\
c) whether it respected authority limits;\
d) whether records were complete;\
e) whether conflicts and recusals were handled;\
f) whether it became too dominant;\
g) whether it duplicated another committee;\
h) whether its membership remained balanced;\
i) whether it supported or weakened full Council deliberation; and\
j) whether it should be renewed, revised, merged, suspended, or dissolved.

Standing committees shall not continue because no one reviewed them. Their continuation shall be an affirmative governance choice.

#### 239.13 Interpretive Rule for Standing Committees of Councils

This Section shall be interpreted to preserve a controlling proposition: Council standing committees in GCRI US exist only to support credentials, rules, drafting, consultation, safeguards, nominations, succession, and other formally chartered Council functions, and shall remain subordinate, recorded, mandate-bound, transparent to the Council, and incapable of becoming hidden decision bodies or authority substitutes.

Where ambiguity exists, the interpretation that better preserves:

a) formal committee creation;\
b) credentials and fit-and-proper integrity;\
c) procedural discipline;\
d) text and output-control discipline;\
e) meaningful consultation;\
f) safeguards and anti-capture oversight;\
g) nominations and succession resilience;\
h) prohibition on informal standing bodies;\
i) clear reporting and records;\
j) controlled cross-Council committee use; and\
k) annual review and sunset discipline

shall prevail unless a contrary result is required by law.

### 240. Working Parties, Drafting Groups, and Time-Bound Mandates (GCRI United States)

#### 240.1 Authority to Create Working Parties and Drafting Groups

A Helix Council may create a working party, drafting group, task group, technical drafting cell, consultation synthesis group, redrafting team, or time-bound review group only where the Council Charter, Council Bureau, Council Operating System, or competent corporate authority permits such creation. Working parties and drafting groups shall be instruments of disciplined Council work. They shall not become shadow Councils, private steering groups, donor channels, expert clubs, vendor rooms, public-authority substitutes, or hidden decision bodies.

A working party may be created where a matter requires focused preparation before full Council deliberation, including:

a) drafting of Council outputs, advisory notes, consultation summaries, dissent records, public-safe summaries, or adoption-ready inputs;\
b) review of technical, methodological, public-law, operational, safeguards, public-claims, or community-sensitive materials;\
c) synthesis of consultation comments;\
d) preparation of issue maps, risk maps, or options papers;\
e) cross-Council reconciliation of competing views;\
f) controlled-room review of sensitive materials;\
g) rapid response to urgent but non-emergency Council matters; and\
h) preparation of materials for Board, Secretariat, committee, or competent authority review.

A working party shall be created by recorded mandate. The mandate shall identify the matter, purpose, members, chair or lead, rapporteur, authority limits, output type, deadline, records obligations, handling class, conflicts process, and closure conditions. No working party shall rely on informal invitation, repeated meetings, private chat groups, or personal networks as authority.

#### 240.2 Time-Bound Mandate Requirement

Every working party and drafting group shall have a time-bound mandate. Time limitation is essential because working parties are exceptions to ordinary full-Council deliberation. They are created to complete a defined task, not to become standing influence structures.

The mandate shall specify:

a) start date;\
b) end date or review date;\
c) deliverables;\
d) decision clock;\
e) reporting cadence;\
f) conditions for extension;\
g) closure procedure; and\
h) handoff route.

Extensions shall be recorded and justified. A working party shall not continue simply because it remains useful, convenient, prestigious, or controlled by influential participants. Repeated extension shall trigger review of whether the function should be converted into a standing committee, reassigned to the Secretariat, returned to the full Council, or discontinued.

Where a working party’s task becomes broader than the original mandate, it shall pause and seek revised authority. Mission creep is not permitted through drafting practice.

#### 240.3 Membership Selection, Independence, and Conflict Rules

Membership of working parties shall be selected based on mandate relevance, competence, independence, representation balance, safeguards needs, and conflict profile. A working party shall not be populated only by those most available, most senior, most commercially interested, most vocal, most donor-aligned, or most supportive of a predetermined outcome.

Selection shall consider:

a) subject-matter expertise;\
b) Council representation balance;\
c) independence from the matter;\
d) conflicts of interest;\
e) public-authority, industry, academic, media, community, Indigenous, donor, sponsor, vendor, or execution-side affiliations;\
f) ability to comply with confidentiality and handling rules;\
g) ability to preserve dissent and limitations;\
h) safeguards and participation-safety requirements; and\
i) need for independent rapporteur or text reviewer.

Where a working party concerns a vendor, sponsor, funder, public authority, community, Indigenous matter, technical method, public-facing claim, or sensitive data, the membership shall be scrutinized carefully. Conflicted participants may be excluded, limited to factual submissions, barred from drafting, converted to observer status, or subject to recusal from specific sections.

No person shall be placed in a working party to control the outcome of a matter in which they have a material interest.

#### 240.4 Scope, Deliverables, and Closure Conditions

Each working party shall have defined scope, deliverables, and closure conditions. Its task must be narrow enough to complete and clear enough to review. A working party that cannot state what it is producing should not be created.

Deliverables may include:

a) draft Council advisory note;\
b) draft consultation summary;\
c) issue map;\
d) evidence limitation note;\
e) method review table;\
f) public-claims risk review;\
g) safeguards referral note;\
h) controlled-room summary;\
i) comment disposition matrix;\
j) cross-Council reconciliation memorandum;\
k) proposed amendments to a draft output;\
l) minority-report synthesis; or\
m) adoption-ready input package.

Closure conditions shall state when the working party ends. Closure may occur when the deliverable is submitted, the Council rejects or accepts the output, the matter is escalated, the mandate expires, the Board or Secretariat assumes the matter, the working party becomes conflicted or ineffective, or the Council determines that the work is no longer needed.

A working party shall close through a closure note identifying final status, documents produced, unresolved issues, records location, and any continuing restrictions.

#### 240.5 Reporting, Handoff, and Dissolution Requirements

Working parties shall report to the full Council, Council Bureau, Secretariat, or other authority identified in the mandate. Reporting shall be regular enough to prevent hidden drafting, capture, or divergence from mandate.

Reports shall identify:

a) progress against mandate;\
b) materials reviewed;\
c) participant attendance and roles;\
d) conflicts and recusals;\
e) unresolved issues;\
f) dissent or minority concerns;\
g) handling restrictions;\
h) draft outputs;\
i) recommended next step; and\
j) any matter requiring escalation.

Handoff shall be disciplined. A working party may hand off a draft to the full Council for review, to another Council for cross-Council input, to the Secretariat for formatting and records, to safeguards or legal review, to security or privacy review, to ARC or IOC for technical review, to CMC for public-claims review, or to CIC for community and Indigenous safeguards review.

Dissolution shall be recorded. Upon dissolution, access rights shall be reviewed and revoked where no longer needed, draft files shall be archived, public-description status shall be corrected, and any outstanding risks shall be assigned.

#### 240.6 No Working Party May Become a Shadow Council or Permanent Authority Surface

No working party may become a shadow Council, private Council, permanent authority surface, or substitute for full Council deliberation. This rule is fundamental to the integrity of the Helix Council System. Working parties may prepare; they may not govern. They may draft; they may not decide. They may synthesize; they may not erase dissent. They may recommend; they may not adopt.

A working party becomes unsafe where it:

a) repeatedly controls Council agenda;\
b) drafts final outputs without full Council review;\
c) excludes dissenting participants;\
d) becomes dominated by one donor, sponsor, vendor, sector, public authority, technical group, or institutional network;\
e) continues beyond mandate without renewal;\
f) issues public statements;\
g) privately negotiates Council positions;\
h) grants access or status;\
i) decides matters reserved to the Council, Board, Secretariat, or corporate authority; or\
j) becomes the place where real decisions are made while the Council only ratifies.

Where such pattern appears, the working party shall be suspended, reconstituted, dissolved, or brought under formal standing-committee rules.

#### 240.7 Record, Publication, and Archive Discipline for Working-Party Outputs

Working-party outputs shall be recorded, classified, version-controlled, and archived. A draft prepared by a working party shall remain a draft until approved by the proper Council or authority. No working-party output shall be circulated publicly unless its publication class permits and required review has occurred.

Working-party records shall include:

a) mandate;\
b) membership;\
c) meeting dates;\
d) materials reviewed;\
e) conflicts and recusals;\
f) draft versions;\
g) comments received;\
h) dissent or minority text;\
i) output classification;\
j) handoff record;\
k) closure note; and\
l) archive location.

Publication rules shall prevent public overclaim. A working-party draft shall not be described as a Council position. A technical drafting group note shall not be described as ARC validation. A public-authority working group note shall not be described as government endorsement. A community-sensitive working group note shall not be described as consent. A vendor-heavy working party output shall not be described as procurement or operator approval.

Archive discipline shall preserve institutional memory. Future users must be able to determine whether a working-party output was draft, final, rejected, superseded, escalated, or adopted by another authority.

#### 240.8 Working Parties in Cross-Council and Multi-Domain Matters

Where a matter crosses multiple Councils, a cross-Council working party may be created. Such working party shall preserve Council distinctions and shall not become a hidden plenary. Its mandate shall identify which Councils are represented, what perspective each Council is expected to contribute, and how outputs return to each Council or to the proper authority.

A cross-Council working party may be useful for:

a) systemic risk frameworks requiring public-sector, operator, research, civil-society, and community review;\
b) AI, data, geospatial, or risk-intelligence outputs requiring method, security, public-trust, and safeguards review;\
c) Nexus-aligned public-good architecture requiring non-execution, public-claims, technical, and participation discipline;\
d) consultation outputs requiring comment disposition across multiple knowledge domains; and\
e) urgent correction of public overclaim where several Councils are implicated.

Cross-Council working parties shall record whether they speak for participating Councils or merely prepare materials for those Councils. Unless expressly authorized, they prepare materials only. They do not create cross-Council concurrence.

#### 240.9 Drafting Groups for Bylaw, Charter, Standards, and Policy Text

Drafting groups may be used for bylaw schedules, Council Charters, standards proposals, policy text, consultation submissions, public-good frameworks, technical templates, and decision-pack language. Drafting groups shall operate under strong text-integrity controls.

A drafting group shall:

a) preserve the authority map;\
b) identify source materials;\
c) maintain version control;\
d) avoid unauthorized legal-effect language;\
e) preserve dissent and unresolved issues;\
f) distinguish drafting suggestions from adopted text;\
g) use controlled vocabulary;\
h) include review gates; and\
i) submit text through the proper pathway.

Drafting groups shall not “improve” text by deleting limits that protect GCRI US. They shall not convert “advisory” into “approved,” “consulted” into “consented,” “reviewed” into “validated,” or “recommended” into “adopted.” In the GCRI US model, legal meaning is part of institutional safety.

#### 240.10 Working Parties for Sensitive, Controlled-Room, or Protected Matters

Working parties may be created for sensitive or controlled-room matters only under enhanced controls. Such matters may involve public-authority-sensitive information, commercially sensitive operational detail, personal data, community or Indigenous knowledge, whistleblower information, cybersecurity vulnerabilities, legal privilege, donor-sensitive information, or high-risk public claims.

Sensitive working-party mandates shall specify:

a) restricted participant list;\
b) access basis;\
c) confidentiality requirements;\
d) device and recording rules;\
e) secure repository location;\
f) controlled minutes;\
g) public-safe summary rules;\
h) review by safeguards, legal, security, privacy, or records functions; and\
i) closure and access-revocation requirements.

Controlled-room working parties shall not use sensitivity as a reason to avoid accountability. The record may be restricted, but the existence, mandate, and closure of the process shall be visible to the appropriate authority.

#### 240.11 Working-Party Performance, Review, and Corrective Action

Working parties shall be reviewed for performance, discipline, and mandate compliance. A working party that is late, captured, inactive, unsafe, unclear, poorly recorded, or repeatedly outside scope shall be corrected or dissolved.

Review may consider:

a) whether the mandate remains valid;\
b) whether deliverables are on track;\
c) whether participation is balanced;\
d) whether conflicts are managed;\
e) whether records are complete;\
f) whether sensitive information is protected;\
g) whether dissent is preserved;\
h) whether drafts are within authority;\
i) whether the working party is becoming permanent without authority; and\
j) whether continuation serves the Council’s public-good function.

Corrective action may include narrowing mandate, replacing the lead, adding independent review, requiring full Council review, removing conflicted participants, imposing controlled-room rules, extending with conditions, or dissolving the group.

#### 240.12 Interpretive Rule for Working Parties, Drafting Groups, and Time-Bound Mandates

This Section shall be interpreted to preserve a controlling proposition: working parties and drafting groups in GCRI US are time-bound, mandate-bound, records-bound instruments for focused preparation, review, synthesis, and drafting, and may not become shadow Councils, permanent authority surfaces, unrecorded influence channels, or substitutes for full Council, Board, Secretariat, safeguards, or competent authority review.

Where ambiguity exists, the interpretation that better preserves:

a) formal creation authority;\
b) time-bound mandates;\
c) balanced and conflict-managed membership;\
d) clear deliverables and closure;\
e) disciplined reporting and handoff;\
f) prohibition on shadow authority;\
g) record and publication controls;\
h) cross-Council role clarity;\
i) text-integrity discipline;\
j) controlled-room safeguards; and\
k) performance review and corrective action

shall prevail unless a contrary result is required by law.

### 241. Expert Mechanisms and Review Bodies (GCRI United States)

#### 241.1 Expert Panels, Technical Review Panels, and Special Rapporteurs

GCRI US may establish expert panels, technical review panels, special rapporteurs, independent reviewers, replication reviewers, safety-case reviewers, or equivalent expert mechanisms where a Council, the Board, the Secretariat, or a competent governance function determines that a matter requires specialized analysis beyond ordinary Council deliberation. Expert mechanisms shall exist to strengthen rigor, independence, contestability, and decision readiness. They shall not become shadow Councils, private advisory clubs, certification authorities, procurement committees, or substitutes for Board adoption.

Expert mechanisms may be used where a matter involves:

a) complex scientific, technical, legal, operational, safeguards, data, AI, cybersecurity, community, Indigenous, public-authority, or public-claims issues;

b) contested evidence, disputed methodology, unresolved dissent, or significant uncertainty;

c) public-good infrastructure with reliance risk;

d) draft standards, frameworks, or tools that may be externally cited as authoritative;

e) sensitive publication decisions;

f) serious claims of overstatement, methodological defect, public harm, or unsafe consultation;

g) cross-Council disagreement that cannot be resolved through ordinary deliberation; or

h) high-consequence Nexus-aligned materials where public-good governance, technical integrity, and non-execution discipline must be tested together.

An expert mechanism shall be created by written mandate. The mandate shall identify the question, the reviewers, the independence standard, the materials to be reviewed, the output expected, the timeline, the confidentiality class, the reporting route, the conflict rules, and the effect of the review. No expert mechanism shall be created merely to endorse a predetermined conclusion.

#### 241.2 Red Teams, Replication Teams, and Safety-Case Review Functions

GCRI US may use red teams, replication teams, model challenge teams, adversarial review groups, safety-case review functions, or structured challenge panels to test the robustness of Council outputs, technical claims, evidence systems, public-good tools, AI-supported analysis, policy proposals, or public-facing institutional claims.

Red-team and replication functions may examine:

a) whether evidence can be independently reproduced;

b) whether a method fails under plausible stress conditions;

c) whether assumptions are hidden or fragile;

d) whether AI-generated or AI-assisted analysis contains hallucination, bias, weak provenance, or unverifiable inference;

e) whether a public-good technical system has cybersecurity, privacy, access-control, or supply-chain weaknesses;

f) whether a public-facing claim can be misunderstood as endorsement, certification, adoption, public mandate, routeability, or execution authority;

g) whether community, Indigenous, public-authority, or protected-participant information is exposed or overclaimed; and

h) whether an output creates legal, financial, operational, or reputational reliance beyond its authority.

A safety-case review may be required where a proposed output or system could affect trust, rights, public-sector interpretation, community dignity, sensitive data, or downstream institutional reliance. The safety-case shall identify the claim, evidence supporting the claim, risks and failure modes, controls, limitations, unresolved objections, and conditions for safe publication or adoption.

#### 241.3 Independence, Eligibility, and Rotation Standards for Experts

Experts serving in expert mechanisms shall be selected for competence, independence, integrity, and relevance to the question under review. Expert selection shall not be based solely on prestige, institutional brand, donor preference, sector influence, public profile, or convenience.

Eligibility review shall consider:

a) subject-matter expertise;

b) independence from the matter under review;

c) conflicts of interest, including financial, professional, institutional, research, donor, sponsor, vendor, political, public-authority, community, Indigenous, media, or execution-side interests;

d) prior involvement in drafting the material under review;

e) ability to comply with confidentiality, handling, and records rules;

f) ability to distinguish review, advice, validation, certification, and institutional adoption;

g) capacity to produce a written, reasoned output; and

h) willingness to preserve uncertainty, limitations, and dissent.

Experts shall be rotated where repeated use creates dependence, capture, intellectual monoculture, or appearance of preferred conclusions. GCRI US shall maintain a broad expert pool where feasible, including independent, cross-disciplinary, public-good, technical, safeguards, community, Indigenous, public-authority, operational, and methodological expertise.

No expert shall review their own work without disclosure and appropriate limitation. No vendor shall review its own product as independent. No donor-funded expert shall control findings affecting the donor. No public authority participant shall be presented as issuing official approval unless lawfully authorized.

#### 241.4 Scope, Appointment, and Record Requirements

Every expert mechanism shall have a recorded scope, appointment record, and review file. The scope shall define the question being asked and the boundaries of the review. Expert mechanisms shall not be given vague mandates such as “validate,” “approve,” “clear,” or “endorse” unless those terms are legally and institutionally defined.

The appointment record shall include:

a) appointing authority;

b) expert names or role markers;

c) qualifications or selection basis;

d) conflict disclosures;

e) independence assessment;

f) confidentiality and handling undertakings;

g) access rights;

h) materials provided;

i) review question;

j) deliverable format;

k) deadline;

l) compensation or reimbursement terms, if any;

m) publication and attribution rules; and

n) reporting route.

The review file shall preserve materials reviewed, questions asked, assumptions made, limitations identified, dissent among experts if any, and the final expert output. Where the review is sensitive, the file may be restricted, but it shall remain available to the competent authority.

#### 241.5 Use of Expert Mechanisms in Contested, High-Risk, or High-Consequence Matters

Expert mechanisms shall be used more readily where a matter is contested, high-risk, novel, technically complex, legally sensitive, community-sensitive, Indigenous-sensitive, public-authority-sensitive, security-sensitive, or likely to be externally relied upon. The purpose is to reduce institutional overconfidence before GCRI US publishes, escalates, adopts, or permits reliance on a material output.

Expert review should be considered where:

a) Councils disagree materially;

b) dissent raises credible evidence, method, safeguards, or authority concerns;

c) an output may shape public-sector understanding;

d) a technical framework may be implemented by external institutions;

e) a public-good tool may affect data, privacy, security, or community rights;

f) a publication may influence policy, funding, or institutional behavior;

g) an AI or model-based output is central to the conclusion;

h) a community or Indigenous concern has not been resolved; or

i) the Corporation’s non-execution boundary could be misunderstood.

The competent authority shall decide whether expert review is mandatory, recommended, waived, or unnecessary. Any waiver of expert review for a high-consequence matter shall be recorded with reasons.

#### 241.6 Expert Outputs as Bounded Inputs, Not Self-Grounding Institutional Acts

Expert outputs shall be bounded inputs. They shall not become self-grounding institutional acts, corporate approvals, Board decisions, Council adoption, certifications, recognitions, endorsements, public mandates, regulatory comfort, procurement determinations, or execution authority. Expert review strengthens decision quality; it does not replace decision authority.

An expert output shall state:

a) the question reviewed;

b) the materials reviewed;

c) methodology or review approach;

d) assumptions;

e) limitations;

f) findings or observations;

g) dissent or uncertainty;

h) recommended conditions, if any;

i) unresolved issues; and

j) effect boundary.

The effect boundary shall state that the output is expert input to GCRI US and does not bind the Corporation unless adopted through competent authority. Where the expert output concerns a method, model, tool, framework, or public-good system, the output shall not use the word “validated” unless the validation standard, scope, and limitations are defined.

#### 241.7 Publication Class, Confidentiality, and Challenge Discipline for Expert Outputs

Expert outputs shall be classified according to sensitivity and intended use. Some expert outputs may be public. Others may be internal, restricted, privileged, controlled-room, or confidential because they involve cybersecurity vulnerabilities, personal data, Indigenous knowledge, community-sensitive input, legal risk, public-authority sensitivity, commercial sensitivity, donor issues, or unfinished deliberation.

Publication rules shall ensure that:

a) expert names are used only with consent and attribution approval;

b) institutional affiliations are not used as endorsement without authority;

c) limitations and dissent are not removed;

d) partial quotations do not mislead;

e) sensitive material is redacted or summarized safely;

f) public summaries preserve the output’s effect boundary; and

g) expert outputs are not used in fundraising, procurement, partnership, regulatory, investor, or market-facing claims beyond authority.

Challenge discipline shall allow relevant participants, Councils, or competent functions to challenge an expert output where there is concern about conflict, scope, method, missing evidence, unsafe publication, overclaim, or procedural defect. The challenge may result in clarification, supplemental review, reclassification, withdrawal, or escalation.

#### 241.8 Expert Mechanisms and Council Relationship

Expert mechanisms may be convened by a Council, support a Council, or report into a Council process, but they shall not displace the Council’s role unless expressly authorized. Where expert review is commissioned for a Council matter, the Council shall receive the expert output according to classification rules and shall decide, within its own authority, how to use it.

A Council may:

a) request expert review;

b) identify the question for review;

c) nominate experts subject to conflict screening;

d) receive and deliberate on expert outputs;

e) incorporate expert findings into Council outputs;

f) preserve dissent where Council members disagree with expert conclusions; and

g) escalate expert outputs to competent authority.

A Council may not claim that expert review automatically resolves all questions. Expert review may answer a technical issue while leaving public-law, safeguards, public-claims, community, Indigenous, operational, or governance issues unresolved. The Council record shall preserve that distinction.

#### 241.9 Expert Mechanisms for Nexus-Aligned Public-Good Infrastructure

Where GCRI US contributes to Nexus-aligned public-good infrastructure, risk intelligence, evidence frameworks, AI governance, ontology, standards, resilience models, or national readiness concepts, expert mechanisms may be used to test whether the work is technically credible, legally bounded, socially safe, and non-executionary.

Such expert mechanisms may examine:

a) evidence lineage and reproducibility;

b) model risk and uncertainty;

c) interoperability and open-source governance;

d) cybersecurity and supply-chain risk;

e) data sovereignty, privacy, and compute-to-data constraints;

f) public-sector interpretation;

g) community and Indigenous safeguards;

h) public-claims boundaries;

i) misuse risks by downstream actors; and

j) whether the output could be mistaken for regulated execution, certification, or routeability.

Expert review in this context shall be especially careful not to create market reliance. A technical expert may confirm that a method is coherent within stated assumptions. That does not mean the method is legally approved, financially actionable, insurable, investable, government-adopted, or execution-ready.

#### 241.10 Compensation, Independence, and Funding of Expert Review

Experts may be compensated, reimbursed, or serve pro bono according to approved policy, funding availability, and conflict rules. Compensation shall be transparent to the competent authority and shall not create outcome dependence.

Expert compensation shall not be:

a) contingent on a favorable finding;

b) tied to adoption of an output;

c) linked to procurement or future work;

d) funded by an interested party without disclosure and controls;

e) structured to create private benefit or nonprofit-status risk; or

f) used to purchase endorsement.

Where expert review is funded by a donor, sponsor, member, vendor, or interested institution, the funding relationship shall be disclosed and controlled. The Board, Council, or Secretariat may require independent funding, pooled funding, blind review, external oversight, or additional review where independence could reasonably be questioned.

#### 241.11 Expert Rosters, Qualification Files, and Rotation Records

GCRI US may maintain expert rosters or qualification files to support timely review. Such rosters shall not create endorsement, employment, certification, membership, or guaranteed appointment. They are administrative tools for identifying possible experts.

A roster may include:

a) area of expertise;

b) qualifications;

c) institutional affiliations;

d) conflicts and restrictions;

e) prior review history;

f) confidentiality status;

g) languages or accessibility capabilities;

h) community or Indigenous knowledge protocols where relevant;

i) security or controlled-room clearance status where applicable; and

j) rotation or cooling-off requirements.

Roster inclusion shall be reviewed periodically. Experts may be removed or restricted for conflict, misconduct, breach, poor performance, repeated bias, failure to comply with records rules, or misuse of GCRI US affiliation.

#### 241.12 Interpretive Rule for Expert Mechanisms and Review Bodies

This Section shall be interpreted to preserve a controlling proposition: expert mechanisms within GCRI US exist to strengthen rigor, independence, challenge, safety, and decision readiness, but expert outputs remain bounded inputs that do not create corporate adoption, certification, recognition, endorsement, public mandate, procurement preference, regulatory comfort, or execution authority.

Where ambiguity exists, the interpretation that better preserves:

a) formal expert mandates;

b) independence and conflict review;

c) red-team and replication discipline;

d) controlled scope and review files;

e) use of expert review in high-risk matters;

f) bounded effect of expert outputs;

g) careful publication and attribution;

h) Council relationship discipline;

i) Nexus-aligned non-execution boundaries;

j) compensation independence; and

k) expert roster integrity

shall prevail unless a contrary result is required by law.

### 242. Council Secretariat, Docketing, and Forms-First Operating System (GCRI United States)

#### 242.1 Council Secretariat as the Procedural Spine of the Council System

GCRI US shall maintain a Council Secretariat function to serve as the procedural spine of the Helix Council System. The Council Secretariat may be staffed by employees, officers, contractors, authorized volunteers, or designated governance-support personnel, but its function shall remain institutional and records-based. It shall not operate as an informal assistant pool, event team, communications desk, or private support function for Council chairs.

The Council Secretariat shall support:

a) intake of Council matters;\
b) docketing and case identification;\
c) Council assignment and routing;\
d) meeting notices, agendas, and materials;\
e) participant eligibility, access, and attendance records;\
f) conflict, recusal, and handling checks;\
g) minutes, outputs, consultation logs, and decision-pack linkage;\
h) preservation of dissent and minority reports;\
i) records classification and repository management;\
j) escalation to Board, committees, officers, safeguards, security, legal, communications, finance, or management channels; and\
k) closure, archive, supersession, and public-safe summary controls.

The Council Secretariat shall support validity, not control substance. It may reject incomplete submissions for correction, flag authority defects, require classification, request conflict review, or pause circulation pending safeguards review. It may not suppress issues because they are inconvenient, rewrite Council meaning, manufacture consensus, or convert Council work into corporate approval.

#### 242.2 Forms-First Rule for All Council Matters

All material Council matters shall enter the Council Operating System through approved forms, templates, or equivalent structured intake records. The forms-first rule shall apply to ordinary Council items, urgent matters, consultation requests, working-party mandates, expert-review requests, controlled-room matters, dissent submissions, escalation memoranda, public-safe summaries, and adoption-ready decision-pack inputs.

A Council intake form shall identify, as applicable:

a) submitting person, role, and authority;\
b) Council or Councils requested;\
c) subject matter and case title;\
d) purpose of Council consideration;\
e) question to be answered;\
f) requested output type;\
g) proposed timeline;\
h) materials submitted;\
i) classification and handling considerations;\
j) known conflicts and affected participants;\
k) safeguards, community, Indigenous, public-authority, security, privacy, finance, research, or public-claims sensitivities;\
l) whether cross-Council review may be required;\
m) whether external publication is contemplated; and\
n) proposed escalation or adoption pathway.

No material Council output shall be treated as valid if the matter never entered the forms-first process, unless emergency governance permits provisional handling and the record is completed as soon as practicable.

#### 242.3 Docketing, Case IDs, and Matter Lifecycle Control

Each material Council matter shall be assigned a docket entry and case ID. The case ID shall follow the matter through intake, triage, assignment, meeting, consultation, drafting, dissent, review, escalation, adoption-ready packaging, closure, and archive. The case ID shall allow GCRI US to prove what happened, who handled it, what was reviewed, what outputs were produced, and what authority remains required.

A Council matter lifecycle may include:

a) submitted;\
b) intake complete;\
c) returned for clarification;\
d) admitted;\
e) assigned to Council;\
f) assigned to working party or expert mechanism;\
g) under consultation;\
h) under review;\
i) output drafted;\
j) dissent window open;\
k) Council output finalized;\
l) escalated;\
m) adoption-ready;\
n) adopted by competent authority;\
o) returned for revision;\
p) closed without adoption;\
q) superseded; or\
r) withdrawn.

The Secretariat shall maintain lifecycle status accurately. No person shall publicly describe a matter as adopted, approved, certified, endorsed, final, or active if its docket status does not support that description.

#### 242.4 Intake Triage and Jurisdictional Routing

The Council Secretariat shall conduct intake triage to determine whether a matter is complete enough for Council review and whether it belongs before one Council, multiple Councils, a committee, a working party, an expert mechanism, the Board, management, legal, safeguards, security, privacy, finance, records, communications, or another function.

Triage shall consider:

a) whether the matter falls within a Council mandate;\
b) whether Council review is advisory, consultation-based, risk-based, or adoption-ready;\
c) whether Board reserved matters are implicated;\
d) whether legal or regulatory review is required before Council circulation;\
e) whether safeguards, protected participation, CIC-sensitive, Indigenous, community, or rights-sensitive issues exist;\
f) whether public-authority or PAC-sensitive handling is required;\
g) whether competition, procurement, vendor, or IOC-sensitive issues exist;\
h) whether research-integrity, evidence, data, AI, or ARC-sensitive review is required;\
i) whether public-claims, media, civil-society, or CMC-sensitive review is required; and\
j) whether security, privacy, controlled-room, or restricted-access controls are needed.

The Secretariat may return a matter for clarification, route it to the correct Council, recommend cross-Council review, or escalate it before Council deliberation. Triage shall be recorded and subject to review where challenged.

#### 242.5 Meeting Notice, Agenda, Materials, and Attendance Controls

The Council Secretariat shall support meeting notice, agenda, materials, and attendance controls. Council meetings shall not proceed as valid formal meetings unless notice, agenda, materials, and participation controls meet the requirements of the Council Charter and this Part.

Meeting notices shall identify:

a) Council name;\
b) meeting type;\
c) date, time, and modality;\
d) agenda items and case IDs;\
e) materials circulated;\
f) classification and handling requirements;\
g) expected outputs;\
h) quorum and voting requirements where applicable;\
i) conflict and recusal reminders;\
j) attendance limitations; and\
k) public-description restrictions where relevant.

Materials shall be distributed only to eligible participants. Attendance shall be recorded by name or approved role marker, capacity, participant type, and access level. Where controlled-room or restricted segments occur, attendance for those segments shall be recorded separately. A person may attend one portion of a meeting without being eligible for another.

#### 242.6 Minutes, Records, and Council Output Certification

The Council Secretariat shall ensure that minutes and Council records are prepared, reviewed, corrected, classified, and preserved. Minutes shall be complete enough to support institutional reliance without becoming unsafe, excessive, or misleading.

Council minutes shall record:

a) Council name and meeting ID;\
b) date, time, and modality;\
c) chair, rapporteur, Secretariat support, and participants;\
d) participant capacity where relevant;\
e) quorum status;\
f) agenda and case IDs;\
g) materials reviewed;\
h) conflicts, recusals, exclusions, and abstentions;\
i) summary of deliberation sufficient to show reasoning;\
j) motions, votes, consensus statements, or procedural rulings;\
k) dissent, minority notes, objections, and unresolved issues;\
l) outputs approved or referred;\
m) escalation actions;\
n) public-description or publication restrictions; and\
o) action items and closure status.

Council output certification shall confirm only that the output followed Council procedure. It shall not certify that the substance is legally, scientifically, technically, publicly, or institutionally approved unless the competent authority has granted that effect.

#### 242.7 Consultation Logs, Comment Disposition, and Feedback Records

Where Councils conduct or support consultation, the Secretariat shall maintain consultation logs and comment disposition records. This discipline is essential to prevent performative consultation and to show that input was received, considered, and handled.

A consultation log shall include:

a) consultation title and case ID;\
b) consultation question;\
c) consultation period;\
d) participant categories;\
e) materials provided;\
f) submissions received;\
g) confidentiality or attribution terms;\
h) comments accepted, rejected, deferred, or escalated;\
i) reasons for material disposition decisions;\
j) dissent or unresolved issues;\
k) safeguards or handling restrictions; and\
l) feedback or closure communication.

Comment disposition shall not be manipulated to create false consensus. Where comments are rejected, the record shall give a reason at an appropriate level of detail. Where comments raise legal, safeguards, security, public-claims, or authority issues, they shall be escalated, not buried in a general summary.

#### 242.8 Secretariat Role in Controlled Rooms and Restricted Council Process

The Council Secretariat shall administer controlled-room and restricted Council processes where required. It shall coordinate access approvals, materials segmentation, secure circulation, restricted attendance, note-taking rules, output classification, and closure controls.

Controlled-room administration shall include:

a) controlled-room trigger and authority;\
b) approved participant list;\
c) access basis and duration;\
d) confidentiality and handling attestations;\
e) materials inventory;\
f) meeting or review log;\
g) restricted minutes;\
h) public-safe summary route;\
i) access revocation at closure; and\
j) archive location.

Controlled-room process shall not be used to hide ordinary disagreement, avoid Council scrutiny, exclude dissenters without cause, or create unaccountable decision-making. It exists to protect sensitive information while preserving traceable governance.

#### 242.9 Secretariat Neutrality, Independence, and Non-Suppression Duty

The Council Secretariat shall maintain neutrality in Council administration. It may enforce procedure, but it shall not manipulate outcomes. It may advise on forms and records, but it shall not reshape Council conclusions. It may correct overclaim, but it shall not suppress legitimate criticism.

The Secretariat shall have a non-suppression duty with respect to:

a) dissent and minority reports;\
b) safeguards concerns;\
c) conflict and recusal issues;\
d) public-claims warnings;\
e) public-authority overclaim concerns;\
f) community and Indigenous participation concerns;\
g) competition and vendor-capture issues;\
h) research-integrity warnings;\
i) security and privacy concerns; and\
j) non-execution boundary concerns.

Where a Council chair, executive, donor, sponsor, trustee, member, public authority, vendor, or participant pressures the Secretariat to suppress or alter the record, the Secretariat shall escalate through protected channels.

#### 242.10 Integration With Corporate Records, Board Packs, and Adoption Pathways

Council Secretariat records shall integrate with corporate records, Board packs, adoption pathways, public-claims review, and publication processes. Council work that informs institutional action must be traceable.

Where a Council output is routed for adoption, the Secretariat shall ensure that the decision pack includes:

a) case ID;\
b) Council output;\
c) output type and effect code;\
d) minutes or deliberation summary;\
e) dissent or minority views;\
f) conflict and recusal record;\
g) consultation log where applicable;\
h) safeguards, legal, security, privacy, finance, research, or public-claims review status;\
i) recommended adoption language;\
j) unresolved issues; and\
k) public-description limits.

A Board or committee shall not be asked to adopt a Council-derived output without knowing its procedural history and limitations.

#### 242.11 Secretariat Capacity, Systems, and Continuity

GCRI US shall ensure that the Council Secretariat has sufficient capacity, systems, and continuity to support the Council system. Under-resourced Secretariat functions create records failure, public-claims risk, participation harm, and adoption defects.

Secretariat capacity shall include:

a) trained personnel;\
b) secure repositories;\
c) docketing tools;\
d) template library;\
e) classification system;\
f) meeting and attendance records;\
g) consultation management tools;\
h) access-control coordination;\
i) version control;\
j) escalation workflows; and\
k) continuity plan.

The Secretariat shall not depend on one person’s private files, personal email, private calendar, or unshared knowledge. Continuity arrangements shall ensure that Council records, open dockets, pending outputs, access lists, and sensitive matters can continue through personnel transition.

#### 242.12 Interpretive Rule for Council Secretariat, Docketing, and Forms-First Operating System

This Section shall be interpreted to preserve a controlling proposition: the Council Secretariat and forms-first operating system of GCRI US exist to make Council work valid, traceable, safeguarded, classified, procedurally fair, adoption-ready where appropriate, and incapable of being transformed into informal authority or public overclaim.

Where ambiguity exists, the interpretation that better preserves:

a) Secretariat neutrality;\
b) mandatory intake and docketing;\
c) case ID lifecycle control;\
d) correct routing;\
e) meeting and attendance validity;\
f) faithful minutes and output certification;\
g) consultation disposition discipline;\
h) controlled-room administration;\
i) non-suppression of material concerns;\
j) integration with Board and corporate records; and\
k) Secretariat capacity and continuity

shall prevail unless a contrary result is required by law.

### 243. Council Intake, Agenda Formation, and Matter Classification (GCRI United States)

#### 243.1 Intake as the First Validity Gate for Council Work

Council intake shall serve as the first validity gate for all material Helix Council work of GCRI US. No matter shall move into formal Council deliberation unless it has been received, screened, classified, docketed, and routed through the Council Secretariat or another approved intake function. Intake is not a clerical step. It is the point at which the Corporation determines whether a question is suitable for Council consideration, whether the correct Council has been identified, whether safeguards are needed, whether conflicts are visible, whether the matter may create public-claims or non-execution risk, and whether the record is sufficient to support later reliance.

A matter may be submitted for Council intake by:

a) the Board or a Board committee;\
b) the Chair, Secretary, Treasurer, executive leadership, or another authorized officer;\
c) the Council Bureau or Council Chair;\
d) the Secretariat or governance-spine function;\
e) another Council or cross-Council mechanism;\
f) a working party, expert mechanism, or rapporteur;\
g) a member, partner, host institution, or invited participant where permitted;\
h) a safeguards, integrity, security, legal, public-claims, or records function; or\
i) another person or body authorized under the Council Charter.

The intake record shall establish what the Council is being asked to do. A Council shall not be asked to “discuss” a matter where the real institutional purpose is to approve, validate, endorse, de-risk, publish, certify, or create reliance. If the submitter seeks advisory review, the intake shall say advisory review. If the submitter seeks adoption-ready input, the intake shall say adoption-ready input. If the submitter seeks escalation of a risk, the intake shall say escalation. The Council system shall not rely on ambiguous requests.

#### 243.2 Mandatory Intake Information and Completeness Review

Every material Council intake shall include sufficient information to permit classification, routing, conflict review, safeguards assessment, and agenda formation. A matter shall not proceed merely because it is urgent, senior-sponsored, donor-supported, public-facing, or strategically attractive.

The intake record shall include, at minimum:

a) title of the matter;\
b) submitting person, office, Council, or body;\
c) authority or basis for submission;\
d) requested Council or Councils;\
e) issue statement;\
f) specific question to be answered;\
g) requested output type;\
h) intended use of the output;\
i) deadline or timing driver;\
j) materials submitted;\
k) proposed publication class;\
l) known conflicts;\
m) affected participants, institutions, communities, public authorities, sectors, or knowledge holders;\
n) whether the matter may require legal, safeguards, security, privacy, research, finance, public-claims, or Board review;\
o) whether external reliance, public communication, consultation, or adoption is contemplated; and\
p) whether the matter implicates the non-execution boundary.

The Secretariat may reject, return, hold, or request clarification where the intake is incomplete. A returned intake shall state what is missing and whether any interim protective action is required. A matter that cannot be clearly framed shall not be forced into Council deliberation. Poor framing creates poor governance.

#### 243.3 Matter Classification by Substance, Sensitivity, and Institutional Effect

Each Council matter shall be classified by substance, sensitivity, and institutional effect. Classification shall determine routing, access, handling, required review, meeting design, output type, and publication rules.

Substance classification shall identify whether the matter concerns:

a) public authority, public law, regulatory perception, public finance, or administrative feasibility;\
b) operations, infrastructure, technology, cybersecurity, implementation, or vendor neutrality;\
c) research, evidence, method, data, AI, ontology, or publication integrity;\
d) civil society, media, transparency, public meaning, consultation, or communications integrity;\
e) community, Indigenous, lived context, rights-sensitive, land-sensitive, or safeguards-heavy concerns;\
f) cross-Council systemic risk, resilience, sustainability, or Nexus-aligned public-good architecture;\
g) Council governance, procedure, membership, composition, or role discipline; or\
h) risk, incident, correction, escalation, or emergency concern.

Sensitivity classification shall identify whether the matter includes:

i) personal information;\
ii) protected participation or whistleblower content;\
iii) community-sensitive or Indigenous knowledge;\
iv) public-authority-sensitive information;\
v) security, privacy, or controlled-room material;\
vi) commercially sensitive or competition-sensitive information;\
vii) legal privilege or litigation risk;\
viii) donor, sponsor, vendor, or funding sensitivity;\
ix) unpublished research or draft standards; or\
x) public-claims risk.

Institutional-effect classification shall identify whether the matter is for discussion, advisory input, consultation, warning, escalation, public-safe summary, adoption-ready recommendation, or closure. The stronger the intended effect, the stronger the required record.

#### 243.4 Agenda Formation and Priority Setting

Council agendas shall be formed through a disciplined process that reflects mandate, urgency, materiality, readiness, risk, participant availability, and governance need. Agenda formation shall not be controlled by personality, donor pressure, public visibility, media urgency, staff convenience, or the preferences of the most powerful participants.

Agenda priority may be given to matters that:

a) affect Board or corporate reserved matters;\
b) require Council input before publication or adoption;\
c) involve serious safeguards, public-claims, public-authority, community, Indigenous, security, or non-execution risk;\
d) are time-sensitive because of consultation deadlines, filing deadlines, public events, or Board decision cycles;\
e) involve unresolved dissent or cross-Council disagreement;\
f) concern high-impact public-good infrastructure or Nexus-aligned architecture;\
g) require correction of misinformation, overclaim, or defective records; or\
h) affect Council integrity, participation safety, or mandate discipline.

Agenda formation shall also protect lower-power matters from being displaced indefinitely by high-profile items. Community harm, safeguards concerns, dissent, procedural defects, and public-claims risks shall not be deprioritized because they are less commercially attractive or less visible.

#### 243.5 Agenda Notice, Consent Agenda, and Restricted Agenda Items

Council agendas shall be circulated with sufficient notice to allow participants to prepare, disclose conflicts, request recusal, seek clarification, identify handling concerns, and submit preliminary comments. Agenda materials shall state the expected output and whether any item requires vote, consensus testing, dissent window, consultation disposition, controlled-room handling, or escalation.

A Council may use a consent agenda for routine procedural items, such as approval of prior minutes, administrative updates, non-substantive scheduling, or closure of low-risk matters. A consent agenda shall not be used for:

a) adoption-ready outputs;\
b) public-safe summaries of sensitive matters;\
c) matters involving dissent or minority reports;\
d) conflicts, recusals, or participant challenges;\
e) safeguards, community, Indigenous, public-authority, or security concerns;\
f) matters with public-claims implications;\
g) cross-Council disagreements; or\
h) any matter requiring substantive deliberation.

Restricted agenda items shall be clearly marked. Participants not authorized for restricted items shall be excluded from the relevant segment, and the minutes shall reflect segmented attendance. Restriction shall protect legitimate sensitivity and shall not be used to avoid scrutiny.

#### 243.6 Classification-Driven Routing to Councils, Working Parties, Expert Mechanisms, or Corporate Functions

Matter classification shall drive routing. The Secretariat shall route a matter to the correct Council, Councils, working party, expert mechanism, or corporate function based on substance, sensitivity, and intended effect.

Routing may include:

a) PAC for public-authority, regulatory, public-finance, public-law, administrative, and public-sector feasibility issues;\
b) IOC for implementation, operations, infrastructure, cybersecurity, interoperability, and vendor-neutrality issues;\
c) ARC for evidence, method, research, AI, data, ontology, reproducibility, and publication-integrity issues;\
d) CMC for transparency, public meaning, communications integrity, consultation accessibility, media, and civil-society concerns;\
e) CIC for community, Indigenous, rights-sensitive, lived-context, dignity, land-sensitive, and safeguards-heavy issues;\
f) cross-Council process for multi-domain matters;\
g) expert mechanism for specialized independent review;\
h) safeguards, legal, security, privacy, finance, records, or public-claims functions for control review; and\
i) Board or committee review where corporate authority is implicated.

Routing shall be recorded. Where routing is contested, the challenge shall be resolved through the Council Operating System, Council Bureau, Secretariat, Secretary, or Board process as appropriate.

#### 243.7 Agenda Readiness and Pre-Meeting Review

Before a matter appears on a Council agenda, the Secretariat or Bureau shall confirm agenda readiness. Readiness review protects participants from being asked to deliberate without sufficient information or proper controls.

Agenda readiness shall require:

a) completed intake;\
b) case ID assigned;\
c) Council jurisdiction confirmed;\
d) materials prepared and classified;\
e) participant eligibility reviewed;\
f) conflicts and recusal issues flagged;\
g) handling and controlled-room requirements identified;\
h) expected output type stated;\
i) decision or escalation pathway identified;\
j) translation, accessibility, or participant-support needs considered where relevant; and\
k) public-claims boundary understood.

Where agenda readiness is not satisfied, the item may be deferred, returned, rerouted, or admitted only for preliminary discussion with no formal output. A Council shall not be pressured to produce formal output from incomplete materials.

#### 243.8 Emergency, Urgent, and Stop-the-Line Agenda Items

The Council Operating System may permit emergency, urgent, or stop-the-line agenda items where a delay could create material harm to GCRI US, participants, public trust, safeguards, security, public-good assets, records, or the non-execution boundary. Such items shall be narrowly framed, recorded, and subject to follow-up.

Urgent Council matters may include:

a) public overclaim requiring correction;\
b) misuse of Council status;\
c) unsafe publication of community or Indigenous material;\
d) public-authority overclaim;\
e) controlled-room breach;\
f) competition-sensitive discussion requiring immediate intervention;\
g) research-integrity defect in imminent publication;\
h) security or privacy concern in a technical release;\
i) retaliation or participation-safety concern; or\
j) non-execution boundary drift.

Urgency shall not eliminate records discipline. If emergency handling prevents full intake before action, a retrospective intake record shall be completed promptly. Urgent Council review shall not be used to bypass the Board, legal, safeguards, security, or other required authority.

#### 243.9 Public-Claims Review at Intake and Agenda Stage

Public-claims review shall begin at intake and agenda stage where a matter may later be referenced publicly. The Council system shall prevent public overclaim before it occurs, not merely correct it afterward.

Public-claims review shall ask:

a) Could this matter be misunderstood as GCRI US approval?\
b) Could participation be misread as endorsement?\
c) Could public-authority involvement be misread as government mandate?\
d) Could community or Indigenous input be misread as consent?\
e) Could academic review be misread as validation?\
f) Could operator review be misread as vendor or procurement approval?\
g) Could civil-society or media input be misread as public mandate or media endorsement?\
h) Could the matter imply execution-side authority?\
i) Could the output be used by a participant for marketing, fundraising, procurement, investor, regulatory, or political claims?\
j) Does the output require limitation language before circulation?

Where public-claims risk exists, the item shall include public-description controls from the beginning. A well-controlled public-safe summary is easier to prepare when the risk is recognized at intake.

#### 243.10 Intake and Agenda Controls for Nexus-Aligned Public-Good Matters

Matters involving Nexus-aligned public-good architecture shall receive heightened intake and agenda review. These matters may involve evidence rails, risk intelligence, AI governance, resilience finance interfaces, standards, readiness frameworks, public-sector use, open-source infrastructure, or cross-entity coordination. Such matters are valuable but can easily be misread as execution, certification, routeability, or market validation.

For Nexus-aligned matters, intake shall identify:

a) whether the matter is public-good, research, standards, evidence, policy, technical, training, consultation, or governance in nature;\
b) whether any downstream execution-side use is contemplated by separate actors;\
c) whether GCRI US could be perceived as approving, routing, certifying, underwriting, brokering, advising, settling, or guaranteeing;\
d) whether other entities such as GCRI Canada, GRF, GRA, protocol authorities, host institutions, or delivery actors are involved;\
e) whether legal separateness and public-description limitations are clear;\
f) whether public-good assets, open-source materials, data, or AI outputs are involved; and\
g) whether cross-Council review is required.

Agenda materials for such matters shall include explicit non-execution framing. Councils may improve public-good quality and governance. They shall not become execution infrastructure.

#### 243.11 Reclassification, Deferral, and Return of Matters

A Council matter may be reclassified, deferred, returned, or rerouted where new information shows that the original classification was incomplete, wrong, unsafe, or too narrow.

Reclassification may occur where:

a) a public-law issue emerges;\
b) a community or Indigenous concern appears;\
c) evidence or method uncertainty becomes material;\
d) implementation or security risk is identified;\
e) public-claims risk increases;\
f) conflicts are discovered;\
g) participant capacity is misdescribed;\
h) the matter requires Board or legal review;\
i) a draft output exceeds Council authority; or\
j) the matter is no longer suitable for Council handling.

Deferral shall be used where more information, review, consent, access control, or participant support is required. Return shall be used where the submitter must clarify purpose, materials, authority, or intended output. Rerouting shall be used where another Council or function is more appropriate.

The record shall state the reason for reclassification, deferral, return, or rerouting. This prevents later confusion and shows that the Council system acted deliberately.

#### 243.12 Interpretive Rule for Council Intake, Agenda Formation, and Matter Classification

This Section shall be interpreted to preserve a controlling proposition: all material Council work in GCRI US must begin with disciplined intake, classification, docketing, agenda readiness, routing, and public-claims review so that Councils deliberate only on properly framed, properly handled, properly classified, and properly authorized matters.

Where ambiguity exists, the interpretation that better preserves:

a) intake as a validity gate;\
b) completeness review;\
c) substance, sensitivity, and effect classification;\
d) fair and risk-based agenda formation;\
e) appropriate notice and restricted agenda handling;\
f) classification-driven routing;\
g) agenda readiness;\
h) emergency and stop-the-line discipline;\
i) public-claims control from the outset;\
j) Nexus-aligned non-execution framing; and\
k) reclassification, deferral, and return procedures

shall prevail unless a contrary result is required by law.

### 244. Council Meetings, Convening Rules, and Deliberation Standards (GCRI United States)

#### 244.1 Authority to Convene Council Meetings

Each Helix Council of GCRI US may be convened only by the persons or bodies authorized under the applicable Council Charter, Council Operating System, Board-approved delegation, or other recorded authority. A Council meeting shall not be valid merely because participants assemble, a calendar invitation is issued, a chair calls a discussion, or an external partner requests engagement. Formal Council convening requires authority, notice, agenda discipline, classification, and records.

A Council meeting may be convened by:

a) the Council Chair or authorized Acting Chair;\
b) the Council Bureau, where the Charter permits;\
c) the Secretariat, where acting under approved procedure;\
d) the Board or a Board committee, where Council input is required;\
e) a competent officer, where the matter is properly routed;\
f) a cross-Council coordination mechanism, where joint deliberation is required; or\
g) another authority expressly identified in the Council Charter.

The convening record shall identify the meeting type, purpose, Council authority, agenda, expected output, participants, classification, and records custodian. Informal preparatory calls may occur, but they shall not be described as Council meetings unless convened under this Section.

#### 244.2 Meeting Types and Procedural Classes

Council meetings shall be classified by procedural type so that participants understand the meeting’s purpose and effect. The Council Operating System shall distinguish between ordinary meetings, special meetings, emergency meetings, controlled-room meetings, consultation meetings, working sessions, joint Council sessions, bureau meetings, committee meetings, expert-review meetings, and public-facing convenings.

A meeting may be classified as:

a) Ordinary Council Meeting, for regular docketed matters and Council operations;\
b) Special Council Meeting, for a specific matter requiring focused deliberation;\
c) Emergency or Urgent Council Meeting, for time-sensitive protective, corrective, or escalation matters;\
d) Controlled-Room Meeting, for restricted, sensitive, or need-to-know deliberation;\
e) Consultation Session, for receiving structured input rather than forming a Council output;\
f) Working Session, for drafting, synthesis, technical review, or preparation;\
g) Joint Council Session, for multi-domain matters involving more than one Council;\
h) Bureau or Committee Meeting, for procedural support or delegated committee work;\
i) Expert Review Meeting, for specialist review under mandate; and\
j) Public-Facing Council Convening, for approved public engagement, subject to public-claims controls.

Each meeting type shall carry different notice, quorum, participation, recording, output, and publication rules. A consultation session shall not be treated as a Council approval meeting. A working session shall not be treated as final deliberation. A public-facing convening shall not create institutional position unless adopted through the proper authority.

#### 244.3 Notice, Agenda, Materials, and Preparation Duties

Formal Council meetings shall be preceded by notice sufficient to permit meaningful preparation, conflict disclosure, recusal review, access control, safeguards review, and participant readiness. Notice shall be proportionate to the meeting type and urgency, but shall never be so vague that participants cannot understand what is being asked of them.

Meeting notice shall include:

a) Council name and meeting type;\
b) date, time, duration, and modality;\
c) convening authority;\
d) agenda items and case IDs;\
e) purpose of each agenda item;\
f) expected output type;\
g) materials circulated;\
h) classification and handling rules;\
i) conflict and recusal reminders;\
j) quorum or participation requirements;\
k) whether voting, consensus testing, or dissent capture will occur;\
l) whether controlled-room segments will occur; and\
m) public-description restrictions.

Participants shall be expected to review materials, disclose conflicts, identify access or handling concerns, and prepare comments before the meeting. Where participants have not received materials in time, the Council may discuss the matter preliminarily but should not finalize formal outputs unless the Charter permits and the record explains why.

#### 244.4 Meeting Modality, Remote Participation, and Secure Convening

Council meetings may occur in person, by video conference, by secure digital platform, by hybrid modality, by written procedure, or through another approved method. The modality shall be appropriate to the subject matter, sensitivity, participant needs, accessibility, and records requirements.

Remote and hybrid meetings shall ensure:

a) identity verification;\
b) participant eligibility;\
c) secure access links;\
d) controlled waiting rooms where needed;\
e) prohibition on unauthorized recording;\
f) management of chat, screen sharing, file sharing, and transcription;\
g) separate handling for restricted agenda items;\
h) reliable attendance records;\
i) secure voting or consensus confirmation where applicable; and\
j) backup process if technical failure affects participation.

For controlled-room, CIC-sensitive, PAC-sensitive, security-sensitive, or legally sensitive matters, ordinary commercial meeting tools may be insufficient unless configured with adequate controls. GCRI US shall match the tool to the risk. Convenience shall not determine security.

#### 244.5 Deliberation Standards and Chairing Discipline

Council deliberation shall be conducted to produce useful institutional input, not performative discussion. The Chair or acting procedural leader shall maintain disciplined, fair, and respectful deliberation aligned with the meeting purpose.

Deliberation standards shall require:

a) relevance to the docketed matter;\
b) respect for participant capacity and role;\
c) distinction between fact, opinion, inference, institutional position, and personal experience;\
d) disclosure of uncertainty and assumptions;\
e) preservation of dissent and unresolved issues;\
f) avoidance of personal attacks, intimidation, or retaliation;\
g) avoidance of commercial solicitation or political campaigning;\
h) avoidance of public-authority, community, Indigenous, media, academic, or industry overclaim;\
i) observance of classification and confidentiality rules; and\
j) routing of matters beyond Council authority to the proper function.

The Chair may intervene to stop improper discussion, redirect irrelevant matters, require written submission, call for recusal review, pause for safeguards review, or close a segment where necessary. Such intervention shall be recorded where material.

#### 244.6 Competition-Safe, Safeguards-Safe, and Public-Claims-Safe Meeting Conduct

Council meetings shall be conducted in a manner that is competition-safe, safeguards-safe, and public-claims-safe. These controls apply to all Councils but shall be especially important in the IOC, CIC, PAC, CMC, and cross-Council sessions.

Competition-safe conduct shall prohibit price, bid, market-allocation, customer, procurement, confidential business strategy, or coordinated market behavior discussions.

Safeguards-safe conduct shall require dignity, non-retaliation, protected participation, attribution control, trauma-sensitive handling where appropriate, and prohibition on pressure to disclose sensitive knowledge.

Public-claims-safe conduct shall prevent participants from treating attendance, silence, comment, or preliminary discussion as approval, endorsement, recognition, certification, consent, public mandate, or adoption.

Where unsafe discussion begins, the Chair, Secretariat, safeguards lead, legal observer, or any participant may raise a procedural stop. The meeting record shall capture that the issue was stopped or rerouted without unnecessarily recording sensitive details.

#### 244.7 Minutes, Record of Deliberation, and Action Tracking

Each formal Council meeting shall have minutes or an equivalent record appropriate to its classification. Minutes shall preserve institutional memory and procedural validity. They shall not be stenographic unless required, but they must be complete enough to evidence what was considered, what was concluded, what was not concluded, and what remains unresolved.

Minutes shall include:

a) meeting identifier;\
b) Council and meeting type;\
c) date, time, modality, and chair;\
d) participants and capacity, subject to handling rules;\
e) quorum status;\
f) agenda and case IDs;\
g) materials reviewed;\
h) conflicts, recusals, abstentions, and exclusions;\
i) summary of material discussion;\
j) decisions within Council authority;\
k) recommendations, warnings, or advisory outputs;\
l) dissent, minority notes, objections, or unresolved concerns;\
m) escalation items;\
n) action items, owners, and deadlines;\
o) classification and publication status; and\
p) correction and approval process.

Action tracking shall continue until closure. Council action items shall not disappear after a meeting. The Secretariat shall maintain status, follow-up, and closure evidence.

#### 244.8 Public-Facing Convenings and External Participation Events

Where a Council participates in a public-facing convening, external forum, listening session, webinar, conference, consultation event, or stakeholder roundtable, the event shall be governed by public-claims, attribution, records, and authority controls. Public-facing convenings may advance mission, but they also create risk of overclaim.

Before any public-facing Council event, GCRI US shall determine:

a) whether the event is a Council meeting, public consultation, educational event, listening session, or external appearance;\
b) who is authorized to speak;\
c) whether statements are institutional, personal, or educational;\
d) whether recording is permitted;\
e) whether participant names may be used;\
f) whether public summaries will be issued;\
g) whether questions and comments will become part of the record;\
h) whether safeguards or moderation are required; and\
i) what disclaimers are necessary.

Public events shall not imply that Council outputs are adopted, that participants endorse GCRI US, or that GCRI US has received public mandate. Event materials shall use bounded language.

#### 244.9 Attendance, Participation Failure, and Meeting Integrity

Council attendance shall be tracked. Repeated non-attendance, late attendance, failure to prepare, failure to disclose conflicts, disruptive conduct, or participation only for public status may affect renewal, voting eligibility, committee assignment, or continuing participation.

Meeting integrity concerns include:

a) unauthorized attendees;\
b) undisclosed observers;\
c) recording without permission;\
d) forwarding materials without authorization;\
e) participation from conflicted persons;\
f) use of AI transcription or note-taking tools without approval;\
g) disclosure of controlled materials;\
h) domination by one participant or bloc;\
i) intimidation or retaliation; and\
j) post-meeting misrepresentation of outcomes.

Where meeting integrity is compromised, the Council may invalidate affected outputs, re-run the discussion, correct minutes, revoke access, impose restrictions, or escalate to safeguards, security, integrity, legal, or Board review.

#### 244.10 Adjournment, Continuation, and Closure of Meetings

A Council meeting may be adjourned, continued, paused, or closed according to the Council Charter and procedural rules. Adjournment may be required where quorum is lost, materials are incomplete, conflicts are unresolved, participants require safeguards protection, technical failure prevents fair participation, or the matter requires review by another function.

A meeting closure record shall identify:

a) matters completed;\
b) matters deferred;\
c) outputs approved or pending;\
d) dissent or objection windows;\
e) follow-up actions;\
f) escalations;\
g) next meeting or decision point; and\
h) records and classification status.

A meeting shall not be treated as complete until the Secretariat has captured the required records and action items. Closure is procedural, not merely the end of a call.

#### 244.11 Meeting Defects, Cure, and Re-Convening

Where a Council meeting suffers a material procedural defect, the defect shall be reviewed and cured where possible. A meeting defect may affect validity of outputs, public use, adoption-ready routing, or reliance.

Material defects may include:

a) lack of authority to convene;\
b) defective notice;\
c) missing agenda or case ID;\
d) quorum failure;\
e) improper participant inclusion or exclusion;\
f) unresolved conflict;\
g) required controlled-room process not used;\
h) unauthorized recording or disclosure;\
i) failure to capture dissent;\
j) output approval outside threshold; or\
k) public communication before finalization.

Cure may include corrected minutes, re-notice, re-convening, re-vote, supplemental consultation, dissent inclusion, reclassification, withdrawal of output, or public correction. Some defects may not be curable and may require the matter to restart.

#### 244.12 Interpretive Rule for Council Meetings, Convening Rules, and Deliberation Standards

This Section shall be interpreted to preserve a controlling proposition: Council meetings of GCRI US shall be valid only when properly convened, noticed, classified, attended, chaired, recorded, and closed under procedures that protect fair deliberation, safeguards, competition safety, public-claims discipline, and Council mandate limits.

Where ambiguity exists, the interpretation that better preserves:

a) authority to convene;\
b) correct meeting classification;\
c) sufficient notice and materials;\
d) secure and accessible modality;\
e) disciplined deliberation;\
f) competition, safeguards, and public-claims safety;\
g) accurate minutes and action tracking;\
h) bounded public-facing convenings;\
i) attendance and meeting-integrity controls;\
j) proper adjournment and closure; and\
k) cure of procedural defects

shall prevail unless a contrary result is required by law.

### 245. Council Records, Minutes, Registers, and Evidence of Proceedings (GCRI United States)

#### 245.1 Records as the Validity Spine of the Council System

Council records shall constitute the validity spine of the Helix Council System of GCRI US. A Council does not act merely because participants spoke, a meeting occurred, a draft circulated, or a chair stated an outcome. A Council acts only where the proceeding is recorded with sufficient clarity to show authority, notice, attendance, deliberation, conflicts, dissent, output type, classification, escalation, and closure.

Council records shall be maintained to prove:

a) which Council or Council body acted;\
b) under what authority the matter was considered;\
c) what question was placed before the Council;\
d) who participated and in what capacity;\
e) whether quorum or procedural requirements were met;\
f) what materials were reviewed;\
g) what conflicts, recusals, restrictions, or access limits applied;\
h) what views, warnings, dissent, or unresolved issues were recorded;\
i) what output was produced and with what effect code;\
j) whether the output was internal, restricted, public-safe, advisory, escalated, or adoption-ready; and\
k) what follow-up, escalation, adoption, correction, or closure occurred.

The Council record shall protect both institutional memory and institutional restraint. It shall allow GCRI US to show that participation was real, deliberation was disciplined, dissent was preserved, and no Council output was overclaimed beyond its authority.

#### 245.2 Required Council Record Categories

GCRI US shall maintain a defined set of Council record categories. Each category shall have an owner, classification, retention rule, and repository location.

Council records may include:

a) Council Charters, interim charters, amendments, and supersession notes;\
b) Council participant registers, seat registers, role declarations, capacity statements, and authorization records;\
c) Bureau, committee, working-party, drafting-group, and expert-mechanism mandates;\
d) intake forms, docket entries, case IDs, matter-classification records, and routing decisions;\
e) meeting notices, agendas, materials lists, attendance records, and quorum confirmations;\
f) minutes, meeting summaries, controlled-room notes, procedural rulings, and action logs;\
g) conflict disclosures, recusal records, access restrictions, and challenge records;\
h) consultation logs, comment-disposition tables, participant feedback, and public-safe summaries;\
i) advisory notes, warnings, recommendations, review memoranda, dissent notes, minority reports, escalation memoranda, and adoption-ready package inputs;\
j) publication approvals, attribution consents, redaction records, and public-description records;\
k) correction, withdrawal, supersession, reclassification, and closure records; and\
l) annual Council performance, composition, risk, and lifecycle review records.

No material Council record shall be held only in personal files, private email, unmanaged chat, local drives, event platforms, social media messages, or external partner systems. Council records are corporate records of GCRI US and shall remain under institutional control.

#### 245.3 Minutes and Deliberation Records

Each formal Council meeting, Bureau meeting, committee meeting, working-party meeting, joint session, controlled-room session, or expert-review meeting shall have minutes or an equivalent deliberation record appropriate to the meeting type and classification. The record shall be accurate, proportionate, and sufficient for later institutional reliance.

Minutes shall include, as applicable:

a) meeting title, Council, body, case ID, and meeting type;\
b) date, time, modality, and convening authority;\
c) chair, rapporteur, Secretariat support, and records custodian;\
d) participants, observers, guests, liaisons, and role capacity;\
e) quorum status and procedural validity;\
f) agenda items and materials reviewed;\
g) conflicts disclosed, recusals applied, abstentions, exclusions, and access limits;\
h) summary of material deliberation;\
i) warnings, objections, dissent, minority views, and unresolved issues;\
j) procedural rulings and challenges;\
k) motions, votes, consensus statements, or output approvals;\
l) outputs produced, output type, effect code, and classification;\
m) escalations, action items, owners, and deadlines;\
n) publication or attribution restrictions; and\
o) approval, correction, and closure status.

Minutes need not be transcripts unless required by law, policy, or the sensitivity of the matter. They shall not be so thin that the Council’s reasoning disappears, nor so detailed that they expose protected persons, sensitive community knowledge, public-authority-sensitive matters, security vulnerabilities, privileged information, or commercially sensitive material unnecessarily.

#### 245.4 Council Registers and Participant Status Records

GCRI US shall maintain Council registers to track Council constitution, participant status, seat allocation, role rights, terms, renewals, vacancies, restrictions, recusals, and public-description permissions. These registers shall support accuracy in internal operations and public materials.

Council registers may include:

a) Council Register identifying current Councils, charters, review dates, and status;\
b) Seat Register identifying seat class, term, holder, role, and renewal status;\
c) Participant Register identifying Council participants, capacity, access level, and public-description permissions;\
d) Bureau and Officer Register identifying chairs, vice-chairs, rapporteurs, committee chairs, and working-party leads;\
e) Observer and Guest Register for non-member participation;\
f) Controlled-Access Register for restricted materials, controlled-room participation, and access expiry;\
g) Conflict and Recusal Register for matter-specific restrictions;\
h) Output Register for Council outputs, effect codes, version status, and publication class; and\
i) Public Description Register for approved external use of Council titles, participant names, affiliations, and summaries.

Registers shall be reviewed periodically and promptly updated after appointment, resignation, term expiry, removal, suspension, access change, role change, conflict change, or public-description correction. An outdated register is a public-claims risk.

#### 245.5 Evidence of Proceedings and Reliance Conditions

Council records shall serve as evidence of proceedings. A Council output may be relied upon internally only where the record shows that the proceeding was valid for the intended effect. A Council output may be externally referenced only where the output’s publication class, effect code, attribution rules, and public-description limits permit such reference.

Before relying on a Council output, GCRI US shall verify:

a) the output is final for Council purposes;\
b) the output has the correct case ID and version;\
c) the Council acted within mandate;\
d) quorum, notice, and procedural requirements were satisfied;\
e) conflicts and recusals were handled;\
f) dissent and limitations were preserved;\
g) required legal, safeguards, security, privacy, finance, research, or public-claims review occurred or was waived by competent authority;\
h) the output has not been withdrawn or superseded; and\
i) the output is being used only within its effect boundary.

A defective or incomplete record shall not be cured by personal recollection alone. Where the record is insufficient, the matter shall be corrected, reapproved, rerouted, reclassified, or treated as informal input.

#### 245.6 Records Classification, Confidentiality, and Access Controls

Council records shall be classified according to sensitivity, legal status, public meaning, participant safety, security, privacy, public-authority sensitivity, competition sensitivity, community and Indigenous knowledge boundaries, research confidentiality, and institutional reliance risk.

Classification levels may include:

a) public;\
b) public-safe summary;\
c) internal;\
d) restricted;\
e) confidential;\
f) privileged or legal-sensitive;\
g) controlled-room;\
h) clean-room or need-to-know; and\
i) protected-participation record.

Access shall follow role, need-to-know, classification, and time-bounded authority. A person may be a Council participant and still lack access to certain records. A Council chair may not access every controlled-room record by title alone. A donor, sponsor, member, public authority, vendor, academic partner, media participant, or community participant shall receive only records appropriate to their role and classification.

Where records contain CIC-sensitive, Indigenous, community, whistleblower, personal, public-authority-sensitive, security, or commercially sensitive information, access shall be narrowed and logged.

#### 245.7 Attribution, Consent, Redaction, and Public-Safe Records

Council records shall distinguish between internal deliberation records and public-safe records. Public-safe records may summarize Council work without exposing sensitive information or overstating authority.

Before any Council record is published, quoted, summarized, or externally circulated, GCRI US shall review:

a) publication class;\
b) effect code;\
c) participant attribution permissions;\
d) institutional affiliation permissions;\
e) public-authority capacity limits;\
f) media independence considerations;\
g) community and Indigenous consent and knowledge-boundary rules;\
h) security, privacy, and legal restrictions;\
i) donor, sponsor, vendor, or competition sensitivity; and\
j) whether limitations, dissent, and non-execution disclaimers remain visible.

Redaction shall preserve meaning. It shall not remove inconvenient dissent, warnings, or limitations merely to create a cleaner narrative. Public-safe summaries shall be truthful, bounded, and tied to the authoritative record.

#### 245.8 Correction, Amendment, Supersession, and Withdrawal of Council Records

Council records may be corrected, amended, superseded, or withdrawn only through recorded procedure. Silent edits are prohibited where they affect meaning, authority, classification, output effect, public description, dissent, participant status, or institutional reliance.

Corrections may include:

a) clerical correction;\
b) correction of participant name, role, or capacity;\
c) correction of quorum or attendance record;\
d) addition of omitted conflict, recusal, abstention, or dissent;\
e) clarification of output type or effect code;\
f) revision of public-description limits;\
g) reclassification of sensitivity;\
h) withdrawal of defective output;\
i) supersession by later Council output; and\
j) public-safe correction where external use occurred.

Substantive corrections shall be approved by the Council, Bureau, Secretariat, Secretary, or competent authority according to the nature of the defect. Where a participant believes minutes or outputs misrepresent their contribution, capacity, dissent, or consent, they may request correction through the Council Operating System.

#### 245.9 Retention, Archiving, and Destruction Rules

Council records shall be retained and archived according to the GCRI US records-retention schedule. Records with constitutional, governance, public-good, legal, safeguards, security, financial, membership, or cross-entity significance may require long-term or permanent retention. Routine administrative records may have shorter retention periods, subject to legal, audit, or dispute requirements.

Retention rules shall identify:

a) record category;\
b) retention period;\
c) repository;\
d) custodian;\
e) classification;\
f) legal-hold conditions;\
g) access restrictions;\
h) archive method; and\
i) destruction approval and method.

No Council record shall be destroyed while it is subject to legal hold, audit, investigation, safeguards review, public-claims review, dispute, correction request, or Board inquiry. Destruction shall be documented. Sensitive records shall be destroyed securely.

#### 245.10 Digital Records, AI Tools, Transcripts, and Meeting Artifacts

Council records may be created or stored through digital tools, provided that GCRI US preserves integrity, access control, confidentiality, retention, and authoritative-copy discipline. Digital convenience shall not compromise governance validity.

Digital record controls shall address:

a) approved platforms;\
b) access rights;\
c) version control;\
d) audit logs;\
e) backups;\
f) exportability;\
g) retention settings;\
h) legal-hold capability;\
i) unauthorized sharing prevention; and\
j) secure deletion.

AI tools shall not be used to record, transcribe, summarize, classify, or analyze Council meetings or materials unless permitted by policy and classification. AI-generated minutes or summaries shall not become authoritative records without human review and approval. Sensitive Council materials, including CIC, Indigenous, public-authority-sensitive, security, legal, whistleblower, personal, or controlled-room records, shall not be processed through unauthorized AI systems.

Meeting chats, polls, shared documents, recordings, transcripts, whiteboards, and platform logs may constitute Council records where they contain substantive material. The Secretariat shall determine what must be preserved and what may be discarded under retention rules.

#### 245.11 Cross-Entity and Nexus-Aligned Record Boundaries

Where Council work involves GCRI Canada, GRF, GRA, protocol authorities, host institutions, members, public authorities, universities, communities, Indigenous bodies, donors, or external partners, GCRI US shall maintain clear record boundaries. Council records of GCRI US shall not be treated as records of another entity unless a shared records instrument so provides. Likewise, records of another entity shall not be treated as GCRI US approval.

Cross-entity records shall identify:

a) parties involved;\
b) capacity of each participant;\
c) which entity convened the process;\
d) which entity owns the record;\
e) which entity may publish or rely on the output;\
f) confidentiality and access rules;\
g) public-description limits; and\
h) whether separate approvals are required.

Nexus-aligned cooperation shall preserve legal separateness and non-execution discipline. A Council record concerning Nexus public-good architecture shall not imply that GCRI US has authority over other entities, delivery stacks, financial actors, or protocol bodies unless a separate lawful instrument says so.

#### 245.12 Interpretive Rule for Council Records, Minutes, Registers, and Evidence of Proceedings

This Section shall be interpreted to preserve a controlling proposition: Council authority within GCRI US exists only through accurate, classified, retained, traceable, and correctable records that evidence proceedings, preserve dissent, protect sensitive participation, control public meaning, and prevent informal deliberation from becoming unrecorded authority.

Where ambiguity exists, the interpretation that better preserves:

a) records as Council validity spine;\
b) complete Council record categories;\
c) accurate minutes and deliberation records;\
d) current Council registers;\
e) reliance only on procedurally valid records;\
f) classification and access control;\
g) attribution and public-safe disclosure discipline;\
h) correction and supersession integrity;\
i) retention and legal-hold compliance;\
j) digital and AI records control; and\
k) cross-entity record boundaries

shall prevail unless a contrary result is required by law.

### 246. Council Notices, Gazette Linkage, and Publication of Council Acts (GCRI United States)

#### 246.1 Notice as a Validity, Fairness, and Reliance Control

Council notices shall operate as validity, fairness, and reliance controls within the Helix Council System of GCRI US. Notice is not merely an administrative reminder. It is the instrument through which participants understand what is being convened, why it is being convened, what role they are expected to play, what materials they may rely upon, what restrictions apply, and what institutional effect may follow.

Each material Council notice shall identify:

a) the Council, committee, working party, expert mechanism, or joint session being convened;

b) the convening authority;

c) the meeting type and procedural class;

d) the date, time, modality, and access method;

e) the agenda items, matter IDs, and expected outputs;

f) the participant roles eligible to attend, speak, draft, vote, observe, or submit written comments;

g) the classification, confidentiality, handling, controlled-room, or public-description rules;

h) any known conflict, recusal, consent, or eligibility requirements;

i) any pre-read, draft, consultation package, evidence pack, technical material, or public-safe summary under review;

j) whether dissent, minority notes, written objections, or procedural challenges may be submitted and by when;

k) whether the session may result in an advisory note, warning, recommendation, consultation summary, public-safe summary, escalation memorandum, or adoption-ready input; and

l) the records custodian and process for correction of notices, minutes, or outputs.

Notice shall be clear enough that a reasonable participant can decide whether to attend, prepare, disclose conflicts, request recusal, request accommodations, object to classification, identify public-claims risk, or seek safeguards review. Where notice is defective and the defect may affect participation, fairness, quorum, handling, or reliance, the matter shall be deferred, re-noticed, cured, or limited to informal discussion.

#### 246.2 Notice Channels, Proof of Delivery, and Notice Records

GCRI US shall maintain approved notice channels for Council business. Notices may be delivered by secure email, Council portal, approved collaboration platform, calendar invitation linked to the Council Operating System, registered communication where appropriate, or another approved channel. Sensitive notices may require restricted delivery, role-marker delivery, encrypted access, or limited distribution.

The Secretariat shall maintain proof of notice sufficient to show:

a) who was notified;

b) when notice was sent;

c) through which channel notice was delivered;

d) what materials were included or linked;

e) what classification and handling rules applied;

f) whether delivery failed or access was denied;

g) whether any participant requested clarification, accommodation, recusal, or correction; and

h) whether any waiver, reduced notice, or emergency notice procedure was used.

Proof of notice may include email logs, portal logs, platform delivery records, attendance confirmation, acknowledgement receipts, Secretary certification, or other evidence. Notice records shall be preserved with the relevant matter file. A Council output shall not proceed to adoption-ready status where the underlying notice was materially defective and not cured.

#### 246.3 Ordinary, Special, Emergency, Restricted, and Public Notices

Council notices shall be classified according to meeting type and public meaning. Ordinary notices are for regular Council business. Special notices are for focused matters requiring dedicated attention. Emergency notices are for urgent protective or corrective matters. Restricted notices are for controlled, sensitive, confidential, or need-to-know deliberation. Public notices are for approved public-facing Council events, consultations, or public-safe outputs.

Ordinary notice shall follow the standard timeline in the Council Charter. Special notice shall identify the specific matter and shall not be used to add unrelated business without proper procedure. Emergency notice may be shorter, but shall state the emergency basis and shall be followed by a complete record. Restricted notice shall identify handling rules without unnecessarily disclosing sensitive content. Public notice shall be accurate, bounded, and non-misleading.

No public notice shall state or imply that:

a) the Council is a corporate governing body;

b) the Council has adopted a GCRI US position unless competent authority has done so;

c) participation equals endorsement;

d) public authority attendance equals government support;

e) industry attendance equals vendor approval;

f) academic attendance equals scientific validation;

g) civil-society or media attendance equals public mandate; or

h) community or Indigenous attendance equals consent.

Public notices shall carry appropriate disclaimers and public-description limits.

#### 246.4 Gazette Linkage and Authoritative Notice System

GCRI US may maintain an internal Gazette, Council Register, notice ledger, public notice page, or equivalent authoritative notice system for Council acts that require institutional traceability. Gazette linkage shall be used where Council constitution, Council Charter adoption, Council leadership appointment, public-safe Council output, consultation opening, consultation closure, major Council recommendation, cross-Council review, suspension, reconstitution, or dissolution requires a stable record.

The Gazette or notice system may record:

a) Council constitution and status;

b) current Council Charter and public summary;

c) Council leadership and bureau appointments;

d) consultation notices and comment periods;

e) public-safe summaries of Council outputs;

f) adoption-ready referrals;

g) public corrections, withdrawals, or supersessions;

h) Council lifecycle events, including suspension, reconstitution, merger, or dissolution;

i) public-description restrictions; and

j) links to authoritative records where public access is permitted.

Gazette linkage shall not publish restricted, privileged, protected, community-sensitive, Indigenous, security-sensitive, commercially sensitive, or public-authority-sensitive material unless lawfully reviewed and approved. The Gazette shall provide authoritative notice where appropriate, not uncontrolled transparency.

#### 246.5 Publication of Council Acts and Public-Safe Summaries

Council acts may be published only where publication is authorized, classification permits, public-claims controls are satisfied, attribution permissions are secured, and the output’s effect code is preserved. Publication shall be treated as a governance act because public release can create reliance, misinterpretation, reputational effect, and external use.

A Council act may be published as:

a) a public-safe summary;

b) a consultation opening notice;

c) a consultation closure notice;

d) a comment disposition summary;

e) an advisory note;

f) a public-interest warning;

g) a cross-Council synthesis;

h) a Council annual report section;

i) a Charter or public Council description; or

j) a public correction, withdrawal, or supersession notice.

Before publication, the Secretariat or competent function shall verify:

i) output type and effect code;

ii) Council authority and mandate;

iii) classification;

iv) public-claims boundary;

v) dissent and limitation treatment;

vi) attribution consent;

vii) public authority, community, Indigenous, media, academic, and industry overclaim controls;

viii) legal, safeguards, security, privacy, finance, research, or communications review where required;

ix) version status; and

x) publication approval.

Publication shall not convert an advisory Council act into a corporate decision. The published record shall state its effect.

#### 246.6 Publication Timing, Embargoes, and Controlled Release

Council publications may be subject to timing controls, embargoes, staged release, controlled release, or delayed release where necessary to protect legal review, safeguards, public authority sensitivity, security, privacy, community consent, Indigenous knowledge boundaries, research integrity, or Board decision-making.

Publication may be delayed where:

a) a dissent or minority report must be incorporated;

b) consent or attribution review is incomplete;

c) public-claims risk remains unresolved;

d) a public authority capacity statement requires correction;

e) community or Indigenous knowledge handling is unresolved;

f) security or privacy review is pending;

g) legal privilege, litigation, or regulatory sensitivity exists;

h) a related Board decision has not occurred;

i) a consultation disposition log is incomplete; or

j) a public-safe summary requires redaction.

Embargoes shall be recorded and time-bound. A publication hold shall not be used to bury inconvenient dissent, conceal misconduct, suppress protected reporting, or delay correction of public misinformation where correction is required. Controlled release shall specify recipients, conditions, permitted use, onward-sharing restrictions, and expiry.

#### 246.7 Corrections, Withdrawals, Supersessions, and Public Notice of Defective Council Acts

Where a published Council act is inaccurate, misleading, defective, misclassified, overclaimed, wrongly attributed, unsafe, superseded, or withdrawn, GCRI US shall correct the public record. Correction discipline is central to institutional trust. The Corporation shall not leave defective public materials in circulation because correction is inconvenient or reputationally uncomfortable.

A correction, withdrawal, or supersession notice shall identify, as appropriate:

a) the Council act affected;

b) the date and version of the affected output;

c) whether the act is corrected, withdrawn, superseded, reclassified, or restricted;

d) the reason at a public-safe level of detail;

e) the current authoritative version or status;

f) whether external reliance should cease;

g) whether prior quotations, public claims, or participant descriptions must be corrected;

h) whether related public materials require update; and

i) the contact or process for clarification.

Where the defect concerns sensitive information, public notice shall be carefully worded. The notice shall correct the public meaning without unnecessarily exposing protected persons, community knowledge, security vulnerabilities, legal matters, or confidential information.

#### 246.8 Notice and Publication Controls for Council Participant Status

Council participant status, Council leadership status, bureau membership, committee membership, working-party participation, observer status, and expert-review participation shall be publicly noticed only where accurate, authorized, and safe. Public listing is not required for all participants and may be inappropriate for public authority, community, Indigenous, media, protected, or sensitive roles.

Where participant status is published, the notice shall state:

a) role and Council;

b) capacity, where relevant;

c) whether participation is institutional or personal;

d) term or status, where appropriate;

e) public-description limitations; and

f) whether the listing implies no endorsement, certification, public authority, or representation beyond the stated role.

Public participant lists shall be promptly corrected after resignation, removal, suspension, term expiry, role change, or public-description withdrawal. Former participants may be listed only in dated historical form where accurate and permitted. A person shall not be kept on a public Council list for optics after authority or participation has ended.

#### 246.9 Notice and Publication Controls for Consultations

Consultation notices shall be designed to enable meaningful participation and prevent public misunderstanding. A consultation notice shall identify the purpose, question, materials, comment period, who may submit, how input will be used, whether comments may be public, whether anonymity or confidentiality is available, whether the consultation creates consent or endorsement, and how closure will be reported.

Consultation notices shall include:

a) plain-language summary;

b) technical or detailed materials where needed;

c) submission instructions;

d) deadline;

e) confidentiality and attribution options;

f) accessibility supports where feasible;

g) safeguards and non-retaliation statement where appropriate;

h) public-claims boundary;

i) comment disposition process; and

j) anticipated next step.

A consultation notice shall not imply that GCRI US has already decided the matter if input is genuinely being sought. Nor shall it imply that consultation participants will control the outcome where the competent authority retains decision-making power. Consultation must be honest about effect.

#### 246.10 Gazette Linkage With Corporate Records and Board Authority

Where a Council act is linked to the Gazette or public notice system and later informs Board action, the Gazette entry shall be linked to the corporate record. This linkage shall show the chain from Council intake, Council deliberation, Council output, adoption-ready routing, Board or competent authority action, and final publication.

The linkage shall preserve:

a) Council advisory nature;

b) Board or competent authority adoption record;

c) dissent and limitations;

d) review gates completed;

e) public-claims boundaries;

f) current version;

g) supersession history; and

h) public-safe record.

The Gazette shall not be used to create authority that the Board has not granted. If a Council act is only advisory, the Gazette shall say so. If the Board adopts a Council-derived output, the Gazette may note adoption only after the Board record exists.

#### 246.11 Misuse of Notices, Gazette Entries, or Published Council Acts

Misuse of Council notices, Gazette entries, or published Council acts shall be treated as an integrity matter. Misuse may occur where a participant, member, donor, sponsor, vendor, public authority participant, academic participant, media participant, community participant, or external actor uses Council publication to imply status, approval, or authority not granted.

Misuse may include:

a) quoting Council acts without limitations;

b) using draft notices as proof of adoption;

c) presenting consultation participation as consent;

d) presenting Gazette listing as certification;

e) presenting Council membership as partnership;

f) presenting public-authority Council attendance as government approval;

g) presenting IOC review as vendor endorsement;

h) presenting ARC review as scientific validation;

i) presenting CMC review as media or civil-society endorsement;

j) presenting CIC input as community or Indigenous approval; or

k) using Council acts in procurement, investor, regulatory, fundraising, or marketing materials beyond authority.

GCRI US may require correction, issue public clarification, restrict participant status, revoke access, suspend Council participation, terminate membership, or escalate to legal, integrity, safeguards, or Board review.

#### 246.12 Interpretive Rule for Council Notices, Gazette Linkage, and Publication of Council Acts

This Section shall be interpreted to preserve a controlling proposition: Council notices, Gazette entries, and published Council acts of GCRI US shall provide accurate, controlled, classified, and authoritative public or internal notice of Council process without creating false adoption, endorsement, certification, public mandate, execution authority, or external reliance beyond the recorded effect.

Where ambiguity exists, the interpretation that better preserves:

a) notice as a validity and fairness control;

b) proof of delivery and notice records;

c) proper distinction among ordinary, special, emergency, restricted, and public notices;

d) Gazette linkage as authoritative notice, not authority creation;

e) publication only with effect-code and public-claims controls;

f) controlled timing and embargo discipline;

g) correction, withdrawal, and supersession transparency;

h) careful publication of participant status;

i) honest consultation notices;

j) linkage with corporate records and Board authority; and

k) remedies for misuse of Council acts

shall prevail unless a contrary result is required by law.

### 247. Council Conflicts, Recusals, Competition Safety, and Anti-Capture Controls (GCRI United States)

#### 247.1 Council Integrity as a Condition of Structured Participation

Council integrity shall be a condition of participation in the Helix Council System of GCRI US. The Councils are designed to bring public authorities, operators, researchers, civil society, media, communities, Indigenous participants, experts, members, and partners into disciplined deliberation. That design creates value only if conflicts, recusal, competition sensitivity, public-claims risk, and capture risk are actively controlled.

Each Council shall therefore maintain conflict and integrity controls sufficient to ensure that:

a) participants disclose material interests before influencing matters;\
b) conflicted participants do not shape outputs in which they have an improper interest;\
c) commercial participants do not convert Council access into procurement or market advantage;\
d) public authority participants are not overclaimed as official endorsers;\
e) academic participants are not used as false validators;\
f) civil-society and media participants are not used as public mandate;\
g) community and Indigenous participants are not used as consent or social license;\
h) donors, sponsors, vendors, members, founders, or executives do not capture Council agenda or outputs; and\
i) Council outputs remain advisory, bounded, evidence-based, safeguarded, and non-executionary.

Council integrity shall be assessed at intake, agenda formation, meeting conduct, drafting, voting, publication, external use, and post-publication correction. A conflict discovered late shall still be addressed. Delay in discovery shall not validate an unsafe process.

#### 247.2 Disclosure Duties for Council Participants

Every Council participant shall disclose material interests, affiliations, roles, relationships, funding links, public responsibilities, professional obligations, representation limits, and external incentives that may affect or appear to affect their participation. Disclosure shall be proportionate to role and risk, but shall be required before a participant receives sensitive materials, participates in a controlled-room session, joins a working party, votes, drafts outputs, or influences adoption-ready materials.

Disclosable interests may include:

a) employment, consulting, board, advisory, fiduciary, public office, academic, media, civil-society, community, Indigenous, donor, sponsor, vendor, member, or execution-side roles;\
b) financial interests, ownership interests, grants, contracts, reimbursements, honoraria, sponsorships, procurement opportunities, or future work expectations;\
c) institutional relationships with GCRI US, GCRI Canada, GRF, GRA, protocol bodies, host institutions, delivery actors, funders, vendors, public authorities, universities, or members;\
d) involvement in drafting or promoting the matter under review;\
e) relationship to a person, institution, community, public authority, vendor, donor, or sponsor affected by the matter;\
f) prior public position that may materially constrain independent review;\
g) confidential obligations to another institution that may limit participation; and\
h) any pressure, inducement, expectation, or instruction received from an external actor concerning the Council matter.

Disclosure shall be updated when circumstances change. A participant shall not wait for a formal annual cycle if a new conflict arises before a meeting, vote, draft, consultation, or publication.

#### 247.3 Recusal Rules for Council Deliberation, Drafting, Voting, and Access

Recusal shall be applied wherever a participant’s interest, affiliation, role, duty, access, or external incentive may impair or appear to impair independent Council participation. Recusal may be partial or complete, depending on the matter.

A recusal may restrict a participant from:

a) receiving materials;\
b) attending a meeting or segment;\
c) joining deliberation;\
d) proposing language;\
e) joining a drafting group;\
f) voting or joining consensus testing;\
g) serving as rapporteur or reviewer;\
h) participating in public-safe summary preparation;\
i) communicating externally about the matter; or\
j) accessing follow-up records.

Recusal shall be recorded in the Council records. The record shall state the matter, participant, role, conflict category, restriction applied, whether quorum was affected, and whether any replacement or alternate was admitted. Where recording details would expose sensitive information, the record may use controlled language.

A participant shall not avoid recusal by abstaining only at the final vote after influencing earlier stages. Recusal may apply to the entire influence chain.

#### 247.4 Competition Safety and Antitrust Discipline

All Councils shall observe competition safety, and the IOC and cross-Council sessions involving market participants shall apply heightened antitrust discipline. Council convening shall never become a forum for market coordination, procurement signaling, price alignment, vendor exclusion, bid coordination, information exchange, or strategic commercial positioning.

Participants shall not discuss or exchange:

a) prices, rates, margins, fees, premiums, commissions, discounts, or commercial terms;\
b) bids, tenders, procurement strategies, proposal intentions, or award expectations;\
c) customer, client, insured, borrower, funder, investor, supplier, or counterparty allocation;\
d) non-public market strategy, business plans, capacity, supply constraints, or future commercial conduct;\
e) competitor exclusion, boycott, refusal to deal, preferred-provider alignment, or coordinated procurement pressure;\
f) confidential customer, account, claim, project, or transaction information; or\
g) information that could reasonably facilitate anti-competitive conduct.

Where a discussion begins to enter competition-sensitive territory, the Chair, Secretariat, legal observer, IOC lead, or any participant may stop the discussion. The minutes shall record that the matter was stopped or redirected, without reproducing sensitive commercial detail. Competition-safety reminders should be included in agendas for meetings involving industry, operators, vendors, financial institutions, insurers, technology providers, consultancies, or procurement-adjacent actors.

#### 247.5 Anti-Capture Controls for Donors, Sponsors, Vendors, Members, and Founders

Councils shall operate under anti-capture controls. Capture occurs when a donor, sponsor, vendor, member, founder, public authority, sector, academic network, civil-society bloc, media actor, community representative, or technical group gains disproportionate influence over Council agenda, composition, drafting, outputs, public description, or escalation.

Anti-capture controls shall include:

a) transparent disclosure of funding and sponsorship links;\
b) limits on sponsor or donor influence over agenda and outputs;\
c) restrictions on vendor drafting of outputs affecting vendor interests;\
d) balanced seat allocation and rotation;\
e) independent facilitation where dominance risk exists;\
f) dissent and minority-report protection;\
g) no privileged access to Council outputs before approved release;\
h) no public-description advantage for funders or sponsors;\
i) conflict review for repeated leadership by related participants; and\
j) Board or integrity escalation where capture risk becomes material.

A donor may support Council operations, but may not own the Council. A sponsor may fund a convening, but may not control the agenda. A vendor may provide technical facts, but may not write vendor-neutral standards around its product. A founder may support mission coherence, but may not bypass Council procedure. A member may participate, but may not convert membership into influence rights beyond the governing instruments.

#### 247.6 Public-Authority, Academic, Media, Community, and Indigenous Overclaim Controls

Council conflicts are not limited to money. They include representational overclaim. GCRI US shall therefore control how public authority, academic, media, civil-society, community, and Indigenous participation is described and used.

The following shall be prohibited without explicit authority and record:

a) describing PAC participation as government endorsement, regulatory comfort, public mandate, procurement eligibility, or policy adoption;\
b) describing ARC participation as scientific validation, university endorsement, peer-reviewed approval, or final research certification;\
c) describing CMC participation as civil-society consensus, public mandate, media endorsement, or political support;\
d) describing CIC participation as community consent, Indigenous consent, social license, tribal approval, or affected-population endorsement;\
e) describing IOC participation as vendor approval, operator endorsement, commercial validation, procurement readiness, or implementation preference.

Capacity statements, public-description limits, attribution consent, and public-safe summaries shall be used to prevent overclaim. Where an overclaim occurs, GCRI US shall correct it promptly and may restrict the participant or issuer responsible.

#### 247.7 Integrity Review for Council Outputs With Interested Participation

Where a Council output is prepared with participation by interested persons, the output shall undergo integrity review proportionate to the risk. Interested participation is not automatically prohibited; many Council participants are valuable precisely because they are close to the issues. However, proximity must be controlled.

Integrity review may consider:

a) whether interested participants disclosed their interests;\
b) whether their participation was appropriate;\
c) whether they influenced drafting, voting, or consensus beyond permitted scope;\
d) whether dissent or independent review was included;\
e) whether the output favors a private, institutional, sectoral, or political interest;\
f) whether public language could be used for external advantage;\
g) whether a disinterested review is required; and\
h) whether publication should be limited, delayed, or accompanied by caveats.

Outputs involving a donor, sponsor, vendor, member, public authority, Indigenous body, community, academic institution, media organization, or regulated actor shall be reviewed carefully before public use. The more valuable an output could be externally, the stronger the integrity control required.

#### 247.8 Remedies for Conflict, Recusal, Competition, or Capture Breach

Where a conflict, recusal, competition, or capture breach occurs, GCRI US shall take corrective action proportionate to materiality, intent, harm, recurrence, and public reliance.

Remedies may include:

a) correction of minutes or output records;\
b) exclusion of tainted comments, drafts, votes, or consensus statements;\
c) re-deliberation without conflicted participants;\
d) reclassification or withdrawal of the output;\
e) public-safe correction;\
f) participant warning, restriction, suspension, or removal;\
g) access revocation;\
h) referral to safeguards, integrity, legal, security, Board, or committee review;\
i) amendment of Council Charter or procedure;\
j) disbanding or reconstituting a working party, committee, or Council; and\
k) notification to affected persons or counterparties where required.

A breach shall not be ignored because the output is useful, the participant is senior, the donor is important, the timeline is tight, or the issue is reputationally uncomfortable. Integrity is a condition of institutional reliance.

#### 247.9 Interpretive Rule for Council Conflicts, Recusals, Competition Safety, and Anti-Capture Controls

This Section shall be interpreted to preserve a controlling proposition: Council participation in GCRI US shall remain independent, disclosed, conflict-managed, competition-safe, anti-capture, and resistant to representational overclaim, so that Council outputs cannot be used to launder private advantage, public authority, academic validation, media support, community consent, Indigenous consent, or execution-side legitimacy.

Where ambiguity exists, the interpretation that better preserves disclosure, recusal, competition safety, anti-capture discipline, capacity clarity, public-description restraint, independent review, and effective remedies shall prevail unless a contrary result is required by law.

### 248. Safeguards, Protected Participation, Accessibility, and Non-Retaliation in Councils (GCRI United States)

#### 248.1 Safeguards as a Core Condition of Council Legitimacy

Council participation in GCRI US shall be governed by safeguards as a core condition of legitimacy. A Council process shall not be considered institutionally sound merely because it is well-attended, technically strong, procedurally efficient, or publicly impressive. It must also be safe, respectful, accessible, non-extractive, non-retaliatory, and capable of protecting persons whose participation may expose them to institutional, professional, social, cultural, political, commercial, community, or personal risk.

Safeguards shall apply across all Councils and shall be heightened where participation involves community experience, Indigenous knowledge, affected populations, public authority sensitivities, whistleblowing, employment vulnerability, donor pressure, vendor pressure, public criticism, media visibility, rights-sensitive issues, or controlled information. The safeguards function of Part X shall protect the integrity of participation before, during, and after Council proceedings.

Council safeguards shall require that:

a) participants understand the purpose, scope, use, and limits of their participation;

b) no participant is pressured to disclose information beyond the agreed scope;

c) dissent and objection can be expressed without retaliation;

d) sensitive identity, community, Indigenous, public-authority, media, security, legal, or professional information is handled appropriately;

e) participants can request confidentiality, role-marker treatment, anonymization, recusal review, accessibility support, or protected escalation where appropriate;

f) Council outputs do not misuse participant contributions;

g) public summaries do not convert participation into endorsement, consent, approval, or public mandate; and

h) harm, retaliation, intimidation, exclusion, or misrepresentation is treated as a governance concern, not interpersonal inconvenience.

The Council system shall be judged not only by what it produces, but by how it treats those whose knowledge makes production possible.

#### 248.2 Protected Participation Across All Council Classes

Protected participation shall apply to all Council classes, including PAC, IOC, ARC, CMC, CIC, cross-Council sessions, working parties, expert mechanisms, consultations, public-facing events, controlled-room deliberations, and adoption-ready review processes. Protection shall not depend on whether a participant is powerful, institutional, public-facing, under-resourced, technical, community-based, or invited for one session only.

Protected participation shall include the right, subject to role and procedure, to:

a) receive clear notice of purpose and expected use;

b) understand whether participation is public, internal, restricted, attributed, anonymized, or controlled;

c) disclose conflicts or representation limits without penalty;

d) decline attribution where rules permit;

e) submit dissent, minority views, objections, or corrections;

f) raise safeguards, accessibility, conflict, public-claims, or handling concerns;

g) withdraw from participation where conditions become unsafe or materially different from what was represented;

h) report retaliation or intimidation through protected routes; and

i) request correction where their contribution, role, affiliation, consent, or position is misrepresented.

Protected participation does not give a participant unlimited control over Council outcomes. It ensures that participation is not coerced, distorted, exploited, or punished. It also ensures that GCRI US can rely on Council records as evidence of fair process.

#### 248.3 Non-Retaliation Rule for Council Participation, Dissent, and Reporting

No trustee, officer, executive, Council chair, Bureau member, rapporteur, Secretariat staff member, employee, contractor, volunteer, member, donor, sponsor, vendor, public authority participant, institutional representative, community participant, Indigenous participant, media participant, academic participant, operator, observer, guest, or external actor acting in relation to GCRI US may retaliate against a person for good-faith Council participation, dissent, objection, refusal to consent, correction request, conflict disclosure, safeguards concern, whistleblowing, public-claims concern, or protected escalation.

Retaliation includes:

a) removal, suspension, non-renewal, exclusion, or demotion from Council role because of protected action;

b) denial of access, participation opportunity, speaking time, committee assignment, working-party role, or future invitation for retaliatory reasons;

c) reputational attack, public disparagement, informal blacklisting, intimidation, harassment, or social exclusion;

d) pressure on a participant’s employer, funder, institution, public authority, community, academic body, media organization, or professional network;

e) withdrawal of reimbursement, honorarium, travel support, accessibility support, or participation support for retaliatory reasons;

f) misuse of confidentiality, conflict, security, public-claims, or conduct rules to silence a participant;

g) public naming, doxxing, exposure, or misattribution of a participant who requested protected handling;

h) manipulation of minutes, records, outputs, or summaries to erase or distort dissent; and

i) adverse treatment against a person who supports, corroborates, or assists another protected participant.

Retaliation shall be treated as a serious Council-integrity breach regardless of whether the underlying concern is later substantiated. Good-faith participation and reporting are protected because they preserve institutional truth.

#### 248.4 Accessibility, Inclusion, and Meaningful Participation Standards

GCRI US shall design Council participation to be accessible and meaningful. Formal invitation is not sufficient if materials are inaccessible, procedures are unclear, timing is unreasonable, language is exclusionary, technology is difficult to use, costs are uncompensated where burdens are substantial, or power dynamics prevent genuine contribution.

Accessibility and inclusion standards may include:

a) clear meeting materials and plain-language summaries where appropriate;

b) sufficient preparation time for non-insider participants;

c) reasonable accommodation for disability, caregiving, language, connectivity, time-zone, or participation constraints where feasible;

d) structured opportunities to submit written input before or after meetings;

e) facilitation that prevents domination by frequent speakers or technical insiders;

f) participation support, reimbursement, or honoraria where lawful, appropriate, and necessary to avoid extractive participation;

g) role-marker, anonymized, or confidential participation where public naming would be unsafe;

h) culturally respectful process for Indigenous, community, and rights-sensitive participation;

i) avoidance of unnecessary jargon, acronyms, and internal shorthand in consultation materials; and

j) feedback loops explaining how input was handled.

Accessibility does not require that every Council process be open to everyone. It requires that the participants invited or entitled to participate can do so in a real and safe manner consistent with the purpose of the proceeding.

#### 248.5 Safeguards Review for Community, Indigenous, Rights-Sensitive, and Affected-Population Matters

Any Council matter involving community, Indigenous, rights-sensitive, land-sensitive, lived-experience, affected-population, vulnerable-person, public-health, emergency, disaster, trauma, conflict, displacement, surveillance, geospatial, AI, environmental, or social-harm issues shall be screened for safeguards review. The CIC shall have a special role, but safeguards review shall not be limited to the CIC.

Safeguards review shall assess:

a) who may be affected by the Council matter;

b) whether participation could expose persons or communities to harm;

c) whether consent, permission, or representation authority is required;

d) whether Indigenous knowledge, community knowledge, cultural material, or lived-experience testimony is involved;

e) whether information should be anonymized, role-marked, restricted, or excluded from publication;

f) whether public summaries could overclaim consent, endorsement, or social license;

g) whether grievance or correction routes are available;

h) whether participation support is necessary;

i) whether trauma-informed or culturally appropriate facilitation is needed; and

j) whether the matter should be paused, redesigned, or escalated before deliberation continues.

Where safeguards review identifies unacceptable risk, GCRI US shall not proceed merely because the work is strategically important. Public-good purpose does not excuse unsafe process.

#### 248.6 Handling of Sensitive Identity, Attribution, and Representation

Council processes shall handle identity, attribution, and representation with precision. Participants may have different levels of visibility and authority. A person may speak as an individual, institutional representative, public authority observer, former official, academic expert, media professional, community member, Indigenous knowledge-holder, technical adviser, or invited guest. Misstating capacity can create harm.

GCRI US shall therefore maintain attribution controls requiring that:

a) participant names are used only where permitted;

b) institutional affiliations are described accurately;

c) public authority capacity is not overstated;

d) media participation is not described as media endorsement;

e) academic participation is not described as institutional validation;

f) community or Indigenous participation is not generalized as broad consent;

g) personal lived-experience testimony is not converted into collective position;

h) role-marker treatment is used where identity protection is necessary; and

i) public summaries preserve capacity limitations.

Attribution consent may be specific to a document, meeting, output, quote, public summary, biography, roster, or event. Consent for one use shall not imply consent for all future uses.

#### 248.7 Council Conduct Standards and Dignity Rules

Council participation shall be governed by conduct standards and dignity rules. GCRI US shall not permit Council spaces to become hostile, extractive, performative, intimidating, discriminatory, commercially predatory, politically coercive, or disrespectful.

Participants shall:

a) engage respectfully and substantively;

b) avoid personal attacks, harassment, intimidation, and humiliation;

c) respect time limits and facilitation;

d) respect confidentiality and handling rules;

e) avoid using Council access for solicitation, lobbying, procurement pressure, fundraising pressure, or media leverage;

f) avoid misrepresenting their role or authority;

g) avoid pressuring others to endorse, consent, withdraw dissent, or disclose sensitive information;

h) avoid discriminatory or degrading language;

i) respect community and Indigenous knowledge boundaries; and

j) follow escalation routes for concerns.

The Chair, Secretariat, safeguards lead, or competent authority may intervene where conduct standards are breached. Intervention may include warning, pause, removal from meeting, restricted participation, referral to safeguards or integrity review, or suspension pending review.

#### 248.8 Safeguards in Public-Facing Council Events and Consultations

Public-facing Council events and consultations shall include safeguards appropriate to the audience, subject matter, and risk. Public events can create reputational, social, political, employment, or safety exposure for participants. Consultation processes can also raise expectations that must be handled honestly.

Safeguards for public-facing processes may include:

a) clear explanation of whether the event is informational, consultative, deliberative, or decision-linked;

b) moderator rules and participant conduct standards;

c) warning against public overclaim of participation;

d) confidentiality and attribution options for submissions;

e) no-retaliation statement;

f) accessibility arrangements;

g) public-safe question collection;

h) moderation of harassment, misinformation, or doxxing;

i) protection of community and Indigenous input from unauthorized reuse; and

j) post-event correction and feedback route.

Public consultations shall not invite input on terms that imply influence where no influence is possible. If a matter is already decided, the event shall not be described as consultation. If input is advisory only, the notice shall say so.

#### 248.9 Protected Escalation for Safeguards Concerns

Council participants shall have protected escalation routes for safeguards concerns. A participant shall not be required to raise concerns only through the person implicated in the concern or through a public meeting where doing so would be unsafe.

Protected escalation routes may include:

a) Council Chair or Vice-Chair, where not conflicted;

b) Secretariat or Secretary;

c) safeguards lead or safeguards function;

d) integrity or ethics function;

e) Board committee or Board-designated protected recipient;

f) legal or security function where relevant;

g) controlled-room escalation route; and

h) whistleblowing route where the concern involves misconduct, retaliation, fraud, public overclaim, or serious governance risk.

Safeguards escalations shall be recorded, classified, and routed according to risk. Where urgent harm may occur, interim protective measures may be imposed before final determination.

#### 248.10 Remedies for Safeguards Breach, Misrepresentation, or Participation Harm

Where Council safeguards are breached, GCRI US shall take corrective action proportionate to the harm, risk, intent, recurrence, and public reliance. Corrective action shall focus on protection, correction, accountability, and prevention.

Remedies may include:

a) correction of minutes, outputs, public summaries, rosters, or attribution;

b) withdrawal or revision of public materials;

c) anonymization or removal of sensitive information;

d) apology or remedy to affected participant where appropriate;

e) removal of unauthorized quote, story, name, image, affiliation, or representation claim;

f) access restriction or participant suspension;

g) removal of a chair, rapporteur, Bureau member, or participant;

h) redesign of consultation or meeting process;

i) safeguards training or independent facilitation;

j) referral to whistleblowing, legal, security, Board, or integrity review;

k) public-safe correction where external misunderstanding occurred; and

l) reconstitution of a Council or working party where harm reflects structural failure.

A safeguards breach shall not be minimized because no legal claim has been filed. Institutional harm can occur before legal harm is recognized.

#### 248.11 Interpretive Rule for Safeguards, Protected Participation, Accessibility, and Non-Retaliation in Councils

This Section shall be interpreted to preserve a controlling proposition: Council participation in GCRI US shall be safe, accessible, non-retaliatory, dignified, role-bounded, consent-aware, and protected against misuse, so that plural participation strengthens public-good governance without extracting legitimacy, exposing participants, suppressing dissent, or causing avoidable harm.

Where ambiguity exists, the interpretation that better preserves safeguards, protected participation, accessibility, non-retaliation, dignity, accurate attribution, community and Indigenous knowledge boundaries, safe public consultation, protected escalation, and meaningful remedy shall prevail unless a contrary result is required by law.

### 249. Controlled-Room Deliberation, Confidential Sessions, and Sensitive Council Materials (GCRI United States)

#### 249.1 Controlled-Room Deliberation as a Protective Council Mechanism

Controlled-room deliberation may be used within the Helix Council System of GCRI US where a Council matter requires restricted, need-to-know handling because ordinary Council circulation would create unacceptable legal, safeguards, security, privacy, public-authority, community, Indigenous, commercial, research-integrity, public-claims, or institutional risk. Controlled-room treatment shall be a protective mechanism, not a secrecy preference, executive convenience, donor accommodation, or device for avoiding dissent.

A controlled-room process may be justified where the matter involves:

a) personal information, protected participation records, whistleblower concerns, retaliation concerns, employment-sensitive matters, or participant-safety risks;

b) Indigenous knowledge, community-sensitive information, lived-experience testimony, land-sensitive materials, cultural information, or affected-population data requiring restricted handling;

c) public-authority-sensitive information, regulatory sensitivity, public procurement concerns, government capacity limits, official/non-official participation ambiguity, or public-law constraints;

d) cybersecurity vulnerabilities, technical exploit information, critical-infrastructure dependencies, system access information, controlled repositories, credentials, or incident-response materials;

e) commercially sensitive operator information, vendor information, confidential implementation constraints, or competition-sensitive material;

f) unpublished research, pre-publication evidence, contested methodology, data lineage, model-risk analysis, AI audit information, or confidential expert review;

g) legal advice, litigation risk, privilege-sensitive communications, investigation records, or dispute materials;

h) donor, sponsor, funding, or restricted-resource matters requiring confidentiality and conflict review; or

i) draft Council outputs where premature disclosure could create public overclaim, market misuse, false reliance, participant exposure, or institutional harm.

Controlled-room deliberation shall be narrowly scoped. The fact that a topic is important, difficult, controversial, reputationally sensitive, or likely to generate disagreement shall not by itself justify controlled-room treatment. Sensitive handling must be based on identifiable risk.

#### 249.2 Authority to Designate Controlled-Room Status

Controlled-room status may be designated only by a person or function authorized under the Council Charter, Council Operating System, Board-approved policy, or emergency governance procedure. A Council chair, Bureau member, Secretariat officer, safeguards function, legal function, security function, privacy function, Board committee, or other competent authority may request controlled-room designation, but the designation shall be recorded and justified.

A controlled-room designation record shall identify:

a) the matter or case ID;

b) the reason for controlled-room treatment;

c) the type of sensitivity involved;

d) the Council, committee, working party, expert mechanism, or cross-Council process affected;

e) the persons or roles authorized to access the material;

f) the materials covered;

g) the handling rules;

h) the duration of controlled-room status;

i) the review date;

j) the conditions for downgrade, public-safe summary, or closure; and

k) the authority approving the designation.

No person may unilaterally designate a matter as controlled merely to avoid scrutiny, prevent a Council from seeing dissent, exclude a participant, shield management, protect a donor, limit Board visibility, or prevent public correction. Controlled-room designation is reviewable and may be challenged through the Council Operating System, Secretary, safeguards function, integrity function, legal function, or Board route.

#### 249.3 Access Control, Need-to-Know, and Participant Eligibility

Access to controlled-room materials shall be role-based, need-to-know, matter-specific, time-bounded, and revocable. Council membership alone shall not create entitlement to controlled-room access. Council office, technical expertise, donor status, public authority status, Board liaison status, institutional seniority, or prior participation shall not create access where the person lacks need-to-know or presents conflict, safety, or handling risk.

Before granting access, GCRI US shall confirm:

a) participant identity and role;

b) authority or eligibility to access the specific matter;

c) need-to-know basis;

d) conflict and recusal status;

e) confidentiality undertaking;

f) handling-rule acknowledgment;

g) public-description and attribution restrictions;

h) security and privacy requirements;

i) any required safeguards, cultural, community, Indigenous, or legal conditions; and

j) access expiry and revocation trigger.

A person may be admitted to one controlled-room segment and excluded from another. A participant may receive a public-safe summary rather than raw materials. A conflicted person may be allowed to provide factual information but excluded from deliberation. Controlled access shall be granular, not all-or-nothing by status.

#### 249.4 Controlled-Room Materials Inventory and Handling Rules

Every controlled-room matter shall have a controlled materials inventory. The inventory shall identify the documents, datasets, recordings, notes, technical artifacts, draft outputs, correspondence, evidence packs, images, transcripts, maps, model outputs, AI logs, or other materials covered by the controlled-room designation.

The inventory shall state:

a) title or description of each item;

b) version or date;

c) owner or custodian;

d) classification level;

e) permitted access group;

f) permitted uses;

g) copying, download, print, screenshot, recording, forwarding, and AI-processing restrictions;

h) storage location;

i) retention rule;

j) public-safe summary status; and

k) destruction or archive requirement.

Unless expressly authorized, controlled-room materials shall not be downloaded to personal devices, forwarded by email, copied into unmanaged systems, pasted into unauthorized AI tools, recorded, transcribed, photographed, screenshotted, printed, or shared with external advisers. Where external legal, technical, safeguards, or expert review is necessary, the reviewer must be admitted under controlled-room rules and recorded.

#### 249.5 Confidential Sessions and Segmented Council Deliberation

A Council may hold a confidential session or segmented deliberation where only eligible participants may attend. Segmentation shall be used to preserve access controls while allowing the broader Council process to continue where appropriate.

Segmented deliberation may include:

a) general session for non-sensitive framing;

b) restricted session for controlled facts;

c) expert-only session for technical vulnerability review;

d) safeguards session for protected participant or community-sensitive matters;

e) legal-sensitive session for privileged or dispute-related matters;

f) public-authority-sensitive session for capacity and public-law concerns;

g) industry-restricted session for non-competition-sensitive operational facts; and

h) public-safe reconvening for broader Council discussion.

The minutes shall reflect that a segmented session occurred, who was eligible, the basis for restriction, the output or escalation arising from the session, and whether a public-safe or broader-Council summary is required. The minutes shall not expose restricted content unnecessarily.

Segmentation shall not be used to exclude affected voices from matters that concern them unless their exclusion is necessary for safety, legal, security, conflict, or confidentiality reasons. Where affected voices cannot be present, compensating consultation or safeguards review should be considered.

#### 249.6 Controlled-Room Dissent, Objections, and Minority Notes

Controlled-room processes shall preserve dissent, objections, and minority views. Restricted handling shall not become a method of suppressing disagreement. Participants admitted to controlled-room deliberation shall have a safe route to record dissent within the controlled record, and where appropriate, to submit a public-safe dissent summary.

Controlled-room dissent may be necessary where:

a) a participant believes the controlled-room designation is too broad or too narrow;

b) a participant believes sensitive information is being withheld from necessary decision-makers;

c) a participant believes publication is unsafe;

d) a participant believes public-safe summary language overclaims or conceals risk;

e) a participant identifies legal, security, safeguards, public-authority, community, Indigenous, research, or competition concerns;

f) a participant believes a conflicted person is improperly included; or

g) a participant believes a Council output cannot proceed without further review.

The dissent record shall be classified appropriately. Where the dissent itself includes sensitive material, the Secretariat shall preserve it in restricted form and prepare a safe escalation note if needed.

#### 249.7 Public-Safe Summaries of Controlled-Room Proceedings

Where a controlled-room matter affects broader Council work, Board action, public communication, consultation integrity, participant status, or adoption-ready materials, GCRI US should prepare a public-safe or broader-internal summary where feasible. The summary shall disclose enough to support governance legitimacy without exposing sensitive details.

A public-safe summary may state:

a) that a restricted review occurred;

b) the general category of risk reviewed;

c) the Council or function involved;

d) whether the matter was cleared, conditioned, escalated, deferred, corrected, withdrawn, or held;

e) whether unresolved concerns remain;

f) whether publication, adoption, or public reliance is restricted; and

g) whether further review is required.

A public-safe summary shall not identify protected persons, reveal Indigenous or community knowledge without consent, expose vulnerabilities, disclose privileged information, identify confidential public-authority positions, reveal trade secrets, or disclose commercially sensitive information. It shall also not sanitize the matter so much that decision-makers are misled about risk.

#### 249.8 Controlled-Room Records, Audit Logs, and Access Review

Controlled-room records shall be maintained with enhanced auditability. The Corporation shall be able to prove who accessed controlled materials, when they accessed them, under what authority, and what restrictions applied.

Controlled-room recordkeeping shall include:

a) controlled-room designation record;

b) access list;

c) access approvals;

d) confidentiality undertakings;

e) materials inventory;

f) meeting notices;

g) attendance logs;

h) restricted minutes;

i) dissent and objection records;

j) output drafts and public-safe summaries;

k) access revocation record;

l) breach or incident logs; and

m) closure or downgrade record.

Access shall be reviewed periodically and at closure. Participants who no longer require access shall be removed. If a participant changes role, becomes conflicted, leaves the Council, breaches rules, or no longer needs access, access shall be revoked promptly.

#### 249.9 Controlled-Room Breach, Unauthorized Disclosure, and Remedial Action

Unauthorized access, disclosure, copying, publication, AI processing, forwarding, public quotation, or external use of controlled-room materials shall be treated as a serious Council-integrity incident. The response shall be proportionate to harm and risk, but shall not be casual.

Upon suspected breach, GCRI US may:

a) suspend access;

b) preserve logs and records;

c) identify materials affected;

d) identify persons with access;

e) require return or deletion of materials where lawful;

f) notify affected persons or authorities where required;

g) pause publication or adoption processes;

h) conduct security, legal, safeguards, privacy, or integrity review;

i) correct public materials if overclaim or disclosure occurred;

j) restrict, suspend, or remove responsible participants;

k) refer the matter to Board, legal, law enforcement, regulator, or other authority where required; and

l) revise controls to prevent recurrence.

Where breach involves community or Indigenous knowledge, protected participation, whistleblower material, personal data, security vulnerabilities, or legal privilege, response shall be immediate and controlled. The Corporation shall prioritize harm containment over reputational management.

#### 249.10 AI, Digital Tools, and Controlled-Room Prohibitions

Controlled-room materials shall not be processed through unauthorized AI tools, transcription systems, translation systems, meeting bots, note-taking tools, cloud services, or external analytics platforms. The Corporation shall treat AI processing as disclosure unless the tool, environment, access control, retention rule, and data-use terms have been approved for the material’s classification.

Unless expressly permitted, controlled-room participants shall not:

a) use AI assistants to summarize controlled materials;

b) upload controlled documents into external systems;

c) enable automatic transcription;

d) use meeting bots;

e) copy controlled text into personal productivity tools;

f) translate controlled materials through unmanaged services;

g) use personal devices for controlled notes;

h) export controlled records to external storage; or

i) use controlled material for model training, benchmarking, prompt testing, or tool evaluation.

Where AI or digital tools are approved, the approval shall identify environment, data retention, access logs, data-use restrictions, security controls, and review authority. Human review remains required for any summary used as Council record.

#### 249.11 Downgrade, Declassification, Closure, and Continuing Restrictions

Controlled-room status shall be reviewed and may be downgraded, declassified, partially released, summarized, archived, or closed when sensitivity decreases or when continued restriction is no longer justified. Over-classification can weaken transparency and participation, while under-classification can create harm. The Corporation shall manage both risks.

Downgrade or declassification review shall consider:

a) whether the original sensitivity remains;

b) whether participants consent to attribution or release;

c) whether public-authority, community, Indigenous, legal, security, privacy, commercial, or research restrictions remain;

d) whether public-safe summary is sufficient;

e) whether broader Council access is now appropriate;

f) whether Board or public communication requires limited disclosure;

g) whether any material must remain permanently restricted; and

h) whether supersession or correction is required.

Closure shall include access revocation, archive designation, final inventory, unresolved restrictions, and any continuing confidentiality obligations. A participant’s duty to protect controlled-room material may survive the end of Council service.

#### 249.12 Interpretive Rule for Controlled-Room Deliberation, Confidential Sessions, and Sensitive Council Materials

This Section shall be interpreted to preserve a controlling proposition: controlled-room deliberation within GCRI US exists to protect sensitive Council matters through narrow, justified, recorded, need-to-know handling while preserving dissent, auditability, public-safe accountability, and lawful escalation.

Where ambiguity exists, the interpretation that better preserves controlled-room necessity, access minimization, materials inventory, segmented deliberation, safe dissent, public-safe summaries, audit logs, breach response, AI and digital-tool restrictions, downgrade discipline, and continuing confidentiality shall prevail unless a contrary result is required by law.

### 250. Forms-First Council Operating System, Case IDs, Decision Clocks, and Closure Controls (GCRI United States)

#### 250.1 No Email Governance Rule in Council Operations

GCRI US shall apply a no-email-governance rule to all material Helix Council operations. Email may be used for notice, circulation, scheduling, acknowledgement, and administrative communication, but it shall not serve as the authoritative system of record for Council action, Council approval, Council dissent, Council recommendation, Council publication, Council escalation, Council consultation, or Council closure.

Council governance shall not be conducted through unmanaged email threads because unmanaged email:

a) obscures authority and role;\
b) loses dissent and minority views;\
c) permits informal approval without quorum or threshold;\
d) prevents reliable conflict and recusal tracking;\
e) creates uncontrolled forwarding and access risk;\
f) weakens public-claims discipline;\
g) makes version control unreliable;\
h) prevents audit-grade case linkage; and\
i) allows informal practice to become apparent authority.

Accordingly, every material Council act shall be entered, classified, tracked, and closed through the approved Council Operating System or equivalent records-first process. Email may point to the system. It shall not replace it.

#### 250.2 Mandatory Case ID for Every Material Council Act

Every material Council act shall receive a case ID before deliberation, circulation, review, approval, escalation, publication, or adoption-ready routing. The case ID shall be the operating thread that connects the matter from intake to closure.

A case ID shall be required for:

a) Council meeting items;\
b) Council recommendations, warnings, advisory notes, and review memoranda;\
c) consultation openings and closures;\
d) dissent notes and minority reports;\
e) working-party mandates;\
f) expert-review requests;\
g) cross-Council joint sessions;\
h) controlled-room deliberations;\
i) public-safe summaries;\
j) adoption-ready decision packs;\
k) corrections, withdrawals, supersessions, and reclassifications; and\
l) escalations to the Board, Secretariat, legal, safeguards, security, integrity, finance, communications, or management lanes.

No Council output shall be considered final for institutional reliance unless its case ID, version, status, effect code, classification, and closure state are recorded.

#### 250.3 Intake Forms, Metadata, and Classification Assignment

The Council Operating System shall require structured intake forms and metadata for all material Council matters. Metadata is not clerical decoration. It is the institutional control layer that tells the Corporation what the matter is, who owns it, what risks attach to it, what authority is requested, and what record must be preserved.

Each intake record shall include:

a) case title;\
b) submitting person or body;\
c) authority basis;\
d) relevant Council or Councils;\
e) requested output type;\
f) intended use;\
g) timeline;\
h) public, internal, restricted, confidential, or controlled-room classification;\
i) public-claims risk;\
j) safeguards, CIC, Indigenous, community, or protected-participation sensitivity;\
k) public-authority, PAC, legal, or regulatory sensitivity;\
l) operator, IOC, commercial, procurement, or competition sensitivity;\
m) ARC, research, data, AI, model, ontology, or publication-integrity sensitivity;\
n) CMC, media, public-trust, transparency, or communications sensitivity;\
o) conflicts and recusals known at intake; and\
p) required review gates.

The classification assigned at intake may be changed as new information emerges, but every change shall be recorded.

#### 250.4 Completeness Gates and Admissibility Controls

A matter shall pass completeness gates before formal Council deliberation. Completeness gates ensure that Councils do not deliberate on vague, unsafe, incomplete, or misclassified matters.

A matter shall not be admitted for formal action unless the record shows:

a) the question is clear;\
b) the Council has jurisdiction;\
c) materials are available and classified;\
d) participants can understand the requested output;\
e) conflicts are identified or capable of review;\
f) public-claims implications are understood;\
g) safeguards and controlled-room issues are assessed;\
h) required pre-review has occurred or been waived by competent authority; and\
i) the matter has a defined route after Council review.

Where a matter fails completeness review, it may be returned, narrowed, deferred, rerouted, converted into preliminary discussion only, or escalated to a control function. Senior sponsorship, donor interest, strategic importance, or public urgency shall not cure an incomplete matter.

#### 250.5 Decision Clocks, Timeboxing, and Time-in-State Controls

The Council Operating System shall maintain decision clocks and time-in-state controls. Council matters shall not remain indefinitely “under review,” “pending consultation,” “awaiting drafting,” “with Bureau,” “in controlled room,” or “adoption-ready” without escalation.

Time controls shall include:

a) intake review clock;\
b) agenda admission clock;\
c) consultation open and close dates;\
d) working-party mandate duration;\
e) expert-review deadline;\
f) dissent submission window;\
g) controlled-room review date;\
h) output finalization deadline;\
i) escalation deadline;\
j) decision-pack completion deadline; and\
k) closure or supersession deadline.

Where a matter exceeds time-in-state thresholds, the system shall trigger review. The matter may be escalated, narrowed, assigned new owner, closed without action, or converted into a longer-term workstream by competent authority. Stale Council matters create false expectations and public-claims risk.

#### 250.6 Docket States, Routing, and Escalation Triggers

Each Council matter shall carry a docket state. The docket state shall determine what may happen next and what claims may be made externally.

Permitted docket states may include:

a) draft intake;\
b) submitted;\
c) intake incomplete;\
d) admitted;\
e) routed to Council;\
f) routed to cross-Council review;\
g) routed to working party;\
h) routed to expert mechanism;\
i) under consultation;\
j) under controlled-room handling;\
k) output drafted;\
l) dissent window open;\
m) Council output finalized;\
n) escalated;\
o) adoption-ready;\
p) adopted by competent authority;\
q) returned for revision;\
r) closed without adoption;\
s) superseded; and\
t) withdrawn.

Escalation triggers shall include material dissent, unresolved conflict, safeguards concern, public overclaim, public-authority sensitivity, competition issue, security or privacy risk, research-integrity concern, non-execution boundary issue, missed decision clock, or authority uncertainty.

#### 250.7 Knowledge Graph Indexing and Cross-Case Linkage

GCRI US may maintain knowledge graph indexing or equivalent cross-case linkage for Council matters. The purpose is to make institutional learning cumulative rather than fragmented. Council matters often connect across time, Councils, geographies, risk domains, public-good outputs, and governance issues. Cross-case linkage allows the Corporation to identify repeated concerns, unresolved risks, recurring public-claims issues, and structural improvement opportunities.

Cross-case linkage may connect:

a) related Council outputs;\
b) repeated dissent themes;\
c) consultation comments across matters;\
d) public-claims corrections;\
e) safeguards concerns;\
f) Indigenous or community knowledge-boundary issues;\
g) AI, data, ontology, or evidence-quality issues;\
h) operator feasibility concerns;\
i) public-authority sensitivity patterns;\
j) Council performance indicators; and\
k) Board or committee actions arising from Council work.

Knowledge graph indexing shall respect classification. Sensitive materials may be indexed by metadata or restricted tags without exposing protected content.

#### 250.8 Closure Memos and Finalization Requirements

Every material Council matter shall close with a closure memo or equivalent finalization record. A matter shall not be considered closed merely because a meeting ended, a document was circulated, or no one followed up.

A closure memo shall state:

a) case ID;\
b) matter title;\
c) final docket state;\
d) Council or Councils involved;\
e) output produced, if any;\
f) effect code;\
g) dissent or unresolved concerns;\
h) consultation status;\
i) controlled-room or classification status;\
j) public-safe summary status;\
k) adoption, rejection, withdrawal, supersession, or no-action result;\
l) records location;\
m) continuing obligations; and\
n) next review date, if any.

Closure discipline protects GCRI US from dormant claims, unfinished consultations, stale Council outputs, and informal reliance on incomplete work.

#### 250.9 Operating System Controls for Nexus-Aligned Public-Good Work

Where a Council matter concerns Nexus-aligned public-good work, the Council Operating System shall apply enhanced metadata and closure controls. Such matters may touch evidence rails, risk intelligence, AI-enabled analysis, standards, readiness frameworks, open-source infrastructure, resilience finance interfaces, or cross-entity cooperation. They require particular clarity because they may be misread externally as certification, routeability, market readiness, government adoption, or execution authority.

The case record shall state:

a) whether the matter is research, public-good infrastructure, standards input, policy input, consultation, training, or governance;\
b) whether any downstream execution is outside GCRI US;\
c) whether GCRI Canada, GRF, GRA, protocol bodies, host institutions, or delivery actors are referenced;\
d) whether public-good and execution-stack boundaries are clear;\
e) whether public claims require limitation language; and\
f) whether Board, legal, safeguards, security, or cross-Council review is required before release.

Nexus-aligned Council work shall remain public-good and non-executionary unless a separate lawful authority outside GCRI US performs regulated activity.

#### 250.10 System Permissions, Audit Logs, and Administrative Integrity

The Council Operating System shall maintain permissions and audit logs. Administrative users shall have defined access rights. No person shall have uncontrolled ability to alter records, delete dissent, change docket states, modify public classifications, or publish outputs without review.

System controls shall include:

a) role-based access;\
b) change logs;\
c) version history;\
d) restricted deletion rights;\
e) publication approvals;\
f) access expiry;\
g) audit review;\
h) backup and continuity; and\
i) incident response for unauthorized changes.

Administrative convenience shall not override records integrity. Silent edits, undocumented status changes, and unlogged publication actions are prohibited for material Council records.

#### 250.11 Interpretive Rule for Forms-First Council Operating System, Case IDs, Decision Clocks, and Closure Controls

This Section shall be interpreted to preserve a controlling proposition: GCRI US Council work shall be governed by a forms-first, case-ID-based, classified, time-controlled, auditable operating system that prevents email governance, informal authority, stale matters, untracked outputs, and public reliance on incomplete Council acts.

Where ambiguity exists, the interpretation that better preserves mandatory case IDs, structured metadata, completeness gates, decision clocks, docket-state discipline, escalation triggers, cross-case learning, closure memos, Nexus-aligned non-execution controls, and system auditability shall prevail unless a contrary result is required by law.

### 251. Decision Packs and Adoption-Ready Council Outputs (GCRI United States)

#### 251.1 Decision Pack as Mandatory Instrument for Adoption-Seeking Council Outputs

Any Council output that seeks adoption, approval, publication, institutional reliance, Board consideration, committee action, executive implementation, public release, external submission, or incorporation into an authoritative GCRI US instrument shall be accompanied by a decision pack. The decision pack shall be the mandatory bridge between Council deliberation and competent institutional action.

A Council output shall not be treated as adoption-ready merely because it is well drafted, urgent, consensus-supported, publicly useful, donor-relevant, strategically important, or requested by senior leadership. Adoption-readiness requires a complete record showing what was reviewed, by whom, under what authority, with what limitations, with what dissent, and with what proposed effect.

The decision pack shall ensure that the receiving authority can determine:

a) whether the Council acted within mandate;\
b) whether the output is advisory, internal, public-safe, escalated, or adoption-seeking;\
c) whether the output requires Board, officer, committee, legal, safeguards, security, privacy, finance, research, communications, or public-claims review;\
d) whether conflicts, recusals, competition issues, public-authority sensitivities, community or Indigenous concerns, and dissent were properly handled;\
e) whether the output can be adopted as drafted, adopted with conditions, returned for revision, rejected, held, or reclassified; and\
f) whether public release would create any false implication of endorsement, certification, public mandate, routeability, market readiness, government support, community consent, Indigenous consent, or execution authority.

The decision pack is therefore a control instrument. It prevents Council work from drifting into institutional effect without the discipline required by nonprofit governance, records validity, public-good stewardship, and the non-execution boundary.

#### 251.2 Minimum Contents of Council Decision Packs

Each Council decision pack shall contain the minimum information necessary for competent review. The pack shall be compact enough to be usable and complete enough to be audit-grade.

A complete Council decision pack shall include:

a) Cover Memorandum, identifying the case ID, title, submitting Council, date, requested action, proposed decision, and responsible drafter;\
b) Authority Map, identifying the Council mandate, Charter basis, submitting authority, receiving authority, and any Board or officer reserved matter;\
c) Output Text, including the proposed advisory note, recommendation, warning, consultation summary, public-safe summary, policy text, Charter text, standards input, or other Council output;\
d) Output Type and Effect Code, stating what the output does and does not do;\
e) Materials Reviewed, listing drafts, evidence, consultation submissions, technical materials, legal notes, safeguards notes, public-claims notes, expert outputs, or cross-Council inputs reviewed;\
f) Deliberation Summary, identifying meetings, participants, quorum, voting, consensus, dissent, and unresolved issues;\
g) Conflict and Recusal Record, identifying disclosed interests, restrictions, abstentions, exclusions, and any effect on quorum or drafting;\
h) Consultation and Comment Record, where applicable, including comment disposition and unresolved comments;\
i) Safeguards and Rights Review, identifying community, Indigenous, protected participation, accessibility, dignity, non-retaliation, and grievance implications;\
j) Legal, Security, Privacy, Finance, Research, and Public-Claims Review Status, stating what review occurred, what remains pending, and what conditions apply;\
k) Publication and Attribution Plan, identifying whether the output is public, internal, restricted, controlled, redacted, or public-safe;\
l) Dissent and Minority Notes, including material objections and treatment of unresolved issues;\
m) Version and Supersession Record, identifying current version, prior versions, draft status, and any superseded materials;\
n) Recommended Decision Language, suitable for Board, committee, officer, or other competent authority action; and\
o) Closure and Post-Decision Actions, identifying notice, Gazette entry, publication, repository, access revocation, correction, or follow-up obligations.

A decision pack lacking material elements shall be returned, completed, narrowed, or reclassified before the receiving authority is asked to act.

#### 251.3 Evidence Lineage, Uncertainty, and Limitations Discipline

Every adoption-seeking Council output shall include evidence lineage, uncertainty, and limitations discipline. The receiving authority must know what the output rests upon and where it remains uncertain.

Evidence lineage shall identify:

a) the sources, documents, data, consultations, expert reviews, Council deliberations, and institutional records used;\
b) whether sources are public, internal, restricted, controlled, preliminary, verified, contested, or superseded;\
c) whether AI, models, data pipelines, ontologies, remote sensing, geospatial analysis, simulations, surveys, interviews, expert judgment, or community input were used;\
d) whether the evidence is general, local, U.S.-specific, global, sector-specific, community-specific, Indigenous, public-authority-sensitive, or experimental; and\
e) whether the evidence can be reproduced, independently reviewed, or corrected.

Limitations shall be stated in the decision pack and, where relevant, in the output itself. Limitations may include:

i) limited consultation;\
ii) incomplete data;\
iii) unresolved dissent;\
iv) methodological uncertainty;\
v) implementation dependency;\
vi) public-authority sensitivity;\
vii) community or Indigenous knowledge boundary;\
viii) security or privacy restriction;\
ix) non-execution limitation; and\
x) need for future review.

GCRI US shall not adopt or publish outputs that conceal uncertainty for rhetorical strength. A public-good institution earns trust by stating what is known, what is not known, what is provisional, and what remains subject to correction.

#### 251.4 Rights, Safeguards, Externalities, and Market-Sensitivity Review

A Council decision pack shall include rights, safeguards, externalities, and market-sensitivity review where the output may affect persons, communities, public authorities, operators, markets, institutional reputation, data subjects, Indigenous knowledge holders, or downstream users.

The review shall consider:

a) whether the output could expose, misrepresent, or instrumentalize communities, Indigenous participants, public authorities, civil-society actors, media participants, researchers, operators, or whistleblowers;\
b) whether participation has been properly consented, attributed, anonymized, compensated, or protected;\
c) whether the output could create public reliance beyond its authority;\
d) whether the output could be used by vendors, members, sponsors, donors, public authorities, or external actors for marketing, procurement, investor, regulatory, fundraising, or political claims;\
e) whether the output creates competition, antitrust, or market-signaling concerns;\
f) whether the output risks implying regulated execution, investment advice, insurance readiness, securities readiness, lending readiness, transaction routing, settlement capacity, or public guarantee;\
g) whether public summaries preserve limitations and dissent; and\
h) whether corrective, grievance, or withdrawal pathways are available.

If material safeguards, rights, or market-sensitivity issues remain unresolved, the output shall not proceed to full adoption without recorded acceptance of that risk by the competent authority and any required protective conditions.

#### 251.5 Authority Mapping and Effect Statement

Each decision pack shall include an authority map and effect statement. The authority map shall show which body has power to do what. The effect statement shall state what legal, institutional, public, procedural, or advisory effect would follow if the output is adopted.

The authority map shall identify:

a) the Council’s authority to produce the output;\
b) the receiving authority’s power to adopt, note, reject, return, publish, or escalate;\
c) whether Board reserved matters are implicated;\
d) whether officer authority is sufficient;\
e) whether member approval, if any, is required;\
f) whether legal review is required before adoption;\
g) whether another entity’s approval is required because the output references GCRI Canada, GRF, GRA, protocol bodies, host institutions, or other Nexus-aligned entities; and\
h) whether the output has any external-facing effect.

The effect statement shall state, in precise language, whether adoption would:

i) create an internal policy;\
ii) approve public release;\
iii) authorize consultation;\
iv) approve a Council Charter, committee, working party, or process;\
v) adopt a public-good framework;\
vi) approve a submission or public statement;\
vii) record a warning or risk position;\
viii) authorize further development only; or\
ix) take no external effect beyond institutional learning.

No effect statement shall imply certification, recognition, routeability, procurement eligibility, market validation, public authority approval, community consent, Indigenous consent, or execution authority unless a separate lawful instrument clearly grants that effect.

#### 251.6 Version Control, Traceability, and Revision Discipline

Adoption-ready outputs shall be subject to strict version control, traceability, and revision discipline. The competent authority shall know exactly which version it is reviewing and adopting.

The decision pack shall include:

a) version number;\
b) date;\
c) drafting history;\
d) Council approval status;\
e) changes from prior version;\
f) unresolved comments;\
g) dissent status;\
h) required review status;\
i) superseded drafts; and\
j) proposed final repository location.

No person shall substitute a revised version after approval without recorded authority. No “clean copy” shall omit limitations, dissent, effect code, classification, or public-claims language approved in the decision pack. Redline discipline shall be used for material changes.

Where the receiving authority adopts an output subject to conditions, the revised final version shall be checked against those conditions before publication or implementation. Conditional adoption is not final release.

#### 251.7 No Adoption-Ready Text Without Complete Pack and Required Review Gates

No Council output shall be placed before the Board, committee, officer, executive function, or public release channel as adoption-ready unless the required decision pack is complete and review gates have been satisfied, waived, or expressly identified as pending.

Required review gates may include:

a) Council approval of the advisory output;\
b) Secretariat completeness check;\
c) legal review;\
d) safeguards review;\
e) security or privacy review;\
f) finance or restricted-fund review;\
g) research or method review;\
h) public-claims and communications review;\
i) conflict and recusal review;\
j) cross-Council review;\
k) controlled-room review; and\
l) Board committee review.

A waiver of a review gate shall be recorded with reasons and authority. Waiver shall not be used to bypass safeguards, legal obligations, protected participation, or Board reserved matters. Where a review gate is pending, the output may be considered only for direction, not final adoption, unless the competent authority expressly accepts the pending condition.

#### 251.8 Decision Pack Use for Board, Committee, Officer, and Secretariat Action

Decision packs shall be adapted to the receiving authority. A Board decision pack may require broader fiduciary framing, risk analysis, budget implications, public-claims control, and inter-entity consequences. A committee pack may require specialized review. An officer pack may require authority and execution instructions. A Secretariat pack may require records and publication handling.

A decision pack submitted to the Board shall identify:

a) fiduciary implications;\
b) mission-lock implications;\
c) nonprofit status and private-benefit considerations;\
d) non-execution boundary implications;\
e) financial, legal, safeguards, and reputational risks;\
f) public-good asset implications;\
g) cross-entity implications; and\
h) proposed resolution language.

A decision pack submitted to an officer or Secretariat function shall identify the specific authority requested and shall not ask the officer or Secretariat to decide matters outside their role. The pack shall preserve the chain of authority.

#### 251.9 Adoption Outcomes, Conditional Approval, Return, Rejection, and Closure

The competent authority may adopt, conditionally approve, note, return, reject, defer, reclassify, escalate, withdraw, or close a Council decision pack. Each outcome shall be recorded clearly.

Possible outcomes include:

a) Adopted as Presented, where the authority approves the output and effect;\
b) Adopted With Conditions, where specified changes, reviews, or limits must be satisfied before release;\
c) Noted Without Adoption, where the output informs the record but creates no adopted position;\
d) Returned for Revision, where defects must be corrected;\
e) Deferred, where more information or review is needed;\
f) Rejected, where the authority declines the output;\
g) Escalated, where another authority must review;\
h) Reclassified, where the output’s effect or handling changes;\
i) Withdrawn, where the output is removed from reliance; and\
j) Closed Without Action, where no further action is taken.

The record shall state whether public notice, Gazette entry, participant notification, repository update, access revocation, or public correction is required.

#### 251.10 Post-Adoption Implementation, Publication, and Monitoring

Where a Council-derived output is adopted, GCRI US shall monitor implementation, publication, and public use. Adoption does not end governance responsibility.

Post-adoption controls shall ensure:

a) the correct version is published or implemented;\
b) limitations and disclaimers remain attached;\
c) public summaries match the adopted text;\
d) participant attribution follows consent;\
e) public authority, community, Indigenous, academic, media, civil-society, and industry overclaim is avoided;\
f) external misuse is monitored;\
g) corrections are made when needed; and\
h) supersession or review date is tracked.

Where an adopted output is later found defective, unsafe, overclaimed, inaccurate, or superseded, the Corporation shall correct, withdraw, or supersede it through records-first procedure.

#### 251.11 Interpretive Rule for Decision Packs and Adoption-Ready Council Outputs

This Section shall be interpreted to preserve a controlling proposition: Council outputs of GCRI US may seek institutional adoption only through complete decision packs that preserve authority, evidence lineage, limitations, safeguards, dissent, conflicts, review gates, effect statements, version control, and post-adoption controls.

Where ambiguity exists, the interpretation that better preserves decision-pack completeness, competent authority review, evidence and uncertainty discipline, safeguards and market-sensitivity controls, precise effect statements, version integrity, mandatory review gates, conditional adoption discipline, and post-adoption monitoring shall prevail unless a contrary result is required by law.

### 252. Consultation, Comment Handling, and Participation Safety in Council Work (GCRI United States)

#### 252.1 Consultation as a Disciplined Governance Instrument

Consultation in the Helix Council System of GCRI US shall be a disciplined governance instrument, not a public-relations exercise, informal survey, symbolic listening exercise, or post-decision validation device. Consultation shall be used where Council work, public-good outputs, standards proposals, risk frameworks, policy positions, technical architectures, participation rules, safeguards procedures, or Nexus-aligned materials would benefit from structured input before being finalized, published, escalated, or adopted.

Consultation shall be required, recommended, or considered where a matter materially affects:

a) public-sector interpretation, public-law feasibility, or public authority engagement;\
b) operational feasibility, implementation burden, security, interoperability, or vendor neutrality;\
c) scientific method, evidence quality, data, AI, ontology, reproducibility, or publication integrity;\
d) civil-society legitimacy, media interpretation, public trust, transparency, or public-claims discipline;\
e) community, Indigenous, lived-context, rights-sensitive, land-sensitive, or affected-population concerns;\
f) membership, Council participation, governance access, or institutional representation;\
g) public-good assets, open-source materials, standards, templates, or reference architectures; or\
h) any matter that may be relied upon externally as a GCRI US public-good position.

Consultation shall be honest about effect. If input is advisory, the consultation shall say so. If the Board or another competent authority retains final decision-making power, the consultation shall say so. If only specific parts are open for comment, the consultation shall say so. Consultation shall never imply that participants control the outcome unless the governing process expressly creates that right.

#### 252.2 Consultation Triggers, Waivers, and Emergency Exceptions

The Council Operating System shall define consultation triggers. Consultation may be mandatory, discretionary, targeted, public, restricted, cross-Council, expert-only, community-specific, Indigenous-specific, member-facing, public-authority-sensitive, or controlled-room-based depending on the matter.

Consultation should be triggered where:

a) a Council output is intended for public release and may affect external understanding;\
b) an output proposes a new Council Charter, membership structure, participation model, or governance procedure;\
c) a public-good framework may affect communities, Indigenous participants, public authorities, operators, researchers, or civil society;\
d) a standards, evidence, AI, data, or risk-intelligence proposal may be cited as authoritative;\
e) a consultation is necessary to test accessibility, legitimacy, feasibility, or safeguards;\
f) a material dissent indicates that affected or expert voices have not been adequately heard;\
g) a prior publication or Council act requires correction; or\
h) the Board, Secretariat, safeguards function, legal function, or Council determines that consultation is necessary for readiness.

Consultation may be waived only by competent authority and with recorded reasons. Waiver may be appropriate where:

i) the matter is purely internal and low risk;\
ii) consultation would expose protected persons or sensitive information;\
iii) emergency protective action is required;\
iv) consultation has already occurred through an equivalent process;\
v) the issue is procedural and does not affect rights, public meaning, or external reliance; or\
vi) consultation would create legal, security, privacy, or safeguards risk disproportionate to its value.

Emergency exceptions shall be narrow. Where urgent action occurs without consultation, the record shall state whether post-action consultation, feedback, review, or correction is required.

#### 252.3 Consultation Package Standards and Accessibility Minimums

Every material consultation shall be supported by a consultation package appropriate to the audience and subject matter. The package shall enable meaningful input, not merely invite comments on documents too vague, technical, lengthy, or final to be effectively reviewed.

A consultation package shall include, as applicable:

a) consultation title and case ID;\
b) purpose and institutional context;\
c) specific questions for comment;\
d) scope of what is open and what is not open;\
e) draft text or materials under review;\
f) plain-language summary where needed;\
g) explanation of the intended output and effect;\
h) participation instructions and deadline;\
i) confidentiality, attribution, anonymity, and public-use options;\
j) safeguards and non-retaliation statement;\
k) accessibility instructions and support options;\
l) public-claims boundary;\
m) submission format; and\
n) expected comment disposition and closure process.

Accessibility shall be treated as a minimum condition of meaningful consultation. Where the intended audience includes non-specialists, under-resourced organizations, community participants, Indigenous participants, students, local actors, or cross-sector participants, GCRI US shall use plain language, explanatory framing, reasonable time, and formats that do not privilege only professional insiders.

#### 252.4 Comment Logging, Disposition Discipline, and No-Orphan-Comment Rule

All material consultation comments shall be logged, assigned to a case ID, classified, reviewed, and disposed of through a recorded process. GCRI US shall apply a no-orphan-comment rule: no material comment shall disappear without disposition.

A comment log shall include:

a) submitter name or role marker, subject to confidentiality rules;\
b) submitter capacity, where relevant;\
c) date received;\
d) comment category;\
e) document section or issue addressed;\
f) classification and attribution status;\
g) whether the comment raises legal, safeguards, security, public-claims, research, operational, public-authority, community, Indigenous, competition, or authority issues;\
h) disposition decision;\
i) reason for disposition;\
j) resulting text change or action; and\
k) escalation route where needed.

Disposition categories may include:

i) accepted;\
ii) accepted in part;\
iii) rejected with reason;\
iv) deferred;\
v) out of scope;\
vi) escalated;\
vii) requires further review;\
viii) protected or restricted;\
ix) incorporated into dissent or unresolved-issue register; or\
x) retained for future workstream.

A comment raising serious safeguards, legal, public-authority, public-claims, Indigenous, community, security, privacy, or non-execution concern shall not be dismissed as editorial. It shall be routed to the competent function.

#### 252.5 Protected Participation, Retaliation Prevention, and Safe Handling

Consultation shall be conducted with protected participation and retaliation prevention. Persons must be able to provide criticism, dissent, correction, safeguards concerns, public-claims concerns, community concerns, Indigenous knowledge-boundary concerns, and methodological objections without fear of retaliation or misuse.

Consultation safety controls may include:

a) anonymous or role-marker submissions;\
b) confidentiality options;\
c) restricted handling of sensitive submissions;\
d) separation between comment review and persons implicated by the comment;\
e) safeguards review for sensitive submissions;\
f) no-retaliation notice;\
g) limits on public attribution;\
h) secure submission channels;\
i) protection of whistleblower-adjacent information; and\
j) prohibition on using consultation submissions for commercial, political, reputational, or punitive purposes.

Where a participant claims retaliation or unsafe handling, GCRI US shall route the matter through safeguards, integrity, legal, or Board channels as appropriate. Consultation cannot be legitimate if participants are punished for honest input.

#### 252.6 Consultation Completion as Readiness Gate for Certain Outputs

For certain outputs, consultation completion shall be a readiness gate. The output shall not proceed to publication, adoption-ready status, Board action, or external submission until consultation is complete or a waiver has been recorded.

Consultation completion requires:

a) consultation period closed or validly shortened;\
b) comments logged;\
c) material comments reviewed;\
d) disposition completed or escalated;\
e) safeguards and public-claims issues resolved or identified for decision;\
f) dissent and unresolved issues captured;\
g) text revised where required;\
h) decision pack updated;\
i) public-safe consultation summary prepared where appropriate; and\
j) closure memo completed.

A consultation is not complete merely because the deadline passed. It is complete when the institution has processed the input responsibly. Where unresolved material comments remain, the decision pack shall disclose them.

#### 252.7 Publication of Consultation Outcomes and Recorded Reasons

GCRI US may publish consultation outcomes where appropriate and safe. Publication shall improve transparency and accountability while preserving confidentiality, protected participation, Indigenous and community knowledge boundaries, public-authority sensitivities, security, privacy, legal, and competition controls.

A consultation outcome publication may include:

a) consultation question;\
b) number and categories of submissions;\
c) major themes;\
d) material changes made;\
e) comments accepted, rejected, deferred, or escalated;\
f) unresolved issues;\
g) dissent or minority concerns where safe;\
h) limitations of consultation;\
i) next steps; and\
j) public-claims limitations.

Recorded reasons matter. Where GCRI US rejects material comments, it should explain why at an appropriate level. Reasons may include inconsistency with mission, legal risk, public-claims risk, evidence insufficiency, non-execution boundary, out-of-scope content, implementation infeasibility, safeguards concern, or need for further review.

#### 252.8 Targeted, Restricted, and Community-Sensitive Consultations

Not all consultations shall be public. Some matters require targeted or restricted consultation because public consultation would be unsafe, ineffective, premature, or misleading.

Targeted consultation may be appropriate where:

a) specialized technical expertise is required;\
b) public authority capacity issues must be handled carefully;\
c) community or Indigenous knowledge requires permission and context;\
d) commercially sensitive or security-sensitive information is involved;\
e) unpublished research or draft standards require limited expert review;\
f) public release could create market or public-claims distortion; or\
g) affected participants need safe, smaller-format engagement.

Community-sensitive and Indigenous-sensitive consultations shall be designed with safeguards first. They shall address representation, consent, attribution, compensation where appropriate, language, cultural protocol, knowledge boundaries, feedback, grievance, and correction. GCRI US shall not treat targeted consultation as inferior where it is the safer and more respectful method.

#### 252.9 Consultation Interface With Councils, Board, and Corporate Authority

Consultation outputs shall be routed to the correct authority. A consultation summary is not itself corporate approval. It informs Council outputs, decision packs, Board decisions, public statements, or revisions.

The consultation interface shall preserve:

a) Council role as deliberative and advisory;\
b) Secretariat role as record and process custodian;\
c) Board role as fiduciary authority;\
d) officer role as authorized corporate function;\
e) safeguards, legal, security, privacy, research, finance, and public-claims review roles; and\
f) public-good and non-execution boundaries.

Where a consultation reveals that a matter is not ready, the Council shall not force adoption. Consultation may result in revision, withdrawal, deferral, reclassification, additional review, or abandonment. That is a sign of functioning governance, not failure.

#### 252.10 Consultation Misuse, Manipulation, and Integrity Breach

Consultation misuse shall be treated as an integrity breach. Misuse occurs where consultation is used to manufacture legitimacy, misstate consent, bury objections, recruit endorsements, pressure participants, extract community knowledge, influence procurement, or create public narrative unsupported by the record.

Misuse may include:

a) describing consultation as approval;\
b) describing silence as consent;\
c) omitting critical comments from summaries;\
d) cherry-picking supportive comments;\
e) using participant names without permission;\
f) creating fake consensus;\
g) inviting comments after the decision is already closed while implying openness;\
h) using consultation to identify and retaliate against critics;\
i) using community or Indigenous input for fundraising or branding without consent;\
j) using consultation with industry participants to signal procurement or market preference; or\
k) using consultation outcomes in public materials without limitations.

Remedies may include correction, withdrawal, re-consultation, public-safe clarification, participant notification, disciplinary action, safeguards review, Board escalation, or redesign of the consultation process.

#### 252.11 Consultation in Nexus-Aligned Public-Good Work

Where consultation concerns Nexus-aligned public-good work, the consultation shall explicitly preserve GCRI US’s public-good, non-execution, and legal-separateness boundaries. Such consultation may address evidence systems, risk intelligence, AI governance, standards, readiness frameworks, public-good technical infrastructure, or finance-adjacent resilience concepts. These topics can be misunderstood as market, investment, insurance, government, or execution instruments.

Consultation materials shall state:

a) GCRI US is seeking public-good, evidence, governance, standards, policy, or learning input;\
b) consultation does not create certification, recognition, routeability, investment readiness, insurance readiness, procurement readiness, or execution authority;\
c) any regulated execution, if applicable downstream, belongs to separate lawful actors;\
d) participation does not imply endorsement by GCRI US or by other participants;\
e) cross-entity references do not imply merger, agency, or control; and\
f) public-good outputs remain subject to adoption, review, correction, and non-execution limits.

This framing protects both the Corporation and consultation participants from improper reliance.

#### 252.12 Interpretive Rule for Consultation, Comment Handling, and Participation Safety in Council Work

This Section shall be interpreted to preserve a controlling proposition: consultation in GCRI US Council work shall be meaningful, safe, accessible, recorded, dispositioned, and truthful about effect, so that participation strengthens institutional learning without becoming performative, extractive, retaliatory, or misleading.

Where ambiguity exists, the interpretation that better preserves consultation integrity, no-orphan-comment discipline, protected participation, safe handling, completion as readiness gate, transparent outcomes, targeted consultation where appropriate, correct routing to corporate authority, misuse remedies, and Nexus-aligned non-execution framing shall prevail unless a contrary result is required by law.

### 253. Council Performance Governance, Accountability, and Review Cycle (GCRI United States)

#### 253.1 Council Performance Governance as an Institutional Control

GCRI US shall maintain performance governance for each Helix Council, Council Bureau, standing committee, working party, expert mechanism, and Council Secretariat function. Performance governance shall ensure that Councils are not merely constituted, named, convened, or publicly described, but are actually useful, balanced, safe, disciplined, timely, and aligned with the Corporation’s public-good mission.

Council performance shall be assessed against the Council’s constitutional purpose, not against volume alone. A Council shall not be considered successful merely because it holds many meetings, attracts prestigious participants, produces long documents, or appears publicly impressive. It shall be considered effective where it produces high-quality deliberation, improves institutional outputs, preserves dissent, identifies risk, protects participation, avoids capture, respects non-execution boundaries, and strengthens GCRI US’s credibility.

Performance governance shall evaluate:

a) whether the Council is fulfilling its mandate;\
b) whether its composition remains balanced and relevant;\
c) whether participation is active and meaningful;\
d) whether outputs are timely, useful, and properly bounded;\
e) whether records are complete and audit-grade;\
f) whether dissent and minority views are preserved;\
g) whether safeguards, accessibility, and non-retaliation rules are functioning;\
h) whether conflicts, recusals, and competition-safety rules are respected;\
i) whether Council outputs improve Board, Secretariat, publication, consultation, and public-good work; and\
j) whether the Council should continue, be redesigned, be merged, be suspended, or be sunset.

#### 253.2 Council Scorecards, KPIs, and Reporting Cadence

Each standing Council may maintain a Council scorecard or equivalent performance dashboard. The scorecard shall be used for governance learning, not cosmetic reporting. It shall be reviewed periodically by the Council Bureau, Secretariat, relevant Board committee, or Board, according to the Charter.

Council performance indicators may include:

a) throughput indicators, including number of matters docketed, reviewed, closed, escalated, returned, deferred, or adopted;\
b) timeliness indicators, including time from intake to agenda, review, output, consultation closure, escalation, and closure;\
c) quality indicators, including proportion of outputs with complete effect coding, evidence lineage, dissent treatment, and review gates;\
d) legitimacy indicators, including participation balance, attendance, contribution diversity, accessibility support, and consultation responsiveness;\
e) integrity indicators, including conflicts disclosed, recusals applied, public-claims corrections, misuse incidents, and competition-safety interventions;\
f) safeguards indicators, including protected participation issues, retaliation concerns, CIC-sensitive handling, attribution corrections, and grievance-linked escalations;\
g) impact indicators, including outputs adopted, outputs revised because of Council input, risks prevented, public-claims improved, or governance controls strengthened; and\
h) learning indicators, including recurring issues, unresolved concerns, cross-case patterns, and policy or Charter improvements generated from Council work.

The reporting cadence shall be proportionate. High-volume or high-risk Councils may report quarterly. Lower-volume Councils may report semi-annually or annually. Serious incidents shall be escalated immediately, not held for periodic reporting.

#### 253.3 Chair and Bureau Accountability, Including Growth-With-Integrity Metrics

Council Chairs, Vice-Chairs, rapporteurs, Bureau members, committee chairs, working-party leads, and Council officers shall be accountable for procedural leadership, records quality, fairness, safeguards, and mandate compliance. They shall not be judged only by activity volume, public visibility, recruitment success, or event production.

Chair and Bureau accountability shall consider:

a) whether agendas are properly formed and classified;\
b) whether meetings are fair, disciplined, and productive;\
c) whether dissent is preserved;\
d) whether conflicts and recusals are handled;\
e) whether participation is balanced and not dominated;\
f) whether outputs use correct controlled vocabulary and effect coding;\
g) whether sensitive matters are handled safely;\
h) whether public descriptions remain accurate;\
i) whether membership or participant growth is pursued with integrity; and\
j) whether the Council contributes to GCRI US’s institutional maturity.

Where a Council has growth or membership objectives, those objectives shall be “growth-with-integrity” objectives. Growth shall not mean indiscriminate recruitment, prestige accumulation, sponsor capture, weak screening, or expansion without Secretariat capacity. Growth shall mean responsible expansion of credible, diverse, mission-aligned, role-bounded participation.

#### 253.4 Throughput, Quality, Legitimacy, Integrity, and Impact Indicators

Council performance shall be reviewed across five core dimensions: throughput, quality, legitimacy, integrity, and impact.

Throughput shall measure whether matters move through the Council system without stagnation. It shall not reward speed at the expense of safeguards or quality.

Quality shall measure whether Council outputs are useful, accurate, evidence-informed, clear, properly classified, effect-coded, and adoption-ready where intended.

Legitimacy shall measure whether relevant perspectives are present, heard, recorded, and responded to, including under-resourced, community, Indigenous, civil-society, public-authority, operator, and research perspectives where relevant.

Integrity shall measure whether the Council resists capture, manages conflicts, preserves competition safety, prevents public overclaim, protects confidentiality, and respects the non-execution boundary.

Impact shall measure whether Council work actually improves GCRI US outputs, risk governance, public-good quality, public trust, consultation responsiveness, correction discipline, and institutional learning.

A Council that produces many outputs but weakens safeguards or creates public overclaim shall be underperforming. A Council that produces fewer outputs but prevents serious institutional error may be highly valuable.

#### 253.5 Non-Compliance, Corrective Action, and Escalation

Where a Council, Bureau, committee, working party, expert mechanism, or Secretariat support process fails to comply with Part X, the Council Charter, records rules, safeguards rules, conflict controls, competition-safety rules, public-claims controls, or non-execution boundaries, corrective action shall be required.

Corrective action may include:

a) correction of records, minutes, outputs, or public summaries;\
b) reclassification, withdrawal, or supersession of defective outputs;\
c) additional training for Council officers or participants;\
d) revision of templates, controlled vocabulary, intake forms, or decision-pack standards;\
e) replacement or restriction of chair, rapporteur, Bureau member, committee chair, or working-party lead;\
f) recusal or removal of conflicted participants;\
g) suspension of public description or publication authority;\
h) independent review of Council process;\
i) redesign of Council composition or seat allocation;\
j) escalation to Board, legal, safeguards, security, integrity, finance, or records functions; and\
k) suspension, reconstitution, merger, or sunset of the Council.

Non-compliance shall be documented. Repeated non-compliance shall be treated as structural failure, not isolated mistake.

#### 253.6 Annual Council Report Packs and Review Cycle

Each standing Council shall prepare or contribute to an annual Council report pack unless the Board or Council Charter provides a different cadence. The annual report pack shall support institutional review, not public relations.

The annual Council report pack may include:

a) Council mandate and Charter status;\
b) participant composition and seat changes;\
c) meetings held and attendance patterns;\
d) matters docketed, reviewed, escalated, closed, or pending;\
e) outputs issued and their effect codes;\
f) consultations conducted and comment-disposition summaries;\
g) dissent, minority reports, and unresolved issues;\
h) conflicts, recusals, safeguards matters, and integrity interventions;\
i) public-claims corrections or misuse incidents;\
j) controlled-room matters and public-safe summaries;\
k) adopted outputs influenced by the Council;\
l) performance against scorecard;\
m) risks, dead zones, capacity gaps, and recommendations; and\
n) proposed Charter, composition, procedure, or support changes.

Public versions may be prepared, but sensitive information shall be redacted or summarized safely. The authoritative internal annual report shall remain part of the corporate record.

#### 253.7 External Feedback Loop and Institutional Learning

GCRI US shall maintain an external feedback loop where appropriate. Council outputs should be tested not only internally but also against the experience of users, participants, affected persons, public authorities, operators, researchers, civil society, communities, Indigenous participants, and other relevant stakeholders.

External feedback may identify:

a) unclear Council outputs;\
b) inaccessible consultation materials;\
c) public overclaim or misunderstanding;\
d) participant-status misuse;\
e) implementation gaps;\
f) research or evidence limitations;\
g) safeguards or attribution problems;\
h) community or Indigenous concerns;\
i) public-authority sensitivity; and\
j) need for correction or revision.

Feedback shall be routed into the Council Operating System. It shall not remain informal commentary. Where feedback shows a recurring problem, GCRI US shall update templates, training, public descriptions, Charter provisions, consultation processes, or records controls.

#### 253.8 Sunset, Redesign, or Suspension of Underperforming Council Structures

A Council, Bureau, committee, working party, expert mechanism, or Council-like structure may be sunset, redesigned, suspended, merged, or reconstituted where it no longer serves its mandate or creates unacceptable risk.

Triggers may include:

a) persistent inactivity;\
b) failure to produce useful outputs;\
c) capture by a sector, donor, sponsor, vendor, personality, or bloc;\
d) repeated public overclaim;\
e) failure to preserve dissent;\
f) safeguards or retaliation concerns;\
g) weak records or untracked outputs;\
h) recurring conflicts or competition-safety risk;\
i) loss of relevant expertise;\
j) duplicated mandate;\
k) Secretariat capacity failure; or\
l) misalignment with GCRI US mission or non-execution boundary.

Sunset or redesign shall include records preservation, closure of open matters, transfer of active cases, public-description correction, access revocation, and notice to affected participants. Reconstitution shall not be used to remove dissenters or consolidate control.

#### 253.9 Interpretive Rule for Council Performance Governance, Accountability, and Review Cycle

This Section shall be interpreted to preserve a controlling proposition: the Helix Councils of GCRI US shall be continuously evaluated for usefulness, integrity, legitimacy, safeguards, records quality, public-claims discipline, throughput, impact, and mission alignment, and Council structures that underperform or create risk shall be corrected, redesigned, suspended, or sunset.

Where ambiguity exists, the interpretation that better preserves performance accountability, growth with integrity, annual review, external feedback, corrective action, and lifecycle discipline shall prevail unless a contrary result is required by law.

### 254. Cross-Council Coordination, Escalation, and Dispute Routing (GCRI United States)

#### 254.1 Cross-Council Coordination as a Controlled Governance Function

Cross-Council coordination shall be a controlled governance function of GCRI US. It shall ensure that matters requiring more than one knowledge surface are handled coherently without creating a hidden plenary body, informal super-Council, or substitute Board authority. Coordination shall be used to align public-authority, operator, academic, civil-society, media, community, Indigenous, safeguards, technical, and institutional perspectives while preserving each Council’s distinct mandate.

Cross-Council coordination may be required where a matter involves:

a) public-sector feasibility and community impact;\
b) technical implementation and evidence quality;\
c) AI, data, ontology, and public trust;\
d) public-good infrastructure and non-execution boundary risk;\
e) consultation outputs requiring multiple domains of review;\
f) Council disagreement affecting adoption-readiness;\
g) publication materials that may create public reliance;\
h) safeguards concerns affecting more than one Council; and\
i) Nexus-aligned work where legal separateness, public claims, technical quality, and participation legitimacy must be examined together.

Coordination shall not erase Council distinctions. The PAC speaks to public authority and public-law sensitivity. The IOC speaks to operational feasibility and competition-safe implementation. The ARC speaks to method, evidence, AI, data, and research integrity. The CMC speaks to transparency, public meaning, consultation, and communications integrity. The CIC speaks to dignity, community, Indigenous, rights-sensitive, and lived-context concerns. Coordination exists to put these views into relationship, not to flatten them into artificial consensus.

#### 254.2 Escalation Ladder Across Councils and to Higher Organs

GCRI US shall maintain an escalation ladder for Council matters. Escalation shall ensure that risks, disputes, defects, warnings, and unresolved issues reach the competent authority before publication, adoption, reliance, or external use.

The escalation ladder may include:

a) matter owner or submitting function;\
b) Council Chair, Vice-Chair, or Bureau;\
c) relevant Council committee or working party;\
d) Council Secretariat;\
e) cross-Council coordination process;\
f) safeguards, integrity, legal, security, privacy, finance, records, research, or public-claims function;\
g) Board committee;\
h) full Board; and\
i) emergency governance route where immediate protective action is required.

Escalation shall be mandatory where a matter involves material public overclaim, unsafe participation, retaliation risk, unresolved conflict, competition concern, controlled-room breach, community or Indigenous overclaim, public authority overclaim, research-integrity defect, security or privacy concern, financial-control issue, or non-execution boundary drift.

Escalation is not failure. It is the method by which the Council system protects the Corporation from informal authority and premature reliance.

#### 254.3 Procedural Disputes, Integrity Disputes, and Methodological Disputes

Council disputes shall be classified before resolution. Different disputes require different routes.

A procedural dispute concerns notice, quorum, agenda, voting, dissent capture, classification, access, minutes, output coding, or meeting validity. It shall be routed to the Council Bureau, Rules and Procedure Committee, Secretariat, Secretary, or Board committee where material.

An integrity dispute concerns conflict, recusal, capture, retaliation, misuse of Council status, public overclaim, confidentiality breach, competition safety, participant conduct, or procedural abuse. It shall be routed to safeguards, integrity, legal, Secretariat, or Board review depending on severity.

A methodological dispute concerns evidence, data, AI, ontology, reproducibility, uncertainty, model risk, research design, or publication integrity. It shall be routed to ARC, expert review, red-team review, replication process, research-integrity review, or Board review where institutional reliance is high.

A safeguards dispute concerns community harm, Indigenous knowledge, dignity, attribution, participation safety, grievance, protected reporting, or retaliation. It shall be routed to CIC, safeguards function, controlled-room process, legal review, or Board review as appropriate.

A public-claims dispute concerns whether an output may be misunderstood as approval, endorsement, recognition, certification, public mandate, government support, community consent, Indigenous consent, market readiness, routeability, or execution authority. It shall be routed to CMC, communications integrity, legal, Secretariat, or Board review.

#### 254.4 Cross-Council Reconciliation and Convergence Procedures

Where Councils produce divergent views on the same matter, GCRI US may use reconciliation and convergence procedures. The goal shall not be to force agreement. The goal shall be to determine what can be resolved, what remains contested, what conditions are required, and what the competent authority must know before acting.

Reconciliation may include:

a) joint issue map;\
b) side-by-side Council findings;\
c) structured question reframing;\
d) supplementary evidence request;\
e) working party with balanced Council representation;\
f) expert mechanism or red-team review;\
g) controlled-room session for sensitive facts;\
h) safeguards review;\
i) public-claims review;\
j) separate annexes preserving Council-specific positions; and\
k) escalation to Board or committee decision.

A convergence memorandum may identify:

i) areas of agreement;\
ii) areas of disagreement;\
iii) reasons for disagreement;\
iv) evidence or safeguards gaps;\
v) proposed conditions for proceeding;\
vi) matters requiring further review; and\
vii) matters that should not proceed.

Convergence shall not erase dissent. If disagreement remains material, the decision pack shall preserve it.

#### 254.5 Routing to Board, Secretariat, Safeguards, Integrity, or Legal Lanes as Needed

Council matters shall be routed to the appropriate institutional lane when they exceed Council authority. Councils may identify risks and recommend action, but they shall not assume powers assigned to the Board, officers, legal function, safeguards function, security function, finance function, or corporate records authority.

Routing shall be required where:

a) Board reserved matters are implicated;\
b) external legal commitments may arise;\
c) nonprofit status, private benefit, or tax issues are implicated;\
d) public statements may create legal or reputational reliance;\
e) contracts, grants, funding, or financial obligations are implicated;\
f) personal data, security, or controlled information is involved;\
g) protected participation or retaliation issues arise;\
h) conflict, capture, or serious integrity concerns arise;\
i) public authority or regulated-perimeter sensitivity exists; or\
j) Council outputs may affect GCRI US’s legal separateness from other Nexus-aligned entities.

Routing records shall state why the matter was routed, to whom, under what authority, with what timeline, and what interim restrictions apply.

#### 254.6 Finality, Reopening, and Anti-Forum-Shopping Controls

GCRI US shall maintain finality and reopening rules for Council matters. A matter that has been resolved, closed, rejected, withdrawn, or adopted shall not be repeatedly reopened merely because a participant seeks a different outcome. At the same time, reopening shall be permitted where new evidence, procedural defect, safeguards concern, public-claims defect, or material risk justifies review.

A matter may be reopened where:

a) new material evidence emerges;\
b) a conflict or recusal defect is discovered;\
c) dissent was suppressed or omitted;\
d) consultation comments were mishandled;\
e) public-claims language was defective;\
f) community or Indigenous input was overclaimed;\
g) security, privacy, legal, or safeguards risk emerges;\
h) the output has been misused externally;\
i) the record is incomplete or inaccurate; or\
j) the competent authority requests reconsideration.

Forum-shopping shall be prohibited. A participant may not take the same matter from Council to Council, committee to committee, or reviewer to reviewer to avoid an adverse decision, bypass safeguards, suppress dissent, or secure more favorable wording. The Council Operating System shall link related cases and require disclosure of prior routing, prior decisions, and current status.

#### 254.7 Records Linkage and Notice Discipline for Cross-Council Disputes

All cross-Council disputes, escalations, and reconciliation processes shall be linked to the relevant case IDs. Records linkage shall allow GCRI US to see the full chain of proceedings and prevent fragmented institutional memory.

Cross-Council dispute records shall include:

a) originating matter;\
b) Councils involved;\
c) nature of dispute;\
d) prior outputs;\
e) dissent or minority notes;\
f) routing decisions;\
g) escalation route;\
h) reconciliation steps;\
i) final or current status;\
j) unresolved issues; and\
k) publication or adoption restrictions.

Notice discipline shall ensure that affected Councils and participants know when a matter has been escalated, reopened, reclassified, deferred, or closed, subject to classification and need-to-know rules. No Council shall publicly describe a disputed output as settled while a material dispute remains open.

#### 254.8 Cross-Council Disputes in Nexus-Aligned and Public-Good Infrastructure Matters

Where a dispute concerns Nexus-aligned public-good infrastructure, evidence rails, risk intelligence, AI-enabled analysis, standards, readiness frameworks, resilience finance interfaces, or cross-entity cooperation, GCRI US shall apply heightened routing discipline. Such matters may be misunderstood externally and may implicate legal separateness, public-good boundaries, execution-side confusion, public authority perception, and community trust.

In these matters, dispute routing shall verify:

a) whether GCRI US is acting only within its nonprofit public-good capacity;\
b) whether any other entity’s authority is being implied;\
c) whether downstream execution is being suggested without lawful actor separation;\
d) whether public-good output could be treated as routeability, certification, or market readiness;\
e) whether evidence, AI, or data claims are adequately bounded;\
f) whether public authority, community, or Indigenous participation is overclaimed; and\
g) whether the Board or legal function must review before publication.

Where ambiguity remains, the matter shall be narrowed, conditioned, or held until authority and public meaning are clear.

#### 254.9 Interpretive Rule for Cross-Council Coordination, Escalation, and Dispute Routing

This Section shall be interpreted to preserve a controlling proposition: cross-Council coordination and dispute routing in GCRI US shall ensure that multi-domain matters are reconciled, escalated, and recorded through competent pathways without creating hidden plenary authority, forum-shopping, false consensus, or Council outputs that exceed mandate.

Where ambiguity exists, the interpretation that better preserves Council-specific mandates, escalation discipline, dispute classification, proper routing, finality with correctionability, anti-forum-shopping controls, records linkage, notice discipline, and Nexus-aligned non-execution safeguards shall prevail unless a contrary result is required by law.

### 255. Lifecycle, Review, Reconstitution, Suspension, and Sunset of Councils (GCRI United States)

#### 255.1 Periodic Review of Each Council’s Mandate, Composition, Utility, and Risk Profile

Each Helix Council of GCRI US shall be subject to periodic lifecycle review. The purpose of lifecycle review is to ensure that each Council continues to serve a real public-good function, remains aligned with the Corporation’s mission lock, operates within its Charter, preserves participation integrity, produces useful outputs, and does not become stale, captured, symbolic, duplicative, unsafe, or misaligned with the non-execution boundary.

Lifecycle review shall examine, at minimum:

a) whether the Council’s mandate remains necessary and current;\
b) whether the Council’s composition reflects its purpose;\
c) whether the Council has the right balance of expertise, institutional perspective, lived-context knowledge, independence, and safeguards capacity;\
d) whether the Council has active participation rather than nominal rosters;\
e) whether its outputs are timely, usable, well-recorded, effect-coded, and within authority;\
f) whether dissent, minority views, and unresolved issues are preserved;\
g) whether consultation, comment handling, and feedback loops are meaningful;\
h) whether conflicts, recusals, competition sensitivity, and public-claims risks are being managed;\
i) whether the Council creates value for Board, Secretariat, public-good, research, standards, policy, and safeguards functions;\
j) whether its work creates any execution-side confusion, certification overclaim, public-authority overclaim, community or Indigenous overclaim, or market-reliance risk; and\
k) whether the Council should continue, be amended, expanded, contracted, merged, suspended, reconstituted, or sunset.

Lifecycle review shall not be a ceremonial annual exercise. It shall be a governance control capable of changing Council structure where necessary.

#### 255.2 Amendment, Expansion, Contraction, Merger, or Sunset of Councils

The Board or other competent authority may amend, expand, contract, merge, suspend, sunset, or reconstitute a Council where institutional need, risk, performance, safeguards, mandate overlap, participant safety, or public-good value requires it.

A Council may be amended where its Charter requires clarification, its outputs require better taxonomy, its safeguards need strengthening, its procedures require modernization, or its relationship to other Councils requires better routing.

A Council may be expanded where:

a) new expertise is required;\
b) material blind spots have emerged;\
c) under-represented perspectives need inclusion;\
d) workload exceeds existing capacity;\
e) new public-good domains require structured review; or\
f) the Council’s mandate has legitimately matured.

A Council may be contracted where:

i) participation is too broad for effective deliberation;\
ii) access risk is excessive;\
iii) a smaller specialist structure would be safer;\
iv) seat proliferation creates confusion;\
v) Secretariat capacity is insufficient; or\
vi) broad membership creates public-claims or confidentiality risk.

A Council may be merged where mandates overlap and separate structures create duplication, fragmentation, or inconsistent output. A Council may be sunset where its mandate has expired, its utility has ended, its risk exceeds its value, or its functions can be better performed through another body.

#### 255.3 Trigger Events for Urgent Reconstitution or Suspension

Urgent reconstitution or suspension may occur where ordinary lifecycle review is insufficient to protect the Corporation, participants, public trust, records, or public-good assets. Suspension may be full or partial. It may apply to a Council, Bureau, committee, working party, expert mechanism, participant class, output pathway, public-facing function, or controlled-room process.

Trigger events may include:

a) serious safeguards breach, retaliation, harassment, intimidation, or unsafe participation;\
b) material public overclaim involving Council status, public authority, academic validation, industry endorsement, media support, community consent, or Indigenous approval;\
c) donor, sponsor, vendor, political, sectoral, or institutional capture;\
d) repeated failure to maintain records, minutes, case IDs, dissent, output coding, or closure records;\
e) competition, antitrust, procurement, or market-sensitivity breach;\
f) controlled-room breach, unauthorized disclosure, privacy incident, or security incident;\
g) serious conflict-of-interest or recusal failure;\
h) misuse of Council outputs in fundraising, procurement, investor, regulatory, political, or public-facing materials;\
i) repeated role inflation by Chair, Bureau, rapporteur, Secretariat, or participants;\
j) inability to achieve quorum or active participation over repeated cycles;\
k) public loss of trust arising from Council operation;\
l) misalignment with GCRI US’s nonprofit status, mission lock, public-good role, or non-execution boundary; or\
m) legal, regulatory, fiduciary, or reputational concern requiring immediate pause.

Suspension shall be recorded with reasons, scope, effective date, interim restrictions, records controls, communication plan, review route, and conditions for reinstatement or reconstitution.

#### 255.4 Continuity of Records, Ongoing Cases, and Delegated Work During Restructuring

Where a Council is amended, suspended, merged, reconstituted, or sunset, GCRI US shall preserve continuity of records, ongoing cases, delegated work, and participant protections. Structural change shall not erase prior records, unresolved dissent, consultation obligations, safeguards issues, controlled-room restrictions, or pending escalations.

The restructuring plan shall identify:

a) open case IDs;\
b) pending Council outputs;\
c) ongoing consultations;\
d) working-party mandates;\
e) expert-review engagements;\
f) unresolved dissent or minority reports;\
g) controlled-room materials;\
h) public-safe summaries pending release;\
i) participant-status records;\
j) conflicts and recusals;\
k) access rights requiring revocation or transfer;\
l) Board, committee, legal, safeguards, security, privacy, finance, research, or public-claims matters requiring continuity; and\
m) repository and archive actions.

Where a Council is sunset or merged, open matters shall be transferred to an appropriate Council, Board committee, Secretariat function, expert mechanism, or closed with reasons. No matter shall be abandoned silently.

#### 255.5 No Reconstitution May Defeat Representation Integrity, Mission Lock, or Non-Substitution Rules

Reconstitution shall not be used to defeat representation integrity, remove dissenters improperly, consolidate control, reward allies, punish critics, erase minority views, hide prior defects, evade public-claims correction, or bypass Council procedures. Reconstitution must serve public-good governance, not power consolidation.

Accordingly, any reconstitution shall preserve:

a) mission lock and nonprofit public-benefit purpose;\
b) Board fiduciary authority and reserved matters;\
c) role-bounded Council authority;\
d) safeguards, protected participation, and non-retaliation;\
e) conflict, recusal, competition, and anti-capture controls;\
f) public-description and attribution accuracy;\
g) records continuity and dissent preservation;\
h) non-execution boundary;\
i) community and Indigenous knowledge protections; and\
j) legal separateness from GCRI Canada, GRF, GRA, protocol bodies, host institutions, delivery actors, and other Nexus-aligned entities.

If reconstitution follows a dispute or breach, the reconstitution record shall distinguish structural correction from retaliation. Participants removed for integrity reasons shall be treated according to due process and confidentiality rules. Participants removed merely because they raised good-faith concerns shall be protected.

#### 255.6 Gazette, Repository, and Public-Description Discipline for Council Lifecycle Changes

Council lifecycle changes shall be reflected in the authoritative repository and, where appropriate, in the Gazette or public notice system. The public record shall not show a Council as active when it has been suspended, merged, sunset, or materially reconstituted. Participant rosters, public pages, biographies, event materials, consultation pages, and Council summaries shall be updated promptly.

Lifecycle notices may include:

a) creation of a new Council;\
b) adoption or amendment of a Council Charter;\
c) appointment or transition of Council leadership;\
d) suspension of a Council or Council function;\
e) merger of Councils;\
f) reconstitution after review;\
g) sunset or dissolution;\
h) transfer of ongoing matters; and\
i) correction of public-description errors.

Public notices shall be carefully framed. They shall not disclose sensitive reasons where doing so would expose protected persons, confidential matters, legal concerns, security issues, Indigenous or community-sensitive information, or controlled-room material. However, they shall be truthful enough to prevent public misunderstanding.

The repository shall preserve superseded Charters, prior rosters, lifecycle decisions, closure memoranda, public notices, and cross-references to affected case IDs.

#### 255.7 Lifecycle Review Criteria for the Five Helix Councils

Lifecycle review shall be tailored to each Council.

For the PAC, review shall assess whether public-authority participation remains accurately bounded, whether public-law and public-sector feasibility input is useful, whether government-overclaim is controlled, and whether public authority sensitivities are handled safely.

For the IOC, review shall assess whether operational and technical input remains useful, whether competition and antitrust controls are effective, whether vendor-neutrality is preserved, whether implementation advice avoids procurement preference, and whether cyber and resilience expertise remains adequate.

For the ARC, review shall assess whether methodological challenge, evidence-quality review, AI/data/ontology review, uncertainty discipline, research-integrity review, and publication correction functions remain strong.

For the CMC, review shall assess whether public-legibility, transparency, communications integrity, consultation accessibility, media independence, civil-society challenge, and anti-reputation-laundering controls remain effective.

For the CIC, review shall assess whether community and Indigenous participation is safe, non-extractive, properly supported, consent-aware, rights-sensitive, dignity-centered, and not overclaimed.

Each Council shall be reviewed in light of its particular risks. Uniform process shall not erase Council-specific accountability.

#### 255.8 Transition, Handover, and Interim Governance During Council Change

During Council amendment, suspension, merger, reconstitution, or sunset, GCRI US may appoint interim governance arrangements. Interim arrangements shall be narrow, time-bound, and records-first. They may preserve urgent functions while preventing loss of records, participant protection, public correction, or mission-critical review.

Interim arrangements may include:

a) temporary Secretariat custody of open matters;\
b) acting Bureau or caretaker chair;\
c) temporary routing to another Council;\
d) suspension of public-facing outputs;\
e) controlled access to records;\
f) transfer of consultation management;\
g) completion of urgent public-safe correction;\
h) continuation of safeguards or protected escalation routes; and\
i) Board oversight of high-risk matters.

Interim authority shall not become permanent by inertia. It shall expire on the date stated unless extended by competent authority with reasons.

#### 255.9 Post-Reconstitution Validation and Readiness Review

A reconstituted Council shall not resume full operations until readiness review confirms that it can operate safely and lawfully. Readiness review shall ensure that the Council’s Charter, leadership, participant roles, records, Secretariat support, conflict controls, safeguards, controlled-room rules, output taxonomy, and public-description controls are ready.

Readiness review shall confirm:

a) approved Charter or interim Charter;\
b) updated seat allocation;\
c) participant onboarding;\
d) capacity declarations;\
e) conflict disclosures;\
f) Bureau appointments;\
g) Secretariat support;\
h) records repository;\
i) open case transfer;\
j) consultation obligations;\
k) public-description updates;\
l) access rights and revocations; and\
m) training requirements.

A reconstituted Council shall not rely on old authority unless the reconstitution instrument preserves it. Where old outputs remain valid, the record shall say so. Where old outputs are withdrawn, superseded, or subject to review, the record shall say so.

#### 255.10 Interpretive Rule for Lifecycle, Review, Reconstitution, Suspension, and Sunset of Councils

This Section shall be interpreted to preserve a controlling proposition: each Council of GCRI US shall remain a living, reviewable, correctable, and mission-aligned institutional structure that may be amended, rebalanced, suspended, reconstituted, merged, or sunset where necessary to protect public-good value, safeguards, records integrity, role discipline, and the non-execution boundary.

Where ambiguity exists, the interpretation that better preserves periodic review, lifecycle discipline, urgent suspension authority, records continuity, representation integrity, public-description accuracy, Council-specific accountability, interim governance limits, and readiness review shall prevail unless a contrary result is required by law.

### 256. Constitutional Effect of Part X (GCRI United States)

#### 256.1 Part X as the Governing Map for Helix Councils and Structured Plural Participation

Part X shall constitute the governing map for all Helix Councils and structured plural participation within GCRI US. It shall control the creation, constitution, authority, composition, deliberation, output, records, safeguards, consultation, controlled-room handling, performance review, escalation, reconstitution, and sunset of all Councils and Council-like bodies operating under or in association with GCRI US.

Part X shall apply to:

a) each standing Helix Council;\
b) each Council Bureau, Chair, Vice-Chair, rapporteur, committee, working party, drafting group, and expert mechanism;\
c) each Council delegate, alternate, adviser, observer, guest, expert, public authority participant, operator participant, academic participant, civil-society participant, media participant, community participant, Indigenous participant, and Secretariat-supported participant;\
d) each Council intake, docket, case ID, agenda, notice, meeting, consultation, output, dissent note, minority report, decision pack, public-safe summary, correction, withdrawal, supersession, and closure memorandum; and\
e) each public description of Council status, participant status, Council output, consultation result, or Council-derived institutional action.

Part X shall be read as an integrated operating constitution. No section shall be used to weaken another section. Council participation exists only because it is role-bounded, records-first, safeguards-protected, conflict-managed, competition-safe, and non-executionary. If those controls fail, the Council system loses its constitutional legitimacy.

#### 256.2 No Council, Bureau, Committee, Working Party, Expert Mechanism, or Secretariat Process May Contradict Part X

No Council, Bureau, committee, working party, drafting group, expert mechanism, Secretariat process, consultation process, public-facing event, controlled-room session, or Council-like structure may contradict Part X. Any Charter, notice, agenda, minutes, output, decision pack, public description, or participant communication that purports to grant broader authority than Part X permits shall be void, voidable, severed, corrected, withdrawn, or superseded to the extent of the inconsistency.

Accordingly:

a) no Council may become a Board substitute;\
b) no Bureau may become a hidden decision body;\
c) no working party may become a shadow Council;\
d) no expert mechanism may become a certification authority by implication;\
e) no consultation may become consent unless expressly designed and lawfully authorized as such;\
f) no public authority participation may become government mandate by attendance;\
g) no industry participation may become vendor endorsement;\
h) no academic participation may become scientific validation;\
i) no civil-society or media participation may become public mandate;\
j) no community or Indigenous participation may become social license, consent, or approval beyond recorded scope; and\
k) no Council output may create routeability, recognition, certification, procurement preference, regulated execution, or external reliance without explicit lawful authority.

Council convenience, institutional ambition, public visibility, donor expectation, participant prestige, or urgency shall not override Part X.

#### 256.3 Council Legitimacy Depends on Forms-First, Records-First, Safeguarded, and Role-Bounded Operation

Council legitimacy shall depend on forms-first, records-first, safeguarded, and role-bounded operation. A Council shall not be legitimate merely because important persons attended, powerful institutions participated, public-facing language was polished, or consensus was announced. Legitimacy requires that the record show proper authority, correct role, clear mandate, fair procedure, protected participation, preserved dissent, accurate classification, and bounded effect.

The controlling conditions of Council legitimacy are:

a) constitution, meaning the Council or Council-like body exists under a valid Charter or mandate;\
b) intake, meaning the matter entered the Council Operating System with case ID, classification, and purpose;\
c) role discipline, meaning each participant acted within recorded capacity;\
d) safeguards, meaning participation was protected and not extractive, coercive, retaliatory, or unsafe;\
e) conflict control, meaning interests, recusals, competition risks, and capture risks were managed;\
f) deliberation integrity, meaning views, evidence, dissent, and uncertainty were considered honestly;\
g) records integrity, meaning minutes, outputs, decision packs, and closure records are complete enough for reliance;\
h) effect coding, meaning outputs state what they do and do not do;\
i) public-claims discipline, meaning public descriptions do not overstate authority; and\
j) non-execution discipline, meaning Council work remains public-good, advisory, deliberative, and non-regulated.

If a Council act lacks these conditions, it may still be informative, but it shall not carry formal Council effect unless corrected or ratified by competent authority where lawful.

#### 256.4 Ambiguity Resolves Toward Narrower Council Authority, Stronger Participation Protection, and Clearer Non-Substitution

Any ambiguity under Part X shall be resolved toward narrower Council authority, stronger participation protection, clearer records, stricter public-claims discipline, stronger safeguards, and clearer non-substitution for corporate authority. Councils are designed to strengthen institutional learning. They are not designed to absorb corporate power.

This interpretive rule applies where ambiguity exists concerning:

a) whether a Council output is advisory or adopted;\
b) whether a Council may publish or only recommend publication;\
c) whether a participant speaks personally, institutionally, officially, or as observer;\
d) whether public authority participation creates public mandate;\
e) whether community or Indigenous participation creates consent;\
f) whether academic review creates validation;\
g) whether operator review creates procurement or vendor preference;\
h) whether media or civil-society participation creates public endorsement;\
i) whether a working party has authority to decide or only draft;\
j) whether a controlled-room classification protects legitimate sensitivity or improperly restricts participation;\
k) whether dissent must be included in a decision pack; and\
l) whether a Council matter touches regulated execution or remains within public-good stewardship.

Where authority is unclear, the Council shall not assume it. Where public meaning is unclear, the claim shall be narrowed. Where participation safety is unclear, safeguards shall control.

#### 256.5 Failure to Respect Part X as a Constitutional Governance Failure

A material failure to respect Part X shall constitute a constitutional governance failure, not a mere meeting defect. Such failure may compromise the Corporation’s nonprofit integrity, public trust, records validity, participation safety, public-good credibility, and non-execution boundary.

Material failures include:

a) creating or operating a Council without Charter or mandate;\
b) permitting a Council to bind GCRI US without authority;\
c) issuing Council outputs without case ID, effect code, classification, or records;\
d) suppressing dissent or minority views;\
e) mishandling community or Indigenous participation;\
f) overclaiming public authority, academic, media, civil-society, industry, community, or Indigenous participation;\
g) allowing vendor, donor, sponsor, political, sectoral, or personality capture;\
h) conducting Council business through informal email governance;\
i) publishing Council outputs without public-claims review;\
j) allowing working parties or Bureaus to become hidden decision bodies;\
k) failing to correct public misuse of Council status;\
l) mishandling controlled-room materials;\
m) failing to manage conflicts, recusals, or competition-sensitive discussions; and\
n) permitting Council work to drift into procurement, market activity, certification, routeability, or regulated execution.

Where such failure occurs, GCRI US shall correct records, review affected outputs, suspend reliance where necessary, notify affected participants where appropriate, impose safeguards or access restrictions, revise procedures, and escalate to the Board, legal, safeguards, integrity, or other competent function as required.

#### 256.6 Binding Effect on Future Council Design, Charters, Procedures, and Public Descriptions

Part X shall bind all future Council design, Council Charters, schedules, templates, public descriptions, consultation processes, decision packs, public-safe summaries, controlled-room procedures, expert mechanisms, working-party mandates, and Council performance systems unless lawfully amended.

Future Council instruments shall preserve:

a) the five-Council topology unless amended by competent authority;\
b) formal Charter discipline;\
c) role-bounded participation;\
d) advisory and deliberative Council status;\
e) Board and corporate authority primacy;\
f) Secretariat and records-first validity;\
g) safeguards and protected participation;\
h) conflict, recusal, competition, and anti-capture controls;\
i) dissent and minority protection;\
j) public-claims discipline;\
k) controlled-room integrity;\
l) consultation honesty;\
m) decision-pack completeness;\
n) performance review and lifecycle discipline; and\
o) non-execution public-good boundaries.

No future instrument shall use softer language, operational shortcuts, or public-facing ambiguity to weaken Part X. Growth of the Council system must mean stronger governance, not larger informality.

#### 256.7 Final Reading Rule for Part X

Part X shall be read to ensure that GCRI US can convene plural intelligence at serious institutional scale without creating role collapse, hidden authority, false endorsement, public overclaim, unsafe participation, or execution-side confusion. The Councils are a constitutional participation architecture: they are powerful because they are bounded.

The final reading rule is therefore:

No Council without Charter. No matter without case ID. No output without effect code. No consultation without disposition. No dissent without record. No sensitive material without handling. No public claim without authority. No participation without safeguards. No Council recommendation without adoption pathway. No Council structure that substitutes for Board, officer, Secretariat, safeguards, legal, security, finance, research, or corporate authority. No Council act that compromises nonprofit integrity, public-good stewardship, legal separateness, or the non-execution boundary.

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.therisk.global/organization/organization/governance/charter-us/x.-councils.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.