ARTICLE XVIII. DEFINITIONS

Section 504. Definitions Purpose and Scope

504.1 Definitions Purpose.

504.1.1 Definitions under these Bylaws shall provide the Corporation’s authoritative interpretive framework for institutional identity, governance authority, public-benefit purpose, nonprofit character, participation, support, records, public authority interfaces, finance boundaries, certification and procurement boundaries, data / AI / cyber / privacy controls, public-safe publication, technical assets, Nexus coordination, safeguards, protected knowledge, validity-by-record, correctionability, dissolution, wind-up, and enforcement.

504.1.2 Definitions shall ensure that terms used by or for the Corporation are not used loosely, commercially, politically, technically, or rhetorically in a manner that creates unsupported authority, public authority confusion, finance reliance, certification implication, recognition implication, procurement advantage, provider preference, public warning confusion, emergency command confusion, public-good asset enclosure, data misuse, protected knowledge exposure, or Nexus role collapse.

504.1.3 Definitions shall be read as operative governance controls and not merely as drafting conveniences. Each defined term shall carry the restrictions, exclusions, conditions, record requirements, and boundary protections assigned to it by these Bylaws, applicable law, the certificate or articles, Board resolutions, policies, schedules, forms, registers, public-safe materials, technical asset records, and Nexus interface records.

504.2 Definitions as Operative Terms.

504.2.1 Defined terms shall operate as binding interpretive terms throughout these Bylaws unless the context expressly and lawfully requires otherwise.

504.2.2 A defined term shall not be interpreted in isolation. Each defined term shall be read together with all related provisions governing authority, limits, records, approvals, public-safe status, correction, access, confidentiality, role separation, public authority boundaries, finance boundaries, certification and recognition boundaries, procurement neutrality, data / AI / cyber controls, safeguards, protected knowledge, and Nexus coordination.

504.2.3 Where a defined term appears in a policy, schedule, form, public material, repository notice, technical baseline, agreement, dashboard, map, publication, public authority notice, finance-boundary notice, or Nexus interface instrument, it shall carry the meaning assigned by these Bylaws unless a more restrictive approved definition is adopted for that instrument.

504.3 Definitions as Controlled Vocabulary.

504.3.1 Definitions shall form part of the Corporation’s controlled vocabulary.

504.3.2 Terms with public meaning, technical meaning, legal meaning, finance meaning, public authority meaning, certification meaning, recognition meaning, procurement meaning, maturity meaning, Docket meaning, Grid meaning, Nexus-compatible meaning, or public-safe meaning shall be used only in accordance with these Bylaws and approved controlled vocabulary records.

504.3.3 Controlled vocabulary shall be used to prevent semantic drift, overclaim, informal authority creation, sponsor distortion, provider distortion, public authority confusion, public-safe misframing, and misuse of technical outputs.

504.3.4 Where a term becomes ambiguous through practice, public use, partner use, sponsor use, provider use, media use, AI-generated content, repository use, public authority reference, or Nexus interface usage, the Corporation shall clarify, restrict, correct, supersede, or withdraw the term as required.

504.4 Definitions as Claims-Discipline Controls.

504.4.1 Definitions shall control public claims and institutional claims made by or about the Corporation.

504.4.2 No defined term shall be used in a public claim unless the claim is supported by competent records, source lineage, approval records, public-safe review where required, controlled vocabulary review where required, and boundary review where required.

504.4.3 Defined terms shall prevent the unsupported use of terms such as “official,” “approved,” “validated,” “verified,” “recognized,” “certified,” “compliant,” “conformant,” “finance-ready,” “insurance-ready,” “capital-readable,” “bankable,” “investable,” “Nexus-compatible,” “Docket-approved,” “Grid-approved,” “public authority approved,” “public warning,” “emergency command,” “provider-preferred,” and substantially similar terms unless competent authority exists.

504.5 Definitions as Public Authority Boundary Controls.

504.5.1 Definitions shall preserve the Corporation’s public authority boundaries.

504.5.2 Terms concerning public authorities, public officials, public employees, public infrastructure operators, observers, regulator-listening participants, public finance readers, emergency-management participants, public health participants, public safety participants, public works participants, public authority data, public authority rooms, public grants, public records, procurement, public finance, regulatory participation, public warning, and emergency command shall be interpreted to prevent unauthorized public authority meaning.

504.5.3 No defined term shall create or imply public authority status, public authority delegation, official government decision-making, public procurement authority, public finance approval, regulatory approval, public warning authority, emergency command authority, public health order authority, safety command authority, sovereign obligation, or public-private partnership unless a competent public authority record and applicable law expressly provide such meaning.

504.6 Definitions as Finance Boundary Controls.

504.6.1 Definitions shall preserve the Corporation’s finance, securities, insurance, lending, rating, public finance, and capital-reader boundaries.

504.6.2 Terms concerning finance-readiness, capital-readability, insurance-readiness, proof packs, diligence translation, RNFD, NFD, UNFSD, capital-reader rooms, public finance, investment, lending, insurance, ratings, guarantees, public credit, tax credits, grants, and regulated-perimeter matters shall be interpreted consistently with GRA role separation and the Corporation’s non-finance role.

504.6.3 No defined term shall create investment advice, securities offering, securities solicitation, broker-dealer activity, finder activity, placement activity, underwriting, lending, banking, insurance placement, insurance underwriting, claims handling, rating, credit opinion, public finance approval, public guarantee, public credit, or finance-readiness authority for the Corporation.

504.7 Definitions as Certification and Procurement Boundary Controls.

504.7.1 Definitions shall preserve the Corporation’s certification, accreditation, conformance, compliance, procurement, approved-vendor, and provider-preference boundaries.

504.7.2 Terms concerning certification, accreditation, compliance, conformance, approval, procurement, approved vendor status, provider preference, technical baselines, public-good software, test harnesses, benchmarks, Nexus-compatible status, Docket, Grid, recognition, maturity, and standing shall be interpreted to prevent unauthorized approval meaning.

504.7.3 No defined term shall create certification, accreditation, legal compliance approval, procurement approval, approved vendor status, provider preference, GRF recognition, maturity standing, Docket approval, Grid guarantee, or Nexus-compatible status unless competent records from the proper authority provide such meaning.

504.8 Definitions as Nexus Role-Separation Controls.

504.8.1 Definitions shall preserve role separation within the Nexus architecture.

504.8.2 Terms concerning GCRI US, GCRI Canada, other GCRI entities, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Network, Nexus Standards, protocol authorities, Nexus Observatory, Nexus Universe, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, Nexus Competence Cells, consortiums, national companies, Project SPVs, providers, hosts, sponsors, public authorities, and enterprise actors shall be interpreted to preserve legal separateness and functional distinction.

504.8.3 No defined term shall create merger, agency, partnership, joint venture, shared liability, authority to bind another entity, public authority delegation, finance-readiness transfer, recognition transfer, certification transfer, procurement approval, or enterprise execution authority.

504.9 Definitions as Data / AI / Cyber / Privacy Controls.

504.9.1 Definitions shall preserve the Corporation’s data governance, AI governance, cybersecurity, privacy, verifiable compute, verifiable intelligence, proof receipt, repository security, and controlled-room controls.

504.9.2 Terms concerning data, datasets, personal information, rights-bearing data, health-sensitive data, public authority data, cyber-sensitive data, infrastructure-sensitive data, community-protected data, protected knowledge data, model registers, inference records, compute workload records, proof receipts, AI outputs, dashboards, maps, repositories, controlled rooms, clean rooms, data rooms, evidence rooms, public authority rooms, and no-download rooms shall be interpreted according to their classification, authority record, access class, public-safe status, and correction path.

504.9.3 No AI output, automated output, dashboard output, map output, proof receipt, ledger entry, sensor signal, AI-RAN / O-RAN signal, DePIN record, DLT record, digital twin output, model output, or compute output shall be treated as authority merely because it exists or is technically generated.

504.10 Definitions as Safeguards and Protected Knowledge Controls.

504.10.1 Definitions shall preserve civil rights, accessibility, community safeguards, Tribal / Indigenous protocols, local knowledge protections, territorial knowledge protections, cultural knowledge protections, environmental knowledge protections, protected knowledge controls, public-safe mapping controls, consent, non-consent, attribution, withdrawal, restriction, grievance, protected participation, and non-retaliation.

504.10.2 Terms concerning Tribal / Indigenous interfaces, Indigenous data, Indigenous knowledge, community-protected data, local knowledge, territorial knowledge, cultural knowledge, environmental knowledge, ecological knowledge, sacred knowledge, sensitive sites, public-safe mapping, vulnerable communities, and protected knowledge shall be interpreted according to the most protective lawful reading.

504.10.3 No defined term shall convert protected knowledge into public data, research material, AI training material, public dashboard content, map layer, sponsor asset, provider asset, finance-facing evidence, public authority evidence, or transferable technical asset without competent authority and safeguards review.

504.11 Definitions as Validity-by-Record Controls.

504.11.1 Definitions shall implement the validity-by-record doctrine.

504.11.2 A defined status, authority, approval, role, access right, release status, evidence status, method status, public authority status, finance-boundary status, recognition status, certification status, procurement status, Docket status, Grid status, Nexus-compatible status, public-safe status, controlled-room status, technical asset status, or correction status exists only to the extent supported by an Authoritative Record.

504.11.3 Where a defined term is used without a required record, the term shall have no public meaning and shall be corrected, limited, withdrawn, or disregarded as appropriate.

504.12 Definitions as Correctionability Controls.

504.12.1 Definitions shall support correctionability.

504.12.2 Where a defined term is inaccurate, obsolete, overbroad, misleading, boundary-defective, inconsistent with law, inconsistent with role separation, inconsistent with Nexus instruments, inconsistent with public authority records, inconsistent with finance-boundary records, inconsistent with safeguards records, or inconsistent with technical records, the Corporation shall correct, supersede, withdraw, restrict, clarify, or restate the term.

504.12.3 Correction of a defined term may require public-safe notice, controlled notice, repository correction, publication correction, technical asset correction, public authority correction, GRF notice, GRA notice, Nexus interface notice, or archive annotation.

504.13 Definitions Apply Across Bylaw, Policies, Schedules, Forms, Records, Registers, Public Materials, Technical Assets, Agreements, and Nexus Interfaces Unless Otherwise Stated.

504.13.1 Definitions in these Bylaws shall apply across these Bylaws, policies, schedules, forms, records, registers, matrices, protocols, public materials, websites, repositories, publications, dashboards, maps, datasets, software, technical baselines, agreements, contracts, grants, sponsorships, public authority instruments, contributor terms, controlled-room instruments, public-safe notices, archive statements, Nexus interface instruments, and other Corporation instruments unless an instrument expressly adopts a narrower or more restrictive meaning.

504.13.2 A more permissive meaning shall not be inferred from context unless adopted by competent authority and lawful under applicable law, the certificate or articles, these Bylaws, Board resolution, or other competent record.

504.13.3 Translations, summaries, AI summaries, deck text, diagrams, public explainers, repository readme files, marketing materials, and public-facing narratives shall not alter defined terms.

504.14 No Defined Term May Be Used to Expand Authority Beyond Law, Articles, Certificate, This Bylaw, Board Resolution, or Competent Record.

504.14.1 No defined term may be used to expand the Corporation’s authority beyond applicable law, the certificate or articles, these Bylaws, Board resolution, member approval where required, contract authority, public authority record, Nexus interface record, or other competent record.

504.14.2 No defined term may be used to create informal amendment, apparent authority, public authority status, finance authority, certification authority, recognition authority, procurement authority, provider preference, public warning authority, emergency command authority, enterprise execution authority, or authority to bind another entity.

504.14.3 If use of a defined term would create ambiguity about authority, the term shall be read narrowly, accompanied by limitation language where appropriate, or corrected.

504.15 Definitions Records.

504.15.1 The Corporation shall maintain Definitions Records, including definitions purpose records, operative-term records, controlled vocabulary records, claims-discipline records, public authority boundary records, finance boundary records, certification and procurement boundary records, Nexus role-separation records, data / AI / cyber / privacy definition records, safeguards and protected knowledge definition records, validity-by-record definition records, correctionability definition records, cross-instrument application records, no-authority-expansion records, correction records, controlled vocabulary updates, Board interpretations, legal interpretations, and archive records.

---

Section 505. Institutional Definitions

505.1 “GCRI US.”

505.1.1 “GCRI US” means the United States legal entity of The Global Centre for Risk and Innovation operating under these Bylaws as a nonprofit, nonstock, non-share, non-distributing, non-executing, public-benefit, public-good technical institution.

505.1.2 GCRI US functions as an evidence steward, methods steward, observability methods steward, ontology steward, technical truth steward, public-benefit R&D steward, public-good software steward, open technical baseline steward, verifiable compute and verifiable intelligence methods steward, Nexus Truth Engine methods steward, Nexus Observatory methods steward, and public authority learning support institution.

505.1.3 GCRI US does not by default function as a public authority, regulator, procurement authority, finance-readiness authority, certification body, recognition body, provider, operator, national company, Project SPV, fund, lender, insurer, broker, dealer, investment adviser, rating agency, public warning body, emergency command body, or enterprise execution vehicle.

505.2 “The Global Centre for Risk and Innovation - United States.”

505.2.1 “The Global Centre for Risk and Innovation - United States” means the full institutional name or formal descriptive name of GCRI US, subject to the Corporation’s name-use rules, mark controls, legal status records, public-safe communications rules, and jurisdictional records.

505.2.2 Use of the full name shall not imply that GCRI US represents all GCRI entities, governs GCRI Canada, governs other GCRI entities, controls GRF, controls GRA, controls Nexus Network, or speaks for any public authority or Nexus participant unless competent records expressly provide such authority.

505.3 “GCRI Function.”

505.3.1 “GCRI Function” means a public-good technical function associated with The Global Centre for Risk and Innovation family of institutions, including evidence, methods, observability, ontology, technical truth, public-benefit R&D, public-good software, open technical baselines, verifiable compute methods, verifiable intelligence methods, public authority learning support, public-safe publication support, and correctionability.

505.3.2 A GCRI Function does not include GRF recognition functions, GRA finance-readiness functions, public authority functions, certification functions, procurement functions, enterprise execution functions, or regulated finance functions unless a competent record lawfully assigns such function and the assignment is consistent with these Bylaws.

505.4 “GCRI Canada.”

505.4.1 “GCRI Canada” means a Canadian GCRI entity legally separate from GCRI US.

505.4.2 GCRI Canada may coordinate with GCRI US through recorded cross-border, North America, public-good, evidence, methods, observability, technical asset, public authority, data, protected knowledge, or Nexus interfaces.

505.4.3 GCRI Canada does not govern GCRI US, and GCRI US does not govern GCRI Canada, unless a specific lawful instrument creates a limited recorded coordination or authority.

505.5 “Other GCRI Entity.”

505.5.1 “Other GCRI Entity” means any GCRI-affiliated, GCRI-aligned, or GCRI-named entity other than GCRI US or GCRI Canada, whether national, regional, sectoral, project-specific, or otherwise organized.

505.5.2 Other GCRI Entities shall be treated as legally separate unless competent records establish otherwise.

505.5.3 No Other GCRI Entity may bind GCRI US, and GCRI US may not bind any Other GCRI Entity, absent lawful authority and competent records.

505.6 “The Global Risks Forum (GRF).”

505.6.1 “The Global Risks Forum (GRF)” means the separate Nexus public-good institution responsible, within its governing instruments, for public-good registry, recognition, maturity records, standing, claims discipline, stakeholder formation, public-safe reporting, and public-facing legitimacy stewardship.

505.6.2 GRF functions are legally and institutionally distinct from GCRI US technical evidence, methods, ontology, observability, public-good software, and technical truth functions.

505.6.3 No GCRI US record, publication, proof receipt, dashboard, map, technical baseline, software release, public authority learning material, or Nexus interface input shall create GRF recognition meaning without a competent GRF record.

505.7 “The Global Risks Alliance (GRA).”

505.7.1 “The Global Risks Alliance (GRA)” means the separate Nexus institution responsible, within its governing instruments, for capital-readability, finance-readiness, proof packs, insurance-readiness, diligence translation, RNFD, NFD, UNFSD, capital-reader room discipline, and regulated-perimeter finance discipline.

505.7.2 GRA functions are legally and institutionally distinct from GCRI US technical evidence, methods, observability, ontology, public-good software, technical baseline, and public authority learning support functions.

505.7.3 No GCRI US record, publication, dashboard, map, proof receipt, technical baseline, software release, public authority learning material, or Nexus interface input shall create GRA finance-readiness, capital-readability, insurance-readiness, public finance, rating, investment, lending, or capital execution meaning without a competent GRA record and, where required, lawful regulated authority.

505.8 “Nexus Network.”

505.8.1 “Nexus Network” means the permanent public-good infrastructure rail, coordination architecture, or institutional network through which Nexus-aligned public-good functions, evidence flows, methods flows, records, interfaces, observability, public authority learning support, technical assets, standards support, and ecosystem coordination may be structured.

505.8.2 Nexus Network does not mean a single merged legal entity, public authority, finance authority, certification authority, procurement authority, recognition authority, operator, or enterprise execution body.

505.8.3 Participation in Nexus Network shall not create agency, partnership, joint venture, shared liability, merger, or authority to bind another Nexus participant without competent records.

505.9 “Nexus Public-Good Stack.”

505.9.1 “Nexus Public-Good Stack” means the set of Nexus-aligned institutions, roles, instruments, records, methods, public-safe publications, technical assets, observability functions, public authority learning functions, recognition functions, finance-readiness translation functions, standards-support functions, and safeguards functions that operate for public-benefit and public-good purposes without enterprise execution by default.

505.9.2 GCRI US is positioned in the Nexus Public-Good Stack as a technical evidence, methods, observability, ontology, technical truth, public-good software, and technical baseline steward.

505.9.3 The Nexus Public-Good Stack shall remain distinct from the Nexus Enterprise Stack.

505.10 “Nexus Enterprise Stack.”

505.10.1 “Nexus Enterprise Stack” means the set of execution-side, investible, operational, commercial, project, provider, host, asset-owner, national company, state operating company, regional company, Project SPV, fund, lender, insurer, operator, contractor, or enterprise-facing actors and instruments that may implement, finance, operate, procure, or execute projects where lawfully structured.

505.10.2 GCRI US shall not be treated as a Nexus Enterprise Stack actor merely because its public-good outputs inform, support, or are used by enterprise stack actors.

505.10.3 Enterprise Stack participation shall not create GCRI US endorsement, certification, recognition, procurement approval, finance-readiness, provider preference, public authority adoption, public warning, or emergency command meaning.

505.11 “Nexus Standards.”

505.11.1 “Nexus Standards” means Nexus-aligned standards, standards-support instruments, technical profiles, protocol specifications, reference frameworks, interoperability requirements, schemas, tests, baselines, or similar instruments adopted or maintained by a competent Nexus Standards body or protocol authority.

505.11.2 GCRI US may provide evidence, methods, technical baselines, reference implementations, test harnesses, schemas, profiles, benchmark support, and correction signals to Nexus Standards processes without becoming the standards authority by default.

505.11.3 Nexus Standards do not create certification, procurement approval, legal compliance approval, provider preference, public authority adoption, finance-readiness, recognition, rating, public warning, or emergency command by mere reference.

505.12 “Protocol Authority.”

505.12.1 “Protocol Authority” means a competent body or recorded authority responsible for adopting, maintaining, interpreting, versioning, correcting, or retiring protocol specifications, role keys, smart licenses, ledger references, proof receipt profiles, interoperability profiles, or other protocol instruments within a defined scope.

505.12.2 GCRI US is not a Protocol Authority unless separately and lawfully designated by competent record.

505.12.3 A reference implementation, technical baseline, method, schema, API, SDK, or test harness prepared by GCRI US shall not itself create Protocol Authority.

505.13 “Nexus Observatory.”

505.13.1 “Nexus Observatory” means the Nexus-aligned observability institution, framework, or operating architecture for structured sensing, evidence gathering, observability methods, nodes, hubs, clusters, hotspots, regional clusters, national dense Nexus cores, dashboards, maps, public-safe outputs, and degraded-mode awareness.

505.13.2 GCRI US may support Nexus Observatory methods, ontology, technical baselines, public-safe mapping methods, dashboard methods, and evidence records.

505.13.3 Nexus Observatory outputs shall not be public warnings, emergency commands, public authority decisions, finance-readiness determinations, certifications, procurement approvals, recognitions, ratings, or provider preferences unless competent external authority separately provides such meaning.

505.14 “Nexus Universe.”

505.14.1 “Nexus Universe” means the annual or periodic Nexus operating arena, controlled build environment, live operation learning environment, simulation environment, benchmarking environment, Academy lab environment, public authority learning environment, and public-safe demonstration environment for Nexus-aligned work.

505.14.2 GCRI US may support Nexus Universe through evidence, methods, technical after-action review, public-good software, technical baselines, public-safe publication, public authority learning, and records.

505.14.3 Nexus Universe activities do not create public authority delegation, public warning, emergency command, procurement approval, finance-readiness, certification, recognition, provider preference, or enterprise execution by GCRI US.

505.15 “Nexus Risk Management.”

505.15.1 “Nexus Risk Management” means the Nexus-aligned function or institution concerned with risk governance, risk registers, issue registers, control registers, systemic risk, resilience, safeguards, escalation, boundary controls, assurance, monitoring, evaluation, corrective action, and public-safe risk discipline.

505.15.2 GCRI US may provide evidence, methods, observability, technical records, public-good software, and correction signals to Nexus Risk Management interfaces without assuming enterprise risk transfer, insurance, rating, public authority, or command functions.

505.16 “Nexus Rails.”

505.16.1 “Nexus Rails” means the Nexus-aligned rails, pathways, public-good-to-enterprise interfaces, finance translation interfaces, evidence-routing interfaces, proof-pack interfaces, public authority learning interfaces, capital-reader interfaces, or other structured pathways by which records, methods, technical assets, and public-good outputs may move across authorized interfaces.

505.16.2 Nexus Rails shall not be interpreted as regulated finance activity, securities activity, public finance approval, procurement approval, public authority decision, or enterprise execution by GCRI US.

505.17 “Nexus Grid.”

505.17.1 “Nexus Grid” means a Nexus-aligned grid, maturity, routing, standing, eligibility, or coordination interface maintained by the proper Nexus authority.

505.17.2 GCRI US may provide technical evidence, methods, public-good software, technical baselines, observability records, and correction signals as inputs to Nexus Grid where authorized.

505.17.3 GCRI US does not itself create Grid approval, Grid guarantee, Grid routing, maturity standing, eligibility, procurement approval, recognition, finance-readiness, or public authority approval unless competent authority expressly provides otherwise.

505.18 “Nexus Academy.”

505.18.1 “Nexus Academy” means the Nexus-aligned learning, training, workforce, fellowship, curriculum, lab, credential-support, or educational interface.

505.18.2 GCRI US may provide evidence, methods, technical baselines, public-good software, public authority learning materials, public-safe publication materials, and technical content to Nexus Academy.

505.18.3 GCRI US does not issue Nexus Academy credentials, professional licenses, public authority qualifications, certifications, procurement eligibility, or finance-readiness determinations unless separately and lawfully authorized.

505.19 “Nexus Competence Cells.”

505.19.1 “Nexus Competence Cells” means specialized teams, cells, groups, or units organized around technical, sectoral, geographic, public authority, safeguards, data, AI, cyber, observability, software, standards-support, or public-good implementation support functions.

505.19.2 Nexus Competence Cells may interface with GCRI US through recorded authority, scope, role separation, confidentiality, data controls, public authority boundary controls, finance-boundary controls, safeguards, and correction paths.

505.19.3 Competence Cell participation does not create GCRI US enterprise execution, certification, recognition, finance-readiness, procurement approval, provider preference, public authority decision, public warning, or emergency command.

505.20 “Nexus Docket.”

505.20.1 “Nexus Docket” means a record-based intake, routing, tracking, case, proof, issue, project, method, evidence, or maturity-related docket maintained by a competent Nexus authority or instrument.

505.20.2 GCRI US may provide evidence, methods, technical inputs, correction signals, public-good software records, technical baseline records, or observability records to the Nexus Docket where authorized.

505.20.3 Docket inclusion, Docket record creation, Docket input, or Docket reference does not create GCRI US approval, GRF recognition, GRA finance-readiness, certification, procurement approval, public authority approval, provider preference, public warning, or emergency command.

505.21 “National Nexus Financing for Development (NFD).”

505.21.1 “National Nexus Financing for Development (NFD)” means a national-level Nexus finance-readiness, capital-readability, diligence translation, public-good-to-capital interface, or development-finance-related framework operated or stewarded by the appropriate GRA or Nexus finance authority.

505.21.2 GCRI US may support NFD through technical evidence, methods, observability, ontology, public-good software, technical baselines, public-safe records, and correction signals.

505.21.3 GCRI US does not make NFD finance-readiness determinations, investment decisions, lending decisions, insurance decisions, ratings, public finance approvals, or capital commitments.

505.22 “Regional Nexus Financing for Development (RNFD).”

505.22.1 “Regional Nexus Financing for Development (RNFD)” means a regional-level Nexus finance-readiness, capital-readability, diligence translation, resilience-finance, public-good-to-capital, or development-finance-related framework operated or stewarded by the appropriate GRA or Nexus finance authority.

505.22.2 GCRI US may support RNFD only within its technical evidence and methods role.

505.22.3 RNFD references shall not imply GCRI US finance authority, public finance approval, investment advice, rating, or capital execution.

505.23 “Universal Nexus Financing for Sustainable Development (UNFSD).”

505.23.1 “Universal Nexus Financing for Sustainable Development (UNFSD)” means a universal or global Nexus finance-readiness, sustainable development, capital-readability, diligence translation, public-good-to-capital, or development-finance-related framework operated or stewarded by the appropriate GRA or Nexus finance authority.

505.23.2 GCRI US may support UNFSD by providing technical evidence, methods, public-good software, technical baselines, and correction signals without entering regulated finance activity.

505.24 “Global Nexus Consortium.”

505.24.1 “Global Nexus Consortium” means a global consortium, council, alliance, or coordination body structured for Nexus public-good coordination across countries, regions, sectors, institutions, public authorities, enterprise actors, universities, laboratories, communities, and civil society.

505.24.2 Participation in a Global Nexus Consortium shall not create merger, agency, partnership, joint venture, shared liability, public authority delegation, finance-readiness, certification, recognition, procurement approval, provider preference, or enterprise execution by GCRI US.

505.25 “Regional Nexus Consortium.”

505.25.1 “Regional Nexus Consortium” means a regional Nexus coordination body, consortium, forum, or interface organized across a region, cross-border area, macro-region, or sectoral geography.

505.25.2 Regional Nexus Consortium interfaces shall preserve legal separateness, local law, cross-border data controls, public authority boundaries, protected knowledge controls, and public-good stack / enterprise stack separation.

505.26 “National Nexus Consortium.”

505.26.1 “National Nexus Consortium” means a national Nexus public-good consortium, national coordination body, national public-good interface, or national stakeholder formation structure.

505.26.2 National Nexus Consortiums may interface with GCRI US for evidence, methods, observability, public authority learning, public-good software, technical baselines, and technical records.

505.26.3 National Nexus Consortium participation does not make GCRI US a national company, public authority, procurement authority, finance authority, or enterprise execution vehicle.

505.27 “State Nexus Interface.”

505.27.1 “State Nexus Interface” means a state-level Nexus coordination, public authority, public-good, technical, observability, community, university, infrastructure, or implementation-support interface.

505.27.2 State Nexus Interfaces shall be governed by capacity classification, public authority boundary rules, state law localization, public records considerations, data controls, and public-safe publication controls.

505.28 “Territorial Nexus Interface.”

505.28.1 “Territorial Nexus Interface” means a territorial-level Nexus coordination, public authority, public-good, technical, observability, community, infrastructure, disaster, climate, health, or public-safe interface.

505.28.2 Territorial Nexus Interfaces shall preserve local law, territorial public authority boundaries, language access, accessibility, protected knowledge, public-safe mapping, and data / AI / cyber controls.

505.29 “Tribal / Indigenous Nexus Interface.”

505.29.1 “Tribal / Indigenous Nexus Interface” means a Nexus interface involving Tribal governments, Indigenous governments, Indigenous communities, Indigenous institutions, Indigenous data, Indigenous knowledge, local knowledge, cultural knowledge, environmental knowledge, sacred knowledge, sensitive sites, or related public authority and community protocols.

505.29.2 Tribal / Indigenous Nexus Interfaces require lawful and respectful structuring, safeguards review, permission records, consent or non-consent records where applicable, attribution or non-attribution records, public-safe mapping review, protected knowledge controls, and grievance pathways.

505.29.3 No Tribal / Indigenous Nexus Interface shall be inferred from attendance, public availability of information, informal discussion, third-party data, or technical accessibility.

505.30 “Local Nexus Interface.”

505.30.1 “Local Nexus Interface” means a local, county, municipal, metropolitan, community, utility, port, public health, emergency management, public safety, public works, infrastructure, university, civil society, or place-based Nexus interface.

505.30.2 Local Nexus Interfaces shall preserve public authority boundary rules, public-safe mapping, community safeguards, accessibility, civil rights, local knowledge protections, and no public warning or emergency command authority by GCRI US.

505.31 “National Company.”

505.31.1 “National Company” means a national-level enterprise stack entity, company, vehicle, implementation company, or execution-side organization structured to support or implement Nexus-aligned projects, operations, services, or investible activities where lawfully organized.

505.31.2 A National Company is legally distinct from GCRI US unless competent records expressly provide otherwise.

505.31.3 GCRI US does not become a National Company by providing technical evidence, methods, public-good software, public authority learning, or technical baseline support.

505.32 “State Operating Company.”

505.32.1 “State Operating Company” means a state-level enterprise stack company or operating vehicle organized for implementation, service delivery, operations, asset support, project support, or other execution-side functions.

505.32.2 GCRI US shall remain legally and functionally distinct from any State Operating Company.

505.32.3 State Operating Company references shall not imply public authority adoption, procurement approval, provider preference, certification, recognition, finance-readiness, or GCRI US execution.

505.33 “Regional Company.”

505.33.1 “Regional Company” means a regional enterprise stack company or operating vehicle organized for implementation, service delivery, operations, asset support, project support, or other execution-side functions across a region.

505.33.2 A Regional Company is not GCRI US and shall not be treated as holding GCRI US authority without competent record.

505.34 “Project SPV.”

505.34.1 “Project SPV” means a special purpose vehicle, project company, project entity, implementation vehicle, finance vehicle, asset vehicle, or other enterprise stack entity organized for a specific project or set of projects.

505.34.2 Project SPVs may receive or use public-good evidence, methods, technical baselines, or proof-pack inputs through proper interfaces, but such use does not create GCRI US execution, endorsement, certification, recognition, procurement approval, public authority approval, finance-readiness, or provider preference.

505.34.3 GCRI US shall not be liable for a Project SPV merely because GCRI US provided public-good technical support, unless a lawful written instrument expressly creates an obligation.

505.35 “Qualified Enterprise Provider.”

505.35.1 “Qualified Enterprise Provider” means a provider, vendor, operator, implementer, technology company, service provider, infrastructure provider, software provider, cloud provider, AI provider, cybersecurity provider, telecommunications provider, engineering provider, or other enterprise actor that meets criteria established by an appropriate enterprise stack, procurement, standards, or other competent authority.

505.35.2 GCRI US does not by default qualify, approve, certify, rank, prefer, recognize, or procure Qualified Enterprise Providers.

505.35.3 Any reference to a Qualified Enterprise Provider shall be subject to provider neutrality, public-safe claims, public authority boundaries, procurement neutrality, finance-boundary review, and records.

505.36 “Host.”

505.36.1 “Host” means a person or entity that provides venue, infrastructure, data environment, cloud environment, compute environment, repository environment, public authority interface, event setting, controlled room, community setting, technical environment, or other hosting support.

505.36.2 Host status does not create control, endorsement, public authority approval, procurement advantage, certification, recognition, finance-readiness, provider preference, or authority to direct Corporation outputs.

505.36.3 Host relationships shall be recorded and reviewed for data, AI, cyber, privacy, public authority, safeguards, conflict, sponsorship, and public-safe publication implications.

505.37 “Sponsor.”

505.37.1 “Sponsor” means a person or entity providing funding, support, sponsorship, in-kind resources, cloud credits, compute credits, software credits, event support, program support, technical support, or other resources to the Corporation or a Corporation-related activity.

505.37.2 Sponsor status does not create control over evidence, methods, findings, publications, corrections, public authority access, technical baselines, software, recognition-related inputs, finance-readiness inputs, certification meaning, provider status, procurement outcomes, or Nexus interface meaning.

505.37.3 Sponsor references shall be accurate, proportionate, recorded, public-safe, and subject to sponsor non-control.

505.38 “Public Authority.”

505.38.1 “Public Authority” means any federal, state, District of Columbia, territorial, Tribal / Indigenous government where lawfully and respectfully engaged, local, county, municipal, metropolitan, public health, emergency management, public safety, public works, public infrastructure, utility, port, airport, transit, transportation, water, energy, food, telecom, cyber, environmental, housing, education, research, health-system, public finance, budget, treasury, grant, procurement, regulatory, inspector general, legislative, judicial, or oversight authority or public-sector body.

505.38.2 Public Authority includes public officials, public employees, public institutions, public infrastructure operators, public universities, public laboratories, regulators, public finance readers, emergency management personnel, public health personnel, public safety personnel, and public works personnel when acting within relevant public-sector contexts.

505.38.3 Public Authority participation in the Corporation’s activities shall be classified by capacity and shall not imply endorsement, adoption, funding approval, procurement approval, public finance approval, regulatory approval, public warning, emergency command, sovereign obligation, public-private partnership, or public authority decision unless competent records expressly provide such meaning.

505.39 Institutional Definition Records.

505.39.1 The Corporation shall maintain Institutional Definition Records, including GCRI US definition records, The Global Centre for Risk and Innovation - United States definition records, GCRI Function records, GCRI Canada records, Other GCRI Entity records, GRF definition records, GRA definition records, Nexus Network records, Nexus Public-Good Stack records, Nexus Enterprise Stack records, Nexus Standards records, Protocol Authority records, Nexus Observatory records, Nexus Universe records, Nexus Risk Management records, Nexus Rails records, Nexus Grid records, Nexus Academy records, Nexus Competence Cells records, Nexus Docket records, NFD records, RNFD records, UNFSD records, Global Nexus Consortium records, Regional Nexus Consortium records, National Nexus Consortium records, State Nexus Interface records, Territorial Nexus Interface records, Tribal / Indigenous Nexus Interface records, Local Nexus Interface records, National Company records, State Operating Company records, Regional Company records, Project SPV records, Qualified Enterprise Provider records, Host records, Sponsor records, Public Authority records, correction records, controlled vocabulary records, and archive records.

---

Section 506. Governance Definitions

506.1 “Board.”

506.1.1 “Board” means the Board of Directors of the Corporation, as constituted under applicable law, the certificate or articles, these Bylaws, and competent governance records.

506.1.2 The Board is the Corporation’s governing body and holds the powers, duties, oversight responsibilities, reserved matters, fiduciary responsibilities, amendment authority, dissolution authority, and other authority assigned by law, the certificate or articles, and these Bylaws.

506.2 “Director.”

506.2.1 “Director” means an individual lawfully elected, appointed, designated, or otherwise seated as a member of the Board according to applicable law, the certificate or articles, these Bylaws, and Board records.

506.2.2 A Director owes the duties required by law and these Bylaws and shall comply with conflicts, confidentiality, records, public authority boundary, finance-boundary, data / AI / cyber, safeguards, and non-retaliation obligations.

506.3 “Officer.”

506.3.1 “Officer” means an individual appointed or elected to an officer role of the Corporation according to applicable law, the certificate or articles, these Bylaws, Board resolution, or competent authority record.

506.3.2 Officer authority exists only to the extent recorded and shall be subject to the Authority Matrix, Delegation records, Board oversight, reserved matters, conflicts rules, records duties, and legal limits.

506.4 “Principal Officer.”

506.4.1 “Principal Officer” means the officer designated by the Board or applicable law as the primary executive, administrative, or accountable officer for the Corporation or for a legally required filing, record, notice, or operational function.

506.4.2 Principal Officer status does not create authority beyond the office, delegation, Board resolution, or legal requirement defining that status.

506.5 “Executive Leadership.”

506.5.1 “Executive Leadership” means the officers, senior staff, executives, or other persons designated by the Board or Principal Officer to support management of the Corporation.

506.5.2 Executive Leadership may support implementation but shall not exercise Board reserved powers, amendment authority, dissolution authority, public authority status, finance-readiness authority, recognition authority, certification authority, procurement authority, or enterprise execution authority unless lawfully authorized.

506.6 “Secretary.”

506.6.1 “Secretary” means the officer or designated person responsible for corporate records, minutes, notices, certifications, governance records, official repository coordination, and other duties assigned by law, the certificate or articles, these Bylaws, or Board resolution.

506.6.2 Secretary certification shall certify record status only within recorded authority and shall not create substantive authority, public authority meaning, finance-readiness, recognition, certification, procurement approval, or public warning meaning.

506.7 “Treasurer.”

506.7.1 “Treasurer” means the officer or designated person responsible for financial records, budgets, accounts, fiscal controls, tax records, restricted fund records, grant financial records, financial reporting, and related duties assigned by law, the certificate or articles, these Bylaws, or Board resolution.

506.7.2 Treasurer authority shall be subject to financial controls, Board oversight, spending authority, conflicts rules, restricted fund rules, grant rules, and records requirements.

506.8 “Chair.”

506.8.1 “Chair” means the Director or officer designated to chair the Board or another body according to these Bylaws, Board resolution, or charter.

506.8.2 Chair status does not create unilateral authority to amend Bylaws, dissolve the Corporation, approve reserved matters, bind the Corporation beyond delegated authority, or speak publicly beyond approved authority.

506.9 “Vice-Chair.”

506.9.1 “Vice-Chair” means the Director or officer designated to support or substitute for the Chair within the scope authorized by these Bylaws, Board resolution, or charter.

506.9.2 Vice-Chair authority shall be limited to recorded authority.

506.10 “President.”

506.10.1 “President” means an officer title that may be used for the Corporation’s executive, institutional, or administrative leadership role if adopted by Board record.

506.10.2 President authority shall be defined by Board resolution, officer appointment record, Authority Matrix, employment or service agreement where applicable, and these Bylaws.

506.11 “Executive Director.”

506.11.1 “Executive Director” means an officer or senior executive role responsible for day-to-day management, implementation, public-benefit program coordination, staff supervision, external coordination, or other functions assigned by Board record.

506.11.2 Executive Director authority shall not include Board reserved matters unless expressly delegated and lawful.

506.12 “Chief Executive Officer.”

506.12.1 “Chief Executive Officer” means an officer title that may be used where the Board designates a chief executive role.

506.12.2 Chief Executive Officer authority shall be recorded and shall not create public authority status, finance-readiness authority, certification authority, recognition authority, procurement authority, or enterprise execution authority.

506.13 “Committee.”

506.13.1 “Committee” means a body created by the Board or other competent authority to perform governance, oversight, advisory, review, implementation, assurance, or other functions within a recorded scope.

506.13.2 Committee authority shall be defined by charter, Board resolution, these Bylaws, or applicable law and shall not exceed recorded authority.

506.14 “Standing Committee.”

506.14.1 “Standing Committee” means a committee intended to continue for an ongoing governance or oversight function until dissolved, amended, or superseded.

506.14.2 Standing Committees may address governance, finance, audit, compliance, risk, research integrity, data / AI / cyber, safeguards, publication, technical assets, public authority boundaries, Nexus coordination, or other recurring matters.

506.15 “Special Committee.”

506.15.1 “Special Committee” means a committee created for a limited purpose, time, matter, investigation, project, transaction, amendment, wind-up, assurance review, conflict review, or other defined task.

506.15.2 A Special Committee shall terminate or be reviewed according to its charter or Board record.

506.16 “Executive Committee.”

506.16.1 “Executive Committee” means a committee authorized by the Board, if permitted by law and these Bylaws, to act on specified matters between Board meetings.

506.16.2 Executive Committee authority shall be limited by law, Board reserved matters, these Bylaws, the committee charter, and records.

506.16.3 An Executive Committee shall not amend Bylaws, dissolve the Corporation, approve nondelegable matters, or act contrary to Board instructions unless lawfully authorized.

506.17 “Council.”

506.17.1 “Council” means a governance-adjacent, advisory, coordination, technical, public-good, public authority learning, stakeholder, safeguards, or Nexus interface body created or recognized by competent record.

506.17.2 A Council shall have only the authority expressly assigned by its charter or record and shall not be presumed to govern the Corporation.

506.18 “Leadership Council.”

506.18.1 “Leadership Council” means a Council composed of leaders, officers, directors, advisors, institutional representatives, technical experts, public-good representatives, or other persons designated to support strategy, coordination, review, or advisory functions.

506.18.2 Leadership Council participation does not create Board authority, officer authority, public authority approval, finance-readiness, recognition, certification, procurement approval, or provider preference.

506.19 “Helix Council.”

506.19.1 “Helix Council” means a Nexus-aligned or Corporation-recognized council structured to support cross-functional coordination among public-good, technical, institutional, public authority, safeguards, finance-boundary, recognition-boundary, standards-support, and enterprise-interface considerations.

506.19.2 A Helix Council shall not override the Board, GCRI / GRF / GRA role separation, public authority boundaries, finance boundaries, certification boundaries, recognition boundaries, procurement neutrality, or legal separateness.

506.20 “Advisory Forum.”

506.20.1 “Advisory Forum” means an advisory body, forum, roundtable, convening, or group formed to provide non-binding advice, expertise, perspective, review, or feedback.

506.20.2 Advisory Forum participation shall not create authority to bind the Corporation, endorse outputs, approve public authority meaning, approve finance meaning, certify, recognize, procure, or execute.

506.21 “Working Group.”

506.21.1 “Working Group” means a time-limited or continuing group formed to perform drafting, research, technical, review, coordination, public-good, publication, safeguards, or interface work within a defined scope.

506.21.2 Working Group outputs are drafts or recommendations unless adopted by competent authority.

506.22 “Expert Panel.”

506.22.1 “Expert Panel” means a group of persons with technical, legal, governance, sectoral, public authority, community, safeguards, data, AI, cyber, finance-boundary, or other expertise convened for review, advice, evaluation, or challenge.

506.22.2 Expert Panel conclusions shall not be treated as certification, public authority approval, finance-readiness, recognition, procurement approval, rating, public warning, or emergency command unless competent authority separately provides such meaning.

506.23 “Peer Review Panel.”

506.23.1 “Peer Review Panel” means a panel convened to review research, evidence, methods, publications, datasets, technical baselines, software, dashboards, maps, or technical outputs for integrity, quality, limitations, and correction needs.

506.23.2 Peer review supports evidence integrity but does not itself create certification, recognition, finance-readiness, procurement approval, public authority approval, or legal compliance approval.

506.24 “Model Review Panel.”

506.24.1 “Model Review Panel” means a review body convened to review AI systems, models, model cards, system cards, benchmark cards, evaluation harnesses, inference records, compute workload records, proof receipts, bias, safety, hallucination, drift, prompt injection, data leakage, privacy, cybersecurity, and public-safe output risks.

506.24.2 Model Review Panel findings shall be recorded and shall not create public authority decision, finance-readiness, certification, recognition, procurement approval, public warning, or emergency command.

506.25 “Controlled-Room Review Group.”

506.25.1 “Controlled-Room Review Group” means a group assigned to review, approve, monitor, or close out controlled rooms, clean rooms, data rooms, evidence rooms, public authority rooms, no-download rooms, regulator-listening rooms, public finance reader rooms, emergency learning rooms, or other restricted environments.

506.25.2 Controlled-Room Review Group authority shall be limited to its charter and shall preserve data, AI, cyber, privacy, public authority, finance, competition, protected knowledge, public-safe publication, and records controls.

506.26 “Delegation.”

506.26.1 “Delegation” means a recorded grant of authority by the Board, an officer, a committee, or another competent authority to a person or role to perform specified actions within stated limits.

506.26.2 Delegation shall be interpreted narrowly and shall not include reserved matters, amendment authority, dissolution authority, finance-readiness authority, recognition authority, certification authority, procurement authority, public authority status, public warning authority, emergency command authority, or enterprise execution authority unless expressly and lawfully included.

506.27 “Authority Matrix.”

506.27.1 “Authority Matrix” means the recorded instrument identifying who may approve, sign, release, publish, spend, contract, access, correct, restrict, hold, transfer, archive, or otherwise act for the Corporation by role, threshold, matter, risk class, and limitation.

506.27.2 The Authority Matrix implements but does not override these Bylaws.

506.28 “Reserved Matter.”

506.28.1 “Reserved Matter” means a matter reserved to the Board, members where required, or another competent authority by law, the certificate or articles, these Bylaws, Board resolution, policy, contract, grant, or risk classification.

506.28.2 Reserved Matters include, at minimum where applicable, bylaw amendment, dissolution, major asset disposition, major restricted fund action, major public authority boundary issue, major finance-boundary issue, major technical asset disposition, major legal claim, indemnification decision where required, and other matters designated by the Board.

506.29 “Quorum.”

506.29.1 “Quorum” means the minimum number or proportion of Directors, committee members, members where applicable, or other voting participants required to conduct business.

506.29.2 Quorum shall be determined under applicable law, the certificate or articles, these Bylaws, or the applicable charter.

506.30 “Recusal.”

506.30.1 “Recusal” means abstaining from participation in deliberation, decision, vote, access, influence, or approval because of a conflict, related-party interest, legal requirement, confidentiality concern, public authority issue, finance-boundary issue, or other integrity concern.

506.30.2 Recusal shall be recorded where material.

506.31 “Abstention.”

506.31.1 “Abstention” means a decision not to vote while remaining present or recorded for meeting purposes, subject to applicable law and governance rules.

506.31.2 Abstentions shall be recorded where required or material.

506.32 “Written Consent.”

506.32.1 “Written Consent” means action taken without a meeting by written, electronic, or other legally permitted consent according to applicable law, the certificate or articles, these Bylaws, and governance records.

506.32.2 Written Consent shall identify action approved, date, consenting persons, required threshold, and effective date.

506.33 “Emergency Decision.”

506.33.1 “Emergency Decision” means a time-sensitive decision made under emergency or urgent conditions according to authority granted by law, these Bylaws, Board resolution, policy, or recorded delegation.

506.33.2 Emergency Decisions shall be limited to what is necessary, recorded promptly, reviewed or ratified where required, and shall not create unauthorized public authority action, finance activity, certification, recognition, procurement approval, public warning, emergency command, or enterprise execution.

506.34 “Break-Glass Authority.”

506.34.1 “Break-Glass Authority” means narrowly limited emergency authority to take immediate protective action to prevent or mitigate serious harm, legal violation, data breach, cybersecurity incident, public-safe risk, protected knowledge exposure, public authority confusion, finance-boundary violation, repository compromise, or record integrity failure.

506.34.2 Break-Glass Authority may include access restriction, system isolation, credential rotation, publication hold, repository hold, data hold, controlled-room hold, takedown, or escalation.

506.34.3 Break-Glass Authority shall be recorded, reviewed, sunsetted, and ratified where required.

506.35 Governance Definition Records.

506.35.1 The Corporation shall maintain Governance Definition Records, including Board definition records, Director records, Officer records, Principal Officer records, Executive Leadership records, Secretary records, Treasurer records, Chair records, Vice-Chair records, President records, Executive Director records, Chief Executive Officer records, Committee records, Standing Committee records, Special Committee records, Executive Committee records, Council records, Leadership Council records, Helix Council records, Advisory Forum records, Working Group records, Expert Panel records, Peer Review Panel records, Model Review Panel records, Controlled-Room Review Group records, Delegation records, Authority Matrix records, Reserved Matter records, Quorum records, Recusal records, Abstention records, Written Consent records, Emergency Decision records, Break-Glass Authority records, correction records, and archive records.

---

Section 507. Membership, Participation, and Support Definitions

507.1 “Member.”

507.1.1 “Member” means a person or entity having membership status in the Corporation only if such status is created by applicable law, the certificate or articles, these Bylaws, Board resolution, or competent membership record.

507.1.2 Use of “member” in public materials, community materials, program materials, supporter materials, or participation materials shall not create statutory membership, voting rights, governance rights, fiduciary rights, equity rights, distribution rights, or authority to bind the Corporation unless competent records expressly provide such rights.

507.2 “Statutory Member.”

507.2.1 “Statutory Member” means a member having rights under the governing nonprofit corporation statute, the certificate or articles, or these Bylaws.

507.2.2 Statutory Member rights shall exist only to the extent expressly created and recorded.

507.3 “Voting Member.”

507.3.1 “Voting Member” means a member with voting rights on specified matters under applicable law, the certificate or articles, these Bylaws, or competent records.

507.3.2 Voting Member status shall not be inferred from donation, sponsorship, participation, subscription, affiliation, attendance, contribution, public authority status, or support.

507.4 “Non-Voting Member.”

507.4.1 “Non-Voting Member” means a person or entity designated as a member without voting rights, if such class is lawfully created.

507.4.2 Non-Voting Member status shall not confer governance authority unless expressly granted by competent record.

507.5 “Supporter.”

507.5.1 “Supporter” means a person or entity that provides encouragement, participation, contribution, donation, sponsorship, in-kind support, or other support without governance authority.

507.5.2 Supporter status does not confer membership, voting rights, endorsement authority, public authority meaning, finance-readiness, recognition, certification, procurement approval, provider preference, or right to use the Corporation’s name.

507.6 “Subscriber.”

507.6.1 “Subscriber” means a person or entity receiving publications, updates, notices, newsletters, repository updates, public-safe summaries, or other communications from the Corporation.

507.6.2 Subscriber status does not confer membership, participation authority, governance rights, access rights, or endorsement.

507.7 “Affiliate.”

507.7.1 “Affiliate” means a person or entity described as affiliated with the Corporation only where competent records define the relationship.

507.7.2 Affiliate status shall be construed narrowly and shall not create agency, partnership, joint venture, shared liability, authority to bind the Corporation, or institutional merger.

507.8 “Participant.”

507.8.1 “Participant” means any person or entity participating in a program, meeting, room, committee, council, forum, working group, panel, event, research activity, public authority interface, technical activity, repository, training, Academy activity, Nexus interface, or other Corporation-related activity.

507.8.2 Participant status does not create authority to bind the Corporation, approve outputs, make public claims, certify, recognize, determine finance-readiness, approve procurement, issue public warnings, or issue emergency commands.

507.9 “Public Authority Participant.”

507.9.1 “Public Authority Participant” means a Public Authority, public official, public employee, public infrastructure operator, public university representative, public laboratory representative, regulator, public finance reader, emergency-management participant, public health participant, public safety participant, public works participant, or other public-sector participant involved in a Corporation activity.

507.9.2 Public Authority Participant status shall be classified by capacity and shall not imply endorsement, adoption, approval, funding, procurement, regulatory approval, public finance approval, public warning, emergency command, or sovereign obligation.

507.10 “Observer.”

507.10.1 “Observer” means a participant admitted for learning, awareness, listening, or observation without approval authority, adoption authority, endorsement authority, decision authority, public authority decision-making authority, finance authority, certification authority, recognition authority, or procurement authority.

507.10.2 Observer attendance shall not be used as endorsement, adoption, funding approval, procurement approval, regulatory approval, public finance approval, public warning, emergency command, or public authority decision.

507.11 “Regulator-Listening Participant.”

507.11.1 “Regulator-Listening Participant” means a regulator or regulatory staff member participating in a listening, learning, awareness, or information-receiving capacity.

507.11.2 Regulator-Listening participation shall not constitute regulatory guidance, approval, safe harbor, permit, compliance determination, enforcement position, waiver, policy adoption, or public authority endorsement.

507.12 “Public Finance Reader.”

507.12.1 “Public Finance Reader” means a public finance, budget, treasury, grant, public credit, development finance, or public funding participant reviewing materials for learning, literacy, diligence awareness, or public finance understanding.

507.12.2 Public Finance Reader status shall not create grant approval, budget allocation, appropriation, public finance approval, MDB / DFI approval, public guarantee, public credit, tax credit approval, sovereign obligation, capital commitment, investment advice, or GRA finance-readiness determination.

507.13 “Emergency-Management Participant.”

507.13.1 “Emergency-Management Participant” means a public or authorized emergency management person participating in learning, scenario, simulation, tabletop, after-action, public-safe reporting, or resilience literacy activities.

507.13.2 Emergency-Management Participant status shall not create incident command, dispatch authority, evacuation authority, emergency alert authority, official public warning, public health order, safety command, or operational resource direction by the Corporation.

507.14 “Public Infrastructure Operator Participant.”

507.14.1 “Public Infrastructure Operator Participant” means a person or entity operating, managing, or supporting public or publicly regulated infrastructure participating in a Corporation activity.

507.14.2 Such participation shall be subject to infrastructure-sensitive data controls, cyber-sensitive data controls, public authority boundary controls, procurement neutrality, and public-safe publication controls.

507.15 “Controlled-Room Participant.”

507.15.1 “Controlled-Room Participant” means a person admitted to a controlled room, clean room, data room, evidence room, public authority room, no-download room, regulator-listening room, public finance reader room, emergency learning room, or other restricted environment.

507.15.2 Controlled-Room Participant status is limited by room charter, access records, capacity classification, confidentiality, data / AI / cyber restrictions, public authority boundaries, finance boundaries, protected knowledge restrictions, and no-overclaim rules.

507.16 “Advisor.”

507.16.1 “Advisor” means a person appointed, retained, invited, or recognized to provide advice, expertise, perspective, review, or counsel to the Corporation.

507.16.2 Advisor status does not create authority to bind the Corporation or approve outputs unless expressly delegated by competent record.

507.17 “Fellow.”

507.17.1 “Fellow” means a person participating in a fellowship, research, technical, policy, public-good, training, Academy, or Nexus-related program of the Corporation.

507.17.2 Fellow status shall be subject to role records, confidentiality, IP, data, AI, cyber, publication, safeguards, and public claims rules.

507.18 “Volunteer.”

507.18.1 “Volunteer” means a person providing services without compensation or with limited reimbursement, according to applicable law and Corporation records.

507.18.2 Volunteer status does not create employment, officer status, agency, public authority status, or authority to bind the Corporation unless competent records provide otherwise.

507.19 “Contributor.”

507.19.1 “Contributor” means a person or entity contributing content, code, data, documentation, review, research, methods, technical assets, public-safe materials, or other work product to the Corporation or its repositories.

507.19.2 Contributor rights and duties shall be governed by contributor terms, licenses, assignments, confidentiality rules, data restrictions, AI-use restrictions, public-safe claims rules, and records.

507.20 “Technical Contributor.”

507.20.1 “Technical Contributor” means a Contributor contributing software, code, schemas, APIs, SDKs, profiles, datasets, models, test harnesses, benchmarks, documentation, infrastructure, cybersecurity materials, or technical methods.

507.20.2 Technical Contributors shall comply with secure development, repository governance, IP, license, data, AI, cyber, secrets, export-control, controlled technology, public-safe release, and no-overclaim requirements.

507.21 “Developer.”

507.21.1 “Developer” means a person contributing to software, systems, code, repositories, APIs, SDKs, models, automation, infrastructure, or technical assets.

507.21.2 Developer status does not create maintainer authority, release authority, repository owner authority, publication authority, or institutional authority unless recorded.

507.22 “Maintainer.”

507.22.1 “Maintainer” means a person authorized to maintain a repository, software project, dataset, technical baseline, schema, API, SDK, profile, documentation set, or technical asset.

507.22.2 Maintainer authority shall be defined by repository records and shall not include authority to alter institutional meaning, certify, recognize, determine finance-readiness, approve procurement, or issue public authority claims.

507.23 “Reviewer.”

507.23.1 “Reviewer” means a person assigned to review records, research, evidence, methods, publications, public claims, data, AI systems, cybersecurity controls, technical assets, repositories, public authority references, finance-boundary statements, safeguards, or Nexus interface materials.

507.23.2 Reviewer findings are advisory or review records unless approval authority is separately recorded.

507.24 “Public-Good Support.”

507.24.1 “Public-Good Support” means financial, in-kind, technical, infrastructure, data, cloud, compute, software, hosting, professional, volunteer, institutional, or other support provided to advance the Corporation’s public-benefit and public-good purposes.

507.24.2 Public-Good Support shall be support-without-control unless a lawful and recorded restriction applies.

507.25 “Donation.”

507.25.1 “Donation” means a voluntary contribution to the Corporation without exchange for equivalent value, subject to applicable law, donor restrictions where accepted, tax rules, records, and public-benefit use.

507.25.2 Donation does not create control, membership, endorsement, recognition, finance-readiness, certification, procurement advantage, or public authority access.

507.26 “Grant.”

507.26.1 “Grant” means a financial or in-kind award, contribution, cooperative agreement, subaward, public grant, private grant, research grant, or similar support subject to grant terms, restrictions, reporting, allowable use, and records.

507.26.2 Grant terms may define scope but shall not control evidence, methods, findings, corrections, public-safe publications, recognition, finance-readiness, certification, procurement neutrality, or provider status beyond lawful and recorded terms.

507.27 “Sponsorship.”

507.27.1 “Sponsorship” means support provided in exchange for acknowledgment, participation, visibility, or other limited benefits consistent with law and the Corporation’s public-benefit purpose.

507.27.2 Sponsorship shall not create sponsor control, public authority access, provider preference, procurement advantage, finance-readiness, recognition, certification, or outcome purchase.

507.28 “In-Kind Contribution.”

507.28.1 “In-Kind Contribution” means non-cash support, including services, equipment, cloud credits, compute credits, software credits, data access, venue support, professional support, technical support, repository support, or other non-monetary resources.

507.28.2 In-Kind Contributions shall be reviewed for value where required, restrictions, conflicts, data / AI / cyber risks, provider dependency, sponsor control, and public-benefit compatibility.

507.29 “Restricted Fund.”

507.29.1 “Restricted Fund” means money or assets restricted by donor, grantor, law, public authority instrument, contract, Board designation, or other competent record for a specified purpose, time, program, project, geography, or use.

507.29.2 Restricted Funds shall be used, tracked, reported, reallocated, returned, or closed out according to applicable restrictions and law.

507.30 “Unrestricted Support.”

507.30.1 “Unrestricted Support” means support received without donor, grantor, sponsor, contract, or legal restriction beyond general public-benefit use and applicable law.

507.30.2 Unrestricted Support remains subject to nonprofit purpose, private inurement prohibitions, private benefit restrictions, fiscal controls, and Board oversight.

507.31 “Fee.”

507.31.1 “Fee” means an amount charged for lawful services, events, materials, training, access, participation, cost recovery, technical support, publication, or other activity consistent with the Corporation’s nonprofit purpose.

507.31.2 Fees shall not create equity, membership rights, public authority status, certification, recognition, finance-readiness, procurement approval, or provider preference unless competent records expressly provide a lawful limited meaning.

507.32 “Cost Recovery.”

507.32.1 “Cost Recovery” means charges, reimbursements, fees, or contributions intended to recover reasonable costs of activities, programs, events, publications, technical assets, controlled rooms, data processing, public authority learning support, or other lawful functions.

507.32.2 Cost Recovery shall not be used to distribute profits, create private inurement, sell outcomes, or create sponsor or provider control.

507.33 “Sponsored Seat.”

507.33.1 “Sponsored Seat” means participation support funded by a sponsor, donor, funder, host, public-good support provider, or other contributor for a participant, fellow, advisor, learner, public authority participant, community participant, or other person.

507.33.2 A Sponsored Seat shall not create sponsor control over participant views, evidence, methods, findings, publication, public authority access, recognition, finance-readiness, certification, procurement, or outcomes.

507.34 “Support-Without-Control.”

507.34.1 “Support-Without-Control” means the principle that donations, grants, sponsorships, in-kind contributions, cloud credits, compute credits, software credits, hosted resources, public-good support, or other support may assist the Corporation’s public-benefit mission but shall not control institutional judgment, evidence, methods, findings, public-safe publication, correction, public authority access, technical baseline status, software status, provider status, recognition, finance-readiness, certification, procurement outcomes, or Nexus interface meaning.

507.34.2 Support-Without-Control is a mandatory interpretive principle for all support relationships.

507.35 Membership, Participation, and Support Definition Records.

507.35.1 The Corporation shall maintain Membership, Participation, and Support Definition Records, including Member records, Statutory Member records, Voting Member records, Non-Voting Member records, Supporter records, Subscriber records, Affiliate records, Participant records, Public Authority Participant records, Observer records, Regulator-Listening Participant records, Public Finance Reader records, Emergency-Management Participant records, Public Infrastructure Operator Participant records, Controlled-Room Participant records, Advisor records, Fellow records, Volunteer records, Contributor records, Technical Contributor records, Developer records, Maintainer records, Reviewer records, Public-Good Support records, Donation records, Grant records, Sponsorship records, In-Kind Contribution records, Restricted Fund records, Unrestricted Support records, Fee records, Cost Recovery records, Sponsored Seat records, Support-Without-Control records, correction records, and archive records.

---

Section 508. Public-Benefit and Nonprofit Definitions

508.1 “Public-Benefit Purpose.”

508.1.1 “Public-Benefit Purpose” means the Corporation’s lawful purpose to advance public benefit through evidence, methods, observability, ontology, technical truth, public-good R&D, public-good software, open technical baselines, verifiable compute and verifiable intelligence methods, public authority learning support, public-safe publication, safeguards, protected knowledge controls, correctionability, and Nexus public-good coordination.

508.1.2 Public-Benefit Purpose shall be interpreted to exclude private inurement, impermissible private benefit, sponsor capture, provider capture, enterprise capture, public authority capture, public-good asset enclosure, and unauthorized regulated activity.

508.2 “Public-Good Purpose.”

508.2.1 “Public-Good Purpose” means a purpose directed toward shared public benefit, systemic risk literacy, resilience, public-safe evidence, public-good technical infrastructure, interoperable methods, public authority learning, community safeguards, open technical baselines, public-good software, and technical memory.

508.2.2 Public-Good Purpose does not mean unrestricted public disclosure of all materials. Public-good work may require controlled access, restricted rooms, confidentiality, privacy, cybersecurity protections, public authority restrictions, protected knowledge safeguards, or delayed publication.

508.3 “Public-Good Technical Institution.”

508.3.1 “Public-Good Technical Institution” means a nonprofit or public-benefit institution that develops, stewards, documents, reviews, publishes, corrects, and maintains technical evidence, methods, software, baselines, ontologies, records, observability tools, and public-safe technical outputs for public-good purposes.

508.3.2 A Public-Good Technical Institution is not by that status a public authority, regulator, certifier, rating agency, procurement authority, finance authority, provider, operator, or enterprise execution vehicle.

508.4 “Nonprofit Character.”

508.4.1 “Nonprofit Character” means the Corporation’s legal and institutional character as a nonstock, non-share, non-distributing organization organized and operated for public-benefit purposes rather than private ownership or profit distribution.

508.4.2 Nonprofit Character shall govern interpretation of revenue, fees, grants, donations, sponsorships, cost recovery, asset distribution, dissolution, compensation, contracts, and technical asset stewardship.

508.5 “Non-Distribution Principle.”

508.5.1 “Non-Distribution Principle” means that the Corporation shall not distribute net earnings, surplus, assets, technical assets, IP value, or public-good value to private persons except through lawful payment of reasonable compensation, reimbursement, debts, obligations, contracts, indemnification, advancement, settlement, or other lawful amounts.

508.5.2 The Non-Distribution Principle shall survive dissolution and wind-up.

508.6 “No Private Inurement.”

508.6.1 “No Private Inurement” means that no part of the Corporation’s net earnings, assets, restricted funds, public-good technical assets, IP, or institutional value shall inure to the benefit of directors, officers, insiders, founders, members, related parties, sponsors, donors, funders, providers, hosts, contractors, employees, or private persons except as lawfully permitted.

508.6.2 No Private Inurement is mandatory and shall not be waived by Board action, contract, sponsorship, donor preference, provider preference, or Nexus interface.

508.7 “Impermissible Private Benefit.”

508.7.1 “Impermissible Private Benefit” means a non-incidental, unlawful, excessive, or mission-inconsistent benefit to a private person, related party, sponsor, provider, donor, funder, host, contractor, enterprise actor, or other private interest.

508.7.2 Impermissible Private Benefit includes public-good asset enclosure, provider preference, sponsor capture, procurement advantage, private control of evidence or methods, private control of public-safe publication, and restricted fund diversion where unlawful or inconsistent with mission.

508.8 “Excess Benefit.”

508.8.1 “Excess Benefit” means a transaction or arrangement that provides economic benefit to a disqualified, related, insider, or covered person in excess of the value received by the Corporation or otherwise violates applicable tax or nonprofit rules.

508.8.2 Excess Benefit review shall be conducted where required by law, policy, or risk.

508.9 “Tax-Exempt-Compatible.”

508.9.1 “Tax-Exempt-Compatible” means structured, interpreted, and operated in a manner intended to preserve compatibility with applicable tax-exempt or public-benefit tax requirements where the Corporation has, seeks, or maintains such status.

508.9.2 Tax-Exempt-Compatible shall not be used to represent that tax-exempt status has been granted, maintained, or approved unless competent tax records support the statement.

508.10 “Charitable Purpose Where Applicable.”

508.10.1 “Charitable Purpose Where Applicable” means a purpose recognized as charitable under applicable law where the Corporation has adopted, seeks, or maintains charitable status or charitable-compatible activity.

508.10.2 Charitable purpose may include education, science, relief of burdens, community benefit, public-good technical infrastructure, or other lawful charitable purposes where applicable.

508.11 “Scientific Purpose Where Applicable.”

508.11.1 “Scientific Purpose Where Applicable” means a purpose involving systematic research, evidence generation, methods development, technical inquiry, publication, replication where appropriate, public-benefit knowledge production, and public-good technical advancement.

508.11.2 Scientific purpose shall be pursued with research integrity, ethics review where required, evidence discipline, limitation disclosure, uncertainty disclosure, and correctionability.

508.12 “Educational Purpose Where Applicable.”

508.12.1 “Educational Purpose Where Applicable” means a purpose involving public-benefit learning, public authority learning, evidence literacy, technical literacy, AI literacy, cyber literacy, resilience literacy, workforce learning, Academy support, training, public-safe publication, and dissemination of accurate, accessible, non-misleading information.

508.12.2 Educational purpose shall not be used to provide professional advice, public authority decision-making, public warning, emergency command, finance advice, certification, recognition, procurement approval, or legal compliance approval.

508.13 “Public Trust.”

508.13.1 “Public Trust” means the confidence reasonably placed in the Corporation’s integrity, records, public-good mission, role separation, public-safe publication, correctionability, safeguards, and public-benefit stewardship.

508.13.2 Public Trust shall be protected through accuracy, transparency, limitation disclosure, independence, non-execution, sponsor non-control, provider neutrality, public authority boundary discipline, finance-boundary discipline, safeguards, and correction.

508.14 “Public-Safe Transparency.”

508.14.1 “Public-Safe Transparency” means transparency that advances public understanding and accountability while protecting privacy, cybersecurity, infrastructure sensitivity, public authority confidentiality, privilege, protected knowledge, civil rights, community safety, and legal obligations.

508.14.2 Public-Safe Transparency is not unrestricted disclosure and shall not create certification, recognition, finance-readiness, procurement approval, rating, public authority endorsement, public warning, or emergency command.

508.15 “Public-Good Firewall.”

508.15.1 “Public-Good Firewall” means the institutional, governance, records, conflict, funding, publication, role-separation, provider-neutrality, sponsor-non-control, public authority boundary, finance-boundary, data, AI, cyber, safeguards, and correction controls that prevent public-good functions from being captured by private, enterprise, sponsor, provider, public authority, finance, or political control.

508.15.2 The Public-Good Firewall protects evidence independence, methods independence, technical truth, public-safe publication, correctionability, and public trust.

508.16 “Mission Lock.”

508.16.1 “Mission Lock” means the binding interpretation and governance principle that the Corporation’s assets, authority, programs, records, publications, technical assets, revenues, support, and wind-up actions shall remain aligned with public-benefit and public-good purposes.

508.16.2 Mission Lock prohibits drift into private-benefit operation, provider preference, sponsor capture, enterprise execution, public authority substitution, regulated finance activity, certification authority, recognition authority, or procurement authority without lawful and recorded authority.

508.17 “Anti-Capture.”

508.17.1 “Anti-Capture” means the policy and governance principle that the Corporation shall not be controlled, distorted, directed, or functionally captured by sponsors, donors, funders, providers, hosts, enterprise actors, public authorities, political actors, capital actors, insiders, related parties, or any narrow interest inconsistent with public-benefit purpose.

508.17.2 Anti-Capture requires conflicts review, support-without-control, provider neutrality, public authority boundary discipline, finance-boundary discipline, procurement neutrality, public-safe publication, safeguards, independent records, and correctionability.

508.18 “Provider Neutrality.”

508.18.1 “Provider Neutrality” means the principle that the Corporation shall not prefer, approve, certify, rank, endorse, select, procure, or create procurement advantage for providers unless a lawful, recorded, and appropriately authorized process expressly permits a limited action consistent with the Corporation’s role.

508.18.2 Provider Neutrality applies to software providers, AI providers, cloud providers, cybersecurity providers, telecom providers, infrastructure providers, consultants, contractors, hosts, vendors, enterprise providers, national companies, regional companies, Project SPVs, and other enterprise actors.

508.19 “Sponsor Non-Control.”

508.19.1 “Sponsor Non-Control” means that sponsorship or sponsor support shall not control evidence, methods, findings, publication, corrections, public authority access, technical baselines, public-good software, provider status, recognition, finance-readiness, certification, procurement outcomes, public-safe summaries, or Nexus interface meaning.

508.19.2 Sponsor Non-Control shall apply regardless of sponsorship amount, visibility, strategic importance, in-kind contribution, technical dependency, or public authority relationship.

508.20 “Donor Non-Control.”

508.20.1 “Donor Non-Control” means that donations shall not control governance, evidence, methods, findings, publications, corrections, technical assets, public authority access, provider status, recognition, finance-readiness, certification, procurement outcomes, or Nexus interface meaning except for lawful and accepted donor restrictions concerning use of donated assets.

508.20.2 Donor intent may restrict use of funds where lawfully accepted but shall not override the Corporation’s public-benefit purpose or integrity controls.

508.21 “Funder Non-Control.”

508.21.1 “Funder Non-Control” means that funders, grantors, public grantors, cooperative agreement partners, public-good support providers, and other funding sources shall not control evidence, methods, findings, corrections, public-safe publications, public authority access, provider status, recognition, finance-readiness, certification, procurement outcomes, or Nexus interface meaning beyond lawful and recorded scope terms.

508.21.2 Funder reporting requirements shall not be interpreted as control over technical truth or institutional meaning.

508.22 “Host Non-Control.”

508.22.1 “Host Non-Control” means that a host providing venue, infrastructure, cloud, compute, repository, data room, event space, public authority interface, technical environment, or other hosting support shall not control the Corporation’s governance, evidence, methods, findings, publications, corrections, access, technical baselines, public-good software, recognition, finance-readiness, certification, procurement outcomes, provider status, or Nexus interface meaning.

508.22.2 Host operational requirements may define safe use of hosted environments but shall not alter institutional authority.

508.23 Public-Benefit and Nonprofit Definition Records.

508.23.1 The Corporation shall maintain Public-Benefit and Nonprofit Definition Records, including Public-Benefit Purpose records, Public-Good Purpose records, Public-Good Technical Institution records, Nonprofit Character records, Non-Distribution Principle records, No Private Inurement records, Impermissible Private Benefit records, Excess Benefit records, Tax-Exempt-Compatible records, Charitable Purpose records where applicable, Scientific Purpose records where applicable, Educational Purpose records where applicable, Public Trust records, Public-Safe Transparency records, Public-Good Firewall records, Mission Lock records, Anti-Capture records, Provider Neutrality records, Sponsor Non-Control records, Donor Non-Control records, Funder Non-Control records, Host Non-Control records, correction records, controlled vocabulary records, and archive records.

Section 509. Non-Execution and Boundary Definitions

509.1 “Non-Execution.”

509.1.1 “Non-Execution” means the Corporation’s binding institutional posture that GCRI US develops, stewards, reviews, records, publishes, corrects, and supports public-good evidence, methods, observability, ontology, technical truth, public-good software, open technical baselines, verifiable compute methods, verifiable intelligence methods, public authority learning, public-safe publication, safeguards, and Nexus coordination, without itself operating, commanding, financing, procuring, certifying, recognizing, rating, regulating, warning, underwriting, lending, insuring, executing, or delivering enterprise projects.

509.1.2 Non-Execution shall apply to all Corporation activities, including research, evidence generation, methods development, public-good software, technical baselines, dashboards, maps, controlled rooms, proof receipts, public authority learning materials, Nexus interface outputs, GRF interface inputs, GRA interface inputs, public-safe publications, Academy materials, repository releases, public claims, and technical asset disposition.

509.1.3 Non-Execution shall not prevent the Corporation from performing lawful nonprofit, administrative, research, technical, educational, public-good, convening, records, publication, repository, safeguarding, or support functions within its mission, provided such functions do not become execution, command, regulated finance, procurement, certification, recognition, public authority action, public warning, or enterprise operation.

509.2 “Non-Executing Institution.”

509.2.1 “Non-Executing Institution” means an institution that supports public-benefit objectives through evidence, methods, records, public-good software, technical baselines, learning, observability, ontology, publication, safeguards, and coordination, while remaining outside the chain of operational command, procurement decision, finance execution, public authority action, certification, recognition, provider selection, project delivery, and asset operation.

509.2.2 GCRI US is a Non-Executing Institution. Its outputs may inform, support, or be read by public authorities, GRF, GRA, Nexus Standards, Nexus Network, Nexus Observatory, Nexus Universe, Nexus Rails, Nexus Grid, Nexus Academy, consortiums, national companies, Project SPVs, providers, hosts, sponsors, communities, universities, laboratories, and capital readers, but such use shall not convert GCRI US into an executing body.

509.3 “Emergency Command.”

509.3.1 “Emergency Command” means authority to direct, coordinate, order, control, or command emergency response, emergency operations, emergency resources, incident response operations, evacuation, dispatch, alerting, public safety action, public health orders, infrastructure shutdowns, restoration priorities, mutual aid, or emergency protective measures.

509.3.2 GCRI US does not exercise Emergency Command. No report, dashboard, map, observability output, simulation, public-safe summary, public authority learning material, AI output, sensor signal, AI-RAN / O-RAN signal, DePIN record, DLT record, digital twin output, proof receipt, or Nexus interface output shall be treated as Emergency Command.

509.4 “Incident Command.”

509.4.1 “Incident Command” means formal or operational authority to direct an incident response structure, assign incident roles, allocate operational resources, control tactical response, set response objectives, manage field operations, or issue operational orders during an incident.

509.4.2 GCRI US may support incident learning, after-action review, scenario analysis, tabletop exercises, degraded-mode awareness, evidence literacy, and public-safe technical support, but shall not assume Incident Command.

509.5 “Official Public Warning.”

509.5.1 “Official Public Warning” means a warning, alert, bulletin, instruction, advisory, evacuation notice, shelter notice, public health notice, public safety notice, cyber emergency notice, infrastructure warning, or similar communication issued by a competent public authority or other lawful authority to direct or warn the public.

509.5.2 GCRI US does not issue Official Public Warnings. Public-safe summaries, dashboards, maps, publications, observability outputs, technical notes, or evidence records shall not be described or relied upon as Official Public Warnings.

509.6 “Emergency Alert.”

509.6.1 “Emergency Alert” means an official alert issued through a public warning, emergency management, public safety, public health, communications, utility, infrastructure, or other lawful alerting channel.

509.6.2 GCRI US shall not initiate, issue, transmit, authorize, or substitute for Emergency Alerts, except that GCRI US may provide non-command public-safe learning or technical support to competent authorities where lawfully structured.

509.7 “Public Health Order.”

509.7.1 “Public Health Order” means a legally operative order, directive, restriction, mandate, quarantine, isolation requirement, closure order, inspection order, health emergency instruction, or similar act issued by a competent public health authority.

509.7.2 GCRI US does not issue Public Health Orders. Health-sensitive research, public health evidence, dashboards, maps, or technical outputs shall not be used to imply that GCRI US has public health command or order authority.

509.8 “Safety Command.”

509.8.1 “Safety Command” means authority to direct safety operations, issue safety instructions, control field safety decisions, order shutdowns, require evacuations, assign safety resources, or command protective action.

509.8.2 GCRI US does not exercise Safety Command. Public-safe framing by GCRI US means non-command, evidence-disciplined, limitation-aware communication, not operational command.

509.9 “Regulation.”

509.9.1 “Regulation” means governmental rulemaking, supervision, enforcement, licensing, permitting, compliance determination, sanctioning, binding guidance, adjudication, inspection, regulatory approval, or other exercise of public regulatory authority.

509.9.2 GCRI US is not a regulator. Its methods, evidence, technical baselines, public-good software, dashboards, maps, proof receipts, public authority learning materials, and Nexus interface outputs shall not be treated as Regulation.

509.10 “Regulatory Approval.”

509.10.1 “Regulatory Approval” means an approval, authorization, clearance, license, permit, no-objection, safe harbor, compliance acceptance, waiver, enforcement position, or similar determination by a competent regulator.

509.10.2 GCRI US does not grant Regulatory Approval. No regulator attendance, regulator-listening participation, standards mapping, evidence review, proof receipt, technical baseline, dashboard, map, publication, or learning session shall be represented as Regulatory Approval.

509.11 “Compliance Approval.”

509.11.1 “Compliance Approval” means a determination that a person, project, provider, system, product, public authority, process, dataset, model, software, infrastructure, or organization complies with applicable law, regulation, standard, contract, policy, procurement requirement, or professional requirement.

509.11.2 GCRI US does not provide Compliance Approval unless a separate lawful instrument expressly authorizes a limited non-regulatory review within the Corporation’s role. Standards mapping, evidence review, methods review, technical baselines, and public-good software shall not be treated as Compliance Approval.

509.12 “Permit.”

509.12.1 “Permit” means a government-issued or authority-issued authorization to conduct an activity, build, operate, discharge, emit, deploy, use infrastructure, access restricted areas, perform regulated work, or otherwise engage in conduct requiring approval.

509.12.2 GCRI US does not issue Permits and shall not represent its outputs as satisfying, replacing, or guaranteeing Permit issuance.

509.13 “Public Procurement.”

509.13.1 “Public Procurement” means the acquisition, purchasing, tendering, contracting, vendor selection, award, framework qualification, bid evaluation, public contract formation, or procurement-related decision process of a public authority or publicly regulated body.

509.13.2 GCRI US does not conduct Public Procurement for public authorities and does not select vendors, approve vendors, score bids, award contracts, create approved vendor lists, or confer procurement advantage.

509.14 “Procurement Approval.”

509.14.1 “Procurement Approval” means approval, qualification, selection, scoring, eligibility, preferred status, award recommendation, approved vendor status, or procurement acceptance for a product, provider, project, service, technology, method, system, or organization.

509.14.2 No GCRI US evidence, technical baseline, software, proof receipt, dashboard, map, public-safe publication, repository release, room participation, sponsor status, provider status, Nexus interface, or public authority learning activity shall be treated as Procurement Approval.

509.15 “Provider Preference.”

509.15.1 “Provider Preference” means express or implied preference, endorsement, ranking, selection advantage, procurement advantage, commercial advantage, official approval, approved-provider status, or favored status for a provider, vendor, host, sponsor, contractor, platform, technology, model, cloud, AI system, cybersecurity system, telecom system, infrastructure system, or enterprise actor.

509.15.2 GCRI US shall maintain Provider Neutrality. Provider participation, sponsorship, contribution, technical support, repository involvement, event participation, controlled-room participation, or Nexus interface participation shall not create Provider Preference.

509.16 “Certification.”

509.16.1 “Certification” means a formal attestation, credential, approval, seal, certificate, mark, status, or determination that a person, organization, provider, product, project, system, model, dataset, technical asset, process, method, or infrastructure meets specified requirements.

509.16.2 GCRI US does not provide Certification by default. Public-good technical baselines, test harnesses, benchmarks, evidence records, proof receipts, public-safe publications, dashboards, maps, or software releases shall not be described as Certification unless competent authority expressly creates such status.

509.17 “Accreditation.”

509.17.1 “Accreditation” means recognition that a body, person, provider, laboratory, assessor, certification body, educational body, process, or system is competent or authorized to perform a function.

509.17.2 GCRI US does not provide Accreditation by default and shall not imply Accreditation through training, Academy support, review panels, technical baselines, repository access, or Nexus participation.

509.18 “Conformance.”

509.18.1 “Conformance” means alignment with, satisfaction of, or meeting of a standard, profile, protocol, test, baseline, schema, requirement, technical specification, or benchmark.

509.18.2 Conformance may be used only with precision, authority, scope, version, test record, limitation, and competent review. Passing a test harness, using a schema, implementing an API, referencing a baseline, or participating in Nexus shall not automatically create conformance status.

509.19 “Nexus-Compatible.”

509.19.1 “Nexus-Compatible” means a compatibility status, claim, or relationship with Nexus instruments, protocols, technical profiles, interfaces, records, role keys, software, baselines, standards, or coordination architecture.

509.19.2 Nexus-Compatible status exists only if supported by the proper authority and competent records. No fork, integration, use, adoption, test pass, repository reference, public-good software use, technical baseline use, provider participation, sponsor status, public authority attendance, Docket input, or Grid input shall automatically create Nexus-Compatible status.

509.20 “Recognition.”

509.20.1 “Recognition” means an official or institutional acknowledgment of standing, maturity, eligibility, public legitimacy, registry status, public-facing legitimacy, or other recognition-related status by the competent recognition authority.

509.20.2 Recognition is a GRF-related function unless otherwise lawfully assigned by competent records. GCRI US evidence, methods, technical baselines, observability outputs, software, publications, proof receipts, or public authority learning materials do not create Recognition.

509.21 “Standing.”

509.21.1 “Standing” means an acknowledged position, status, registry posture, eligibility posture, maturity posture, or legitimacy posture assigned by a competent authority under a defined record system.

509.21.2 GCRI US does not assign public standing, market standing, maturity standing, finance standing, or procurement standing unless separately and lawfully authorized.

509.22 “Maturity.”

509.22.1 “Maturity” means a staged, scored, classified, qualitative, or record-based assessment of development, readiness, governance, evidence, implementation, resilience, safeguards, technical status, or institutional capability.

509.22.2 Maturity meaning shall be controlled by the authority that creates it. GCRI US may provide technical evidence or methods inputs but does not create GRF maturity recognition, procurement maturity, finance maturity, or public authority maturity by default.

509.23 “Docket Approval.”

509.23.1 “Docket Approval” means approval, acceptance, routing, eligibility, or official status within a Nexus Docket or comparable record system by the competent authority.

509.23.2 GCRI US may provide Docket inputs where authorized, but Docket input, evidence submission, method review, proof receipt, public authority learning record, or technical baseline record shall not create Docket Approval by GCRI US.

509.24 “Grid Guarantee.”

509.24.1 “Grid Guarantee” means any express or implied guarantee, assurance, standing, eligibility, routing, maturity, adoption, or success claim arising from Nexus Grid or similar grid-related status.

509.24.2 GCRI US does not issue Grid Guarantees. No evidence record, software release, baseline, proof receipt, Docket input, dashboard, map, publication, or Nexus participation shall be treated as a Grid Guarantee.

509.25 “Public Finance Approval.”

509.25.1 “Public Finance Approval” means approval, allocation, appropriation, budget authorization, grant approval, public credit approval, public guarantee, tax credit approval, MDB / DFI approval, sovereign obligation, public finance commitment, or other public finance decision by a competent authority.

509.25.2 GCRI US does not provide Public Finance Approval. Public finance reader participation, grant application support, public authority learning, evidence packs, proof packs, dashboards, maps, or technical baselines shall not be represented as Public Finance Approval.

509.26 “Investment Advice.”

509.26.1 “Investment Advice” means advice, recommendation, analysis, opinion, or communication concerning the advisability of buying, selling, holding, financing, investing in, lending to, insuring, underwriting, rating, or otherwise transacting in securities, assets, projects, companies, funds, SPVs, instruments, or opportunities.

509.26.2 GCRI US does not provide Investment Advice. Evidence, methods, technical baselines, proof receipts, resilience analysis, public-safe reports, or GRA interface inputs shall not be used as Investment Advice.

509.27 “Securities Solicitation.”

509.27.1 “Securities Solicitation” means solicitation, offering, promotion, placement, recommendation, marketing, subscription support, investor introduction, or other activity concerning securities or investment interests.

509.27.2 GCRI US shall not engage in Securities Solicitation. Nexus, GRA, proof-pack, finance-readiness, capital-reader, or public-good evidence interfaces shall be governed to prevent securities solicitation by GCRI US.

509.28 “Broker-Dealer Activity.”

509.28.1 “Broker-Dealer Activity” means activity requiring broker, dealer, placement agent, underwriter, finder, investment adviser, or similar regulated status under applicable law.

509.28.2 GCRI US shall not conduct Broker-Dealer Activity and shall not receive compensation structured as transaction-based compensation for securities, capital raising, investment placement, lending placement, insurance placement, or similar regulated transactions unless lawful and separately authorized, which these Bylaws do not by themselves authorize.

509.29 “Finder Activity.”

509.29.1 “Finder Activity” means identifying, introducing, soliciting, referring, arranging, or facilitating investors, lenders, insurers, underwriters, buyers, sellers, issuers, projects, providers, or capital actors in a manner that may be regulated or that creates transaction-based finance activity.

509.29.2 GCRI US shall not engage in Finder Activity. Public-good convening, public authority learning, evidence literacy, or Nexus coordination shall be structured to avoid finder status.

509.30 “Lending.”

509.30.1 “Lending” means extending credit, arranging credit, approving credit, underwriting loans, guaranteeing repayment, servicing loans, making credit decisions, or otherwise acting as lender, bank, credit provider, loan broker, or credit intermediary.

509.30.2 GCRI US does not conduct Lending and shall not represent evidence, methods, public-safe reports, technical baselines, or Nexus interfaces as loan approval, credit approval, or repayment guarantee.

509.31 “Insurance Placement.”

509.31.1 “Insurance Placement” means soliciting, arranging, binding, placing, brokering, underwriting, pricing, advising on, or selling insurance, reinsurance, risk transfer, or insurance-like products.

509.31.2 GCRI US does not conduct Insurance Placement. Insurance-readiness interface support, where any, shall remain within GRA role separation and shall not become insurance activity by GCRI US.

509.32 “Underwriting.”

509.32.1 “Underwriting” means evaluating, assuming, pricing, approving, placing, guaranteeing, or committing risk, securities, loans, insurance, public finance, or other financial exposure.

509.32.2 GCRI US does not perform Underwriting. Technical evidence, observability, methods, resilience indicators, datasets, proof receipts, or public-safe materials shall not be represented as underwriting.

509.33 “Rating.”

509.33.1 “Rating” means a score, grade, rank, opinion, classification, or determination that expresses creditworthiness, investment quality, resilience grade, insurance quality, financeability, bankability, public finance eligibility, provider quality, public authority approval, maturity, safety, or similar evaluative status.

509.33.2 GCRI US does not issue Ratings unless a competent, lawful, Board-approved and boundary-reviewed instrument expressly authorizes a limited non-regulated technical classification, and such classification is clearly distinguished from finance, insurance, public finance, procurement, recognition, certification, and public authority ratings.

509.34 “Professional Advice.”

509.34.1 “Professional Advice” means advice requiring licensed or regulated professional status, including legal, tax, accounting, engineering, architectural, medical, public health, investment, insurance, lending, brokerage, rating, cybersecurity certification, or other professional advice.

509.34.2 GCRI US public-good materials are not Professional Advice unless expressly provided by a qualified professional under an authorized engagement and recorded scope. Public materials shall include limitation language where professional reliance risk exists.

509.35 “Public Authority Decision.”

509.35.1 “Public Authority Decision” means a decision, approval, denial, permit, order, finding, enforcement action, funding award, procurement award, public finance commitment, public warning, emergency command, public health order, regulatory action, legislative action, judicial action, or official act by a competent public authority.

509.35.2 GCRI US does not make Public Authority Decisions. Public authority participants may learn from, review, or receive GCRI US materials, but such interaction does not transform GCRI US outputs into Public Authority Decisions.

509.36 Boundary Definition Records.

509.36.1 The Corporation shall maintain Boundary Definition Records, including Non-Execution records, Non-Executing Institution records, Emergency Command records, Incident Command records, Official Public Warning records, Emergency Alert records, Public Health Order records, Safety Command records, Regulation records, Regulatory Approval records, Compliance Approval records, Permit records, Public Procurement records, Procurement Approval records, Provider Preference records, Certification records, Accreditation records, Conformance records, Nexus-Compatible records, Recognition records, Standing records, Maturity records, Docket Approval records, Grid Guarantee records, Public Finance Approval records, Investment Advice records, Securities Solicitation records, Broker-Dealer Activity records, Finder Activity records, Lending records, Insurance Placement records, Underwriting records, Rating records, Professional Advice records, Public Authority Decision records, correction records, public-safe limitation records, and archive records.

---

Section 510. Evidence, Research, Methods, and Technical Truth Definitions

510.1 “Research.”

510.1.1 “Research” means systematic, structured, or disciplined inquiry, investigation, study, analysis, testing, review, evidence generation, method development, observability review, dataset analysis, technical evaluation, or public-benefit knowledge work conducted by or for the Corporation.

510.1.2 Research may include qualitative, quantitative, mixed-method, technical, computational, legal-institutional, systems, resilience, public authority learning, community-informed, observability, data, AI, cyber, environmental, infrastructure, or technology-family research.

510.1.3 Research shall be subject to research integrity, ethics review where required or appropriate, evidence records, method records, limitation disclosure, uncertainty disclosure, safeguards, and correctionability.

510.2 “Public-Benefit R&D.”

510.2.1 “Public-Benefit R&D” means research and development conducted for public-good, scientific, educational, evidence, methods, observability, ontology, technical baseline, public-good software, verifiable compute, verifiable intelligence, public authority learning, safeguards, resilience, and Nexus coordination purposes.

510.2.2 Public-Benefit R&D shall not be used as a cover for private product development, provider preference, sponsor-controlled research, regulated finance activity, public authority substitution, certification, recognition, procurement approval, or enterprise execution.

510.3 “Evidence.”

510.3.1 “Evidence” means record-supported information, observation, dataset, source, signal, document, measurement, review, computation, inference, proof receipt, corroboration, benchmark result, method output, or other material that supports or challenges a factual, technical, institutional, public-safe, or methodological claim.

510.3.2 Evidence is distinct from opinion, recognition, finance-readiness, certification, procurement approval, public authority decision, public warning, emergency command, and rating.

510.3.3 Evidence shall be classified by source, lineage, quality, confidence, uncertainty, limitations, public-safe status, access class, correction status, and authority record.

510.4 “Evidence Record.”

510.4.1 “Evidence Record” means an Authoritative Record documenting evidence identity, source, lineage, custody, method, classification, confidence, uncertainty, limitations, reviewer notes, related records, public-safe status, access class, correction path, and retention status.

510.4.2 Evidence Records are necessary for material evidence claims, public-safe summaries, public authority learning materials, GRF inputs, GRA inputs, Docket inputs, Grid inputs, technical baselines, software claims, dashboards, maps, and Nexus interface outputs.

510.5 “Evidence Doctrine.”

510.5.1 “Evidence Doctrine” means the Corporation’s doctrine that evidence is record-based technical support and not recognition, finance-readiness, certification, procurement approval, public authority action, public warning, emergency command, rating, or legal compliance approval.

510.5.2 Evidence Doctrine shall govern collection, review, publication, correction, challenge, and interface use of evidence.

510.6 “Technical Truth.”

510.6.1 “Technical Truth” means the Corporation’s disciplined, record-based, method-supported, source-traceable, limitation-aware, uncertainty-aware, correctionable representation of technical facts, system states, evidence relationships, method outputs, and public-safe technical claims.

510.6.2 Technical Truth is not absolute certainty, public authority decision, finance determination, certification, recognition, or operational command.

510.6.3 Technical Truth requires records, methods, source lineage, confidence discipline, limitation disclosure, public-safe framing, and correctionability.

510.7 “Method.”

510.7.1 “Method” means a documented process, protocol, workflow, analytical approach, computational procedure, evaluation approach, test approach, observability approach, ontology approach, mapping approach, benchmark procedure, model evaluation procedure, or evidence review approach used to produce or assess evidence or technical outputs.

510.7.2 Methods shall be versioned, documented, reviewed, classified, and corrected where appropriate.

510.8 “Methods Stewardship.”

510.8.1 “Methods Stewardship” means the Corporation’s role in developing, documenting, reviewing, versioning, publishing where public-safe, maintaining, restricting where required, correcting, superseding, withdrawing, and archiving methods.

510.8.2 Methods Stewardship shall not be treated as certification, public authority approval, procurement approval, finance-readiness, recognition, or regulated professional approval.

510.9 “Validation.”

510.9.1 “Validation” means a documented assessment that a method, model, dataset, system, software, technical baseline, dashboard, map, proof receipt, or output is fit for a stated purpose within a stated scope and limitations.

510.9.2 Validation is scope-limited and record-based. Validation shall not imply certification, legal compliance, public authority approval, finance-readiness, procurement approval, recognition, rating, or public warning status unless the competent authority expressly provides such meaning.

510.10 “Verification.”

510.10.1 “Verification” means a documented assessment that a claim, result, record, process, computation, dataset, software release, technical asset, source, or output conforms to specified requirements, records, or expected conditions within a stated scope.

510.10.2 Verification shall identify what was checked, against what reference, by whom, using what method, on what date, with what limitations.

510.11 “Corroboration.”

510.11.1 “Corroboration” means support for evidence or a claim through independent, partially independent, alternative, or additional sources, methods, signals, records, or reviewer assessments.

510.11.2 Corroboration strengthens but does not eliminate uncertainty and does not create authority beyond the corroborated scope.

510.12 “Calibration.”

510.12.1 “Calibration” means documented adjustment, checking, benchmarking, alignment, or comparison of instruments, sensors, models, methods, dashboards, evaluation systems, or confidence estimates against references, standards, baseline data, or known conditions.

510.12.2 Calibration records shall identify reference, method, date, result, limitations, and correction implications.

510.13 “Benchmark.”

510.13.1 “Benchmark” means a structured test, reference task, dataset, scenario, comparison, evaluation procedure, performance reference, or metric used to assess systems, models, methods, software, datasets, dashboards, maps, protocols, or technical baselines.

510.13.2 Benchmarks shall be documented with scope, version, limitations, suitability, known biases, data restrictions, and public-safe status.

510.13.3 A Benchmark result is not a rating, certification, recognition, procurement approval, finance-readiness, public authority approval, or provider preference unless a competent authority expressly provides such meaning.

510.14 “Gold Vector.”

510.14.1 “Gold Vector” means a reference input, expected output, canonical case, test vector, verified example, or known-valid data point used to evaluate correctness, consistency, interoperability, or regression behavior.

510.14.2 Gold Vectors shall be versioned, sourced, documented, protected where sensitive, and corrected when defects are discovered.

510.15 “Negative Test.”

510.15.1 “Negative Test” means a test designed to confirm that a system, method, model, software, interface, technical baseline, dashboard, map, or workflow rejects, flags, contains, limits, or fails safely under invalid, adversarial, unsafe, unauthorized, out-of-scope, or boundary-defective conditions.

510.15.2 Negative Tests may be restricted where disclosure could create security, misuse, protected knowledge, public authority, or public-safe risks.

510.16 “Test Harness.”

510.16.1 “Test Harness” means software, scripts, tooling, datasets, scenarios, procedures, workflows, infrastructure, or interfaces used to run, measure, reproduce, evaluate, validate, verify, or challenge a technical system, method, model, dataset, protocol, baseline, API, SDK, dashboard, map, or output.

510.16.2 Test Harnesses shall be versioned, documented, licensed, secured, and accompanied by limitations.

510.17 “Evaluation Set.”

510.17.1 “Evaluation Set” means a dataset, set of prompts, cases, tasks, signals, scenarios, examples, records, or inputs used to evaluate performance, safety, accuracy, bias, robustness, drift, hallucination, interoperability, or other properties.

510.17.2 Evaluation Sets shall be governed by data rights, privacy, protected knowledge, public authority restrictions, security, and publication controls.

510.18 “Source Lineage.”

510.18.1 “Source Lineage” means the documented chain identifying where evidence, data, claims, records, signals, models, methods, outputs, or technical assets came from, how they were obtained, how they were transformed, and what records support them.

510.18.2 Source Lineage is required for material public claims, evidence records, datasets, dashboards, maps, technical baselines, software claims, GRF inputs, GRA inputs, and Nexus interface outputs.

510.19 “Provenance.”

510.19.1 “Provenance” means documented origin, authorship, custody, transformation, version, processing history, source authority, and record history of data, software, technical assets, publications, evidence, models, compute outputs, and claims.

510.19.2 Provenance supports integrity, auditability, correctionability, and public-safe reliance limitations.

510.20 “Custody.”

510.20.1 “Custody” means possession, control, stewardship, authorized access, storage, processing, or responsibility for records, data, evidence, technical assets, public authority materials, protected knowledge, or other materials.

510.20.2 Custody shall be documented for restricted, confidential, public authority, protected knowledge, cyber-sensitive, infrastructure-sensitive, health-sensitive, rights-bearing, and controlled-room materials.

510.21 “Chain-of-Custody.”

510.21.1 “Chain-of-Custody” means the documented sequence of possession, transfer, access, handling, processing, review, storage, sealing, release, correction, archive, or disposal of evidence, data, records, technical assets, or restricted materials.

510.21.2 Chain-of-Custody records shall be maintained where integrity, legality, public authority restrictions, research integrity, security, protected knowledge, or dispute resolution requires traceability.

510.22 “Confidence Score.”

510.22.1 “Confidence Score” means a qualitative, quantitative, categorical, probabilistic, or structured expression of confidence in evidence, method output, model output, observation, dashboard output, map output, or public-safe claim.

510.22.2 Confidence Scores shall be accompanied by method, scope, uncertainty, limitations, and source lineage. They shall not be represented as certification, rating, recognition, finance-readiness, procurement approval, public authority approval, public warning, or emergency command.

510.23 “Uncertainty.”

510.23.1 “Uncertainty” means known or reasonably foreseeable limits, variability, ambiguity, incompleteness, error range, unknowns, model limitations, measurement limitations, sampling limitations, source limitations, method limitations, temporal limitations, or interpretation limits affecting evidence or outputs.

510.23.2 Material uncertainty shall be disclosed in public-safe and controlled outputs according to audience, classification, and risk.

510.24 “Disputed Evidence.”

510.24.1 “Disputed Evidence” means evidence whose accuracy, source, method, interpretation, classification, completeness, authority, custody, public-safe status, or use has been challenged or is subject to unresolved disagreement.

510.24.2 Disputed Evidence shall be flagged, reviewed, restricted where necessary, and corrected, superseded, withdrawn, or retained with limitations as appropriate.

510.25 “Failed Signal.”

510.25.1 “Failed Signal” means a signal, data point, sensor output, telemetry item, model output, observability output, proof receipt, inference, or evidence element that has failed validation, verification, quality review, calibration, source review, plausibility review, or public-safe review.

510.25.2 Failed Signals shall not support material public claims unless clearly labeled and used for failure analysis.

510.26 “Spoofed Signal.”

510.26.1 “Spoofed Signal” means a signal, source, record, telemetry item, sensor output, digital identity, ledger entry, AI output, or observability record that is fabricated, manipulated, impersonated, adversarially generated, replayed, falsified, or otherwise made to appear authentic when it is not.

510.26.2 Spoofed Signals shall be handled as integrity, cybersecurity, evidence, or incident matters and shall not support public claims except as evidence of spoofing.

510.27 “Stale Evidence.”

510.27.1 “Stale Evidence” means evidence whose age, update status, context, source status, environmental conditions, system conditions, legal status, public authority status, or technical status materially limits current use.

510.27.2 Stale Evidence may be used for historical context if labeled and shall not be used for current public claims without review.

510.28 “Superseded Evidence.”

510.28.1 “Superseded Evidence” means evidence replaced by later, better, corrected, more authoritative, more complete, or more current evidence.

510.28.2 Superseded Evidence shall be retained for traceability where appropriate but shall not be used as current evidence unless context requires and limitations are disclosed.

510.29 “Corrected Evidence.”

510.29.1 “Corrected Evidence” means evidence amended, clarified, limited, reclassified, recalculated, re-sourced, reinterpreted, or otherwise corrected through an authorized correction process.

510.29.2 Corrected Evidence shall include correction records, affected claims, downstream dependencies, and notice where required.

510.30 “Research Integrity.”

510.30.1 “Research Integrity” means adherence to accuracy, honesty, transparency, reproducibility where appropriate, replicability where appropriate, method documentation, conflict management, sponsor and provider independence, peer review where appropriate, ethical review where required or appropriate, data and source integrity, limitation disclosure, uncertainty disclosure, public-safe framing, and correctionability.

510.31 “Research Misconduct.”

510.31.1 “Research Misconduct” means fabrication, falsification, plagiarism, improper source omission, unsupported confidence claim, suppression of material limitation, misleading public-safe summary, misuse of GCRI US name or technical baseline, misuse of proof receipt or boundary terms, sponsor or provider distortion, AI-generated fabrication, or other material departure from research integrity requirements.

510.32 “Peer Review.”

510.32.1 “Peer Review” means review by qualified persons of research, evidence, methods, publications, datasets, software, technical baselines, dashboards, maps, models, benchmarks, or other outputs to assess quality, accuracy, limitations, and correction needs.

510.32.2 Peer Review may be internal, external, blinded, open, controlled, technical, community-informed, public authority-informed, or safeguards-informed, as appropriate.

510.32.3 Peer Review does not create certification, finance-readiness, recognition, procurement approval, public authority approval, or rating by default.

510.33 “Public-Safe Summary.”

510.33.1 “Public-Safe Summary” means a public-facing or broadly shareable summary that communicates accurate, limitation-aware, non-command, non-overclaim, non-sensitive information while protecting privacy, cybersecurity, infrastructure sensitivity, public authority restrictions, protected knowledge, and public safety.

510.33.2 Public-Safe Summaries shall not substitute for full evidence records, controlled annexes, legal advice, public authority decisions, public warnings, finance-readiness determinations, certifications, or recognition decisions.

510.34 “Controlled Annex.”

510.34.1 “Controlled Annex” means a non-public, restricted, confidential, public authority, research-sensitive, finance-sensitive, cyber-sensitive, infrastructure-sensitive, protected knowledge, or otherwise controlled supplement to a public-safe publication, evidence pack, report, dataset, dashboard, map, or technical output.

510.34.2 Controlled Annexes shall be access-controlled, logged, classified, and subject to confidentiality, data, AI, cyber, privacy, public authority, protected knowledge, and retention requirements.

510.35 Evidence, Research, Methods, and Technical Truth Definition Records.

510.35.1 The Corporation shall maintain Evidence, Research, Methods, and Technical Truth Definition Records, including Research records, Public-Benefit R&D records, Evidence records, Evidence Record definitions, Evidence Doctrine records, Technical Truth records, Method records, Methods Stewardship records, Validation records, Verification records, Corroboration records, Calibration records, Benchmark records, Gold Vector records, Negative Test records, Test Harness records, Evaluation Set records, Source Lineage records, Provenance records, Custody records, Chain-of-Custody records, Confidence Score records, Uncertainty records, Disputed Evidence records, Failed Signal records, Spoofed Signal records, Stale Evidence records, Superseded Evidence records, Corrected Evidence records, Research Integrity records, Research Misconduct records, Peer Review records, Public-Safe Summary records, Controlled Annex records, correction records, and archive records.

---

Section 511. Observability and Nexus Observatory Definitions

511.1 “Observability.”

511.1.1 “Observability” means the disciplined ability to observe, record, structure, interpret, and communicate system states, signals, telemetry, conditions, events, dependencies, vulnerabilities, resilience indicators, and degraded-mode conditions through lawful, ethical, public-safe, and technically sound methods.

511.1.2 Observability may include sensors, telemetry, AI-RAN / O-RAN signals, DePIN records, DLT records, digital twins, cyber telemetry, geospatial evidence, Earth observation, edge compute, dashboards, maps, public-safe visualizations, and evidence records.

511.1.3 Observability shall not be treated as public warning, emergency command, surveillance authority, public authority decision, certification, recognition, finance-readiness, procurement approval, rating, or provider preference.

511.2 “Observability Stewardship.”

511.2.1 “Observability Stewardship” means the Corporation’s role in developing, documenting, reviewing, versioning, correcting, and public-safely communicating observability methods, observability records, observability outputs, public-safe maps, dashboards, and related technical baselines.

511.2.2 Observability Stewardship shall be subject to data / AI / cyber / privacy controls, public authority boundaries, protected knowledge safeguards, infrastructure-sensitive restrictions, and public-safe publication rules.

511.3 “Nexus Observatory Methods.”

511.3.1 “Nexus Observatory Methods” means the methods, protocols, workflows, ontologies, schemas, profiles, evidence records, dashboards, maps, quality controls, and public-safe publication controls used to support Nexus Observatory functions.

511.3.2 GCRI US may steward or support Nexus Observatory Methods within its non-executing technical role.

511.4 “Observatory Node.”

511.4.1 “Observatory Node” means a structured point, unit, site, system, organization, technical environment, sensor environment, data environment, public authority learning environment, community interface, or observability function that contributes to or participates in observability.

511.4.2 Observatory Node status shall not create public authority status, certification, recognition, procurement approval, finance-readiness, operational command, or provider preference.

511.5 “Nexus Hub.”

511.5.1 “Nexus Hub” means a Nexus-aligned hub through which observability, evidence, methods, public authority learning, technical assets, community safeguards, or Nexus coordination may be organized.

511.5.2 Nexus Hub status shall be record-based and shall not imply legal merger, public authority delegation, procurement approval, finance-readiness, certification, recognition, or enterprise execution by GCRI US.

511.6 “Nexus Cluster.”

511.6.1 “Nexus Cluster” means a grouping of nodes, hubs, institutions, communities, public authorities, technical assets, infrastructure systems, or thematic functions organized for Nexus-aligned observability, evidence, methods, learning, or coordination.

511.6.2 Nexus Cluster status shall be subject to records, role separation, public-safe publication, data controls, and protected knowledge safeguards.

511.7 “Nexus Hotspot.”

511.7.1 “Nexus Hotspot” means a place, system, sector, risk pattern, infrastructure dependency, technology concentration, vulnerability, opportunity, or public-good focus area identified for observability, learning, methods development, safeguards, or coordination.

511.7.2 A Nexus Hotspot designation shall not be treated as a public warning, emergency command, public authority determination, rating, recognition, finance-readiness, certification, procurement approval, or stigmatizing label.

511.8 “Regional Cluster.”

511.8.1 “Regional Cluster” means a regional grouping of Nexus functions, observability nodes, public-good institutions, public authority learning interfaces, communities, infrastructure systems, universities, laboratories, providers, or enterprise actors.

511.8.2 Regional Cluster status shall preserve regional legal distinctions, public authority boundaries, cross-border data controls, protected knowledge safeguards, and Nexus role separation.

511.9 “National Dense Nexus Core.”

511.9.1 “National Dense Nexus Core” means a concentrated national-level Nexus configuration, capacity, or interface involving public-good institutions, public authorities, observability functions, technical assets, evidence flows, methods, public authority learning, and ecosystem coordination.

511.9.2 National Dense Nexus Core status shall not create national public authority status, sovereign authority, public finance approval, procurement authority, emergency command, public warning, certification, recognition, or enterprise execution by GCRI US.

511.10 “Sensor.”

511.10.1 “Sensor” means a device, system, process, signal source, software instrument, human-reported observation, automated feed, satellite source, edge device, network signal, cyber log, infrastructure telemetry source, or other means of detecting or recording information.

511.10.2 Sensor outputs require source lineage, quality review, calibration where appropriate, classification, and public-safe review before material use.

511.11 “Reference Sensor.”

511.11.1 “Reference Sensor” means a sensor, signal source, benchmark source, calibration source, or trusted reference used to compare, validate, verify, calibrate, or corroborate other signals.

511.11.2 Reference Sensor status shall be documented and shall not guarantee accuracy beyond its scope and limitations.

511.12 “Telemetry.”

511.12.1 “Telemetry” means remotely or automatically collected measurements, signals, logs, events, state data, operational data, network data, sensor data, infrastructure data, AI-RAN / O-RAN data, cyber data, or system data.

511.12.2 Telemetry shall be classified and handled according to privacy, public authority, cyber-sensitive, infrastructure-sensitive, commercial-sensitive, protected knowledge, and public-safe requirements.

511.13 “Edge Compute.”

511.13.1 “Edge Compute” means computation, processing, inference, filtering, aggregation, storage, or analytics performed near sensors, devices, networks, infrastructure, facilities, field environments, or operational systems.

511.13.2 Edge Compute outputs shall not be treated as authoritative without records, review, classification, security controls, and correction path.

511.14 “AI-RAN Signal.”

511.14.1 “AI-RAN Signal” means a signal, telemetry record, inference, control-plane indicator, performance indicator, security indicator, operational indicator, or observability output associated with AI-enabled radio access networks or related telecom infrastructure.

511.14.2 AI-RAN Signals may be cyber-sensitive or infrastructure-sensitive and shall not be publicized, mapped, or used for public claims without review.

511.14.3 AI-RAN Signals do not constitute public warnings, emergency commands, public authority decisions, certifications, procurement approvals, finance-readiness determinations, or provider preferences.

511.15 “O-RAN Signal.”

511.15.1 “O-RAN Signal” means a signal, telemetry record, interface indicator, operational indicator, security indicator, performance indicator, or observability output associated with open radio access network architectures or components.

511.15.2 O-RAN Signals shall be subject to telecom, cyber, infrastructure, public authority, provider neutrality, and public-safe review controls.

511.16 “DePIN Record.”

511.16.1 “DePIN Record” means a record, signal, telemetry item, proof, ledger-linked record, device record, infrastructure participation record, token-linked record, or decentralized physical infrastructure network record.

511.16.2 DePIN Records require source, integrity, spoofing, custody, privacy, cyber, infrastructure, finance-boundary, and public-safe review before material use.

511.17 “DLT Record.”

511.17.1 “DLT Record” means a distributed ledger, blockchain, token, smart contract, hash, transaction, timestamp, proof, role-key, smart-license, or ledger-linked record.

511.17.2 A DLT Record is not authoritative merely because it is on a ledger. It requires authority, source lineage, lawful basis, interpretation, and review.

511.18 “Digital Twin Output.”

511.18.1 “Digital Twin Output” means a modeled, simulated, estimated, visualized, or computed representation generated by or from a digital twin of a system, infrastructure, environment, asset, region, process, or risk pattern.

511.18.2 Digital Twin Outputs shall disclose model assumptions, data sources, limitations, uncertainty, update status, and public-safe constraints.

511.18.3 Digital Twin Outputs shall not be treated as public authority decisions, emergency commands, public warnings, certifications, finance-readiness, ratings, or procurement approvals.

511.19 “Cyber Telemetry.”

511.19.1 “Cyber Telemetry” means logs, alerts, events, packet data, endpoint data, network data, vulnerability data, identity data, access data, threat intelligence, incident artifacts, or security observations.

511.19.2 Cyber Telemetry is presumptively sensitive unless classified otherwise and shall be protected from overdisclosure.

511.20 “Geospatial Evidence.”

511.20.1 “Geospatial Evidence” means evidence with spatial, locational, geographic, mapping, coordinate, boundary, parcel, infrastructure, environmental, community, or place-based relevance.

511.20.2 Geospatial Evidence shall be reviewed for public-safe mapping, protected knowledge, infrastructure sensitivity, public authority restrictions, privacy, community safety, and risk of stigmatization.

511.21 “Earth Observation Evidence.”

511.21.1 “Earth Observation Evidence” means evidence derived from satellites, aircraft, drones, remote sensing, imagery, radar, lidar, environmental sensors, climate data, land cover data, ocean data, atmospheric data, or other Earth observation sources.

511.21.2 Earth Observation Evidence shall be reviewed for source lineage, resolution, uncertainty, timeliness, licensing, public-safe mapping, protected knowledge, and infrastructure sensitivity.

511.22 “Dashboard.”

511.22.1 “Dashboard” means a visual, interactive, static, public, controlled, internal, or restricted interface displaying data, evidence, indicators, signals, maps, charts, statuses, outputs, risks, or technical records.

511.22.2 Dashboards shall include source, timestamp, version, confidence, limitations, classification, update status, and non-reliance notices where appropriate.

511.23 “Map.”

511.23.1 “Map” means a spatial representation, geospatial visualization, layer, digital twin view, public-safe visualization, dashboard map, risk map, observability map, infrastructure map, community map, or public authority map.

511.23.2 Maps shall be subject to public-safe mapping review, infrastructure-sensitive review, cyber-sensitive review, public authority data review, and protected knowledge review where applicable.

511.24 “Public-Safe Map.”

511.24.1 “Public-Safe Map” means a map designed for public or broad sharing after review to reduce risk of harm, exposure, misinterpretation, stigmatization, public authority confusion, public warning confusion, infrastructure vulnerability, cyber misuse, privacy harm, or protected knowledge disclosure.

511.24.2 A Public-Safe Map is not an official public warning, public authority decision, emergency command, safety command, certification, recognition, finance-readiness, rating, or procurement approval.

511.25 “Degraded-Mode Awareness.”

511.25.1 “Degraded-Mode Awareness” means awareness of reduced, impaired, uncertain, disrupted, compromised, partial, or unreliable system operation, data availability, infrastructure state, communications state, observability state, AI state, cyber posture, or public authority operating context.

511.25.2 Degraded-Mode Awareness supports learning and public-safe technical understanding and shall not be used as emergency command by GCRI US.

511.26 “Resilience Indicator.”

511.26.1 “Resilience Indicator” means a qualitative or quantitative indicator used to understand capacity, exposure, vulnerability, redundancy, adaptability, recovery, robustness, continuity, or degraded-mode performance.

511.26.2 Resilience Indicators shall not be represented as ratings, finance-readiness, insurance-readiness, public authority approval, procurement approval, certification, or recognition without competent authority.

511.27 “Observability Output.”

511.27.1 “Observability Output” means an evidence item, dashboard, map, signal interpretation, telemetry interpretation, public-safe summary, technical note, indicator, alert-like internal note, or method output derived from observability.

511.27.2 Observability Outputs shall be classified, versioned, limitation-aware, public-safe reviewed where shared, and correctionable.

511.28 “Nexus Truth Engine.”

511.28.1 “Nexus Truth Engine” means a Nexus-aligned method, architecture, record system, computation system, ontology-supported reasoning system, evidence relationship system, or technical framework for structuring, testing, tracing, and correcting technical truth claims.

511.28.2 GCRI US may steward methods supporting Nexus Truth Engine functions, but Truth Engine methods do not create public authority decisions, finance-readiness, certification, recognition, procurement approval, public warning, or emergency command.

511.29 “Truth Engine Output.”

511.29.1 “Truth Engine Output” means an output, inference, relationship, record, confidence statement, contradiction flag, evidence map, method result, or technical claim generated through Nexus Truth Engine methods or systems.

511.29.2 Truth Engine Outputs require human review, record support, limitation disclosure, public-safe classification, and correction path before material public or interface use.

511.30 Observability Definition Records.

511.30.1 The Corporation shall maintain Observability Definition Records, including Observability records, Observability Stewardship records, Nexus Observatory Methods records, Observatory Node records, Nexus Hub records, Nexus Cluster records, Nexus Hotspot records, Regional Cluster records, National Dense Nexus Core records, Sensor records, Reference Sensor records, Telemetry records, Edge Compute records, AI-RAN Signal records, O-RAN Signal records, DePIN Record records, DLT Record records, Digital Twin Output records, Cyber Telemetry records, Geospatial Evidence records, Earth Observation Evidence records, Dashboard records, Map records, Public-Safe Map records, Degraded-Mode Awareness records, Resilience Indicator records, Observability Output records, Nexus Truth Engine records, Truth Engine Output records, correction records, and archive records.

---

Section 512. Ontology, Semantic, and Controlled Vocabulary Definitions

512.1 “Ontology.”

512.1.1 “Ontology” means a structured representation of concepts, relationships, classes, properties, terms, constraints, meanings, and semantic relationships used to organize evidence, methods, risks, technologies, public authority capacities, finance boundaries, certification boundaries, data classes, safeguards, public-safe terms, and Nexus interfaces.

512.1.2 Ontology supports semantic interoperability and controlled meaning. It does not create legal authority, certification, recognition, finance-readiness, procurement approval, public authority decision, public warning, or emergency command.

512.2 “Taxonomy.”

512.2.1 “Taxonomy” means a structured classification system for organizing concepts, records, risks, evidence, methods, data, technologies, outputs, publications, incidents, assets, roles, or interfaces.

512.2.2 A Taxonomy shall be versioned, documented, and corrected when classifications become inaccurate or misleading.

512.3 “Controlled Vocabulary.”

512.3.1 “Controlled Vocabulary” means the approved set of defined, restricted, reserved, prohibited, preferred, or context-specific terms governing institutional language, public claims, evidence status, technical claims, public authority references, finance-boundary statements, certification and recognition terms, Nexus interface terms, safeguards terms, and public-safe materials.

512.3.2 Controlled Vocabulary is mandatory for material public and institutional claims.

512.4 “Schema.”

512.4.1 “Schema” means a structured specification defining data fields, types, relationships, constraints, formats, metadata, validation rules, interoperability requirements, or record structures.

512.4.2 Schemas support interoperability but do not by themselves create certification, conformance approval, procurement mandate, public authority adoption, finance-readiness, recognition, or legal compliance approval.

512.5 “Data Dictionary.”

512.5.1 “Data Dictionary” means a documented set of data elements, definitions, fields, permissible values, formats, classifications, source notes, quality rules, sensitivity rules, access rules, and interpretation notes.

512.5.2 Data Dictionaries shall be aligned with the Corporation’s ontology, controlled vocabulary, data classification, and public-safe publication rules.

512.6 “Semantic Interoperability.”

512.6.1 “Semantic Interoperability” means the ability of systems, records, datasets, methods, dashboards, maps, repositories, institutions, and Nexus interfaces to exchange and interpret information consistently according to shared meaning.

512.6.2 Semantic Interoperability does not mean legal equivalence, certification, public authority adoption, finance-readiness, recognition, procurement approval, or provider preference.

512.7 “AI-Readable Knowledge Structure.”

512.7.1 “AI-Readable Knowledge Structure” means an ontology, schema, data dictionary, structured record, embedding-supported structure, graph, taxonomy, prompt-safe corpus, or other structured resource designed to be read, used, retrieved, or reasoned over by AI systems.

512.7.2 AI-Readable Knowledge Structures shall be governed by AI-use restrictions, data rights, protected knowledge controls, privacy, cybersecurity, source lineage, and correctionability.

512.8 “Risk Category.”

512.8.1 “Risk Category” means a defined category used to classify risk, including systemic, technological, cyber, AI, infrastructure, public authority, finance, procurement, public-safe publication, civil rights, accessibility, community, protected knowledge, legal, compliance, reputational, operational, and Nexus coordination risks.

512.8.2 Risk Categories support governance and do not by themselves create ratings or public warnings.

512.9 “Evidence Class.”

512.9.1 “Evidence Class” means a classification of evidence by type, source, quality, confidence, uncertainty, public-safe status, access class, legal sensitivity, technical sensitivity, public authority status, protected knowledge status, or correction status.

512.9.2 Evidence Class shall be recorded and updated when evidence is corrected, superseded, disputed, stale, or withdrawn.

512.10 “Technology Family.”

512.10.1 “Technology Family” means a class of technologies covered by the Corporation’s work, including AI, AI-RAN, O-RAN, private wireless, telecommunications, blockchain, DLT, Web3, quantum-relevant systems, HPC, sovereign compute, cyber, robotics, drones, sensing, Earth observation, geospatial systems, digital twins, biosecurity, climate, nature, WEFH systems, energy, advanced manufacturing, semiconductors, and related exponential technologies.

512.10.2 Technology Family classification shall not imply provider preference, certification, procurement approval, public authority adoption, finance-readiness, recognition, or rating.

512.11 “Maturity Concept.”

512.11.1 “Maturity Concept” means a conceptual stage, level, category, or descriptor used to discuss development, governance, resilience, evidence quality, implementation readiness, technical capability, safeguards, or institutional capacity.

512.11.2 Maturity Concepts used by GCRI US are technical or conceptual unless competent GRF, GRA, Nexus Grid, or other authority gives them formal status.

512.12 “Public Authority Capacity Concept.”

512.12.1 “Public Authority Capacity Concept” means a controlled term describing the capacity in which a public authority or public-sector person participates, including official participant, observer, regulator-listening participant, public finance reader, emergency-management participant, public infrastructure operator participant, public health participant, public safety participant, public works participant, personal-capacity participant, non-attributable participant, data provider, reviewer, or simulation participant.

512.12.2 Public Authority Capacity Concepts prevent public authority overclaim and shall be recorded.

512.13 “Finance Boundary Concept.”

512.13.1 “Finance Boundary Concept” means a controlled term or classification used to distinguish technical evidence, public-good records, proof-pack inputs, capital-reader learning, finance-readiness meaning, investment advice, securities activity, lending, insurance, rating, public finance approval, and capital execution.

512.13.2 Finance Boundary Concepts shall preserve GRA role separation and GCRI US non-finance status.

512.14 “Certification Boundary Concept.”

512.14.1 “Certification Boundary Concept” means a controlled term or classification used to distinguish technical baselines, conformance tests, benchmarks, evidence reviews, validation, verification, certification, accreditation, procurement approval, compliance approval, recognition, Nexus-compatible status, Docket status, and Grid status.

512.14.2 Certification Boundary Concepts shall prevent unsupported certification, recognition, procurement, and public authority meaning.

512.15 “Public-Safe Term.”

512.15.1 “Public-Safe Term” means a term approved for public or broad use because it is accurate, limitation-aware, non-command, non-overclaim, non-sensitive, accessible, and unlikely to create public authority, finance, certification, recognition, procurement, public warning, emergency command, protected knowledge, or public safety confusion.

512.16 “Restricted Term.”

512.16.1 “Restricted Term” means a term that may be used only with approval, context, limitation language, record support, or controlled audience because it carries legal, public authority, finance, certification, recognition, procurement, security, protected knowledge, or public-safe risk.

512.17 “Reserved Term.”

512.17.1 “Reserved Term” means a term reserved to the Board, a proper Nexus authority, GRF, GRA, Nexus Standards, protocol authority, public authority, or other competent body.

512.17.2 Reserved Terms shall not be used by GCRI US without authority from the proper source and record support.

512.18 “Semantic Drift.”

512.18.1 “Semantic Drift” means gradual, informal, public, internal, technical, AI-generated, sponsor-driven, provider-driven, public authority-driven, or media-driven change in the meaning or perceived meaning of a term away from its approved meaning.

512.18.2 Semantic Drift shall trigger review, correction, controlled vocabulary update, public-safe clarification, or restriction where material.

512.19 “Equivalence Note.”

512.19.1 “Equivalence Note” means a record explaining whether and how one term, classification, standard, method, profile, jurisdictional concept, public authority capacity, finance-boundary concept, or Nexus interface term is equivalent or not equivalent to another.

512.19.2 Equivalence Notes do not create legal equivalence, certification, recognition, finance-readiness, procurement approval, or public authority approval unless competent authority expressly provides such meaning.

512.20 “Compatibility Note.”

512.20.1 “Compatibility Note” means a record describing technical, semantic, procedural, policy, data, AI, cyber, public authority, finance-boundary, safeguards, or Nexus compatibility between systems, records, methods, institutions, standards, baselines, or interfaces.

512.20.2 Compatibility Notes shall not create Nexus-Compatible status unless issued by competent authority for that purpose.

512.21 “Divergence Log.”

512.21.1 “Divergence Log” means a record documenting differences, conflicts, deviations, localizations, exceptions, unresolved issues, or controlled departures among terms, instruments, methods, baselines, policies, jurisdictions, Nexus interfaces, or technical assets.

512.21.2 Divergence Logs support transparency and correctionability without creating approval or waiver by default.

512.22 “Localization Note.”

512.22.1 “Localization Note” means a record explaining how a term, policy, method, protocol, public authority language, data rule, safeguard, technical asset, publication, or Nexus interface is adapted for a jurisdiction, community, public authority, sector, language, cultural context, or legal context.

512.22.2 Localization Notes shall not weaken mandatory Bylaw protections.

512.23 “Interface Map.”

512.23.1 “Interface Map” means a structured record showing relationships, roles, dependencies, handoffs, boundaries, records, data flows, public authority interfaces, finance interfaces, technical interfaces, Nexus interfaces, or safeguards interfaces among persons, institutions, systems, or instruments.

512.23.2 Interface Maps are explanatory and operational tools and shall not create authority beyond competent records.

512.24 Ontology and Semantic Definition Records.

512.24.1 The Corporation shall maintain Ontology and Semantic Definition Records, including Ontology records, Taxonomy records, Controlled Vocabulary records, Schema records, Data Dictionary records, Semantic Interoperability records, AI-Readable Knowledge Structure records, Risk Category records, Evidence Class records, Technology Family records, Maturity Concept records, Public Authority Capacity Concept records, Finance Boundary Concept records, Certification Boundary Concept records, Public-Safe Term records, Restricted Term records, Reserved Term records, Semantic Drift records, Equivalence Note records, Compatibility Note records, Divergence Log records, Localization Note records, Interface Map records, correction records, and archive records.

---

Section 513. Data, AI, Cybersecurity, Privacy, and Compute Definitions

513.1 “Data.”

513.1.1 “Data” means recorded information, observations, measurements, signals, text, images, audio, video, metadata, telemetry, logs, structured records, unstructured records, derived records, synthetic records, model inputs, model outputs, embeddings, vector records, geospatial information, public authority materials, protected knowledge materials, or other machine-readable or human-readable information.

513.1.2 Data shall be governed by classification, source authority, lawful basis, permissions, privacy, cybersecurity, public authority restrictions, protected knowledge restrictions, retention, access, and correction requirements.