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.
375.6.2 Such interfaces may support shared learning, common vocabulary, public-safe observability methods, evidence-literacy materials, technical baselines, data governance templates, AI governance templates, cyber hygiene learning, and public-safe publication, but shall not create cross-border operational control or intergovernmental action.
375.6.3 Cross-border infrastructure, public health, cyber, telecom, transportation, food, water, energy, and disaster materials shall include limitation language sufficient to prevent public warning, emergency command, procurement, public finance, regulatory, or sovereign-obligation misunderstanding.
375.7 Cross-Border Public Authority Data Controls.
375.7.1 Cross-Border Public Authority Data shall be governed by authority records, jurisdictional permissions, permitted use, prohibited use, source restrictions, public authority restrictions, privacy obligations, data localization considerations, transfer restrictions, AI-use restrictions, publication restrictions, retention, deletion, access class, attribution, non-attribution, public-safe status, and correction path.
375.7.2 Cross-border public authority data shall not be published, mapped, transferred, trained on, embedded, indexed, commercialized, routed into finance-readiness, routed into recognition, used for certification-like claims, used for procurement implication, or externally shared beyond recorded authority.
375.7.3 Cross-border public authority data interfaces shall preserve separation among GCRI US, GCRI Canada, GRF, GRA, public authorities, consortiums, national companies, Project SPVs, providers, sponsors, and enterprise actors.
375.8 Cross-Border Privacy, AI, Cyber, Export-Control, Sanctions, Controlled Technology, Public Authority, Indigenous, Protected Knowledge, and Conflict-of-Law Review.
375.8.1 Cross-border interfaces shall receive review where they may implicate privacy, data protection, AI governance, cybersecurity, controlled technology, export-control, sanctions, public authority restrictions, Indigenous data, protected knowledge, confidential materials, public health data, infrastructure data, cyber-sensitive materials, or conflict-of-law issues.
375.8.2 Review may require legal review, public authority confirmation, GCRI Canada coordination where Canada-related, language-access review, Indigenous safeguards review, public-safe mapping review, access restriction, no-download access, controlled-room treatment, transfer limitation, recipient limitation, jurisdiction limitation, redaction, delay, denial of release, or deletion where lawful.
375.8.3 Where laws, permissions, public authority restrictions, community protocols, or protected knowledge obligations conflict, the Corporation shall apply the most restrictive rule reasonably necessary to protect rights, lawful authority, public trust, public safety, public-good purpose, and correctionability.
375.9 No North America Sovereign Authority.
375.9.1 The Corporation shall not claim, imply, exercise, accept, or be represented as holding North America sovereign authority, regional sovereign authority, cross-border public authority, supranational authority, treaty authority, or governmental power.
375.9.2 North America anchor language shall refer only to the Corporation’s non-executing public-good evidence, methods, observability, technical asset, and public authority learning role, and shall not imply control over sovereigns, public authorities, GCRI Canada, Mexico-related authorities, Caribbean authorities, Arctic authorities, GRF, GRA, consortiums, national companies, Project SPVs, providers, sponsors, or enterprise actors.
375.10 No Treaty Authority.
375.10.1 The Corporation shall not negotiate, enter, interpret, administer, implement, or enforce treaties, international agreements, intergovernmental agreements, memoranda among sovereigns, cross-border compacts, public authority compacts, or diplomatic commitments.
375.10.2 Corporation participation in cross-border learning, evidence, methods, observability, technical baseline, or public-safe publication activity shall not be represented as treaty-related action or diplomatic action.
375.11 No Intergovernmental Decision Authority.
375.11.1 The Corporation shall not make intergovernmental decisions, coordinate sovereign decisions, bind public authorities, allocate public duties, approve cross-border programs, issue regional public authority findings, or determine public authority obligations.
375.11.2 Intergovernmental decisions may be made only by competent public authorities through lawful processes, and no Corporation record shall be used to imply otherwise.
375.12 No Cross-Border Public Warning, Emergency Command, Procurement, Public Finance, Regulatory, or Sovereign Obligation Authority.
375.12.1 The Corporation shall not issue cross-border public warnings, emergency commands, public health orders, public safety orders, infrastructure directives, cyber alerts on behalf of public authorities, procurement approvals, public finance approvals, regulatory approvals, sovereign obligations, public guarantees, public credit commitments, or public-private partnership approvals.
375.12.2 Cross-border dashboards, maps, observability outputs, evidence packs, proof packs, public-safe summaries, digital twins, simulations, technical baselines, and public authority learning materials shall include limitation language where such misunderstanding is possible.
375.13 North America Interface Records.
375.13.1 The Corporation shall maintain North America Interface Records, including North America public authority interface purpose records, Canada interface coordination records with GCRI Canada, Mexico interface records, Caribbean interface records, Arctic interface records, Great Lakes / Atlantic / Pacific / Gulf / border / port / energy / water / food / public health / cyber / telecom / transportation / supply chain / disaster interface records, Cross-Border Public Authority Data Control records, cross-border privacy / AI / cyber / export-control / sanctions / controlled technology / public authority / Indigenous / protected knowledge / conflict-of-law review records, no-North-America-sovereign-authority records, no-treaty-authority records, no-intergovernmental-decision-authority records, no-cross-border-public-warning / emergency-command / procurement / public-finance / regulatory / sovereign-obligation-authority records, corrections, clarifications, restrictions, withdrawals, and archive records.
Section 376. Public Authority Data Contributions
376.1 Public Authority Data Contribution Purpose.
376.1.1 Public Authority Data Contributions shall be governed to ensure that any data, records, documents, maps, dashboards, telemetry, logs, public information, non-public information, source materials, public records, restricted materials, public health materials, emergency management materials, public safety materials, infrastructure materials, cyber materials, grant materials, procurement materials, public finance materials, regulatory materials, or other inputs contributed by public authorities are received, classified, used, retained, published, restricted, corrected, or deleted only according to lawful authority and recorded conditions.
376.1.2 Public Authority Data Contributions may support evidence literacy, methods literacy, observability, public-safe publication, public-good software, technical baselines, public authority learning, public-safe dashboards, public-safe maps, controlled-room review, and correctionability, but shall not by themselves constitute public authority endorsement, adoption, official finding, procurement approval, public finance approval, public warning, emergency command, certification, recognition, finance-readiness, or provider preference.
376.2 Authority Record Requirement.
376.2.1 Each material Public Authority Data Contribution shall have an Authority Record identifying the contributor, public authority, source authority, legal or institutional basis for contribution, permitted recipient, permitted purpose, limitations, confidentiality, public records status where applicable, and publication status.
376.2.2 Where authority is unclear, the Corporation shall restrict use until authority is clarified or decline the contribution.
376.3 Capacity Record Requirement.
376.3.1 Each material Public Authority Data Contribution shall include a Capacity Record identifying whether the contributor acts as official participant, delegated representative, data provider, observer, reviewer, public information source, personal-capacity participant, or other capacity.
376.3.2 Capacity shall determine whether the contribution may be attributed, used, published, mapped, summarized, transferred, or referenced.
376.4 Data Contribution Agreement Where Appropriate.
376.4.1 A Data Contribution Agreement or equivalent recorded instrument shall be used where contributions involve non-public data, restricted data, personal information, health-sensitive data, public authority restricted data, cyber-sensitive data, infrastructure-sensitive data, protected knowledge, controlled technology, confidential materials, grant materials, procurement materials, public finance materials, or materials requiring defined rights and obligations.
376.4.2 The agreement may address authority, scope, permitted use, prohibited use, access class, confidentiality, privacy, cybersecurity, AI-use restrictions, publication restrictions, transfer restrictions, retention, deletion, correction, withdrawal, attribution, non-attribution, audit, incident notification, and dispute resolution.
376.5 Dataset Description.
376.5.1 Public Authority Data Contributions shall include a dataset or source description sufficient to identify data type, source, date, version, coverage, format, fields, sensitivity, quality limits, known gaps, collection method where known, update status, public-safe status, and correction path.
376.5.2 Dataset descriptions shall not disclose restricted contents in public-facing records unless authorized and public-safe.
376.6 Permitted Use.
376.6.1 Permitted Use shall identify the specific purposes for which contributed data may be used, including internal review, evidence support, methods support, public authority learning, dashboard development, map development, public-safe summary, technical baseline development, software testing, controlled-room review, research, publication, correction, or archive.
376.6.2 Uses not expressly permitted shall be prohibited unless subsequently authorized.
376.7 Prohibited Use.
376.7.1 Prohibited Use shall identify uses not allowed, including unauthorized publication, unauthorized mapping, unauthorized AI training, unauthorized embeddings, unauthorized model improvement, unauthorized transfer, unauthorized commercial use, provider development, sponsor benefit, finance-readiness routing, recognition routing, certification-like use, procurement implication, public warning, emergency command, re-identification, linkage, or use beyond purpose.
376.7.2 Prohibited Use shall remain binding notwithstanding internal access, technical ability, public interest, sponsor request, provider request, public authority request from a different authority, or perceived usefulness.
376.8 Classification.
376.8.1 Public Authority Data Contributions shall be classified according to access class and sensitivity, including public, public-safe, internal, controlled, confidential, restricted, public authority, research, clean-room, data-room, evidence-room, no-download, community-protected, Tribal / Indigenous, finance-sensitive, cyber-sensitive, infrastructure-sensitive, health-sensitive, personal information, controlled technology, archived, or sealed.
376.8.2 Classification shall be reviewed before release, transfer, AI use, publication, dashboarding, mapping, or public-safe summarization.
376.9 Confidentiality.
376.9.1 Confidentiality terms shall be recorded where contributed data is non-public, sensitive, restricted, public authority confidential, procurement-sensitive, grant-sensitive, regulatory-sensitive, public health-sensitive, emergency-sensitive, cyber-sensitive, infrastructure-sensitive, finance-sensitive, or otherwise restricted.
376.9.2 Confidentiality terms shall be lawful, compatible with public records obligations where applicable, and not used to conceal misconduct, suppress required correction, or evade legal notice obligations.
376.10 AI-Use Restrictions.
376.10.1 Public Authority Data Contributions shall identify whether data may be used with AI systems, including AI-assisted review, classification, summarization, embeddings, retrieval, model evaluation, fine-tuning, training, model improvement, synthetic data generation, or agentic workflows.
376.10.2 Unless expressly authorized, Public Authority Data Contributions shall not be used for AI training, fine-tuning, model improvement, external embeddings, public AI tools, or agentic workflows with external tool access.
376.10.3 AI-use restrictions shall be reflected in access controls, documentation, workflow controls, and review records.
376.11 Publication Restrictions.
376.11.1 Public Authority Data Contributions shall identify whether the data may be published, summarized, quoted, mapped, visualized, included in dashboards, included in public-safe summaries, included in evidence packs, included in technical baselines, cited, or externally referenced.
376.11.2 Publication restrictions may require redaction, aggregation, delay, attribution, non-attribution, public authority review, public-safe review, no-download access, controlled annex, or denial of publication.
376.12 Retention and Deletion.
376.12.1 Public Authority Data Contributions shall identify retention period, archival status, legal hold requirements, public authority retention requirements, grant retention requirements, deletion requirements, secure disposal requirements, backup handling, and correction path.
376.12.2 Deletion shall not occur where legal hold, public authority retention requirement, audit requirement, correctionability, or evidence integrity requires retention, unless law requires deletion.
376.13 Transfer Restrictions.
376.13.1 Public Authority Data Contributions shall identify whether data may be transferred to GCRI Canada, GRF, GRA, consortiums, national companies, Project SPVs, providers, sponsors, universities, laboratories, public authorities, vendors, cloud providers, AI providers, controlled rooms, external reviewers, or other parties.
376.13.2 No transfer shall occur unless authority, permitted use, data rights, privacy, cybersecurity, public authority restrictions, protected knowledge safeguards, export-control, sanctions, controlled technology, and public-safe review support the transfer.
376.14 Public Records, FOIA, Sunshine, Open Meetings, Public Procurement, Grant, and Legal Hold Considerations.
376.14.1 Public Authority Data Contributions shall be reviewed for public records, FOIA, sunshine, open meetings, procurement records, grant records, public finance records, regulatory records, audit records, inspector general records, litigation hold, regulatory hold, and legal hold implications where applicable.
376.14.2 The Corporation shall not structure data contributions or controlled environments to evade lawful transparency, records, audit, procurement, or public authority obligations.
376.15 Public-Safe Review Before Release.
376.15.1 Public Authority Data Contributions shall receive public-safe review before any public or external release, including release through reports, dashboards, maps, datasets, software, repositories, technical baselines, public-safe summaries, media statements, Academy materials, public authority learning materials, or partner materials.
376.15.2 Public-safe review shall assess authority, classification, confidentiality, privacy, cyber sensitivity, infrastructure sensitivity, protected knowledge, public authority meaning, procurement implication, finance implication, public warning risk, emergency command risk, and correction path.
376.16 Withdrawal or Correction by Public Authority.
376.16.1 Public authorities may request withdrawal, correction, restriction, reclassification, non-attribution, or clarification of contributed data where permitted by law, agreement, or recorded terms.
376.16.2 The Corporation shall review such requests promptly and may implement correction, supersession, withdrawal, access restriction, public-safe clarification, controlled clarification, takedown, archive update, or denial with recorded rationale.
376.16.3 Withdrawal or correction shall preserve historical traceability where lawful and shall not erase records required for legal compliance, audit, evidence integrity, or correctionability.
376.17 Public Authority Data Contribution Records.
376.17.1 The Corporation shall maintain Public Authority Data Contribution Records, including contribution purpose records, Authority Records, Capacity Records, Data Contribution Agreements where appropriate, dataset descriptions, permitted use records, prohibited use records, classification records, confidentiality records, AI-use restriction records, publication restriction records, retention and deletion records, transfer restriction records, public records / FOIA / sunshine / open meetings / procurement / grant / legal hold consideration records, public-safe release review records, withdrawal or correction request records, corrections, restrictions, reclassifications, and archive records.
Section 377. Public Authority References, Names, Logos, Titles, Quotes, Attendance, Photographs, and Data Contribution Statements
377.1 Public Authority Reference Purpose.
377.1.1 Public Authority Reference governance shall ensure that every external or public use of public authority names, logos, seals, titles, quotes, attendance references, photographs, recordings, event references, data contribution statements, or participation descriptions is accurate, authorized, capacity-classified, permission-aware, public-safe, and non-misleading.
377.1.2 Public Authority References shall preserve public authority trust, public records discipline, non-endorsement, non-adoption, procurement neutrality, public finance neutrality, non-regulatory posture, non-public-warning posture, non-emergency-command posture, and the Corporation’s non-executing role.
377.2 Public Authority Name Use Approval.
377.2.1 Public authority name use shall be approved where the name is used in a publication, event material, website, social media post, press release, dashboard, map, dataset, software documentation, repository, technical baseline, public authority learning material, sponsor material, provider material, partner material, or media material.
377.2.2 Approval shall identify the public authority, permitted name form, context, duration, access class, permitted channels, limitation language, and whether public authority review is required before release.
377.2.3 Public authority name use shall not imply endorsement, adoption, funding approval, procurement approval, regulatory approval, public finance approval, public warning, emergency command, sovereign obligation, or public-private partnership.
377.3 Public Authority Logo Use Approval.
377.3.1 Public authority logos, seals, flags, insignia, crests, official emblems, program marks, and agency marks shall not be used without appropriate permission, legal authority, and public-safe review.
377.3.2 Logo use approval shall define exact mark, placement, size, context, duration, permitted channels, co-branding restrictions, disclaimer requirements, and removal requirements.
377.3.3 Public authority logos shall not be used in a manner that creates official endorsement, adoption, sponsorship, public authority approval, procurement approval, public finance approval, regulatory approval, public warning, emergency command, or public-private partnership implication unless expressly and lawfully authorized.
377.4 Public Authority Title Use Approval.
377.4.1 Public authority titles, offices, ranks, agency roles, program roles, and official designations shall be used only where accurate, current, permission-aware, and capacity-appropriate.
377.4.2 Title use shall identify whether the person participates in official, institutional, technical expert, observer, personal, academic, regulator-listening, public finance reader, emergency-management, public health, public safety, public works, data provider, reviewer, or other capacity.
377.4.3 Titles shall not be used to imply that a person binds a public authority, approves a publication, endorses the Corporation, or adopts Corporation materials unless supported by competent record.
377.5 Public Authority Quote Approval.
377.5.1 Public authority quotes shall be approved before use and shall be limited to the exact approved text, attribution, title, context, channel, duration, and purpose.
377.5.2 Quotes shall not be edited, excerpted, translated, displayed, captioned, or paired with visuals in a manner that expands meaning or implies broader public authority endorsement, adoption, funding approval, procurement approval, public finance approval, regulatory approval, public warning, emergency command, or sovereign obligation.
377.5.3 Quotes from personal-capacity participants shall not be presented as official statements.
377.6 Public Authority Attendance Reference Approval.
377.6.1 Public authority attendance references shall be approved where externally referenced and shall identify capacity, event, date, public authority, permission status, and limitation language.
377.6.2 Attendance references shall use narrow and accurate wording, including “attended,” “observed,” “participated in learning,” “joined as observer,” “joined in personal capacity,” “received briefing,” “reviewed as technical expert,” or other recorded capacity language.
377.6.3 Attendance shall not imply endorsement, adoption, approval, funding, procurement, regulation, public finance, public warning, emergency command, or official decision.
377.7 Public Authority Photograph, Recording, or Event Reference Approval.
377.7.1 Photographs, recordings, screenshots, video clips, event references, participant lists, agenda excerpts, venue references, and visual depictions involving public authorities shall require approval where external use may create public authority meaning.
377.7.2 Approval shall address consent, privacy, public records, security, attribution, non-attribution, public-safe framing, official-capacity risk, logo visibility, title use, and correction path.
377.7.3 Visual materials shall not be used to imply public authority endorsement, adoption, funding, procurement, public finance approval, regulation, public warning, emergency command, or public-private partnership.
377.8 Public Authority Data Contribution Statement Approval.
377.8.1 Public Authority Data Contribution Statements shall be approved before publication or external use.
377.8.2 Such statements shall accurately describe the nature of the contribution, source authority, public authority capacity, data class, permitted use, publication status, attribution permission, limitations, and whether the contributing authority reviewed or approved the statement.
377.8.3 Data contribution statements shall not imply that the public authority endorses, adopts, validates, verifies, funds, procures, regulates, warns through, commands through, certifies, recognizes, finances, rates, or approves Corporation outputs.
377.9 Official Capacity Language.
377.9.1 Official Capacity Language shall be used only where official participation is supported by competent record.
377.9.2 Official Capacity Language shall state the limited scope of official participation and shall not imply endorsement, adoption, approval, funding, procurement, public finance, regulatory position, public warning, emergency command, or sovereign obligation beyond the record.
377.10 Observer Capacity Language.
377.10.1 Observer Capacity Language shall state that the public authority or public-sector participant attended, observed, listened, or received information in a non-decisional capacity.
377.10.2 Observer Capacity Language shall be used wherever public authority attendance might otherwise be misunderstood as endorsement, adoption, approval, funding, procurement, regulation, public finance, public warning, emergency command, or official decision.
377.11 Personal Capacity Language.
377.11.1 Personal Capacity Language shall be used where a public official, public employee, public university actor, public laboratory actor, regulator, public finance actor, infrastructure operator employee, or other public-sector-affiliated person participates outside official authority.
377.11.2 Personal Capacity Language shall not be undermined by use of official logos, seals, titles, agency names, or visual framing that creates contrary implication.
377.12 Non-Attributable Participation Language.
377.12.1 Non-Attributable Participation Language shall be used where participant identity, affiliation, title, contribution, quote, comment, or attendance may not be publicly attributed because of confidentiality, public authority restriction, protected knowledge, privacy, security, community safeguards, or public-safe review.
377.12.2 Non-attributable participation may be described generically only where such description is permitted and not misleading.
377.13 Required Non-Endorsement Language.
377.13.1 Public Authority References shall include non-endorsement language where needed to prevent public authority overclaim.
377.13.2 Non-endorsement language shall state that public authority participation, attendance, reference, data contribution, quote, review, or learning interface does not imply endorsement, adoption, approval, funding, procurement, public finance approval, regulatory approval, public warning, emergency command, sovereign obligation, public-private partnership, certification, recognition, finance-readiness, rating, or provider preference.
377.14 No Public Authority Approval, Adoption, Funding, Procurement, Regulation, Public Finance, Public Warning, Emergency Command, Sovereign Obligation, or Public-Private Partnership by Reference.
377.14.1 No Public Authority Reference, including name use, logo use, title use, quote use, attendance reference, photograph, recording, data contribution statement, event reference, room participation, dashboard review, map review, public authority learning, or technical review, shall create or imply public authority approval, adoption, funding, procurement, regulation, public finance approval, public warning, emergency command, sovereign obligation, public-private partnership, official guidance, official standard, certification, recognition, finance-readiness, rating, or provider preference.
377.14.2 Any reference that creates such implication shall be revised, restricted, withdrawn, corrected, or clarified.
377.15 Correction of Misdescribed Public Authority References.
377.15.1 The Corporation shall correct misdescribed Public Authority References promptly upon discovery.
377.15.2 Correction may include revised language, removal of name or logo, quote correction, event-page correction, social media correction, dashboard correction, map correction, partner-material correction, public clarification, controlled clarification, public authority notice, takedown, or archive update.
377.16 Public Authority Reference Records.
377.16.1 The Corporation shall maintain Public Authority Reference Records, including reference purpose records, name-use approval records, logo-use approval records, title-use approval records, quote approval records, attendance reference approval records, photograph / recording / event reference approval records, data contribution statement approval records, official capacity language records, observer capacity language records, personal capacity language records, non-attributable participation language records, required non-endorsement language records, no-public-authority-approval / adoption / funding / procurement / regulation / public finance / public warning / emergency command / sovereign obligation / public-private partnership records, misdescription correction records, public authority notices, restrictions, and archive records.
Section 378. Public Authority Rooms, Controlled Rooms, Regulator-Listening Rooms, Public Finance Reader Rooms, and Emergency Learning Rooms
378.1 Public Authority Room Purpose.
378.1.1 Public Authority Rooms shall provide structured, lawful, capacity-classified, public-safe, non-executing environments for public authorities and public-sector participants to receive, review, discuss, or learn from evidence materials, public-safe summaries, methods, dashboards, maps, technical baselines, observability materials, data governance materials, AI governance materials, cyber materials, and public-good technical assets.
378.1.2 Public Authority Rooms shall not be used to create public authority decisions, public authority adoption, procurement approval, funding approval, regulatory approval, public finance approval, public warning, emergency command, sovereign obligation, public-private partnership, certification, recognition, finance-readiness, rating, or provider preference.
378.2 Controlled Room Purpose.
378.2.1 Controlled Rooms shall provide access-controlled environments for review of sensitive materials, including public authority data, cyber-sensitive data, infrastructure-sensitive data, health-sensitive data, finance-sensitive data, protected knowledge, controlled technology, non-public vulnerability materials, datasets, evidence packs, dashboards, maps, technical baselines, and public-safe publication materials.
378.2.2 Controlled Rooms shall be governed by defined purpose, admission criteria, access class, confidentiality terms, data / AI / cyber / privacy controls, no-download rules where appropriate, public authority boundary controls, finance and procurement boundary controls, public-safe publication controls, and closeout procedures.
378.3 Regulator-Listening Room Purpose.
378.3.1 Regulator-Listening Rooms shall provide non-decisional environments for regulators or regulatory staff to listen, learn, observe, ask questions, and understand public-benefit evidence, methods, technical baselines, public-good software, data governance, AI governance, cyber governance, observability, and public-safe publication issues.
378.3.2 Regulator-Listening Rooms shall not create regulatory guidance, regulatory approval, safe harbor, permit, compliance determination, enforcement position, waiver, policy adoption, public authority endorsement, or official decision.
378.4 Public Finance Reader Room Purpose.
378.4.1 Public Finance Reader Rooms shall provide non-approval environments for public finance, budget, treasury, grant, tax credit, MDB / DFI, development finance, guarantee, public credit, municipal finance, sovereign finance, or fiscal actors to review materials for learning, diligence literacy, evidence literacy, technical literacy, observability literacy, and public-safe decision-support literacy.
378.4.2 Public Finance Reader Rooms shall not create grant approval, budget allocation, appropriation, public finance approval, MDB / DFI approval, public guarantee, public credit, tax credit approval, sovereign obligation, capital commitment, investment advice, finance-readiness, rating, or GRA finance-readiness determination.
378.5 Emergency Learning Room Purpose.
378.5.1 Emergency Learning Rooms shall provide non-command environments for emergency-management, public safety, public health, public works, public infrastructure, cyber, telecom, energy, water, food, transportation, and disaster-resilience actors to participate in learning, simulation, tabletop exercises, after-action learning, dashboard review, map review, evidence literacy, methods literacy, observability literacy, and public-safe decision-support literacy.
378.5.2 Emergency Learning Rooms shall not create incident command, dispatch authority, evacuation authority, emergency alert authority, official public warning, public health order, safety command, operational resource direction, or substitution for competent public authorities.
378.6 Room Charter.
378.6.1 Each material Public Authority Room, Controlled Room, Regulator-Listening Room, Public Finance Reader Room, or Emergency Learning Room shall have a Room Charter or equivalent record identifying purpose, sponsor if any, host if any, owner, custodian, participants, access class, materials, permitted uses, prohibited uses, confidentiality, no-download rules, AI-use restrictions, publication restrictions, public authority boundaries, finance boundaries, procurement boundaries, competition and antitrust controls, public-safe publication controls, closeout, and correction path.
378.6.2 A Room Charter shall not create public authority delegation, endorsement, adoption, procurement approval, funding approval, regulatory approval, public finance approval, public warning, emergency command, sovereign obligation, public-private partnership, certification, recognition, finance-readiness, or provider preference.
378.7 Admission Criteria.
378.7.1 Admission criteria shall be defined before room access is granted and shall consider participant capacity, purpose, authority, need to know, confidentiality, conflicts, competition concerns, public authority constraints, procurement sensitivity, public finance sensitivity, data sensitivity, cyber sensitivity, infrastructure sensitivity, protected knowledge, and public-safe risk.
378.7.2 Admission shall not be sold, traded, promised, or used to create provider preference, sponsor influence, procurement advantage, public authority access advantage, finance-readiness advantage, recognition advantage, certification advantage, or outcome purchase.
378.8 Capacity Classification.
378.8.1 Each room participant shall be capacity-classified, including official participant, delegated representative, observer, regulator-listening participant, public finance reader, emergency-management participant, public infrastructure operator participant, data provider, reviewer, technical expert, controlled-room participant, personal-capacity participant, non-attributable participant, or other applicable role.
378.8.2 Capacity classification shall govern access, attribution, permitted statements, public references, confidentiality, publication rights, and correction path.
378.9 Confidentiality Terms.
378.9.1 Confidentiality terms shall be established where rooms include non-public, restricted, confidential, public authority, cyber-sensitive, infrastructure-sensitive, finance-sensitive, health-sensitive, personal, controlled technology, protected knowledge, or other sensitive materials.
378.9.2 Confidentiality terms may include non-disclosure, no-download, no-copying, no-screenshot, no-recording, no-AI-use, no-redistribution, non-attribution, controlled-output review, access logging, and closeout obligations.
378.9.3 Confidentiality shall not be used to conceal misconduct, suppress required correction, evade legal notice, or avoid public authority records obligations.
378.10 Public Records and Public Sector Constraints Review.
378.10.1 Rooms involving public authorities shall be reviewed for public records, FOIA, sunshine, open meetings, audit, procurement, grant, public finance, regulatory, inspector general, legal hold, confidentiality, and public sector ethics constraints where applicable.
378.10.2 The Corporation shall not design rooms to evade lawful public authority transparency, records, audit, procurement, or accountability obligations.
378.11 Data / AI / Cyber / Privacy Controls.
378.11.1 Rooms shall implement data / AI / cyber / privacy controls appropriate to materials and access class, including data minimization, purpose limitation, access controls, AI-use restrictions, no-training restrictions, embedding restrictions, logging where feasible, secure transfer, secure storage, output review, incident response, and deletion or return where required.
378.11.2 Rooms involving public authority data, personal information, health-sensitive data, cyber-sensitive data, infrastructure-sensitive data, protected knowledge, controlled technology, or non-public vulnerabilities shall receive heightened review.
378.12 Competition and Antitrust Controls.
378.12.1 Rooms involving providers, sponsors, vendors, competitors, public authorities, procurement actors, utilities, infrastructure operators, national companies, Project SPVs, or market participants shall be reviewed for competition, antitrust, procurement integrity, market allocation, bid coordination, commercially sensitive information, provider preference, and sponsor influence risks.
378.12.2 Rooms shall not be used to exchange competitively sensitive information, allocate markets, coordinate bids, influence procurement unlawfully, create preferred-provider status, or disadvantage non-participants.
378.13 Public Authority Boundary Controls.
378.13.1 Rooms shall include public authority boundary controls sufficient to prevent room participation from being understood as endorsement, adoption, approval, funding, procurement, regulation, public finance approval, public warning, emergency command, sovereign obligation, or public-private partnership.
378.13.2 Public authority boundary controls may include capacity labels, opening statements, participant acknowledgments, limitation notices, non-endorsement language, controlled notes, and publication restrictions.
378.14 Finance and Procurement Boundary Controls.
378.14.1 Rooms involving capital readers, public finance readers, grants, procurement actors, providers, sponsors, national companies, Project SPVs, or enterprise actors shall include finance and procurement boundary controls.
378.14.2 Such controls shall state that room participation does not create finance-readiness, investment advice, lending approval, insurance approval, rating, public finance approval, grant approval, procurement approval, provider qualification, preferred-provider status, public-private partnership approval, or capital commitment.
378.15 Public-Safe Publication Controls.
378.15.1 No room material, transcript, notes, dashboard, map, participant list, quote, recording, screenshot, output, summary, or conclusion shall be published or externally referenced without public-safe publication review and required permissions.
378.15.2 Public-safe outputs from rooms may require aggregation, redaction, non-attribution, controlled annexes, public authority review, protected knowledge review, cyber-sensitive review, infrastructure-sensitive review, finance-boundary review, procurement-boundary review, and correction path.
378.16 Room Closeout.
378.16.1 Room closeout shall address access termination, data return, deletion, archival, correction path, output review, participant obligations, public-safe summaries, unresolved issues, incident review, and records retention.
378.16.2 Room closeout shall not release participants from continuing confidentiality, protected knowledge, data use, AI-use, no-download, non-attribution, or public-safe obligations.
378.17 No Room Participation as Endorsement, Adoption, Approval, Funding, Procurement, Public Finance, Regulatory Guidance, Public Warning, Emergency Command, or Sovereign Obligation.
378.17.1 Participation in any Public Authority Room, Controlled Room, Regulator-Listening Room, Public Finance Reader Room, Emergency Learning Room, data room, evidence room, clean room, no-download room, simulation room, or related room shall not constitute endorsement, adoption, approval, funding, procurement approval, public finance approval, regulatory guidance, public warning, emergency command, sovereign obligation, public-private partnership, certification, recognition, finance-readiness, rating, provider preference, or execution authority.
378.17.2 Any contrary statement or implication shall be corrected, clarified, restricted, or withdrawn.
378.18 Public Authority Room Records.
378.18.1 The Corporation shall maintain Public Authority Room Records, including Public Authority Room purpose records, Controlled Room purpose records, Regulator-Listening Room purpose records, Public Finance Reader Room purpose records, Emergency Learning Room purpose records, Room Charters, admission criteria records, capacity classification records, confidentiality records, public records and public sector constraints review records, data / AI / cyber / privacy control records, competition and antitrust control records, public authority boundary control records, finance and procurement boundary control records, public-safe publication control records, room closeout records, no-room-participation-as-endorsement / adoption / approval / funding / procurement / public finance / regulatory guidance / public warning / emergency command / sovereign obligation records, corrections, restrictions, and archive records.
Section 379. Public Grants, Cooperative Agreements, Government Funding, Public Support, and No Public Authority Capture
379.1 Public Grant Purpose.
379.1.1 Public Grant governance shall ensure that any grant, award, subsidy, contribution, public support, or government funding received by the Corporation is accepted, administered, reported, and publicly described in a manner consistent with law, the Corporation’s nonprofit public-benefit purposes, public-good independence, evidence integrity, methods integrity, research integrity, publication independence, correctionability, public authority boundaries, procurement neutrality, provider neutrality, sponsor non-control, and non-execution.
379.1.2 Public grants may support research, evidence literacy, methods development, observability, ontology, public-good software, open technical baselines, public authority learning, public-safe publication, Academy materials, community safeguards, public-safe dashboards, public-safe maps, or other mission-compatible activities only within the approved scope and applicable restrictions.
379.1.3 Public grant receipt shall not convert the Corporation into a public authority, public agent, procurement body, regulator, public finance body, public warning authority, emergency command body, certification body, recognition body, finance-readiness body, provider-selection body, or execution body.
379.2 Cooperative Agreement Purpose.
379.2.1 Cooperative agreements with public authorities shall be reviewed for substantial involvement, public authority oversight, public records, procurement rules, grant compliance, IP rights, data rights, publication rights, public authority data restrictions, privacy, cybersecurity, controlled technology, export-control, sanctions, public-safe publication, conflicts, and role separation.
379.2.2 Cooperative agreement involvement shall not be described as public authority endorsement, adoption, procurement approval, public finance approval, regulatory approval, public warning, emergency command, sovereign obligation, certification, recognition, finance-readiness, or provider preference unless a competent record expressly supports the precise statement.
379.3 Government Funding Review.
379.3.1 Government Funding Review shall be conducted before acceptance of material public funding to assess lawful authority, charitable compatibility, mission alignment, restricted purpose, reporting obligations, audit obligations, public records implications, lobbying restrictions, political activity restrictions, procurement restrictions, conflicts, public authority influence, publication rights, correction rights, data rights, IP rights, public-safe publication, and independence.
379.3.2 Government funding shall not be accepted where it would give a public authority improper control over evidence, methods, findings, publications, corrections, public authority access, Nexus interface outputs, recognition, finance-readiness, certification, procurement outcomes, provider status, or public-safe framing.
379.4 Federal Grant Review.
379.4.1 Federal Grant Review shall assess federal award terms, allowable costs, reporting obligations, audit requirements, data rights, IP rights, publication rights, acknowledgment requirements, lobbying restrictions, political activity restrictions, procurement rules, subaward rules, human-subjects obligations, privacy, cybersecurity, controlled unclassified information where applicable, export-control, sanctions, national security sensitivity, and public-safe publication.
379.4.2 Federal grant acknowledgments shall not imply federal endorsement, federal approval of findings, federal certification, federal recognition, federal finance-readiness, federal procurement approval, public warning, emergency command, public-private partnership, or federal sovereign obligation.
379.5 State Grant Review.
379.5.1 State Grant Review shall assess state award terms, allowable costs, reporting obligations, audit requirements, data rights, IP rights, publication rights, acknowledgment requirements, lobbying restrictions, procurement rules, subaward rules, public records obligations, state privacy, AI, cybersecurity, public health, emergency management, infrastructure rules, and public-safe publication.
379.5.2 State grant acknowledgments shall not imply state endorsement, state approval of findings, state procurement approval, state public finance approval, state regulation, public warning, emergency command, certification, recognition, finance-readiness, or sovereign obligation.
379.6 Territorial Grant Review.
379.6.1 Territorial Grant Review shall assess territorial award terms, allowable costs, reporting obligations, audit requirements, data rights, IP rights, publication rights, acknowledgment requirements, public records obligations, procurement rules, public finance implications, privacy, cybersecurity, public health, emergency management, infrastructure, language access, accessibility, disaster resilience, and public-safe publication.
379.6.2 Territorial grant acknowledgments shall not imply territorial endorsement, adoption, procurement approval, funding approval beyond the award, public finance approval, public warning, emergency command, certification, recognition, finance-readiness, public-private partnership, or sovereign obligation.
379.7 Local Grant Review.
379.7.1 Local Grant Review shall assess local award terms, allowable costs, reporting obligations, audit requirements, data rights, IP rights, publication rights, acknowledgment rules, public records, open meetings, procurement rules, public finance implications, privacy, cybersecurity, public health, emergency management, public works, infrastructure, community safeguards, and public-safe publication.
379.7.2 Local grant acknowledgments shall not imply local endorsement, adoption, procurement approval, public finance approval, regulation, public warning, emergency command, certification, recognition, finance-readiness, public-private partnership, or official local action beyond the award record.
379.8 Tribal or Indigenous Government Funding Review Where Applicable.
379.8.1 Tribal or Indigenous Government Funding Review shall be conducted where funding, support, subaward, sponsorship, contribution, cooperative arrangement, or resource support is received from or in coordination with a Tribal or Indigenous government or Indigenous governance body.
379.8.2 Review shall address authority, sovereignty, protocols, consent, non-consent, attribution, non-attribution, data rights, knowledge safeguards, publication rights, public-safe mapping, AI-use restrictions, community safeguards, reporting obligations, and non-execution.
379.8.3 Such funding or support shall not imply Tribal or Indigenous endorsement, adoption, waiver of sovereignty, data transfer permission beyond record, knowledge-use permission beyond record, procurement approval, public warning, emergency command, recognition, finance-readiness, certification, or sovereign obligation.
379.9 Public Support Acceptance Test.
379.9.1 The Corporation may accept public support only where the support is lawful, mission-compatible, public-benefit-aligned, independence-preserving, records-supported, conflict-managed, publication-safe, and consistent with nonprofit status and this Bylaw.
379.9.2 Public support shall be rejected, narrowed, conditioned, or escalated where it would create public authority capture, sponsor-like control, provider preference, procurement advantage, finance-readiness implication, certification implication, recognition implication, improper public authority access, publication suppression, correction suppression, protected knowledge risk, data misuse, or role confusion.
379.10 Grant Compliance.
379.10.1 The Corporation shall comply with lawful grant and cooperative agreement requirements, including scope of work, budgets, allowable costs, reporting, records retention, audits, subrecipient monitoring where applicable, procurement obligations where applicable, data security, privacy, publication conditions, IP conditions, acknowledgment rules, and closeout requirements.
379.10.2 Grant compliance shall be administered without compromising evidence integrity, methods integrity, research integrity, public-safe publication, correctionability, independence, or role separation.
379.11 Public Funding Restrictions.
379.11.1 Public funding restrictions shall be recorded and followed, including restrictions on use of funds, lobbying, political activity, procurement, subawards, cost sharing, matching, data use, publication, intellectual property, export-control, sanctions, controlled technology, confidentiality, and public authority data.
379.11.2 Restrictions shall not be interpreted to permit unlawful suppression of material correction, concealment of conflicts, provider favoritism, public authority overclaim, finance overclaim, certification overclaim, recognition overclaim, or procurement overclaim.
379.12 Public Reporting Obligations.
379.12.1 Public Reporting Obligations shall be satisfied accurately, timely, and consistently with public-safe publication, confidentiality, privacy, cybersecurity, protected knowledge, public authority data restrictions, and legal obligations.
379.12.2 Public reports shall distinguish grant performance reporting, public-benefit reporting, financial reporting, research reporting, technical reporting, public-safe summaries, and publication outputs.
379.13 Audit and Record Requirements.
379.13.1 Public grants and government funding shall be subject to audit and record requirements according to applicable law, award terms, internal controls, retention schedules, public authority restrictions, financial controls, and governance requirements.
379.13.2 Audit and records shall preserve source support, expenditure records, deliverables, approvals, conflicts, publication reviews, data rights, IP rights, public-safe review, correction records, and closeout materials.
379.14 Public Authority Data and Publication Terms.
379.14.1 Public funding instruments shall be reviewed for public authority data and publication terms, including rights to use, rights to publish, rights to restrict, rights to review, attribution requirements, non-attribution requirements, open data requirements, privacy obligations, cybersecurity obligations, public-safe publication, and correction rights.
379.14.2 Publication terms shall not be accepted if they require the Corporation to publish inaccurate, misleading, unsafe, privacy-defective, cyber-defective, protected-knowledge-defective, public-authority-boundary-defective, finance-boundary-defective, certification-boundary-defective, recognition-boundary-defective, procurement-boundary-defective, or non-correctionable materials.
379.15 No Public Funder Control Over Evidence, Methods, Findings, Publications, Public Authority Access, Nexus Interface Outputs, Recognition, Finance-Readiness, Certification, or Provider Status.
379.15.1 No public funder, grantor, public authority, public finance body, procurement body, regulator, public official, public employee, or government sponsor shall control the Corporation’s evidence conclusions, methods, findings, publications, corrections, public authority access classifications, Nexus interface outputs, public-good technical assets, open technical baselines, GRF-related inputs, GRA-related inputs, recognition, finance-readiness, certification, procurement status, provider status, or public-safe framing.
379.15.2 Public funders may impose lawful grant scope, reporting, budget, audit, and compliance requirements, but shall not purchase findings, suppress corrections, dictate evidence outcomes, create provider preference, or convert the Corporation into an execution body.
379.16 No Public Grant as Public Authority Delegation.
379.16.1 Receipt of a public grant, cooperative agreement, government funding, public support, in-kind public support, public authority-hosted support, or public authority participation shall not constitute delegation of public authority powers to the Corporation.
379.16.2 The Corporation shall not treat grant funding as authority to regulate, procure, fund third parties, issue public warnings, command emergencies, approve public finance, certify, recognize, provide finance-readiness, approve providers, or execute public authority functions.
379.17 Public Grant and Government Funding Records.
379.17.1 The Corporation shall maintain Public Grant and Government Funding Records, including public grant purpose records, cooperative agreement purpose records, Government Funding Review records, Federal Grant Review records, State Grant Review records, Territorial Grant Review records, Local Grant Review records, Tribal or Indigenous Government Funding Review records where applicable, Public Support Acceptance Test records, grant compliance records, public funding restriction records, public reporting obligation records, audit and record requirement records, public authority data and publication term records, no-public-funder-control records, no-public-grant-as-public-authority-delegation records, corrections, clarifications, restrictions, closeout records, and archive records.
Section 380. Lobbying, Political Activity, Government Ethics, Gifts, Honoraria, Travel, and Public Official Interaction
380.1 Lobbying and Political Activity Boundary Purpose.
380.1.1 Lobbying, political activity, government ethics, gifts, honoraria, travel, sponsored attendance, procurement integrity, revolving-door, public official conflict, and public official interaction governance shall preserve the Corporation’s nonprofit, nonpartisan, 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 character.
380.1.2 The Corporation may lawfully educate, inform, brief, convene, publish, conduct research, support public authority learning, support technical literacy, support evidence literacy, support public-safe decision-support literacy, and provide nonpartisan public-benefit materials, provided that such activity does not become unauthorized lobbying, prohibited political campaign intervention, procurement influence, public finance influence, improper gift, improper inducement, official-action purchase, public authority capture, or misuse of public office.
380.1.3 Public official interaction shall be structured to protect ethics compliance, public trust, transparency where required, public records integrity, procurement neutrality, public finance neutrality, sponsor non-control, provider neutrality, nonpartisanship, correctionability, and accurate capacity classification.
380.2 Federal Lobbying Review Where Applicable.
380.2.1 Federal Lobbying Review shall be required where communications, publications, meetings, briefings, testimony, letters, policy materials, appropriations references, grant references, procurement references, agency references, legislative references, regulatory references, or public authority learning materials may constitute lobbying, lobbying support, grassroots lobbying, appropriations advocacy, procurement advocacy, regulatory advocacy, or reportable federal contact.
380.2.2 Federal Lobbying Review shall assess charitable-law limits, registration requirements, reporting requirements, grant restrictions, federal award restrictions, public authority ethics, procurement integrity, political activity restrictions, and whether the communication is nonpartisan research, technical assistance, public-benefit education, or advocacy.
380.2.3 No federal communication shall be characterized internally or externally as merely technical if its substance seeks official legislative, appropriations, regulatory, procurement, grant, public finance, or agency action requiring lobbying review.
380.3 State Lobbying Review Where Applicable.
380.3.1 State Lobbying Review shall be required where Corporation activity may involve state legislative advocacy, state agency advocacy, state appropriations advocacy, state regulatory advocacy, state procurement advocacy, state grant advocacy, state budget advocacy, or state public finance advocacy.
380.3.2 State Lobbying Review shall be jurisdiction-specific and shall not assume that federal classifications, another state’s classifications, or general nonprofit educational rules apply uniformly.
380.3.3 State communications shall be structured to preserve the Corporation’s nonpartisan public-benefit education role and to avoid unauthorized lobbying, reportable lobbying, procurement influence, public finance influence, or political activity where not approved.
380.4 Territorial and Local Lobbying Review Where Applicable.
380.4.1 Territorial and Local Lobbying Review shall be required where communications with territorial, county, municipal, metropolitan, utility, port, airport, public works, public health, public safety, emergency management, procurement, grant, budget, public finance, or regulatory actors may constitute lobbying, advocacy, procurement influence, public finance influence, or reportable official contact.
380.4.2 Review shall account for territorial and local law, ethics rules, public records rules, open meetings rules, procurement rules, grant rules, gift rules, language access, accessibility, community safeguards, and public-safe publication.
380.5 Lobbying Registration Review.
380.5.1 The Corporation shall conduct Lobbying Registration Review where activity, contacts, compensation, expenditures, subject matter, public official interaction, legislative action, regulatory action, procurement action, public finance action, grant action, or public authority action may trigger registration, reporting, disclosure, or internal tracking requirements.
380.5.2 No director, officer, employee, contractor, fellow, advisor, volunteer, sponsor, provider, partner, or other participant shall engage in lobbying on behalf of the Corporation unless authorized and reviewed.
380.5.3 Lobbying registration decisions shall be recorded and periodically reviewed where activities change.
380.6 Political Campaign Activity Controls.
380.6.1 The Corporation shall not participate or intervene in any political campaign on behalf of or in opposition to any candidate for public office where prohibited by applicable nonprofit law.
380.6.2 Corporation resources, publications, events, public authority learning materials, dashboards, maps, repositories, mailing lists, staff time, facilities, logos, social media channels, and public-good technical assets shall not be used for prohibited campaign activity.
380.6.3 Candidate appearances, public official appearances during campaigns, election-season events, policy forums, public authority learning sessions, and media statements shall be reviewed to preserve nonpartisanship, equal treatment where required, public-safe framing, and no campaign intervention.
380.7 Nonpartisan Public-Benefit Research and Education Controls.
380.7.1 The Corporation may conduct and publish nonpartisan public-benefit research and education concerning systemic risk, resilience, observability, evidence, methods, data governance, AI governance, cybersecurity, public-good technical assets, open technical baselines, public-safe dashboards, maps, and Nexus architecture.
380.7.2 Nonpartisan education shall be factual, evidence-supported, balanced where appropriate, limitation-aware, public-safe, correctionable, and not structured as campaign intervention, candidate support, party support, procurement influence, finance solicitation, regulatory evasion, or official-action inducement.
380.7.3 Nonpartisan materials shall distinguish public-benefit learning from lobbying, political advocacy, procurement recommendation, public finance recommendation, regulatory guidance, certification, recognition, finance-readiness, public warning, or emergency command.
380.8 Government Ethics Rules.
380.8.1 Public official interactions shall be reviewed for applicable government ethics rules, including gifts, meals, travel, honoraria, outside activities, conflicts of interest, appearance of impropriety, misuse of office, preferential treatment, procurement integrity, post-employment restrictions, confidential information, and official title use.
380.8.2 The Corporation shall not request, encourage, reward, or appear to reward any public official, public employee, regulator, procurement actor, grant actor, public finance actor, public infrastructure operator, emergency-management actor, public health actor, or public safety actor for official action.
380.8.3 Where ethics rules are uncertain, the Corporation shall apply the most restrictive reasonable approach or obtain competent review.
380.9 Gifts to Public Officials.
380.9.1 Gifts to public officials, public employees, regulators, procurement personnel, public finance personnel, grant personnel, emergency-management personnel, public health personnel, public safety personnel, public works personnel, and public infrastructure operator representatives shall be prohibited unless reviewed and lawful.
380.9.2 Gifts include meals, beverages, entertainment, tickets, travel, lodging, honoraria, awards, discounts, services, data access, software access, conference access, sponsored attendance, subscriptions, equipment, cloud credits, technical services, or other things of value.
380.9.3 No gift shall be offered, provided, solicited, or used to obtain public authority access, endorsement, adoption, procurement advantage, funding advantage, regulatory advantage, public finance advantage, public warning implication, emergency-management influence, or official action.
380.10 Honoraria.
380.10.1 Honoraria to public officials, public employees, public university actors, public laboratory actors, regulators, public finance actors, or other public-sector-affiliated persons shall be reviewed for lawfulness, employer rules, ethics restrictions, grant restrictions, procurement restrictions, conflict risk, and public-safe interpretation.
380.10.2 Honoraria shall not be used to purchase participation, endorsement, adoption, public authority access, procurement advantage, funding advantage, regulatory advantage, public finance advantage, or favorable statements.
380.10.3 Honoraria decisions shall be recorded where material.
380.11 Travel Support.
380.11.1 Travel support for public officials or public-sector-affiliated persons shall be reviewed for ethics, gifts, procurement integrity, public records, funding restrictions, sponsor influence, provider influence, and appearance concerns.
380.11.2 Travel support shall be limited to lawful, mission-compatible, documented purposes and shall not be conditioned on endorsement, adoption, public authority approval, procurement action, funding action, regulatory action, public finance action, public warning, emergency command, or public statement.
380.12 Sponsored Attendance.
380.12.1 Sponsored Attendance shall be reviewed where the Corporation, a sponsor, donor, funder, provider, host, partner, or other third party supports public official attendance at events, workshops, rooms, trainings, briefings, simulations, or public authority learning sessions.
380.12.2 Sponsored Attendance shall not create public authority access purchase, preferential treatment, provider preference, procurement advantage, sponsor influence, funder influence, endorsement, adoption, funding approval, regulatory approval, or public finance approval.
380.12.3 Sponsored Attendance shall be disclosed or restricted where required by law, policy, ethics rules, grant terms, or public-safe publication.
380.13 Procurement Integrity.
380.13.1 Public official interactions shall be reviewed for procurement integrity where procurement personnel, vendors, providers, sponsors, national companies, Project SPVs, bidders, public authorities, technical baselines, dashboards, maps, software, evidence packs, or procurement-relevant information are involved.
380.13.2 The Corporation shall not facilitate bid coordination, unequal access to procurement-sensitive information, preferred-provider status, procurement scoring, vendor selection, public contract advantage, procurement advocacy, or procurement approval unless separately and lawfully authorized, which shall not be presumed.
380.13.3 Procurement-sensitive information shall be access-controlled and shall not be used for sponsor benefit, provider advantage, capital-reader advantage, or public claims.
380.14 Revolving-Door Considerations.
380.14.1 The Corporation shall review interactions, hiring, contracting, advisory roles, fellowship roles, board roles, committee roles, consulting roles, and paid engagements involving current or former public officials, public employees, regulators, procurement personnel, grant personnel, public finance personnel, public infrastructure personnel, emergency-management personnel, public health personnel, or public safety personnel for post-employment, cooling-off, conflict, confidentiality, procurement integrity, and appearance issues.
380.14.2 No current or former public-sector actor shall be engaged to exploit confidential information, obtain improper access, influence procurement, influence grants, influence regulation, influence public finance, imply endorsement, or create public authority overclaim.
380.15 Public Official Conflict Review.
380.15.1 Public Official Conflict Review shall be conducted where a public official or public employee participates, speaks, reviews, contributes data, receives support, enters a room, joins a committee, advises, consults, contracts, or appears in Corporation materials in a manner that may create actual, potential, or apparent conflict.
380.15.2 Conflict review shall consider official duties, procurement role, regulatory role, grant role, public finance role, public authority data access, sponsor ties, provider ties, financial interests, family interests, employment interests, political interests, and public-safe interpretation.
380.16 Public-Safe Meeting Notes.
380.16.1 Meeting notes involving public officials or public authorities shall be factual, capacity-classified, non-misleading, access-controlled where appropriate, and reviewed for confidentiality, public records, public-safe publication, public authority boundaries, procurement sensitivity, public finance sensitivity, regulatory sensitivity, protected knowledge, cyber sensitivity, infrastructure sensitivity, and correctionability.
380.16.2 Meeting notes shall not characterize public official silence, questions, comments, attendance, or informal reactions as endorsement, adoption, approval, funding support, procurement support, regulatory position, public finance approval, public warning, emergency command, or official decision.
380.17 Lobbying, Political Activity, Government Ethics, and Public Official Interaction Records.
380.17.1 The Corporation shall maintain Lobbying, Political Activity, Government Ethics, and Public Official Interaction Records, including lobbying and political activity boundary purpose records, federal lobbying review records, state lobbying review records, territorial and local lobbying review records, lobbying registration review records, political campaign activity control records, nonpartisan public-benefit research and education control records, government ethics records, gift records, honoraria records, travel support records, sponsored attendance records, procurement integrity records, revolving-door review records, public official conflict review records, public-safe meeting notes, corrections, restrictions, disclosures, recusals, and archive records.
Section 381. Public Records, FOIA, Sunshine Laws, Open Meetings, Confidentiality, Privilege, and Controlled Disclosure
381.1 Public Records Purpose.
381.1.1 Public Records governance shall ensure that the Corporation’s interactions with public authorities, public officials, public employees, public infrastructure operators, public finance actors, regulators, grantors, procurement bodies, emergency-management actors, public health actors, public safety actors, public universities, public laboratories, Tribal / Indigenous governments, and other public-sector actors are managed with appropriate respect for public records, FOIA, sunshine laws, open meetings, confidentiality, privilege, work product, controlled disclosure, and public-safe redaction.
381.1.2 Public Records governance shall preserve lawful transparency where required, lawful confidentiality where permitted or required, public-safe publication, privacy, cybersecurity, infrastructure protection, protected knowledge safeguards, correctionability, and the Corporation’s legal separateness as a private nonprofit entity except where law provides otherwise.
381.2 FOIA Considerations.
381.2.1 Federal FOIA considerations shall be reviewed where Corporation materials are provided to, received from, created with, funded by, relied upon by, or held by a federal public authority in a manner that may affect public disclosure, confidentiality, public records status, controlled unclassified information, trade secrets, personal information, privileged material, cyber-sensitive information, infrastructure-sensitive information, or protected knowledge.
381.2.2 The Corporation shall label, classify, and transmit materials in a manner that accurately reflects confidentiality, public-safe status, data rights, public authority restrictions, and disclosure sensitivity, without making unsupported claims of exemption or confidentiality.
381.3 State Public Records Considerations.
381.3.1 State public records considerations shall be reviewed where Corporation materials are exchanged with state public authorities, state universities, state laboratories, state regulators, state procurement bodies, state grantors, state public finance actors, or state infrastructure actors.
381.3.2 State public records treatment shall be jurisdiction-specific and shall account for confidentiality, exemptions, procurement sensitivity, public health sensitivity, public safety sensitivity, cyber sensitivity, infrastructure sensitivity, privacy, trade secret, protected knowledge, and public-safe publication.
381.4 Sunshine and Open Meetings Considerations.
381.4.1 Sunshine and open meetings considerations shall be reviewed where public authority participants, boards, commissions, councils, committees, public university bodies, public infrastructure bodies, or multi-member public bodies participate in Corporation meetings, rooms, workshops, briefings, simulations, public authority learning sessions, or publication reviews.
381.4.2 The Corporation shall not structure meetings, controlled rooms, evidence rooms, data rooms, or communications to evade lawful open meetings, sunshine, notice, agenda, minutes, or public access requirements applicable to public authorities.
381.5 Public Authority Confidentiality.
381.5.1 Public Authority Confidentiality shall be recorded where public authorities provide non-public, confidential, restricted, sensitive, procurement-sensitive, grant-sensitive, public finance-sensitive, regulatory-sensitive, public health-sensitive, public safety-sensitive, cyber-sensitive, infrastructure-sensitive, personnel-sensitive, legally sensitive, or protected materials.
381.5.2 Confidentiality commitments shall be lawful, specific, records-based, consistent with public records obligations where applicable, and subject to public-safe correction, legal notice, incident response, and records retention obligations.
381.6 Privilege Protection.
381.6.1 Privileged materials shall be protected from unauthorized disclosure, waiver, public release, AI processing, repository exposure, dashboard inclusion, map inclusion, external sharing, or uncontrolled room access.
381.6.2 Privilege protection may apply to attorney-client communications, legal advice, regulatory strategy, litigation-sensitive materials, internal investigations, incident response legal work, and other privileged communications.
381.6.3 Privilege shall be asserted or preserved only where legally supportable and not as a substitute for public-safe correction or lawful disclosure obligations.
381.7 Work Product Protection.
381.7.1 Work Product Protection shall apply to materials prepared in anticipation of litigation, enforcement, regulatory inquiry, incident response, investigation, dispute, or legal strategy where applicable.
381.7.2 Work product shall be access-controlled, labeled where appropriate, and reviewed before disclosure, publication, external sharing, public authority transmission, AI processing, or repository inclusion.
381.8 Trade Secret, Commercially Sensitive, Cyber-Sensitive, Infrastructure-Sensitive, Public Authority, Personal, Health-Sensitive, Finance-Sensitive, Community-Protected, Tribal / Indigenous, and Protected Knowledge Materials.
381.8.1 Materials containing trade secrets, commercially sensitive information, cyber-sensitive information, infrastructure-sensitive information, public authority restricted information, personal information, sensitive personal information, health-sensitive data, finance-sensitive data, community-protected data, Tribal / Indigenous data, Indigenous knowledge, local knowledge, territorial knowledge, cultural knowledge, environmental knowledge, sacred knowledge, ecological knowledge, or protected knowledge shall be classified and protected before disclosure or publication.
381.8.2 Such materials shall not be disclosed, summarized, mapped, visualized, trained on, embedded, transferred, published, or externally shared without authority, access control, public-safe review, and required safeguards.
381.9 Controlled Disclosure.
381.9.1 Controlled Disclosure shall mean release of materials to defined recipients under defined conditions, access class, purpose limitation, confidentiality, no-download terms where applicable, AI-use restrictions, transfer restrictions, publication restrictions, retention rules, deletion rules, and correction pathways.
381.9.2 Controlled Disclosure may be used for public authority rooms, regulator-listening rooms, public finance reader rooms, data rooms, evidence rooms, clean rooms, emergency learning rooms, grant compliance, audits, legal review, public-safe review, technical review, and protected knowledge review.
381.10 Public-Safe Redaction.
381.10.1 Public-Safe Redaction shall remove or obscure information that should not be disclosed while preserving sufficient meaning, accuracy, and correctionability for the permitted audience.
381.10.2 Redaction may apply to personal information, health-sensitive information, public authority restricted information, privileged material, work product, trade secrets, commercial sensitivity, cyber-sensitive details, infrastructure-sensitive details, protected knowledge, community-sensitive information, finance-sensitive information, and non-public vulnerability details.
381.10.3 Redactions shall not distort meaning, conceal material limitations, or mislead audiences.
381.11 Public Authority Records Request Coordination.
381.11.1 Where the Corporation becomes aware of public authority records requests, FOIA requests, subpoenas, discovery requests, audits, inspector general reviews, legislative requests, or other disclosure processes affecting Corporation materials, the Corporation shall coordinate review with competent authority.
381.11.2 Coordination shall address confidentiality, privilege, work product, protected knowledge, personal information, cyber-sensitive data, infrastructure-sensitive data, public-safe redaction, notification obligations, and correctionability.
381.12 Legal Hold Coordination.
381.12.1 Legal Hold Coordination shall preserve records where litigation, investigation, regulatory inquiry, audit, public authority request, incident response, public records dispute, protected knowledge dispute, publication challenge, or other legal obligation requires retention.
381.12.2 Legal holds shall suspend deletion, secure disposal, or alteration of affected records and shall be communicated to relevant custodians.
381.13 No Assumption That GCRI US Records Are Public Records Except Where Law Requires.
381.13.1 Corporation records shall not be assumed to be public records merely because the Corporation interacts with public authorities, receives public grants, conducts public-benefit work, publishes public-safe materials, or supports public authority learning.
381.13.2 Where law, contract, grant terms, public authority custody, public records doctrine, or other authority may require disclosure, the Corporation shall conduct legal and records review.
381.14 No Disclosure Without Review.
381.14.1 No director, officer, employee, contractor, fellow, advisor, volunteer, contributor, maintainer, committee member, sponsor, provider, partner, public authority participant, or other person shall disclose, release, transmit, post, upload, publish, quote, map, train on, embed, or externally share sensitive records without required review and authority.
381.14.2 Unauthorized disclosure shall be subject to incident response, correction, takedown, access restriction, role restriction, contract remedy, legal review, or referral.
381.15 Public Records and Controlled Disclosure Records.
381.15.1 The Corporation shall maintain Public Records and Controlled Disclosure Records, including public records purpose records, FOIA consideration records, state public records consideration records, sunshine and open meetings consideration records, public authority confidentiality records, privilege protection records, work product protection records, sensitive material classification records, controlled disclosure records, public-safe redaction records, public authority records request coordination records, legal hold coordination records, no-assumption-of-public-records records, no-disclosure-without-review records, corrections, restrictions, holds, disclosures, redactions, and archive records.
Section 382. Procurement Neutrality and Public Procurement Boundary
382.1 Procurement Neutrality Purpose.
382.1.1 Procurement Neutrality shall ensure that the Corporation does not function as a public procurement body, vendor selector, bid evaluator, purchasing recommender, procurement scoring authority, preferred-provider creator, public contract gatekeeper, grant procurement authority, public-private partnership approver, or procurement specification mandate by default.
382.1.2 Procurement Neutrality shall preserve provider neutrality, sponsor non-control, public authority trust, competition integrity, antitrust discipline, public-safe publication, technical baseline integrity, open public-good infrastructure, and the Corporation’s non-executing role.
382.1.3 Procurement implications shall be assessed by practical effect, not by labels. Technical baselines, dashboards, maps, evidence packs, Nexus-compatible references, public-good software, standards-support materials, controlled rooms, public authority learning, and provider participation may create procurement meaning even where procurement terms are absent.
382.2 No Public Procurement Authority.
382.2.1 The Corporation shall not exercise public procurement authority, approve public purchasing, issue public procurement decisions, determine public procurement compliance, manage public tender processes, or act as a procurement agent for public authorities by default.
382.2.2 Public authorities remain solely responsible for their procurement processes, legal compliance, competition requirements, public notices, bid evaluation, contract award, vendor selection, and public accountability.
382.3 No Public Contract Award Authority.
382.3.1 The Corporation shall not award public contracts, approve contract awards, recommend awardees, rank bidders, negotiate public contracts, or create public contract commitments.
382.3.2 No Corporation publication, technical asset, dashboard, map, room participation, or public authority learning process shall be cited as public contract award authority.
382.4 No Vendor Selection for Public Authorities.
382.4.1 The Corporation shall not select vendors, providers, contractors, consultants, implementers, integrators, infrastructure operators, technology suppliers, AI providers, cloud providers, cybersecurity providers, telecom providers, or other suppliers for public authorities by default.
382.4.2 The Corporation may describe general technical requirements, public-good baselines, interoperability considerations, evidence quality considerations, and public-safe methods only with limitation language sufficient to avoid vendor-selection implication.
382.5 No Preferred Provider Status.
382.5.1 The Corporation shall not create preferred provider status, preferred vendor status, preferred integration status, approved provider status, certified provider status, public authority-preferred status, procurement-ready status, or favored implementation status by default.
382.5.2 Provider participation, contribution, sponsorship, hosting, technical support, compatibility testing, use of public-good software, alignment with technical baselines, or room participation shall not create preferred status.
382.6 No Approved Vendor List.
382.6.1 The Corporation shall not maintain or publish an approved vendor list, public procurement list, qualified vendor list, certified provider list, preferred provider list, public authority-approved list, or procurement eligibility list by default.
382.6.2 Any directory, registry, contributor list, participant list, provider list, sponsor list, technical contributor list, or public-good ecosystem list shall include language preventing approved-vendor interpretation where needed.
382.7 No Procurement Scoring by GCRI US.
382.7.1 GCRI US shall not score vendors, bids, proposals, providers, products, projects, national companies, Project SPVs, technical implementations, software, datasets, models, dashboards, maps, or infrastructure for public procurement purposes by default.
382.7.2 Evidence classifications, technical maturity discussions, benchmark results, test outputs, dashboard indicators, map layers, proof receipts, or public-safe summaries shall not be used as procurement scores unless a competent procurement authority independently and lawfully creates such use outside the Corporation’s authority.
382.8 No Procurement Specification Mandate by Technical Baseline.
382.8.1 Open technical baselines, schemas, APIs, SDKs, reference architectures, technical profiles, test harnesses, public-good software, and interoperability materials shall not constitute procurement specifications, mandatory requirements, public tender criteria, minimum qualifications, or contract terms by default.
382.8.2 Public authorities may independently consider public-good materials within their lawful procurement processes, but the Corporation shall not present those materials as mandated procurement specifications.
382.9 No Public Tender Advantage by Participation.
382.9.1 Participation in the Corporation’s programs, rooms, events, working groups, repositories, technical reviews, public authority learning sessions, sponsor programs, provider programs, or Nexus interfaces shall not create public tender advantage.
382.9.2 Where public authority procurement may be pending, anticipated, or active, the Corporation shall manage access, information flows, provider participation, sponsor participation, public authority participation, and publication language to avoid unequal procurement advantage.
382.10 No Bid Support as Public Authority Action.
382.10.1 The Corporation shall not provide bid support, proposal support, tender support, procurement strategy, public contract strategy, bid-writing assistance, or procurement lobbying as public authority action or on behalf of public authorities.
382.10.2 Any technical explanation provided to providers, sponsors, public authorities, or enterprise actors shall not be framed as bid endorsement, public authority support, procurement approval, or contract-winning guidance.
382.11 No Provider Endorsement.
382.11.1 The Corporation shall not endorse providers, vendors, products, services, platforms, tools, models, cloud services, cybersecurity services, telecom services, AI-RAN / O-RAN services, DePIN services, DLT services, integrators, consultants, national companies, Project SPVs, or implementation actors for public procurement.
382.11.2 Neutral acknowledgment of contribution, sponsorship, participation, interoperability work, or technical support shall not be written or displayed as provider endorsement.
382.12 No Sponsor Procurement Advantage.
382.12.1 Sponsors, donors, funders, providers, hosts, or partners shall not receive procurement advantage, public authority access advantage, preferred-provider status, technical baseline control, dashboard positioning, map positioning, publication framing, or public-safe claims benefit in exchange for support.
382.12.2 Sponsor support shall not influence public authority learning, procurement-sensitive information flows, provider references, technical baseline content, evidence conclusions, methods, corrections, or publication approvals.
382.13 Procurement-Sensitive Information Controls.
382.13.1 Procurement-sensitive information shall be classified and access-controlled, including draft solicitations, procurement planning, evaluation criteria, budget estimates, bid information, vendor proposals, market research, source selection information, technical evaluation notes, grant procurement materials, and confidential public authority procurement communications.
382.13.2 Procurement-sensitive information shall not be disclosed to providers, sponsors, donors, funders, partners, competitors, national companies, Project SPVs, or unauthorized persons.
382.13.3 Unauthorized access to procurement-sensitive information shall trigger incident review and corrective action.
382.14 Public Authority Procurement Participation Controls.
382.14.1 Public authority procurement personnel participating in Corporation activities shall be capacity-classified and shall be subject to procurement boundary controls.
382.14.2 Rooms, events, workshops, technical sessions, and public authority learning involving procurement personnel and providers shall be structured to avoid procurement influence, unequal access, bid coordination, market allocation, sponsor control, provider preference, or public contract implication.
382.15 Correction of Procurement Overclaim.
382.15.1 The Corporation shall correct any publication, statement, dashboard, map, repository, technical baseline, provider material, sponsor material, partner material, media statement, or public authority reference that implies procurement approval, vendor qualification, preferred-provider status, approved vendor list, procurement scoring, tender advantage, public-private partnership approval, or public contract support without competent record.
382.15.2 Correction may include takedown, revision, disclaimer, public clarification, controlled clarification, notice to public authority, notice to provider, notice to sponsor, access restriction, termination of mark use, or legal review.
382.16 Procurement Neutrality Records.
382.16.1 The Corporation shall maintain Procurement Neutrality Records, including procurement neutrality purpose records, no-public-procurement-authority records, no-public-contract-award-authority records, no-vendor-selection records, no-preferred-provider-status records, no-approved-vendor-list records, no-procurement-scoring records, no-procurement-specification-mandate records, no-public-tender-advantage records, no-bid-support-as-public-authority-action records, no-provider-endorsement records, no-sponsor-procurement-advantage records, procurement-sensitive information control records, public authority procurement participation control records, procurement overclaim correction records, restrictions, clarifications, and archive records.
Section 383. Regulatory Boundary and Compliance-Approval Boundary
383.1 Regulatory Boundary Purpose.
383.1.1 Regulatory Boundary governance shall ensure that the Corporation does not function as a regulator, enforcement body, permitting authority, licensing authority, compliance approval body, safe-harbor issuer, supervisory authority, public authority standard-setter with legal force, or public-sector decision-maker.
383.1.2 Regulatory Boundary governance shall preserve the distinction between public-benefit evidence support, methods support, observability support, public-good software, open technical baselines, public-safe publication, and public authority learning on the one hand, and regulation, compliance approval, enforcement, permitting, licensing, legal interpretation, official guidance, and public authority action on the other.
383.2 No Regulator Status.
383.2.1 The Corporation shall not claim, imply, accept, or exercise regulator status by default.
383.2.2 Public authority participation, regulator-listening participation, technical baseline publication, dashboard review, map review, evidence review, method review, public-safe publication, or public authority learning shall not make the Corporation a regulator.
383.3 No Enforcement Authority.
383.3.1 The Corporation shall not enforce laws, regulations, permits, licenses, public authority orders, procurement requirements, public finance conditions, public health orders, public safety orders, cyber requirements, AI requirements, privacy requirements, or infrastructure requirements unless a competent public authority lawfully delegates a narrow role and the Board approves such role, which shall not be presumed.
383.3.2 The Corporation’s internal enforcement of its own Bylaws, policies, access restrictions, licenses, publication controls, technical asset governance, and participation terms shall not be represented as public regulatory enforcement.
383.4 No Permit Authority.
383.4.1 The Corporation shall not issue permits, licenses, approvals to operate, approvals to deploy, approvals to collect data, approvals to process data, approvals to publish, approvals to map, approvals to use AI, approvals to transfer technology, or approvals to conduct regulated activity by default.
383.4.2 Corporation outputs shall not be used as substitutes for permits, licenses, authorizations, or approvals required by public authorities.
383.5 No Compliance Approval.
383.5.1 The Corporation shall not issue legal compliance approval, regulatory compliance approval, AI compliance approval, cybersecurity compliance approval, privacy compliance approval, export-control compliance approval, sanctions compliance approval, procurement compliance approval, public health compliance approval, public safety compliance approval, environmental compliance approval, professional compliance approval, or public-sector compliance approval by default.
383.5.2 The Corporation may describe evidence, methods, baselines, controls, records, or learning materials that may support independent compliance work, but shall not state that compliance has been achieved unless competent review supports the precise statement and the Corporation is authorized to make it.
383.6 No Regulatory Safe Harbor.
383.6.1 No Corporation output shall create regulatory safe harbor, immunity, no-action status, enforcement protection, compliance shield, official tolerance, authorized pathway, approved implementation route, or regulator-cleared status.
383.6.2 Regulator attendance, listening, comments, questions, silence, non-objection, or receipt of materials shall not create safe harbor.
383.7 No Legal Equivalence by Standards Mapping.
383.7.1 Mapping Corporation technical baselines, schemas, profiles, methods, or public-good software to laws, regulations, standards, public authority guidance, procurement criteria, or compliance frameworks shall not create legal equivalence.
383.7.2 Standards mapping may support literacy, interoperability, and evidence organization only with limitation language that mapping is not legal advice, compliance approval, regulatory approval, procurement approval, or certification.
383.8 No Compliance Determination by Evidence Review.
383.8.1 Evidence review, evidence packs, proof receipts, source-lineage records, dashboards, maps, public-safe summaries, observability outputs, or technical truth outputs shall not constitute compliance determinations.
383.8.2 Evidence may indicate that records exist or support technical understanding, but shall not determine legal compliance, regulatory compliance, public authority compliance, procurement compliance, cybersecurity compliance, privacy compliance, AI compliance, or professional compliance by itself.
383.9 No Regulatory Guidance by Learning Session.
383.9.1 Public authority learning sessions, regulator-listening rooms, workshops, briefings, simulations, technical reviews, or public-safe decision-support literacy activities shall not constitute regulatory guidance, agency interpretation, official policy, supervisory guidance, compliance instruction, or enforcement position.
383.9.2 Materials used in such sessions shall include boundary language where regulatory misunderstanding is possible.
383.10 No Authority by Regulator-Listening Participation.
383.10.1 Regulator-listening participation shall not create authority, approval, safe harbor, compliance determination, enforcement position, policy adoption, public authority endorsement, procurement approval, finance-readiness, certification, recognition, public warning, emergency command, or official action.
383.10.2 Any contrary implication shall be corrected promptly.
383.11 No AI, Dashboard, Map, Proof Receipt, Technical Baseline, Method, or Observatory Output as Compliance Approval.
383.11.1 No AI output, dashboard, map, proof receipt, compute record, inference record, technical baseline, method, observatory output, Truth Engine output, software output, dataset, model card, system card, benchmark card, test harness, or public-safe summary shall constitute compliance approval.
383.11.2 Such materials may support learning, evidence organization, technical review, public-safe reporting, or independent compliance analysis only within their recorded scope and limitations.
383.12 Regulatory Overclaim Review.
383.12.1 Regulatory Overclaim Review shall be initiated where any publication, statement, dashboard, map, dataset, software, technical baseline, room, public authority learning material, sponsor material, provider material, partner material, media statement, or digital channel suggests regulatory approval, safe harbor, compliance determination, permit, waiver, guidance, enforcement position, public authority adoption, or legal equivalence without competent record.
383.12.2 Review may require correction, takedown, public clarification, controlled clarification, regulator notice, legal review, publication hold, access restriction, or training.
383.13 Regulatory Boundary Disclaimers.
383.13.1 Regulatory Boundary Disclaimers shall be used where materials discuss regulation, compliance, standards, technical baselines, public authority learning, regulator-listening participation, evidence packs, proof receipts, dashboards, maps, AI governance, cyber governance, privacy, controlled technology, or public-sector rules in a way that could create regulatory reliance.
383.13.2 Such disclaimers shall state that materials are not regulation, official guidance, legal advice, compliance approval, safe harbor, permit, regulatory interpretation, enforcement position, or public authority decision.
383.14 Correction of Regulatory Overclaim.
383.14.1 The Corporation shall correct regulatory overclaims promptly upon discovery.
383.14.2 Correction may include term removal, limitation language, public clarification, controlled clarification, dashboard label change, map label change, technical baseline correction, repository correction, partner-material correction, sponsor-material correction, provider-material correction, social media correction, takedown, or legal notice.
383.15 Regulatory Boundary Records.
383.15.1 The Corporation shall maintain Regulatory Boundary Records, including regulatory boundary purpose records, no-regulator-status records, no-enforcement-authority records, no-permit-authority records, no-compliance-approval records, no-regulatory-safe-harbor records, no-legal-equivalence-by-standards-mapping records, no-compliance-determination-by-evidence-review records, no-regulatory-guidance-by-learning-session records, no-authority-by-regulator-listening-participation records, no-AI / dashboard / map / proof receipt / technical baseline / method / observatory output as compliance approval records, regulatory overclaim review records, regulatory boundary disclaimer records, regulatory overclaim correction records, restrictions, clarifications, and archive records.
Section 384. Public Warning, Emergency Command, Public Health Order, and Safety Command Boundary
384.1 Public Warning Boundary Purpose.
384.1.1 Public Warning, Emergency Command, Public Health Order, and Safety Command Boundary governance shall ensure that the Corporation’s publications, dashboards, maps, observability outputs, AI outputs, Truth Engine outputs, sensor signals, AI-RAN / O-RAN signals, DePIN records, DLT records, digital twins, proof receipts, evidence packs, reports, public-safe summaries, technical baselines, software, public authority learning materials, simulations, tabletop exercises, and emergency learning materials are not misread as official public warnings, emergency alerts, evacuation instructions, public health orders, safety commands, dispatch commands, incident commands, operational resource directions, or public authority substitutions.
384.1.2 This boundary shall protect the public, public authorities, communities, emergency-management systems, public health systems, public safety systems, infrastructure operators, providers, sponsors, and the Corporation from unsafe reliance, false alarm, false reassurance, operational confusion, public authority confusion, and unauthorized command.
384.2 No Official Public Warning.
384.2.1 The Corporation shall not issue official public warnings, hazard warnings, public health warnings, public safety warnings, infrastructure warnings, cyber warnings on behalf of public authorities, environmental warnings, biosecurity warnings, food-system warnings, water-system warnings, energy-system warnings, telecom warnings, transportation warnings, or emergency risk communications.
384.2.2 Corporation materials may describe evidence, limitations, observability, public-safe learning, correction, or technical context, but shall not be labeled, designed, timed, pushed, geofenced, color-coded, or distributed as official warnings.
384.3 No Emergency Alert.
384.3.1 The Corporation shall not issue emergency alerts, wireless emergency alerts, public alert and warning system messages, siren instructions, emergency broadcast messages, emergency app alerts, official cyber alerts, official infrastructure alerts, or emergency notifications on behalf of public authorities.
384.3.2 Where urgent public safety matters arise, the Corporation may refer audiences to competent public authorities, emergency services, or official channels without assuming alert authority.
384.4 No Evacuation Instruction.
384.4.1 The Corporation shall not issue evacuation instructions, shelter-in-place instructions, route instructions, public movement instructions, reentry instructions, facility closure instructions, public access restrictions, or protective-action directives.
384.4.2 Maps, dashboards, simulations, digital twins, observability outputs, public-safe summaries, or AI outputs shall not be published or displayed in a manner that could reasonably be treated as evacuation guidance.
384.5 No Public Health Order.
384.5.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, hospital directives, health-system operational instructions, or biosecurity orders.
384.5.2 Public health and biosecurity materials shall be framed as research, evidence, methods, observability, public authority learning, technical literacy, data governance, safeguards, or public-safe publication unless issued by a competent public health authority through lawful process.
384.6 No Safety Command.
384.6.1 The Corporation shall not issue safety commands, law enforcement directives, fire service directives, rescue directives, emergency medical directives, dispatch directives, public works directives, facility safety orders, infrastructure safety commands, crowd-control instructions, or operational safety orders.
384.6.2 Public safety materials shall not be labeled as command, instruction, order, directive, deployment, dispatch, clearance, all-clear, warning, or official safety action unless issued by a competent public authority.
384.7 No Dispatch or Incident Command.
384.7.1 The Corporation shall not dispatch emergency personnel, public safety personnel, public health personnel, public works personnel, infrastructure crews, telecom crews, cyber response teams, providers, volunteers, medical resources, food resources, water resources, energy resources, shelter resources, equipment, or operational assets.
384.7.2 The Corporation shall not act as incident command, unified command, emergency operations center, public safety command, public health command, public works command, infrastructure command, cyber command, or operational coordination body.
384.8 No Operational Resource Direction.
384.8.1 The Corporation shall not direct deployment, staging, prioritization, allocation, routing, restoration, shutdown, activation, deactivation, maintenance, repair, containment, mitigation, or withdrawal of operational resources.
384.8.2 Evidence records, dashboards, maps, public-safe visualizations, observability outputs, degraded-mode indicators, digital twin scenarios, proof receipts, or reports shall not be represented as operational resource direction.
384.9 No Public Authority Substitution Through Dashboard, Map, AI Output, Truth Engine Output, Sensor Signal, AI-RAN Signal, DePIN Record, Digital Twin, Proof Receipt, or Report.
384.9.1 No dashboard, map, AI output, Truth Engine output, sensor signal, AI-RAN / O-RAN signal, DePIN record, DLT record, digital twin, proof receipt, compute workload record, inference record, benchmark, observability output, evidence pack, report, whitepaper, technical note, public-safe summary, software output, technical baseline, or public-good technical asset shall substitute for public authority decision-making, public warning, emergency command, public health order, public safety order, infrastructure operator action, or operational control.
384.9.2 Automated, interactive, AI-assisted, or real-time outputs shall include stronger boundary controls where velocity, visual design, notification behavior, or apparent precision could create command-like reliance.
384.10 Public-Safe Reporting as Non-Command.
384.10.1 Public-Safe Reporting may communicate evidence-supported, limitation-aware, non-executing information, corrections, summaries, educational materials, public authority learning materials, or technical context.
384.10.2 Public-Safe Reporting shall be framed as information, learning, evidence support, methods support, technical support, or correction, and not as public authority action, warning, command, order, directive, approval, clearance, all-clear, or operational instruction.
384.11 Escalation to Appropriate Public Authority Where Required or Appropriate.
384.11.1 Where the Corporation becomes aware of information that may require official public warning, emergency action, public health action, public safety action, cyber response, infrastructure response, law enforcement action, or public authority decision, the Corporation may escalate, refer, or notify appropriate public authorities where lawful, appropriate, and consistent with confidentiality, privacy, cybersecurity, protected knowledge, public-safe communication, and legal obligations.
384.11.2 Escalation shall not be represented as public authority approval, public warning issuance, emergency command, public authority action, or substitute for official channels.
384.12 Emergency Communications Discipline.
384.12.1 Emergency-adjacent communications shall be authorized, factual, minimum-necessary, non-speculative, public-safe, and coordinated with legal, data, AI, cyber, privacy, public authority, infrastructure-sensitive, public health, public safety, and protected knowledge review where applicable.
384.12.2 Such communications shall avoid alarmist framing, false reassurance, unsupported causation, unsupported absence-of-impact claims, operational instructions, public authority overclaim, and disclosure of sensitive operational details.
384.13 Correction of Public Warning Overclaim.
384.13.1 The Corporation shall promptly correct any statement, publication, dashboard, map, social media post, AI output, report, technical baseline, software output, partner material, sponsor material, provider material, media statement, or public authority reference that implies public warning, emergency command, public health order, safety command, dispatch, incident command, operational resource direction, official alert, or public authority substitution without competent authority.
384.13.2 Correction may include immediate takedown, alert-like design removal, label revision, dashboard hold, map hold, public clarification, controlled clarification, public authority notice, media correction, partner notice, sponsor notice, provider notice, access restriction, or incident response.
384.14 Public Warning and Emergency Command Boundary Records.
384.14.1 The Corporation shall maintain Public Warning and Emergency Command Boundary Records, including public warning boundary purpose records, no-official-public-warning records, no-emergency-alert records, no-evacuation-instruction records, no-public-health-order records, no-safety-command records, no-dispatch-or-incident-command records, no-operational-resource-direction records, no-public-authority-substitution-through-dashboard / map / AI output / Truth Engine output / sensor signal / AI-RAN signal / DePIN record / digital twin / proof receipt / report records, public-safe reporting as non-command records, escalation-to-public-authority records, emergency communications discipline records, public warning overclaim correction records, restrictions, clarifications, notices, and archive records.
Section 385. Public Finance, Budget, Grant, Appropriation, Tax Credit, Public Guarantee, and Sovereign Obligation Boundary
385.1 Public Finance Boundary Purpose.
385.1.1 Public Finance Boundary governance shall ensure that the Corporation’s public-benefit evidence, methods, observability, ontology, public-good R&D, public-good software, open technical baselines, public authority learning, public-safe publication, dashboards, maps, datasets, evidence packs, proof packs, technical records, Docket-facing inputs, Grid-facing inputs, GRA-facing inputs, capital-readable materials, and Nexus interface outputs are not misread as public finance approval, budget allocation, appropriation, grant approval, tax credit approval, MDB / DFI approval, public guarantee, public credit, sovereign obligation, public debt approval, capital commitment, finance-readiness, rating, investment advice, lending approval, insurance approval, or fiscal commitment.
385.1.2 Public Finance Boundary governance shall preserve the legal and institutional separation between GCRI US as a non-executing public-good evidence and methods institution; The Global Risks Alliance (GRA) as the separate finance-readiness and capital-reader interface body where applicable; public finance authorities as public decision-makers; and investors, lenders, insurers, public finance readers, development finance institutions, multilateral development banks, national companies, Project SPVs, sponsors, providers, and enterprise actors as separate actors with their own authority, diligence, risk, and legal duties.
385.1.3 Public Finance Boundary governance shall apply to all Corporation materials that may be reviewed by public finance actors, budget offices, treasuries, grantors, MDBs, DFIs, sovereign funds, municipal finance actors, public credit actors, guarantee authorities, tax credit authorities, capital readers, insurers, lenders, sponsors, Project SPVs, national companies, public authorities, or enterprise actors.
385.2 No Public Finance Approval.
385.2.1 The Corporation shall not approve public finance, public infrastructure finance, blended finance, concessional finance, sovereign finance, municipal finance, development finance, climate finance, resilience finance, guarantee finance, tax-supported finance, public credit support, public-private partnership finance, MDB finance, DFI finance, or any governmental or quasi-governmental fiscal commitment.
385.2.2 No report, evidence pack, public-safe summary, dashboard, map, technical baseline, proof receipt, Docket input, Grid input, GRA-facing input, capital-readable record, public authority learning material, or controlled-room material shall be represented as public finance approval.
385.2.3 Public finance approval may be made only by competent public finance authorities through lawful procedures, and no Corporation material shall be used to imply otherwise.
385.3 No Budget Allocation.
385.3.1 The Corporation shall not allocate public budgets, approve budget lines, authorize expenditures, determine agency budget priorities, approve program funding, direct fiscal resources, or create budget obligations.
385.3.2 Public authority attendance, public finance reader participation, grant discussion, evidence review, technical review, dashboard review, map review, or public authority learning shall not constitute budget allocation.
385.3.3 Corporation materials may identify public-benefit evidence gaps, technical needs, resilience needs, observability needs, methods needs, and public-good infrastructure needs only as non-binding learning and evidence support, and not as budget determinations.
385.4 No Appropriation.
385.4.1 The Corporation shall not make, approve, recommend as official, create, direct, administer, or imply public appropriations.
385.4.2 No communication with legislative, executive, budget, treasury, public finance, grant, or public authority actors shall be framed as appropriation approval, appropriation commitment, budget enactment, fiscal authorization, or public expenditure authority.
385.4.3 Where Corporation materials are used in nonpartisan education or public-benefit research concerning public needs, the materials shall not be presented as legislative action, appropriations request, official budget instruction, or public finance commitment unless separately reviewed and authorized under applicable lobbying and political activity controls.
385.5 No Public Grant Approval.
385.5.1 The Corporation shall not approve public grants, determine grant eligibility, score grant applications, award public grants, commit grant funds, recommend grant awards as a public authority, or create grant entitlement.
385.5.2 Corporation participation in public authority learning, evidence review, technical literacy, public-good software demonstration, controlled-room review, or grant-funded programming shall not constitute grant approval.
385.5.3 Any reference to public grants shall distinguish grant application, grant award to the Corporation, grant-funded work, grant reporting, public-benefit output, and grant approval by competent public authority.
385.6 No Tax Credit Approval.
385.6.1 The Corporation shall not approve tax credits, tax incentives, tax allocations, tax benefits, tax compliance, tax equity eligibility, public tax-supported finance, or any tax authority decision.
385.6.2 Corporation materials concerning resilience, public-good infrastructure, Project SPVs, national companies, observability, technical baselines, public authority learning, or finance-facing evidence shall not be described as supporting tax credit approval except as non-binding technical or evidence materials subject to independent public authority and professional review.
385.7 No MDB / DFI Approval.
385.7.1 The Corporation shall not approve, commit, represent, bind, or imply approval by any multilateral development bank, development finance institution, export credit agency, sovereign fund, public lender, guarantee authority, public finance institution, or similar capital actor.
385.7.2 MDB / DFI attendance, review, listening, capital-reader participation, receipt of materials, public finance reader room participation, or comments shall not imply concept approval, board approval, investment committee approval, credit committee approval, guarantee approval, project approval, environmental and social approval, public finance approval, or capital commitment.
385.8 No Public Guarantee.
385.8.1 The Corporation shall not issue, approve, arrange, recommend, represent, or imply public guarantees, sovereign guarantees, municipal guarantees, credit guarantees, insurance guarantees, performance guarantees, resilience guarantees, infrastructure guarantees, completion guarantees, payment guarantees, or guarantee eligibility.
385.8.2 Evidence, proof receipts, technical baselines, dashboards, maps, observability outputs, Grid inputs, Docket inputs, or public-safe summaries shall not be treated as guarantees or guarantee approvals.
385.9 No Public Credit.
385.9.1 The Corporation shall not approve public credit, public loans, public credit enhancement, public lending, public credit support, creditworthiness, municipal credit, sovereign credit, concessional credit, or credit eligibility.
385.9.2 No Corporation evidence output, technical output, public-safe publication, or GRA-facing input shall be represented as credit approval, credit opinion, credit support, rating, or underwriting support.
385.10 No Sovereign Obligation.
385.10.1 The Corporation shall not create, approve, bind, imply, or represent sovereign obligations, municipal obligations, public debts, public liabilities, treaty obligations, intergovernmental fiscal commitments, public-private partnership obligations, public guarantees, public credit commitments, or governmental fiscal duties.
385.10.2 Public authority participation, North America interface activity, cross-border learning, public finance reader participation, public authority room participation, or government funding shall not create sovereign obligation.
385.11 No Public Debt Approval.
385.11.1 The Corporation shall not approve public debt, bonds, notes, municipal obligations, sovereign borrowing, public infrastructure debt, public credit instruments, public-private partnership debt, or public borrowing programs.
385.11.2 No Corporation material shall be used as debt approval, offering support, municipal advisor opinion, credit rating, bond counsel opinion, underwriting approval, investor recommendation, or public debt validation.
385.12 No Capital Commitment by Public Finance Reader Participation.
385.12.1 Public Finance Reader participation shall not constitute capital commitment, public funding commitment, investment commitment, lending commitment, guarantee commitment, grant commitment, budget commitment, appropriation commitment, tax credit commitment, MDB / DFI commitment, or public credit support.
385.12.2 Public Finance Reader participation shall be described as learning, diligence-literacy, evidence-literacy, technical-literacy, public-safe decision-support literacy, or non-approval review unless a separate competent public finance record states otherwise.
385.13 No Finance-Readiness by GCRI US Evidence Output.
385.13.1 No GCRI US evidence output, method output, observability output, public-safe summary, dashboard, map, dataset, technical baseline, proof receipt, inference record, compute workload record, software release, public authority learning material, Docket-facing input, Grid-facing input, or GRA-facing input shall by itself constitute finance-readiness, insurance-readiness, capital-readiness, investment-readiness, bankability, investability, creditworthiness, underwriteability, public finance-readiness, or rating.
385.13.2 GCRI US may support record-based evidence, methods, observability, and technical clarity for separate consideration by competent bodies, but shall not determine finance-readiness.
385.14 GRA Role-Separation.
385.14.1 Where finance-readiness, capital-readability, insurance-readiness, proof packs, diligence translation, capital-reader rooms, Nexus Rails, RNFD, NFD, UNFSD, Docket-facing materials, Grid-facing materials, or finance-facing evidence is referenced, GCRI US shall preserve role separation from The Global Risks Alliance (GRA).
385.14.2 GRA role-separation language shall state, where necessary, that GCRI US provides non-executing evidence, methods, observability, technical records, and public-safe materials only, and that any GRA finance-readiness function, if applicable, is separate and must be supported by competent GRA records.
385.14.3 References to GRA shall not imply that GRA has issued finance-readiness, approved a project, arranged financing, placed capital, underwritten risk, issued a rating, or accepted any obligation unless a competent GRA record expressly supports the statement.
385.15 Correction of Public Finance Overclaim.
385.15.1 The Corporation shall correct any public finance overclaim, including any statement, publication, dashboard, map, dataset, evidence pack, proof pack, technical baseline, public authority reference, sponsor material, provider material, partner material, media statement, digital channel post, or room summary that implies public finance approval, budget allocation, appropriation, public grant approval, tax credit approval, MDB / DFI approval, public guarantee, public credit, sovereign obligation, public debt approval, capital commitment, or finance-readiness without competent record.
385.15.2 Correction may include immediate hold, takedown, revision, limitation language, public clarification, controlled clarification, notice to public authority, notice to GRA, notice to affected capital readers, access restriction, withdrawal, retraction, or legal review.
385.16 Public Finance Boundary Records.
385.16.1 The Corporation shall maintain Public Finance Boundary Records, including public finance boundary purpose records, no-public-finance-approval records, no-budget-allocation records, no-appropriation records, no-public-grant-approval records, no-tax-credit-approval records, no-MDB / DFI-approval records, no-public-guarantee records, no-public-credit records, no-sovereign-obligation records, no-public-debt-approval records, no-capital-commitment-by-public-finance-reader-participation records, no-finance-readiness-by-GCRI-US-evidence-output records, GRA role-separation records, public finance overclaim correction records, notices, restrictions, clarifications, withdrawals, and archive records.
Section 386. Public-Private Partnership, Intergovernmental, Joint Exercise, Tabletop, Simulation, Pilot, and Demonstration Boundary
386.1 PPP Boundary Purpose.
386.1.1 Public-Private Partnership, intergovernmental, joint exercise, tabletop, simulation, pilot, and demonstration boundary governance shall ensure that participation in Corporation activities is not misrepresented as a public-private partnership, intergovernmental agreement, joint venture, public adoption, procurement approval, public authority delegation, emergency command, finance approval, certification, recognition, provider preference, sovereign obligation, or execution authority.
386.1.2 Pilots, demonstrations, simulations, tabletop exercises, joint exercises, controlled rooms, public authority rooms, public finance reader rooms, emergency learning rooms, public-good software demonstrations, dashboard demonstrations, map demonstrations, technical baseline demonstrations, AI-RAN / O-RAN demonstrations, DePIN demonstrations, DLT demonstrations, digital twin demonstrations, and observability demonstrations shall remain within their documented scope and shall not create legal status by implication.
386.2 No PPP by Participation Alone.
386.2.1 No public-private partnership shall be created by attendance, participation, sponsorship, hosting, technical review, pilot participation, demonstration participation, public authority learning, data contribution, room participation, dashboard review, map review, or publication reference alone.
386.2.2 A public-private partnership may exist only where competent public authority and competent Corporation records expressly establish such relationship, and any such relationship shall be reviewed for lawfulness, nonprofit compatibility, procurement, public finance, public records, conflicts, public authority boundaries, and non-execution.
386.3 No Intergovernmental Agreement by Participation Alone.
386.3.1 No intergovernmental agreement, compact, treaty, sovereign arrangement, public authority memorandum, regional public authority decision, or public authority commitment shall be created by participation alone.
386.3.2 Corporation materials shall not describe joint learning, cross-border learning, public authority rooms, or multi-authority exercises as intergovernmental agreements unless competent public authorities have lawfully established such agreement and the Corporation is authorized to reference it.
386.4 No Joint Venture by Participation Alone.
386.4.1 No joint venture, legal partnership, agency, shared control, shared treasury, shared liability, common enterprise, public-private venture, or execution vehicle shall be created by participation, sponsorship, hosting, public authority learning, controlled-room participation, pilot participation, or demonstration participation alone.
386.4.2 Any actual joint venture or execution vehicle shall require separate legal authorization and shall not be presumed within GCRI US public-good evidence functions.
386.5 No Public Adoption by Joint Exercise.
386.5.1 Joint exercises, simulations, tabletop exercises, after-action learning, pilots, demonstrations, public authority learning sessions, or controlled-room processes shall not constitute public adoption of Corporation methods, software, dashboards, maps, technical baselines, evidence packs, observability outputs, public-safe summaries, or Nexus architecture.
386.5.2 Public adoption requires separate lawful public authority action and shall not be inferred from participation.
386.6 No Procurement Approval by Pilot.
386.6.1 Pilot participation shall not constitute procurement approval, vendor qualification, public tender advantage, preferred-provider status, public contract eligibility, public-private partnership approval, or purchasing recommendation.
386.6.2 Pilot charters shall state that participation does not determine future procurement and does not confer advantage unless a competent procurement authority lawfully provides otherwise outside the Corporation’s authority.
386.7 No Public Authority Delegation by Demonstration.
386.7.1 Demonstration of software, dashboard, map, technical baseline, public-good asset, AI tool, observability method, digital twin, AI-RAN / O-RAN signal interface, DePIN telemetry interface, DLT interface, or proof receipt workflow shall not constitute delegation of public authority powers.
386.7.2 Demonstrations shall not be framed as operational handoff, public authority adoption, emergency deployment, procurement approval, regulatory approval, or public warning system activation.
386.8 No Emergency Command by Tabletop.
386.8.1 Tabletop exercises, emergency learning rooms, simulations, after-action learning, degraded-mode scenarios, digital twin exercises, and scenario planning shall not create emergency command, incident command, dispatch authority, evacuation authority, public health order, public safety command, public works command, infrastructure command, or operational resource direction.
386.8.2 Tabletop materials shall be labeled as learning, simulation, hypothetical, scenario, exercise, or after-action learning materials.
386.9 No Finance Approval by Simulation.
386.9.1 Simulation, digital twin output, resilience scenario, finance-facing evidence translation, proof pack review, capital-reader room participation, public finance reader participation, or Grid-facing discussion shall not constitute finance approval, public finance approval, investment approval, lending approval, insurance approval, rating, finance-readiness, bankability, or capital commitment.
386.9.2 Finance-adjacent simulations shall include non-reliance and finance-boundary language.
386.10 No Certification by Demonstration.
386.10.1 Demonstrations, pilots, test runs, benchmark displays, public-good software demonstrations, dashboard demonstrations, map demonstrations, technical baseline demonstrations, AI model demonstrations, or observability demonstrations shall not constitute certification, accreditation, conformance approval, legal compliance approval, public authority adoption, procurement approval, recognition, maturity determination, or guarantee.
386.10.2 Passing a demonstration, pilot, test harness, benchmark, or scenario shall not create certified, compliant, approved, recognized, finance-ready, procurement-ready, public-warning-ready, or emergency-ready status.
386.11 Pilot and Demonstration Charter Requirement.
386.11.1 Each material pilot or demonstration shall have a Pilot and Demonstration Charter or equivalent record identifying purpose, scope, participants, capacity classifications, public authority role, sponsor role, provider role, host role, data used, systems used, public-safe status, access class, permitted uses, prohibited uses, publication limits, procurement boundary, finance boundary, regulatory boundary, certification boundary, recognition boundary, public warning boundary, emergency command boundary, IP terms, data / AI / cyber / privacy controls, protected knowledge safeguards, correction path, and closeout.
386.11.2 The charter shall state that the pilot or demonstration is non-executing unless a separate competent record expressly provides otherwise.
386.12 Simulation and Tabletop Public-Safe Disclaimers.
386.12.1 Simulation and tabletop materials shall include public-safe disclaimers sufficient to distinguish scenario from observed fact, model from forecast, demonstration from deployment, learning from command, public authority participation from adoption, and technical output from public warning.
386.12.2 Disclaimers shall be visible in materials, summaries, dashboards, maps, recordings, slides, public-safe outputs, and after-action materials where reliance risk exists.
386.13 Public Authority Approval Records for References.
386.13.1 Public references to public authority participation in PPP-related, intergovernmental, joint exercise, tabletop, simulation, pilot, or demonstration activities shall require Public Authority Approval Records or other competent reference approval where the reference could imply official status.
386.13.2 Approval records shall specify permitted language, capacity, attribution, name use, logo use, quote use, photographs, recordings, data contribution statements, and required non-endorsement language.
386.14 Correction of PPP or Joint Exercise Overclaim.
386.14.1 The Corporation shall correct any overclaim that characterizes participation, pilot, demonstration, tabletop, simulation, joint exercise, controlled room, public authority learning, data contribution, or event as a PPP, intergovernmental agreement, joint venture, public adoption, procurement approval, public authority delegation, emergency command, finance approval, certification, recognition, provider preference, sovereign obligation, or execution authority without competent record.
386.14.2 Correction may include hold, takedown, revision, limitation language, public clarification, controlled clarification, public authority notice, partner notice, sponsor notice, provider notice, legal review, withdrawal, or retraction.
386.15 PPP, Exercise, Simulation, Pilot, and Demonstration Records.
386.15.1 The Corporation shall maintain PPP, Exercise, Simulation, Pilot, and Demonstration Records, including PPP boundary purpose records, no-PPP-by-participation-alone records, no-intergovernmental-agreement-by-participation-alone records, no-joint-venture-by-participation-alone records, no-public-adoption-by-joint-exercise records, no-procurement-approval-by-pilot records, no-public-authority-delegation-by-demonstration records, no-emergency-command-by-tabletop records, no-finance-approval-by-simulation records, no-certification-by-demonstration records, Pilot and Demonstration Charters, simulation and tabletop disclaimer records, public authority approval records for references, PPP or joint exercise overclaim correction records, closeout records, restrictions, and archive records.
Section 387. Public Authority Boundary Incidents, Overclaims, Corrections, Withdrawals, and Public Clarifications
387.1 Public Authority Boundary Incident Definition.
387.1.1 A Public Authority Boundary Incident means any actual, suspected, alleged, or reasonably foreseeable misstatement, misuse, omission, publication defect, reference defect, capacity defect, role inflation, overclaim, unauthorized disclosure, unauthorized name use, unauthorized logo use, unauthorized quote use, false endorsement claim, false adoption claim, false funding approval claim, false procurement approval claim, false regulatory approval claim, false public finance approval claim, false public warning or emergency command claim, false PPP claim, false sovereign obligation claim, or related public authority boundary failure.
387.1.2 Public Authority Boundary Incidents may arise in publications, dashboards, maps, datasets, evidence packs, proof packs, technical baselines, software, repositories, public-safe summaries, media statements, social media, newsletters, events, public authority rooms, controlled rooms, grant materials, sponsor materials, provider materials, partner materials, public authority learning materials, or third-party statements referencing the Corporation.
387.2 Misdescribed Capacity.
387.2.1 Misdescribed Capacity occurs where a public authority participant, public official, public employee, regulator, public finance reader, emergency-management participant, public infrastructure operator, public health participant, public safety participant, public university actor, public laboratory actor, Tribal / Indigenous representative, observer, reviewer, data provider, or personal-capacity participant is described in a capacity broader, different, more official, more approving, more endorsing, or more binding than the record supports.
387.2.2 Misdescribed Capacity shall be corrected promptly, including through revised capacity language, non-attribution, removal, public clarification, controlled clarification, or public authority notice where appropriate.
387.3 Unauthorized Public Authority Name Use.
387.3.1 Unauthorized Public Authority Name Use occurs where a public authority name, office, department, agency, program, institution, or official body is referenced without authority, permission, public-safe review, or accurate capacity classification where required.
387.3.2 Unauthorized name use may require removal, revision, notice, public clarification, controlled clarification, or takedown.
387.4 Unauthorized Public Authority Logo Use.
387.4.1 Unauthorized Public Authority Logo Use occurs where a logo, seal, flag, insignia, crest, emblem, letterhead, badge, program mark, or official visual identifier is used without required permission or in a misleading context.
387.4.2 Logo misuse shall be treated as high-risk where it implies endorsement, adoption, official status, funding approval, procurement approval, public finance approval, regulatory approval, public warning, emergency command, or public-private partnership.
387.5 Unauthorized Public Authority Quote Use.
387.5.1 Unauthorized Public Authority Quote Use occurs where a public official, public employee, public authority representative, regulator, public finance actor, or public-sector-affiliated person is quoted without permission, outside approved context, with inaccurate attribution, in misleading excerpt, or in a manner implying approval beyond the record.
387.5.2 Quote misuse may require correction, quote removal, attribution correction, public authority notice, public clarification, controlled clarification, or takedown.
387.6 False Endorsement Claim.
387.6.1 False Endorsement Claim means any statement or implication that a public authority endorses, supports, recommends, sponsors, validates, verifies, approves, or officially backs the Corporation, a publication, a technical asset, a sponsor, a provider, a partner, a project, a national company, a Project SPV, or a Nexus output without competent record.
387.7 False Adoption Claim.
387.7.1 False Adoption Claim means any statement or implication that a public authority has adopted, implemented, accepted, relied upon as official, incorporated, mandated, or made operative any Corporation method, dashboard, map, dataset, software, technical baseline, evidence pack, public-safe summary, observability output, Nexus-compatible profile, or publication without competent record.
387.8 False Funding Approval Claim.
387.8.1 False Funding Approval Claim means any statement or implication that a public authority, grantor, budget office, treasury, funder, public finance actor, MDB, DFI, or public program has approved funding, grants, budget allocation, appropriations, tax credits, guarantees, public credit, or capital support without competent record.
387.9 False Procurement Approval Claim.
387.9.1 False Procurement Approval Claim means any statement or implication that a public authority has approved procurement, selected a vendor, qualified a provider, created preferred-provider status, approved a public contract, approved a public-private partnership, endorsed a bid, adopted a procurement specification, or granted tender advantage without competent record.
387.10 False Regulatory Approval Claim.
387.10.1 False Regulatory Approval Claim means any statement or implication that a regulator has approved, guided, cleared, authorized, permitted, licensed, safe-harbored, adopted, waived, or determined compliance for the Corporation, a technical asset, a provider, a project, a dashboard, a map, a dataset, a model, a system, a method, or a publication without competent record.
387.11 False Public Finance Approval Claim.
387.11.1 False Public Finance Approval Claim means any statement or implication that public finance approval, MDB / DFI approval, public guarantee, public credit, tax credit approval, sovereign obligation, public debt approval, public finance-readiness, or capital commitment has been issued without competent record.
387.12 False Public Warning or Emergency Command Claim.
387.12.1 False Public Warning or Emergency Command Claim means any statement or implication that the Corporation, or a public authority through Corporation materials, issued public warning, emergency alert, evacuation instruction, public health order, safety command, dispatch instruction, incident command, infrastructure directive, or operational resource direction without competent authority.
387.13 False PPP or Sovereign Obligation Claim.
387.13.1 False PPP or Sovereign Obligation Claim means any statement or implication that participation, a pilot, demonstration, room, event, grant, public authority learning session, cross-border interface, or publication created a public-private partnership, intergovernmental agreement, joint venture, sovereign obligation, treaty obligation, public debt, public guarantee, or governmental fiscal commitment without competent record.
387.14 Incident Intake.
387.14.1 Public Authority Boundary Incident Intake shall record the reported issue, affected material, public authority involved, public official involved where applicable, capacity classification, publication channel, audience, risk level, evidence provided, complainant where known, urgency, public-safe risk, legal risk, public authority notice need, and interim action.
387.14.2 Incident Intake may be initiated by directors, officers, staff, contractors, fellows, advisors, volunteers, public authorities, public officials, communities, sponsors, providers, partners, media, members of the public, or monitoring processes.
387.15 Hold, Takedown, Correction, Withdrawal, Retraction, Public Clarification, Notice to Public Authority, or Legal Response.
387.15.1 Where a Public Authority Boundary Incident presents material risk, the Corporation may impose publication hold, dashboard hold, map hold, repository hold, room hold, public authority reference hold, access restriction, takedown, correction, withdrawal, retraction, public clarification, controlled clarification, notice to public authority, notice to affected participants, legal review, regulator referral, funder referral, or law enforcement referral where required or appropriate.
387.15.2 The remedy shall be proportionate to harm, reliance risk, public authority risk, public finance risk, procurement risk, regulatory risk, emergency risk, public-safe risk, recurrence, intent, and correctionability.
387.16 Public Authority Boundary Incident Records.
387.16.1 The Corporation shall maintain Public Authority Boundary Incident Records, including incident definition records, misdescribed capacity records, unauthorized public authority name-use records, unauthorized public authority logo-use records, unauthorized public authority quote-use records, false endorsement claim records, false adoption claim records, false funding approval claim records, false procurement approval claim records, false regulatory approval claim records, false public finance approval claim records, false public warning or emergency command claim records, false PPP or sovereign obligation claim records, incident intake records, hold / takedown / correction / withdrawal / retraction / public clarification / public authority notice / legal response records, closeout records, recurrence-prevention records, and archive records.
Section 388. Public Authority Interface Training
388.1 Training Purpose.
388.1.1 Public Authority Interface Training shall ensure that directors, officers, employees, contractors, fellows, advisors, volunteers, contributors, committee members, public authority participants, sponsors, providers, partners, and other relevant persons understand the Corporation’s public authority boundary, non-execution doctrine, capacity classification system, public authority data controls, public authority reference controls, procurement neutrality, regulatory boundary, public warning boundary, emergency command boundary, public finance reader boundary, government ethics, gifts, lobbying, public records, open meetings, public sector confidentiality, state and territorial localization, Tribal / Indigenous interface safeguards, local interface rules, and North America interface rules.
388.1.2 Training shall be practical, records-based, role-specific, scenario-informed, and updated as the Corporation’s public authority interfaces, technologies, public-good assets, dashboards, maps, rooms, public authority learning materials, and Nexus interfaces evolve.
388.2 Director Training.
388.2.1 Directors shall receive training on fiduciary oversight of public authority boundaries, public authority risk, public finance risk, procurement neutrality, lobbying and political activity limits, government ethics, public grants, public authority data, public records, public-safe publication, corrections, and enforcement.
388.2.2 Director training shall emphasize Board-level oversight of high-risk public authority interfaces, public grants, major publications, public authority rooms, crisis communications, and boundary incidents.
388.3 Officer Training.
388.3.1 Officers shall receive training on implementation of public authority boundary controls, capacity classification, official capacity records, public authority data contributions, publication approvals, public authority references, public finance reader controls, procurement neutrality, regulator-listening controls, public warning boundaries, room governance, public grants, incident response, and corrective action.
388.3.2 Officer training shall include authority to pause, restrict, hold, correct, withdraw, or escalate public authority-facing activity where risk requires.
388.4 Staff and Contractor Training.
388.4.1 Staff and contractors engaged in research, evidence, methods, observability, publications, dashboards, maps, software, repositories, public authority learning, events, rooms, grants, media, digital channels, data governance, AI governance, cybersecurity, or public authority communications shall receive role-specific public authority interface training.
388.4.2 Training shall cover prohibited claims, controlled vocabulary, public authority names and logos, official capacity records, public authority data restrictions, no-AI-use restrictions, public-safe mapping, public records considerations, and correction pathways.
388.5 Fellow, Advisor, Volunteer, Contributor, and Committee Training.
388.5.1 Fellows, advisors, volunteers, contributors, maintainers, reviewers, committee members, and council participants shall receive training appropriate to their access, authority, publication role, public authority exposure, repository access, data access, room participation, and public-facing activity.
388.5.2 Training shall state that affiliation, expertise, advisory role, contribution, or committee participation does not create authority to speak for the Corporation or represent public authority status.
388.6 Public Authority Participant Orientation.
388.6.1 Public Authority Participant Orientation shall be provided where appropriate before public authority rooms, controlled rooms, public finance reader rooms, regulator-listening rooms, emergency learning rooms, simulations, tabletop exercises, data contributions, dashboard reviews, map reviews, or public authority learning sessions.
388.6.2 Orientation shall address capacity classification, non-endorsement, no adoption, no procurement approval, no funding approval, no public finance approval, no regulatory approval, no public warning, no emergency command, confidentiality, public records considerations, and publication reference rules.
388.7 Capacity Classification Training.
388.7.1 Capacity Classification Training shall teach how to distinguish official participant, delegated representative, institutional representative, observer, regulator-listening participant, public finance reader, emergency-management participant, public infrastructure operator participant, public health participant, public safety participant, public works participant, academic representative, personal-capacity participant, non-attributable participant, controlled-room participant, data provider, reviewer, simulation participant, and host authority.
388.7.2 Training shall include examples of misdescribed capacity and required correction.
388.8 Public Authority Data Training.
388.8.1 Public Authority Data Training shall cover authority records, capacity records, data contribution agreements, permitted use, prohibited use, classification, confidentiality, AI-use restrictions, publication restrictions, retention, deletion, transfer restrictions, public records considerations, public-safe release review, withdrawal, and correction.
388.9 Public Authority Reference Training.
388.9.1 Public Authority Reference Training shall cover public authority name use, logo use, title use, quote use, attendance references, photographs, recordings, event references, data contribution statements, official capacity language, observer language, personal capacity language, non-attribution, non-endorsement language, and correction of misdescribed references.
388.10 Procurement Neutrality Training.
388.10.1 Procurement Neutrality Training shall cover no public procurement authority, no vendor selection, no preferred provider status, no approved vendor list, no procurement scoring, no procurement specification mandate, no tender advantage, no bid support as public authority action, provider neutrality, sponsor non-control, procurement-sensitive information controls, and procurement overclaim correction.
388.11 Regulatory Boundary Training.
388.11.1 Regulatory Boundary Training shall cover no regulator status, no enforcement authority, no permit authority, no compliance approval, no safe harbor, no legal equivalence by standards mapping, no compliance determination by evidence review, no regulatory guidance by learning session, no authority by regulator-listening participation, and regulatory boundary disclaimers.
388.12 Public Warning and Emergency Command Boundary Training.
388.12.1 Public Warning and Emergency Command Boundary Training shall cover no official public warning, no emergency alert, no evacuation instruction, no public health order, no safety command, no dispatch or incident command, no operational resource direction, no public authority substitution through dashboards, maps, AI outputs, Truth Engine outputs, sensor signals, AI-RAN signals, DePIN records, digital twins, proof receipts, or reports, and escalation to competent public authorities.
388.13 Public Finance Reader Training.
388.13.1 Public Finance Reader Training shall cover public finance reader status, no grant approval, no budget allocation, no appropriation, no public finance approval, no MDB / DFI approval, no public guarantee, no public credit, no tax credit approval, no sovereign obligation, no capital commitment, no investment advice, no GRA finance-readiness determination by GCRI US, and public finance reference controls.
388.14 Government Ethics, Gifts, Lobbying, Public Records, Open Meetings, and Public Sector Confidentiality Training Where Applicable.
388.14.1 Training shall cover lobbying review, political campaign activity controls, nonpartisan public-benefit research and education controls, government ethics, gifts, honoraria, travel support, sponsored attendance, procurement integrity, revolving-door considerations, public official conflicts, public records, FOIA, sunshine, open meetings, public authority confidentiality, privilege, work product, controlled disclosure, and public-safe redaction where applicable.
388.15 State, Territorial, Tribal, Local, and North America Interface Training.
388.15.1 Training shall address jurisdiction-specific and context-specific interface risks, including state localization, territorial localization, Tribal sovereignty, Indigenous governance, protected knowledge, local public authority interfaces, infrastructure interfaces, public records, public-safe mapping, cross-border data, privacy, AI, cyber, export-control, sanctions, controlled technology, and North America role separation.
388.16 Training Records.
388.16.1 The Corporation shall maintain Public Authority Interface Training Records, including training purpose records, director training records, officer training records, staff and contractor training records, fellow / advisor / volunteer / contributor / committee training records, public authority participant orientation records, capacity classification training records, public authority data training records, public authority reference training records, procurement neutrality training records, regulatory boundary training records, public warning and emergency command boundary training records, public finance reader training records, government ethics / gifts / lobbying / public records / open meetings / public sector confidentiality training records, state / territorial / Tribal / local / North America interface training records, attendance records, completion records, renewal records, and archive records.
Section 389. Public Authority Boundary Review, Monitoring, Assurance, and Annual Review
389.1 Boundary Review Purpose.
389.1.1 Public Authority Boundary Review, Monitoring, Assurance, and Annual Review shall provide continuing oversight of the Corporation’s public authority interfaces to ensure that capacity records, public authority data, public authority references, public authority rooms, grants, communications, localization, Tribal and Indigenous interfaces, procurement neutrality, regulator-listening status, public finance reader status, emergency management boundaries, public warning boundaries, incidents, corrections, and enforcement remain effective, current, records-based, and public-safe.
389.1.2 Boundary review shall be risk-based and shall prioritize interfaces involving public authority names or logos, public finance readers, regulators, procurement actors, public safety actors, emergency management actors, public health actors, infrastructure operators, Tribal or Indigenous interfaces, cross-border interfaces, public grants, dashboards, maps, datasets, AI systems, public-good technical assets, public-safe publications, and media communications.
389.2 Capacity Record Review.
389.2.1 Capacity Record Review shall assess whether public authority participants have been correctly classified, whether official capacity records support official references, whether observer status is clear, whether public finance readers and regulator-listening participants are properly labeled, and whether personal-capacity and non-attribution rules are followed.
389.2.2 Defects shall require correction, reclassification, limitation language, public authority confirmation, access restriction, or publication correction where appropriate.
389.3 Public Authority Data Review.
389.3.1 Public Authority Data Review shall assess authority records, capacity records, contribution agreements, permitted use, prohibited use, classification, confidentiality, AI-use restrictions, publication restrictions, transfer restrictions, retention, deletion, public records implications, public-safe release review, and withdrawal or correction requests.
389.3.2 Review shall confirm that public authority data is not used beyond authority, including unauthorized publication, mapping, AI training, embeddings, finance-readiness routing, recognition routing, certification-like use, procurement implication, public warning, or emergency command.
389.4 Public Authority Reference Review.
389.4.1 Public Authority Reference Review shall assess public authority name use, logo use, title use, quote use, attendance references, photographs, recordings, event references, data contribution statements, capacity language, non-endorsement language, public authority approval records, and correction needs.
389.5 Public Authority Room Review.
389.5.1 Public Authority Room Review shall assess room charters, admission criteria, capacity classification, confidentiality terms, public records constraints, data / AI / cyber / privacy controls, competition and antitrust controls, public authority boundary controls, finance and procurement boundary controls, public-safe publication controls, closeout, and room records.
389.6 Public Authority Grant and Funding Review.
389.6.1 Public Authority Grant and Funding Review shall assess public grants, cooperative agreements, government funding, public support, restrictions, compliance, reporting, audit records, data terms, publication terms, funder influence, public authority capture risk, and no-delegation boundary.
389.7 Public Authority Communications Review.
389.7.1 Public Authority Communications Review shall assess briefings, emails, meeting notes, public authority learning materials, media statements, press releases, website content, social media, newsletters, event materials, public-safe summaries, dashboards, maps, and digital channels for public authority boundary compliance.
389.8 State and Territorial Localization Review.
389.8.1 State and Territorial Localization Review shall assess whether materials accurately reflect state-specific, District-specific, territorial, local, public records, procurement, public finance, privacy, AI, cybersecurity, public health, emergency management, infrastructure, language access, and accessibility contexts.
389.8.2 Materials suggesting uniform application across states or territories shall be revised where unsupported.
389.9 Tribal and Indigenous Interface Review.
389.9.1 Tribal and Indigenous Interface Review shall assess sovereignty, governance, consent, non-consent, attribution, withdrawal, restriction, correction, Tribal Data Sovereignty, Indigenous Data Safeguards, Indigenous Knowledge Safeguards, protected knowledge, community protocols, public-safe mapping, AI-use restrictions, and no-assumption-of-representation.
389.10 Public Procurement Neutrality Review.
389.10.1 Public Procurement Neutrality Review shall assess whether publications, rooms, provider interactions, sponsor interactions, technical baselines, dashboards, maps, public-good software, evidence packs, public authority learning, and Nexus-compatible references create procurement advantage, provider preference, vendor qualification, approved vendor lists, procurement scoring, tender advantage, or procurement specification mandates.
389.11 Regulator-Listening Review.
389.11.1 Regulator-Listening Review shall assess whether regulator participation remains listening-only and whether materials avoid regulatory guidance, approval, safe harbor, permit, compliance determination, enforcement position, waiver, policy adoption, public authority endorsement, or reliance on regulator attendance.
389.12 Public Finance Reader Review.
389.12.1 Public Finance Reader Review shall assess whether public finance reader participation remains non-approval, non-commitment, and non-finance-readiness, and whether materials avoid grant approval, budget allocation, appropriation, public finance approval, MDB / DFI approval, public guarantee, public credit, tax credit approval, sovereign obligation, capital commitment, investment advice, rating, and GRA finance-readiness implication.
389.13 Emergency Management and Public Warning Boundary Review.
389.13.1 Emergency Management and Public Warning Boundary Review shall assess whether emergency learning, public safety, public health, public works, public infrastructure, simulations, tabletop exercises, dashboards, maps, sensor signals, AI-RAN signals, DePIN records, digital twins, proof receipts, Truth Engine outputs, and reports remain non-command and non-public-warning.
389.14 Public Authority Incident Review.
389.14.1 Public Authority Incident Review shall assess boundary incidents, overclaims, misdescribed capacity, unauthorized name use, unauthorized logo use, unauthorized quote use, false endorsement, false adoption, false funding approval, false procurement approval, false regulatory approval, false public finance approval, false public warning or emergency command, false PPP or sovereign obligation, corrective actions, recurrence prevention, and closeout.
389.15 Annual Public Authority Boundary Assurance Review.
389.15.1 The Corporation shall conduct an Annual Public Authority Boundary Assurance Review, or more frequent review where risk requires, to assess the effectiveness of Article XIII controls, records, training, incidents, corrections, publications, rooms, public authority data, public authority references, grants, localization, public finance boundaries, regulatory boundaries, procurement neutrality, public warning boundaries, and enforcement.
389.15.2 The Annual Review may result in policy updates, training updates, vocabulary updates, template updates, access-control updates, publication corrections, room governance updates, public authority reference updates, or Board-level recommendations.
389.16 Boundary Review Records.
389.16.1 The Corporation shall maintain Boundary Review Records, including boundary review purpose records, capacity record review records, public authority data review records, public authority reference review records, public authority room review records, public authority grant and funding review records, public authority communications review records, state and territorial localization review records, Tribal and Indigenous interface review records, public procurement neutrality review records, regulator-listening review records, public finance reader review records, emergency management and public warning boundary review records, public authority incident review records, annual public authority boundary assurance review records, findings, corrective actions, Board reports where applicable, and archive records.
Section 390. Public Authority Records and Register
390.1 Public Authority Register Requirement.
390.1.1 The Corporation shall maintain a Public Authority Register or equivalent system sufficient to record, retrieve, audit, review, protect, correct, and archive material public authority interfaces, participants, capacity classifications, official capacity records, observer status records, regulator-listening status records, public finance reader status records, emergency-management participation records, public infrastructure operator participation records, data contributions, reference approvals, room records, public grants, government funding, incidents, corrections, and related access classifications.
390.1.2 The Public Authority Register shall support public authority boundary compliance, public-safe publication, legal review, public records coordination, privacy, cybersecurity, protected knowledge safeguards, procurement neutrality, public finance neutrality, regulatory boundary discipline, emergency command boundary discipline, correctionability, and institutional memory.
390.2 Public Authority Participant Register.
390.2.1 The Public Authority Participant Register shall identify material public authority participants, public officials, public employees, regulators, public finance readers, emergency-management participants, public health participants, public safety participants, public works participants, public infrastructure operator participants, public university actors, public laboratory actors, Tribal / Indigenous government representatives, and other public-sector-affiliated participants.
390.2.2 The register shall include role, authority, capacity, organization, date, activity, access class, attribution status, restrictions, public reference permissions, and correction path where material.
390.3 Capacity Classification Register.
390.3.1 The Capacity Classification Register shall record each material participant’s classification, including official participant, institutional representative, delegated representative, observer, speaker, technical expert, policy discussant, regulator-listening participant, public finance reader, public infrastructure operator participant, emergency-management participant, public health participant, public safety participant, public works participant, academic representative, personal-capacity participant, non-attributable participant, controlled-room participant, data provider, reviewer, simulation / tabletop / exercise / after-action participant, or host authority.
390.4 Official Capacity Register.
390.4.1 The Official Capacity Register shall record written authority, institutional confirmation, scope, limits, attribution permission, approved public language, logo and name use permission, quote permission, data contribution permission, confidentiality limits, public records considerations, legal review, term, expiration, withdrawal, correction, and archive status.
390.5 Observer Register.
390.5.1 The Observer Register shall record observer attendance, learning-only status, access limits, confidentiality, non-attribution where applicable, no-endorsement, no-adoption, no-funding-approval, no-procurement-approval, no-regulatory-approval, no-public-finance-approval, no-public-warning, no-emergency-command, and overclaim corrections.
390.6 Regulator-Listening Register.
390.6.1 The Regulator-Listening Register shall record regulator-listening participants, listening capacity, no-guidance language, no-approval language, no-safe-harbor language, no-permit language, no-compliance-determination language, no-enforcement-position language, no-waiver language, no-policy-adoption language, confidentiality, public records review, reference controls, and corrections.
390.7 Public Finance Reader Register.
390.7.1 The Public Finance Reader Register shall record public finance reader participants, learning or diligence-literacy status, no-grant-approval, no-budget-allocation, no-appropriation, no-public-finance-approval, no-MDB / DFI-approval, no-public-guarantee, no-public-credit, no-tax-credit-approval, no-sovereign-obligation, no-capital-commitment, no-investment-advice, no-GRA-finance-readiness-determination, reference controls, and corrections.
390.8 Emergency-Management Participant Register.
390.8.1 The Emergency-Management Participant Register shall record emergency-management, public safety, public health, public works, public infrastructure, simulation, tabletop, after-action, emergency learning, and related participants, including no-incident-command, no-dispatch, no-evacuation, no-emergency-alert, no-public-warning, no-public-health-order, no-safety-command, no-operational-resource-direction, and no-substitution records.
390.9 Public Infrastructure Operator Register.
390.9.1 The Public Infrastructure Operator Register shall record public infrastructure operators, utilities, ports, airports, transit, transportation, water, energy, telecom, public works, cyber, health-system, and other infrastructure participants, including capacity, technical context contributions, operational context contributions, infrastructure-sensitive data controls, cyber-sensitive data controls, public-safe mapping controls, no-operational-control, no-public-authority-adoption, no-procurement-approval, no-provider-preference, no-public-warning, and no-emergency-command.
390.10 Public Authority Data Contribution Register.
390.10.1 The Public Authority Data Contribution Register shall record authority records, capacity records, contribution agreements, dataset descriptions, permitted uses, prohibited uses, classifications, confidentiality, AI-use restrictions, publication restrictions, retention, deletion, transfer restrictions, public records considerations, public-safe release review, withdrawal requests, correction requests, and archive status.
390.11 Public Authority Reference Approval Register.
390.11.1 The Public Authority Reference Approval Register shall record public authority name use, logo use, title use, quote use, attendance references, photographs, recordings, event references, data contribution statements, official capacity language, observer capacity language, personal capacity language, non-attributable participation language, non-endorsement language, correction records, and expiration or withdrawal.
390.12 Public Authority Room Register.
390.12.1 The Public Authority Room Register shall record public authority rooms, controlled rooms, regulator-listening rooms, public finance reader rooms, emergency learning rooms, data rooms, evidence rooms, clean rooms, and no-download rooms, including room charters, participants, admission criteria, capacity classifications, confidentiality terms, public records review, data / AI / cyber / privacy controls, competition and antitrust controls, boundary controls, public-safe publication controls, closeout, and archive status.
390.13 Public Grant and Government Funding Register.
390.13.1 The Public Grant and Government Funding Register shall record public grants, cooperative agreements, government funding, public support, funding reviews, award terms, restrictions, compliance obligations, reporting obligations, audit obligations, data terms, publication terms, no-public-funder-control records, no-public-grant-as-delegation records, closeout, and archive status.
390.14 Public Authority Incident and Correction Register.
390.14.1 The Public Authority Incident and Correction Register shall record public authority boundary incidents, misdescribed capacity, unauthorized name use, unauthorized logo use, unauthorized quote use, false endorsement, false adoption, false funding approval, false procurement approval, false regulatory approval, false public finance approval, false public warning or emergency command, false PPP or sovereign obligation, incident intake, holds, takedowns, corrections, withdrawals, retractions, public clarifications, public authority notices, legal responses, closeout, and recurrence prevention.
390.15 Retention, Access, Confidentiality, Sealing, Redaction, Archival, and Secure Disposal of Public Authority Records.
390.15.1 Public Authority Records shall be retained, accessed, sealed, redacted, archived, deleted, or securely disposed of according to law, contract, public authority restriction, grant terms, public records considerations, privacy, cybersecurity, protected knowledge safeguards, litigation holds, regulatory holds, audit requirements, correctionability, technical memory, and public-safe publication.
390.15.2 Records involving public authority restricted information, personal information, health-sensitive data, cyber-sensitive information, infrastructure-sensitive information, procurement-sensitive information, finance-sensitive information, privileged material, work product, protected knowledge, confidential materials, or legal risk shall be access-controlled and sealed or redacted where appropriate.
390.15.3 Secure disposal shall not occur where records are subject to legal hold, public authority retention, audit, correction, investigation, incident response, or technical memory requirements.
Section 391. Enforcement of Article XIII
391.1 Article XIII Enforcement Purpose.
391.1.1 Enforcement of Article XIII shall protect public authority boundary integrity, public authority trust, public records discipline, procurement neutrality, regulatory boundary discipline, public finance boundary discipline, public warning and emergency command boundaries, Tribal and Indigenous safeguards, cross-border role separation, public authority data controls, public authority reference controls, public authority room governance, grant compliance, government ethics, lobbying limits, political activity controls, correctionability, and the Corporation’s non-executing public-benefit role.
391.1.2 Enforcement shall be proportionate, records-based, public-safe, conflict-reviewed, and capable of immediate protective action where public authority confusion, public finance reliance, procurement reliance, regulatory reliance, public warning confusion, emergency command confusion, data misuse, protected knowledge exposure, cyber risk, infrastructure risk, or public trust risk requires prompt action.
391.2 Public Authority Capacity Violation Review.
391.2.1 Public Authority Capacity Violation Review shall be initiated where capacity is misstated, omitted, inflated, unsupported, outdated, or inconsistent with official capacity records, observer records, regulator-listening records, public finance reader records, personal-capacity records, non-attribution records, or room records.
391.2.2 Review may require reclassification, public authority confirmation, publication correction, public clarification, controlled clarification, access restriction, or training.
391.3 Public Authority Data Violation Review.
391.3.1 Public Authority Data Violation Review shall be initiated where public authority data is received, used, classified, published, mapped, trained on, embedded, transferred, retained, deleted, summarized, routed, or externally shared beyond authority, permitted use, classification, confidentiality, AI-use restrictions, publication restrictions, transfer restrictions, or public-safe review.
391.3.2 Review may require data hold, publication hold, dashboard hold, map hold, AI hold, repository hold, access restriction, deletion where lawful, public authority notice, incident response, legal review, or corrective action.
391.4 Public Authority Reference Violation Review.
391.4.1 Public Authority Reference Violation Review shall be initiated where public authority names, logos, titles, quotes, attendance references, photographs, recordings, event references, data contribution statements, official capacity language, observer language, personal capacity language, or non-attribution rules are violated.
391.4.2 Review may require reference takedown, correction, public authority notice, public clarification, controlled clarification, mark removal, quote removal, event-page revision, social media correction, or legal review.
391.5 Public Authority Room Violation Review.
391.5.1 Public Authority Room Violation Review shall be initiated where room charters, admission criteria, capacity classifications, confidentiality terms, public records reviews, data / AI / cyber / privacy controls, competition controls, public authority boundary controls, finance and procurement boundary controls, publication controls, or closeout requirements are violated.
391.5.2 Review may require room hold, access restriction, participant removal, data hold, output hold, publication hold, incident response, correction, closeout revision, or training.
391.6 Public Grant or Government Funding Violation Review.
391.6.1 Public Grant or Government Funding Violation Review shall be initiated where grant terms, cooperative agreement terms, public funding restrictions, reporting obligations, audit requirements, data terms, publication terms, lobbying restrictions, political activity restrictions, procurement restrictions, public authority capture controls, or no-delegation rules may have been violated.
391.6.2 Review may require grant compliance action, funder notice, corrective report, repayment assessment, publication correction, access restriction, legal review, audit response, or Board escalation.
391.7 Lobbying, Political Activity, Government Ethics, Gifts, Procurement Integrity, Public Records, or Public Sector Confidentiality Violation Review.
391.7.1 Violation Review shall be initiated where lobbying activity, political campaign activity, government ethics, gifts, honoraria, travel support, sponsored attendance, procurement integrity, revolving-door restrictions, public official conflicts, public records obligations, open meetings considerations, public sector confidentiality, privilege, work product, controlled disclosure, or public-safe redaction may have been violated.
391.7.2 Review may require disclosure, registration review, refund or return of benefit, meeting correction, public official notice, public authority notice, procurement hold, records hold, legal hold, correction, training, suspension, termination, or referral.
391.8 Procurement Neutrality Violation Review.
391.8.1 Procurement Neutrality Violation Review shall be initiated where any activity implies public procurement authority, public contract award authority, vendor selection, preferred provider status, approved vendor list, procurement scoring, procurement specification mandate, tender advantage, bid support as public authority action, provider endorsement, sponsor procurement advantage, or misuse of procurement-sensitive information.
391.8.2 Review may require public authority notice, provider notice, sponsor notice, publication correction, takedown, access restriction, room hold, procurement-sensitive information containment, contract remedy, or legal review.
391.9 Regulatory Boundary Violation Review.
391.9.1 Regulatory Boundary Violation Review shall be initiated where any activity implies regulator status, enforcement authority, permit authority, compliance approval, regulatory safe harbor, legal equivalence by standards mapping, compliance determination by evidence review, regulatory guidance by learning session, authority by regulator-listening participation, or compliance approval through AI, dashboard, map, proof receipt, technical baseline, method, observatory output, or public-good technical asset.
391.9.2 Review may require correction, regulator notice, legal review, publication hold, public clarification, controlled clarification, disclaimer update, vocabulary correction, or training.
391.10 Public Warning, Emergency Command, Public Health Order, or Safety Command Boundary Violation Review.
391.10.1 Violation Review shall be initiated where any activity implies official public warning, emergency alert, evacuation instruction, public health order, safety command, dispatch, incident command, operational resource direction, emergency command, or public authority substitution.
391.10.2 Review may require immediate takedown, dashboard hold, map hold, alert-like design removal, public authority notice, public clarification, controlled clarification, emergency communications review, incident response, or legal referral.
391.11 Public Finance, Budget, Grant, Appropriation, Tax Credit, Public Guarantee, or Sovereign Obligation Boundary Violation Review.
391.11.1 Violation Review shall be initiated where any activity implies public finance approval, budget allocation, appropriation, public grant approval, tax credit approval, MDB / DFI approval, public guarantee, public credit, sovereign obligation, public debt approval, capital commitment, or finance-readiness by GCRI US evidence output.
391.11.2 Review may require public clarification, controlled clarification, GRA notice, public authority notice, funder notice, public finance reader notice, publication correction, access restriction, legal review, withdrawal, or retraction.
391.12 PPP, Intergovernmental, Simulation, Tabletop, Pilot, or Demonstration Overclaim Review.
391.12.1 Overclaim Review shall be initiated where participation, public authority learning, public authority rooms, controlled rooms, pilots, demonstrations, simulations, tabletop exercises, joint exercises, after-action learning, data contributions, or event participation are described as PPP, intergovernmental agreement, joint venture, public adoption, procurement approval, public authority delegation, emergency command, finance approval, certification, recognition, provider preference, sovereign obligation, or execution authority without competent record.
391.12.2 Review may require charter correction, public authority reference correction, public clarification, controlled clarification, takedown, public authority notice, partner notice, sponsor notice, provider notice, access restriction, or legal review.
391.13 Corrective Action.
391.13.1 Corrective action under Article XIII may include capacity reclassification, official capacity confirmation, access restriction, data hold, AI hold, publication hold, room hold, dashboard hold, map hold, repository hold, public authority reference takedown, logo removal, quote removal, correction, supersession, withdrawal, retraction, public clarification, controlled clarification, disclaimer update, vocabulary correction, public authority notice, GRA notice, GRF notice, Nexus Standards notice, funder notice, regulator notice, provider notice, sponsor notice, training, role restriction, suspension, termination, contract remedy, legal referral, regulator referral, funder referral, public authority referral, or law enforcement referral where required or appropriate.
391.13.2 Corrective action shall be proportionate to severity, authority involved, public reliance, public finance risk, procurement risk, regulatory risk, emergency risk, public safety risk, public health risk, cyber risk, infrastructure risk, privacy risk, protected knowledge risk, recurrence, intent, and institutional duty to correct.
391.14 Access Restriction, Publication Hold, Room Hold, Public Authority Reference Takedown, Correction, Supersession, Withdrawal, Retraction, Public Clarification, Suspension, Termination, Contract Remedy, Public Authority Notice, Legal Referral, Regulator Referral, Funder Referral, or Law Enforcement Referral Where Required or Appropriate.
391.14.1 Where required or appropriate, the Corporation may impose immediate or staged remedies, including access restriction, publication hold, room hold, public authority reference takedown, correction, supersession, withdrawal, retraction, public clarification, controlled clarification, suspension, termination, contract remedy, public authority notice, legal referral, regulator referral, funder referral, law enforcement referral, or other remedy authorized by law, contract, policy, or this Bylaw.
391.14.2 Referral and notice actions shall preserve confidentiality, privilege, public-safe communication, privacy, cybersecurity, protected knowledge safeguards, public authority trust, non-retaliation, and legal compliance.
391.15 Enforcement Records.
391.15.1 The Corporation shall maintain Article XIII Enforcement Records, including enforcement purpose records, public authority capacity violation review records, public authority data violation review records, public authority reference violation review records, public authority room violation review records, public grant or government funding violation review records, lobbying / political activity / government ethics / gifts / procurement integrity / public records / public sector confidentiality violation review records, procurement neutrality violation review records, regulatory boundary violation review records, public warning / emergency command / public health order / safety command boundary violation review records, public finance / budget / grant / appropriation / tax credit / public guarantee / sovereign obligation boundary violation review records, PPP / intergovernmental / simulation / tabletop / pilot / demonstration overclaim review records, corrective action records, access restrictions, publication holds, room holds, reference takedowns, corrections, supersessions, withdrawals, retractions, clarifications, suspensions, terminations, contract remedies, notices, referrals, closeout records, recurrence-prevention records, and archive records.
Last updated
Was this helpful?