ARTICLE XIII. AUTHORITIES

Section 360. Public Authority Boundary Purpose

360.1 Public Authority Boundary Purpose.

360.1.1 Public Authority Boundary governance shall preserve the Corporation’s public-benefit, non-executing, evidence, methods, observability, ontology, public-good R&D, public-good software, open technical baseline, public authority learning, and public-safe publication role when interacting with federal, state, District of Columbia, territorial, Tribal, Indigenous governmental, local, county, municipal, metropolitan, public health, emergency management, public safety, public works, public infrastructure, utility, port, airport, transit, transportation, water, energy, food, telecom, cyber, environmental, housing, education, research, health-system, public finance, budget, treasury, grant, procurement, regulatory, inspector general, legislative, judicial, oversight, and other public-sector actors.

360.1.2 Public Authority Boundary governance shall ensure that public authority engagement with the Corporation is accurately characterized as learning, evidence literacy, technical literacy, observability literacy, public-safe publication support, methods support, controlled-room participation, data contribution, public information exchange, technical review, or other authorized non-executing interface, and not as delegation, endorsement, adoption, funding approval, procurement approval, regulatory approval, public finance approval, public warning, emergency command, sovereign obligation, public-private partnership, or public authority action unless separately and lawfully established by competent public authority record.

360.1.3 Public Authority Boundary governance shall protect public authority trust, public records discipline where applicable, procurement neutrality, public finance neutrality, ethics compliance, confidentiality, privacy, cybersecurity, infrastructure protection, protected knowledge, public-safe communication, role separation, and correctionability.

360.2 Government Interface Purpose.

360.2.1 Government Interface governance shall establish disciplined, lawful, transparent, capacity-classified, and records-based methods for Corporation interaction with public authorities and public officials.

360.2.2 Government Interfaces may include briefings, workshops, public authority learning sessions, controlled rooms, public authority rooms, evidence rooms, data rooms, clean rooms, simulations, tabletop exercises, technical reviews, public-safe dashboard reviews, map reviews, observability discussions, data governance discussions, AI governance discussions, cybersecurity discussions, public-good software demonstrations, open technical baseline discussions, and publication review processes.

360.2.3 Government Interfaces shall be structured so that no public authority participant is misrepresented as approving, adopting, funding, procuring, regulating, endorsing, warning, commanding, or authorizing Corporation outputs unless the relevant public authority has separately and lawfully recorded that status.

360.3 Public Authority Learning Purpose.

360.3.1 Public Authority Learning shall support public-sector understanding of systemic risk evidence, observability, methods, technical baselines, public-good software, data governance, AI governance, cybersecurity, verifiable compute, verifiable intelligence, public-safe dashboards, public-safe maps, controlled vocabulary, correctionability, and Nexus role separation.

360.3.2 Public Authority Learning may provide structured information, explanatory materials, demonstrations, training, evidence literacy, method literacy, technical literacy, and public-safe decision-support literacy, but shall not make decisions for public authorities or substitute for legal, regulatory, procurement, public finance, emergency management, public health, public safety, infrastructure, or operational authority.

360.3.3 Public Authority Learning shall be documented with access class, capacity classification, subject matter, materials used, public authority restrictions, correction path, and limitation language where material.

360.4 Public Authority Evidence Literacy Purpose.

360.4.1 Public Authority Evidence Literacy shall support public-sector understanding of source records, evidence records, provenance, evidence classes, confidence, uncertainty, limitations, source lineage, data quality, evidence gaps, public-safe summaries, proof receipts, challenge pathways, correction pathways, and technical memory.

360.4.2 Evidence literacy support shall not convert evidence records into official findings, public authority determinations, public warnings, emergency commands, procurement specifications, funding approvals, finance approvals, certifications, recognitions, ratings, or regulated conclusions.

360.4.3 Evidence literacy materials shall distinguish evidence, observation, inference, public authority data, community input, model output, dashboard output, map output, proof receipt, source record, and public-safe summary.

360.5 Public Authority Technical Literacy Purpose.

360.5.1 Public Authority Technical Literacy shall support public-sector understanding of technical assets, open technical baselines, schemas, APIs, SDKs, public-good software, reference architectures, interoperability profiles, AI-RAN / O-RAN signal structures, DePIN and DLT telemetry, digital twins, geospatial outputs, cyber telemetry, sensor systems, data pipelines, model records, inference records, compute workload records, controlled rooms, and secure release controls.

360.5.2 Technical literacy support shall be non-executing and shall not constitute engineering approval, system deployment, production readiness, cybersecurity certification, AI compliance approval, public authority adoption, procurement approval, provider qualification, public warning, emergency command, or operational instruction.

360.5.3 Technical literacy materials shall include limitations, unsupported uses, access restrictions, public-safe status, known issues, known limitations, correction path, and role-separation language where material.

360.6 Public-Safe Decision-Support Literacy Purpose.

360.6.1 Public-Safe Decision-Support Literacy shall help public authorities understand how evidence, methods, observability, public-good technical assets, dashboards, maps, digital twins, AI outputs, benchmark results, and technical baselines may inform lawful public authority learning without becoming public authority decisions.

360.6.2 Decision-support literacy shall emphasize that the Corporation’s materials are inputs to learning and understanding, not substitutes for public authority judgment, statutory authority, emergency authority, regulatory process, procurement process, public finance process, official public warning, or professional review.

360.6.3 Materials used for decision-support literacy shall include boundary language, confidence and uncertainty language, access classification, source limitations, and correction pathways proportionate to the context.

360.7 United States All-States-and-Territories Public Authority Boundary Purpose.

360.7.1 The Corporation’s United States all-states-and-territories public authority boundary shall ensure accurate treatment of federal, state, District of Columbia, territorial, Tribal, local, county, municipal, metropolitan, and public-sector interfaces across diverse legal, administrative, public records, procurement, emergency, public health, infrastructure, and privacy contexts.

360.7.2 The Corporation shall not imply that a position, interface, reference, data contribution, learning session, technical review, public-safe dashboard, map, method, baseline, or publication applicable to one state, territory, locality, or public authority applies uniformly to all states, territories, localities, or public authorities.

360.7.3 United States all-states-and-territories communications shall preserve jurisdictional precision, federalism sensitivity, territorial context, Tribal sovereignty, local authority, public records discipline, procurement neutrality, public finance neutrality, public-safe publication, and non-execution.

360.8 North America Public Authority Interface Purpose.

360.8.1 The North America Public Authority Interface shall govern the Corporation’s public-good, non-executing, evidence, methods, observability, public-good software, public authority learning, and public-safe publication interfaces involving the United States, Canada, Mexico, the Caribbean, Arctic contexts, cross-border systems, Indigenous cross-border contexts, and regional resilience concerns.

360.8.2 North America public authority interfaces shall preserve legal separateness, entity separateness, no shared treasury, no agency, no partnership, no joint venture, no treaty claim, no sovereign coordination claim, no public authority delegation, no cross-border execution authority, and no implied control over GCRI Canada, GRF, GRA, consortiums, national companies, Project SPVs, public authorities, providers, sponsors, or enterprise actors.

360.8.3 North America public authority interfaces shall be reviewed for cross-border data, privacy, public authority restrictions, Indigenous data safeguards, protected knowledge, export-control, sanctions, controlled technology, cyber sensitivity, infrastructure sensitivity, and public-safe publication.

360.9 Non-Delegation Purpose.

360.9.1 Non-Delegation shall mean that the Corporation shall not receive, assume, imply, or exercise delegated public authority powers unless a competent public authority lawfully delegates a specific function under an express written instrument, and the Board determines that accepting such function is lawful, mission-compatible, consistent with nonprofit status, and not inconsistent with this Bylaw.

360.9.2 By default, the Corporation shall not act as regulator, procurement authority, grant authority, public finance authority, emergency management authority, public health authority, public safety authority, public works authority, public infrastructure operator, public warning authority, licensing authority, certification authority, inspection authority, enforcement authority, or public decision-maker.

360.9.3 Public authority attendance, learning, consultation, comment, review, data sharing, controlled-room participation, or technical engagement shall not constitute delegation.

360.10 Non-Endorsement Purpose.

360.10.1 Non-Endorsement shall mean that public authority engagement with the Corporation shall not imply that any public authority endorses, approves, adopts, funds, procures, regulates through, relies upon, certifies, recognizes, finances, or officially supports the Corporation, its publications, technical assets, dashboards, maps, datasets, software, methods, evidence packs, baselines, events, programs, partners, sponsors, providers, national companies, Project SPVs, or Nexus outputs unless a competent public authority record expressly supports the statement.

360.10.2 The Corporation shall likewise not endorse a public authority’s policy, procurement, funding decision, regulatory action, public warning, emergency action, public finance action, or operational decision unless separately authorized and consistent with its non-executing public-benefit role.

360.11 Non-Public-Warning Purpose.

360.11.1 Non-Public-Warning shall mean that the Corporation shall not issue official public warnings, hazard alerts, public health alerts, public safety alerts, infrastructure alerts, evacuation notices, emergency notices, cyber alerts on behalf of public authorities, or other official public risk communications.

360.11.2 The Corporation may publish public-safe summaries, corrections, technical explanations, observability outputs, dashboard limitations, map limitations, or evidence materials, but such outputs shall not be framed or designed as public warnings.

360.11.3 Where risk of public-warning confusion exists, the Corporation shall use limitation language, redesign, restricted access, delay, redaction, aggregation, or withdrawal.

360.12 Non-Emergency-Command Purpose.

360.12.1 Non-Emergency-Command shall mean that the Corporation shall not direct emergency response, incident command, public safety operations, evacuation, sheltering, restoration, dispatch, infrastructure operation, public works action, public health action, cyber response, law enforcement action, or public authority command.

360.12.2 Corporation simulations, tabletop exercises, after-action learning, degraded-mode analysis, public-safe maps, dashboards, observability materials, and public authority learning sessions shall be described as learning or evidence support and not as operational command.

360.13 Non-Regulatory Purpose.

360.13.1 Non-Regulatory shall mean that the Corporation shall not issue regulations, official regulatory guidance, safe harbors, enforcement positions, compliance approvals, permits, licenses, regulatory certifications, regulatory interpretations, or public-sector standards with regulatory force.

360.13.2 The Corporation may produce public-good methods, evidence, technical baselines, software, and learning materials that may be informative to regulatory audiences, but shall not present those materials as regulatory requirements or official interpretations.

360.14 Non-Procurement Purpose.

360.14.1 Non-Procurement shall mean that the Corporation shall not approve procurements, qualify vendors, rank bidders, establish preferred-provider lists, recommend purchases, issue procurement specifications, determine public contract eligibility, or create procurement advantages by default.

360.14.2 Technical baselines, evidence packs, dashboards, maps, datasets, software, interoperability profiles, and public-safe summaries shall not be represented as procurement approval or vendor qualification.

360.15 Non-Funding-Approval Purpose.

360.15.1 Non-Funding-Approval shall mean that the Corporation shall not approve grants, award public funds, authorize appropriations, determine eligibility for public funding, approve donor funding for third parties, create grant eligibility, or approve public or private funding outcomes by default.

360.15.2 References to funders, grantors, public finance readers, sponsors, donors, national companies, Project SPVs, capital readers, or public authorities shall not be framed as funding approval or funding commitment.

360.16 Non-Public-Finance-Approval Purpose.

360.16.1 Non-Public-Finance-Approval shall mean that the Corporation shall not approve public finance, tax credits, public guarantees, public credit support, municipal obligations, sovereign obligations, MDB / DFI approvals, public-private partnerships, budget allocations, treasury commitments, public infrastructure finance, or governmental fiscal commitments.

360.16.2 Evidence packs, proof packs, capital-readable records, GRA-facing inputs, Docket inputs, Grid inputs, dashboards, maps, and technical materials may be used only as non-executing, limited, public-safe evidence or learning support, and not as public finance approvals.

360.17 Public Authority Boundary Records.

360.17.1 The Corporation shall maintain Public Authority Boundary Records, including public authority boundary purpose records, government interface records, public authority learning records, evidence literacy records, technical literacy records, public-safe decision-support literacy records, United States all-states-and-territories boundary records, North America public authority interface records, non-delegation records, non-endorsement records, non-public-warning records, non-emergency-command records, non-regulatory records, non-procurement records, non-funding-approval records, non-public-finance-approval records, limitation notices, corrections, clarifications, withdrawals, and archive records.

---

Section 361. Public Authority Definition and Covered Public-Sector Interfaces

361.1 Public Authority Definition.

361.1.1 “Public Authority” means any governmental, quasi-governmental, statutory, regulatory, public-sector, publicly controlled, publicly chartered, publicly funded where material, public infrastructure, public health, public safety, public works, public finance, procurement, oversight, legislative, judicial, administrative, Tribal, Indigenous governmental, territorial, local, county, municipal, metropolitan, utility, port, airport, transit, transportation, water, energy, food, telecom, cyber, environmental, housing, education, research, health-system, or other public-purpose body or official actor whose participation may reasonably create public authority meaning.

361.1.2 Public Authority status shall be interpreted broadly for purposes of boundary control, public-safe publication, capacity classification, records discipline, and non-execution.

361.1.3 Public Authority status shall not mean that the Corporation treats the public authority as endorsing, adopting, approving, funding, procuring, regulating, warning, commanding, financing, guaranteeing, or authorizing any Corporation output unless a competent record expressly supports that status.

361.2 Federal Public Authorities.

361.2.1 Federal Public Authorities include federal departments, agencies, commissions, bureaus, offices, regulators, public health bodies, emergency management bodies, public safety bodies, public works bodies, public finance bodies, grant bodies, procurement bodies, oversight bodies, inspectors general, federally owned or controlled entities, federal laboratories, federal research entities, federal infrastructure entities, and federal officials or employees acting in any public-sector capacity.

361.2.2 Federal interface records shall distinguish official capacity, observer capacity, regulator-listening capacity, public finance reader capacity, technical expert capacity, public information source capacity, personal capacity, and other relevant roles.

361.3 State Public Authorities.

361.3.1 State Public Authorities include state executive agencies, departments, commissions, regulators, public health agencies, emergency management agencies, public safety bodies, public works bodies, public utility commissions, public finance authorities, grant agencies, procurement bodies, legislatures, courts, offices, universities where acting as public institutions, laboratories, public infrastructure entities, and state officials or employees acting in public-sector capacity.

361.3.2 State interfaces shall be jurisdiction-specific and shall not be generalized across states without supporting records.

361.4 District of Columbia Public Authorities.

361.4.1 District of Columbia Public Authorities include District agencies, offices, councils, public health bodies, emergency management bodies, public safety bodies, public works bodies, public infrastructure bodies, public finance bodies, grant bodies, procurement bodies, regulators, public institutions, and District officials or employees acting in public-sector capacity.

361.4.2 District interfaces shall be reviewed for District-specific law, public records, public authority status, procurement, public finance, emergency, public health, infrastructure, and public-safe communication issues.

361.5 Territorial Public Authorities.

361.5.1 Territorial Public Authorities include agencies, offices, legislatures, courts, public corporations, public utilities, public finance bodies, procurement bodies, emergency management bodies, public health bodies, public safety bodies, public works bodies, infrastructure bodies, port bodies, and officials or employees of United States territories and other relevant territorial contexts where the Corporation lawfully interfaces.

361.5.2 Territorial interfaces shall account for territorial law, federal-territorial relationships, island and remote infrastructure conditions, disaster resilience, public health, telecom, water, energy, food, ports, language access, accessibility, and community safeguards.

361.6 Tribal and Indigenous Governments Where Lawfully and Respectfully Engaged.

361.6.1 Tribal and Indigenous Governments include federally recognized Tribes, state-recognized Tribes where applicable, Indigenous governmental authorities, councils, traditional authorities where applicable, and other Indigenous governance bodies engaged lawfully and respectfully.

361.6.2 Engagement with Tribal and Indigenous Governments shall be sovereignty-aware, protocol-aware, permission-based, safeguards-reviewed, and respectful of data governance, knowledge governance, attribution, non-attribution, withdrawal, correction, publication, mapping, AI-use, and transfer restrictions.

361.6.3 Nothing in Corporation records or publications shall imply waiver of sovereignty, public authority delegation, endorsement, adoption, unrestricted knowledge use, public-safe mapping permission, or data transfer permission absent competent record.

361.7 Local Public Authorities.

361.7.1 Local Public Authorities include local agencies, departments, boards, commissions, districts, councils, public health bodies, emergency bodies, public safety bodies, public works bodies, utilities, public institutions, and local officials or employees acting in public-sector capacity.

361.7.2 Local interface records shall identify locality, role, capacity, authority, access restrictions, public records considerations, and public-safe publication constraints where material.

361.8 County Authorities.

361.8.1 County Authorities include county governments, county agencies, county public health authorities, county emergency management bodies, county public safety bodies, county public works bodies, county infrastructure bodies, county procurement bodies, county finance bodies, and county officials or employees.

361.8.2 County interfaces shall be reviewed for public health, public safety, emergency management, public works, land use, infrastructure, public records, procurement, and community exposure implications where material.

361.9 Municipal Authorities.

361.9.1 Municipal Authorities include city, town, village, borough, parish, township, municipal corporation, municipal agency, municipal utility, municipal public health, municipal public safety, municipal public works, municipal infrastructure, municipal procurement, municipal finance, and municipal officials or employees.

361.9.2 Municipal references shall be precise and shall not imply approval by a broader state, county, metropolitan region, or public authority unless supported by record.

361.10 Metropolitan Authorities.

361.10.1 Metropolitan Authorities include regional planning bodies, metropolitan planning organizations, transit authorities, regional infrastructure bodies, regional public health or emergency bodies, regional water or energy bodies, regional port or transportation bodies, and similar multi-jurisdictional public-sector entities.

361.10.2 Metropolitan interfaces shall be reviewed for multi-jurisdictional authority, public records, procurement, infrastructure sensitivity, data-sharing, public-safe mapping, and intergovernmental implications.

361.11 Public Health Authorities.

361.11.1 Public Health Authorities include public health departments, health agencies, health boards, epidemiological units, health surveillance bodies, health emergency bodies, public hospitals where acting in public authority capacity, and public health officials or employees.

361.11.2 Public health interfaces shall be reviewed for health-sensitive data, privacy, public health authority status, public warning risk, emergency command risk, vulnerable populations, biosecurity, civil rights, accessibility, and public-safe publication.

361.12 Emergency Management Authorities.

361.12.1 Emergency Management Authorities include emergency management agencies, emergency operations centers, civil defense bodies, disaster response bodies, incident management bodies, resilience offices, emergency communications bodies, and emergency management officials or employees.

361.12.2 Emergency management interfaces shall be reviewed to prevent public warning confusion, emergency command confusion, operational reliance, infrastructure exposure, public safety risk, and disclosure of sensitive incident information.

361.13 Public Safety Authorities.

361.13.1 Public Safety Authorities include law enforcement, fire, rescue, emergency medical, public safety communications, homeland security, emergency dispatch, corrections, public safety agencies, and public safety officials or employees.

361.13.2 Public safety interfaces shall be reviewed for operational sensitivity, civil rights, privacy, public-safe publication, vulnerable populations, emergency command, public warning, cyber sensitivity, and records restrictions.

361.14 Public Works Authorities.

361.14.1 Public Works Authorities include public works departments, roads, bridges, water, wastewater, sanitation, drainage, facilities, buildings, public lands, maintenance, engineering, and related public-sector bodies.

361.14.2 Public works interfaces shall be reviewed for infrastructure sensitivity, geospatial exposure, procurement sensitivity, operational reliance, and public-safe mapping.

361.15 Public Infrastructure Operators.

361.15.1 Public Infrastructure Operators include public, publicly controlled, publicly regulated, or public-purpose operators of critical or important infrastructure, including telecom, AI-RAN / O-RAN, energy, water, wastewater, food systems, transportation, ports, airports, transit, public health infrastructure, emergency systems, cyber systems, digital public infrastructure, sensors, and public works systems.

361.15.2 Public Infrastructure Operator status shall not imply that the Corporation operates, directs, audits, certifies, rates, ranks, supervises, controls, funds, procures, or guarantees infrastructure.

361.16 Utilities and Publicly Regulated Infrastructure Operators.

361.16.1 Utilities and Publicly Regulated Infrastructure Operators include investor-owned utilities, municipal utilities, cooperatives, public utility districts, regulated telecom providers, water utilities, energy providers, transport operators, port operators, airport operators, and other operators subject to public regulation or public-purpose duties.

361.16.2 Such interfaces shall be reviewed for public-private status, regulatory sensitivity, procurement sensitivity, confidential infrastructure information, cyber sensitivity, public authority meaning, and provider-neutrality risk.

361.17 Ports, Airports, Transit, Transportation, Water, Energy, Food, Telecom, Cyber, Environmental, Housing, Education, Research, and Health-System Public Interfaces.

361.17.1 Public interfaces in ports, airports, transit, transportation, water, energy, food, telecom, cyber, environmental, housing, education, research, and health systems shall be governed according to sector-specific sensitivity, public authority role, public records, privacy, cybersecurity, infrastructure protection, procurement, public finance, civil rights, accessibility, protected knowledge, and public-safe publication.

361.17.2 Sector interface records shall distinguish learning support, technical support, evidence support, public information exchange, data contribution, infrastructure operator participation, public authority participation, and operational authority.

361.18 Public Finance, Budget, Treasury, Grant, Procurement, Regulatory, Inspector General, Legislative, Judicial, and Oversight Interfaces.

361.18.1 Public finance, budget, treasury, grant, procurement, regulatory, inspector general, legislative, judicial, and oversight interfaces shall be governed with heightened boundary discipline due to risk of finance approval, funding approval, procurement implication, regulatory implication, investigation implication, legislative implication, judicial implication, public authority endorsement, or official action.

361.18.2 Corporation materials provided to such actors shall include non-reliance, non-procurement, non-finance, non-regulatory, non-certification, non-recognition, and non-public-authority-action language where appropriate.

361.19 Public Authority Interface Records.

361.19.1 The Corporation shall maintain Public Authority Interface Records, including public authority definition records, federal public authority records, state public authority records, District of Columbia public authority records, territorial public authority records, Tribal and Indigenous government engagement records, local public authority records, county authority records, municipal authority records, metropolitan authority records, public health authority records, emergency management authority records, public safety authority records, public works authority records, public infrastructure operator records, utility and publicly regulated infrastructure operator records, sector public interface records, public finance / budget / treasury / grant / procurement / regulatory / inspector general / legislative / judicial / oversight interface records, capacity classifications, limitation notices, corrections, withdrawals, and archive records.

---

Section 362. Public Authority Participation Principles

362.1 Participation by Public Authorities.

362.1.1 Participation by Public Authorities in Corporation activities shall be structured, recorded, capacity-classified, and public-safe.

362.1.2 Public Authority participation may include attendance, observation, speaking, technical discussion, learning, data contribution, public information sharing, public authority room participation, controlled-room participation, simulation, tabletop exercise, after-action learning, dashboard review, map review, method review, evidence literacy, technical literacy, public-safe decision-support literacy, or other lawful engagement.

362.1.3 Participation shall not imply endorsement, adoption, funding approval, procurement approval, regulatory approval, public finance approval, public warning, emergency command, official decision, sovereign obligation, public-private partnership, or delegation unless a competent public authority record expressly provides otherwise.

362.2 Participation by Public Officials.

362.2.1 Participation by Public Officials shall be governed according to capacity, authority, ethics rules, public records considerations, public-safe publication, official title use, and permission to reference participation.

362.2.2 A Public Official’s participation shall be described only within the role actually performed, including official participant, observer, speaker, technical expert, policy discussant, regulator-listening participant, public finance reader, emergency-management participant, public infrastructure operator participant, academic representative, personal-capacity participant, reviewer, data provider, or other recorded capacity.

362.2.3 Public Official participation shall not be used for promotional overclaim, public authority endorsement implication, finance implication, procurement implication, recognition implication, certification implication, or public warning implication.

362.3 Participation by Public Employees.

362.3.1 Participation by Public Employees shall be governed by the same boundary discipline applicable to Public Officials, with attention to whether the employee participates within official duties, delegated duties, personal capacity, academic capacity, technical expert capacity, observer capacity, or other capacity.

362.3.2 Public Employee attendance, comment, question, data contribution, review, or learning participation shall not bind the public authority unless competent public authority record supports such authority.

362.4 Participation by Public Infrastructure Operators.

362.4.1 Public Infrastructure Operator participation shall be reviewed for operational sensitivity, cyber sensitivity, infrastructure sensitivity, public-safe mapping, confidential infrastructure information, regulated-provider status, public authority status, and provider-neutrality risk.

362.4.2 Participation by a Public Infrastructure Operator shall not imply that the Corporation operates, audits, certifies, rates, ranks, commands, supervises, controls, funds, procures, approves, or guarantees the infrastructure operator or its systems.

362.5 Participation by Public Finance Readers.

362.5.1 Public Finance Reader participation shall mean review, listening, learning, or structured receipt of materials by public finance, budget, treasury, development finance, MDB / DFI, grant, guarantee, or fiscal actors in a non-approval capacity unless otherwise recorded.

362.5.2 Public Finance Reader participation shall not imply public finance approval, grant approval, tax credit approval, appropriation, public guarantee, sovereign obligation, municipal obligation, MDB / DFI approval, credit support, investment approval, rating, finance-readiness, or capital commitment.

362.6 Participation by Regulators in Listening Capacity.

362.6.1 Regulators may participate in listening capacity for learning, technical literacy, evidence literacy, observability literacy, or public-safe decision-support literacy.

362.6.2 Regulator-listening participation shall not imply regulatory approval, enforcement position, safe harbor, compliance approval, legal interpretation, official guidance, or adoption of Corporation materials.

362.6.3 Materials referencing regulator-listening participation shall use precise capacity language and shall not use regulatory titles in a misleading manner.

362.7 Participation by Emergency Management Personnel.

362.7.1 Emergency Management Personnel may participate in learning sessions, simulations, tabletop exercises, evidence literacy, public-safe dashboard review, map review, degraded-mode analysis, observability review, or after-action learning.

362.7.2 Such participation shall not imply public warning, emergency command, incident command, emergency declaration, evacuation instruction, operational direction, public safety order, public health order, or official response action.

362.8 Participation by Public Health Personnel.

362.8.1 Public Health Personnel may participate in public health evidence literacy, data governance, public-safe publication, biosecurity learning, health-sensitive data review, dashboard review, map review, observability methods, and community safeguards discussions.

362.8.2 Such participation shall not imply public health order, official public health guidance, public warning, clinical advice, health certification, regulatory approval, or emergency command.

362.9 Participation by Public Safety Personnel.

362.9.1 Public Safety Personnel may participate in learning, public-safe evidence review, simulations, after-action learning, cyber-physical infrastructure discussions, and public safety literacy activities.

362.9.2 Such participation shall not imply law enforcement action, emergency dispatch, public safety order, incident command, operational direction, official warning, certification, procurement approval, or public authority adoption.

362.10 Participation by Tribal / Indigenous Government Representatives.

362.10.1 Participation by Tribal / Indigenous Government Representatives shall be lawful, respectful, sovereignty-aware, protocol-aware, permission-based, safeguards-reviewed, and capacity-classified.

362.10.2 Such participation shall not imply endorsement, adoption, waiver of sovereignty, data transfer permission, knowledge-use permission, public-safe mapping permission, public authority delegation, funding approval, procurement approval, public warning, emergency command, recognition, or finance-readiness unless competent record expressly supports the limited statement.

362.10.3 Participation records shall respect attribution, non-attribution, confidentiality, protected knowledge, withdrawal, restriction, and correction requirements.

362.11 Participation by Public Universities and Public Laboratories.

362.11.1 Participation by public universities and public laboratories shall be classified according to whether the institution, laboratory, researcher, faculty member, staff member, student, fellow, or technical expert participates in official institutional, academic, research, personal, public authority, or technical expert capacity.

362.11.2 Such participation shall not imply institutional endorsement, public authority adoption, peer review, academic validation, certification, procurement approval, finance-readiness, recognition, rating, or guarantee unless competent record supports the statement.

362.12 Participation in Personal Capacity.

362.12.1 Personal-capacity participation shall be identified where a public official, public employee, public university employee, laboratory employee, regulator, public finance actor, infrastructure operator employee, or other public-sector-affiliated person participates outside official authority.

362.12.2 Personal-capacity participation shall not be paired with titles, agency logos, official insignia, or official descriptions in a manner that implies official participation.

362.12.3 Personal-capacity participants shall not disclose restricted public authority information, confidential information, protected knowledge, non-public data, or privileged materials through Corporation activities.

362.13 Participation in Official Capacity Only With Record.

362.13.1 Participation shall be described as official only where a competent record supports that the participant had authority to participate officially and where the scope of that official participation is recorded.

362.13.2 Official-capacity participation records shall identify public authority, participant, title, authority, scope, date, activity, permitted public reference, public records status, confidentiality, and limitations.

362.13.3 Official-capacity participation shall not be extrapolated beyond the recorded scope.

362.14 No Participation as Endorsement.

362.14.1 Participation by a public authority, public official, public employee, public infrastructure operator, public finance reader, regulator, emergency management personnel, public health personnel, public safety personnel, Tribal / Indigenous representative, public university, public laboratory, or other public-sector actor shall not constitute endorsement of the Corporation, any publication, technical asset, event, sponsor, provider, partner, project, national company, Project SPV, Nexus structure, GRF activity, GRA activity, or public-good output.

362.15 No Participation as Adoption.

362.15.1 Participation shall not constitute adoption of a Corporation method, evidence record, dashboard, map, dataset, software release, open technical baseline, schema, API, SDK, reference architecture, public-safe summary, public authority learning material, publication, or technical asset by a public authority.

362.16 No Participation as Funding Approval.

362.16.1 Participation shall not constitute approval of funding, grants, appropriations, tax credits, sponsor support, donor support, public finance, public guarantee, public credit support, or any financial commitment by any public authority or public-sector actor.

362.17 No Participation as Procurement Approval.

362.17.1 Participation shall not constitute procurement approval, procurement eligibility, vendor qualification, preferred-provider status, purchasing recommendation, public contract support, grant procurement support, or public-private partnership approval.

362.18 No Participation as Regulatory Approval.

362.18.1 Participation shall not constitute regulatory approval, official guidance, safe harbor, enforcement position, legal interpretation, compliance approval, or agency determination.

362.19 No Participation as Public Warning or Emergency Command.

362.19.1 Participation shall not constitute public warning, emergency command, incident command, operational control, public health order, public safety order, infrastructure directive, evacuation instruction, sheltering instruction, cyber response directive, or emergency-management action.

362.20 Participation Records.

362.20.1 The Corporation shall maintain Participation Records, including public authority participation records, public official participation records, public employee participation records, public infrastructure operator participation records, public finance reader participation records, regulator-listening participation records, emergency management personnel participation records, public health personnel participation records, public safety personnel participation records, Tribal / Indigenous government representative participation records, public university and public laboratory participation records, personal-capacity participation records, official-capacity participation records, no-endorsement records, no-adoption records, no-funding-approval records, no-procurement-approval records, no-regulatory-approval records, no-public-warning or emergency-command records, capacity classifications, permissions, corrections, clarifications, withdrawals, and archive records.

---

Section 363. Capacity Classification System

363.1 Capacity Classification Purpose.

363.1.1 The Capacity Classification System shall classify the role in which a public authority, public official, public employee, public infrastructure operator, public finance actor, regulator, emergency management actor, public health actor, public safety actor, public works actor, university actor, laboratory actor, Tribal / Indigenous government representative, host authority, reviewer, data provider, simulation participant, or other public-sector-affiliated participant engages with the Corporation.

363.1.2 Capacity Classification shall prevent role inflation, official-status ambiguity, public authority overclaim, public finance overclaim, procurement overclaim, regulatory overclaim, public warning confusion, emergency command confusion, endorsement implication, adoption implication, and public-safe publication defects.

363.1.3 Capacity Classification shall be recorded before or promptly after material public authority engagement and shall be used in publications, attendance references, quotes, event materials, controlled-room records, dashboard review records, map review records, public-safe summaries, and public authority learning materials where material.

363.2 Official Participant.

363.2.1 An Official Participant is a person participating on behalf of a public authority with recorded authority to participate officially in a defined activity.

363.2.2 Official Participant classification shall identify the public authority, participant, title, authority, scope, date, permitted references, confidentiality, public records implications, and limitations.

363.2.3 Official Participant status shall not by itself imply endorsement, adoption, funding approval, procurement approval, regulatory approval, public finance approval, public warning, emergency command, or binding public authority decision beyond the recorded scope.

363.3 Institutional Representative.

363.3.1 An Institutional Representative is a person participating on behalf of a public-sector institution, public university, public laboratory, public infrastructure entity, public authority program, or other public-sector body for institutional learning, discussion, review, or representation within a defined scope.

363.3.2 Institutional Representative status shall identify whether the person may speak for the institution, receive materials for the institution, provide institutional comments, or only participate in institutional learning.

363.3.3 Institutional Representative status shall not imply approval, adoption, certification, procurement support, finance support, regulatory approval, or official decision absent competent record.

363.4 Delegated Representative.

363.4.1 A Delegated Representative is a person with recorded delegation from a public authority or public-sector institution to perform a defined role in a Corporation interface.

363.4.2 Delegation shall be documented by competent record identifying delegating authority, delegated person, scope, limitations, duration, permitted statements, and whether public reference is permitted.

363.4.3 Delegated Representative status shall be interpreted narrowly and shall not be expanded by implication.

363.5 Observer.

363.5.1 An Observer is a person or public authority participant who attends, views, listens, or receives information without adopting, approving, endorsing, deciding, directing, funding, procuring, regulating, warning, commanding, or committing.

363.5.2 Observer status may be used for public authorities, regulators, public finance actors, public infrastructure operators, universities, laboratories, public officials, public employees, or other public-sector actors.

363.5.3 Observer status shall be described as non-decisional and non-endorsement where public reference is made.

363.6 Speaker.

363.6.1 A Speaker is a person who presents remarks, comments, technical information, policy context, institutional perspective, or public information in a Corporation event or publication context.

363.6.2 Speaker status shall be classified further as official, institutional, technical expert, academic, personal capacity, or other capacity where material.

363.6.3 Speaker status shall not imply that the speaker or speaker’s institution approves the event, publication, Corporation, sponsors, providers, outcomes, or technical assets.

363.7 Technical Expert.

363.7.1 A Technical Expert is a person participating because of subject-matter expertise in evidence, methods, data, AI, cybersecurity, infrastructure, public health, emergency management, telecom, AI-RAN / O-RAN, DePIN, DLT, digital twins, geospatial systems, energy, water, food, biosecurity, climate, nature, public-good software, technical baselines, or other relevant domains.

363.7.2 Technical Expert status shall not imply institutional approval, public authority approval, certification, compliance approval, procurement approval, finance-readiness, recognition, or official determination.

363.8 Policy Discussant.

363.8.1 A Policy Discussant is a person participating in discussion of policy context, governance needs, institutional design, public authority learning, public-safe publication, risk governance, safeguards, or public-benefit implications without issuing official policy or regulatory decision.

363.8.2 Policy Discussant status shall not imply regulatory approval, public authority adoption, public policy endorsement, legislative support, procurement support, or official guidance.

363.9 Regulator-Listening Participant.

363.9.1 A Regulator-Listening Participant is a regulator, regulatory staff member, or regulatory-adjacent public authority participant who receives information, observes, listens, asks questions, or participates in learning without issuing regulatory approval, official guidance, enforcement position, safe harbor, compliance interpretation, or regulatory adoption.

363.9.2 Regulator-Listening Participant status shall be clearly stated where public reference is made and shall not be used to imply regulatory endorsement.

363.10 Public Finance Reader.

363.10.1 A Public Finance Reader is a public finance, budget, treasury, grant, MDB / DFI, development finance, guarantee, tax credit, appropriation, or fiscal actor who receives or reviews materials in a non-approval, non-commitment, non-investment, non-rating, non-guarantee capacity unless separately recorded.

363.10.2 Public Finance Reader status shall not imply public finance approval, funding approval, tax credit approval, appropriation, MDB / DFI approval, sovereign obligation, municipal obligation, public guarantee, public credit support, finance-readiness, rating, or capital commitment.

363.11 Public Infrastructure Operator Participant.

363.11.1 A Public Infrastructure Operator Participant is a public, publicly controlled, publicly regulated, or public-purpose infrastructure actor participating in learning, technical review, observability discussion, public-safe mapping review, resilience discussion, simulation, or controlled-room process.

363.11.2 Such status shall not imply that the Corporation operates, supervises, certifies, rates, ranks, audits, controls, commands, funds, procures, or guarantees the infrastructure or operator.

363.12 Emergency-Management Participant.

363.12.1 An Emergency-Management Participant is a public authority or person with emergency management responsibilities participating in learning, simulation, tabletop, after-action review, observability discussion, dashboard review, map review, or public-safe evidence discussion.

363.12.2 Emergency-Management Participant status shall not imply emergency command, public warning, incident command, emergency declaration, evacuation instruction, operational control, public safety order, or public health order.

363.13 Public Health Participant.

363.13.1 A Public Health Participant is a public health authority, official, employee, researcher, public health system representative, or health-adjacent public-sector actor participating in public health learning, evidence literacy, data governance, biosecurity discussion, public-safe publication review, dashboard review, map review, or safeguards review.

363.13.2 Public Health Participant status shall not imply public health order, clinical advice, public warning, emergency command, official public health guidance, certification, or regulatory approval.

363.14 Public Safety Participant.

363.14.1 A Public Safety Participant is a law enforcement, fire, rescue, emergency medical, dispatch, public safety communications, homeland security, or public safety actor participating in learning, technical review, simulation, public-safe evidence discussion, or infrastructure discussion.

363.14.2 Public Safety Participant status shall not imply law enforcement action, public safety order, emergency command, operational control, dispatch, official warning, certification, or public authority adoption.

363.15 Public Works Participant.

363.15.1 A Public Works Participant is a public works, roads, bridges, water, wastewater, sanitation, drainage, facilities, public lands, engineering, maintenance, or infrastructure actor participating in learning, technical discussion, evidence review, map review, dashboard review, or simulation.

363.15.2 Public Works Participant status shall not imply infrastructure operation by the Corporation, public works direction, engineering certification, procurement approval, public authority adoption, emergency command, or operational instruction.

363.16 Academic Representative.

363.16.1 An Academic Representative is a person participating on behalf of, or associated with, a public university, public college, public research institute, public laboratory, or academic program.

363.16.2 Academic Representative status shall distinguish institutional representative, researcher, faculty member, student, fellow, lab member, technical expert, personal-capacity participant, or official public institution representative.

363.16.3 Academic Representative status shall not imply peer review, academic validation, institutional endorsement, accreditation, certification, public authority adoption, finance-readiness, procurement approval, recognition, or rating unless competent record supports the statement.

363.17 Personal-Capacity Participant.

363.17.1 A Personal-Capacity Participant is a person affiliated with a public authority or public-sector body who participates outside official authority and does not bind or represent the public authority.

363.17.2 Personal-capacity status shall be clearly recorded where material and shall not be paired with official title, seal, logo, agency name, or public authority reference in a manner that creates official implication.

363.18 Non-Attributable Participant.

363.18.1 A Non-Attributable Participant is a participant whose name, title, public authority affiliation, institution, community affiliation, Tribal / Indigenous affiliation, or contribution may not be publicly attributed due to confidentiality, public authority restriction, protected knowledge, privacy, security, community safeguards, retaliation risk, or agreed non-attribution.

363.18.2 Non-attribution shall be respected in publications, event materials, records released externally, dashboards, maps, media materials, and public-safe summaries.

363.19 Controlled-Room Participant.

363.19.1 A Controlled-Room Participant is a person authorized to access a controlled room, clean room, data room, evidence room, public authority room, no-download room, or other access-controlled environment.

363.19.2 Controlled-Room Participant status shall identify room type, access class, permitted uses, prohibited uses, confidentiality, AI-use restrictions, download restrictions, output review, logging where applicable, closeout, and correction path.

363.19.3 Controlled-Room Participant status shall not imply endorsement, adoption, certification, recognition, finance-readiness, procurement approval, public authority decision, public warning, emergency command, or provider preference.

363.20 Data Provider.

363.20.1 A Data Provider is a public authority, public-sector actor, public infrastructure operator, university, laboratory, community, Tribal / Indigenous body, provider, sponsor, or other participant that provides data, public information, restricted information, source materials, telemetry, records, or other inputs.

363.20.2 Data Provider status shall identify authority, data rights, permitted uses, prohibited uses, attribution, non-attribution, publication status, AI-use restrictions, retention, deletion, confidentiality, public-safe status, and correction path.

363.20.3 Data Provider status shall not imply endorsement of the Corporation’s analysis, methods, dashboard, map, publication, evidence pack, technical baseline, finance-facing input, recognition-facing input, certification-like output, public warning, or emergency command.

363.21 Reviewer.

363.21.1 A Reviewer is a person who reviews materials, data, methods, evidence, dashboards, maps, public authority references, technical assets, publications, controlled-room outputs, or public-safe summaries.

363.21.2 Reviewer status shall identify whether review is factual, technical, legal, public authority, public-safe, data, AI, cyber, privacy, safeguards, protected knowledge, community, Tribal / Indigenous, finance-boundary, certification-boundary, recognition-boundary, procurement-boundary, or editorial.

363.21.3 Reviewer status shall not imply approval unless the reviewer is authorized to approve and the approval is recorded.

363.22 Simulation, Tabletop, Exercise, or After-Action Participant.

363.22.1 A Simulation, Tabletop, Exercise, or After-Action Participant is a person participating in a non-operational learning, scenario, model, test, after-action, or exercise environment.

363.22.2 Such participation shall not imply real-world incident response, public warning, emergency command, operational readiness, public authority adoption, procurement approval, certification, finance-readiness, recognition, or guarantee.

363.22.3 Simulation outputs shall be labeled as simulation, scenario, exercise, or after-action learning outputs and shall not be presented as live operational findings unless separately supported by record.

363.23 Host Authority.

363.23.1 A Host Authority is a public authority or public-sector entity that hosts, convenes, provides venue, provides access, supports logistics, permits use of facilities, or supports a Corporation interface in a defined capacity.

363.23.2 Host Authority status shall not imply endorsement, adoption, funding approval, procurement approval, public finance approval, regulatory approval, public warning, emergency command, public-private partnership, sovereign obligation, or approval of outcomes.

363.23.3 Host Authority references shall be reviewed for logo use, venue naming, public authority name use, public-safe meaning, and public records implications.

363.24 Capacity Classification Records.

363.24.1 The Corporation shall maintain Capacity Classification Records, including capacity classification purpose records, Official Participant records, Institutional Representative records, Delegated Representative records, Observer records, Speaker records, Technical Expert records, Policy Discussant records, Regulator-Listening Participant records, Public Finance Reader records, Public Infrastructure Operator Participant records, Emergency-Management Participant records, Public Health Participant records, Public Safety Participant records, Public Works Participant records, Academic Representative records, Personal-Capacity Participant records, Non-Attributable Participant records, Controlled-Room Participant records, Data Provider records, Reviewer records, Simulation / Tabletop / Exercise / After-Action Participant records, Host Authority records, permissions, limitations, corrections, clarifications, withdrawals, and archive records.

Section 364. Official Capacity Records

364.1 Official Capacity Record Requirement.

364.1.1 The Corporation shall maintain Official Capacity Records where any public authority, public official, public employee, public infrastructure operator, public finance actor, regulator, emergency-management actor, public health actor, public safety actor, public works actor, public university actor, public laboratory actor, Tribal / Indigenous government representative, or other public-sector-affiliated person is described, treated, referenced, or relied upon as participating in an official, institutional, delegated, authorized, or public-sector capacity.

364.1.2 Official Capacity Records shall prevent official-status ambiguity, public authority overclaim, endorsement implication, adoption implication, funding implication, procurement implication, public finance implication, regulatory implication, public warning confusion, emergency command confusion, and unauthorized public reference.

364.1.3 Official Capacity Records shall be created or confirmed before public reference where feasible, and in all cases before publication of any material statement that could reasonably be understood as representing official participation, approval, statement, authority, data contribution, quote, endorsement, adoption, or decision.

364.2 Written Authority Where Available.

364.2.1 Where available, official capacity shall be supported by written authority from the competent public authority, including formal letter, signed authorization, memorandum, contract, public authority notice, meeting authorization, delegated authority instrument, official email, approved agenda, public authority record, or other competent written evidence.

364.2.2 Written authority shall identify the public authority, participant, title, role, scope, permitted participation, permitted attribution, limits, duration, confidentiality, publication permissions, and any public records or legal review conditions.

364.2.3 A written authority shall be interpreted narrowly and shall not be expanded by implication to unrelated publications, events, datasets, dashboards, maps, software releases, technical baselines, public authority learning materials, finance-facing materials, procurement-facing materials, or media statements.

364.3 Email or Institutional Confirmation Where Appropriate.

364.3.1 Email or institutional confirmation may support official capacity where formal written authorization is not required by the public authority and where the confirmation is from an authorized public authority account, official representative, or other reliable institutional source.

364.3.2 Email or institutional confirmation shall identify the participant, public authority, capacity, activity, scope, permitted public description, attribution permission, quote permission where applicable, name or logo use permission where applicable, data contribution permission where applicable, and any limitations.

364.3.3 Informal correspondence, verbal statements, calendar invitations, copied emails, meeting attendance, business cards, public titles, or introductions shall not by themselves establish official capacity where official status is material.

364.4 Scope of Authority.

364.4.1 Official Capacity Records shall define the scope of authority with precision, including whether the person is authorized to attend, observe, speak, provide public information, provide non-public data, review materials, approve factual references, approve quotes, approve name use, approve logo use, participate in controlled rooms, participate in simulations, receive confidential materials, provide public authority comments, or bind the public authority.

364.4.2 Scope shall be limited by activity, date, subject matter, publication class, access class, event, dataset, dashboard, map, technical asset, public authority learning material, controlled room, or other defined context.

364.4.3 No scope of authority shall be presumed to include endorsement, adoption, funding approval, procurement approval, regulatory approval, public finance approval, public warning, emergency command, sovereign obligation, or public-private partnership unless expressly stated by competent public authority record.

364.5 Limits of Authority.

364.5.1 Official Capacity Records shall identify limits of authority, including matters the participant may not approve, statements the participant may not make, materials the participant may not authorize, public references the participant may not approve, data the participant may not provide, confidential matters the participant may not disclose, and uses the Corporation may not make.

364.5.2 Limits may include no endorsement, no adoption, no procurement approval, no funding approval, no public finance approval, no regulatory approval, no public warning, no emergency command, no official guidance, no public-private partnership, no sovereign obligation, no data transfer beyond purpose, no AI training, no publication, no attribution, no logo use, no quote use, or no external circulation.

364.5.3 Where limits are unclear, the Corporation shall apply the most restrictive reasonable interpretation until clarification is obtained.

364.6 Attribution Permission.

364.6.1 Attribution Permission shall identify whether the public authority, participant, office, title, agency, department, program, or institution may be named publicly or externally in connection with an activity, publication, event, dataset, dashboard, map, technical asset, or learning material.

364.6.2 Attribution Permission shall specify whether attribution may include name, title, public authority, role, quote, photograph, logo, agenda listing, participant list, contribution description, data source description, or controlled-room reference.

364.6.3 Absence of express attribution permission shall require non-attribution, anonymization, aggregation, generic description, or omission where public-safe interpretation or confidentiality requires.

364.7 Approved Public Language.

364.7.1 Where a public authority or public official is referenced externally, the Corporation shall use Approved Public Language where required or where public authority meaning may be sensitive.

364.7.2 Approved Public Language may define the precise terms permitted, such as “attended in an observer capacity,” “participated in a learning session,” “provided public information,” “served as a technical reviewer,” “joined in personal capacity,” “participated as a regulator-listening participant,” “reviewed materials in a non-approval capacity,” or other capacity-classified wording.

364.7.3 Approved Public Language shall not be edited, shortened, translated, excerpted, placed in promotional context, paired with logos, or visually framed in a manner that changes its meaning.

364.8 Logo and Name Use Permission.

364.8.1 Public authority logo, seal, insignia, agency mark, official emblem, program mark, office mark, or official name use shall require express permission where not clearly authorized by law, public authority policy, or public record.

364.8.2 Logo and name use permission shall specify the exact logo or name, context, duration, placement, size, co-branding conditions, disclaimers, permitted channels, and any prohibition on implying endorsement or partnership.

364.8.3 Public authority logo or name use shall not be used where it creates risk of endorsement, adoption, procurement approval, funding approval, public finance approval, regulatory approval, public warning, emergency command, public-private partnership, or official sponsorship unless that status is expressly and lawfully authorized.

364.9 Quote Permission.

364.9.1 Public authority quotes shall require permission from the speaker and, where the speaker acts or is presented in official capacity, permission or confirmation from the relevant public authority where required.

364.9.2 Quote Permission shall identify the exact quotation, attribution, title, context, publication channel, permitted edits, translation, duration, and whether the quote may be used in promotional, public-safe, technical, event, media, or web materials.

364.9.3 Quotes shall not be edited, excerpted, captioned, translated, visually emphasized, or placed near claims that create broader endorsement, adoption, approval, funding, procurement, public finance, regulatory, public warning, or emergency command implication.

364.10 Data Contribution Permission.

364.10.1 Public authority data contribution permission shall identify source authority, data type, data class, permitted use, prohibited use, publication status, confidentiality, public records status where applicable, AI-use restriction, transfer restriction, retention, deletion, correction, attribution, non-attribution, public-safe status, and access classification.

364.10.2 Public authority data contribution shall not be treated as permission to publish, map, train on, embed, commercialize, transfer, benchmark, finance-readiness-route, recognition-route, certify, procure, or publicly attribute unless such permission is expressly recorded.

364.10.3 Data contribution permission shall be reviewed before any dataset release, dashboard release, map release, public-safe summary, evidence pack, technical baseline, model use, AI workflow, or external publication involving the contributed data.

364.11 Public Authority Confidentiality Limits.

364.11.1 Official Capacity Records shall identify confidentiality limits applicable to public authority engagement, including confidentiality restrictions, public records obligations, open meeting obligations, procurement restrictions, regulatory confidentiality, public health confidentiality, law enforcement sensitivity, infrastructure sensitivity, cyber sensitivity, personnel sensitivity, legal privilege, and protected knowledge restrictions.

364.11.2 Confidentiality commitments to public authorities shall be lawful, documented, and consistent with the Corporation’s nonprofit duties, public-safe publication obligations, correctionability, and legal compliance.

364.11.3 Confidentiality shall not be used to conceal misconduct, suppress required correction, evade breach notification, hide conflicts, or avoid lawful public authority record obligations.

364.12 Public Records and FOIA Considerations.

364.12.1 Official Capacity Records shall identify public records, freedom of information, open government, sunshine, audit, retention, public meeting, procurement, grant, public finance, and public authority disclosure considerations where applicable.

364.12.2 The Corporation shall not structure communications, controlled rooms, evidence rooms, data rooms, dashboards, maps, repositories, or publication review to evade lawful public authority records obligations.

364.12.3 Public Records and FOIA considerations may require capacity classification, meeting notices, public-safe redaction, separate public authority recordkeeping, confidentiality review, access restrictions, or legal review.

364.13 Public Authority Legal Review Where Required.

364.13.1 Public Authority Legal Review shall be obtained or confirmed where the public authority’s rules require review before official participation, data sharing, logo use, quote use, publication reference, controlled-room participation, confidentiality commitment, public records treatment, procurement-related communication, public finance-related communication, or publication approval.

364.13.2 The Corporation may require its own legal review before accepting or referencing any public authority legal position, confidentiality term, data restriction, official-capacity statement, or publication condition.

364.13.3 Public authority legal review shall not be represented as endorsement, adoption, approval, regulatory guidance, procurement approval, public finance approval, public warning, emergency command, or legal compliance approval for the Corporation.

364.14 Term and Expiration of Authority.

364.14.1 Official Capacity Records shall identify the term, expiration, event limit, project limit, publication limit, or continuing status of authority.

364.14.2 Authority shall expire at the end of its stated term, upon completion of the activity, upon participant role change, upon public authority revocation, upon material change in publication context, or upon discovery that the authority was invalid, unless renewed or confirmed.

364.14.3 Expired authority shall not support future references, continued logo use, repeated quote use, updated publications, new dashboards, new maps, new datasets, or new technical assets without renewal where material.

364.15 Withdrawal of Authority.

364.15.1 A public authority or participant may withdraw authority where permitted by law, agreement, or recorded terms.

364.15.2 Withdrawal of authority may require correction, removal, takedown, relabeling, non-attribution, access restriction, data use restriction, quote removal, logo removal, public clarification, controlled clarification, or archive update.

364.15.3 Withdrawal shall not require alteration of historical records where retention is lawful and necessary, but may require restriction, sealing, redaction, or public-safe treatment.

364.16 Official Capacity Records.

364.16.1 The Corporation shall maintain Official Capacity Records, including official capacity requirement records, written authority records, email or institutional confirmation records, scope of authority records, limits of authority records, attribution permission records, Approved Public Language records, logo and name use permission records, quote permission records, data contribution permission records, public authority confidentiality limit records, public records and FOIA consideration records, public authority legal review records, term and expiration records, withdrawal records, corrections, clarifications, restrictions, and archive records.

---

Section 365. Observer Status

365.1 Observer Status Definition.

365.1.1 Observer Status means a non-decisional, non-approving, non-endorsing, non-adopting, non-funding, non-procuring, non-regulatory, non-public-finance, non-public-warning, and non-emergency-command capacity in which a public authority, public official, public employee, regulator, public finance actor, infrastructure operator, public university actor, public laboratory actor, Tribal / Indigenous government representative, or other public-sector-affiliated person attends, receives, listens, views, or reviews information for learning or awareness.

365.1.2 Observer Status may apply to meetings, briefings, public authority learning sessions, workshops, controlled rooms, evidence rooms, data rooms, clean rooms, simulations, tabletop exercises, after-action learning, dashboard reviews, map reviews, technical reviews, events, panels, demonstrations, public-safe publication discussions, or other Corporation interfaces.

365.2 Observer Status as Learning or Awareness Only.

365.2.1 Observer Status shall be limited to learning, awareness, familiarization, listening, review, or information receipt, and shall not include approval, adoption, endorsement, official decision, public authority action, funding approval, procurement approval, regulatory approval, public finance approval, public warning, emergency command, or delegation.

365.2.2 Materials circulated to Observers shall include limitation language where risk exists that attendance or receipt may be misread as official action.

365.3 Observer Attendance.

365.3.1 Observer attendance shall be recorded where material, including participant name where permitted, public authority or institution where permitted, capacity, date, event, access class, materials received, restrictions, attribution status, and publication permissions.

365.3.2 Observer attendance shall not be publicly referenced unless attribution permission and public-safe review support the reference.

365.4 Observer Access Limits.

365.4.1 Observer access shall be limited to materials appropriate to the observer’s capacity, purpose, authority, access class, confidentiality obligations, public records implications, data rights, public authority restrictions, protected knowledge, cyber sensitivity, infrastructure sensitivity, and public-safe status.

365.4.2 Observer Status shall not automatically permit access to confidential, restricted, no-download, public authority, community-protected, Tribal / Indigenous, protected knowledge, cyber-sensitive, infrastructure-sensitive, finance-sensitive, or controlled-room materials.

365.4.3 Observer access may be revoked, restricted, or reclassified where access exceeds authority or creates risk.

365.5 Observer Confidentiality.

365.5.1 Observers may be required to comply with confidentiality, non-disclosure, no-download, no-copying, no-publication, no-attribution, no-AI-use, no-redistribution, public-safe handling, or controlled-room restrictions.

365.5.2 Observer confidentiality obligations shall be lawful, recorded, and consistent with public records obligations where applicable.

365.5.3 Confidentiality shall not convert Observer Status into approval or endorsement.

365.6 Observer Non-Attribution Where Applicable.

365.6.1 Observer identity, public authority affiliation, title, attendance, comments, questions, or presence shall not be attributed where non-attribution is required by agreement, public authority restriction, public records considerations, privacy, security, protected knowledge, or public-safe review.

365.6.2 Non-attribution may require generic description, aggregation, anonymization, omission from public materials, restricted attendance lists, or controlled records.

365.7 Observer No-Endorsement Rule.

365.7.1 Observer attendance, access, review, questions, comments, or receipt of materials shall not constitute endorsement of the Corporation, its publications, events, sponsors, providers, partners, technical assets, public authority learning materials, dashboards, maps, datasets, software, baselines, Nexus roles, GRF-related activities, GRA-related activities, national companies, Project SPVs, or any public-good output.

365.8 Observer No-Adoption Rule.

365.8.1 Observer Status shall not constitute adoption of Corporation evidence, methods, software, datasets, dashboards, maps, open technical baselines, schemas, APIs, SDKs, public authority learning materials, public-safe summaries, controlled vocabulary, Nexus-compatible profiles, or other outputs.

365.9 Observer No-Funding-Approval Rule.

365.9.1 Observer Status shall not constitute funding approval, grant approval, appropriation, donor approval, sponsor approval, public funding commitment, private funding commitment, or budget allocation.

365.10 Observer No-Procurement-Approval Rule.

365.10.1 Observer Status shall not constitute procurement approval, procurement eligibility, vendor qualification, preferred-provider status, purchasing recommendation, public contract approval, grant procurement approval, or public-private partnership approval.

365.11 Observer No-Regulatory-Approval Rule.

365.11.1 Observer Status shall not constitute regulatory approval, official guidance, safe harbor, enforcement position, compliance approval, permit approval, license approval, agency interpretation, regulatory endorsement, or policy adoption.

365.12 Observer No-Public-Finance-Approval Rule.

365.12.1 Observer Status shall not constitute public finance approval, tax credit approval, MDB / DFI approval, public guarantee, public credit support, sovereign obligation, municipal obligation, public finance commitment, public capital commitment, or public finance readiness.

365.13 Observer No-Public-Warning Rule.

365.13.1 Observer Status shall not constitute public warning, hazard alert, public health alert, public safety alert, infrastructure alert, cyber alert, evacuation notice, or official public risk communication.

365.14 Observer No-Emergency-Command Rule.

365.14.1 Observer Status shall not constitute emergency command, incident command, dispatch authority, evacuation authority, public health order, public safety order, emergency management direction, infrastructure operation direction, cyber response command, or operational resource direction.

365.15 Observer Correction Requirement for Overclaim.

365.15.1 Where Observer Status is publicly or externally misstated as endorsement, adoption, funding approval, procurement approval, regulatory approval, public finance approval, public warning, emergency command, public authority decision, official approval, or public-private partnership, the Corporation shall require correction, limitation language, public clarification, controlled clarification, takedown, or other remedy appropriate to the risk.

365.16 Observer Status Records.

365.16.1 The Corporation shall maintain Observer Status Records, including observer definition records, learning-or-awareness-only records, attendance records, access limit records, confidentiality records, non-attribution records, no-endorsement records, no-adoption records, no-funding-approval records, no-procurement-approval records, no-regulatory-approval records, no-public-finance-approval records, no-public-warning records, no-emergency-command records, overclaim correction records, permissions, restrictions, clarifications, and archive records.

---

Section 366. Regulator-Listening Status

366.1 Regulator-Listening Status Definition.

366.1.1 Regulator-Listening Status means a non-decisional capacity in which a regulator, regulatory staff member, regulatory office, public authority with regulatory duties, or regulatory-adjacent participant receives information, listens, observes, asks questions, reviews technical materials, or participates in learning without issuing or implying regulatory guidance, approval, safe harbor, permit, compliance determination, enforcement position, waiver, policy adoption, endorsement, or official decision.

366.1.2 Regulator-Listening Status may occur in briefings, workshops, public authority learning sessions, controlled rooms, technical reviews, dashboard reviews, map reviews, standards-support discussions, AI governance discussions, cybersecurity discussions, public-safe publication discussions, simulations, or other Corporation interfaces.

366.2 Listening Capacity Only.

366.2.1 Regulator-Listening participation shall be limited to listening, learning, observation, question-asking, technical discussion, awareness, or non-decisional review.

366.2.2 Regulator-Listening participation shall not be described as consultation, approval, clearance, endorsement, guidance, compliance review, official interpretation, or regulator acceptance unless a competent regulatory record expressly supports that status.

366.3 No Regulatory Guidance.

366.3.1 Regulator-Listening Status shall not constitute regulatory guidance, agency guidance, interpretive guidance, compliance guidance, no-action position, staff guidance, policy position, supervisory guidance, or regulatory instruction.

366.3.2 Corporation publications shall not state or imply that regulator attendance or comments establish how law or regulation applies.

366.4 No Regulatory Approval.

366.4.1 Regulator-Listening Status shall not constitute regulatory approval of the Corporation, its publications, technical assets, software, datasets, dashboards, maps, baselines, methods, evidence packs, public authority learning materials, Nexus-compatible profiles, sponsors, providers, projects, national companies, Project SPVs, or partner activities.

366.5 No Safe Harbor.

366.5.1 Regulator-Listening Status shall not create safe harbor, immunity, compliance shield, enforcement protection, authorized pathway, approved implementation route, or regulator-cleared process.

366.5.2 No person shall cite Regulator-Listening participation as evidence that any system, project, provider, dataset, AI model, cybersecurity practice, privacy practice, technical baseline, or public-good asset is safe-harbored.

366.6 No Permit.

366.6.1 Regulator-Listening Status shall not constitute permit, license, authorization, approval to operate, approval to deploy, approval to collect data, approval to publish, approval to map, approval to process data, approval to train AI, approval to transfer technology, or approval to perform regulated activity.

366.7 No Compliance Determination.

366.7.1 Regulator-Listening Status shall not constitute determination of legal compliance, regulatory compliance, AI compliance, cybersecurity compliance, privacy compliance, procurement compliance, public records compliance, export-control compliance, sanctions compliance, environmental compliance, public health compliance, public safety compliance, or professional compliance.

366.7.2 Compliance statements shall require separate competent review and shall not rely on regulator-listening attendance.

366.8 No Enforcement Position.

366.8.1 Regulator-Listening Status shall not constitute an enforcement position, non-enforcement commitment, no-action letter, enforcement discretion, waiver, settlement position, investigation result, audit conclusion, inspector general position, or supervisory opinion.

366.9 No Waiver.

366.9.1 Regulator-Listening Status shall not waive any legal, regulatory, public records, procurement, public finance, privacy, cybersecurity, public health, public safety, environmental, infrastructure, professional, or other obligation.

366.9.2 Neither the Corporation nor any participant shall represent that regulator attendance waives compliance obligations or review requirements.

366.10 No Policy Adoption.

366.10.1 Regulator-Listening Status shall not constitute adoption of Corporation policy, technical baseline, method, public-good software, dashboard, map, dataset, observability output, AI governance framework, cyber governance framework, controlled vocabulary, or Nexus architecture as public policy.

366.11 No Public Authority Endorsement.

366.11.1 Regulator-Listening Status shall not constitute endorsement, approval, sponsorship, support, validation, verification, certification, recognition, finance-readiness, procurement approval, rating, public warning, emergency command, or public authority action.

366.12 No Reliance on Regulator Attendance.

366.12.1 No person shall rely on regulator attendance, questions, comments, silence, non-objection, participation, receipt of materials, or listening as evidence of regulatory meaning.

366.12.2 Materials involving Regulator-Listening participation shall include non-reliance or regulator-listening limitation language where external reliance risk exists.

366.13 Regulator Confidentiality and Public Records Review.

366.13.1 Regulator-Listening participation shall be reviewed for confidentiality, public records, open government, procurement, enforcement sensitivity, supervisory confidentiality, privileged materials, public authority restrictions, and publication limitations where applicable.

366.13.2 The Corporation shall not disclose regulator participation, comments, questions, materials, or attendance where prohibited or where public-safe review requires non-attribution.

366.14 Regulator Reference Controls.

366.14.1 Regulator references shall use precise capacity language, avoid promotional framing, avoid logo use unless authorized, avoid quotes unless permitted, and avoid implication of approval, guidance, safe harbor, compliance, enforcement position, or policy adoption.

366.14.2 Regulator titles and agency names shall not be used in a manner that converts listening participation into authority.

366.15 Regulator-Listening Correction Requirement.

366.15.1 Where Regulator-Listening Status is misstated as guidance, approval, safe harbor, permit, compliance determination, enforcement position, waiver, policy adoption, endorsement, certification, recognition, finance-readiness, procurement approval, public warning, emergency command, or official action, the Corporation shall require prompt correction, public clarification, controlled clarification, takedown, or other remedy appropriate to risk.

366.16 Regulator-Listening Records.

366.16.1 The Corporation shall maintain Regulator-Listening Records, including status definition records, listening-capacity records, no-regulatory-guidance records, no-regulatory-approval records, no-safe-harbor records, no-permit records, no-compliance-determination records, no-enforcement-position records, no-waiver records, no-policy-adoption records, no-public-authority-endorsement records, non-reliance records, confidentiality and public records review records, reference control records, correction records, clarifications, restrictions, and archive records.

---

Section 367. Public Finance Reader Status

367.1 Public Finance Reader Status Definition.

367.1.1 Public Finance Reader Status means a non-approval, non-commitment, non-funding, non-investment, non-rating, non-guarantee, non-sovereign-obligation capacity in which a public finance, budget, treasury, grant, tax credit, appropriation, development finance, multilateral development bank, development finance institution, public guarantee, public credit, municipal finance, sovereign finance, infrastructure finance, or fiscal actor receives, reviews, listens to, or discusses Corporation materials for learning, diligence-literacy, evidence-literacy, or public-safe decision-support literacy.

367.1.2 Public Finance Reader Status may occur in capital-reader rooms, public finance reader rooms, public authority rooms, evidence rooms, data rooms, controlled rooms, briefings, workshops, RNFD, NFD, UNFSD, Nexus Rails discussions, Docket-facing discussions, Grid-facing discussions, GRA-facing discussions, dashboard reviews, map reviews, evidence pack reviews, proof pack reviews, or technical baseline discussions.

367.2 Public Finance Reader as Learning or Diligence-Literacy Participant.

367.2.1 Public Finance Reader participation shall be limited to learning, diligence literacy, public finance literacy, evidence literacy, technical literacy, observability literacy, public-safe decision-support literacy, or non-approval review unless a competent public finance authority separately and lawfully records a different status.

367.2.2 Public Finance Reader materials shall include limitation language stating that the Corporation does not approve financing, grants, tax credits, appropriations, guarantees, credit support, MDB / DFI participation, public finance, capital commitments, or sovereign obligations.

367.3 No Grant Approval.

367.3.1 Public Finance Reader Status shall not constitute grant approval, grant eligibility, grant scoring, grant award, grant commitment, grant recommendation, or grant compliance approval.

367.4 No Budget Allocation.

367.4.1 Public Finance Reader Status shall not constitute budget allocation, fiscal authorization, treasury commitment, agency budget approval, line-item support, program allocation, or public expenditure decision.

367.5 No Appropriation.

367.5.1 Public Finance Reader Status shall not constitute appropriation, legislative budget action, public authorization, fiscal measure, or legally binding allocation of public funds.

367.6 No Public Finance Approval.

367.6.1 Public Finance Reader Status shall not constitute public finance approval, infrastructure finance approval, public-private partnership approval, bond approval, loan approval, guarantee approval, tax-exempt financing approval, concessional finance approval, blended finance approval, or development finance approval.

367.7 No MDB / DFI Approval.

367.7.1 Public Finance Reader Status shall not constitute MDB approval, DFI approval, mandate letter, concept approval, board approval, investment committee approval, credit committee approval, environmental and social approval, project approval, guarantee approval, or public-sector lender commitment.

367.8 No Public Guarantee.

367.8.1 Public Finance Reader Status shall not constitute public guarantee, sovereign guarantee, municipal guarantee, public credit support, guarantee eligibility, guarantee term sheet, or guarantee commitment.

367.9 No Public Credit.

367.9.1 Public Finance Reader Status shall not constitute public credit, public loan, public credit enhancement, public lending decision, creditworthiness determination, public credit approval, or public credit commitment.

367.10 No Tax Credit Approval.

367.10.1 Public Finance Reader Status shall not constitute tax credit approval, tax incentive eligibility, tax allocation, tax benefit determination, tax compliance approval, or tax authority decision.

367.11 No Sovereign Obligation.

367.11.1 Public Finance Reader Status shall not constitute sovereign obligation, municipal obligation, public debt, public liability, fiscal commitment, public-private partnership commitment, treaty obligation, intergovernmental commitment, or government guarantee.

367.12 No Capital Commitment.

367.12.1 Public Finance Reader Status shall not constitute capital commitment, investment commitment, financing commitment, underwriting commitment, lending commitment, insurance commitment, grant commitment, budget commitment, or procurement commitment.

367.13 No Investment Advice.

367.13.1 Public Finance Reader materials shall not constitute investment advice, securities advice, recommendation to buy, sell, hold, invest, divest, finance, insure, lend, guarantee, underwrite, or commit public or private capital.

367.13.2 Public Finance Reader engagement shall not make the Corporation a broker-dealer, finder, placement agent, underwriter, financial adviser, municipal adviser, investment adviser, credit rating agency, insurance broker, lender, bank, public finance adviser, or transaction arranger.

367.14 No GRA Finance-Readiness Determination by GCRI US.

367.14.1 GCRI US shall not make finance-readiness, insurance-readiness, bankability, capital-readiness, investment-readiness, rating, or GRA finance-readiness determinations through Public Finance Reader engagement.

367.14.2 GCRI US may provide record-supported evidence, methods, observability, public-safe summaries, technical records, and GRA-facing inputs only within its non-executing evidence role and without determining finance-readiness.

367.15 Public Finance Reader Reference Controls.

367.15.1 References to Public Finance Readers shall be capacity-classified, non-promotional, non-approval, and non-commitment in language.

367.15.2 Public Finance Reader references shall not use names, logos, quotes, titles, attendance, comments, questions, or participation to imply grant approval, public finance approval, MDB / DFI approval, public guarantee, public credit, tax credit approval, sovereign obligation, capital commitment, finance-readiness, or investment support.

367.15.3 Public Finance Reader references shall include non-reliance and finance-boundary language where public or capital-reader reliance risk exists.

367.16 Public Finance Reader Records.

367.16.1 The Corporation shall maintain Public Finance Reader Records, including status definition records, learning or diligence-literacy participation records, no-grant-approval records, no-budget-allocation records, no-appropriation records, no-public-finance-approval records, no-MDB / DFI-approval records, no-public-guarantee records, no-public-credit records, no-tax-credit-approval records, no-sovereign-obligation records, no-capital-commitment records, no-investment-advice records, no-GRA-finance-readiness-determination records, reference control records, non-reliance language records, corrections, clarifications, restrictions, and archive records.

---

Section 368. Emergency-Management, Public Safety, and Public Health Participation

368.1 Emergency-Management Participation Definition.

368.1.1 Emergency-Management Participation means participation by emergency management agencies, emergency operations centers, disaster management bodies, civil defense bodies, resilience offices, incident management personnel, emergency communications personnel, emergency planners, or emergency-management-affiliated persons in Corporation learning, simulation, tabletop, after-action, observability, dashboard, map, evidence, technical literacy, or public-safe decision-support activities.

368.1.2 Emergency-Management Participation shall be non-command, non-public-warning, non-operational, non-dispatch, non-evacuation, non-resource-direction, and non-substitutional unless a competent public authority separately and lawfully records a different role, which shall not be presumed.

368.2 Public Safety Participation Definition.

368.2.1 Public Safety Participation means participation by law enforcement, fire, rescue, emergency medical services, dispatch, public safety communications, homeland security, emergency response, public safety planning, public safety technology, or similar public safety personnel or bodies in Corporation activities.

368.2.2 Public Safety Participation shall be governed with heightened attention to civil rights, privacy, public-safe publication, public warning risk, emergency command risk, vulnerable populations, public authority capacity, operational sensitivity, cyber sensitivity, infrastructure sensitivity, and records restrictions.

368.3 Public Health Participation Definition.

368.3.1 Public Health Participation means participation by public health agencies, epidemiological units, health surveillance bodies, public health emergency bodies, public hospitals in public authority capacity, biosecurity actors, health-system public interfaces, or public health personnel in Corporation learning, evidence, data governance, observability, dashboard, map, public-safe publication, biosecurity, public authority learning, or safeguards activities.

368.3.2 Public Health Participation shall be governed with heightened attention to health-sensitive data, privacy, vulnerable populations, biosecurity, public warning risk, public health order risk, emergency command risk, civil rights, accessibility, and public-safe communication.

368.4 Emergency Management Learning Only.

368.4.1 Emergency-management interfaces by default shall be learning-only, evidence-literacy, technical-literacy, observability-literacy, simulation, or public-safe decision-support literacy activities.

368.4.2 The Corporation shall not frame emergency-management participation as operational readiness approval, emergency command support, emergency alert approval, public warning approval, evacuation planning authority, resource deployment authority, public safety authority, or public health authority.

368.5 Scenario and Simulation Support.

368.5.1 Scenario and simulation support may include synthetic scenarios, degraded-mode analysis, digital twin demonstrations, AI-RAN / O-RAN signal scenarios, cyber incident scenarios, infrastructure resilience scenarios, public health scenarios, biosecurity scenarios, climate scenarios, nature-risk scenarios, water / food / energy scenarios, and cross-sector systemic risk scenarios.

368.5.2 Scenario and simulation outputs shall be clearly labeled as scenario, simulation, model, exercise, hypothetical, synthetic, demonstration, or learning materials and shall not be treated as real-world observations, forecasts, warnings, orders, or operational instructions unless a separate competent public authority record supports such treatment.

368.6 Tabletop Exercise Support.

368.6.1 Tabletop Exercise Support may include design, facilitation, evidence materials, technical literacy, observability materials, public-safe decision-support literacy, controlled-room materials, dashboards, maps, after-action learning, and correction records.

368.6.2 Tabletop Exercise Support shall not make the Corporation an incident commander, emergency management agency, public safety agency, public health authority, infrastructure operator, dispatch authority, or operational resource coordinator.

368.6.3 Tabletop materials shall include limitation language identifying their non-operational, non-command, non-public-warning, and learning-only status.

368.7 After-Action Learning Support.

368.7.1 After-Action Learning Support may include structured review of lessons, evidence gaps, method gaps, observability gaps, data governance gaps, communication gaps, technology gaps, public-safe publication gaps, and correction needs following exercises, simulations, incidents, or public authority learning activities.

368.7.2 After-Action Learning Support shall not constitute official after-action report of a public authority unless separately and lawfully authorized, and shall not create fault findings, liability determinations, regulatory findings, procurement determinations, public finance determinations, public warnings, or emergency commands.

368.7.3 After-action materials shall be reviewed for confidentiality, public records, public authority restrictions, cyber sensitivity, infrastructure sensitivity, health sensitivity, civil rights, community safeguards, protected knowledge, and public-safe publication.

368.8 No Incident Command.

368.8.1 The Corporation shall not act as incident commander, unified command participant, emergency operations authority, operational coordinator, emergency response director, public safety commander, public health commander, or infrastructure command body.

368.8.2 Corporation personnel shall not issue directions within an incident command structure unless separately and lawfully authorized in a role approved by the Board or competent officer, and any such role shall be narrowly recorded and consistent with applicable law.

368.9 No Dispatch Authority.

368.9.1 The Corporation shall not dispatch emergency personnel, public safety personnel, public health personnel, public works personnel, infrastructure crews, telecommunications crews, cyber response teams, medical personnel, volunteers, providers, or resources.

368.9.2 Dashboards, maps, observability outputs, simulations, evidence packs, or public-safe summaries shall not be used by the Corporation as dispatch instructions.

368.10 No Evacuation Authority.

368.10.1 The Corporation shall not issue evacuation orders, shelter-in-place orders, route instructions, public movement instructions, facility closure orders, public access restrictions, or other emergency protective-action directives.

368.10.2 Any materials that might be mistaken for evacuation or protective-action guidance shall be revised, restricted, labeled, or withheld unless issued by a competent public authority.

368.11 No Emergency Alert Authority.

368.11.1 The Corporation shall not issue official emergency alerts, wireless emergency alerts, public alert and warning system messages, public safety alerts, cyber alerts on behalf of public authorities, health alerts, weather alerts, infrastructure alerts, or public hazard alerts.

368.11.2 Corporation communications may refer audiences to competent public authority channels where appropriate but shall not replicate or replace emergency alert authority.

368.12 No Official Public Warning.

368.12.1 The Corporation shall not issue official public warnings concerning hazards, public health, public safety, cyber incidents, infrastructure failure, environmental conditions, biosecurity events, energy, water, food, telecom, transportation, or other emergency or risk conditions.

368.12.2 Public-safe summaries, dashboards, maps, observability outputs, degraded-mode indicators, or resilience indicators shall include limitation language where public warning confusion is possible.

368.13 No Public Health Order.

368.13.1 The Corporation shall not issue public health orders, clinical directives, quarantine directives, isolation directives, vaccination directives, testing directives, treatment directives, public health emergency declarations, or health-system operational instructions.

368.13.2 Public health materials shall be framed as learning, evidence support, methods support, data governance support, observability support, public-safe publication, or technical literacy unless a competent public health authority separately and lawfully issues official guidance.

368.14 No Safety Command.

368.14.1 The Corporation shall not issue public safety commands, law enforcement directives, fire service directives, rescue directives, emergency medical directives, dispatch directives, facility safety orders, infrastructure safety commands, crowd control instructions, or operational safety orders.

368.14.2 Public safety learning materials shall not be designed, labeled, or distributed as operational commands.

368.15 No Operational Resource Direction.

368.15.1 The Corporation shall not direct deployment, allocation, staging, activation, deactivation, routing, prioritization, or withdrawal of operational resources, including personnel, equipment, vehicles, infrastructure crews, cyber response teams, telecom crews, medical resources, public works resources, emergency supplies, food, water, energy, or shelter resources.

368.15.2 Evidence records, dashboards, maps, simulations, observability outputs, or public-safe summaries shall not be represented as operational resource direction.

368.16 No Substitution for Emergency Management, Public Safety, or Public Health Authorities.

368.16.1 Corporation activities shall not substitute for emergency management authorities, public safety authorities, public health authorities, public works authorities, public infrastructure operators, public warning authorities, public emergency communications systems, clinical authorities, or other competent public authorities.

368.16.2 Where a matter requires official public authority action, public warning, emergency command, public health order, public safety command, or operational response, the Corporation shall defer to and, where appropriate, direct audiences to competent public authorities.

368.17 Emergency-Management, Public Safety, and Public Health Records.

368.17.1 The Corporation shall maintain Emergency-Management, Public Safety, and Public Health Records, including emergency-management participation definition records, public safety participation definition records, public health participation definition records, emergency management learning-only records, scenario and simulation support records, tabletop exercise support records, after-action learning support records, no-incident-command records, no-dispatch-authority records, no-evacuation-authority records, no-emergency-alert-authority records, no-official-public-warning records, no-public-health-order records, no-safety-command records, no-operational-resource-direction records, no-substitution records, limitation notices, corrections, clarifications, restrictions, and archive records.

Section 369. Public Infrastructure Operator Participation

369.1 Public Infrastructure Operator Definition.

369.1.1 “Public Infrastructure Operator” means any public, publicly controlled, publicly regulated, publicly chartered, publicly funded where material, public-purpose, concessioned, franchised, licensed, or critical-service operator that owns, operates, manages, monitors, maintains, supports, regulates, supervises, coordinates, or materially participates in infrastructure serving the public, including utilities, ports, airports, transit systems, transportation systems, water systems, wastewater systems, energy systems, telecom systems, AI-RAN / O-RAN systems, public works systems, public health systems, cyber systems, emergency communications systems, food systems, logistics systems, environmental systems, housing systems, education systems, research infrastructure, and health-system infrastructure.

369.1.2 Public Infrastructure Operator status shall be interpreted broadly for boundary, records, public-safe publication, cyber-sensitive, infrastructure-sensitive, public authority, procurement, finance, provider-neutrality, and non-execution purposes.

369.1.3 Participation by a Public Infrastructure Operator shall not make the Corporation an infrastructure operator, utility operator, telecom operator, cyber operator, AI-RAN / O-RAN operator, port operator, airport operator, transportation operator, public works operator, public health operator, emergency communications operator, emergency management body, public safety authority, public authority, regulator, procurement body, funding body, or execution body.

369.2 Public Utility Participation.

369.2.1 Public Utility Participation may include participation by electric, gas, water, wastewater, district energy, broadband, telecommunications, public utility district, municipal utility, cooperative utility, investor-owned utility subject to public regulation, or other utility actors in learning, observability, evidence literacy, technical literacy, public-safe mapping review, controlled-room review, dashboard review, data governance, AI governance, cybersecurity, resilience, degraded-mode awareness, or technical baseline discussions.

369.2.2 Public Utility Participation shall be classified according to capacity, including public authority participant, regulated infrastructure operator, provider participant, technical expert, data provider, observer, public finance reader, emergency-management participant, or other recorded role.

369.2.3 Public Utility Participation shall not imply utility endorsement, public authority adoption, regulatory approval, procurement approval, provider preference, resilience certification, infrastructure rating, finance-readiness, public warning, emergency command, operational direction, or public-private partnership.

369.3 Port, Airport, Transit, Transportation, Water, Energy, Telecom, Public Works, Cyber, Health-System, and Other Infrastructure Participation.

369.3.1 Participation by port, airport, transit, transportation, water, energy, telecom, public works, cyber, health-system, and other infrastructure actors may support public-benefit learning, sectoral evidence literacy, observability literacy, methods development, public-safe dashboard review, map review, infrastructure-sensitive review, cyber-sensitive review, public authority data review, controlled-room review, and technical baseline improvement.

369.3.2 Such participation shall be reviewed for operational sensitivity, cyber sensitivity, infrastructure sensitivity, public authority capacity, regulated-provider status, procurement sensitivity, public finance sensitivity, civil rights, accessibility, community safeguards, protected knowledge, public-safe mapping, and emergency-management implications.

369.3.3 Participation by infrastructure operators shall not be used to imply operational control by the Corporation, operator approval of Corporation outputs, public authority adoption, public warning, emergency command, public finance approval, procurement approval, provider preference, certification, recognition, rating, or guarantee.

369.4 Technical Context Contribution.

369.4.1 A Public Infrastructure Operator may contribute technical context concerning system design, technical constraints, interoperability needs, observability requirements, resilience considerations, data governance needs, cyber considerations, infrastructure dependencies, AI-RAN / O-RAN signal context, DePIN or DLT telemetry context, digital twin context, geospatial context, or public-safe publication concerns.

369.4.2 Technical Context Contributions shall be recorded with source, date, contributor capacity, access class, confidentiality, data rights, public authority restrictions, cyber sensitivity, infrastructure sensitivity, permitted use, prohibited use, attribution, non-attribution, public-safe status, and correction path where material.

369.4.3 Technical Context Contributions shall not be treated as official operator approval, public authority adoption, certification, procurement support, regulatory approval, public finance support, finance-readiness, recognition, rating, public warning, emergency command, or operational instruction.

369.5 Operational Context Contribution.

369.5.1 Operational Context Contributions may include non-public or public information concerning operational realities, constraints, dependencies, degraded-mode conditions, restoration considerations, field limitations, public works realities, emergency-management interfaces, public health interfaces, public safety interfaces, cyber-physical dependencies, staffing constraints, supply constraints, geographic constraints, or service continuity concerns.

369.5.2 Operational Context Contributions shall be handled with heightened care and shall not be published, mapped, visualized, modeled, summarized, trained on, embedded, transferred, or externally shared unless lawful authority, data rights, public-safe review, cyber-sensitive review, infrastructure-sensitive review, and public authority review support the use.

369.5.3 Operational context shall be used for public-benefit learning and technical truth support only and shall not be converted into operational direction, public warning, emergency command, infrastructure rating, procurement advantage, finance-readiness, certification, recognition, or provider preference.

369.6 Infrastructure-Sensitive Data Controls.

369.6.1 Infrastructure-Sensitive Data Controls shall apply to data or materials that may reveal infrastructure location, configuration, capacity, dependency, weakness, vulnerability, outage, degraded mode, resilience gap, restoration sequence, operational workflow, physical security posture, cyber-physical dependency, or other information that could increase harm if disclosed or misused.

369.6.2 Infrastructure-Sensitive Data shall be classified, access-controlled, minimized, purpose-limited, logged where appropriate, protected against unauthorized AI processing, protected against unauthorized mapping, protected against unauthorized disclosure, and subject to release review before external use.

369.6.3 Infrastructure-Sensitive Data may require aggregation, redaction, resolution reduction, delay, masking, no-download access, controlled-room access, public authority review, or denial of release.

369.7 Cyber-Sensitive Data Controls.

369.7.1 Cyber-Sensitive Data Controls shall apply to vulnerability information, threat models, incident records, telemetry, logs, access patterns, network diagrams, repository risks, exploit-relevant details, secrets, keys, tokens, credentials, sensitive configurations, AI security findings, prompt-injection examples, data-poisoning examples, and cyber-physical system details.

369.7.2 Cyber-Sensitive Data shall not be published, externally circulated, entered into unapproved AI tools, stored in unapproved repositories, included in public dashboards, included in public maps, or disclosed to unauthorized persons.

369.7.3 Cyber-sensitive publication, if any, shall follow coordinated vulnerability disclosure, public-safe communication, legal review, public authority review where applicable, and incident response procedures.

369.8 Public-Safe Mapping Controls.

369.8.1 Public-Safe Mapping Controls shall apply to maps, dashboards, layers, coordinates, polygons, heatmaps, cluster displays, hotspot displays, digital twin views, AI-RAN / O-RAN signal views, DePIN telemetry views, DLT-linked location views, infrastructure layers, public health layers, public safety layers, and environmental layers involving public infrastructure operators.

369.8.2 Public-Safe Mapping Controls may require location generalization, aggregation, masking, delay, removal of sensitive assets, no-download access, controlled-room treatment, public authority review, infrastructure-sensitive review, cyber-sensitive review, protected knowledge review, and community safeguards review.

369.8.3 Public-safe maps shall not identify sensitive vulnerabilities, operational dependencies, targetable assets, emergency weaknesses, protected places, community-protected locations, or restricted infrastructure conditions unless lawful, authorized, and public-safe.

369.9 No Operational Control by GCRI US.

369.9.1 GCRI US shall not control, operate, dispatch, direct, supervise, manage, restore, maintain, command, certify, audit as authority, regulate, or approve public infrastructure through Public Infrastructure Operator participation.

369.9.2 GCRI US shall not issue operational instructions to infrastructure operators, utility crews, telecom operators, cyber teams, public works teams, port operators, airport operators, transit operators, public health operators, or emergency communications operators.

369.9.3 Any Corporation material that could reasonably be read as operational direction shall be revised, restricted, withdrawn, or relabeled.

369.10 No Public Authority Adoption by Operator Participation.

369.10.1 Public Infrastructure Operator participation shall not constitute public authority adoption of Corporation materials, including evidence records, observability outputs, dashboards, maps, datasets, software, technical baselines, reference architectures, schemas, APIs, SDKs, public authority learning materials, or public-safe summaries.

369.10.2 Public authority adoption may arise only through separate lawful action by the competent public authority and shall not be inferred from operator participation.

369.11 No Procurement Approval by Operator Participation.

369.11.1 Public Infrastructure Operator participation shall not constitute procurement approval, vendor qualification, preferred-provider status, public contract eligibility, purchasing recommendation, procurement specification, grant eligibility, or public-private partnership approval.

369.11.2 No provider, sponsor, vendor, or Project SPV may cite Public Infrastructure Operator participation as procurement advantage unless a competent procurement authority separately and lawfully records such status.

369.12 No Provider Preference by Operator Participation.

369.12.1 Public Infrastructure Operator participation shall not create provider preference, qualified-provider status, preferred integration status, technical approval, endorsement, market preference, ecosystem preference, or implementation preference.

369.12.2 Provider participation alongside Public Infrastructure Operators shall be managed to preserve provider neutrality, conflict controls, public authority trust, procurement neutrality, and public-safe claims discipline.

369.13 No Public Warning by Operator Participation.

369.13.1 Public Infrastructure Operator participation shall not create public warning, hazard alert, cyber alert, infrastructure alert, outage notice, evacuation notice, public health alert, public safety alert, or official risk communication.

369.13.2 Dashboards, maps, observability indicators, degraded-mode indicators, and resilience indicators involving operators shall include limitation language where public warning confusion is possible.

369.14 No Emergency Command by Operator Participation.

369.14.1 Public Infrastructure Operator participation shall not create emergency command, incident command, operational resource direction, restoration direction, dispatch authority, evacuation authority, cyber response command, public works command, public safety command, public health command, or infrastructure command.

369.14.2 Simulation, tabletop, scenario, digital twin, or after-action participation by operators shall be labeled as learning-only unless a competent public authority separately and lawfully records a different role.

369.15 Public Infrastructure Operator Reference Controls.

369.15.1 References to Public Infrastructure Operators shall be accurate, capacity-classified, permission-aware, public-safe, non-promotional, and limitation-aware.

369.15.2 Public Infrastructure Operator names, logos, quotes, images, attendance, technical context, operational context, data contribution, dashboard review, map review, or controlled-room participation shall not be used to imply endorsement, adoption, procurement approval, provider preference, public warning, emergency command, certification, recognition, finance-readiness, rating, public finance approval, or guarantee.

369.15.3 Operator references may require non-attribution, generic description, aggregation, redaction, controlled access, or prior approval where operational sensitivity, public authority restrictions, cyber sensitivity, infrastructure sensitivity, or public-safe risk exists.

369.16 Public Infrastructure Operator Records.

369.16.1 The Corporation shall maintain Public Infrastructure Operator Records, including definition records, public utility participation records, port / airport / transit / transportation / water / energy / telecom / public works / cyber / health-system / infrastructure participation records, technical context contribution records, operational context contribution records, infrastructure-sensitive data control records, cyber-sensitive data control records, public-safe mapping control records, no-operational-control records, no-public-authority-adoption records, no-procurement-approval records, no-provider-preference records, no-public-warning records, no-emergency-command records, reference control records, corrections, clarifications, restrictions, and archive records.

---

Section 370. Federal Interface Rules

370.1 Federal Interface Purpose.

370.1.1 Federal Interface Rules shall govern the Corporation’s interactions with federal public authorities, federal officials, federal employees, federal laboratories, federal research entities, federal grantors, federal procurement bodies, federal regulators, federal public finance readers, federal emergency-management actors, federal public health actors, federal public safety actors, federal infrastructure actors, and federal oversight bodies.

370.1.2 Federal interfaces shall be lawful, capacity-classified, records-based, public-safe, ethics-aware, procurement-neutral, public finance-neutral, non-regulatory, non-executing, non-public-warning, non-emergency-command, and consistent with federal confidentiality, records, cybersecurity, controlled technology, export-control, sanctions, national security sensitivity, and public authority boundary requirements.

370.1.3 Federal participation shall not be used to imply federal endorsement, adoption, procurement approval, funding approval, regulatory approval, public finance approval, sovereign obligation, public warning, emergency command, public-private partnership, or federal decision unless separately and lawfully recorded by competent federal authority.

370.2 Federal Agency Participation.

370.2.1 Federal Agency Participation may include attendance, observation, learning, technical discussion, public information exchange, data contribution, controlled-room participation, public authority room participation, research interface, grant interface, technical review, evidence literacy, public-safe dashboard review, map review, or event participation.

370.2.2 Federal Agency Participation shall be capacity-classified, including official participant, delegated representative, observer, regulator-listening participant, public finance reader, technical expert, public authority data provider, reviewer, emergency-management participant, public health participant, public safety participant, or personal-capacity participant.

370.2.3 Federal agency names, seals, logos, titles, quotes, photographs, and attendance references shall be used only with appropriate authority, permission, and public-safe review.

370.3 Federal Research Interface.

370.3.1 Federal Research Interfaces may include collaboration, public information exchange, grant-funded research, technical review, methods review, data sharing, public-benefit R&D, public-good software, open technical baseline discussion, public authority learning, and evidence literacy.

370.3.2 Federal Research Interfaces shall be reviewed for research ethics, human-subjects issues, public health sensitivity, data rights, IP rights, grant terms, publication rights, confidentiality, public records, federal data restrictions, controlled unclassified information where applicable, cybersecurity, export-control, sanctions, and public-safe publication.

370.3.3 Federal research participation shall not imply federal validation, certification, endorsement, official finding, public authority adoption, procurement approval, funding approval beyond the relevant award, public warning, emergency command, or regulatory approval.

370.4 Federal Grant Interface.

370.4.1 Federal Grant Interfaces shall distinguish grant application, grant discussion, grant award, grant administration, grant compliance, grant reporting, public-facing grant acknowledgment, and grant-funded publication.

370.4.2 Federal grant funding, if any, shall not be represented as federal endorsement, approval of findings, certification, procurement approval, public authority adoption, public warning, emergency command, recognition, finance-readiness, or public-private partnership unless competent federal record expressly supports the specific statement.

370.4.3 Federal grant materials shall comply with applicable award terms, allowable cost rules, reporting obligations, publication requirements, data rights, IP rights, acknowledgement rules, lobbying restrictions, procurement restrictions, and records requirements.

370.5 Federal Public Authority Learning Interface.

370.5.1 Federal Public Authority Learning Interfaces may support federal evidence literacy, methods literacy, observability literacy, technical literacy, data governance literacy, AI governance literacy, cybersecurity literacy, public-safe publication literacy, and decision-support literacy.

370.5.2 Learning interfaces shall not be framed as federal adoption, federal guidance, federal approval, federal regulation, federal procurement specification, federal public finance approval, federal public warning, or federal emergency command.

370.5.3 Learning materials provided to federal actors shall include limitation language proportionate to the risk of official-status confusion.

370.6 Federal Public Authority Data Interface.

370.6.1 Federal Public Authority Data Interfaces shall be governed by source authority, data rights, permitted use, prohibited use, confidentiality, public records considerations, controlled unclassified information considerations where applicable, privacy, cybersecurity, AI-use restrictions, publication restrictions, retention, deletion, attribution, non-attribution, public-safe status, and correction path.

370.6.2 Federal data shall not be published, mapped, trained on, embedded, transferred, used for finance-readiness, used for recognition, used for certification-like claims, used for procurement implication, or externally shared beyond permitted use.

370.7 Federal Procurement Boundary.

370.7.1 The Corporation shall not state or imply federal procurement approval, federal vendor qualification, federal preferred-provider status, federal public contract eligibility, federal procurement scoring, federal purchasing recommendation, federal procurement specification, or federal public-private partnership approval through federal participation.

370.7.2 Federal procurement-related interfaces shall be reviewed for conflicts, procurement integrity, gifts, ethics, lobbying, market neutrality, provider neutrality, sponsor non-control, and public-safe claims.

370.8 Federal Ethics and Gifts Boundary.

370.8.1 Federal interfaces shall be reviewed for ethics, gifts, travel, honoraria, hospitality, event access, preferential treatment, conflicts, appearance concerns, outside activity restrictions, and misuse of official position.

370.8.2 The Corporation shall not offer, provide, solicit, or imply benefits to federal officials or employees in exchange for access, endorsement, approval, procurement advantage, funding advantage, regulatory advantage, public finance advantage, or official action.

370.9 Federal Lobbying and Political Activity Boundary.

370.9.1 Federal interfaces shall be reviewed for lobbying, advocacy, political activity, election activity, appropriations advocacy, procurement advocacy, grant advocacy, regulatory advocacy, and charitable-law implications.

370.9.2 The Corporation shall preserve its nonprofit public-benefit character and shall not allow federal interface communications to become unauthorized lobbying, prohibited political activity, procurement influence, or regulated advocacy beyond lawful authority.

370.10 Federal Public Records and FOIA Considerations.

370.10.1 Federal interfaces shall be reviewed for federal public records, FOIA, agency records, federal retention, open government, audit, inspector general, grant records, procurement records, and confidentiality implications where applicable.

370.10.2 The Corporation shall not structure communications, rooms, dashboards, repositories, or data interfaces to evade lawful federal records obligations.

370.11 Federal Cybersecurity and Controlled Technology Considerations.

370.11.1 Federal interfaces involving cybersecurity, public-sector systems, AI systems, telecom, AI-RAN / O-RAN, DePIN, DLT, digital twins, geospatial data, public health data, emergency systems, critical infrastructure, controlled technology, or federal data shall be reviewed for cybersecurity obligations, access controls, incident response, secure transfer, vulnerability disclosure, controlled-room requirements, and public-safe release.

370.11.2 Federal cyber-sensitive or controlled technology materials shall not be externally released without competent review and authority.

370.12 Federal Export-Control, Sanctions, and National Security Sensitivity Considerations.

370.12.1 Federal interfaces involving controlled technology, dual-use systems, encryption, AI, cyber, geospatial systems, drones, robotics, semiconductors, advanced manufacturing, telecom, AI-RAN / O-RAN, DePIN, DLT, Earth observation, infrastructure, public safety, or national security-adjacent materials shall be reviewed for export-control, sanctions, controlled technology, and national security sensitivity.

370.12.2 Such review may require access restriction, recipient restriction, jurisdiction restriction, no-download access, controlled-room treatment, redaction, delay, denial of release, or legal escalation.

370.13 Federal Public Finance Boundary.

370.13.1 Federal public finance interfaces shall not be represented as federal public finance approval, federal grant approval, federal appropriation, federal guarantee, federal credit support, federal tax credit approval, MDB / DFI approval, sovereign obligation, public finance readiness, investment support, or capital commitment.

370.13.2 Federal public finance readers shall be capacity-classified and provided with non-reliance language where public finance reliance risk exists.

370.14 No Federal Endorsement, Adoption, Procurement, Funding, Regulation, Public Warning, Emergency Command, or Sovereign Obligation by Participation.

370.14.1 Federal participation, attendance, observation, data contribution, funding discussion, grant award, technical review, regulator-listening participation, public finance reading, dashboard review, map review, controlled-room participation, event participation, or public authority learning shall not imply federal endorsement, adoption, procurement approval, funding approval, regulation, public finance approval, public warning, emergency command, sovereign obligation, public-private partnership, or official federal decision beyond a competent federal record.

370.14.2 Any contrary implication shall be corrected, clarified, restricted, or withdrawn.

370.15 Federal Interface Records.

370.15.1 The Corporation shall maintain Federal Interface Records, including federal interface purpose records, federal agency participation records, federal research interface records, federal grant interface records, federal public authority learning interface records, federal public authority data interface records, federal procurement boundary records, federal ethics and gifts boundary records, federal lobbying and political activity boundary records, federal public records and FOIA consideration records, federal cybersecurity and controlled technology consideration records, federal export-control / sanctions / national security sensitivity consideration records, federal public finance boundary records, no-federal-endorsement / adoption / procurement / funding / regulation / public warning / emergency command / sovereign obligation records, corrections, clarifications, restrictions, and archive records.

---

Section 371. State Interface Rules

371.1 State Interface Purpose.

371.1.1 State Interface Rules shall govern the Corporation’s interactions with state agencies, state officials, state employees, state public authorities, state public universities, state laboratories, state public health authorities, state emergency-management authorities, state public safety bodies, state public works bodies, state infrastructure operators, state utility regulators, state public finance readers, state grantors, state procurement bodies, state regulators, state legislatures, state courts, state oversight bodies, and state-affiliated public-sector actors.

371.1.2 State interfaces shall be jurisdiction-specific, capacity-classified, lawful, public-safe, records-based, procurement-neutral, public finance-neutral, ethics-aware, non-regulatory, non-executing, non-public-warning, and non-emergency-command.

371.1.3 The Corporation shall not imply that any state interface applies uniformly across states or that participation by one state authority implies adoption, endorsement, approval, funding, procurement, regulation, public finance approval, public warning, emergency command, public-private partnership, or sovereign obligation by any other state or by the United States.

371.2 State Agency Participation.

371.2.1 State Agency Participation may include attendance, observation, learning, technical discussion, public information exchange, data contribution, controlled-room participation, public authority room participation, research interface, grant interface, technical review, evidence literacy, dashboard review, map review, publication reference, or event participation.

371.2.2 State Agency Participation shall be capacity-classified and shall not imply state endorsement, adoption, procurement approval, funding approval, regulatory approval, public finance approval, public warning, emergency command, sovereign obligation, or official decision unless competent state record supports the exact statement.

371.3 State Public Authority Learning Interface.

371.3.1 State Public Authority Learning Interfaces may support state-level evidence literacy, methods literacy, technical literacy, observability literacy, data governance literacy, AI governance literacy, cybersecurity literacy, public-safe publication literacy, and public-safe decision-support literacy.

371.3.2 Learning materials provided to state actors shall distinguish public-benefit learning support from state guidance, state regulation, state procurement specification, state funding approval, state public finance approval, state public warning, emergency command, or official state action.

371.4 State Research Interface.

371.4.1 State Research Interfaces may involve state universities, public laboratories, agencies, public health bodies, environmental bodies, emergency-management bodies, infrastructure bodies, or state-funded research programs.

371.4.2 State Research Interfaces shall be reviewed for research ethics, data rights, IP rights, grant terms, human-subjects protection, privacy, public health sensitivity, public records, publication rights, confidentiality, public authority restrictions, cyber sensitivity, infrastructure sensitivity, and public-safe publication.

371.4.3 State research participation shall not imply peer review, academic validation, state endorsement, state certification, state adoption, procurement approval, finance-readiness, recognition, rating, public warning, or emergency command.

371.5 State Grant Interface.

371.5.1 State Grant Interfaces shall distinguish grant application, grant discussion, grant award, grant administration, grant compliance, grant reporting, public-facing grant acknowledgment, and grant-funded publication.

371.5.2 State grant funding, if any, shall not be represented as state endorsement, approval of findings, certification, recognition, finance-readiness, procurement approval, public authority adoption, public warning, emergency command, or public-private partnership unless competent state record expressly supports the specific statement.

371.6 State Public Authority Data Interface.

371.6.1 State Public Authority Data Interfaces shall be governed by authority, data rights, permitted use, prohibited use, confidentiality, public records status, privacy, cybersecurity, AI-use restrictions, publication restrictions, retention, deletion, attribution, non-attribution, public-safe status, and correction path.

371.6.2 State data shall not be published, mapped, trained on, embedded, transferred, commercialized, routed into finance-readiness, routed into recognition, used for certification-like claims, or externally shared beyond permitted use.

371.7 State Procurement Boundary.

371.7.1 The Corporation shall not state or imply state procurement approval, vendor qualification, preferred-provider status, public contract eligibility, public-private partnership approval, purchasing recommendation, procurement specification, or procurement scoring through state participation.

371.7.2 State procurement-related interfaces shall be reviewed for procurement integrity, gifts, ethics, conflicts, market neutrality, provider neutrality, sponsor non-control, and public-safe claims.

371.8 State Ethics and Gifts Boundary.

371.8.1 State interfaces shall be reviewed for state ethics, gifts, travel, honoraria, hospitality, event access, conflict rules, appearance concerns, procurement integrity, outside activity restrictions, and misuse of official position.

371.8.2 The Corporation shall not provide or imply benefits to state officials or employees in exchange for endorsement, official access, procurement advantage, funding advantage, regulatory advantage, public finance advantage, or official action.

371.9 State Lobbying and Political Activity Boundary.

371.9.1 State interfaces shall be reviewed for lobbying, advocacy, political activity, election activity, appropriations advocacy, procurement advocacy, grant advocacy, regulatory advocacy, charitable-law restrictions, and state registration requirements where applicable.

371.9.2 The Corporation shall not allow state interface communications to become unauthorized lobbying, prohibited political activity, procurement influence, or regulated advocacy beyond lawful authority.

371.10 State Public Records, Sunshine, and Open Meetings Considerations.

371.10.1 State interfaces shall be reviewed for public records, sunshine, open meetings, audit, records retention, procurement records, grant records, public finance records, regulatory records, inspector general records, and confidentiality obligations where applicable.

371.10.2 Controlled rooms, public authority rooms, evidence rooms, dashboards, maps, repositories, and communications shall not be structured to evade lawful state transparency or records obligations.

371.11 State Privacy, AI, Cybersecurity, Public Sector Data, Public Health, Emergency Management, and Infrastructure Rules Where Applicable.

371.11.1 State interfaces shall be reviewed for applicable state privacy, AI, cybersecurity, public-sector data, public health, emergency management, public safety, public works, infrastructure, utility, critical infrastructure, and sector-specific rules.

371.11.2 State-specific legal or policy context shall not be generalized without review and shall be reflected in localization notes where material.

371.12 State Public Finance Boundary.

371.12.1 State public finance interfaces shall not be represented as state public finance approval, grant approval, appropriation, budget allocation, tax credit approval, guarantee, public credit support, municipal obligation, state obligation, bond approval, MDB / DFI approval, public-private partnership approval, or capital commitment.

371.12.2 State public finance readers shall be capacity-classified and provided with non-reliance language where public finance reliance risk exists.

371.13 State-by-State Localization.

371.13.1 State-by-State Localization shall be required where publications, public authority learning materials, public-safe dashboards, maps, technical baselines, data governance materials, AI governance materials, cyber materials, public authority references, procurement boundary materials, public finance materials, or public-safe summaries could be misread as uniformly applicable across states.

371.13.2 Localization may include state-specific notes, jurisdictional caveats, access restrictions, public authority review, privacy review, procurement review, public records review, or legal review.

371.14 No State Endorsement, Adoption, Procurement, Funding, Regulation, Public Warning, Emergency Command, Public Finance Approval, or Sovereign Obligation by Participation.

371.14.1 State participation, attendance, observation, data contribution, technical review, public authority learning, grant interaction, regulator-listening participation, public finance reading, dashboard review, map review, event participation, or controlled-room participation shall not imply state endorsement, adoption, procurement approval, funding approval, regulation, public warning, emergency command, public finance approval, sovereign obligation, public-private partnership, or official state decision beyond a competent state record.

371.14.2 Any contrary implication shall be corrected, clarified, restricted, or withdrawn.

371.15 State Interface Records.

371.15.1 The Corporation shall maintain State Interface Records, including state interface purpose records, state agency participation records, state public authority learning interface records, state research interface records, state grant interface records, state public authority data interface records, state procurement boundary records, state ethics and gifts boundary records, state lobbying and political activity boundary records, state public records / sunshine / open meetings consideration records, state privacy / AI / cybersecurity / public sector data / public health / emergency management / infrastructure rule review records, state public finance boundary records, state-by-state localization records, no-state-endorsement / adoption / procurement / funding / regulation / public warning / emergency command / public finance approval / sovereign obligation records, corrections, clarifications, restrictions, and archive records.

---

Section 372. District of Columbia and Territorial Interface Rules

372.1 District of Columbia Interface Purpose.

372.1.1 District of Columbia Interface Rules shall govern the Corporation’s interactions with District agencies, District officials, District public authorities, District public health bodies, District emergency-management bodies, District public safety bodies, District public works bodies, District infrastructure actors, District grantors, District procurement bodies, District regulators, District public finance readers, District oversight bodies, and District-affiliated public-sector actors.

372.1.2 District interfaces shall be lawful, capacity-classified, records-based, public-safe, ethics-aware, procurement-neutral, public finance-neutral, non-regulatory, non-executing, non-public-warning, and non-emergency-command.

372.1.3 District participation shall not imply District endorsement, adoption, procurement approval, funding approval, regulatory approval, public finance approval, public warning, emergency command, public-private partnership, or official District action unless competent District record supports the exact statement.

372.2 Puerto Rico Interface.

372.2.1 Puerto Rico interfaces shall be reviewed for Puerto Rico-specific legal, linguistic, public authority, public records, procurement, grant, public finance, emergency management, public health, infrastructure, energy, water, telecom, climate, disaster resilience, accessibility, and language-access considerations.

372.2.2 Materials involving Puerto Rico shall avoid false uniformity with states or other territories and shall include territorial localization where material.

372.2.3 Puerto Rico participation shall not imply endorsement, adoption, procurement approval, funding approval, regulatory approval, public finance approval, public warning, emergency command, sovereign obligation, or public-private partnership absent competent record.

372.3 Guam Interface.

372.3.1 Guam interfaces shall be reviewed for Guam-specific public authority context, public records, procurement, grant, public finance, emergency management, public health, infrastructure, ports, telecom, water, energy, disaster resilience, language access, accessibility, military-adjacent sensitivity where material, and Pacific regional context.

372.3.2 Guam-related publications, dashboards, maps, data, and learning materials shall be public-safe reviewed for territorial specificity, infrastructure sensitivity, geospatial sensitivity, and community safeguards.

372.4 U.S. Virgin Islands Interface.

372.4.1 U.S. Virgin Islands interfaces shall be reviewed for territorial public authority context, public records, procurement, grant, public finance, ports, energy, water, telecom, public health, emergency management, hurricane and climate resilience, tourism-linked infrastructure, language access, accessibility, and public-safe mapping.

372.4.2 U.S. Virgin Islands references shall not imply territorial approval, funding, procurement, public finance approval, public warning, emergency command, or official action without competent record.

372.5 American Samoa Interface.

372.5.1 American Samoa interfaces shall be reviewed for territorial public authority context, cultural context, local governance, public records, procurement, grant, public finance, infrastructure, ports, telecom, energy, water, food, public health, emergency management, climate and disaster resilience, language access, accessibility, and protected knowledge.

372.5.2 American Samoa materials shall be reviewed for cultural and community safeguards, territorial localization, public-safe mapping, and public authority boundary implications.

372.6 Northern Mariana Islands Interface.

372.6.1 Northern Mariana Islands interfaces shall be reviewed for territorial public authority context, public records, procurement, grant, public finance, ports, telecom, energy, water, food, public health, emergency management, climate and disaster resilience, language access, accessibility, community safeguards, and regional sensitivity.

372.6.2 Northern Mariana Islands references shall not imply territorial endorsement, adoption, funding approval, procurement approval, public finance approval, public warning, emergency command, or official territorial action absent competent record.

372.7 Territorial Public Authority Learning Interface.

372.7.1 Territorial Public Authority Learning Interfaces may support evidence literacy, technical literacy, observability literacy, data governance literacy, AI governance literacy, cybersecurity literacy, public-safe publication literacy, emergency management literacy, public health literacy, infrastructure resilience literacy, and decision-support literacy in territorial contexts.

372.7.2 Territorial learning interfaces shall include language-access, accessibility, territorial localization, public authority boundary, public-safe mapping, infrastructure sensitivity, and community safeguards where material.

372.8 Territorial Research Interface.

372.8.1 Territorial Research Interfaces shall be reviewed for research ethics, data rights, human-subjects considerations, public health sensitivity, environmental sensitivity, cultural context, community safeguards, protected knowledge, public authority restrictions, public records, grant terms, IP rights, publication rights, privacy, cybersecurity, and public-safe publication.

372.8.2 Territorial research participation shall not imply territorial endorsement, adoption, certification, recognition, finance-readiness, procurement approval, public warning, emergency command, or official finding.

372.9 Territorial Public Authority Data Interface.

372.9.1 Territorial Public Authority Data Interfaces shall be governed by source authority, permitted use, prohibited use, confidentiality, public records status, privacy, AI-use restrictions, publication restrictions, retention, deletion, attribution, non-attribution, territorial localization, public-safe status, and correction path.

372.9.2 Territorial data shall not be published, mapped, trained on, embedded, transferred, commercialized, used for finance-readiness, used for recognition, used for certification-like claims, used for procurement implication, or externally shared beyond permitted use.

372.10 Territorial Procurement Boundary.

372.10.1 The Corporation shall not state or imply territorial procurement approval, vendor qualification, preferred-provider status, public contract eligibility, public-private partnership approval, purchasing recommendation, grant procurement support, procurement specification, or procurement scoring through territorial participation.

372.10.2 Territorial procurement-related interfaces shall be reviewed for procurement integrity, gifts, ethics, conflicts, market neutrality, provider neutrality, sponsor non-control, and public-safe claims.

372.11 Territorial Ethics, Gifts, Public Records, Open Meetings, Privacy, AI, Cybersecurity, Public Health, Emergency Management, Infrastructure, and Public Finance Considerations Where Applicable.

372.11.1 Territorial interfaces shall be reviewed for ethics, gifts, hospitality, conflicts, public records, open meetings, privacy, AI governance, cybersecurity, public-sector data, public health, emergency management, public safety, infrastructure, public works, procurement, grants, public finance, and sector-specific rules where applicable.

372.11.2 Territorial interfaces may require localized review, public authority confirmation, language-access review, accessibility review, public-safe mapping review, and infrastructure-sensitive review.

372.12 Territorial Localization.

372.12.1 Territorial Localization shall be required where materials could be misread as applying uniformly to all territories, states, federal agencies, or public authorities.

372.12.2 Territorial Localization may include jurisdiction-specific notes, language-access supports, accessibility supports, infrastructure-context notes, disaster-resilience context, public authority capacity notes, privacy notes, public records notes, procurement notes, and public finance notes.

372.13 No Territorial Endorsement, Adoption, Procurement, Funding, Regulation, Public Warning, Emergency Command, Public Finance Approval, or Sovereign Obligation by Participation.

372.13.1 Territorial participation, attendance, observation, data contribution, technical review, public authority learning, regulator-listening participation, public finance reading, dashboard review, map review, event participation, grant interaction, or controlled-room participation shall not imply territorial endorsement, adoption, procurement approval, funding approval, regulation, public warning, emergency command, public finance approval, sovereign obligation, public-private partnership, or official territorial decision beyond a competent territorial record.

372.13.2 Any contrary implication shall be corrected, clarified, restricted, or withdrawn.

372.14 District of Columbia and Territorial Interface Records.

372.14.1 The Corporation shall maintain District of Columbia and Territorial Interface Records, including District of Columbia interface purpose records, Puerto Rico interface records, Guam interface records, U.S. Virgin Islands interface records, American Samoa interface records, Northern Mariana Islands interface records, territorial public authority learning interface records, territorial research interface records, territorial public authority data interface records, territorial procurement boundary records, territorial ethics / gifts / public records / open meetings / privacy / AI / cybersecurity / public health / emergency management / infrastructure / public finance consideration records, territorial localization records, no-territorial-endorsement / adoption / procurement / funding / regulation / public warning / emergency command / public finance approval / sovereign obligation records, corrections, clarifications, restrictions, and archive records.

---

Section 373. Tribal and Indigenous Government Interface Rules

373.1 Tribal and Indigenous Government Interface Purpose.

373.1.1 Tribal and Indigenous Government Interface Rules shall govern the Corporation’s interactions with Tribal governments, Indigenous governmental authorities, councils, traditional authorities where applicable, Indigenous organizations, Indigenous data stewards, knowledge holders, community representatives, and related public authority or community interfaces.

373.1.2 Such interfaces shall be lawful, respectful, sovereignty-aware, protocol-aware, permission-based, safeguards-reviewed, non-extractive, capacity-classified, public-safe, correctionable, and consistent with the Corporation’s non-executing role.

373.1.3 Tribal and Indigenous interfaces shall protect data sovereignty, knowledge governance, cultural integrity, local and territorial context, environmental knowledge, sacred knowledge, ecological knowledge, protected knowledge, attribution, non-attribution, withdrawal, restriction, correction, grievance, public-safe mapping, and AI-use restrictions.

373.2 Respect for Tribal Sovereignty.

373.2.1 The Corporation shall respect Tribal sovereignty, self-government, legal authority, data governance, knowledge governance, decision processes, and protocols.

373.2.2 No Corporation interface, publication, map, dashboard, dataset, evidence pack, technical baseline, software, public-safe summary, controlled-room process, or public authority learning material shall imply waiver of sovereignty, delegation of Tribal authority, consent to unrestricted use, or public authority adoption absent competent record.

373.2.3 Tribal sovereignty considerations shall be reviewed before referencing Tribal governments, lands, data, knowledge, representatives, or participation.

373.3 Respect for Indigenous Governance.

373.3.1 The Corporation shall respect Indigenous governance structures, including formal, traditional, community, cultural, territorial, knowledge-based, and environmental governance structures where applicable and lawfully engaged.

373.3.2 The Corporation shall not assume that a single individual, organization, event participant, data contributor, academic, public official, or community participant represents an Indigenous people, Nation, government, community, or knowledge system without competent record.

373.4 Government-to-Government Sensitivity Where Applicable.

373.4.1 Where engagement involves government-to-government sensitivity, the Corporation shall recognize that it is not a sovereign, not a public authority, and not a substitute for government-to-government relations between competent public authorities and Tribal or Indigenous governments.

373.4.2 The Corporation may support learning, evidence, methods, technical literacy, public-safe publication, and safeguards processes only within its non-executing, non-delegated role.

373.4.3 Government-to-government references shall not be used unless accurate, legally appropriate, and approved by competent authority.

373.5 Consent, Non-Consent, Attribution, Withdrawal, Restriction, and Correction Pathways.

373.5.1 Tribal and Indigenous interfaces shall record consent, non-consent, attribution, non-attribution, withdrawal, restriction, correction, and grievance pathways where materials involve names, references, data, knowledge, maps, dashboards, publications, images, recordings, quotes, public-safe summaries, or technical assets.

373.5.2 Consent shall be specific, informed, revocable where applicable, scope-limited, and recorded. Silence, attendance, informal comment, public availability, or prior publication shall not be treated as consent for all uses.

373.5.3 Withdrawal or restriction requests shall be reviewed promptly and may require access restriction, redaction, non-attribution, map modification, dataset restriction, AI index deletion where feasible, publication correction, controlled notice, or takedown.

373.6 Tribal Data Sovereignty Considerations.

373.6.1 Tribal Data Sovereignty considerations shall apply where data relates to Tribal governments, Tribal citizens, Tribal lands, Tribal resources, Tribal programs, Tribal infrastructure, Tribal public health, Tribal environmental conditions, Tribal cultural resources, or Tribal knowledge.

373.6.2 Such data shall be governed by authority, permission, permitted use, prohibited use, access class, publication rules, AI-use restrictions, transfer restrictions, retention, deletion, attribution, non-attribution, correction, and grievance pathways.

373.6.3 Tribal data shall not be treated as ordinary public data merely because it is available from public sources.

373.7 Indigenous Data Safeguards.

373.7.1 Indigenous Data Safeguards shall apply to data relating to Indigenous peoples, communities, territories, cultural practices, environmental knowledge, public health, infrastructure, vulnerability, or protected knowledge.

373.7.2 Safeguards may include community review, Indigenous review where applicable, restricted access, non-attribution, aggregation, redaction, public-safe mapping, AI-use prohibition, transfer restrictions, commercialization restriction, and correction pathways.

373.8 Indigenous Knowledge Safeguards.

373.8.1 Indigenous Knowledge Safeguards shall protect traditional knowledge, cultural knowledge, sacred knowledge, ecological knowledge, environmental knowledge, place-based knowledge, language knowledge, land-based knowledge, and protected knowledge from unauthorized extraction, publication, mapping, translation, AI processing, embedding, training, commercialization, or transfer.

373.8.2 Indigenous knowledge shall not be used in datasets, benchmarks, model training, embeddings, vector stores, dashboards, maps, digital twins, technical baselines, software, public-safe summaries, or publications without lawful authority and safeguards appropriate to the knowledge context.

373.9 Cultural, Local, Territorial, Environmental, and Protected Knowledge Safeguards.

373.9.1 Cultural, local, territorial, environmental, and protected knowledge safeguards shall apply to materials that may reveal sensitive places, ecological resources, cultural sites, environmental practices, territorial vulnerability, community exposure, sacred locations, or knowledge restricted by community protocol.

373.9.2 Such safeguards may require no-publication, controlled-room access, non-attribution, resolution reduction, redaction, delayed release, aggregation, map masking, AI-use prohibition, or withdrawal.

373.10 Community Protocols.

373.10.1 The Corporation shall respect applicable community protocols, engagement protocols, data protocols, knowledge protocols, publication protocols, mapping protocols, attribution protocols, and grievance protocols where lawfully and respectfully engaged.

373.10.2 Community protocols shall be recorded where material and shall inform access classification, publication review, public-safe mapping, AI use, correction, and withdrawal.

373.11 Public-Safe Mapping Controls.

373.11.1 Public-Safe Mapping Controls shall apply to maps or geospatial outputs involving Tribal or Indigenous lands, territories, communities, infrastructure, cultural places, sacred sites, ecological knowledge, environmental knowledge, vulnerability information, or protected knowledge.

373.11.2 Mapping may require resolution reduction, masking, aggregation, non-attribution, omission, delayed release, controlled access, or denial of release.

373.11.3 Public-safe mapping shall not expose sensitive places, restricted knowledge, vulnerable communities, or protected resources.

373.12 No Assumption of Representation or Consent.

373.12.1 The Corporation shall not assume that participation by any person, organization, official, academic, community member, knowledge holder, public authority participant, or event attendee constitutes representation of, or consent by, a Tribal or Indigenous government, Nation, people, community, or knowledge system.

373.12.2 Representation and consent shall require competent record appropriate to the context.

373.13 No Use of Tribal or Indigenous Names, Symbols, Knowledge, Data, or References Without Approval.

373.13.1 Tribal or Indigenous names, symbols, flags, seals, logos, cultural references, knowledge, data, images, maps, quotes, recordings, stories, language materials, environmental knowledge, sacred knowledge, ecological knowledge, or protected knowledge shall not be used without approval appropriate to the context.

373.13.2 Approval shall be recorded and shall identify scope, duration, attribution, non-attribution, permitted use, prohibited use, publication status, AI-use restrictions, transfer restrictions, correction, withdrawal, and public-safe limitations.

373.14 No Delegation of Tribal or Indigenous Government Authority to GCRI US.

373.14.1 Participation by Tribal or Indigenous governments or representatives shall not delegate governmental authority, cultural authority, data authority, knowledge authority, public warning authority, procurement authority, funding authority, or sovereign authority to GCRI US.

373.14.2 GCRI US shall not represent itself as speaking for, deciding for, certifying, recognizing, financing, procuring for, or exercising authority on behalf of Tribal or Indigenous governments unless a competent and lawful record expressly authorizes a narrow statement.

373.15 No Endorsement, Adoption, Funding, Procurement, Public Warning, Emergency Command, or Sovereign Obligation by Participation.

373.15.1 Tribal or Indigenous participation, attendance, data contribution, knowledge contribution, review, comment, public authority learning, controlled-room participation, dashboard review, map review, or publication involvement shall not imply endorsement, adoption, funding approval, procurement approval, public warning, emergency command, sovereign obligation, public-private partnership, recognition, finance-readiness, certification, or public authority decision absent competent record.

373.15.2 Any contrary implication shall be corrected, clarified, restricted, or withdrawn.

373.16 Tribal and Indigenous Interface Records.

373.16.1 The Corporation shall maintain Tribal and Indigenous Interface Records, including interface purpose records, Tribal sovereignty records, Indigenous governance records, government-to-government sensitivity records, consent / non-consent / attribution / withdrawal / restriction / correction pathway records, Tribal Data Sovereignty consideration records, Indigenous Data Safeguard records, Indigenous Knowledge Safeguard records, cultural / local / territorial / environmental / protected knowledge safeguard records, community protocol records, public-safe mapping control records, no-assumption-of-representation-or-consent records, name / symbol / knowledge / data / reference approval records, no-delegation records, no-endorsement / adoption / funding / procurement / public warning / emergency command / sovereign obligation records, corrections, clarifications, restrictions, and archive records.

---

Section 374. Local, County, Municipal, Metropolitan, Utility, Port, and Infrastructure Interface Rules

374.1 Local Interface Purpose.

374.1.1 Local Interface Rules shall govern the Corporation’s interactions with local, county, municipal, metropolitan, utility, port, airport, public works, public health, public safety, emergency management, telecom, energy, water, food, transportation, logistics, cyber, environmental, housing, education, and infrastructure actors.

374.1.2 Local interfaces shall be lawful, capacity-classified, records-based, public-safe, public authority boundary-compliant, procurement-neutral, public finance-neutral, non-regulatory, non-executing, non-public-warning, and non-emergency-command.

374.1.3 Local participation shall not imply local endorsement, adoption, procurement approval, funding approval, regulation, public warning, emergency command, public finance approval, public-private partnership, or official local action unless competent record supports the exact statement.

374.2 County Interface.

374.2.1 County Interfaces may involve county governments, county agencies, county public health bodies, county emergency management bodies, county public safety bodies, county public works bodies, county infrastructure actors, county procurement bodies, county finance bodies, county courts, county schools where applicable, and county officials or employees.

374.2.2 County interfaces shall be reviewed for public records, procurement, public health, public safety, emergency management, public works, infrastructure, land use, community exposure, privacy, cyber sensitivity, public-safe mapping, public finance, and public authority boundary issues.

374.3 Municipal Interface.

374.3.1 Municipal Interfaces may involve city, town, village, borough, parish, township, municipal corporation, municipal agency, municipal utility, municipal public health, municipal public safety, municipal public works, municipal infrastructure, municipal procurement, municipal finance, and municipal officials or employees.

374.3.2 Municipal references shall be specific to the municipality and shall not imply county, state, metropolitan, regional, federal, or public authority approval unless separately supported by record.

374.4 Metropolitan Interface.

374.4.1 Metropolitan Interfaces may involve metropolitan planning organizations, regional councils, transit authorities, regional infrastructure bodies, regional water bodies, regional energy bodies, port authorities, airport authorities, emergency planning bodies, public health coalitions, and multi-jurisdictional public-sector entities.

374.4.2 Metropolitan interfaces shall be reviewed for multi-jurisdictional authority, public records, procurement, public finance, intergovernmental agreements, public-safe mapping, infrastructure sensitivity, data-sharing, and role attribution.

374.4.3 Participation by one metropolitan actor shall not imply adoption by all jurisdictions in the region.

374.5 Utility Interface.

374.5.1 Utility Interfaces may involve public utilities, municipal utilities, cooperatives, investor-owned utilities subject to public regulation, utility districts, water utilities, wastewater utilities, electric utilities, gas utilities, district energy systems, broadband utilities, telecom utilities, and utility regulators where applicable.

374.5.2 Utility interfaces shall be reviewed for regulated-provider status, public authority status, provider-neutrality risk, procurement sensitivity, public utility data restrictions, cyber sensitivity, infrastructure sensitivity, operational sensitivity, public-safe mapping, and public warning risk.

374.5.3 Utility participation shall not imply utility endorsement, regulatory approval, public authority adoption, procurement approval, provider preference, finance-readiness, recognition, certification, rating, public warning, emergency command, or operational control by GCRI US.

374.6 Port and Airport Interface.

374.6.1 Port and Airport Interfaces may involve port authorities, airport authorities, operators, logistics actors, customs-adjacent actors, transportation authorities, security actors, emergency management actors, public safety actors, infrastructure actors, and regulated private operators performing public-purpose functions.

374.6.2 Port and airport interfaces shall be reviewed for security sensitivity, cyber sensitivity, infrastructure sensitivity, transportation dependency, logistics dependency, public safety, emergency management, public health, geospatial sensitivity, controlled technology, public authority status, procurement, and public finance implications.

374.6.3 Port or airport participation shall not imply operational approval, security approval, public authority adoption, public warning, emergency command, procurement approval, finance-readiness, certification, recognition, rating, or provider preference.

374.7 Public Works Interface.

374.7.1 Public Works Interfaces may involve roads, bridges, buildings, public lands, water, wastewater, stormwater, sanitation, facilities, drainage, maintenance, engineering, and related local or public infrastructure functions.

374.7.2 Public works interfaces shall be reviewed for infrastructure sensitivity, geospatial exposure, public-safe mapping, operational reliance, procurement sensitivity, public records, civil rights, accessibility, environmental context, and community exposure.

374.7.3 Public works participation shall not imply engineering certification, operational direction, infrastructure approval, procurement approval, public authority adoption, public warning, emergency command, or provider preference.

374.8 Public Health and Public Safety Interface.

374.8.1 Public Health and Public Safety Interfaces shall be governed with heightened review for health-sensitive data, vulnerable populations, civil rights, accessibility, public warning risk, emergency command risk, law enforcement sensitivity, public safety sensitivity, privacy, public records, biosecurity, public-safe mapping, and community safeguards.

374.8.2 Public health and public safety participation shall not imply public health order, public safety order, law enforcement action, clinical advice, public warning, emergency command, certification, procurement approval, public authority adoption, finance-readiness, recognition, rating, or operational command.

374.9 Emergency Management Interface.

374.9.1 Emergency Management Interfaces may include learning sessions, simulations, tabletop exercises, after-action learning, degraded-mode analysis, dashboard review, map review, observability review, evidence literacy, technical literacy, and public-safe decision-support literacy.

374.9.2 Emergency management interfaces shall not create incident command, dispatch authority, evacuation authority, emergency alert authority, official public warning, public safety command, public health order, operational resource direction, or substitution for competent emergency management authorities.

374.10 Telecom, Energy, Water, Food, Transportation, Logistics, Cyber, Environmental, Housing, Education, and Infrastructure Interface.

374.10.1 Interfaces involving telecom, energy, water, food, transportation, logistics, cyber, environmental, housing, education, and other infrastructure systems shall be reviewed for sector-specific legal, technical, operational, public authority, public records, procurement, public finance, cyber, privacy, infrastructure-sensitive, community, accessibility, civil rights, protected knowledge, and public-safe publication considerations.

374.10.2 Such interfaces may support evidence literacy, technical literacy, observability, public-good software, technical baselines, data governance, AI governance, cyber governance, resilience learning, and public-safe publication, but shall not create execution authority, provider preference, public authority adoption, procurement approval, finance-readiness, certification, recognition, rating, public warning, or emergency command.

374.11 Local Procurement Boundary.

374.11.1 Local interfaces shall not be represented as local procurement approval, vendor qualification, preferred-provider status, public contract eligibility, public-private partnership approval, purchasing recommendation, procurement specification, grant procurement support, or procurement scoring.

374.11.2 Public-good software, dashboards, maps, evidence packs, methods, technical baselines, APIs, SDKs, schemas, profiles, or Nexus-compatible references shall not be used as local procurement approval by GCRI US.

374.12 Local Public Records and Open Meeting Considerations.

374.12.1 Local interfaces shall be reviewed for public records, open meetings, sunshine, audit, procurement records, grant records, public finance records, emergency records, public health records, public safety records, public works records, and confidentiality obligations where applicable.

374.12.2 The Corporation shall not structure local communications, controlled rooms, evidence rooms, data rooms, dashboards, maps, repositories, or publication reviews to evade lawful local transparency or records obligations.

374.13 Local Public Authority Data Controls.

374.13.1 Local Public Authority Data Controls shall govern data received from, created with, derived from, or referencing local, county, municipal, metropolitan, utility, port, public health, public safety, emergency management, public works, or infrastructure actors.

374.13.2 Such data shall be governed by authority, permitted use, prohibited use, confidentiality, public records status, privacy, cyber sensitivity, infrastructure sensitivity, AI-use restrictions, publication restrictions, retention, deletion, attribution, non-attribution, public-safe status, and correction path.

374.14 Local Public-Safe Mapping Controls.

374.14.1 Local Public-Safe Mapping Controls shall apply to maps, dashboards, geospatial outputs, digital twin views, observability views, infrastructure layers, public health layers, emergency management layers, public safety layers, utility layers, port layers, telecom layers, water layers, energy layers, food layers, environmental layers, and community layers.

374.14.2 Public-safe mapping may require aggregation, redaction, resolution reduction, masking, delay, removal of sensitive layers, no-download access, controlled-room access, public authority review, infrastructure-sensitive review, cyber-sensitive review, community safeguards review, or denial of release.

374.15 No Local Endorsement, Adoption, Procurement, Funding, Regulation, Public Warning, Emergency Command, Public Finance Approval, or Public-Private Partnership by Participation.

374.15.1 Local, county, municipal, metropolitan, utility, port, airport, public health, public safety, emergency management, public works, telecom, energy, water, food, transportation, logistics, cyber, environmental, housing, education, infrastructure, or related participation shall not imply endorsement, adoption, procurement approval, funding approval, regulation, public warning, emergency command, public finance approval, public-private partnership, official decision, provider preference, certification, recognition, finance-readiness, rating, or guarantee beyond a competent public authority record.

374.15.2 Any contrary implication shall be corrected, clarified, restricted, withdrawn, or publicly corrected where necessary.

374.16 Local and Infrastructure Interface Records.

374.16.1 The Corporation shall maintain Local and Infrastructure Interface Records, including local interface purpose records, county interface records, municipal interface records, metropolitan interface records, utility interface records, port and airport interface records, public works interface records, public health and public safety interface records, emergency management interface records, telecom / energy / water / food / transportation / logistics / cyber / environmental / housing / education / infrastructure interface records, local procurement boundary records, local public records and open meeting consideration records, local public authority data control records, local public-safe mapping control records, no-local-endorsement / adoption / procurement / funding / regulation / public warning / emergency command / public finance approval / public-private partnership records, corrections, clarifications, restrictions, and archive records.

Section 375. Cross-Border and North America Public Authority Interfaces

375.1 North America Public Authority Interface Purpose.

375.1.1 North America Public Authority Interfaces shall govern the Corporation’s lawful, non-executing, public-benefit, evidence, methods, observability, ontology, public-good technical asset, public authority learning, and public-safe publication interfaces with public authorities and public-sector actors across the United States, Canada, Mexico, the Caribbean, Arctic contexts, border regions, shared watersheds, shared supply chains, cross-border infrastructure systems, and related regional resilience environments.

375.1.2 North America Public Authority Interfaces shall preserve legal separateness, entity separateness, jurisdictional specificity, sovereign authority boundaries, no shared treasury, no agency, no partnership, no joint venture, no treaty authority, no intergovernmental decision authority, no public authority delegation, no cross-border execution authority, no public warning authority, no emergency command authority, no procurement authority, no public finance authority, and no regulatory authority by implication.

375.1.3 The Corporation may support North America public authority learning, evidence literacy, technical literacy, observability literacy, public-safe decision-support literacy, public-good software literacy, data governance literacy, AI governance literacy, cyber literacy, and resilience literacy, provided that all such support remains record-based, capacity-classified, public-safe, jurisdiction-aware, and consistent with the Corporation’s non-executing role.

375.2 Canada Interface Coordination With GCRI Canada.

375.2.1 Canada-related public authority interfaces shall be coordinated with GCRI Canada where such coordination is lawful, appropriate, mission-compatible, and consistent with entity separateness, separate governance, separate records, separate liabilities, separate treasury, and the respective public-benefit roles of GCRI US and GCRI Canada.

375.2.2 Canada interface coordination may include evidence literacy, methods literacy, observability methods, public-safe publication, public-good technical assets, public authority learning, cross-border resilience learning, public-safe dashboards, public-safe maps, open technical baselines, technical profiles, and controlled vocabulary alignment.

375.2.3 Coordination with GCRI Canada shall not imply that GCRI US controls GCRI Canada, that GCRI Canada controls GCRI US, that either entity speaks for Canadian public authorities, that either entity exercises sovereign authority, or that any Canadian public authority has adopted, endorsed, approved, funded, procured, regulated, publicly warned through, commanded through, or delegated authority to either entity absent competent record.

375.3 Mexico Interface Where Lawfully Structured.

375.3.1 Mexico-related public authority interfaces may be structured only where lawful, appropriately authorized, jurisdictionally reviewed, language-access aware, public-safe, and consistent with the Corporation’s non-executing public-benefit purpose.

375.3.2 Mexico interfaces may include cross-border evidence literacy, public health learning, disaster resilience learning, telecom and energy resilience learning, water and food systems learning, cyber and infrastructure learning, supply-chain resilience learning, and public-safe technical translation.

375.3.3 Mexico-related references shall not imply Mexican federal, state, local, regulatory, public finance, emergency, procurement, or public authority endorsement, adoption, approval, funding, procurement, regulation, public warning, emergency command, sovereign obligation, treaty action, or public-private partnership absent competent record and lawful authority.

375.4 Caribbean Interface Where Lawfully Structured.

375.4.1 Caribbean interfaces may be structured where lawful, public-benefit-aligned, locally respectful, jurisdiction-aware, language-access aware, disaster-resilience aware, public health aware, infrastructure-sensitive, community-safeguards reviewed, and public-safe.

375.4.2 Caribbean interfaces may address public authority learning, island resilience, hurricane and climate risk, water and energy systems, ports, telecom, food systems, public health, cyber resilience, supply chains, disaster recovery, and protected knowledge safeguards.

375.4.3 Caribbean interface materials shall not imply regional authority, sovereign coordination, public authority adoption, public finance approval, procurement approval, emergency command, public warning, treaty authority, or public-private partnership unless separately and lawfully supported.

375.5 Arctic Interface Where Lawfully Structured.

375.5.1 Arctic interfaces may be structured where lawful, public-benefit-aligned, Indigenous-safeguards reviewed, environmental-safeguards reviewed, public authority-boundary reviewed, cross-border reviewed, and public-safe.

375.5.2 Arctic interfaces may involve climate, nature, energy, telecom, transportation, ports, emergency management, public health, food systems, water systems, geospatial systems, Earth observation, digital twins, Indigenous knowledge safeguards, and public-safe mapping.

375.5.3 Arctic interface materials shall not expose sensitive environmental, Indigenous, infrastructure, public safety, geospatial, defense-adjacent, cyber-sensitive, or protected knowledge materials without lawful authority and appropriate safeguards.

375.6 Great Lakes, Atlantic, Pacific, Gulf, Border, Port, Energy, Water, Food, Public Health, Cyber, Telecom, Transportation, Supply Chain, and Disaster Interfaces.

375.6.1 Cross-border and regional interfaces involving the Great Lakes, Atlantic, Pacific, Gulf, land borders, ports, airports, energy systems, water systems, food systems, public health systems, cyber systems, telecom systems, transportation systems, supply chains, disaster systems, and climate or nature systems shall be reviewed for jurisdictional authority, public authority capacity, data rights, privacy, cybersecurity, infrastructure sensitivity, public-safe mapping, Indigenous data safeguards, protected knowledge, export-control, sanctions, controlled technology, public records, procurement, public finance, and emergency implications.