# XII. SAFEGUARDS This section defines the safeguard conditions that apply to leadership participation, records, communications, handoff, and annual-cycle materials. It sets the rules for protecting sensitive information, carrying safeguard conditions forward, and classifying what may be shared, withheld, corrected, or restricted. It also prevents public-safe work, Nexus Universe visibility, and readiness activity from exposing protected information or creating unsafe public meaning. ## **12.1 Safeguard Principles** ### **12.1.1 Safeguards as Leadership Conditions** **12.1.1.1** Safeguards shall be conditions of National Leadership Council participation, leadership eligibility, leadership-pool consideration, Nexus Universe mobilization, National Model support, National Working Group recommendation, public-safe reporting input, AEP Passport candidate preparation, Nexus Rail candidate preparation, and handoff awareness. **12.1.1.2** Safeguards shall not be treated as secondary compliance items, public-relations language, optional ethical preferences, post-event clean-up tasks, or obstacles to visibility. They are structural conditions for safe public-good leadership. **12.1.1.3** The National Leadership Council shall ensure that participants understand that national Nexus leadership may affect people, communities, public authorities, infrastructure, data systems, markets, ecosystems, capital readers, providers, sponsors, public narratives, and future implementation pathways. Leadership participation therefore carries duties of caution, confidentiality, care, role discipline, restraint, and correction. **12.1.1.4** Safeguards may include privacy, cybersecurity, sovereign data, public authority sensitivity, finance sensitivity, community protection, Indigenous safeguards where applicable, protected knowledge, accessibility, health information, biodiversity-sensitive information, infrastructure-sensitive information, location-sensitive information, commercial sensitivity, procurement neutrality, public-safe reporting, non-extractive participation, and consent-boundary discipline. **12.1.1.5** No person shall be advanced into sensitive leadership, working-group, Nexus Universe, public-safe reporting, National Model, AEP Passport, Rail, or handoff roles without sufficient safeguard orientation, role classification, confidentiality awareness, and claims discipline appropriate to the role. **12.1.1.6** The governing rule shall be: **Safeguards are not after-the-fact protections; they are conditions of leadership readiness.** *** ### **12.1.2 Safeguards Travel With Records** **12.1.2.1** Safeguards shall travel with records. Any record created, received, reviewed, recommended, routed, summarized, published, restricted, corrected, archived, or handed off by or through the National Leadership Council shall carry the safeguard conditions applicable to that record. **12.1.2.2** A safeguard condition shall not disappear because a record is copied into another register, summarized for leadership review, adapted for Nexus Universe, included in the National Model, converted into public-safe language, routed to a Working Group, referenced in a Docket item, used in an AEP Passport candidate note, or prepared for a Nexus Rail pathway. **12.1.2.3** Safeguard conditions may include access limits, publication class, redaction requirements, aggregation requirements, anonymization requirements, data-use limits, consent conditions, public authority status limits, finance-readiness disclaimers, community restrictions, Indigenous or protected-knowledge restrictions where applicable, cyber restrictions, commercial restrictions, and correction obligations. **12.1.2.4** Where a record is excerpted, summarized, translated, visualized, converted into a dashboard, used in a presentation, included in a public-safe report, or incorporated into a handoff note, the receiving format shall preserve the safeguard conditions of the source record unless a competent record lawfully modifies them. **12.1.2.5** The governing rule shall be: **A record cannot outrun the safeguards attached to its source.** *** ### **12.1.3 Safeguards Travel With Handoff** **12.1.3.1** Safeguards shall travel with handoff. Any matter identified for possible handoff to a National Consortium Company, Project SPV, public authority, provider-neutral capability process, finance-readiness pathway, safeguard process, GCRI pathway, GRF pathway, GRA pathway, Regional Nexus Consortium, Global Nexus Consortium, Nexus Observatory, Nexus Rail, AEP Passport pathway, Docket pathway, or other receiving actor shall carry the safeguard conditions attached to the source material. **12.1.3.2** Handoff shall not sanitize, weaken, omit, or erase safeguard conditions. If a matter has unresolved privacy, cyber, sovereign data, community, Indigenous, protected-knowledge, biodiversity, health, infrastructure, security, public authority, finance, commercial, procurement, or consent-boundary issues, those issues shall be stated in the handoff record. **12.1.3.3** The receiving actor shall be informed whether the matter is public-safe, controlled, restricted, confidential, public authority-sensitive, finance-sensitive, safeguard-sensitive, not for publication, or subject to further review. **12.1.3.4** Handoff shall not convert access into permission, visibility into consent, candidate status into approval, finance-readiness into finance, public authority learning into public authority decision, provider contribution into provider validation, or National Model inclusion into execution readiness. **12.1.3.5** The governing rule shall be: **Handoff carries safeguards forward; it does not release a matter from them.** *** ### **12.1.4 Safeguards Apply to Public-Safe Reporting** **12.1.4.1** Safeguards shall apply to public-safe reporting. No public-safe report, public summary, National Model extract, Nexus Universe communication, website listing, media reference, public authority-facing material, investor-facing material, sponsor material, provider material, community-facing material, AEP Passport candidate reference, Nexus Rail reference, Docket note, or handoff note shall be released without safeguard review where the content may create harm, confusion, reliance, exposure, or overclaim. **12.1.4.2** Public-safe reporting shall protect against disclosure of sensitive information and against misleading public meaning. It shall not merely remove confidential details while leaving authority, finance, certification, procurement, consent, provider-validation, or execution overclaims intact. **12.1.4.3** Safeguard review for public-safe reporting shall consider: a) whether the information may be public;\ b) whether the information should be aggregated, anonymized, delayed, redacted, or withheld;\ c) whether public authority status is accurately described;\ d) whether finance-readiness language could create false market reliance;\ e) whether community or Indigenous participation could be misread as consent;\ f) whether technical materials could be misread as certification;\ g) whether provider or sponsor participation could be misread as validation or control;\ h) whether cyber, infrastructure, biodiversity, health, or location-sensitive information could create harm;\ i) whether correction language is required. **12.1.4.4** Public-safe reporting shall not be treated as public warning, public authority action, certification, finance approval, procurement approval, consent, or execution authorization. **12.1.4.5** The governing rule shall be: **Public-safe reporting is safe only when both information exposure and public meaning are controlled.** *** ### **12.1.5 Safeguards Apply to Nexus Universe Materials** **12.1.5.1** Safeguards shall apply to all Nexus Universe materials prepared, reviewed, contributed, summarized, displayed, presented, demonstrated, discussed, or routed with support from the National Leadership Council. **12.1.5.2** Nexus Universe materials may include national themes, priority notes, delegation records, National Model summaries, Government Portfolio Showcase materials, Nexus Core materials, technical demonstrations, provider contributions, sponsor references, public authority room materials, capital-reader room materials, safeguard room materials, AEP Passport candidate notes, Nexus Rail candidate notes, Docket items, public-safe reporting materials, and post-cycle renewal notes. **12.1.5.3** Nexus Universe visibility shall not reduce safeguard obligations. The public-stage character of Nexus Universe may increase the need for safeguards because live-week visibility can amplify overclaim, public reliance, media distortion, provider claims, sponsor narratives, public authority confusion, capital-reader misunderstanding, and community harm. **12.1.5.4** Materials prepared for Nexus Universe shall be classified before use as public, public-safe, controlled, restricted, confidential, public authority-sensitive, finance-sensitive, safeguard-sensitive, not for publication, or archive-only, as applicable. **12.1.5.5** The National Leadership Council shall support pre-live correction, live boundary incident response, and post-cycle correction where Nexus Universe materials create safeguard risk. **12.1.5.6** The governing rule shall be: **Nexus Universe visibility must be earned through safeguard readiness, not used to bypass it.** *** ### **12.1.6 Safeguards Apply to AEP Passport and Rail Inputs** **12.1.6.1** Safeguards shall apply to AEP Passport candidate inputs, Proof Receipt inputs, Nexus Rail candidate inputs, routeability notes, evidence inputs, readiness inputs, handoff inputs, technical inputs, public authority learning inputs, finance-readiness inputs, safeguard inputs, National Model inputs, and Nexus Universe inputs. **12.1.6.2** An AEP Passport candidate or Nexus Rail candidate shall not be advanced, summarized, publicized, displayed, routed, or handed off without retaining relevant safeguard conditions. **12.1.6.3** AEP Passport and Rail inputs shall identify: a) source record;\ b) evidence status;\ c) data classification;\ d) public authority status;\ e) finance-readiness boundary;\ f) technical limitation;\ g) community or Indigenous safeguard issue where applicable;\ h) protected-knowledge condition;\ i) cyber or infrastructure sensitivity;\ j) publication class;\ k) correction pathway. **12.1.6.4** AEP Passport candidacy shall not be represented as issued status. Rail candidacy shall not be represented as execution. Safeguard completeness shall not be assumed because a matter is technically strong, finance-readable, or publicly attractive. **12.1.6.5** The governing rule shall be: **Readiness instruments are trustworthy only when their safeguard conditions are visible and carried forward.** *** ### **12.1.7 Safeguards Apply to National Model Inputs** **12.1.7.1** Safeguards shall apply to all National Model inputs supported, reviewed, prioritized, summarized, or routed by the National Leadership Council. **12.1.7.2** National Model inputs may include leadership records, Helix Council inputs, National Investors Council inputs, National Working Group outputs, public authority materials, technical materials, finance-readiness notes, safeguard notes, community materials, Indigenous materials where applicable, National Consortium Company interface notes, Project SPV-readiness notes, Nexus Universe outputs, AEP Passport candidate notes, Nexus Rail candidate notes, and Docket items. **12.1.7.3** The National Model shall identify whether an input is public-safe, controlled, restricted, confidential, public authority-sensitive, finance-sensitive, safeguard-sensitive, not for publication, or subject to further review. **12.1.7.4** National Model inclusion shall not create public permission, publication permission, data-use permission, protected-knowledge permission, community consent, Indigenous consent, public authority approval, finance approval, certification, procurement status, provider validation, or execution authority. **12.1.7.5** Where a National Model input lacks safeguard readiness, the National Model shall record the gap rather than present the matter as ready. **12.1.7.6** The governing rule shall be: **The National Model must record safeguard status as part of readiness, not as an annex to readiness.** *** ### **12.1.8 Safeguards Apply to Leadership Communications** **12.1.8.1** Safeguards shall apply to leadership communications, including emails, letters, presentations, speeches, biographies, website listings, meeting summaries, media statements, sponsor materials, provider materials, public authority-facing materials, investor-facing materials, community-facing materials, Nexus Universe materials, National Model summaries, public-safe reports, handoff notes, and informal communications that may create reliance. **12.1.8.2** Leadership communications shall respect role classification, claims permission, confidentiality, publication class, public authority status, finance-readiness boundaries, sponsor and provider boundaries, community and Indigenous consent boundaries, protected-knowledge limits, cyber sensitivity, and correction obligations. **12.1.8.3** A participant shall not communicate sensitive, controlled, restricted, confidential, public authority-sensitive, finance-sensitive, safeguard-sensitive, or not-for-publication material without permission. **12.1.8.4** Leadership communications shall not use urgency, seniority, sponsor pressure, public authority interest, media attention, capital-reader demand, or Nexus Universe deadlines to bypass safeguard review. **12.1.8.5** The governing rule shall be: **Leadership communication is part of the safeguard system because language can create harm as much as disclosure can.** *** ### **12.1.9 Safeguards Apply to Enterprise Interfaces** **12.1.9.1** Safeguards shall apply to all enterprise interfaces involving National Consortium Companies, Project SPVs, providers, sponsors, hosts, anchors, partners, operators, contractors, investors, insurers, donors, philanthropies, public finance actors, development actors, and other enterprise-stack or implementation-capable actors. **12.1.9.2** Enterprise interfaces shall not use public-good records to create unsupported commercial claims, provider validation, procurement advantage, finance signal, insurance signal, certification implication, community consent implication, Indigenous consent implication, public authority approval implication, or execution authorization. **12.1.9.3** Any enterprise-interface record shall state the applicable safeguards, including data restrictions, publication limits, confidentiality, public authority dependencies, finance-readiness boundaries, procurement neutrality, provider-neutrality requirements, community or Indigenous consent boundaries where applicable, protected-knowledge restrictions, cyber conditions, technical limitations, and correction pathway. **12.1.9.4** Enterprise actors receiving public-good materials shall not treat access as permission to commercialize, publish, sell, finance, insure, procure, deploy, train systems, market, or execute unless separately authorized. **12.1.9.5** The governing rule shall be: **Enterprise interfaces may receive readiness intelligence only with the safeguards that make the intelligence safe to use.** *** ### **12.1.10 Safeguard Correction** **12.1.10.1** Safeguard correction shall occur where safeguard conditions are omitted, misstated, weakened, bypassed, misunderstood, breached, or overtaken by changed facts. **12.1.10.2** Safeguard correction may be required for records, registers, public-safe reports, National Model inputs, Nexus Universe materials, AEP Passport candidate notes, Nexus Rail candidate notes, Docket items, leadership communications, handoff notes, enterprise-interface materials, public authority-facing materials, investor-facing materials, provider-facing materials, sponsor-facing materials, or community-facing materials. **12.1.10.3** Safeguard correction may include: a) reclassification;\ b) access restriction;\ c) public-safe correction;\ d) redaction;\ e) withdrawal;\ f) supersession;\ g) Docket entry;\ h) participant notice;\ i) recipient notice;\ j) breach response;\ k) referral to competent legal, public authority, technical, safeguard, community, Indigenous, cyber, finance, GRF, GCRI, GRA, regional, or global process;\ l) archive of corrected material. **12.1.10.4** Safeguard correction shall not be delayed to protect reputation, stage visibility, sponsor satisfaction, provider interest, capital-reader expectations, public authority optics, or institutional convenience. **12.1.10.5** The governing rule shall be: **A safeguard system is only real if safeguard errors can be corrected quickly, visibly where necessary, and by record.** *** ## **12.2 Data and Confidentiality** This section defines how personal, public authority-sensitive, commercial, finance-sensitive, provider-sensitive, community-sensitive, Indigenous, cyber, health, biodiversity, infrastructure, and other protected information must be handled. ### **12.2.1 Personal Information** **12.2.1.1** Personal information shall be protected in all National Leadership Council activities. **12.2.1.2** Personal information may include names, contact details, biographies, affiliations, participation history, attendance records, leadership-pool status, eligibility notes, conflict records, conduct records, confidentiality records, safeguard records, correction records, community participation details, public authority role details, finance-reader role details, and any information that identifies or can reasonably identify a person. **12.2.1.3** Personal information shall be collected, used, stored, shared, published, retained, corrected, and archived only for legitimate National Council, National Leadership Council, Nexus Universe, National Model, Working Group, public-safe reporting, leadership-pool, safeguard, or handoff purposes and subject to applicable law, consent requirements, confidentiality obligations, access controls, and publication classifications. **12.2.1.4** Personal information shall not be used for unrelated marketing, sponsor promotion, provider promotion, political promotion, investor targeting, media exploitation, public authority overclaim, profiling, automated decision-making, or unauthorized AI processing. **12.2.1.5** Personal information included in public profiles, website listings, Nexus Universe materials, reports, or public-safe summaries shall be limited to what is necessary, accurate, permitted, and claims-safe. **12.2.1.6** The governing rule shall be: **People are not data assets; personal information must be handled as trust-bearing information.** *** ### **12.2.2 Public Authority-Sensitive Information** **12.2.2.1** Public authority-sensitive information shall be protected where National Leadership Council work involves governments, ministries, municipalities, regulators, public utilities, emergency-management bodies, public finance bodies, public health bodies, environmental authorities, infrastructure authorities, public agencies, public officials, or official processes. **12.2.2.2** Public authority-sensitive information may include policy discussions, draft public authority positions, procurement-sensitive information, public finance information, regulatory questions, emergency-management information, infrastructure information, official correspondence, internal public-sector materials, meeting notes, data-sharing discussions, permit or licence issues, and public authority learning-room records. **12.2.2.3** Such information shall not be disclosed, summarized, quoted, published, used in Nexus Universe materials, used in investor-facing materials, used in sponsor or provider materials, or included in public-safe reporting unless permitted by the relevant classification and review process. **12.2.2.4** Public authority-sensitive information shall not be used to imply public authority approval, adoption, funding, procurement, regulatory comfort, public finance commitment, public warning, emergency command, delegation, permit, licence, or official position. **12.2.2.5** The governing rule shall be: **Public authority-sensitive information may support learning, but it must not become unauthorized public authority meaning.** *** ### **12.2.3 Commercially Sensitive Information** **12.2.3.1** Commercially sensitive information shall be protected where participants, sponsors, providers, National Consortium Companies, Project SPVs, operators, contractors, investors, insurers, donors, universities, or other actors provide non-public commercial, technical, strategic, financial, operational, or proprietary information. **12.2.3.2** Commercially sensitive information may include business plans, pricing, vendor information, technical specifications, product roadmaps, client information, contracts, project models, intellectual property, trade secrets, operating assumptions, market strategy, financial models, diligence materials, and implementation plans. **12.2.3.3** The National Leadership Council shall not use commercially sensitive information to create provider preference, procurement advantage, sponsor advantage, capital advantage, market signal, or unfair competitive effect. **12.2.3.4** Public-good records shall distinguish between independent public-good findings and commercially provided claims or materials. **12.2.3.5** Commercially sensitive information shall be redacted, aggregated, restricted, or excluded from public-safe materials unless publication is permitted. **12.2.3.6** The governing rule shall be: **Commercial information may inform readiness, but it must not distort public-good neutrality or create unfair advantage.** *** ### **12.2.4 Finance-Sensitive Information** **12.2.4.1** Finance-sensitive information shall be protected where National Leadership Council activity involves finance-readiness, capital-readability, insurance-readiness, donor-readiness, public finance relevance, SPV-readiness, National Investors Council inputs, GRA-aligned materials, capital-reader rooms, insurance rooms, donor rooms, philanthropic discussions, or development finance discussions. **12.2.4.2** Finance-sensitive information may include financial models, diligence questions, risk allocation, insurance assumptions, underwriting questions, public finance considerations, donor priorities, philanthropic interests, confidential capital-reader feedback, project finance assumptions, debt or equity concepts, guarantee discussions, and SPV-readiness materials. **12.2.4.3** Finance-sensitive information shall be handled on a non-advisory, no-reliance, non-soliciting, non-transactional, confidentiality-aware, competition-compliant, and regulated-perimeter controlled basis. **12.2.4.4** Finance-sensitive information shall not be used to imply investment approval, financeability, bankability, insurability, underwriting, guarantee, public finance approval, donor approval, philanthropic commitment, rating, lending, brokerage, or transaction readiness. **12.2.4.5** The governing rule shall be: **Finance-sensitive information must improve readiness discipline without creating false financial reliance.** *** ### **12.2.5 Provider-Sensitive Information** **12.2.5.1** Provider-sensitive information shall be protected where providers, vendors, technology companies, operators, systems integrators, manufacturers, infrastructure actors, AI actors, cyber actors, compute actors, telecommunications actors, geospatial actors, data actors, or other enterprise contributors provide non-public information. **12.2.5.2** Provider-sensitive information may include technical designs, architecture, security details, software information, hardware specifications, operational procedures, implementation assumptions, customer information, system limitations, proprietary data, pilot details, commercial models, and demonstration materials. **12.2.5.3** Provider-sensitive information shall not be treated as independent validation. It shall be classified according to source, evidence status, technical limitation, provider claim status, public-safe status, and confidentiality class. **12.2.5.4** Provider-sensitive information shall not be disclosed to competitors, public authorities, investors, sponsors, media, Nexus Universe audiences, or public materials unless permitted by classification and applicable agreements. **12.2.5.5** Provider-sensitive information shall not create provider selection, procurement status, certification, standards conformance, Nexus endorsement, public authority approval, finance-readiness, or execution authority. **12.2.5.6** The governing rule shall be: **Provider-sensitive information may support understanding; it must not become validation, leakage, or procurement advantage.** *** ### **12.2.6 Community-Sensitive Information** **12.2.6.1** Community-sensitive information shall be protected where National Leadership Council activity involves communities, local actors, vulnerable groups, civil society, youth, accessibility concerns, diaspora, place-based knowledge, lived experience, local risk, social vulnerability, or community-facing safeguards. **12.2.6.2** Community-sensitive information may include personal stories, local risk descriptions, location-specific vulnerabilities, community needs, household or livelihood information, social conflict, cultural information, community maps, local infrastructure concerns, service gaps, harm histories, or community trust concerns. **12.2.6.3** Community-sensitive information shall not be extracted, publicized, mapped, commercialized, automated, repurposed, or handed off without appropriate permission, public-safe review, dignity review, consent-boundary review, and safeguard controls. **12.2.6.4** Community participation or information sharing shall not be treated as community consent, social license, publication permission, data permission, project approval, or handoff authorization. **12.2.6.5** Community-sensitive information shall be handled with non-extractive participation discipline and shall avoid converting lived experience into institutional narrative without protection. **12.2.6.6** The governing rule shall be: **Community-sensitive information belongs first to the dignity and safety of the people affected, not to institutional storytelling.** *** ### **12.2.7 Indigenous and Protected Knowledge Where Applicable** **12.2.7.1** Indigenous information, Indigenous data, Indigenous participation records, traditional knowledge, cultural knowledge, protected knowledge, sacred knowledge, place-based knowledge, rights-holder information, or other protected knowledge shall be handled with heightened safeguard discipline where applicable. **12.2.7.2** The National Leadership Council shall not assume that Indigenous participation, community participation, public meeting attendance, consultation attendance, knowledge sharing, map discussion, storytelling, or presence in Nexus Universe creates consent, approval, rights-holder authorization, data permission, publication permission, mapping permission, commercialization permission, operationalization permission, or handoff permission. **12.2.7.3** Indigenous and protected knowledge shall be handled according to applicable law, Indigenous data sovereignty principles where applicable, cultural protocols, consent requirements, confidentiality obligations, public-safe classifications, and rights-holder instructions. **12.2.7.4** Such information shall not be used to train AI systems, build dashboards, create maps, support finance-readiness, justify project readiness, support public authority-facing claims, or enable enterprise handoff unless permitted by the appropriate lawful and ethical pathway. **12.2.7.5** Where the status of Indigenous or protected knowledge is uncertain, the default shall be restricted, not public. **12.2.7.6** The governing rule shall be: **Protected knowledge remains protected unless the proper rights-respecting record says otherwise.** *** ### **12.2.8 Biodiversity, Health, Infrastructure, and Security-Sensitive Information** **12.2.8.1** Biodiversity, health, infrastructure, and security-sensitive information shall be protected where disclosure, aggregation, mapping, dashboarding, publication, or handoff could create harm. **12.2.8.2** Sensitive information may include: a) species locations, habitat data, protected areas, ecosystem vulnerability, or biodiversity-risk data;\ b) health data, public health vulnerabilities, disease-risk information, facility information, or population vulnerability information;\ c) critical infrastructure locations, utility systems, telecommunications networks, energy systems, water systems, transport corridors, emergency assets, or industrial facilities;\ d) security-sensitive information relating to cyber systems, physical security, national security, public safety, supply chains, emergency management, or sensitive installations. **12.2.8.3** Such information shall be reviewed before inclusion in National Model materials, Nexus Observatory outputs, dashboards, Nexus Universe materials, public-safe reporting, AEP Passport candidate notes, Rail pathways, or handoff notes. **12.2.8.4** Public-safe treatment may require aggregation, masking, redaction, delay, controlled-room handling, exclusion, or public authority routing. **12.2.8.5** The governing rule shall be: **High-value risk information can become high-risk information if disclosed without controls.** *** ### **12.2.9 Cyber-Sensitive Information** **12.2.9.1** Cyber-sensitive information shall be protected with heightened discipline across National Leadership Council activity. **12.2.9.2** Cyber-sensitive information may include system architecture, network diagrams, vulnerabilities, threat information, incident details, access credentials, software repositories, model details, API keys, operational procedures, security controls, penetration-testing results, data flows, dependencies, supply-chain information, and critical infrastructure cyber posture. **12.2.9.3** Cyber-sensitive information shall not be included in public-safe reports, Nexus Universe public materials, investor-facing materials, sponsor materials, provider materials, media materials, or public dashboards unless reviewed and approved for release. **12.2.9.4** Cyber-sensitive information shall not be uploaded into unauthorized tools, shared through unsecured channels, copied into uncontrolled files, or used for AI processing without approved controls. **12.2.9.5** Cyber-sensitive materials may require restricted rooms, need-to-know access, redaction, aggregation, technical review, and incident-response pathways. **12.2.9.6** The governing rule shall be: **Cyber-sensitive information must be protected because publication can create attack surface.** *** ### **12.2.10 Confidentiality Breach Correction** **12.2.10.1** Any suspected or confirmed confidentiality breach shall be corrected through an appropriate breach-response and correction process. **12.2.10.2** A confidentiality breach may include unauthorized disclosure, publication, copying, forwarding, uploading, summarizing, AI processing, media sharing, investor sharing, sponsor sharing, provider sharing, public authority sharing, community disclosure, protected-knowledge disclosure, cyber disclosure, or inference-based disclosure of restricted information. **12.2.10.3** Breach correction may include: a) containment;\ b) access suspension;\ c) recipient notice;\ d) participant notice;\ e) retrieval or deletion request;\ f) public-safe correction;\ g) reclassification;\ h) Docket entry;\ i) legal review;\ j) public authority notice where required;\ k) community or Indigenous notice where appropriate;\ l) cyber response where relevant;\ m) standing review;\ n) leadership eligibility restriction;\ o) archive and prevention record. **12.2.10.4** Breach correction shall be proportionate to risk, audience, sensitivity, legal requirements, and harm potential. **12.2.10.5** A participant who breaches confidentiality may be restricted, suspended, removed from leadership-pool consideration, excluded from sensitive rooms, or referred to a competent process. **12.2.10.6** The governing rule shall be: **Confidentiality breaches must be contained, corrected, recorded, and prevented from repeating.** *** ## **12.3 Publication Classification** This section defines the release classes that control who may access, share, summarize, publish, reclassify, correct, or withdraw material. ### **12.3.1 Public** **12.3.1.1** **Public** materials may be made available without access restriction because they have been reviewed and determined suitable for general public release. **12.3.1.2** Public classification may apply to approved website text, public summaries, general participation descriptions, public-safe reports approved for public release, event announcements, public agendas, approved press materials, and other materials cleared for unrestricted communication. **12.3.1.3** Public classification shall not mean that the material may be modified, quoted out of context, used for endorsement, converted into finance claims, converted into public authority claims, or used for provider, sponsor, or participant overclaim. **12.3.1.4** Public materials shall remain subject to correction, supersession, withdrawal, and archive where inaccuracies, changed facts, overclaims, or safeguard issues arise. **12.3.1.5** The governing rule shall be: **Public does not mean uncontrolled meaning; even public materials must remain claims-disciplined and correctable.** *** ### **12.3.2 Public-Safe** **12.3.2.1** **Public-Safe** materials may be released to public or external audiences only because they have been reviewed to ensure that the information and its public meaning are safe for the intended audience. **12.3.2.2** Public-Safe classification may apply to summaries, extracts, reports, public-facing National Model materials, Nexus Universe communications, public authority learning summaries, finance-readiness summaries, community-facing summaries, technical summaries, AEP Passport candidate references, Nexus Rail references, and Docket summaries. **12.3.2.3** Public-Safe classification may require disclaimers, role labels, public authority status labels, finance-readiness no-reliance language, sponsor and provider boundary language, community and Indigenous consent-boundary language, redactions, aggregation, or exclusion of sensitive details. **12.3.2.4** Public-Safe materials shall not be treated as unrestricted if they were cleared for a particular audience, timing, purpose, or context. **12.3.2.5** The governing rule shall be: **Public-Safe means safe for the stated purpose, audience, and claims limits—not free for all reuse.** *** ### **12.3.3 Controlled** **12.3.3.1** **Controlled** materials may be shared only with defined recipients for defined purposes under access, confidentiality, claims, and handling conditions. **12.3.3.2** Controlled classification may apply to meeting notes, participant lists, leadership-pool materials, draft National Model materials, Nexus Universe preparation materials, working-group outputs, public authority learning materials, finance-readiness notes, safeguard notes, technical materials, and handoff candidates that are not suitable for general release. **12.3.3.3** Controlled materials may be summarized, excerpted, or discussed only as permitted by the classification record. **12.3.3.4** Controlled materials shall not be forwarded, uploaded, republished, used in media, used in investor materials, used in sponsor materials, used in provider materials, or used in public authority-facing materials unless permitted. **12.3.3.5** The governing rule shall be: **Controlled means purpose-limited access with controlled onward use.** *** ### **12.3.4 Restricted** **12.3.4.1** **Restricted** materials may be shared only on a strict need-to-know basis with specifically authorized persons or bodies. **12.3.4.2** Restricted classification may apply to sensitive leadership-pool records, conflict records, conduct records, public authority-sensitive information, finance-sensitive information, community-sensitive information, Indigenous or protected-knowledge materials where applicable, cyber-sensitive materials, critical infrastructure information, health information, biodiversity-sensitive information, commercially sensitive information, and sensitive handoff notes. **12.3.4.3** Restricted materials shall not be included in general meeting packs, public-safe reports, Nexus Universe public materials, website listings, media materials, sponsor materials, provider materials, investor materials, or public authority-facing materials without reclassification or approved redaction. **12.3.4.4** Restricted access shall be logged where appropriate, and unauthorized disclosure shall trigger breach correction. **12.3.4.5** The governing rule shall be: **Restricted information is shared only because a defined role needs it, not because a participant is generally trusted.** *** ### **12.3.5 Confidential** **12.3.5.1** **Confidential** materials shall be protected from unauthorized access, disclosure, copying, publication, external use, AI processing, or onward sharing. **12.3.5.2** Confidential classification may apply to records involving personal information, leadership eligibility, conflicts, conduct, private institutional communications, legal materials, non-public public authority materials, finance-sensitive materials, proprietary information, protected knowledge, cyber-sensitive information, community-sensitive information, and internal GRF/GCRI/GRA materials. **12.3.5.3** Confidential materials shall be handled according to applicable confidentiality undertakings, legal obligations, technical controls, access controls, retention rules, and breach response requirements. **12.3.5.4** Confidential materials may not be converted into public-safe materials without review, redaction, reclassification, and approval. **12.3.5.5** The governing rule shall be: **Confidential means protected until a competent process changes the classification.** *** ### **12.3.6 Public Authority-Sensitive** **12.3.6.1** **Public Authority-Sensitive** materials involve public authorities, official processes, public-sector learning, public finance, procurement, regulation, emergency management, public health, infrastructure, public utilities, or other governmental or statutory contexts requiring heightened classification. **12.3.6.2** Public Authority-Sensitive materials may include official correspondence, public authority participation records, policy discussions, regulatory questions, procurement-sensitive materials, public finance discussions, emergency-management information, public warning-related information, infrastructure records, data-sharing materials, and public authority learning-room outputs. **12.3.6.3** Such materials shall not be used to imply approval, adoption, funding, procurement, regulation, delegation, public warning, emergency command, or official position unless a lawful public authority record supports the claim. **12.3.6.4** Release of Public Authority-Sensitive materials shall require capacity classification, public-safe review, claims review, and any required public authority permission. **12.3.6.5** The governing rule shall be: **Public Authority-Sensitive material must protect both the public authority and the public from false official meaning.** *** ### **12.3.7 Finance-Sensitive** **12.3.7.1** **Finance-Sensitive** materials involve finance-readiness, capital-readability, insurance-readiness, public finance relevance, donor relevance, philanthropic relevance, SPV-readiness, risk allocation, diligence, guarantees, ratings, investment, lending, insurance, underwriting, or transaction-adjacent matters. **12.3.7.2** Finance-Sensitive materials shall be handled on a non-advisory, no-reliance, non-soliciting, non-transactional, confidentiality-aware, competition-compliant, and regulated-perimeter controlled basis. **12.3.7.3** Finance-Sensitive materials shall not be released or summarized in a manner that creates false investment interest, finance approval, bankability, financeability, insurability, underwriting, guarantee, rating, public finance approval, donor approval, philanthropic commitment, or transaction readiness. **12.3.7.4** Finance-Sensitive material may require controlled rooms, restricted circulation, disclaimers, redaction, and review by competent finance-readiness or legal functions. **12.3.7.5** The governing rule shall be: **Finance-Sensitive information must not become a false market signal.** *** ### **12.3.8 Safeguard-Sensitive** **12.3.8.1** **Safeguard-Sensitive** materials involve privacy, cybersecurity, sovereign data, community protection, Indigenous safeguards where applicable, protected knowledge, accessibility, health information, biodiversity-sensitive information, critical infrastructure information, location-sensitive information, vulnerable populations, public-safe reporting limits, consent boundaries, or non-extractive participation requirements. **12.3.8.2** Safeguard-Sensitive materials shall be reviewed before any sharing, summarization, publication, Nexus Universe use, National Model inclusion, AEP Passport use, Rail use, Docket use, or handoff. **12.3.8.3** Safeguard-Sensitive materials may require restricted access, redaction, aggregation, anonymization, delay, exclusion, rights-holder review, community review, Indigenous review where applicable, public authority routing, cyber review, legal review, or public-safe review. **12.3.8.4** Safeguard-Sensitive classification shall remain attached to derived materials unless a competent process reclassifies them. **12.3.8.5** The governing rule shall be: **Safeguard-Sensitive material remains sensitive even when summarized, visualized, or routed.** *** ### **12.3.9 Not for Publication** **12.3.9.1** **Not for Publication** materials shall not be published, posted, quoted, externally circulated, used in public presentations, used in media, used in sponsor materials, used in provider materials, used in investor-facing materials, used in public authority-facing materials, or used in Nexus Universe public materials. **12.3.9.2** Not for Publication classification may apply to drafts, internal notes, conflict materials, leadership-pool records, sensitive National Model materials, public authority-sensitive materials, finance-sensitive materials, safeguard-sensitive materials, protected knowledge, confidential technical materials, cyber-sensitive materials, and correction records. **12.3.9.3** Not for Publication materials may still be used internally, in controlled rooms, or in restricted processes if the classification permits such use. **12.3.9.4** A Not for Publication material may become public-safe only through review, reclassification, redaction where appropriate, approval, and correction of any overclaim. **12.3.9.5** The governing rule shall be: **Not for Publication means no external public use unless a competent reclassification record changes that status.** *** ### **12.3.10 Reclassification and Correction** **12.3.10.1** Publication classification shall be reclassified or corrected where facts change, errors are found, sensitivity increases, sensitivity decreases, public-safe language is approved, consent or authorization is obtained, public authority status changes, finance-readiness status changes, safeguard conditions change, or a prior classification is found to be unsafe or inaccurate. **12.3.10.2** Reclassification may move material from confidential to restricted, restricted to controlled, controlled to public-safe, public-safe to public, public to corrected public, public to withdrawn, or any other appropriate classification according to the competent record. **12.3.10.3** Reclassification shall identify: a) original classification;\ b) new classification;\ c) reason for change;\ d) approving body or process;\ e) affected materials;\ f) permitted uses;\ g) prohibited uses;\ h) claims limits;\ i) required notices;\ j) correction and archive requirements. **12.3.10.4** Where material was released under an incorrect classification, correction shall include assessment of whether public clarification, recipient notice, withdrawal, redaction, access restriction, breach response, or Docket entry is required. **12.3.10.5** The governing rule shall be: **Classification is not static; it must change when safety, accuracy, authority, or public meaning changes.** ### Related topics * [X. RECORDS](/organization/cooperation/consortiums/gateways/national-councils/leadership/x.-records.md) — the records and registers that carry safeguard conditions, classifications, and correction history. * [XI. CLAIMS](/organization/cooperation/consortiums/gateways/national-councils/leadership/xi.-claims.md) — the claims and communications rules that keep public language aligned with safeguard limits. * [XV. CORRECTION](/organization/cooperation/consortiums/gateways/national-councils/leadership/xv.-correction.md) — correction, withdrawal, supersession, and archive rules when safeguard failures or unsafe disclosures occur. ### Summary This section defines the safeguards that protect people, institutions, records, and public meaning across leadership activity. It also defines how sensitive information is classified, restricted, published, corrected, and carried forward without turning readiness work into unsafe disclosure or false authority. ### Next steps 1. Review [X. RECORDS](/organization/cooperation/consortiums/gateways/national-councils/leadership/x.-records.md) to confirm where safeguard status, publication class, and correction history are recorded. 2. Review [XI. CLAIMS](/organization/cooperation/consortiums/gateways/national-councils/leadership/xi.-claims.md) before using safeguarded material in public, sponsor-facing, provider-facing, or public authority-facing communications. 3. Review [XV. CORRECTION](/organization/cooperation/consortiums/gateways/national-councils/leadership/xv.-correction.md) for how to correct, restrict, withdraw, or supersede unsafe or inaccurate materials. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.therisk.global/organization/cooperation/consortiums/gateways/national-councils/leadership/xii.-safeguards.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.