ARTICLE XII. PUBLICATIONS

Section 337. Public-Safe Publication Purpose

337.1 Public-Safe Publication Purpose.

337.1.1 Public-Safe Publication shall mean the Corporation’s disciplined process for preparing, reviewing, approving, releasing, correcting, superseding, withdrawing, retracting, archiving, and preserving public-facing or externally circulated materials in a manner that is accurate, evidence-supported, limitation-aware, public-benefit-aligned, lawful, non-misleading, accessible where appropriate, safeguards-compliant, and consistent with the Corporation’s non-executing institutional role.

337.1.2 Public-Safe Publication shall apply to all publications, external outputs, public-safe summaries, reports, whitepapers, technical notes, method notes, evidence packs, dashboards, maps, datasets, software releases, open technical baselines, reference architectures, APIs, SDKs, schemas, technical profiles, test harnesses, model cards, system cards, dataset cards, benchmark cards, public authority learning materials, Academy materials, event materials, web pages, press materials, newsletters, social media posts, partner materials, sponsor materials, provider materials, public authority materials, and any other materials that may reasonably be understood by external audiences as issued, approved, supported, authored, co-authored, reviewed, hosted, or endorsed by the Corporation.

337.1.3 Public-Safe Publication shall preserve the distinction between public-good evidence support and execution; between research, methods, and observability and public authority action; between technical baselines and certification; between evidence records and recognition; between evidence support and finance-readiness; between public-safe information and public warning; between learning materials and regulated advice; and between Corporation publications and the separate authorities of The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Observatory, Nexus Rails, consortiums, national companies, Project SPVs, providers, sponsors, hosts, public authorities, universities, laboratories, communities, and other participants.

337.2 Public Trust Purpose.

337.2.1 Public-Safe Publication shall protect public trust by requiring that external outputs be truthful, records-supported, context-aware, non-exaggerated, non-alarmist, non-promotional where evidence neutrality is required, and clear about authorship, authority, limitations, uncertainty, version, date, public-safe status, correction path, and institutional role.

337.2.2 Public trust requires that the Corporation not publish or permit publication of materials that misrepresent evidence, suppress material limitations, imply unsupported certainty, overstate maturity, disguise conflicts, use technical language as authority theater, claim institutional status not held, or create false public reliance.

337.2.3 Public trust further requires that publication controls prevent sponsor capture, provider capture, donor capture, funder capture, public authority overclaim, finance overclaim, certification overclaim, recognition overclaim, procurement overclaim, media distortion, and public warning confusion.

337.3 Evidence Integrity Purpose.

337.3.1 Public-Safe Publication shall preserve evidence integrity by requiring that evidence claims be traceable to source records, evidence records, data records, methods records, review records, public-safe review records, and correction records sufficient for the publication class and reliance context.

337.3.2 Evidence shall not be presented as stronger, broader, more current, more complete, more representative, more generalizable, more verified, more validated, more official, more recognized, more finance-ready, or more conclusive than the underlying record supports.

337.3.3 Publications shall distinguish evidence, observation, inference, model output, expert judgment, public authority statement, community input, protected knowledge, benchmark result, synthetic data, scenario, forecast, assumption, and opinion.

337.4 Methods Integrity Purpose.

337.4.1 Public-Safe Publication shall preserve methods integrity by requiring that material methods, assumptions, limitations, data sources, classification rules, evaluation procedures, confidence approaches, exclusions, uncertainty treatment, and correction pathways be documented or referenced at a level appropriate to the publication class.

337.4.2 Methods shall not be presented as universally valid, formally standardized, certified, public authority approved, legally compliant, finance-grade, procurement-grade, clinically valid, operationally authoritative, or emergency-ready unless a separate competent record supports the specific claim and the publication accurately states its limits.

337.4.3 Where public-safe publication requires simplification, the simplified public-facing explanation shall not materially distort the method, conceal limitations, or create misleading public reliance.

337.5 Research Integrity Purpose.

337.5.1 Public-Safe Publication shall preserve research integrity by requiring honesty, accuracy, source transparency, limitation disclosure, uncertainty disclosure, conflict disclosure, ethical review where required or appropriate, human-subjects and participant safeguards, data and source integrity, reproducibility or replicability discussion where appropriate, correctionability, and prohibition of fabrication, falsification, plagiarism, suppression, selective reporting, or undisclosed material conflict.

337.5.2 Research publications shall distinguish preliminary work, working drafts, internal notes, public-safe summaries, peer-reviewed outputs, independently reviewed outputs, final reports, corrected outputs, superseded outputs, withdrawn outputs, retracted outputs, and archived outputs.

337.5.3 Sponsor, donor, funder, provider, host, public authority, university, laboratory, community, or partner participation shall be disclosed where material to interpretation and shall not impair research independence, publication integrity, correctionability, or limitation language.

337.6 Public-Good Technical Asset Integrity Purpose.

337.6.1 Public-Safe Publication shall preserve integrity of Public-Good Technical Assets by requiring that software releases, technical baselines, schemas, APIs, SDKs, technical profiles, reference architectures, dashboards, maps, datasets, benchmark libraries, evaluation harnesses, proof-receipt formats, model cards, system cards, dataset cards, benchmark cards, and related assets be versioned, licensed, documented, limitation-aware, security-reviewed where appropriate, public-safe reviewed where appropriate, and correctionable.

337.6.2 Technical asset publications shall not imply that an asset is certified, legally compliant, public authority adopted, procurement-approved, provider-preferred, finance-ready, recognized, rated, public-warning-ready, emergency-ready, operationally approved, or guaranteed.

337.6.3 Public technical materials shall include sufficient user guidance, known limitations, known issues, license status, security status where public-safe, dependency status where appropriate, release status, correction path, and deprecation or retirement status where applicable.

337.7 Public Authority Boundary Purpose.

337.7.1 Public-Safe Publication shall preserve public authority boundary discipline by ensuring that references to public authorities, public officials, regulators, procurement bodies, grantors, public finance actors, emergency management bodies, public health bodies, public safety bodies, public works bodies, utilities, ports, state actors, territorial actors, Tribal or Indigenous governments, and local authorities are accurate, capacity-classified, permission-aware, public-safe, and non-misleading.

337.7.2 No publication shall state or imply public authority adoption, official guidance, regulation, procurement approval, grant approval, public finance approval, public warning, emergency command, public-private partnership, sovereign decision, or governmental endorsement unless a competent public authority separately and lawfully creates that status and the publication accurately identifies it.

337.7.3 Public authority participation in a meeting, room, review, event, pilot, working group, learning session, comment process, data exchange, technical discussion, or publication shall not be described as official adoption or endorsement absent competent record.

337.8 Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, Certification, Recognition, and Professional Boundary Purpose.

337.8.1 Public-Safe Publication shall preserve finance, securities, insurance, lending, rating, public finance, procurement, certification, recognition, and professional boundaries by ensuring that Corporation outputs are not presented as investment advice, securities recommendation, broker-dealer activity, finder activity, underwriting approval, insurance approval, credit rating, bankability determination, public finance approval, procurement recommendation, legal advice, accounting advice, tax advice, clinical advice, engineering certification, professional certification, recognition, or regulated professional service.

337.8.2 No publication shall state or imply finance-readiness, insurance-readiness, investment suitability, bankability, rating, procurement eligibility, provider qualification, certification, recognition, GRF recognition, GRA finance-readiness, professional approval, or public authority approval unless a separate competent authority has lawfully issued that status and the publication accurately distinguishes it from GCRI US evidence, methods, observability, technical baseline, or public-good software activity.

337.8.3 Publications that may be read by capital actors, insurers, lenders, public finance bodies, procurement bodies, providers, sponsors, national companies, Project SPVs, or enterprise actors shall include limitation language sufficient to prevent regulated or commercial overclaim.

337.9 Data / AI / Cyber / Privacy Purpose.

337.9.1 Public-Safe Publication shall protect data governance, AI governance, cybersecurity, privacy, controlled-room duties, verifiable compute integrity, verifiable intelligence integrity, and secure release by requiring review of data rights, lawful basis, consent where required, permissions, classification, minimization, privacy risks, AI-use restrictions, cyber-sensitive information, infrastructure-sensitive information, model limitations, hallucination risk, prompt-injection risk, data leakage risk, secrets, credentials, repository risks, and public-safe output status.

337.9.2 No publication shall release personal information, sensitive personal information, health-sensitive data, public authority restricted data, cyber-sensitive data, infrastructure-sensitive data, controlled technology, confidential materials, privileged materials, secrets, keys, tokens, credentials, non-public vulnerability details, protected knowledge, or restricted datasets unless lawful, authorized, public-safe, and approved.

337.9.3 AI-assisted publications shall be human-reviewed, source-grounded, limitation-aware, hallucination-reviewed, bias-reviewed where appropriate, and recorded where material.

337.10 Civil Rights, Accessibility, Community Safeguards, Tribal / Indigenous, Local, Territorial, Cultural, Environmental, and Protected Knowledge Purpose.

337.10.1 Public-Safe Publication shall protect civil rights, accessibility, community safeguards, non-retaliation, protected participants, vulnerable populations, Tribal / Indigenous rights and protocols, local and territorial context, cultural and environmental safeguards, sacred knowledge, ecological knowledge, and protected knowledge.

337.10.2 Publications shall be reviewed where they may stigmatize, expose, misrepresent, classify, map, rank, compare, profile, or create risk for persons, communities, Tribal / Indigenous peoples, local groups, territories, protected classes, rights-bearing persons, or protected knowledge holders.

337.10.3 Public-safe publication measures may include aggregation, redaction, non-attribution, delayed publication, resolution reduction for maps, controlled annexes, restricted release, community review, Tribal or Indigenous review where applicable, accessibility review, language access review, grievance pathways, correction, or withdrawal.

337.11 United States All-States-and-Territories Public Representation Purpose.

337.11.1 Public-Safe Publication shall ensure that the Corporation’s United States all-states-and-territories role is represented accurately, without overstating legal presence, authority, qualification, operational capacity, public authority relationship, state-specific approval, territorial approval, public procurement eligibility, grant status, or regulatory status.

337.11.2 Publications shall avoid implying that the Corporation is a federal agency, state agency, territorial agency, local government, public authority, public procurement body, public warning authority, public finance body, regulator, certifier, or execution body.

337.11.3 State, District of Columbia, territorial, local, Tribal, and public authority references shall be jurisdictionally precise where material and shall avoid false uniformity across the United States.

337.12 North America Anchor Public Representation Purpose.

337.12.1 Public-Safe Publication shall represent the Corporation’s North America anchor role accurately as a public-good, non-executing, evidence, methods, observability, ontology, public-good technical asset, and public authority learning role within a broader Nexus architecture, without implying control over other entities, countries, public authorities, consortiums, national companies, Project SPVs, providers, sponsors, or enterprise actors.

337.12.2 North America references shall preserve cross-border legal separateness, entity separateness, no shared treasury, no agency, no partnership, no joint venture, no sovereign coordination claim, no treaty claim, no public authority delegation, and no execution authority.

337.12.3 Publications involving Canada, Mexico, the Caribbean, Arctic contexts, Indigenous cross-border contexts, or other North America interfaces shall be reviewed for cross-border data, privacy, public authority, protected knowledge, export-control, sanctions, and public-safe implications.

337.13 Nexus Role-Separation Purpose.

337.13.1 Public-Safe Publication shall preserve Nexus role separation among the Corporation, GCRI Canada, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, Nexus Observatory, Nexus Rails, Nexus Grid, Nexus Academy, consortiums, national companies, Project SPVs, qualified providers, sponsors, hosts, public authorities, universities, laboratories, communities, and other participants.

337.13.2 Publications shall distinguish GCRI US evidence, methods, observability, public-good software, open technical baseline, public authority learning, and public-safe publication functions from GRF recognition, GRA finance-readiness, standards authority, protocol authority, public authority action, consortium governance, national company execution, Project SPV execution, provider delivery, sponsor support, and enterprise-stack activity.

337.13.3 No publication shall merge identities, authorities, finances, liabilities, decision rights, records, mandates, or roles across Nexus entities unless a competent instrument expressly provides such relationship and the publication accurately states its limits.

337.14 Non-Execution Purpose.

337.14.1 Public-Safe Publication shall preserve the Corporation’s non-executing role by ensuring that publications do not direct, operate, procure, finance, insure, underwrite, certify, recognize, command, regulate, rank, approve, deploy, manage, supervise, or execute projects, infrastructure, emergency responses, public authority actions, provider services, investments, or enterprise activities.

337.14.2 Publications may support learning, evidence, methods, public-good software, technical baselines, public-safe reporting, observability, technical memory, correction, and public-benefit understanding, but shall not constitute operational instruction, public warning, emergency command, regulated advice, or execution authority.

337.15 Correctionability Purpose.

337.15.1 Public-Safe Publication shall be correctionable. Each material publication shall have a record-based path for challenge, correction, supersession, withdrawal, retraction, archive, notice, and downstream dependency review.

337.15.2 Correctionability shall require version control, publication date, responsible owner or custodian where appropriate, source linkage, limitation language, public-safe status, correction notices, supersession notices, and archive treatment.

337.15.3 The Corporation shall not conceal material errors, suppress corrections for reputational reasons, allow outdated materials to remain misleadingly current, or prevent good-faith challenge.

337.16 Public-Safe Publication Records.

337.16.1 The Corporation shall maintain Public-Safe Publication Records, including publication purpose records, public trust records, evidence integrity records, methods integrity records, research integrity records, public-good technical asset integrity records, public authority boundary records, finance / securities / insurance / lending / rating / public finance / procurement / certification / recognition / professional boundary records, data / AI / cyber / privacy records, civil rights / accessibility / community safeguards / Tribal / Indigenous / local / territorial / cultural / environmental / protected knowledge records, United States all-states-and-territories representation records, North America anchor representation records, Nexus role-separation records, non-execution records, correctionability records, publication approvals, publication holds, corrections, supersessions, withdrawals, retractions, and archive records.

---

Section 338. Publication Authority and Approval Matrix

338.1 Publication Authority Purpose.

338.1.1 Publication Authority shall ensure that materials issued, approved, released, circulated, posted, presented, submitted, filed, published, or externally shared by or on behalf of the Corporation are reviewed and approved by the competent authority appropriate to publication class, audience, risk, reliance, data sensitivity, public authority relevance, finance sensitivity, protected knowledge implications, technical complexity, legal exposure, and institutional significance.

338.1.2 Publication Authority shall preserve accuracy, legal compliance, public-safe publication, evidence integrity, research integrity, methods integrity, public-good technical asset integrity, role separation, sponsor non-control, provider neutrality, correctionability, and non-execution.

338.1.3 No person’s title, expertise, authorship, committee participation, repository access, donor relationship, sponsor relationship, public authority affiliation, provider role, media role, or partner status shall confer publication authority unless authority is expressly granted by Bylaw, Board action, officer delegation, policy, committee mandate, or other competent record.

338.2 Board Approval for Major Publications.

338.2.1 Board approval shall be required for major publications that materially affect institutional purpose, public reputation, public authority relationships, legal position, strategic direction, fiscal commitments, controlled public statements, entity role separation, major technical baselines, major public-good software releases, major whitepapers, major public authority-facing statements, major North America anchor representations, major Nexus architecture statements, or other high-significance external outputs.

338.2.2 The Board may approve a publication directly, approve a publication class, approve a publication framework, delegate approval to officers or committees, or require Board notification before or after release.

338.2.3 Board approval shall not excuse required legal, data, AI, cyber, privacy, public authority, protected knowledge, conflict, sponsor, provider, or public-safe review.

338.3 Officer Approval Within Delegation.

338.3.1 Officers may approve publications within delegated authority, including routine publications, public-safe summaries, technical notes, event materials, web content, public-good technical asset materials, Academy materials, partner materials, and other outputs consistent with Board-approved policies and publication approval matrices.

338.3.2 Officer approval shall be limited by subject matter, publication class, risk level, external audience, public authority relevance, data class, financial or procurement sensitivity, technical asset status, and any Board restrictions.

338.3.3 Officers shall escalate publication approval to the Board, counsel, committee, or other competent authority where publication risk exceeds delegated authority.

338.4 Committee Review Where Required.

338.4.1 Committee review shall be required where a publication falls within a committee’s mandate, including research integrity, evidence and methods, data governance, AI governance, cybersecurity, public-safe publication, public authority interface, community safeguards, protected knowledge, finance-boundary review, technical asset stewardship, or conflicts.

338.4.2 Committee review may be advisory, required before approval, required before release, or required after emergency release depending on policy and risk.

338.4.3 Committee review shall be recorded and shall identify comments, conditions, unresolved concerns, recusals, conflicts, limitations, and final recommendation where applicable.

338.5 Research Integrity Review Where Required.

338.5.1 Research Integrity Review shall be required for research reports, research summaries, whitepapers with research claims, externally circulated findings, peer-facing outputs, public authority learning materials based on research, Academy materials based on research, and any publication presenting original analysis or research findings.

338.5.2 Research Integrity Review shall assess research question, methodology, source support, ethics review where required, data integrity, participant protection, limitations, uncertainty, conflicts, sponsor influence, author contribution, plagiarism risk, reproducibility or replicability where appropriate, and correction path.

338.6 Evidence and Methods Review Where Required.

338.6.1 Evidence and Methods Review shall be required where a publication presents evidence claims, evidence classifications, methods, technical truth claims, observability outputs, public-safe dashboards, public-safe maps, proof receipts, benchmark results, evaluation results, technical baselines, or method notes.

338.6.2 Evidence and Methods Review shall assess source lineage, provenance, evidence class, method documentation, assumptions, confidence, uncertainty, limitations, public-safe status, challenge status, correction status, and risk of overclaim.

338.7 Data / AI / Cyber / Privacy Review Where Required.

338.7.1 Data / AI / Cyber / Privacy Review shall be required where a publication includes or relies upon datasets, personal information, rights-bearing data, health-sensitive data, public authority data, cyber-sensitive data, infrastructure-sensitive data, AI outputs, model records, inference records, compute workload records, dashboards, maps, controlled-room materials, software, repositories, vulnerabilities, or security-sensitive information.

338.7.2 Such review shall assess lawful basis, authority, permission, consent, notice, data classification, minimization, purpose limitation, AI-use restrictions, no-training requirements, hallucination risk, privacy risk, cyber risk, infrastructure exposure, secrets exposure, secure release, and incident implications.

338.8 Public Authority Boundary Review Where Required.

338.8.1 Public Authority Boundary Review shall be required where a publication references public authorities, public officials, public authority data, public programs, public procurement, grants, regulation, public finance, public health, emergency management, public safety, public works, utilities, ports, telecom systems, energy systems, water systems, food systems, or public-sector infrastructure.

338.8.2 Public Authority Boundary Review shall assess capacity classification, official-status risk, public records implications, procurement implications, grant implications, regulatory implications, public finance implications, public warning risk, emergency-command risk, public authority endorsement risk, and permission to reference names, marks, or participation.

338.9 Finance, Securities, Insurance, Lending, Rating, Public Finance, Procurement, Certification, Recognition, Provider-Preference, and Public Warning Boundary Review Where Required.

338.9.1 Boundary Review shall be required where a publication may be read as finance-readiness, securities-related communication, insurance-readiness, lending support, rating, public finance approval, procurement recommendation, certification, recognition, provider preference, public warning, emergency command, or professional approval.

338.9.2 Review shall assess whether the publication includes or implies investment suitability, bankability, underwriting support, capital readiness, GRA finance-readiness, GRF recognition, procurement eligibility, provider ranking, certification-like language, validation overclaim, verification overclaim, safety approval, public authority adoption, or emergency instruction.

338.9.3 Where risk exists, the publication shall be revised, limited, routed to a competent separate authority, restricted, delayed, or withheld.

338.10 Civil Rights, Accessibility, Community Safeguards, Tribal / Indigenous, and Protected Knowledge Review Where Required.

338.10.1 Civil Rights, Accessibility, Community Safeguards, Tribal / Indigenous, and Protected Knowledge Review shall be required where a publication may affect protected classes, rights-bearing persons, vulnerable populations, communities, Tribal or Indigenous peoples, local or territorial groups, cultural knowledge, environmental knowledge, sacred knowledge, ecological knowledge, protected knowledge, public-safe mapping, or community trust.

338.10.2 Review shall assess discriminatory impact, stigmatization, accessibility, language access, retaliation risk, exposure risk, attribution, non-attribution, consent, protocol permission, public-safe mapping resolution, AI-use restrictions, cultural context, environmental context, and grievance pathways.

338.11 Legal, Compliance, Sanctions, Export-Control, Controlled Technology, and Professional Boundary Review Where Required.

338.11.1 Legal, Compliance, Sanctions, Export-Control, Controlled Technology, and Professional Boundary Review shall be required where publication may implicate legal obligations, regulated professional advice, contracts, grants, donor restrictions, sponsor restrictions, public authority restrictions, export-control, sanctions, controlled technology, intellectual property, litigation, privilege, confidentiality, tax, charitable compliance, lobbying, procurement, privacy, cybersecurity, or other regulated context.

338.11.2 Review shall ensure that the publication does not unlawfully disclose restricted materials, provide regulated professional advice without authority, violate sanctions or export-control laws, waive privilege, breach confidentiality, infringe IP, or create legal obligations not approved by competent authority.

338.12 Sponsor, Donor, Funder, Provider, Host, Partner, and Conflict Review Where Required.

338.12.1 Sponsor, Donor, Funder, Provider, Host, Partner, and Conflict Review shall be required where a publication references, is funded by, is supported by, is hosted by, is co-branded with, includes contributions from, or may materially affect such actor.

338.12.2 Review shall assess conflicts, disclosure, sponsor non-control, provider neutrality, donor restrictions, funder restrictions, host restrictions, partner authority, co-branding rules, mark use, commercial-use boundaries, public authority implications, and publication independence.

338.12.3 Sponsors, donors, funders, providers, hosts, or partners may review factual references to themselves where appropriate, but shall not control findings, limitations, corrections, public-safe framing, or publication approval.

338.13 Publication Approval Matrix.

338.13.1 The Corporation shall maintain a Publication Approval Matrix identifying publication classes, approval authorities, required reviews, optional reviews, escalation thresholds, emergency hold authority, release channels, record requirements, correction pathways, and archive rules.

338.13.2 The Publication Approval Matrix shall be risk-based and may classify publications by institutional significance, public audience, public authority relevance, data sensitivity, AI use, cyber sensitivity, infrastructure sensitivity, finance sensitivity, certification risk, recognition risk, procurement risk, protected knowledge risk, sponsor or provider involvement, and technical asset status.

338.13.3 The Publication Approval Matrix shall be reviewed periodically and updated when law, institutional structure, Nexus role separation, publication practices, data classes, AI tools, cybersecurity risk, public authority relationships, or public-safe publication risk changes.

338.14 Emergency Publication Hold Authority.

338.14.1 The Board, an authorized officer, counsel, publication authority, data governance authority, AI governance authority, cybersecurity authority, public authority boundary reviewer, protected knowledge reviewer, or other competent authority may impose an Emergency Publication Hold where release may cause material harm, legal violation, privacy breach, security exposure, public authority confusion, protected knowledge exposure, finance overclaim, certification overclaim, recognition overclaim, procurement overclaim, public warning confusion, or misleading reliance.

338.14.2 Emergency Publication Holds may suspend publication, remove public access, disable public links, pause distribution, restrict dashboards, restrict maps, hold datasets, hold software releases, hold press statements, hold social media, or hold partner materials pending review.

338.14.3 Emergency Publication Holds shall be recorded, reviewed, and resolved through correction, approval, restriction, withdrawal, retraction, or release.

338.15 No Publication by Unauthorized Person.

338.15.1 No director, officer, employee, contractor, fellow, advisor, volunteer, contributor, maintainer, committee member, sponsor, donor, funder, provider, host, partner, public authority participant, media participant, national company participant, Project SPV participant, or other person shall publish, release, post, distribute, submit, file, approve, co-brand, or publicly represent Corporation materials without authority.

338.15.2 Unauthorized publication shall be subject to correction, takedown, access restriction, public clarification, contract remedy, role restriction, termination, legal review, or referral where appropriate.

338.16 Publication Approval Records.

338.16.1 The Corporation shall maintain Publication Approval Records, including publication authority records, Board approval records, officer approval records, committee review records, research integrity review records, evidence and methods review records, data / AI / cyber / privacy review records, public authority boundary review records, finance / securities / insurance / lending / rating / public finance / procurement / certification / recognition / provider-preference / public warning boundary review records, civil rights / accessibility / community safeguards / Tribal / Indigenous / protected knowledge review records, legal / compliance / sanctions / export-control / controlled technology / professional boundary review records, sponsor / donor / funder / provider / host / partner / conflict review records, Publication Approval Matrix records, Emergency Publication Hold records, unauthorized publication records, publication approvals, denials, conditions, corrections, withdrawals, retractions, and archive records.

---

Section 339. Classes of Publications and External Outputs

339.1 Publication Classification Purpose.

339.1.1 Publication Classification shall ensure that each external output is governed according to its class, purpose, audience, authority, risk, review requirements, approval path, public-safe status, correction path, and archive treatment.

339.1.2 Publication Classification shall prevent informal materials, drafts, presentations, dashboards, maps, datasets, software releases, partner materials, sponsor materials, public authority materials, social media posts, or event materials from bypassing appropriate review merely because they are short, visual, technical, preliminary, operational, conversational, co-branded, or distributed through nontraditional channels.

339.1.3 Publication classes shall be interpreted by substance and risk, not by file format, medium, platform, title, or author preference.

339.2 Board-Level Publications.

339.2.1 Board-Level Publications include bylaws, charters, constitutional instruments, major governance frameworks, major institutional position statements, annual reports, major strategic whitepapers, major public authority-facing statements, major Nexus role-separation statements, major North America anchor statements, major risk governance statements, and other publications designated by the Board.

339.2.2 Board-Level Publications shall require Board approval or Board-delegated approval under recorded authority and shall receive legal, public-safe, role-separation, conflict, and other reviews appropriate to the subject matter.

339.2.3 Board-Level Publications shall be versioned, archived, correctionable, and clearly distinguished from drafts, committee materials, working papers, and staff-level outputs.

339.3 Research Reports.

339.3.1 Research Reports include publications presenting research findings, analysis, evidence synthesis, methodological results, empirical observations, systemic risk analysis, resilience analysis, technology analysis, public-benefit R&D results, or public authority learning findings.

339.3.2 Research Reports shall receive research integrity review, evidence and methods review, data / AI / cyber / privacy review where applicable, ethics review where required or appropriate, conflict review, sponsor or funder disclosure review, public-safe review, and correction path approval.

339.3.3 Research Reports shall disclose limitations, uncertainty, scope, source support, methodology, conflicts, sponsor or funder support where material, and non-execution boundaries.

339.4 Whitepapers.

339.4.1 Whitepapers include substantial explanatory, architectural, technical, institutional, legal, policy-adjacent, ecosystem, public-good, Nexus-related, or strategic publications intended to explain frameworks, structures, methods, technical assets, public-good architecture, or institutional design.

339.4.2 Whitepapers shall be reviewed for accuracy, institutional authority, role separation, technical support, public authority boundaries, finance boundaries, certification boundaries, recognition boundaries, procurement neutrality, provider neutrality, public-safe claims, and correctionability.

339.4.3 Whitepapers shall not be used to create legal obligations, public authority adoption, procurement mandates, finance-readiness, certification, recognition, or execution commitments unless separately approved by competent authority and accurately stated.

339.5 Technical Notes.

339.5.1 Technical Notes include concise or focused publications describing technical concepts, implementation patterns, design considerations, software behavior, schemas, APIs, SDKs, dashboards, maps, observability methods, AI governance methods, cybersecurity controls, verifiable compute workflows, proof receipts, or public-good technical assets.

339.5.2 Technical Notes shall be reviewed for technical accuracy, limitation language, security implications, data / AI / cyber / privacy implications, public-safe output risk, license status, dependency status where relevant, and correction path.

339.5.3 Technical Notes shall not be represented as standards, certifications, legal compliance approvals, procurement specifications, public authority guidance, finance-readiness determinations, or provider endorsements.

339.6 Method Notes.

339.6.1 Method Notes include publications describing methods, assumptions, evidence classification approaches, data quality approaches, observability methods, evaluation methods, benchmark methods, dashboard methods, map methods, AI review methods, cyber review methods, public-safe publication methods, and correction methods.

339.6.2 Method Notes shall identify scope, intended use, prohibited use, assumptions, limitations, source dependencies, validation status where applicable, review status, uncertainty, and correction path.

339.6.3 Method Notes shall not be presented as universally valid, formally standardized, certified, legally compliant, procurement-ready, finance-ready, or public authority adopted unless separately supported by competent record.

339.7 Evidence Packs.

339.7.1 Evidence Packs include organized records, source materials, metadata, provenance, evidence classifications, review notes, proof receipts, public-safe summaries, controlled annexes, datasets, dashboards, maps, or other materials assembled to support a defined evidence purpose.

339.7.2 Evidence Packs shall be classified by access status, public-safe status, data class, public authority status, protected knowledge status, confidence, limitations, and correction path.

339.7.3 Evidence Packs may support learning, review, technical understanding, GRF-facing inputs, GRA-facing inputs, Docket inputs, Grid inputs, or public-safe publication, but shall not themselves constitute recognition, finance-readiness, certification, procurement approval, public authority decision, public warning, emergency command, rating, or provider preference.

339.8 Public-Safe Summaries.

339.8.1 Public-Safe Summaries include externally shareable summaries of research, evidence, methods, observability, technical assets, dashboards, maps, controlled-room outputs, public authority learning, or protected materials prepared to communicate accurate meaning without unsafe disclosure.

339.8.2 Public-Safe Summaries shall be reviewed for accuracy, limitation language, omission risk, overgeneralization, public authority boundary, finance boundary, certification boundary, recognition boundary, procurement neutrality, public warning risk, privacy, cybersecurity, infrastructure sensitivity, protected knowledge, accessibility, and correction path.

339.8.3 Public-Safe Summaries shall not create false reassurance, false alarm, false absence of risk, false readiness, false approval, false recognition, false finance-readiness, false certification, or false public authority status.

339.9 Controlled Annexes.

339.9.1 Controlled Annexes include restricted, confidential, sealed, technical, data-rich, vulnerability-relevant, public authority, protected knowledge, cyber-sensitive, infrastructure-sensitive, finance-sensitive, or rights-bearing materials attached to or associated with a public or controlled publication.

339.9.2 Controlled Annexes shall be separately classified, access-controlled, logged where appropriate, and subject to controlled-room or restricted-release rules where required.

339.9.3 Public publications referencing Controlled Annexes shall not disclose restricted contents and shall describe them only in public-safe terms.

339.10 Dashboards.

339.10.1 Dashboards include visual, interactive, static, internal, controlled, or public-facing interfaces displaying evidence, observability data, indicators, resilience information, technical asset status, data quality, benchmark outputs, maps, or other information.

339.10.2 Dashboards shall be reviewed for data rights, source lineage, accuracy, timeliness, public-safe status, accessibility, privacy, cyber sensitivity, infrastructure sensitivity, protected knowledge, public authority boundary, public warning risk, finance overclaim, certification overclaim, recognition overclaim, procurement overclaim, and correction path.

339.10.3 Dashboard indicators, scores, colors, statuses, alerts, filters, labels, or outputs shall not be represented as public warnings, emergency commands, ratings, certifications, recognitions, finance-readiness, procurement approvals, provider preferences, or public authority decisions.

339.11 Maps.

339.11.1 Maps include geospatial, territorial, infrastructure, environmental, public health, risk, resilience, observability, dashboard, digital twin, AI-RAN / O-RAN, DePIN, DLT, community, public authority, or public-safe mapping outputs.

339.11.2 Maps shall be reviewed for geospatial accuracy, resolution sensitivity, sensitive-location exposure, infrastructure exposure, community exposure, protected knowledge, public-safe mapping, public authority restrictions, data rights, privacy, accessibility, civil rights, public warning risk, and correction path.

339.11.3 Maps shall not be treated as operational navigation, emergency command, evacuation guidance, public warning, public authority decision, investment map, procurement map, rating map, certification map, recognition map, or provider-ranking map.

339.12 Datasets.

339.12.1 Datasets include structured, semi-structured, unstructured, derived, synthetic, benchmark, evaluation, public-safe, controlled, internal, restricted, or open data materials released or externally shared by the Corporation.

339.12.2 Datasets shall be reviewed for ownership, license, data rights, lawful basis, authority, consent where required, privacy, public authority restrictions, AI-use restrictions, protected knowledge, cyber sensitivity, infrastructure sensitivity, quality, bias, documentation, dataset card, retention, deletion, and correction path.

339.12.3 Dataset release shall not imply rating, certification, recognition, finance-readiness, procurement approval, public authority decision, public warning, emergency command, or provider preference.

339.13 Software Releases.

339.13.1 Software Releases include public, internal, controlled, restricted, experimental, pilot, patch, security, emergency, deprecated, retired, or archived releases of Corporation software or software-adjacent assets.

339.13.2 Software Releases shall follow release governance, secure development, license review, dependency review, vulnerability review, secrets review, documentation review, public-safe output review, and correction path requirements.

339.13.3 Software outputs shall not be represented as certification, public authority decision, public warning, emergency command, procurement approval, finance-readiness, recognition, rating, legal compliance approval, or provider preference.

339.14 Open Technical Baselines.

339.14.1 Open Technical Baselines include public-good reference materials setting out non-executing technical structures, fields, methods, schemas, profiles, governance expectations, documentation conventions, public-safe language, or interoperability patterns.

339.14.2 Open Technical Baselines shall be reviewed for scope, version, effective date, limitation statement, license, public-safe status, public authority boundaries, finance boundaries, certification boundaries, recognition boundaries, procurement neutrality, provider neutrality, and correction path.

339.14.3 Open Technical Baselines shall not be represented as certification, procurement mandate, legal compliance approval, public authority adoption, provider preference, finance-readiness, recognition, rating, public warning, emergency command, or execution authority.

339.15 Reference Architectures.

339.15.1 Reference Architectures include non-executing design-support publications describing technical, institutional, data, AI, cyber, observability, controlled-room, public authority learning, verifiable compute, verifiable intelligence, or Nexus-compatible structures.

339.15.2 Reference Architectures shall identify scope, assumptions, intended use, prohibited use, dependencies, limitations, public-safe status, security considerations, privacy considerations, protected knowledge considerations, and correction path.

339.15.3 Reference Architectures shall not be represented as engineering approval, enterprise deployment approval, public authority approval, procurement specification, certification, recognition, finance-readiness, rating, public warning, emergency command, or operational instruction.

339.16 APIs, SDKs, Schemas, Technical Profiles, and Test Harnesses.

339.16.1 APIs, SDKs, Schemas, Technical Profiles, and Test Harnesses include technical interface and validation materials released or externally shared to support interoperability, technical learning, implementation, evaluation, public-good software, proof receipts, evidence formats, observability formats, or Nexus-compatible structures.

339.16.2 Such materials shall be reviewed for version, license, scope, security, data handling, dependency status, validation status, public-safe limitations, compatibility claim risk, benchmark-gaming risk, protected knowledge, and correction path.

339.16.3 Passing a test harness, using a schema, implementing an API, using an SDK, or aligning with a technical profile shall not create certification, recognition, finance-readiness, procurement approval, public authority adoption, provider qualification, rating, or guarantee.

339.17 Public Authority Learning Materials.

339.17.1 Public Authority Learning Materials include briefings, explainers, slides, dashboards, maps, evidence literacy guides, methods literacy guides, technical baseline explainers, public-safe summaries, controlled-room materials, and training materials prepared for or involving public authorities.

339.17.2 Such materials shall be reviewed for public authority boundary, capacity classification, public records considerations, procurement implications, grant implications, public finance implications, public warning risk, emergency-command risk, public authority data restrictions, confidentiality, and correction path.

339.17.3 Public Authority Learning Materials shall not constitute official guidance, regulation, procurement criteria, grant criteria, public finance approval, public warning, emergency command, sovereign decision, or public authority adoption unless separately and lawfully issued by the competent public authority.

339.18 Academy, Training, Fellowship, and Workforce Materials.

339.18.1 Academy, Training, Fellowship, and Workforce Materials include curricula, modules, manuals, toolkits, exercises, case studies, evaluation materials, orientation materials, workshop materials, fellowship materials, workforce guides, and learning resources.

339.18.2 Such materials shall be reviewed for accuracy, accessibility, copyright, data rights, public authority boundaries, professional boundary limits, AI-use limits, cyber-sensitive content, protected knowledge, public-safe framing, and correction path.

339.18.3 Training materials shall not be represented as professional licensure, certification, legal advice, clinical advice, engineering approval, public authority training mandate, procurement qualification, finance-readiness, recognition, or employment guarantee unless separately and lawfully supported.

339.19 Event Materials, Speeches, Presentations, Decks, Articles, Blog Posts, Web Pages, Press Releases, Media Statements, Social Media Posts, Newsletters, and Public Notices.

339.19.1 Event materials, speeches, presentations, decks, articles, blog posts, web pages, press releases, media statements, social media posts, newsletters, and public notices shall be treated as publications subject to appropriate review, even where informal, time-sensitive, visual, short-form, conversational, promotional, or platform-native.

339.19.2 Such materials shall be reviewed according to risk for institutional accuracy, public authority boundary, finance boundary, certification boundary, recognition boundary, procurement neutrality, provider neutrality, sponsor disclosure, public-safe claims, protected knowledge, privacy, cybersecurity, accessibility, and correction path.

339.19.3 Rapid or short-form publication shall not excuse unsupported claims, unauthorized mark use, false public authority implication, false finance-readiness implication, false recognition implication, false certification implication, public warning confusion, or publication of restricted materials.

339.20 Partner, Sponsor, Donor, Provider, Host, Public Authority, University, Laboratory, Community, Tribal / Indigenous, Civil Society, and Media Materials Referencing GCRI US.

339.20.1 Materials prepared by or with partners, sponsors, donors, providers, hosts, public authorities, universities, laboratories, communities, Tribal / Indigenous bodies, civil society organizations, or media that reference the Corporation shall be reviewed where the Corporation is asked to approve, quote, co-brand, link to, distribute, host, correct, or otherwise support the materials.

339.20.2 Such materials shall accurately describe the Corporation’s role, avoid false endorsement, avoid sponsor or provider control, preserve public authority boundaries, preserve GRF and GRA role separation, respect protected knowledge, comply with mark-use rules, and include limitation language where necessary.

339.20.3 The Corporation may require revision, disclaimer, removal, correction, takedown, public clarification, or refusal to participate where external materials misstate the Corporation’s role or create unsafe reliance.

339.21 Publication Class Records.

339.21.1 The Corporation shall maintain Publication Class Records, including publication classification purpose records, Board-Level Publication records, Research Report records, Whitepaper records, Technical Note records, Method Note records, Evidence Pack records, Public-Safe Summary records, Controlled Annex records, Dashboard records, Map records, Dataset records, Software Release records, Open Technical Baseline records, Reference Architecture records, API / SDK / Schema / Technical Profile / Test Harness records, Public Authority Learning Material records, Academy / Training / Fellowship / Workforce Material records, event / speech / presentation / deck / article / blog / web page / press release / media statement / social media / newsletter / public notice records, external referencing material records, review records, approval records, correction records, withdrawal records, retraction records, and archive records.

Section 340. Access Classes: Public, Public-Safe, Controlled, Confidential, Restricted, Public Authority, Community-Protected, and Archived

340.1 Access Classification Purpose.

340.1.1 Access Classification shall govern how publications, external outputs, technical assets, datasets, dashboards, maps, evidence packs, controlled annexes, software releases, repositories, public authority materials, public-safe summaries, Academy materials, media materials, partner materials, sponsor materials, provider materials, and other Corporation outputs are made available, withheld, restricted, sealed, redacted, released, withdrawn, corrected, or archived.

340.1.2 Access Classification shall protect public trust, evidence integrity, methods integrity, research integrity, public-good technical asset integrity, public authority trust, privacy, cybersecurity, infrastructure protection, rights-bearing persons, protected knowledge, community safeguards, sponsor non-control, provider neutrality, public-safe publication, correctionability, and non-execution.

340.1.3 Access Classification shall be determined by substance, risk, rights, authority, law, contract, data class, audience, public-safe status, public authority implications, publication reliance, and safeguards requirements, and not merely by the label, platform, file type, author, distribution channel, urgency, or audience expectation.

340.1.4 A publication or output may have multiple access components, including a public summary, controlled annex, restricted dataset, sealed vulnerability record, public authority room, internal method record, and archived historical version, each governed by its own access classification.

340.2 Public Access.

340.2.1 Public Access means material approved for general public availability without individualized access restriction, subject to applicable copyright, license, attribution, non-endorsement, limitation language, public-safe framing, version control, correction path, and archive status.

340.2.2 Public Access shall be permitted only after review confirms that the material does not improperly disclose personal information, sensitive personal information, health-sensitive data, public authority restricted data, cyber-sensitive data, infrastructure-sensitive data, controlled technology, export-controlled material, confidential information, privileged information, community-protected data, Tribal / Indigenous knowledge, protected knowledge, secrets, keys, tokens, credentials, non-public vulnerability details, or other restricted material.

340.2.3 Public Access materials shall include publication date, version, authoring or issuing authority where appropriate, limitation language where appropriate, correction path, and supersession or archive status where applicable.

340.3 Public-Safe Access.

340.3.1 Public-Safe Access means material approved for public or external release only after public-safe review confirms that the material is accurate enough for the intended audience, does not create unsafe reliance, does not overdisclose sensitive information, and includes necessary limitations, redactions, aggregations, disclaimers, and boundary language.

340.3.2 Public-Safe Access may apply to summaries, dashboards, maps, reports, public authority learning materials, evidence packs, technical baselines, software documentation, datasets, public-good technical assets, press materials, social media posts, and other external outputs.

340.3.3 Public-Safe Access does not mean unrestricted technical completeness, official status, certification, recognition, finance-readiness, procurement approval, public authority adoption, rating, public warning, emergency command, or operational instruction.

340.3.4 Public-Safe Access materials shall be reviewed for risk of false reassurance, false alarm, public authority confusion, finance overclaim, certification overclaim, recognition overclaim, procurement overclaim, provider preference, stigmatization, protected knowledge exposure, and downstream misuse.

340.4 Internal Access.

340.4.1 Internal Access means material available within the Corporation or among authorized internal participants for legitimate governance, research, evidence, methods, technical, administrative, legal, financial, publication, or operational support purposes.

340.4.2 Internal Access shall not authorize external sharing, public release, AI processing, repository publication, partner circulation, sponsor circulation, provider circulation, public authority circulation, or media use unless separately approved under this Article.

340.4.3 Internal materials shall not be assumed public-safe merely because they are polished, accurate, non-confidential in tone, or shared broadly within internal channels.

340.5 Controlled Access.

340.5.1 Controlled Access means material made available only to authorized persons, roles, rooms, systems, or entities under defined purpose, access conditions, logging where appropriate, confidentiality, output review, public-safe restrictions, and correction path.

340.5.2 Controlled Access may apply to controlled annexes, evidence packs, datasets, public authority materials, technical baselines under review, software release candidates, dashboards, maps, controlled-room exhibits, protected knowledge materials, cyber-sensitive materials, infrastructure-sensitive materials, and pre-publication materials.

340.5.3 Controlled Access shall identify permitted users, permitted purposes, prohibited uses, AI-use restrictions, copying restrictions, download restrictions, onward-transfer restrictions, citation restrictions, publication restrictions, retention obligations, deletion obligations, and closeout requirements where applicable.

340.6 Confidential Access.

340.6.1 Confidential Access means material protected by confidentiality obligations, contractual restrictions, internal sensitivity, privilege-adjacent sensitivity, donor or sponsor confidentiality, provider confidentiality, personnel sensitivity, financial sensitivity, research sensitivity, commercial sensitivity, public authority confidentiality, or institutional trust obligations.

340.6.2 Confidential Access materials shall be disclosed only to persons with authorized purpose and need to know and shall be protected against unauthorized release, AI processing, repository exposure, public indexing, screenshotting where restricted, and onward transfer.

340.6.3 Confidential Access shall not be used to conceal misconduct, suppress required correction, avoid lawful notification, prevent public-safe transparency, or obscure material conflicts where disclosure is required.

340.7 Restricted Access.

340.7.1 Restricted Access means material requiring heightened protection because unauthorized access, use, publication, transfer, AI processing, mapping, embedding, or disclosure could create legal, privacy, cyber, infrastructure, public authority, protected knowledge, community, financial, safety, export-control, sanctions, or public-safe risk.

340.7.2 Restricted Access materials may include personal information, sensitive personal information, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, controlled technology, export-controlled material, non-public vulnerability details, secrets, public authority restricted data, protected knowledge, controlled-room materials, sealed legal materials, and high-risk datasets.

340.7.3 Restricted Access shall require need-to-know authorization, access logging where feasible, periodic review, secure storage, secure transfer, AI-use restriction, publication restriction, and incident escalation for unauthorized access.

340.8 Public Authority Access.

340.8.1 Public Authority Access means controlled access provided to public authorities, public officials, regulators, procurement personnel, grantors, public finance readers, emergency management bodies, public health bodies, public safety bodies, public works bodies, utilities, ports, or other public-sector actors under recorded capacity, purpose, authority, and limitation.

340.8.2 Public Authority Access shall be capacity-classified and shall not imply official adoption, endorsement, procurement approval, grant approval, public finance approval, regulatory approval, public warning, emergency command, sovereign decision, or public-private partnership.

340.8.3 Materials provided through Public Authority Access shall be reviewed for public records, confidentiality, privacy, cybersecurity, public authority data restrictions, procurement sensitivity, public-safe communication, and correction path where applicable.

340.9 Research Access.

340.9.1 Research Access means access granted for approved research, peer review, method review, replication, validation, academic collaboration, public-benefit R&D, or evidence review under defined authority and restrictions.

340.9.2 Research Access shall be governed by research protocols, ethics review where required or appropriate, confidentiality, data rights, participant protections, publication review, AI-use restrictions, attribution, non-attribution, withdrawal, correction, and retention requirements.

340.9.3 Research Access shall not permit commercial use, public release, AI training, public authority use, finance-facing use, provider development, sponsor benefit, or external sharing unless expressly authorized.

340.10 Clean-Room Access.

340.10.1 Clean-Room Access means access to a controlled analysis environment designed to permit review, comparison, computation, or learning while preventing unauthorized disclosure, copying, extraction, re-identification, linkage, AI training, or uncontrolled export of underlying data.

340.10.2 Clean-Room Access shall be governed by a room charter or equivalent record identifying participants, data classes, permitted analysis, prohibited uses, output review, logging, no-download conditions, AI-use restrictions, public-safe review, and closeout.

340.10.3 Clean-Room Access shall not constitute endorsement, certification, recognition, finance-readiness, procurement approval, public authority adoption, provider preference, rating, or execution authority.

340.11 Data-Room Access.

340.11.1 Data-Room Access means access to defined datasets, records, evidence packs, technical materials, public authority materials, diligence-supporting materials, or controlled annexes under structured access controls and review requirements.

340.11.2 Data-Room Access shall identify purpose, participants, exhibits, access duration, permitted use, prohibited use, confidentiality, public authority boundary, finance boundary, publication restriction, AI-use restriction, download restriction, output review, and correction path.

340.11.3 Data-Room Access shall not convert evidence materials into finance-readiness, investment advice, rating, underwriting approval, public finance approval, certification, recognition, procurement approval, provider preference, public authority decision, or guarantee.

340.12 Evidence-Room Access.

340.12.1 Evidence-Room Access means access to evidence records, source materials, provenance records, method records, proof receipts, challenge materials, correction records, review notes, controlled annexes, or public-safe publication support materials under evidence integrity controls.

340.12.2 Evidence-Room Access shall preserve source restrictions, reviewer independence, custody, traceability, public-safe handling, limitation language, and correctionability.

340.12.3 Evidence-Room Access shall not be represented as recognition, finance-readiness, certification, procurement approval, public authority decision, public warning, emergency command, rating, or provider preference.

340.13 No-Download Room Access.

340.13.1 No-Download Room Access means access permitting viewing, querying, review, or limited interaction while prohibiting downloading, copying, scraping, exporting, photographing, embedding, training, transferring, or otherwise extracting underlying materials except as expressly permitted.

340.13.2 No-Download Room Access may be required for sensitive infrastructure materials, cyber-sensitive materials, public authority data, controlled technology, health-sensitive data, rights-bearing data, commercially sensitive data, finance-sensitive data, protected knowledge, benchmark answer keys, and non-public vulnerability details.

340.13.3 No-Download restrictions shall be supplemented by participant obligations, technical controls where feasible, logging, output review, watermarking where appropriate, access revocation, and incident escalation.

340.14 Community-Protected Access.

340.14.1 Community-Protected Access means access governed by community safeguards, non-extraction principles, non-retaliation, contextual integrity, attribution or non-attribution rules, public-safe mapping limits, grievance pathways, consent or permission conditions where applicable, and correction or withdrawal rights where appropriate.

340.14.2 Community-Protected Access shall be required where publication, mapping, AI processing, transfer, commercial use, or external sharing could expose, stigmatize, exploit, misrepresent, decontextualize, or create retaliation risk for a community.

340.14.3 Community-Protected Access shall not be expanded to sponsors, providers, public authorities, researchers, media, or enterprise actors merely because the material may be useful to them.

340.15 Tribal / Indigenous, Local, Territorial, Cultural, Environmental, and Protected Knowledge Access.

340.15.1 Tribal / Indigenous, local, territorial, cultural, environmental, sacred, ecological, and Protected Knowledge Access shall be governed by lawful authority, protocol permission where applicable, sovereignty-aware safeguards, community review where appropriate, attribution or non-attribution rules, withdrawal or restriction pathways, AI-use restrictions, mapping restrictions, publication restrictions, and transfer restrictions.

340.15.2 Such access shall be granted only where the Corporation has a recorded basis to permit access and where safeguards are sufficient for the knowledge type, community context, territorial context, cultural context, environmental context, and public-safe risk.

340.15.3 Such materials shall not be treated as open data, ordinary research data, public authority data, public-safe evidence, model-training data, or general technical material unless competent review supports that classification.

340.16 Finance-Sensitive Access.

340.16.1 Finance-Sensitive Access means access to non-public financial, donor, sponsor, funder, grant, budget, bank, capital-reader, insurance, underwriting, public finance, national company, Project SPV, or finance-facing materials.

340.16.2 Finance-Sensitive Access shall be governed by confidentiality, conflict review, lawful purpose, role separation, donor or sponsor restrictions, GRA boundary discipline, public finance boundary discipline, securities boundary discipline, lending boundary discipline, insurance boundary discipline, rating boundary discipline, and non-execution.

340.16.3 Finance-Sensitive Access shall not permit persons to represent Corporation materials as finance-readiness, investment suitability, rating, underwriting approval, public finance approval, bankability, procurement approval, certification, recognition, or guarantee.

340.17 Cyber-Sensitive and Infrastructure-Sensitive Access.

340.17.1 Cyber-Sensitive and Infrastructure-Sensitive Access means access to vulnerability details, security architecture, threat models, logs, telemetry, credentials, secrets, incident records, critical infrastructure dependencies, geospatial layers, digital twin outputs, AI-RAN / O-RAN signals, telecom materials, energy materials, water materials, port materials, public safety materials, emergency systems materials, or other materials that could enable harm if misused.

340.17.2 Such access shall require need-to-know, security review, public-safe review, no-download or controlled-room conditions where appropriate, logging where feasible, AI-use restriction, and coordinated disclosure discipline where vulnerabilities are involved.

340.17.3 Such materials shall not be published, mapped, summarized, benchmarked, or released in a way that enables targeting, exploitation, public panic, false reassurance, public warning confusion, emergency command confusion, or infrastructure harm.

340.18 Archived Access.

340.18.1 Archived Access means access to historical, superseded, corrected, deprecated, withdrawn, retracted, retired, sealed, or preserved materials maintained for technical memory, legal compliance, auditability, correctionability, evidence integrity, research integrity, or institutional history.

340.18.2 Archived materials shall be labeled by status and shall not be presented as current, approved, recommended, public-safe, secure, valid, operative, or authoritative unless that status remains accurate.

340.18.3 Archived Access may be public, internal, controlled, confidential, restricted, sealed, or no-download depending on the content and reason for archive.

340.19 Reclassification, Sealing, Redaction, Release, or Withdrawal.

340.19.1 Access classifications shall be reviewed and revised where law, contract, data rights, public authority restrictions, public-safe status, protected knowledge obligations, cybersecurity risk, infrastructure risk, privacy risk, evidence status, correction status, or publication purpose changes.

340.19.2 Reclassification may include release to public access, public-safe redaction, movement to controlled access, sealing, restriction, archive, withdrawal, retraction, takedown, or deletion where lawful and required.

340.19.3 Reclassification shall preserve historical traceability where lawful and shall not be used to conceal errors, suppress corrections, evade public authority obligations, avoid breach notice, or hide misconduct.

340.20 Access Classification Records.

340.20.1 The Corporation shall maintain Access Classification Records, including access classification purpose records, Public Access records, Public-Safe Access records, Internal Access records, Controlled Access records, Confidential Access records, Restricted Access records, Public Authority Access records, Research Access records, Clean-Room Access records, Data-Room Access records, Evidence-Room Access records, No-Download Room Access records, Community-Protected Access records, Tribal / Indigenous / local / territorial / cultural / environmental / protected knowledge access records, Finance-Sensitive Access records, Cyber-Sensitive and Infrastructure-Sensitive Access records, Archived Access records, reclassification records, sealing records, redaction records, release records, withdrawal records, and archive records.

---

Section 341. Claims Substantiation Requirement

341.1 Claims Substantiation Purpose.

341.1.1 Claims Substantiation shall require every material public claim, external claim, publication claim, technical claim, evidence claim, method claim, research claim, dashboard claim, map claim, software claim, dataset claim, model claim, benchmark claim, observability claim, public authority claim, Nexus claim, compatibility claim, public-safe claim, and institutional claim to be supported by sufficient records, review, limitation language, and correction path appropriate to its substance and reliance risk.

341.1.2 Claims Substantiation shall prevent unsupported assertions, institutional overclaim, technical overclaim, sponsor overclaim, provider overclaim, public authority overclaim, finance overclaim, certification overclaim, recognition overclaim, procurement overclaim, public warning confusion, emergency command confusion, and unsafe public reliance.

341.1.3 The level of substantiation required shall be proportionate to the claim’s scope, audience, materiality, public authority relevance, finance relevance, technical reliance, data sensitivity, protected knowledge implications, civil rights implications, and potential harm.

341.2 No Public Claim Without Record Support.

341.2.1 No public claim shall be made by or on behalf of the Corporation unless the claim is supported by a record sufficient to demonstrate the basis, source, authority, review status, limitation, and correction path for the claim.

341.2.2 Record support may include evidence records, source records, method records, dataset records, model records, inference records, compute workload records, proof receipts, review records, Board records, officer approvals, committee reviews, public authority records, conflict records, publication approval records, or other competent records.

341.2.3 Absence of contrary evidence shall not by itself support an affirmative claim.

341.3 Evidence Record Requirement.

341.3.1 Claims based on evidence shall identify or be traceable to evidence records sufficient to support the claim’s factual content, scope, confidence, source lineage, public-safe status, and limitations.

341.3.2 Evidence records shall distinguish direct evidence, indirect evidence, corroborated evidence, uncorroborated evidence, preliminary evidence, historical evidence, public authority-provided evidence, community-provided evidence, model-derived evidence, synthetic data, dashboard output, map output, and inference.

341.3.3 Evidence records shall not be used beyond their access class, permitted use, public-safe status, data rights, or correction status.

341.4 Method Record Requirement.

341.4.1 Claims based on methods shall identify or be traceable to method records describing the method, scope, assumptions, inputs, outputs, limitations, validation status where applicable, review status, uncertainty, and correction path.

341.4.2 Method records shall be sufficient to prevent claims that a method is validated, verified, standardized, certified, public authority approved, procurement-ready, finance-ready, or legally compliant unless such status is separately supported.

341.5 Source Lineage Requirement.

341.5.1 Material claims shall preserve source lineage sufficient to identify the origin, custody, provenance, version, date, authority, transformation, reviewer, and correction status of supporting source materials.

341.5.2 Source lineage shall identify whether sources are public, internal, confidential, restricted, public authority, community-protected, Tribal / Indigenous, derived, synthetic, AI-generated, model-generated, dashboard-generated, or ledger-recorded.

341.5.3 Claims shall not cite sources in a manner that conceals uncertainty, source age, limitations, restrictions, conflicts, or unsupported extrapolation.

341.6 Confidence and Uncertainty Requirement.

341.6.1 Material claims shall state or reflect confidence and uncertainty appropriate to the evidence, method, data quality, source reliability, model reliability, reviewer judgment, publication class, and audience.

341.6.2 Confidence language shall not overstate certainty, imply proof where only indication exists, imply verification where only review occurred, imply validation where only testing occurred, or imply public authority status where none exists.

341.6.3 Uncertainty shall be disclosed where material to interpretation, public-safe reliance, public authority understanding, community impact, technical use, finance boundary, certification boundary, recognition boundary, or procurement boundary.

341.7 Limitation Requirement.

341.7.1 Material claims shall include limitations necessary to prevent misleading interpretation, including scope limits, evidence limits, method limits, data limits, model limits, temporal limits, geographic limits, jurisdictional limits, public authority limits, finance limits, certification limits, recognition limits, procurement limits, technical limits, and public-safe limits.

341.7.2 Limitation language shall be clear, visible, tied to the claim, and sufficient for the intended audience.

341.7.3 Limitation language shall not be used as a substitute for adequate evidence, lawful authority, privacy protection, cybersecurity review, protected knowledge safeguards, or publication approval.

341.8 Public-Safe Review Requirement.

341.8.1 Material public claims shall receive public-safe review appropriate to risk before publication or external use.

341.8.2 Public-safe review shall assess whether the claim is accurate, proportionate, non-misleading, appropriately limited, accessible where appropriate, safeguards-compliant, free of public authority overclaim, free of finance overclaim, free of certification overclaim, free of recognition overclaim, free of procurement overclaim, and unlikely to create unsafe reliance.

341.8.3 Public-safe review may require revision, redaction, aggregation, delay, controlled release, limitation language, review escalation, or denial of publication.

341.9 Conflict Disclosure Requirement Where Material.

341.9.1 Material conflicts affecting a public claim shall be disclosed, mitigated, managed, or otherwise recorded according to publication class and risk.

341.9.2 Conflicts may include sponsor interests, provider interests, donor interests, funder interests, host interests, partner interests, public authority roles, commercial interests, intellectual property interests, financial interests, employment interests, family or related-party interests, academic interests, and institutional interests.

341.9.3 Conflict disclosure shall not be used to justify a misleading or unsupported claim.

341.10 Sponsor, Donor, Funder, Provider, Host, Partner, Public Authority, University, Laboratory, or Community Role Disclosure Where Material.

341.10.1 Where the role of a sponsor, donor, funder, provider, host, partner, public authority, university, laboratory, community, Tribal / Indigenous body, civil society organization, or media actor is material to interpretation, the publication shall disclose the role accurately.

341.10.2 Role disclosure shall distinguish funding, sponsorship, hosting, contribution, authorship, review, data provision, public authority participation, advisory role, technical support, controlled-room participation, publication approval, and independent authority.

341.10.3 Disclosure of a role shall not imply endorsement, approval, official adoption, recognition, finance-readiness, certification, procurement approval, public warning, emergency command, or control unless separately supported by competent record.

341.11 Data / AI / Cyber / Privacy Review Requirement Where Material.

341.11.1 Claims relying on or disclosing data, AI outputs, cyber materials, privacy-relevant information, public authority data, infrastructure-sensitive information, model outputs, embeddings, dashboards, maps, or controlled-room outputs shall receive data / AI / cyber / privacy review where material.

341.11.2 Review shall assess lawful basis, authority, permissions, consent, data classification, AI-use restrictions, hallucination risk, bias risk, data leakage, privacy exposure, cyber exposure, infrastructure exposure, secrets, model limitations, and correction path.

341.12 Safeguards Review Requirement Where Material.

341.12.1 Claims affecting civil rights, accessibility, communities, protected classes, vulnerable populations, Tribal / Indigenous peoples, local groups, territorial communities, cultural materials, environmental knowledge, public-safe mapping, or protected knowledge shall receive safeguards review where material.

341.12.2 Safeguards review shall assess stigmatization, retaliation risk, discriminatory impact, accessibility barriers, language access, exposure, decontextualization, protected knowledge misuse, mapping resolution, attribution, non-attribution, permission, grievance pathways, and correction.

341.13 No Claim Based Solely on Informal Opinion, Internal Enthusiasm, Sponsor Statement, Provider Statement, AI Output, Dashboard Output, Sensor Signal, Proof Receipt, Ledger Entry, or Unreviewed Draft.

341.13.1 No material public claim shall be based solely on informal opinion, internal enthusiasm, strategic aspiration, sponsor statement, donor statement, funder statement, provider statement, host statement, partner statement, media statement, public authority comment, AI output, dashboard output, sensor signal, telemetry event, proof receipt, ledger entry, benchmark result, model result, or unreviewed draft.

341.13.2 Such materials may contribute to a claim only when incorporated into an appropriate evidence record, method record, review record, or publication record with limitations, source lineage, and correction path.

341.13.3 Proof receipts, ledger entries, timestamps, hashes, signatures, or compute logs may evidence that a record or process occurred, but shall not by themselves establish substantive truth, safety, validity, certification, recognition, finance-readiness, procurement approval, public authority decision, public warning, emergency command, or rating.

341.14 Claims Substantiation Records.

341.14.1 The Corporation shall maintain Claims Substantiation Records, including claims substantiation purpose records, public claim support records, evidence records, method records, source lineage records, confidence and uncertainty records, limitation records, public-safe review records, conflict disclosure records, sponsor / donor / funder / provider / host / partner / public authority / university / laboratory / community role disclosure records, data / AI / cyber / privacy review records, safeguards review records, prohibited sole-source claim records, corrections, denials, withdrawals, retractions, and archive records.

---

Section 342. Controlled Vocabulary for Public Claims

342.1 Controlled Vocabulary Purpose.

342.1.1 Controlled Vocabulary for Public Claims shall ensure that the Corporation uses terms consistently, accurately, defensibly, and safely across publications, dashboards, maps, datasets, software releases, technical baselines, public authority learning materials, Academy materials, media materials, partner materials, sponsor materials, provider materials, and public statements.

342.1.2 Controlled Vocabulary shall prevent semantic drift, authority inflation, public authority confusion, finance overclaim, certification overclaim, recognition overclaim, procurement overclaim, provider preference, public warning confusion, emergency command confusion, technical truth misrepresentation, and misuse of Nexus terms.

342.1.3 Controlled Vocabulary shall be maintained as public-good semantic infrastructure and shall align with the Corporation’s evidence doctrine, methods doctrine, observability doctrine, data / AI / cyber governance, non-execution doctrine, validity-by-record discipline, correctionability, and Nexus role separation.

342.2 Required Use of Controlled Terms.

342.2.1 The Corporation shall require controlled terms for material public claims, including terms related to evidence, validation, verification, confidence, uncertainty, public-safe publication, technical truth, recognition, standing, maturity, Docket, Grid, finance-readiness, insurance-readiness, capital-readiness, bankability, investability, proof packs, certification, accreditation, conformance, compliance, approval, Nexus compatibility, public authority roles, North America anchor roles, United States roles, state interfaces, territorial interfaces, Tribal interfaces, and public-good stack roles.

342.2.2 Controlled terms shall be defined, versioned, and applied according to recorded criteria, context, limitations, and permitted uses.

342.2.3 Where a term has regulated, public authority, finance, professional, technical, or common-language ambiguity, the Corporation shall use limitation language or substitute clearer terms.

342.3 Evidence Terms.

342.3.1 Evidence terms shall distinguish evidence, source record, evidence record, source lineage, provenance, observation, inference, indication, corroboration, limitation, uncertainty, public-safe evidence, restricted evidence, controlled evidence, and archived evidence.

342.3.2 Evidence terms shall not imply recognition, certification, finance-readiness, procurement approval, public authority decision, rating, public warning, emergency command, or provider preference.

342.3.3 Terms such as “evidence-supported,” “record-supported,” “source-grounded,” and “observed” shall be used only when the underlying record supports the term.

342.4 Verified and Validated Terms.

342.4.1 “Verified,” “validated,” “validation,” “verification,” “validated by,” “verified by,” and similar terms shall be used only according to defined criteria and supporting records.

342.4.2 Verification shall generally refer to confirmation against a defined record, source, requirement, process, or condition, while validation shall generally refer to assessment of fitness for a defined purpose, method, context, or use case, unless a specific technical or legal framework defines the terms differently.

342.4.3 Verification or validation language shall not imply certification, legal compliance approval, public authority approval, finance-readiness, recognition, procurement approval, rating, public warning, emergency command, or guarantee unless separately authorized and accurately limited.

342.5 Confidence and Uncertainty Terms.

342.5.1 Confidence and uncertainty terms shall distinguish high confidence, moderate confidence, low confidence, preliminary, indicative, inconclusive, insufficient evidence, contested, under review, corrected, superseded, withdrawn, retracted, and archived.

342.5.2 Confidence terms shall be tied to evidence quality, source reliability, method quality, data quality, review status, model limitations, and publication purpose.

342.5.3 Confidence terms shall not be used as rhetorical emphasis or as substitute for substantiation.

342.6 Public-Safe Terms.

342.6.1 Public-safe terms shall distinguish public, public-safe, public-safe summary, controlled annex, restricted, internal, confidential, no-download, public authority access, clean room, data room, evidence room, archived, redacted, aggregated, delayed, and sealed.

342.6.2 “Public-safe” shall mean reviewed for public release or external release within a defined scope; it shall not mean risk-free, complete, official, certified, recognized, finance-ready, public authority approved, procurement approved, or operationally actionable.

342.7 Technical Truth Terms.

342.7.1 Technical truth terms shall distinguish technical truth, technical finding, method output, model output, benchmark result, dashboard output, map output, proof receipt, compute workload record, inference record, verifiable compute record, verifiable intelligence output, and public-safe summary.

342.7.2 Technical truth shall be used only to mean record-supported, method-bounded, limitation-aware technical support within a defined scope and shall not imply universal truth, legal truth, public authority truth, financial truth, certification, recognition, procurement approval, or emergency truth.

342.8 Recognition, Standing, and Maturity Terms.

342.8.1 Recognition, standing, and maturity terms shall be used only where the relevant competent authority, including The Global Risks Forum (GRF) where applicable, has issued or recorded the relevant status.

342.8.2 GCRI US evidence, methods, observability outputs, software, technical baselines, or public-safe publications shall not be described as recognition, maturity standing, registry standing, legitimacy standing, or GRF recognition unless The Global Risks Forum (GRF) separately records such status.

342.8.3 Draft, preliminary, applicant, candidate, observed, evidence-supported, or public-safe terms shall not be used to imply recognition or standing.

342.9 Docket and Grid Terms.

342.9.1 Docket and Grid terms shall be used only according to their defined Nexus meanings and shall distinguish Docket entry, Docket input, Docket record, Grid input, Grid maturity, Grid routeability, Grid status, Grid record, and Grid-facing material.

342.9.2 Docket or Grid terminology shall not be used to imply approval, recognition, certification, finance-readiness, procurement approval, public authority adoption, provider preference, public warning, emergency command, or execution authority unless a separate competent record expressly supports the limited status.

342.10 Finance-Ready, Insurance-Ready, Capital-Readable, Bankable, Investable, and Proof Pack Terms.

342.10.1 Finance-ready, insurance-ready, capital-readable, bankable, investable, proof pack, investment-ready, underwriteable, public finance-ready, and similar terms shall be restricted terms.

342.10.2 Such terms shall not be used by the Corporation except where The Global Risks Alliance (GRA), or another competent finance-readiness authority under lawful and separate authority, has established the meaning, criteria, records, and permitted use of the term.

342.10.3 GCRI US may use terms such as “evidence pack,” “technical record,” “public-safe summary,” or “GRA-facing input” only where accurate and limitation-aware, and shall not convert such materials into finance-readiness.

342.11 Certified, Accredited, Conformant, Compliant, Approved, and Nexus-Compatible Terms.

342.11.1 Certified, accredited, conformant, compliant, approved, verified, validated, Nexus-compatible, compliant with, conforms to, approved by, certified by, and similar terms shall be controlled or restricted according to their risk of implying formal authority.

342.11.2 “Nexus-compatible” shall be used only where criteria, version, scope, interface, review status, limitation, and authority are recorded.

342.11.3 “Compliant” shall not be used to imply legal compliance, regulatory compliance, cybersecurity compliance, AI compliance, privacy compliance, procurement compliance, export-control compliance, or professional compliance unless competent review supports the precise statement.

342.11.4 “Approved” shall identify who approved what, for what purpose, under what authority, and with what limitations.

342.12 Public Authority, Official, Observer, Regulator-Listening, Public Finance Reader, Emergency-Management Participant, and Public Infrastructure Operator Terms.

342.12.1 Public authority terms shall distinguish public authority, public official, observer, regulator-listening participant, public finance reader, procurement reader, emergency-management participant, public infrastructure operator, public authority data source, public authority reviewer, and official decision-maker.

342.12.2 Attendance, observation, listening, comment, review, data provision, controlled-room participation, or learning participation shall not be described as official endorsement, adoption, approval, procurement action, public warning, emergency command, or sovereign decision.

342.12.3 Public authority capacity terms shall be used with precision and shall be supported by records.

342.13 North America Anchor, United States Anchor, State Interface, Territorial Interface, Tribal Interface, and Public-Good Stack Terms.

342.13.1 North America Anchor, United States Anchor, state interface, territorial interface, Tribal interface, public-good stack, enterprise stack, one rail, two stacks, Nexus Network, Nexus Universe, Nexus Observatory, Nexus Standards, Nexus Risk Management, Nexus Rails, Nexus Grid, Nexus Academy, public-good technical institution, and related terms shall be used consistently with the Corporation’s governing instruments and role separation.

342.13.2 Such terms shall not imply control over public authorities, foreign sovereigns, Tribal governments, GCRI Canada, GRF, GRA, consortiums, national companies, Project SPVs, providers, sponsors, hosts, universities, laboratories, communities, or enterprise actors.

342.13.3 Public-good stack terms shall distinguish public-benefit evidence, methods, observability, technical baseline, and public-safe publication roles from enterprise execution, finance execution, procurement, certification, public authority action, and provider delivery.

342.14 Prohibited or Restricted Terms Without Authority.

342.14.1 The Corporation shall prohibit or restrict use of terms that imply authority not held, including certified, accredited, approved, official, public authority-approved, government-approved, procurement-approved, finance-ready, investment-ready, bankable, insured, insurance-ready, rated, recognized, GRF-recognized, GRA finance-ready, compliant, guaranteed, public warning, emergency command, operational directive, execution authority, provider-approved, preferred provider, and similar terms unless competent authority expressly supports their use.

342.14.2 Prohibited or restricted terms shall be removed, revised, limited, or escalated for review when they appear in drafts, publications, partner materials, repository materials, dashboards, maps, software outputs, AI outputs, press materials, or social media.

342.15 Semantic Drift Review.

342.15.1 Semantic Drift Review shall assess whether terms have shifted in meaning through repeated use, public interpretation, partner use, provider use, sponsor use, media use, AI-generated text, dashboard labels, software outputs, translations, or public authority references.

342.15.2 Semantic drift may require vocabulary update, publication correction, retraining, interface redesign, label change, translation review, public clarification, controlled clarification, or withdrawal of misleading materials.

342.16 Controlled Vocabulary Correction.

342.16.1 Controlled Vocabulary Correction shall be required where terminology is inaccurate, misleading, obsolete, overbroad, overclaiming, inconsistent, unsafe, mistranslated, misused by partners, misused by providers, or likely to create public reliance beyond authority.

342.16.2 Corrections may include revised definitions, replacement terms, public-safe notices, controlled notices, glossary updates, dashboard label changes, software output changes, publication corrections, mark-use restrictions, or training updates.

342.17 Controlled Vocabulary Records.

342.17.1 The Corporation shall maintain Controlled Vocabulary Records, including controlled vocabulary purpose records, required term records, evidence term records, verified and validated term records, confidence and uncertainty term records, public-safe term records, technical truth term records, recognition / standing / maturity term records, Docket and Grid term records, finance-ready / insurance-ready / capital-readable / bankable / investable / proof pack term records, certification / accreditation / conformance / compliance / approval / Nexus-compatible term records, public authority / official / observer / regulator-listening / public finance reader / emergency-management participant / public infrastructure operator term records, North America Anchor / United States Anchor / state interface / territorial interface / Tribal interface / public-good stack term records, prohibited and restricted term records, semantic drift review records, correction records, glossary records, translation records, training records, and archive records.

---

Section 343. Technical Claims

343.1 Technical Claims Purpose.

343.1.1 Technical Claims shall mean public or external statements concerning the design, function, performance, security, interoperability, evidence support, method support, data quality, model behavior, benchmark result, observability result, software capability, dataset property, dashboard meaning, map meaning, technical baseline alignment, reference architecture, Nexus compatibility, or public-good technical asset status of any Corporation material or related system.

343.1.2 Technical Claims shall be governed to ensure accuracy, source support, method support, public-safe interpretation, security, privacy, accessibility, protected knowledge safeguards, public authority boundary discipline, finance-boundary discipline, certification-boundary discipline, recognition-boundary discipline, procurement neutrality, provider neutrality, and correctionability.

343.1.3 Technical Claims shall be assessed based on the meaning a reasonable audience may take from the statement, including implications created by labels, charts, colors, scores, badges, dashboards, maps, release notes, benchmarks, model outputs, public authority references, sponsor references, provider references, or Nexus terminology.

343.2 Evidence-Based Technical Claims.

343.2.1 Evidence-Based Technical Claims shall be supported by evidence records, source lineage, provenance, data class, review status, confidence, uncertainty, limitations, public-safe review, and correction path.

343.2.2 Evidence-Based Technical Claims shall distinguish observed facts, record-supported findings, inferred conclusions, model-generated outputs, sensor readings, benchmark outcomes, public authority statements, community inputs, and expert judgments.

343.2.3 Evidence-Based Technical Claims shall not exceed the scope, age, quality, completeness, jurisdiction, technology domain, or confidence of the supporting evidence.

343.3 Method-Based Technical Claims.

343.3.1 Method-Based Technical Claims shall be supported by method records identifying the method, scope, assumptions, inputs, outputs, validation status where applicable, limitations, review status, and correction path.

343.3.2 Method-Based Technical Claims shall not state or imply that a method is universally valid, legally compliant, certified, public authority approved, procurement-ready, finance-ready, operationally authoritative, clinically valid, or emergency-ready unless a competent separate record supports the precise claim.

343.3.3 Method claims shall distinguish method design, method testing, method validation, method application, method output, and public-safe summary.

343.4 Software Claims.

343.4.1 Software Claims shall be supported by software records, repository records, version records, release records, license records, dependency records, security records, known issue records, known limitation records, test records, and correction path.

343.4.2 Software Claims shall identify release status, version, supported uses, prohibited uses, known limitations, security status where public-safe, maintenance status, and deprecation or retirement status where applicable.

343.4.3 Software Claims shall not imply that software is secure, vulnerability-free, production-ready, public authority approved, procurement-approved, certified, finance-ready, recognized, rated, provider-preferred, public-warning-ready, emergency-ready, or operationally sufficient unless separately supported and accurately limited.

343.5 Dataset Claims.

343.5.1 Dataset Claims shall be supported by dataset records, source lineage, data rights, lawful basis, permissions, license, data dictionary, schema, data quality review, bias review where appropriate, public-safe status, AI-use status, access class, limitations, and correction path.

343.5.2 Dataset Claims shall distinguish raw data, cleaned data, derived data, synthetic data, de-identified data, pseudonymized data, aggregated data, public-safe data, restricted data, public authority data, community-protected data, and protected knowledge.

343.5.3 Dataset Claims shall not imply completeness, representativeness, ground truth, public authority endorsement, rating, certification, finance-readiness, procurement approval, recognition, or public warning unless specifically supported.

343.6 Model Claims.

343.6.1 Model Claims shall be supported by model register records, model cards, system cards, evaluation records, dataset records, permitted-use records, prohibited-use records, risk class, known limitations, incident history, monitoring records, human review records, and correction path.

343.6.2 Model Claims shall identify whether claims concern a model family, model version, fine-tuned model, prompt configuration, retrieval system, deployment environment, evaluation harness, benchmark result, or specific use case.

343.6.3 Model Claims shall not imply general intelligence, safety, accuracy, fairness, legal compliance, cyber compliance, privacy compliance, public authority approval, certification, finance-readiness, recognition, procurement eligibility, provider preference, or readiness for high-risk use beyond the evaluated scope.

343.7 Benchmark Claims.

343.7.1 Benchmark Claims shall be supported by benchmark records, evaluation set records, test vector records, method records, scoring records, model records, version records, test conditions, limitations, leakage review where applicable, bias review where applicable, and correction path.

343.7.2 Benchmark Claims shall identify the benchmark version, tested asset, test conditions, scope, limitations, confidence, and whether results are preliminary, internal, public-safe, independently reviewed, or corrected.

343.7.3 Benchmark Claims shall not be used as ratings, rankings, certifications, recognition, procurement eligibility, finance-readiness, public authority approval, provider endorsement, safety guarantee, or general performance proof unless a competent separate authority expressly creates such status and the claim accurately states its limits.

343.8 Observatory Claims.

343.8.1 Observatory Claims shall concern observability methods, observatory nodes, Nexus hubs, clusters, hotspots, regional clusters, national dense Nexus cores, telemetry, signals, indicators, degraded-mode awareness, resilience indicators, public-safe dashboards, maps, and observability outputs.

343.8.2 Observatory Claims shall be supported by observability records, evidence records, telemetry records, data rights, method records, public-safe review, confidence, uncertainty, limitations, public authority boundary review, and correction path.

343.8.3 Observatory Claims shall not be represented as public warning, emergency command, operational control, public authority decision, infrastructure rating, resilience certification, procurement approval, finance-readiness, recognition, provider preference, or guarantee.

343.9 Truth Engine Claims.

343.9.1 Truth Engine Claims shall concern technical truth methods, evidence synthesis, source-lineage structures, verification workflows, validation workflows, proof receipts, verifiable compute, verifiable intelligence, inference records, compute workload records, correction paths, and public-safe summaries.

343.9.2 Truth Engine Claims shall be bounded by records, methods, data rights, model limitations, human review, public-safe review, confidence, uncertainty, and correctionability.

343.9.3 Truth Engine Claims shall not imply absolute truth, legal truth, public authority truth, financial truth, certification, recognition, procurement approval, rating, public warning, emergency command, or guarantee.

343.10 AI-RAN, O-RAN, DePIN, DLT, Digital Twin, Geospatial, Cyber, Sensor, Robotics, Drone, Telecom, Energy, Water, Food, Biosecurity, Climate, Nature, and Critical Infrastructure Claims.

343.10.1 Claims involving AI-RAN, O-RAN, DePIN, DLT, blockchain, digital twins, geospatial systems, cyber systems, sensors, robotics, drones, telecom, energy, water, food, biosecurity, climate, nature, Earth observation, public health, emergency systems, ports, transportation, semiconductors, advanced manufacturing, or critical infrastructure shall receive heightened technical, public-safe, cyber, infrastructure, public authority, protected knowledge, and safeguards review where material.

343.10.2 Such claims shall distinguish observation from simulation, telemetry from inference, benchmark from field performance, digital twin scenario from operational fact, ledger entry from substantive truth, signal from public warning, dashboard indicator from public authority decision, and reference architecture from deployment approval.

343.10.3 Such claims shall not disclose sensitive infrastructure details, cyber-sensitive details, protected knowledge, controlled technology, export-controlled information, public authority restricted data, or unsafe operational information without lawful authority and public-safe approval.

343.11 Public-Good Software Claims.

343.11.1 Public-Good Software Claims shall identify whether software is prototype, experimental, internal, controlled, public release candidate, public release, restricted release, deprecated, retired, or archived.

343.11.2 Such claims shall be supported by release records, repository records, documentation, known limitations, known issues, license, security review, dependency review, vulnerability status, and correction path.

343.11.3 Public-Good Software Claims shall not imply enterprise deployment, production suitability, managed service, service-level commitment, public authority system, procurement system, certification system, finance-readiness system, recognition system, public warning system, or emergency command system.

343.12 Open Technical Baseline Claims.

343.12.1 Open Technical Baseline Claims shall identify baseline version, scope, effective date, review status, public-safe status, limitation statement, interoperability function, evidence quality function, data governance function, AI governance function, cybersecurity function, observability function, public authority learning function, and Nexus compatibility support function where applicable.

343.12.2 Open Technical Baseline Claims shall not state or imply certification, procurement mandate, legal compliance approval, public authority adoption, provider preference, finance-readiness, recognition, rating, public warning, emergency command, or execution authority.

343.13 Interoperability Claims.

343.13.1 Interoperability Claims shall identify the specific schemas, APIs, SDKs, technical profiles, baselines, versions, interfaces, data formats, semantic mappings, validation criteria, and limitations supporting the claim.

343.13.2 Interoperability Claims shall distinguish technical compatibility, semantic compatibility, partial compatibility, experimental compatibility, implementation support, reference implementation, and tested integration.

343.13.3 Interoperability shall not be described as certification, conformance approval, public authority adoption, procurement approval, finance-readiness, recognition, provider qualification, public warning, emergency command, or operational readiness unless separately supported by competent authority.

343.14 Nexus-Compatible Claims.

343.14.1 Nexus-Compatible Claims shall be used only where specific Nexus-compatible criteria, version, asset, interface, evidence format, technical profile, controlled vocabulary, public-safe review, and authority support the claim.

343.14.2 Nexus-Compatible Claims shall distinguish compatibility with a technical asset from institutional recognition, finance-readiness, certification, procurement approval, public authority adoption, provider preference, rating, public warning, emergency command, or execution authority.

343.14.3 Nexus-Compatible Claims shall not imply GRF recognition or GRA finance-readiness unless The Global Risks Forum (GRF) or The Global Risks Alliance (GRA), respectively, has separately issued the relevant status through competent records.

343.15 Technical Limitation Statements.

343.15.1 Technical Claims shall include Technical Limitation Statements where necessary to identify unsupported uses, data limitations, model limitations, method limitations, software limitations, benchmark limitations, sensor limitations, telemetry limitations, geospatial limitations, digital twin limitations, cyber limitations, jurisdictional limitations, public authority limitations, public-safe limitations, and correction paths.

343.15.2 Technical Limitation Statements shall be placed close enough to the claim to prevent misleading reliance and shall be understandable to the intended audience.

343.15.3 Limitation statements shall not be hidden in footnotes, repositories, annexes, or terms where the main claim remains misleading.

343.16 No Technical Claim as Certification, Procurement Approval, Legal Compliance Approval, Provider Preference, Public Authority Adoption, Finance-Readiness, Rating, Recognition, Public Warning, or Emergency Command.

343.16.1 No Technical Claim, including any evidence claim, method claim, software claim, dataset claim, model claim, benchmark claim, observability claim, Truth Engine claim, AI-RAN / O-RAN claim, DePIN or DLT claim, digital twin claim, geospatial claim, cyber claim, sensor claim, robotics claim, drone claim, telecom claim, energy claim, water claim, food claim, biosecurity claim, climate claim, nature claim, critical infrastructure claim, public-good software claim, open technical baseline claim, interoperability claim, or Nexus-Compatible claim, shall constitute or be represented as certification, procurement approval, legal compliance approval, provider preference, public authority adoption, finance-readiness, insurance-readiness, rating, recognition, public warning, emergency command, operational instruction, guarantee, or execution authority.

343.16.2 Where technical claims may reasonably be misread as any such status, the Corporation shall revise, restrict, redact, relabel, withdraw, correct, or refuse publication.

343.17 Technical Claim Records.

343.17.1 The Corporation shall maintain Technical Claim Records, including technical claims purpose records, evidence-based technical claim records, method-based technical claim records, software claim records, dataset claim records, model claim records, benchmark claim records, Observatory claim records, Truth Engine claim records, AI-RAN / O-RAN / DePIN / DLT / digital twin / geospatial / cyber / sensor / robotics / drone / telecom / energy / water / food / biosecurity / climate / nature / critical infrastructure claim records, public-good software claim records, open technical baseline claim records, interoperability claim records, Nexus-Compatible claim records, technical limitation statements, boundary records, corrections, withdrawals, retractions, denials, and archive records.

Section 344. Public Authority References and Government Interface Communications

344.1 Public Authority Reference Purpose.

344.1.1 Public Authority References shall be governed to ensure that any reference by the Corporation to a federal, state, District of Columbia, territorial, Tribal, Indigenous governmental, local, county, municipal, metropolitan, utility, port, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, infrastructure, public finance, procurement, regulatory, legislative, judicial, administrative, or other public-sector body is accurate, lawful, capacity-classified, permission-aware, public-safe, and consistent with the Corporation’s non-executing public-benefit role.

344.1.2 Public Authority References may appear in reports, whitepapers, technical notes, method notes, evidence packs, public-safe summaries, dashboards, maps, datasets, software documentation, open technical baselines, reference architectures, public authority learning materials, event materials, speeches, presentations, web pages, press releases, social media posts, newsletters, partner materials, controlled-room materials, public-good technical asset records, and other external outputs.

344.1.3 Public Authority References shall preserve the distinction between: 344.1.3(a) public authority awareness and public authority approval; 344.1.3(b) public authority attendance and public authority adoption; 344.1.3(c) public authority data contribution and public authority endorsement; 344.1.3(d) public authority learning and public authority action; 344.1.3(e) public authority observation and public authority decision; 344.1.3(f) public authority participation in a controlled room and public authority authorization of outcomes; 344.1.3(g) public authority infrastructure operation and Corporation non-executing evidence support; and 344.1.3(h) public-safe publication and public warning or emergency command.

344.2 Federal Public Authority References.

344.2.1 Federal Public Authority References shall be reviewed for accuracy, legal authority, official-capacity status, procurement sensitivity, grant sensitivity, public finance sensitivity, regulatory sensitivity, federal records implications, controlled unclassified information considerations where applicable, cybersecurity obligations, privacy obligations, export-control, sanctions, public-safe publication, and institutional role separation.

344.2.2 References to federal departments, agencies, offices, commissions, regulators, laboratories, federally funded entities, public finance bodies, emergency management bodies, public health bodies, infrastructure bodies, military or defense-adjacent bodies, or federal officials shall not imply endorsement, adoption, funding approval, procurement approval, regulatory approval, public finance approval, public warning, emergency command, sovereign obligation, or partnership unless a competent federal record supports the precise statement.

344.2.3 Federal references shall be stated in capacity-classified language, such as informational, observer, contributor of public information, participant in learning, regulator-listening, public finance reader, technical reviewer, or official signatory, as applicable and supported by record.

344.3 State Public Authority References.

344.3.1 State Public Authority References shall be reviewed for state-specific legal authority, open records implications, procurement rules, grant rules, public finance sensitivity, public health sensitivity, emergency management sensitivity, cybersecurity sensitivity, privacy obligations, ethics rules, official-capacity status, and public-safe publication risk.

344.3.2 References to one state shall not be generalized to another state. No publication shall imply that all states, multiple states, or state authorities broadly support, approve, adopt, endorse, fund, procure, rely upon, recognize, or mandate a Corporation output unless competent records support the exact scope of the statement.

344.3.3 State participation in a meeting, learning session, public authority room, technical review, workshop, dashboard review, map review, observability discussion, evidence discussion, or controlled-room process shall not be described as state approval, adoption, procurement support, regulatory position, public warning, emergency command, or official state action unless lawfully recorded by competent state authority.

344.4 District of Columbia and Territorial Public Authority References.

344.4.1 References to the District of Columbia and territorial public authorities shall be reviewed for District-specific or territorial legal status, public records rules, procurement rules, grant rules, emergency management context, public health context, infrastructure context, language access, accessibility, disaster resilience, federal-territorial relationships, and public-safe publication obligations.

344.4.2 Territorial references shall be stated with appropriate context for island, coastal, Arctic, remote, disaster-exposed, supply-chain, telecom, energy, water, public health, food security, and community resilience conditions where material.

344.4.3 No District or territorial reference shall imply official adoption, procurement approval, grant approval, public finance approval, emergency command, public warning, public authority endorsement, or sovereign obligation unless a competent District or territorial authority separately and lawfully records such status.

344.5 Tribal and Indigenous Government References Where Lawfully and Respectfully Approved.

344.5.1 References to Tribal or Indigenous governments, authorities, communities, representatives, knowledge holders, territories, data, protocols, meetings, cultural materials, environmental knowledge, sacred knowledge, or protected knowledge shall be made only where lawful, respectful, permission-aware, safeguards-reviewed, and consistent with applicable protocol, capacity, attribution, non-attribution, consent, restriction, withdrawal, and correction conditions.

344.5.2 Tribal and Indigenous Government References shall avoid implication of endorsement, adoption, approval, waiver of sovereignty, data transfer permission, knowledge-use permission, public-safe mapping permission, public authority delegation, public warning, emergency command, or unrestricted reuse.

344.5.3 Where a reference involves Indigenous data, Indigenous knowledge, land-based knowledge, cultural knowledge, ecological knowledge, sacred knowledge, community-protected data, or protected knowledge, the publication shall receive protected knowledge review and, where applicable, Tribal or Indigenous review before release.

344.6 Local, County, Municipal, Metropolitan, Utility, Port, Public Health, Emergency Management, Public Safety, Public Works, Telecom, Energy, Water, Food, Cyber, and Infrastructure References.

344.6.1 References to local, county, municipal, metropolitan, utility, port, public health, emergency management, public safety, public works, telecom, energy, water, food, cyber, and infrastructure actors shall be reviewed for operational sensitivity, public authority capacity, public records implications, infrastructure sensitivity, cyber sensitivity, public-safe mapping risk, public health sensitivity, emergency-management implications, public safety implications, procurement implications, and community exposure.

344.6.2 Such references shall not disclose sensitive infrastructure information, cyber-sensitive information, operational dependency, degraded-mode information, vulnerability information, resilience weaknesses, emergency response details, or public-safe mapping details unless lawful, authorized, reviewed, and public-safe.

344.6.3 References to infrastructure operators or public infrastructure entities shall not imply that the Corporation operates, supervises, certifies, rates, ranks, commands, audits, guarantees, funds, procures, approves, or manages such infrastructure.

344.7 Public Authority Name Use.

344.7.1 Use of a public authority’s name shall be accurate, necessary, permission-aware, and supported by records sufficient to show the basis for the reference.

344.7.2 Public authority name use shall not imply endorsement, adoption, approval, funding, procurement, public finance support, regulatory approval, emergency command, public warning, public-private partnership, sovereign obligation, or official relationship unless specifically supported by competent authority.

344.7.3 Where name use is not necessary for public-safe meaning, the Corporation may use generic, aggregated, anonymized, or capacity-based references.

344.8 Public Authority Logo Use.

344.8.1 Public authority logos, seals, insignia, flags, badges, crests, official emblems, letterheads, or visual marks shall not be used without appropriate permission, legal authority, and public-safe review.

344.8.2 Public authority logo use shall be avoided where it could imply endorsement, sponsorship, official adoption, procurement approval, public finance approval, public warning, emergency command, regulatory approval, or public-private partnership.

344.8.3 Co-branded or event-related logo use shall be subject to documented authorization, role description, limitation language, and review for public authority boundary risk.

344.9 Public Authority Title Use.

344.9.1 Public authority titles, offices, ranks, roles, agency names, department names, program names, and official designations shall be used accurately and with currentness review where material.

344.9.2 A public official’s title shall not be used to imply that the official acts in official capacity, binds an agency, approves a publication, endorses the Corporation, or adopts Corporation materials unless a competent record supports that conclusion.

344.9.3 Where a person participates in personal, academic, expert, observer, listening, or informal capacity, the publication shall not use the title in a way that misrepresents capacity.

344.10 Public Authority Quote Use.

344.10.1 Public authority quotes shall not be used without appropriate permission, accuracy review, context review, capacity classification, and public-safe review.

344.10.2 Quotes shall not be edited, excerpted, framed, captioned, translated, or paired with graphics in a manner that implies broader endorsement, adoption, funding approval, procurement approval, public finance approval, regulatory approval, public warning, emergency command, or sovereign obligation than the speaker authorized.

344.10.3 Where a quote is historical, informal, non-public, controlled-room-based, or made in a listening or observer capacity, such status shall be reflected or the quote shall not be used.

344.11 Public Authority Attendance References.

344.11.1 References to public authority attendance at meetings, events, workshops, controlled rooms, data rooms, evidence rooms, simulations, public authority rooms, briefings, or learning sessions shall be accurate, capacity-classified, and non-misleading.

344.11.2 Attendance shall not imply endorsement, adoption, approval, funding, procurement approval, public finance approval, public warning, emergency command, regulatory approval, or official decision.

344.11.3 Attendance references may use controlled terms such as “attended,” “observed,” “participated in learning,” “received briefing,” “contributed public information,” “provided technical comment,” or “joined in personal capacity,” only where the term accurately reflects the record.

344.12 Public Authority Photograph, Recording, or Event Reference.

344.12.1 Photographs, recordings, screenshots, event references, participant lists, name plates, agenda excerpts, venue references, and visual depictions involving public authorities shall be used only where authorized, accurate, public-safe, privacy-compliant, and not misleading.

344.12.2 Images or recordings shall not be used to imply endorsement, adoption, approval, funding, procurement approval, public finance approval, official sponsorship, public warning, emergency command, or public-private partnership unless separately authorized.

344.12.3 Event references shall distinguish hosting, attendance, sponsorship, speaking, observation, technical contribution, official statement, and formal approval.

344.13 Public Authority Data Contribution Reference.

344.13.1 Public Authority Data Contribution References shall accurately describe the source, authority, permitted use, data class, public records status where applicable, confidentiality, public-safe status, and limitations of the data contribution.

344.13.2 A public authority data contribution shall not imply that the public authority endorses the Corporation’s analysis, method, dashboard, map, report, publication, software, technical baseline, finance-readiness input, recognition input, certification-like output, procurement implication, public warning, or emergency command.

344.13.3 Public authority data shall not be referenced publicly where the contribution is confidential, restricted, non-public, sensitive, or subject to publication limits unless competent authority authorizes the reference.

344.14 Capacity Classification Requirement.

344.14.1 Every material Public Authority Reference shall be capacity-classified according to the role actually held by the public authority or public official in the relevant context.

344.14.2 Capacity classifications may include official decision-maker, authorized signatory, public authority data source, public information source, observer, regulator-listening participant, public finance reader, procurement reader, emergency-management participant, public infrastructure operator, technical reviewer, community-interface participant, simulation participant, event attendee, personal-capacity participant, academic-capacity participant, or informal commenter.

344.14.3 Where capacity is unclear, the Corporation shall use narrower language, obtain clarification, or omit the reference.

344.15 Official Capacity Approval Requirement.

344.15.1 No publication shall state or imply that a public authority or public official acts in official capacity, approves a statement, endorses a publication, adopts a technical asset, supports funding, approves procurement, approves public finance, gives regulatory approval, issues public warning, or participates in emergency command unless the Corporation has competent record of official-capacity approval.

344.15.2 Official-capacity approval shall be recorded, scope-limited, and reviewed for legal sufficiency, public authority authorization, public records implications, public-safe language, and role separation.

344.16 Observer, Regulator-Listening, Public Finance Reader, Emergency-Management Participant, Public Infrastructure Operator, Simulation Participant, and Personal-Capacity Language.

344.16.1 The Corporation shall use precise capacity language where public authority participation is non-decisional, including observer, regulator-listening participant, public finance reader, emergency-management participant, public infrastructure operator, simulation participant, technical reviewer, public information source, or personal-capacity participant, as supported by record.

344.16.2 “Observer” shall mean attendance or review without adoption, approval, endorsement, decision, or commitment unless otherwise recorded.

344.16.3 “Regulator-listening” shall mean a regulator or regulatory staff member received information or listened in a non-decisional capacity and shall not imply regulatory approval, guidance, enforcement position, safe harbor, compliance status, or official view.

344.16.4 “Public finance reader” shall mean a public finance actor reviewed or received materials in a non-approval capacity and shall not imply public finance approval, appropriation, guarantee, credit support, tax credit approval, MDB / DFI approval, or sovereign obligation.

344.16.5 “Emergency-management participant” shall mean a person or body with emergency-management context participated in a learning, simulation, or review setting and shall not imply public warning, emergency command, evacuation instruction, operational control, or official incident action.

344.16.6 “Public infrastructure operator” shall mean an entity or person with infrastructure responsibilities participated or was referenced in a defined capacity and shall not imply that the Corporation operates, certifies, ranks, commands, audits, or controls infrastructure.

344.16.7 “Simulation participant” shall mean participation in a non-real-world exercise, tabletop, model, scenario, or test environment and shall not imply actual incident response, readiness certification, operational approval, or public authority adoption.

344.16.8 “Personal-capacity” language shall be used where a person participates outside official authority and shall not be paired with titles, logos, or agency marks in a way that creates contrary implication.

344.17 No Endorsement, Adoption, Funding Approval, Procurement Approval, Regulatory Approval, Public Finance Approval, Sovereign Obligation, PPP, Public Warning, or Emergency Command by Reference.

344.17.1 No Public Authority Reference, including name use, logo use, title use, quote use, attendance reference, photograph, recording, data contribution, event participation, controlled-room participation, public authority learning material, dashboard review, map review, simulation participation, or technical comment, shall by itself create or imply endorsement, adoption, funding approval, procurement approval, regulatory approval, public finance approval, sovereign obligation, public-private partnership, public warning, emergency command, official guidance, official standard, or public authority decision.

344.17.2 Where a publication may reasonably create such implication, the Corporation shall revise, qualify, redact, restrict, delay, withdraw, or refuse the reference.

344.18 Public Authority Reference Records.

344.18.1 The Corporation shall maintain Public Authority Reference Records, including public authority reference purpose records, federal reference records, state reference records, District of Columbia and territorial reference records, Tribal and Indigenous government reference records, local / county / municipal / metropolitan / utility / port / public health / emergency management / public safety / public works / telecom / energy / water / food / cyber / infrastructure reference records, name-use records, logo-use records, title-use records, quote-use records, attendance-reference records, photograph / recording / event-reference records, data-contribution-reference records, capacity classification records, official-capacity approval records, observer / regulator-listening / public finance reader / emergency-management participant / public infrastructure operator / simulation participant / personal-capacity language records, no-endorsement and boundary records, corrections, withdrawals, and archive records.

---

Section 345. Finance-Readiness, Capital-Readability, Insurance-Readiness, Investment, Lending, Rating, Public Finance, and Capital-Reader References

345.1 Finance-Boundary Reference Purpose.

345.1.1 Finance-Boundary References shall be governed to prevent Corporation publications, technical assets, evidence packs, public-safe summaries, dashboards, maps, datasets, software outputs, proof receipts, Docket inputs, Grid inputs, GRA-facing inputs, public authority learning materials, partner materials, sponsor materials, or media materials from being misread as investment advice, securities activity, broker-dealer activity, finder activity, placement activity, underwriting activity, lending approval, banking activity, insurance activity, rating activity, public finance approval, sovereign obligation, grant approval, tax credit approval, guarantee, or regulated capital-market action.

345.1.2 Finance-Boundary References shall preserve the Corporation’s non-finance, non-executing role and distinguish GCRI US evidence, methods, observability, public-good technical asset, and public-safe publication activity from the separate authority and records of The Global Risks Alliance (GRA), capital readers, public finance actors, insurers, lenders, development finance institutions, multilateral development banks, national companies, Project SPVs, sponsors, providers, and enterprise actors.

345.1.3 Finance-Boundary References shall be reviewed by substance and audience, not only by terminology. A statement, chart, score, color, dashboard, map, benchmark, proof pack, maturity label, or public authority reference may create finance implication even when finance terms are not used.

345.2 Finance-Readiness Reference Review.

345.2.1 References to finance-readiness, finance-ready status, finance-readiness inputs, finance-readiness translation, finance-facing evidence, or GRA-facing materials shall be reviewed for authority, source support, role separation, limitation language, securities risk, lending risk, insurance risk, rating risk, public finance risk, procurement risk, and public-safe reliance risk.

345.2.2 GCRI US may describe materials as evidence records, evidence packs, public-safe summaries, technical records, or GRA-facing inputs only where the description is accurate, record-supported, and expressly limited.

345.2.3 GCRI US shall not state or imply that it has determined finance-readiness unless a separate lawful authority expressly authorizes such role, which shall not be presumed.

345.3 Capital-Readability Reference Review.

345.3.1 Capital-readability references shall be reviewed to ensure they describe the clarity, organization, traceability, or technical intelligibility of evidence for capital readers without implying investment suitability, bankability, finance-readiness, underwriting approval, creditworthiness, rating, or guarantee.

345.3.2 Capital-readability shall not be used as a substitute term for finance-readiness where the publication lacks GRA authority or other competent finance-readiness status.

345.3.3 Any capital-readable label shall identify scope, audience, limitations, record basis, and non-reliance language.

345.4 Proof-Pack Reference Review.

345.4.1 Proof-pack references shall be reviewed for potential implication of validation, verification, finance-readiness, investment readiness, rating, certification, public authority approval, procurement approval, or underwriting support.

345.4.2 Proof packs may describe organized records, evidence, source lineage, proof receipts, compute records, inference records, methods records, limitations, and public-safe summaries only within their documented scope.

345.4.3 No proof pack shall be represented as proving investment suitability, project viability, creditworthiness, insurance readiness, bankability, legal compliance, procurement eligibility, public authority adoption, recognition, or certification.

345.5 Insurance-Readiness Reference Review.

345.5.1 Insurance-readiness references shall be treated as restricted finance-boundary references and shall not be used unless supported by competent authority and reviewed for insurance regulation, underwriting implication, risk-transfer implication, claims-handling implication, pricing implication, broker implication, public-safe reliance risk, and role separation.

345.5.2 GCRI US publications may discuss evidence, resilience indicators, data quality, risk observability, and methods that could be useful to insurance readers only with clear limitation language that the Corporation does not place insurance, bind coverage, underwrite risk, price policies, handle claims, certify insurability, or approve insurance readiness.

345.6 Diligence Translation Reference Review.

345.6.1 Diligence translation references shall be reviewed to ensure they describe translation of technical evidence, methods, records, limitations, and public-safe summaries into formats understandable by diligence readers without becoming investment advice, legal advice, accounting advice, engineering certification, insurance underwriting, credit analysis, securities analysis, or rating activity.

345.6.2 Diligence translation shall not state or imply that diligence is complete, sufficient, independently verified, validated for investment, or approved for financing.

345.6.3 Diligence translation outputs shall identify sources, limitations, excluded matters, non-reliance conditions, and correction path.

345.7 Capital-Reader Room Reference Review.

345.7.1 References to capital-reader rooms, investor rooms, diligence rooms, finance rooms, public finance reader rooms, lender-reader rooms, insurer-reader rooms, or analogous spaces shall be reviewed for securities, finance, lending, insurance, rating, public finance, confidentiality, access, data rights, and non-execution implications.

345.7.2 A capital-reader room shall be described only as a controlled access environment for review of defined materials by defined audiences and shall not imply offering, solicitation, placement, underwriting, endorsement, investment recommendation, credit approval, insurance approval, public finance approval, or guarantee.

345.7.3 Access to a capital-reader room shall not be represented as approval, qualification, endorsement, recognition, finance-readiness, procurement eligibility, public authority support, or investment validation.

345.8 RNFD, NFD, UNFSD, and Nexus Rails Reference Review.

345.8.1 References to Regional Nexus Financing for Development (RNFD), National Nexus Financing for Development (NFD), Universal Nexus Financing for Sustainable Development (UNFSD), Nexus Rails, or related finance-facing Nexus structures shall be reviewed for role separation, authority, finance-boundary language, GRA interface, public authority implications, public finance implications, securities risk, capital-market risk, and public-safe reliance.

345.8.2 Such references shall distinguish public-good evidence infrastructure, rails, learning, records, and technical translation from actual financing, securities issuance, lending, underwriting, insurance placement, public finance approval, grants, appropriations, guarantees, MDB / DFI approvals, or capital execution.

345.8.3 Nexus Rails references shall not imply that GCRI US operates capital rails, places capital, arranges transactions, approves projects, guarantees outcomes, or provides regulated financial services.

345.9 No Investment Advice.

345.9.1 No Corporation publication, output, communication, evidence pack, dashboard, map, dataset, software output, proof receipt, technical baseline, report, whitepaper, presentation, or public-safe summary shall constitute investment advice, recommendation to buy, sell, hold, invest, divest, finance, refinance, insure, lend, guarantee, underwrite, or commit capital.

345.9.2 Publications that may be read by investors or capital readers shall include limitation language sufficient to avoid investment-advice reliance.

345.10 No Securities Offering or Solicitation.

345.10.1 No Corporation publication or communication shall constitute an offer to sell, solicitation of an offer to buy, private placement memorandum, offering circular, investment teaser, securities advertisement, crowdfunding communication, investment solicitation, or securities transaction document.

345.10.2 References to projects, SPVs, national companies, sponsors, providers, infrastructure, capital needs, resilience investments, or finance-facing evidence shall not be framed as securities offerings or solicitations.

345.11 No Broker-Dealer, Finder, Placement, or Underwriting Activity.

345.11.1 GCRI US shall not act as broker-dealer, finder, placement agent, underwriter, investment bank, securities intermediary, capital arranger, transaction advisor, investment platform, exchange, marketplace, or compensation-based capital introducer through publication activity or references.

345.11.2 Publications shall not state or imply that the Corporation arranges, negotiates, places, markets, distributes, underwrites, sells, or intermediates securities, loans, guarantees, insurance, public finance instruments, or investments.

345.12 No Lending, Banking, Credit Approval, or Guarantee.

345.12.1 No Corporation publication shall constitute lending approval, banking service, credit decision, credit support, guarantee, loan recommendation, borrowing recommendation, covenant assessment, collateral valuation, debt service assessment, or bankability determination.

345.12.2 References to resilience, maturity, observability, technical evidence, or project records shall not be represented as sufficient for credit approval or lending reliance.

345.13 No Insurance Placement, Binding, Underwriting, Pricing, Claims Handling, or Approval.

345.13.1 No Corporation publication shall constitute insurance placement, insurance brokerage, binding of coverage, underwriting, pricing, actuarial opinion, claims handling, policy approval, risk-transfer approval, insurance recommendation, or insurability determination.

345.13.2 Insurance-facing readers shall be informed that Corporation outputs are evidence-support or public-good technical materials only and not insurance decisions or insurance advice.

345.14 No Rating, Credit Opinion, Investment Grade Opinion, Resilience Rating, Insurability Rating, Bankability Rating, or Financeability Determination.

345.14.1 No Corporation publication shall constitute a rating, credit opinion, investment grade opinion, resilience rating, insurability rating, bankability rating, financeability determination, risk rating, provider rating, project rating, infrastructure rating, or capital-market grade.

345.14.2 Scores, maturity references, evidence classes, dashboard indicators, technical profiles, proof receipts, benchmark outcomes, or public-safe summaries shall not be presented as ratings or rating substitutes.

345.15 No Public Finance Approval, Grant Approval, Tax Credit Approval, Appropriation, MDB / DFI Approval, Public Guarantee, Public Credit, or Sovereign Obligation.

345.15.1 No Corporation publication shall constitute public finance approval, grant approval, tax credit approval, appropriation, budget authorization, MDB / DFI approval, public guarantee, public credit support, sovereign obligation, municipal obligation, public-private partnership approval, or governmental fiscal commitment.

345.15.2 References to public finance readers, MDB / DFI audiences, government funding programs, grant programs, tax credits, appropriations, guarantees, or public capital shall be limited, accurate, and non-committal unless supported by competent public authority records.

345.16 GRA Role-Separation Language.

345.16.1 Where finance-readiness, capital-readability, insurance-readiness, diligence translation, proof packs, capital-reader rooms, Nexus Rails, RNFD, NFD, UNFSD, or other finance-facing concepts are referenced, the publication shall include GRA role-separation language where necessary.

345.16.2 GRA role-separation language shall distinguish GCRI US evidence, methods, observability, public-good technical asset, and public-safe publication functions from The Global Risks Alliance (GRA)’s separate finance-readiness, capital-reader, and finance-facing functions where applicable.

345.16.3 GRA role-separation language shall not itself imply that GRA has issued finance-readiness, approved a project, arranged financing, or accepted any obligation.

345.17 Non-Reliance Language.

345.17.1 Finance-facing publications shall include non-reliance language appropriate to the audience and risk, stating that the material is not investment advice, securities advice, insurance advice, lending advice, rating, public finance approval, procurement approval, guarantee, or solicitation.

345.17.2 Non-reliance language shall be clear, proximate, and consistent with the substance of the publication. It shall not be used to sanitize a publication that, in substance, operates as a financial recommendation, solicitation, rating, or approval.

345.18 Finance-Boundary Reference Records.

345.18.1 The Corporation shall maintain Finance-Boundary Reference Records, including finance-boundary purpose records, finance-readiness reference review records, capital-readability reference review records, proof-pack reference review records, insurance-readiness reference review records, diligence translation reference review records, capital-reader room reference review records, RNFD / NFD / UNFSD / Nexus Rails reference review records, no-investment-advice records, no-securities-offering or solicitation records, no-broker-dealer / finder / placement / underwriting records, no-lending / banking / credit approval / guarantee records, no-insurance placement / binding / underwriting / pricing / claims handling / approval records, no-rating records, no-public-finance-approval records, GRA role-separation records, non-reliance language records, corrections, withdrawals, and archive records.

---

Section 346. Certification, Accreditation, Conformance, Compliance, Procurement, Recognition, Maturity, Docket, Grid, and Nexus-Compatible References

346.1 Certification-Boundary Reference Purpose.

346.1.1 Certification-Boundary References shall be governed to prevent Corporation publications, technical assets, public-safe summaries, dashboards, maps, datasets, evidence packs, software outputs, technical baselines, Docket references, Grid references, Nexus-Compatible references, partner materials, sponsor materials, provider materials, or media materials from being misread as certification, accreditation, conformance approval, legal compliance approval, procurement approval, public authority adoption, recognition, maturity determination, standing determination, finance-readiness, rating, provider preference, public warning, emergency command, or execution authority.

346.1.2 Certification-Boundary References shall preserve role separation among GCRI US, The Global Risks Forum (GRF), The Global Risks Alliance (GRA), Nexus Standards, protocol authorities where constituted, public authorities, procurement bodies, certifiers, accreditors, professional bodies, providers, sponsors, consortiums, national companies, Project SPVs, and enterprise actors.

346.1.3 Certification-Boundary References shall be reviewed by the reasonable meaning conveyed to the relevant audience, including the effect of words, badges, seals, labels, scores, dashboards, maps, color schemes, public authority references, compatibility terms, and Nexus vocabulary.

346.2 Certification Reference Review.

346.2.1 Certification references, including “certified,” “certification,” “certifies,” “certifying,” “certified by,” “certifiable,” “certification-ready,” and similar terms, shall be treated as restricted terms.

346.2.2 No certification reference shall be used unless a competent certification authority, process, criteria, scope, version, record, and limitation support the specific reference.

346.2.3 GCRI US shall not be described as certifying persons, providers, products, projects, software, models, datasets, systems, infrastructure, maturity, resilience, public authority readiness, finance-readiness, procurement readiness, legal compliance, or safety by default.

346.3 Accreditation Reference Review.

346.3.1 Accreditation references shall be reviewed to prevent implication that the Corporation accredits institutions, programs, providers, laboratories, training programs, public authorities, technical systems, reviewers, maintainers, fellows, courses, or workforce credentials unless a separate competent accreditation framework exists and the statement is authorized.

346.3.2 Academy, training, fellowship, learning, orientation, or workforce materials shall not be described as accredited unless such status is lawfully granted and accurately stated.

346.4 Conformance Reference Review.

346.4.1 Conformance references shall identify the exact standard, baseline, profile, schema, API, SDK, test harness, version, scope, test conditions, review process, authority, and limitations supporting the conformance statement.

346.4.2 Conformance references shall not imply certification, accreditation, legal compliance, procurement eligibility, public authority adoption, finance-readiness, recognition, rating, or provider preference unless separately supported by competent record.

346.4.3 Passing a test harness or validation script shall not create conformance approval unless the applicable test authority expressly provides that result and competent records support it.

346.5 Compliance Reference Review.

346.5.1 Compliance references shall be reviewed for legal, regulatory, cybersecurity, privacy, AI, procurement, export-control, sanctions, tax, charitable, public records, public authority, professional, and standards-related implications.

346.5.2 The Corporation shall avoid stating that any person, product, project, provider, system, dataset, model, software, infrastructure, public authority activity, or implementation is “compliant” unless competent legal or technical review supports the precise compliance claim, jurisdiction, framework, version, and scope.

346.5.3 Alignment with a Corporation technical baseline or public-good technical asset shall not be called legal compliance.

346.6 Procurement Reference Review.

346.6.1 Procurement references shall be reviewed where a publication references vendor eligibility, provider qualification, public contract readiness, preferred provider status, public purchasing, grant eligibility, procurement criteria, procurement specifications, public-private partnerships, national company selection, Project SPV selection, or enterprise procurement.

346.6.2 No Corporation publication shall state or imply procurement approval, procurement recommendation, preferred-provider status, public contract eligibility, grant eligibility, purchasing recommendation, or vendor qualification unless a competent procurement authority separately and lawfully records such status and the Corporation accurately states its non-procurement role.

346.7 Recognition Reference Review.

346.7.1 Recognition references shall be reviewed for GRF authority, registry status, public-facing standing, legitimacy implication, maturity implication, public-good status, public-safe reporting status, and stakeholder-formation implication.

346.7.2 GCRI US shall not state or imply that it recognizes, grants standing to, lists as legitimate, endorses, approves, ranks, certifies, or gives public-facing maturity status to persons, providers, projects, national companies, Project SPVs, public authorities, communities, technical assets, or implementations unless separately authorized and accurately limited.

346.7.3 References to The Global Risks Forum (GRF) shall preserve GRF’s separate recognition, registry, maturity-records, public-facing legitimacy, claims-discipline, and public-safe reporting functions.

346.8 Maturity Reference Review.

346.8.1 Maturity references shall be reviewed to determine whether they imply GRF standing, Grid maturity, finance-readiness, certification, procurement readiness, public authority readiness, operational readiness, or provider ranking.

346.8.2 GCRI US may describe method maturity, evidence maturity, software maturity, release maturity, dataset maturity, documentation maturity, or technical baseline maturity only where defined, scoped, versioned, limitation-aware, and not confused with GRF maturity standing or Grid maturity status.

346.9 Standing Reference Review.

346.9.1 Standing references, including legitimacy standing, registry standing, public-good standing, ecosystem standing, maturity standing, provider standing, or participant standing, shall be reviewed for GRF authority and public-facing reliance risk.

346.9.2 GCRI US shall not issue public-facing standing determinations by default and shall not imply standing through evidence records, public-safe summaries, dashboards, software outputs, proof receipts, or technical baselines.

346.10 Docket Reference Review.

346.10.1 Docket references shall distinguish Docket input, Docket record, Docket entry, Docket package, Docket status, Docket routing, Docket review, and Docket decision where applicable.

346.10.2 GCRI US materials may support Docket inputs through evidence, methods, technical records, public-safe summaries, and correction records but shall not imply Docket approval, Docket acceptance, Docket standing, Docket maturity, public authority adoption, recognition, finance-readiness, certification, procurement approval, or execution authority unless a separate competent Docket authority records such status.

346.11 Grid Reference Review.

346.11.1 Grid references shall distinguish Grid input, Grid maturity record, Grid routeability, Grid status, Grid-facing package, Grid review, Grid update, and Grid decision where applicable.

346.11.2 GCRI US shall not guarantee Grid placement, Grid maturity, Grid routing, Grid acceptance, Grid result, finance-readiness, recognition, procurement eligibility, public authority adoption, certification, or provider status.

346.11.3 Grid references shall include limitation language where public or capital readers may misunderstand Grid-related language as approval or rating.

346.12 Nexus-Compatible Reference Review.

346.12.1 Nexus-Compatible references shall be reviewed for criteria, version, interface, scope, technical asset, public-safe status, authority, and limitations.

346.12.2 Nexus-Compatible shall not mean certified, recognized, finance-ready, procurement-approved, public authority-adopted, provider-preferred, rated, public-warning-ready, emergency-ready, operationally approved, or execution-authorized.

346.12.3 Nexus-Compatible references shall distinguish technical compatibility, semantic compatibility, evidence-format compatibility, interface compatibility, partial compatibility, and experimental compatibility.

346.13 GRF Role-Separation Language.

346.13.1 Publications referencing recognition, maturity, standing, registry, public-facing legitimacy, public-good status, claims discipline, or stakeholder-facing recognition shall include GRF role-separation language where necessary.

346.13.2 GRF role-separation language shall distinguish GCRI US evidence, methods, observability, software, technical baselines, and public-safe publications from The Global Risks Forum (GRF)’s separate authority over recognition, registry, public-facing legitimacy, standing, maturity records, and claims discipline.

346.14 Nexus Standards and Protocol Authority Role-Separation Language.

346.14.1 Publications referencing standards, conformance, protocols, profiles, test harnesses, interoperability, technical baselines, compatibility, validation, verification, or technical criteria shall include Nexus Standards or protocol authority role-separation language where necessary.

346.14.2 Such language shall distinguish GCRI US technical evidence and methods support from formal standards authority, protocol governance, certification, conformance approval, network operation, validator authority, node operation, public authority standard-setting, or procurement authority.

346.15 GRA Role-Separation Language Where Finance Meaning Is Possible.

346.15.1 Publications referencing Grid, Docket, maturity, proof packs, diligence translation, capital-readability, finance-facing evidence, project readiness, infrastructure readiness, or capital-reader materials shall include GRA role-separation language where finance meaning is possible.

346.15.2 Such language shall distinguish GCRI US evidence support from The Global Risks Alliance (GRA)’s separate finance-readiness functions and from any regulated financial, insurance, lending, rating, public finance, or capital-market activity.

346.16 No Certification by GCRI US by Default.

346.16.1 GCRI US shall not certify persons, providers, projects, systems, software, models, datasets, dashboards, maps, technical baselines, infrastructure, public authorities, national companies, Project SPVs, maturity states, resilience states, finance-readiness, procurement readiness, legal compliance, cybersecurity compliance, AI compliance, privacy compliance, or professional competence by default.

346.16.2 Any future certification function, if ever lawfully created, shall require separate governing authority, criteria, records, independence, conflict controls, legal review, public-safe claims controls, and express limitation language.

346.17 No Procurement Approval.

346.17.1 GCRI US shall not approve procurement, recommend vendors for procurement, qualify providers for procurement, rank bidders, issue public contract eligibility, create public-private partnership eligibility, approve grant eligibility, or establish purchasing specifications by default.

346.17.2 Technical baselines, software, dashboards, maps, public-safe summaries, evidence packs, Nexus-compatible references, Docket inputs, Grid inputs, or publication references shall not be used as procurement approval by GCRI US.

346.18 No Recognition or Maturity Determination by GCRI US.

346.18.1 GCRI US shall not issue GRF recognition, public-facing standing, registry standing, legitimacy recognition, maturity standing, stakeholder recognition, or public-good recognition by default.

346.18.2 Evidence, methods, observability, public-safe publication, and technical asset outputs may support records that another competent body may consider, but shall not themselves constitute recognition or maturity determination.

346.19 No Grid Guarantee or Docket Approval by GCRI US.

346.19.1 GCRI US shall not guarantee Grid status, Grid maturity, Grid routing, Docket entry, Docket approval, Docket acceptance, Docket standing, or downstream treatment by any Nexus body.

346.19.2 GCRI US may prepare or support evidence records, methods records, public-safe summaries, proof receipts, and technical materials that are eligible for routing or consideration only where applicable rules allow and limitations are stated.

346.20 Reference Correction for Overclaim.

346.20.1 Where any publication, partner material, sponsor material, provider material, public authority material, media material, dashboard, map, software output, repository description, public-safe summary, report, whitepaper, technical note, or social media post overclaims certification, accreditation, conformance, compliance, procurement approval, recognition, maturity, standing, Docket status, Grid status, Nexus compatibility, finance-readiness, public authority adoption, public warning, emergency command, or provider preference, the Corporation shall require correction.

346.20.2 Correction may include revision, limitation language, badge removal, mark restriction, takedown, public clarification, controlled clarification, notice to affected authority, GRF referral, GRA referral, Nexus Standards referral, public authority referral, legal review, or termination of participation.

346.21 Certification, Procurement, Recognition, Docket, Grid, and Compatibility Reference Records.

346.21.1 The Corporation shall maintain Certification, Procurement, Recognition, Docket, Grid, and Compatibility Reference Records, including certification-boundary purpose records, certification reference reviews, accreditation reference reviews, conformance reference reviews, compliance reference reviews, procurement reference reviews, recognition reference reviews, maturity reference reviews, standing reference reviews, Docket reference reviews, Grid reference reviews, Nexus-Compatible reference reviews, GRF role-separation records, Nexus Standards and protocol authority role-separation records, GRA role-separation records, no-certification records, no-procurement-approval records, no-recognition or maturity determination records, no-Grid-guarantee or Docket-approval records, overclaim correction records, corrections, withdrawals, and archive records.

---

Section 347. Sponsor, Donor, Funder, Provider, Host, Partner, University, Laboratory, Community, Tribal / Indigenous, Civil Society, and Media References

347.1 Third-Party Reference Purpose.

347.1.1 Third-Party References shall be governed to ensure that references to sponsors, donors, funders, providers, hosts, partners, universities, laboratories, communities, Tribal / Indigenous bodies, civil society organizations, media organizations, contributors, collaborators, reviewers, participants, and other non-Corporation actors are accurate, role-specific, permission-aware, conflict-reviewed, public-safe, non-misleading, and consistent with the Corporation’s public-benefit purpose and role separation.

347.1.2 Third-Party References may appear in acknowledgments, reports, whitepapers, technical notes, dashboards, maps, datasets, software documentation, repositories, open technical baselines, event materials, Academy materials, public authority learning materials, press releases, web pages, social media, newsletters, donor reports, sponsor reports, provider materials, partner materials, and media materials.

347.1.3 Third-Party References shall preserve the distinction between support and control, funding and endorsement, contribution and approval, hosting and authority, participation and adoption, data provision and agreement with analysis, technical assistance and provider preference, community input and unrestricted knowledge use, media coverage and institutional approval.

347.2 Sponsor Reference.

347.2.1 Sponsor references shall accurately describe the sponsor’s role, including financial support, in-kind support, event support, technical support, hosting, cloud credits, equipment access, program support, or other defined support.

347.2.2 Sponsor references shall not imply that the sponsor controls research agenda, evidence conclusions, methods, technical baselines, software roadmaps, publications, corrections, public authority interfaces, GRF recognition, GRA finance-readiness, procurement outcomes, provider selection, or public-safe framing.

347.2.3 Sponsor references shall include disclosure sufficient to prevent perceived or actual conflict from misleading audiences.

347.3 Donor Reference.

347.3.1 Donor references shall accurately describe donor support and any relevant restrictions, without overstating donor role or implying donor approval of outputs.

347.3.2 Donor acknowledgment shall not imply that the donor endorses the Corporation’s findings, methods, publications, technical assets, public authority interfaces, Nexus roles, GRF recognition activity, GRA finance-readiness activity, or any project outcome unless separately authorized.

347.3.3 Anonymous donor references shall be handled according to legal, ethical, conflict, transparency, charitable compliance, and public-safe requirements.

347.4 Funder Reference.

347.4.1 Funder references shall distinguish grantor, donor, sponsor, public funder, philanthropic funder, research funder, contract funder, restricted funder, unrestricted funder, and program funder.

347.4.2 Funder references shall accurately state whether the funder funded the Corporation, a program, a publication, a dataset, a technical asset, an event, a fellowship, a controlled room, public authority learning, or another defined activity.

347.4.3 Funder references shall not imply approval of findings, finance-readiness, recognition, procurement status, public authority adoption, certification, rating, or outcome purchase.

347.5 Provider Reference.

347.5.1 Provider references shall accurately describe any provider role, including technology provider, data provider, cloud provider, AI provider, cybersecurity provider, repository provider, telecom provider, infrastructure provider, implementation provider, qualified enterprise provider, or other service provider role.

347.5.2 Provider references shall preserve provider neutrality and shall not imply preferred status, certification, procurement qualification, technical approval, public authority approval, finance-readiness, recognition, rating, or endorsement.

347.5.3 Provider contributions to public-good technical assets shall be disclosed where material and shall not confer control over roadmap, release, technical baseline content, public-safe language, or correction.

347.6 Host Reference.

347.6.1 Host references shall accurately describe hosting of events, meetings, controlled rooms, data rooms, technical workshops, public authority learning sessions, Academy sessions, repositories, infrastructure, cloud environments, or other hosted activities.

347.6.2 Hosting shall not imply endorsement, adoption, official approval, procurement approval, finance-readiness, recognition, certification, provider preference, public authority approval, or control over content unless separately supported by competent record.

347.6.3 Host logos, venue references, public authority references, and co-branding shall be reviewed for public-safe interpretation.

347.7 Partner Reference.

347.7.1 Partner references shall be used only where a partnership, collaboration, memorandum, project, program, working relationship, or co-publication is supported by competent record.

347.7.2 The term “partner” shall not be used to imply legal partnership, agency, joint venture, shared treasury, shared liability, shared governance, public authority delegation, procurement relationship, or execution authority unless such relationship is lawfully created and accurately described.

347.7.3 Partner references shall identify the role, scope, duration, authority, limitations, and whether the partner reviewed, approved, funded, hosted, contributed to, or merely participated in the referenced activity.

347.8 University and Laboratory Reference.

347.8.1 University and laboratory references shall accurately describe institutional role, researcher role, lab role, student role, faculty role, fellow role, research collaboration, data contribution, technical review, publication contribution, hosting, funding, or advisory participation.

347.8.2 University or laboratory participation shall not imply institutional endorsement, peer review, academic validation, public authority adoption, certification, procurement approval, finance-readiness, recognition, rating, or guarantee unless authorized by competent institutional record.

347.8.3 Publications shall respect academic freedom, publication rights, IP terms, research ethics, student protections, data rights, conflicts, attribution, and correctionability.

347.9 Community Reference.

347.9.1 Community references shall be accurate, respectful, safeguards-reviewed, and non-extractive.

347.9.2 References to communities, community organizations, community participants, local knowledge, vulnerability information, public health concerns, environmental concerns, resilience priorities, or community-provided data shall not imply endorsement, unrestricted permission, public authority status, public-safe mapping permission, data ownership transfer, or consent to all downstream uses.

347.9.3 Community references may require non-attribution, aggregation, redaction, delayed publication, public-safe mapping limits, grievance pathways, or withdrawal where necessary to prevent harm.

347.10 Tribal / Indigenous Reference Where Lawfully and Respectfully Approved.

347.10.1 Tribal / Indigenous references shall be made only where lawful, respectful, permission-aware, sovereignty-aware, protocol-aware, safeguards-reviewed, and consistent with any applicable restrictions on attribution, non-attribution, publication, mapping, AI use, transfer, translation, commercialization, correction, withdrawal, and grievance.

347.10.2 The Corporation shall not reference Tribal / Indigenous governments, peoples, communities, representatives, knowledge holders, data, territories, cultural materials, sacred knowledge, ecological knowledge, or protected knowledge in a manner that implies endorsement, waiver of sovereignty, unrestricted data permission, knowledge-use permission, public authority adoption, public warning, emergency command, finance-readiness, recognition, certification, or procurement approval.

347.11 Civil Society Reference.

347.11.1 Civil society references shall accurately describe the role of nonprofits, NGOs, associations, coalitions, advocacy groups, professional societies, community-based organizations, foundations, think tanks, or other civil society actors.

347.11.2 Civil society participation shall not imply endorsement, institutional adoption, certification, recognition, procurement approval, public authority approval, finance-readiness, rating, or control over Corporation outputs unless supported by competent record.

347.11.3 Civil society references shall be reviewed for conflicts, public-safe framing, community safeguards, protected knowledge, and role accuracy.

347.12 Media Reference.

347.12.1 Media references shall accurately describe coverage, interview, quotation, appearance, publication, recording, press attendance, media partnership where lawfully established, or media inquiry.

347.12.2 Media coverage shall not be treated as validation, certification, recognition, public authority approval, finance-readiness, procurement approval, evidence proof, or endorsement.

347.12.3 Press materials shall avoid overstating institutional role, public authority participation, sponsor support, provider involvement, project readiness, finance-readiness, recognition, or technical status.

347.13 Public Acknowledgment Controls.

347.13.1 Public acknowledgments shall be accurate, proportionate, permission-aware, conflict-reviewed where material, and limited to the role actually performed.

347.13.2 Acknowledgments shall distinguish funding, sponsorship, donation, hosting, technical contribution, data contribution, review, comment, participation, authorship, advisory input, public authority participation, and publication approval.

347.13.3 Acknowledgments shall not be sold, traded, implied, promised, or structured as endorsement, outcome purchase, influence purchase, provider preference, procurement advantage, recognition, finance-readiness, or public authority access.

347.14 Contribution Record Requirement.

347.14.1 Material Third-Party References shall be supported by Contribution Records identifying the third party, contribution type, date, scope, authority, restrictions, conflicts, acknowledgment permissions, attribution rules, confidentiality, data rights, IP rights, publication rights, correction path, and whether public acknowledgment is permitted.

347.14.2 Contribution Records shall distinguish factual contribution from approval, endorsement, adoption, control, responsibility, and outcome support.

347.14.3 Where contribution records are insufficient, the Corporation shall use narrower language, obtain clarification, omit the reference, or restrict publication.

347.15 Role Description Accuracy.

347.15.1 Role descriptions shall be accurate, specific, and proportionate to the actual role performed.

347.15.2 Publications shall not use broad terms such as “partner,” “supporter,” “approved by,” “recognized by,” “in collaboration with,” “powered by,” “with,” “endorsed by,” “official,” “certified,” “trusted by,” “public authority-backed,” “finance-ready,” “provider-approved,” or “Nexus-approved” unless the term is authorized, defined, and not misleading.

347.15.3 Role descriptions shall be corrected where they create role inflation, sponsor overclaim, provider overclaim, public authority overclaim, finance overclaim, certification overclaim, recognition overclaim, procurement overclaim, or community overclaim.

347.16 No Endorsement by Reference.

347.16.1 Reference to a sponsor, donor, funder, provider, host, partner, university, laboratory, community, Tribal / Indigenous body, civil society organization, media organization, public authority, or other third party shall not imply endorsement by that party of the Corporation, its publications, findings, methods, technical assets, software, baselines, dashboards, maps, evidence packs, public-safe summaries, Nexus role, GRF-related activity, GRA-related activity, public authority learning, or any project outcome unless competent record supports the specific endorsement.

347.16.2 Reference to the Corporation by any third party shall not imply Corporation endorsement of that third party or its products, services, projects, investments, providers, public authority status, recognition, finance-readiness, certification, procurement eligibility, rating, or claims unless separately authorized.

347.17 No Control, Preferred Status, Procurement Advantage, Certification, Recognition, Finance-Readiness, Public Authority Access, or Outcome Purchase by Reference.

347.17.1 No Third-Party Reference shall create or imply that the referenced actor has control over Corporation decisions, preferred status, procurement advantage, certification, recognition, finance-readiness, public authority access, public authority influence, Grid status, Docket status, Nexus-compatible status, provider qualification, publication approval, research conclusions, method design, software roadmap, technical baseline content, correction decisions, or outcome purchase.

347.17.2 Support, funding, sponsorship, donation, hosting, technical contribution, public authority participation, data contribution, community input, media coverage, university collaboration, or provider participation shall not purchase, guarantee, or influence public-good outcomes, recognition, finance-readiness, procurement results, certification-like status, public authority action, or publication conclusions.

347.17.3 Where a Third-Party Reference could reasonably imply such control or benefit, the Corporation shall revise, qualify, restrict, omit, correct, or withdraw the reference.

347.18 Third-Party Reference Records.

347.18.1 The Corporation shall maintain Third-Party Reference Records, including third-party reference purpose records, sponsor reference records, donor reference records, funder reference records, provider reference records, host reference records, partner reference records, university and laboratory reference records, community reference records, Tribal / Indigenous reference records, civil society reference records, media reference records, public acknowledgment control records, Contribution Records, role description records, no-endorsement records, no-control / preferred-status / procurement-advantage / certification / recognition / finance-readiness / public-authority-access / outcome-purchase records, corrections, withdrawals, and archive records.

Section 348. Dashboards, Maps, Geospatial Outputs, Public-Safe Visualizations, and Interactive Tools

348.1 Dashboard Purpose.

348.1.1 Dashboards shall be governed as public-good evidence interfaces, observability interfaces, technical asset status interfaces, data-quality interfaces, public authority learning interfaces, internal review interfaces, controlled-room interfaces, and public-safe communication tools, and not as public warning systems, emergency command systems, public authority decision systems, rating systems, certification systems, procurement systems, finance-readiness systems, recognition systems, or provider-preference systems.

348.1.2 Dashboards may display evidence summaries, observability records, resilience indicators, technical baseline information, repository status, software status, dataset status, public-safe indicators, method outputs, benchmark summaries, model evaluation summaries, Docket-facing inputs, Grid-facing inputs, GRF-facing inputs, GRA-facing inputs, public authority learning materials, community safeguards information, or other approved materials only within the access class, review status, and limitation language approved for such dashboard.

348.1.3 Dashboards shall be designed to prevent false precision, false certainty, unsupported comparison, public authority overclaim, finance overclaim, certification overclaim, recognition overclaim, procurement overclaim, provider preference, public warning implication, emergency command implication, stigmatization, protected knowledge exposure, cyber exposure, infrastructure exposure, privacy exposure, or unsafe reliance.

348.2 Map Purpose.

348.2.1 Maps shall be governed as geospatial evidence-support, observability-support, public-safe learning, technical communication, community-safeguards, and public authority learning tools, and not as operational maps, public warning maps, emergency command maps, evacuation maps, procurement maps, finance-readiness maps, certification maps, recognition maps, rating maps, provider-ranking maps, or official public authority maps unless separately and lawfully issued by a competent public authority.

348.2.2 Maps may depict only information that has been reviewed for data rights, public-safe status, geospatial accuracy, scale, resolution, confidence, uncertainty, sensitive-location risk, infrastructure-sensitive risk, cyber-sensitive risk, public authority restrictions, protected knowledge, community safeguards, privacy, accessibility, civil rights, and correctionability.

348.2.3 Map design shall avoid unsafe visual signals, including alarm-like colors, ranking-like labels, official-seal-like graphics, emergency-warning visual grammar, unsupported risk gradients, misleading boundaries, unreviewed hotspot claims, false precision, or visual cues that imply public authority command, finance-readiness, recognition, certification, procurement approval, rating, or provider preference.

348.3 Geospatial Output Purpose.

348.3.1 Geospatial Outputs shall include maps, layers, tiles, spatial datasets, coordinates, polygons, boundaries, heatmaps, cluster views, hotspot views, regional cluster views, national dense Nexus core views, digital twin spatial outputs, Earth observation outputs, sensor-linked geospatial outputs, public-safe mapping outputs, dashboards, and visualizations that express place-based or location-related information.

348.3.2 Geospatial Outputs shall be governed to preserve contextual accuracy, community safety, protected knowledge safeguards, public authority boundaries, critical infrastructure protection, public-safe mapping discipline, evidence integrity, and correctionability.

348.3.3 Geospatial Outputs shall not be published or externally shared at a resolution, precision, specificity, or interpretive framing that materially increases risk to persons, communities, infrastructure, ecosystems, protected sites, public authorities, or sensitive systems.

348.4 Public-Safe Visualization Purpose.

348.4.1 Public-Safe Visualizations shall convert evidence, methods, observability, technical asset status, dataset status, model results, benchmark results, public authority learning materials, or public-good technical materials into visual form only where the visual form remains faithful to the underlying record and its limitations.

348.4.2 Public-Safe Visualizations shall be reviewed for scale distortion, color distortion, omitted context, misleading comparison, inappropriate aggregation, inappropriate disaggregation, false trend, false causation, false ranking, false certainty, accessibility barriers, cultural sensitivity, public authority overclaim, finance overclaim, certification overclaim, recognition overclaim, procurement overclaim, and provider-preference implication.

348.4.3 Visual simplification shall not remove material limitations, uncertainty, source qualifications, access classifications, correction status, or non-execution boundaries.

348.5 Interactive Tool Purpose.

348.5.1 Interactive Tools shall include public-facing, internal, controlled, restricted, or public authority-facing tools that allow users to filter, query, compare, simulate, visualize, export, review, annotate, validate, generate, or interact with data, evidence, methods, maps, dashboards, software, technical baselines, model outputs, benchmark results, proof receipts, or public-safe summaries.

348.5.2 Interactive Tools shall be governed for access control, public-safe output, input validation, logging where appropriate, privacy, cybersecurity, AI-use restrictions, export restrictions, data rights, protected knowledge, public authority boundaries, finance boundaries, certification boundaries, recognition boundaries, procurement neutrality, provider neutrality, and correctionability.

348.5.3 Interactive Tools shall not allow users to generate outputs that appear to be official decisions, public warnings, emergency commands, certifications, procurement approvals, finance-readiness determinations, ratings, recognition determinations, provider rankings, legal compliance approvals, or operational instructions unless a separate competent authority lawfully controls and issues such outputs.

348.6 Source Disclosure.

348.6.1 Dashboards, maps, visualizations, and interactive tools shall disclose or make traceable the sources supporting displayed information at a level appropriate to the access class, public-safe status, confidentiality, data rights, and audience.

348.6.2 Source disclosure may include source name, source class, source date, source version, source authority, source lineage, public authority data status, community data status, protected knowledge status, dataset card, method note, evidence record, model record, benchmark card, or public-safe summary.

348.6.3 Source disclosure shall not overdisclose restricted sources, personal information, protected knowledge, cyber-sensitive data, infrastructure-sensitive data, public authority restricted data, or confidential source details. Where full disclosure is unsafe, the Corporation may use aggregated, generalized, controlled, redacted, or non-attributed source descriptions.

348.7 Update Status.

348.7.1 Dashboards, maps, visualizations, and interactive tools shall indicate update status where timeliness affects interpretation, including current, delayed, periodic, historical, frozen, archived, deprecated, superseded, under review, corrected, withdrawn, or experimental status.

348.7.2 Update status shall identify whether information is live, near-real-time, periodically updated, manually updated, snapshot-based, modeled, simulated, derived, static, or no longer maintained.

348.7.3 No output shall be described as live, current, validated, complete, official, operational, public-warning-ready, emergency-ready, finance-ready, recognized, certified, or procurement-ready unless the record supports that precise status.

348.8 Timestamp and Version.

348.8.1 Dashboards, maps, visualizations, and interactive tools shall include timestamps, version identifiers, data currency indicators, model version indicators, method version indicators, baseline version indicators, release version indicators, or snapshot dates where material to interpretation.

348.8.2 Timestamp and version information shall distinguish data collection date, source date, processing date, publication date, update date, model inference date, dashboard refresh date, map layer date, software release date, and correction date where necessary.

348.8.3 Timestamp and version records shall support correction, auditability, supersession, withdrawal, archive, and downstream dependency review.

348.9 Confidence and Limitation Display.

348.9.1 Dashboards, maps, visualizations, and interactive tools shall display confidence, uncertainty, limitations, data gaps, coverage gaps, source limitations, method limitations, model limitations, geospatial limitations, temporal limitations, resolution limitations, public-safe limitations, and use restrictions where material to interpretation.

348.9.2 Confidence and limitation display shall be proximate to the relevant output and understandable to the intended audience.

348.9.3 A visualization shall not use design features that hide, minimize, or contradict stated limitations, including misleading colors, rankings, leaderboards, icons, alerts, labels, or default views.

348.10 Classification Display.

348.10.1 Dashboards, maps, visualizations, and interactive tools shall display classification or access status where material, including public, public-safe, internal, controlled, confidential, restricted, public authority, community-protected, protected knowledge, finance-sensitive, cyber-sensitive, infrastructure-sensitive, archived, corrected, superseded, withdrawn, deprecated, or retired status.

348.10.2 Classification display may be visible to users, embedded in metadata, recorded in access logs, or maintained in associated records depending on sensitivity and public-safe requirements.

348.10.3 Classification labels shall not be used as ratings, certifications, recognitions, maturity determinations, finance signals, procurement signals, public warnings, or provider-preference labels.

348.11 Access Control.

348.11.1 Dashboards, maps, visualizations, and interactive tools shall implement access controls proportionate to sensitivity, including authentication, authorization, least privilege, role-based or attribute-based access, no-download controls, export controls, watermarking where appropriate, logging where feasible, access review, and revocation.

348.11.2 Access controls shall be heightened for materials involving public authority data, personal information, health-sensitive data, rights-bearing data, cyber-sensitive data, infrastructure-sensitive data, finance-sensitive data, protected knowledge, controlled technology, non-public vulnerabilities, or restricted datasets.

348.11.3 Public access to a dashboard, map, visualization, or tool shall not mean that the underlying data, source records, methods, models, code, or restricted annexes are public or reusable.

348.12 Public-Safe Map Review.

348.12.1 Public-Safe Map Review shall be required before public or external release of maps, geospatial layers, hotspot views, cluster views, regional maps, national dense Nexus core maps, public authority maps, infrastructure maps, community maps, environmental maps, public health maps, biosecurity maps, cyber maps, AI-RAN / O-RAN signal maps, DePIN telemetry maps, DLT-linked maps, digital twin maps, or Earth observation outputs.

348.12.2 Public-Safe Map Review shall assess data rights, lawful authority, source quality, geospatial accuracy, resolution, aggregation, sensitive-location risk, public authority status, community exposure, protected knowledge, cyber sensitivity, infrastructure sensitivity, public warning risk, emergency-command risk, accessibility, and correction path.

348.12.3 Public-Safe Map Review may require redaction, aggregation, coarsening, masking, time delay, removal of sensitive layers, controlled release, no-download access, non-attribution, or denial of release.

348.13 Infrastructure-Sensitive Review.

348.13.1 Infrastructure-Sensitive Review shall be required where dashboards, maps, visualizations, or tools include or imply information about critical infrastructure, telecom systems, AI-RAN / O-RAN systems, energy systems, water systems, food systems, ports, transportation, public works, public safety systems, emergency systems, cyber-physical systems, sensors, digital twins, public health systems, industrial systems, or degraded-mode conditions.

348.13.2 Infrastructure-Sensitive Review shall assess whether publication could expose dependencies, vulnerabilities, locations, configurations, outage patterns, resilience weaknesses, operational capacity, security controls, or targeting information.

348.13.3 Infrastructure-sensitive materials shall be restricted, redacted, delayed, aggregated, or withheld where disclosure may increase harm.

348.14 Cyber-Sensitive Review.

348.14.1 Cyber-Sensitive Review shall be required where dashboards, maps, visualizations, or tools include cyber telemetry, vulnerability information, threat intelligence, incident information, access logs, repository status, dependency alerts, security configuration, exploit-relevant material, prompt-injection examples, data-poisoning examples, or AI security findings.

348.14.2 Cyber-Sensitive Review shall assess exploitability, attacker usefulness, public-safe disclosure, coordinated vulnerability disclosure, public authority implications, infrastructure sensitivity, secrets exposure, and incident response needs.

348.14.3 Cyber-sensitive outputs shall not be publicly released in a manner that enables exploitation, reveals credentials, exposes restricted systems, or creates unsafe operational inference.

348.15 Public Authority Data Review.

348.15.1 Public Authority Data Review shall be required where dashboards, maps, visualizations, or tools include data received from, created with, derived from, referencing, or materially affecting public authorities.

348.15.2 Public Authority Data Review shall assess source authority, permitted use, public records status, confidentiality, publication restrictions, official-capacity risk, procurement sensitivity, public finance sensitivity, public warning risk, emergency-command risk, public-safe status, and correction path.

348.15.3 Public authority data display shall not imply public authority endorsement, adoption, approval, public warning, emergency command, procurement approval, grant approval, public finance approval, sovereign decision, or public-private partnership.

348.16 Community-Protected, Tribal / Indigenous, Local, Territorial, Cultural, Environmental, and Protected Knowledge Review.

348.16.1 Community-Protected, Tribal / Indigenous, Local, Territorial, Cultural, Environmental, and Protected Knowledge Review shall be required where dashboards, maps, visualizations, or tools include or may reveal community-protected information, Indigenous knowledge, local knowledge, territorial knowledge, cultural information, sacred knowledge, ecological knowledge, environmental vulnerability, protected sites, sensitive community locations, or protected knowledge.

348.16.2 Review shall assess permission, consent, non-consent, attribution, non-attribution, protocol compliance, public-safe mapping resolution, AI-use restrictions, extraction risk, retaliation risk, stigmatization risk, commercialization risk, transfer restrictions, grievance pathways, correction, withdrawal, and deletion where lawful.

348.16.3 Such materials shall not be mapped, visualized, geocoded, generalized, translated, embedded, trained on, or externally displayed without lawful authority and safeguards sufficient for the knowledge context.

348.17 Vulnerable Community and Public Safety Review.

348.17.1 Vulnerable Community and Public Safety Review shall be required where dashboards, maps, visualizations, or tools may affect vulnerable populations, youth, health-sensitive groups, displaced persons, low-resource communities, communities facing environmental or infrastructure risk, protected classes, or persons subject to retaliation, profiling, surveillance, exclusion, or harm.

348.17.2 Review shall assess civil rights, accessibility, language access, stigmatization, discriminatory impact, exposure, public safety, public health, misinformation risk, alarm risk, false reassurance risk, and community safeguards.

348.17.3 The Corporation may aggregate, redact, delay, restrict, relabel, withdraw, or refuse visual outputs where public display could harm vulnerable communities or public safety.

348.18 No Dashboard, Map, or Tool as Public Warning, Emergency Command, Public Authority Decision, Certification, Procurement Approval, Recognition, Finance-Readiness, Rating, or Provider Preference.

348.18.1 No dashboard, map, geospatial output, public-safe visualization, interactive tool, indicator, signal, score, color, filter, layer, label, marker, hotspot, cluster, alert-like feature, degraded-mode display, resilience indicator, benchmark view, digital twin view, AI-RAN / O-RAN signal view, DePIN telemetry view, DLT-linked view, cyber view, or public authority learning view shall constitute or be represented as public warning, emergency command, public authority decision, certification, procurement approval, recognition, finance-readiness, insurance-readiness, rating, provider preference, legal compliance approval, investment suitability, public finance approval, guarantee, or execution authority.

348.18.2 Where dashboard, map, or tool outputs may reasonably be misunderstood as any such status, the Corporation shall redesign, relabel, restrict, delay, redact, add limitation language, withdraw, or refuse release.

348.19 Dashboard, Map, Visualization, and Tool Records.

348.19.1 The Corporation shall maintain Dashboard, Map, Visualization, and Tool Records, including dashboard purpose records, map purpose records, geospatial output records, public-safe visualization records, interactive tool records, source disclosure records, update status records, timestamp and version records, confidence and limitation display records, classification display records, access control records, Public-Safe Map Reviews, Infrastructure-Sensitive Reviews, Cyber-Sensitive Reviews, Public Authority Data Reviews, community-protected / Tribal / Indigenous / local / territorial / cultural / environmental / protected knowledge review records, vulnerable community and public safety review records, boundary records, corrections, takedowns, withdrawals, deprecations, retirements, and archive records.

---

Section 349. AI-Generated, AI-Assisted, Automated, Agentic, and Synthetic Content

349.1 AI Content Purpose.

349.1.1 AI Content governance shall ensure that AI-generated, AI-assisted, automated, agentic, and synthetic content used in or for Corporation publications, dashboards, maps, datasets, software, technical baselines, public-safe summaries, evidence packs, method notes, Academy materials, public authority learning materials, digital channels, media materials, and external outputs is accurate, source-grounded, human-reviewed, limitation-aware, safeguards-compliant, public-safe, secure, correctionable, and consistent with the Corporation’s non-executing role.

349.1.2 AI Content governance shall protect against hallucination, bias, discrimination, accessibility failure, unsafe automation, data leakage, privacy breach, protected knowledge exposure, cyber exposure, infrastructure exposure, false public authority implication, finance overclaim, certification overclaim, recognition overclaim, procurement overclaim, provider preference, public warning confusion, emergency command confusion, and unsupported technical truth claims.

349.1.3 AI Content shall not be treated as evidence, technical truth, official institutional position, public-safe publication, public authority communication, finance-facing claim, certification-like claim, recognition-like claim, procurement claim, or controlled vocabulary output unless reviewed and recorded according to this Bylaw.

349.2 AI-Generated Content.

349.2.1 AI-Generated Content means content materially generated by an AI system, including text, summaries, images, code, datasets, synthetic data, translations, captions, classifications, maps, dashboards, model cards, evidence summaries, public-safe summaries, recommendations, labels, or outputs.

349.2.2 AI-Generated Content shall be reviewed for source support, factual accuracy, hallucination, bias, public-safe language, data leakage, copyright issues, protected knowledge exposure, confidentiality, public authority boundary, finance boundary, certification boundary, recognition boundary, procurement boundary, and correction path before external release.

349.2.3 AI-Generated Content shall not be published merely because it is plausible, well written, internally consistent, or produced from a controlled prompt.

349.3 AI-Assisted Content.

349.3.1 AI-Assisted Content means content created by a human with material assistance from an AI system, including drafting, summarization, editing, translation, classification, coding, research support, data transformation, visualization generation, metadata generation, or review support.

349.3.2 AI-Assisted Content remains the responsibility of the approving human reviewer and publication authority.

349.3.3 AI assistance shall not reduce the requirements for source verification, evidence support, limitation disclosure, public-safe review, protected knowledge review, data / AI / cyber / privacy review, or publication approval.

349.4 Automated Content.

349.4.1 Automated Content means content generated by rules, scripts, workflows, dashboards, templates, scheduled jobs, data pipelines, sensors, telemetry systems, validation systems, release systems, or other automation without case-by-case human authorship.

349.4.2 Automated Content shall be governed by approved workflow, source records, method records, versioning, logging where appropriate, error handling, public-safe output controls, access controls, human review gates where material, and correction path.

349.4.3 Automated Content shall not be represented as human judgment, public authority decision, certification, recognition, finance-readiness, procurement approval, public warning, emergency command, or technical truth beyond the workflow’s recorded scope.