Stewardship Charter Plain-Language Public Edition v3.2 Public Draft Notice This is the first public draft of the Stewardship Charter (Plain-Language Public Edition). It is subject to amendment for clarity, formatting, definitions, and implementation detail. The platform invariants and constraint logic are fixed and are not subject to amendment. Any changes will be published with a dated version number and a public change log. Purpose This Stewardship Charter governs CTMP infrastructure. Its purpose is to keep essential outputs, meaning electricity and fresh water, stable, affordable, and verifiable over decades, across territories, and across leadership changes. It does this by making rent extraction structurally difficult and easy to detect. The Charter does not claim sovereignty. It does not govern people. It does not claim authority over taxation. It governs the infrastructure and the terms under which the infrastructure connects to participants, markets, and downstream systems. The Charter operates within applicable law in every jurisdiction where CTMP operates. It is incorporated through project documentation, operating conditions, and participant agreements. CTMP complies with local law. If local law would require conduct that breaks Charter invariants, or if host-imposed charges make Charter ceilings unattainable, CTMP cannot provide CTMP Verified status for the affected delivery chain(s) in that jurisdiction, and the reporting record reflects that limitation. This preserves the integrity of the invariants without claiming authority over sovereign law or sovereign taxation. Participation is voluntary. Anyone can decline. Anyone who connects does so under the same published constraints, with no special lanes. Part One: Definitions These definitions apply throughout the Charter. Auditable means publicly accessible and sufficiently itemized that an independent reviewer can reproduce the end user price from the published retail schedule without relying on undisclosed side agreements. Ceiling means the maximum permitted end user price for Core electricity or Core Water outputs represented as CTMP Verified, inclusive of all charges paid by the end user. The public default ceiling for electricity is US$0.05 per kilowatt-hour. If host taxes, surcharges, or regulated charges would cause the end user price to exceed the ceiling, CTMP Verified status cannot be provided for that delivery chain and outputs are reported as Not CTMP Verified. Core means the primary electricity production system delivering firm power under a posted tariff. Core Water means fresh water delivered under the CTMP program, metered at the defined delivery point specified in host operating conditions. CTMP Verified means an output is traceable to CTMP operations, is logged at the applicable metering or custody boundary, and is covered by independent attestation that is current. For Core electricity and Core Water, CTMP Verified additionally requires a published, auditable retail schedule for the delivery chain that keeps end user prices within the applicable ceiling. For non-essential vertical outputs, CTMP Verified does not imply any price ceiling. It requires public price disclosure when CTMP name, marks, or CTMP Verified claims are used and requires a published product specification and QA basis for the claim. Current means within the attestation cadence specified in host operating conditions or published verification program rules. Custody boundary means the defined point where custody, ownership, or billing responsibility for a non-essential vertical output transfers, and where the transfer is logged for verification purposes. This boundary is specified in the applicable product specification and reporting rules. Delivery chain means the identifiable path by which CTMP output moves from the metered delivery point to an end user, including any intermediary billing entity, distributor, retailer, or reseller. Verification status, ceilings, and retail schedule requirements are assessed per delivery chain. Disputed means a participant has contested a published CTMP status clarification in writing, and the affected output is treated as Not CTMP Verified pending independent attestation. Distribution allowance means the charges that local distribution utilities may apply for delivery of Core Water from the municipal boundary to end users. Distribution charges are permitted only as audited cost recovery under a published distribution schedule, independently reviewed on a defined cadence. Distribution charges may not be used as an extraction surface. End user price means the total amount paid by the final consumer for CTMP-derived electricity or water, including all charges, fees, taxes, surcharges, and costs of any kind from any source. Independent attestation means verification by qualified third parties independent of the participant and CTMP operations. Material means material under published CTMP reporting rules, which may vary by product class and market and are applied consistently across participants. Metered delivery point means the defined boundary where CTMP outputs are measured and responsibility transfers. The posted tariff and posted water schedule apply at this boundary. CTMP Verified status additionally requires that downstream retail schedules remain within ceilings for Core electricity and Core Water. Network status means the compliance state of a participant within the CTMP system. The three network statuses are Compliance, Continuity, and Exit, each defined in Part Four. Non-essential vertical outputs means outputs from CTMP verticals other than Core electricity and Core Water. Not CTMP Verified means outputs that may still originate from CTMP operations but cannot be represented as CTMP Verified because required publication, auditability, traceability, QA basis, or independent attestation is not current, or because a Core electricity or Core Water delivery chain retail schedule exceeds ceilings. Out of Network means a facility or output operating outside CTMP terms due to Exit status, seizure, override, or nationalization. CTMP does not attest to Out of Network pricing, quality, safety, or auditability. Participant means any party that receives CTMP outputs under CTMP terms, including governments, utilities, industrial users, commercial users, and downstream distributors. Persistent means continuing after written notice and a reasonable opportunity to cure, or repeating after cure. The reporting record logs notice, cure steps, and outcomes. Posted tariff means the published price for Core electricity at the metered delivery point. The current posted tariff is US$0.025 per kilowatt-hour. Posted water schedule means the published price schedule for Core Water at the metered delivery point, including any essential-use provisions, volume tiers, distribution allowances, and ceiling constraints. Product specification means the publicly published CTMP specification for a non-essential vertical output, including grade or class, key properties, tolerances, and custody-boundary identification. Public price disclosure means a publicly accessible price sheet or schedule stating the item, unit, price, effective date, and seller identity, updated when pricing changes. QA basis means the publicly published quality assurance basis for a non-essential vertical output, including test methods, sampling cadence, acceptance criteria, and traceability requirements. Reporting record means the publicly accessible CTMP reporting log where network status, verification status, notices, cure steps, remediation actions, outcomes, and status changes are recorded. Reporting rules means the publicly published CTMP reporting rules that define required logs, fields, formats, publication cadence, and materiality criteria. Retail schedule means the published set of prices, fees, taxes, and rules that determine the end user price for a delivery chain, including all components that can increase what the end user pays and any time-of-use, tiering, demand charges, fixed charges, or pass-through rules. Safe mode means a defined operational state in which the SLE suspends normal processing to protect infrastructure integrity and human safety, without modifying tariffs, ceilings, allocation rules, or Charter constraints. Sovereign Logic Engine (SLE) means the deterministic enforcement system that applies Charter constraints automatically, including metering, logging, compliance detection, network status updates, and verification status assignment. The term ‘sovereign’ in this context refers to the system’s non-discretionary constraint enforcement and immunity to capture; it is not a claim of state authority, jurisdiction, taxation authority, or sovereignty over people. Vertical means a CTMP-operated business unit that produces outputs using Core power, such as desalination, steel production, concrete production, fertilizer production, or other industrial activities integrated into the platform. Part Two: Scope This Charter applies to the Core electricity infrastructure and its delivery interfaces. It applies to fresh water outputs produced under the CTMP program using Core power. It applies to all CTMP verticals and to the interfaces where outputs are metered, allocated, delivered, and billed. It applies to internal transfers between CTMP verticals, because internal tolls are a common entry point for rent extraction. A system that constrains external pricing but permits internal markups will eventually see margins migrate inward. The Charter prevents this. It applies to the reporting and verification systems that make compliance observable. It applies to the use of CTMP name, marks, and representations in public communications. It applies to the Sovereign Logic Engine and its enforcement of Charter constraints. It applies to the full delivery chain from CTMP production to end user consumption for purposes of CTMP Verified status on Core electricity and Core Water. No participant, utility, or intermediary may represent Core electricity or Core Water outputs as CTMP Verified if the end user price exceeds the applicable ceiling. If host-imposed charges make the ceiling unattainable, the output must be treated as Not CTMP Verified and reported as such. The Charter does not apply to activities entirely outside the CTMP network, to outputs that have exited CTMP terms, or to uses that occur after outputs have been legitimately purchased at the posted tariff or posted water schedule for personal consumption. Part Three: Platform Invariants These constraints are fixed for CTMP terms. CTMP complies with local law. If applicable law would require CTMP to violate an invariant, or if host-imposed charges make ceiling compliance impossible for Core electricity or Core Water, CTMP cannot provide CTMP Verified status for the affected delivery chain(s) in that jurisdiction, and the reporting record reflects that limitation. Invariant One: No rent extraction surfaces. Core electricity and Core Water outputs may not become rent extraction surfaces within CTMP Verified delivery chains. No participant, operator, affiliate, utility, or intermediary may use fees, bundling, priority queues, rebates, side payments, affiliate billing, or any other mechanism that functions to increase the end user price above the applicable ceiling while representing Core electricity or Core Water outputs as CTMP Verified. The test is what the end user pays. If that amount exceeds the ceiling, the output cannot be represented as CTMP Verified. Host charges may exist under law. Governments can tax. CTMP does not claim authority over taxation. But if host-imposed charges cause the end user price to exceed the ceiling, CTMP Verified status cannot be provided for that delivery chain, and the output must be reported as Not CTMP Verified. Invariant Two: No debt and no liens. No CTMP platform asset may be financed with debt. No party may hold a lien, security interest, or equivalent encumbrance over CTMP assets, CTMP outputs, or CTMP receivables. This invariant exists because debt and liens become control surfaces. A lender with security over assets has leverage. Leverage becomes influence. Influence becomes capture. Capture becomes rent. The Charter eliminates the entry vector by prohibiting the instrument. This constraint applies platform-wide, not just to the Core. A vertical that finances its expansion with secured debt has introduced a capture pathway into the system, even if the Core remains unencumbered. This does not refer to ordinary trade payables incurred in operations that are unsecured and do not grant control rights, nor to compliance obligations that do not encumber CTMP assets or receivables. Any instrument that creates control leverage, security over assets, or claim priority over outputs is prohibited. Invariant Three: Transparency is mandatory. Every kilowatt-hour delivered and every cubic meter of Core Water delivered under CTMP terms must be metered, time-stamped, logged, and verifiable. Verification operates through four layers: the Charter text itself, which makes constraints unambiguous; aggregated public reporting of outputs; independent attestation by qualified third parties; and tamper-evident commitments that make unauthorized changes detectable. End user pricing compliance for Core electricity and Core Water is verified through published retail schedules, itemized billing structures, independent attestation, and audit sampling. CTMP does not require surveillance of individual household transactions. It requires that the retail schedule be published, auditable, and verified to remain within ceilings. If an output cannot be verified through these layers, it is not treated as compliant delivery under CTMP terms and cannot be represented as CTMP Verified. Invariant Four: No special lanes. There are no side deals that weaken published constraints. There are no exceptions sold for influence. There are no preferential terms available to parties with leverage that are unavailable to parties without leverage. If a participant requires an exception to pricing constraints, ceiling constraints, audit requirements, or financing constraints, they are not compatible with the platform. The appropriate response is to decline participation, not to negotiate an exception. Part Four: Network Status and Enforcement Enforcement under this Charter operates through network status and verification status, not through physical control of outputs. The Charter does not authorize hostage behavior. Hospitals, water systems, and life safety infrastructure are not bargaining chips. No consequence under this Charter is designed or executed as a life-critical interruption of power or water as an enforcement tool. Safety events and force majeure are handled under separate operating safety procedures and are logged. The platform recognizes three network statuses. Network status determines eligibility for CTMP integrations, expansion, priority allocations, ecosystem services, and inclusion in attestations; verification status determines whether specific outputs may be labeled CTMP Verified. Compliance status Compliance status means the participant receives CTMP outputs under full CTMP terms. This includes posted tariff pricing at the metered delivery point, posted water schedule pricing, integration with other CTMP systems and verticals, eligibility for capacity expansion, access to CTMP ecosystem services, inclusion in CTMP attestations and reporting, and the right to represent outputs as CTMP Verified where applicable requirements are met. Compliance status requires that published retail schedules for Core electricity and Core Water be submitted to independent attestation. Eligibility for capacity expansion, priority allocations, ecosystem services tied to growth, and inclusion in promotional attestations applies only to delivery chains that are CTMP Verified. Delivery chains that are Not CTMP Verified are ineligible for expansion and are excluded from promotional attestations until restored. Continuity status Continuity status means life-critical delivery continues as defined in host operating conditions, but CTMP membership benefits are suspended. Outputs remain metered and logged. The participant pays for what they receive at published rates. But there are no special allocations, no preferential pricing beyond the baseline, no expansion eligibility, no integration with other CTMP systems, and no inclusion in CTMP promotional attestations. Outputs delivered under Continuity status may still be represented as CTMP Verified if applicable requirements are met. Continuity delivery is limited to essential-use allocations and life-safety service levels defined in host operating conditions and is reviewed on a defined cadence until remediation is completed. Remediation and re-entry Continuity status includes a documented remediation path. When violations are cured and independently attested, network status may return to Compliance. Re-entry requires that published retail pricing for Core electricity and Core Water is restored within ceiling limits, that any prohibited charges or extraction mechanisms have been removed, and that full auditability is in place. Public re-entry summary Upon re-entry, CTMP posts a public summary in the reporting record describing (1) the delivery chain affected, (2) the category of violation, (3) the effective date the cure took effect, and (4) the control implemented to prevent recurrence. This summary is public-facing and does not require publication of sensitive internal communications, security details, or proprietary systems. Exit status Exit status means the participant has left the CTMP network. Exit status is triggered only by (1) seizure, override, or nationalization of CTMP facilities, or (2) persistent misrepresentation of CTMP Verified status combined with persistent refusal to publish and submit required retail schedules or product specifications to independent attestation. Exit status is not triggered by the mere existence of host-imposed charges that exceed ceilings. If host-imposed charges make ceiling compliance unattainable for Core electricity or Core Water, CTMP Verified status cannot be provided for that delivery chain and outputs are reported as Not CTMP Verified. The participant remains in the network but cannot claim CTMP Verified status for those outputs. When Exit status occurs, the transition is immediate and recorded in the reporting record. The exited participant no longer receives CTMP terms, CTMP integrations, CTMP supply chain access, CTMP technical support, CTMP attestations, or CTMP ecosystem benefits. Outputs from Exit status facilities are labeled Out of Network. CTMP makes no attestation regarding Out of Network pricing, quality, safety, or auditability. Exit status does not prevent physical operation; it removes eligibility for CTMP terms and for CTMP Verified representations. Part Five: Verification Status and Labeling CTMP uses two distinct status systems: network status and verification status. They serve different purposes and must not be confused. Network status describes whether a participant is part of the CTMP network. The three network statuses are Compliance, Continuity, and Exit. Verification status describes whether specific outputs can be represented as CTMP Verified. Outputs may be CTMP Verified, Not CTMP Verified, Disputed, or Out of Network. If a retail schedule for Core electricity or Core Water is not published, if it is not auditable, or if independent attestation is not current, verification status for the affected delivery chain defaults to Not CTMP Verified until publication, auditability, and attestation are restored. This default rule is automatic and does not require a dispute process. If a non-essential vertical output lacks public price disclosure where CTMP name, marks, or CTMP Verified claims are used, or lacks a published product specification and QA basis, or is not logged at the applicable custody boundary, or independent attestation is not current, verification status defaults to Not CTMP Verified until these requirements are restored. A participant in Compliance or Continuity status may still have some outputs labeled Not CTMP Verified if the retail schedule for those Core electricity or Core Water delivery chains exceeds ceilings or fails to meet publication and attestation requirements, or if non-essential vertical outputs fail to meet disclosure and QA requirements. This is a verification limitation, not a network separation. The participant remains in the network but cannot claim CTMP Verified status for outputs where applicable requirements are not met. Only outputs that meet all applicable CTMP Verified requirements may be reported as CTMP Verified. For Core electricity and Core Water, this means the output is metered and logged at the metered delivery point, sold under a published and auditable retail schedule that keeps end user prices within the ceiling, and verified by independent attestation that is current. For non-essential vertical outputs, this means the output is traceable to CTMP operations, logged at the applicable custody boundary, covered by current independent attestation, has public price disclosure where CTMP name, marks, or CTMP Verified claims are used, and has a published product specification and QA basis. Outputs that do not meet applicable requirements are labeled Not CTMP Verified. This label indicates that the outputs originate from CTMP operations but cannot carry the CTMP Verified designation because applicable requirements are not met. Outputs from Exit status facilities are labeled Out of Network. CTMP makes no attestation regarding Out of Network outputs. It does not verify their pricing. It does not verify their quality. It does not verify their safety or auditability. The Out of Network label is a statement of fact, not a judgment. It means CTMP has no visibility into the output and takes no responsibility for it. This labeling system allows trade partners, investors, downstream users, and the public to distinguish between verified CTMP outputs, outputs that originate from CTMP but cannot be verified due to unmet requirements, and outputs from facilities that have exited the network entirely. Part Six: Use of CTMP Name and Representations The CTMP name, the phrase "CTMP Verified," the posted tariff figures, and any claim of Charter governance are protected representations that may only be used accurately. Participants may not represent Out of Network power or water as CTMP priced, CTMP Verified, tariff-locked, or Charter-governed. This applies to governments, utilities, resellers, and any other party that handles outputs after they leave the CTMP system. Participants may not claim CTMP Verified status for Core electricity or Core Water while selling under retail schedules that push end user prices above the ceiling or that are not published and auditable with current attestation. Any delivery chain where retail schedules exceed ceilings or fail auditability requirements must be represented as Not CTMP Verified. Participants may not claim CTMP Verified status for non-essential vertical outputs without public price disclosure, published product specification, QA basis, and current independent attestation. Misrepresentation is addressed through the reporting record. CTMP will publish a status clarification based on metering, verification records, and published retail schedules or product specifications. If material facts are disputed by the participant in writing, CTMP will label the output Disputed pending independent attestation. This approach resolves disputes through evidence rather than assertion. Persistent misrepresentation combined with refusal to submit retail schedules or product specifications to independent attestation triggers Exit status. This is the boundary between verification limitations and network separation. A participant who cannot meet ceiling requirements for Core electricity or Core Water due to host-imposed charges remains in the network but cannot claim CTMP Verified status. A participant who persistently refuses auditability while claiming CTMP Verified status has chosen to exit the network. This provision exists because extraction disguised as any form of add-on charge, or seizure without consequence, would allow a bad actor to capture CTMP benefits while violating CTMP terms. The Charter cannot prevent a government from taxing. But it can prevent outputs from being claimed as CTMP Verified when they do not meet verification requirements. Physical control of assets and sovereign taxing authority do not confer the right to claim CTMP Verified status. That claim requires actual compliance with verification requirements. Part Seven: Electricity Pricing Core electricity has a posted tariff of US$0.025 per kilowatt-hour at the metered delivery point. This is a system constraint, not an operator policy. Under CTMP terms, the posted tariff is fixed and cannot be changed by participant or operator discretion. Core-derived electricity may not be represented as CTMP Verified if sold to end users above the ceiling. The public default ceiling is US$0.05 per kilowatt-hour, inclusive of all charges paid by the end user. Host charges may exist under law. Governments can tax. CTMP does not claim authority over taxation. But if host-imposed charges cause the end user price to exceed the ceiling, CTMP Verified status cannot be provided for that delivery chain, and the output must be reported as Not CTMP Verified. For direct offtake where the buyer is the end user at the metered delivery point and there is no resale, the offtake price schedule functions as the retail schedule for verification purposes. The reporting record shows published retail schedules and verified end user pricing structures. If any delivery chain's retail schedule causes end user prices to exceed the ceiling, that delivery chain's outputs are reported as Not CTMP Verified. The participant remains in the network unless Exit is triggered by seizure, override, or persistent misrepresentation combined with refusal of auditability. No participant may use fee stacking, rebates, affiliate billing, bundled services, side payments, or any other mechanism to create an effective end user price above the ceiling while claiming CTMP Verified status. The test is what the end user pays under the published retail schedule. If that amount exceeds the ceiling, the output cannot be represented as CTMP Verified, regardless of the formal structure of the billing arrangement or the claimed legal basis for any component of that price. Part Eight: Fresh Water Pricing Core Water is governed by a posted water schedule that is public, auditable, and enforced through the same constraint logic used for electricity. CTMP delivers fresh water from the desalination facility to the municipal boundary or equivalent delivery infrastructure point as specified in host operating conditions. From that point, local distribution utilities deliver water to end users. Distribution charges are permitted only as audited cost recovery under a published distribution schedule, independently reviewed on a defined cadence. Distribution charges may not be used as an extraction surface. The distribution schedule must be public and auditable. Independent review verifies that distribution charges reflect documented costs rather than margin extraction. The total end user price for CTMP water, including the CTMP base price and the distribution allowance, may not exceed the applicable ceiling in the posted water schedule for outputs represented as CTMP Verified. Host charges may exist under law. But if host-imposed charges cause the end user price to exceed the ceiling, CTMP Verified status cannot be provided for that delivery chain, and the output must be reported as Not CTMP Verified. For direct offtake where the buyer is the end user at the metered delivery point and there is no resale, the offtake price schedule functions as the retail schedule for verification purposes. The posted water schedule may include essential-use allocations, meaning defined volumes for basic human needs that are priced at zero or at reduced rates where program design and host coordination specify that outcome. The important characteristics of the water schedule are that it is posted in advance, that classifications are metered and logged, that the rules are the same for all participants in the same classification, and that compliance is auditable. Pricing is not discretionary. Allocation is not discretionary. Classification is not discretionary. Hidden markups are prohibited within CTMP Verified delivery chains for Core Water. This includes surcharges, handling fees, quality premiums, bundled service inflation, and any other charge that functions as price extraction rather than audited cost recovery. The only permitted addition to the CTMP base price for CTMP Verified outputs is the defined distribution allowance, and that allowance must reflect documented costs. Water quality is a technical compliance requirement, not a pricing lever. The platform maintains quality standards. Quality monitoring and compliance reporting are part of the verifiable operating record. No participant may charge a premium for meeting quality standards that the platform already requires. Part Nine: Internal Transfer Integrity The platform prohibits profit-taking tolls between CTMP verticals. This constraint exists because rent extraction often enters through internal transfers long before it appears in external pricing. A vertically integrated system that permits internal markups will see margins migrate from customer-facing outputs to inter-divisional transactions where they are harder to observe. Internal transfers between verticals follow published transfer rules. These rules are designed to pass through costs without markup. The rules are auditable. Transfer pricing is part of the verifiable operating record. If a vertical attempts to introduce an internal toll that behaves like rent, it is treated as a Charter violation. The response is the same as for any other violation: network status change, public reporting, and remediation requirements. Part Ten: Vertical Output Pricing Transparency Non-essential vertical outputs are not subject to price ceilings or resale constraints under this Charter. CTMP Verified status for non-essential vertical outputs does not imply any price ceiling or affordability cap. However, any sale or resale of non-essential vertical outputs that uses CTMP name, marks, or CTMP Verified representations must have its pricing made a matter of public record through Public price disclosure as defined in Part One. Where a reseller's margin is material, the reseller must be able to account for the margin using publicly stated cost and value explanations. This Charter does not prohibit high margins on non-essential vertical outputs. It makes them visible. CTMP vertical pricing policies are published and are designed to prevent rent extraction. Any participant or reseller that uses hidden fees, bundling, side payments, affiliate billing, or other extraction mechanisms while using CTMP name, marks, or CTMP Verified representations will lose CTMP Verified status for the affected outputs and may be moved to Continuity or Exit status where persistent or material. CTMP-operated sales of non-essential vertical outputs generally follow a published pricing corridor designed to remain below incumbent medians, and any attempt to add extractive mechanisms triggers loss of verification and network consequences. Part Eleven: Seizure and Sovereignty Any nation can physically seize a CTMP facility. The Charter does not pretend otherwise and does not attempt to prevent seizure through contract terms or threats. Any government can impose taxes. The Charter does not claim authority over sovereign taxation. If seizure or override occurs, the system response is not coercion. The system cannot coerce a sovereign government and does not try. The response is network separation. If host-imposed charges make ceiling compliance unattainable for Core electricity or Core Water, CTMP Verified status cannot be provided for that delivery chain and outputs are reported as Not CTMP Verified. This is a verification limitation, not a network separation. The participant remains in the network but cannot claim CTMP Verified status for those outputs. CTMP does not penalize taxation. It simply cannot verify outputs as meeting ceiling requirements when they do not. Exit status is triggered only by seizure, override, or nationalization of CTMP facilities, or by persistent refusal to publish and submit retail schedules or product specifications to independent attestation while continuing to claim CTMP Verified status. Exit is the boundary between verification limitations and network separation. When Exit status is triggered, the transition is immediate. The reporting record reflects the exit, the circumstances, and the date. People who opt in to updates may receive notifications of material network status changes. The exited facility or participant no longer receives CTMP terms, CTMP integrations, CTMP supply chain access, CTMP technical support, CTMP attestations, or CTMP ecosystem benefits. Its outputs are labeled Out of Network. It may not represent its outputs as CTMP Verified, CTMP priced, or Charter-governed. Any such representation will be addressed through the status clarification process described in Part Six. The enforcement is economic and reputational. A government that seizes a facility captures the physical asset but loses access to the network that made the asset valuable. A participant that persistently refuses auditability while claiming CTMP Verified status loses network membership. As the network grows and as more nations depend on CTMP integration for their industrial competitiveness, the cost of exit increases. The Charter does not need to threaten consequences it cannot deliver. It only needs to make the cost of exit visible and let participants decide. Re-entry after Exit. A participant that has exited through seizure or through persistent misrepresentation may apply for re-entry. Re-entry requires return of operational control to CTMP terms where applicable, restoration of metering and verification systems, publication of retail schedules or product specifications, submission to independent attestation, and independent verification of compliance. The Out of Network period is recorded in the reporting record. Re-entry after Exit requires a public disclosure in the reporting record describing the cause of Exit, the remediation taken, and the controls implemented to prevent recurrence. There is no permanent exclusion for seizure or for past misrepresentation. The system is designed to allow correction. But re-entry requires genuine restoration of Charter governance, demonstrated through technical compliance, auditability, and public disclosure. Part Twelve: Workforce and Operational Continuity CTMP maintains a network employment framework where practicable under applicable law. This framework supports workforce mobility across the network and provides continuity for personnel when operational circumstances change. In the event of Exit status at any facility, CTMP will offer affected personnel the option to transfer to other network facilities, subject to lawful work authorization, host-country requirements, and individual choice. Support may include travel and transitional assistance as available under the applicable program. Workers may choose to remain at a facility that has exited the network and accept employment under whatever terms the new operator offers. This is a voluntary choice. CTMP does not prevent workers from staying. Any facility operating Out of Network is not covered by CTMP employment guarantees or network employment benefits. Workers who remain at Out of Network facilities are no longer network employees and are not eligible for network relocation support. This structure serves multiple purposes. It protects workers by providing options when circumstances change. It maintains operational knowledge within the network. And it reinforces the principle that network membership provides guarantees that non-membership cannot replicate. Part Thirteen: The Sovereign Logic Engine The Sovereign Logic Engine (SLE) is the deterministic enforcement system that applies Charter constraints automatically. It governs metering, logging, compliance detection, network status updates, and verification status assignment. The SLE operates under deterministic rules. It does not exercise discretion. It applies the constraints defined in this Charter and in the published reporting rules. No human operator can override the SLE to alter tariffs, ceilings, allocation rules, or Charter constraints. The SLE enforces Charter constraints automatically under deterministic rules. A sealed emergency safeguard exists solely to protect infrastructure integrity and human safety in the event of catastrophic malfunction, verified code corruption, or critical system compromise. The safeguard can only place the system into a defined safe mode. It cannot modify tariffs, ceilings, allocation rules, or Charter constraints. Any activation is logged and disclosed in the reporting record on a defined timeline, with independent attestation and a published remediation summary. The SLE produces the verification layers described in Part Fourteen: metering records, time-stamped logs, aggregated public reporting, and tamper-evident commitments. These outputs are the evidentiary basis for all compliance determinations and dispute resolution under this Charter. Part Fourteen: Verification and Auditability The platform must be verifiable without publishing an operational attack surface. Verification operates through four layers that work together. The first layer is the Charter text itself. The constraints are written to be unambiguous so that compliance can be assessed against a clear standard. The second layer is aggregated public reporting. Outputs are metered and logged at the metered delivery point or applicable custody boundary. Published retail schedules and product specifications are reported. Aggregated data is published so that anyone can observe whether the system is delivering what it claims to deliver and whether retail schedules remain within ceilings for Core electricity and Core Water. Network status and verification status for all participants and all delivery chains is part of the reporting record. The third layer is independent attestation. Qualified third parties independent of the participant and CTMP operations verify that reported outputs match actual deliveries, that pricing at the metered delivery point matches published schedules, that downstream retail schedules keep end user prices within ceilings for Core electricity and Core Water outputs claimed as CTMP Verified, and that non-essential vertical outputs meet disclosure and QA requirements for outputs claimed as CTMP Verified. The fourth layer is tamper-evident commitments. The system produces cryptographic commitments or equivalent mechanisms that make unauthorized changes to records detectable. If someone alters the data, the alteration is visible. End user pricing compliance for Core electricity and Core Water is verified through published retail schedules, independent attestation, and audit sampling. CTMP does not require surveillance of individual household transactions. It requires that the retail schedule be published, auditable, and verified to remain within ceilings. These four layers together produce guarantee by structure rather than promise by personality. The system does not ask anyone to trust the operator. It asks them to verify the outputs. Part Fifteen: Change Control and Separation of Duties No single person, team, vendor, or counterparty is permitted to unilaterally alter pricing constraints, ceiling constraints, water schedule constraints, distribution allowance requirements, network status rules, verification requirements, or labeling standards. Separation of duties is mandatory. The functions of operation, compliance monitoring, attestation, and constraint enforcement are distributed across multiple parties with independent authority. No party controls enough of the system to alter constraints without detection. Changes to non-invariant provisions require documented justification, multi-party approval, public notice, and tamper-evident logging of the change itself. Changes that would weaken any invariant, introduce discretionary pricing power, raise ceilings, reduce auditability, or compromise the verification labeling system are not permitted regardless of approval. The platform invariants are immutable by design. This means there is no process for amending them because amenability would defeat their purpose. If circumstances arise that the invariants cannot accommodate, the appropriate response is to acknowledge the limitation publicly rather than to weaken the constraint privately. Part Sixteen: Disputes and Fact Resolution Disputes about compliance are resolved using the verification layers: metering records, time-stamped logs, published retail schedules, product specifications, independent attestation, and tamper-evident commitments. The system is designed so that facts can be proven without relying on reputation or trust. If a participant claims CTMP Verified status, the records either support the claim or they do not. If published retail schedules exceed ceilings, the verification limitation is in the record. If disclosure or QA requirements are not met, the limitation is in the record. If the records are ambiguous, the ambiguity itself is a compliance failure because the transparency invariant requires that outputs and pricing structures be verifiable. Disputes about network status are resolved by reference to the same records. A participant is in Compliance, Continuity, or Exit based on documented facts, not on negotiation or relationship. This does not replace legal processes where legal processes apply. The Charter operates within applicable law. But it provides a factual foundation that legal processes can rely on, and it reduces the scope for disputes that turn on credibility rather than evidence. Part Seventeen: The Wall The Wall is a public demand ledger that records expressions of support for CTMP deployment. It appears in this Charter because questions will arise about its status and relationship to the platform. The Wall is not a petition to any government. It is not a securities offering. It is not a profit participation instrument. It does not create any legal relationship between signatories and CTMP. People who opt in to updates may receive notifications of material network status changes, including seizures, exits, and significant compliance events. This notification is informational. It does not constitute a call to action and does not create any obligation on signatories. A voluntary donation mechanism may exist to support public campaign operating costs. Donations do not purchase influence. Donations do not affect network status. Donations do not create any expectation of profit participation or preferential treatment. The relationship between donation and CTMP access is zero. The Wall exists to make public demand visible so that deployment decisions can reflect actual demand rather than inferred demand. It is a signaling mechanism, not a governance mechanism. Part Eighteen: Canonical Public Statement This statement may be used to describe the Charter accurately in public communications. CTMP infrastructure is governed by a Stewardship Charter that constrains pricing, resale, financing, auditability, and internal transfer integrity across the platform. Core electricity pricing and Core Water pricing are defined by a posted tariff and a posted water schedule at the metered delivery point. Under CTMP terms, the posted tariff is fixed and cannot be changed by participant or operator discretion. End user prices for Core electricity and Core Water are capped by ceilings for outputs represented as CTMP Verified. CTMP Verified status is only available when published retail schedules keep end user prices within ceilings and have current independent attestation. For non-essential vertical outputs, CTMP Verified does not imply any price ceiling; it requires public price disclosure, published product specification, QA basis, logging at the applicable custody boundary, and current attestation. If a retail schedule is not published, not auditable, or attestation is not current, verification status defaults to Not CTMP Verified until restored. Governments can tax; CTMP does not claim authority over taxation. But if host-imposed charges cause ceiling breach for Core electricity or Core Water, CTMP Verified status cannot be provided for that delivery chain, and outputs are reported as Not CTMP Verified. The participant remains in the network unless Exit is triggered by seizure, override, or persistent misrepresentation combined with refusal of auditability. Delivery chains that are Not CTMP Verified are ineligible for expansion and promotional attestations. Charter constraints are enforced automatically by the Sovereign Logic Engine under deterministic rules. A sealed emergency safeguard exists solely to protect infrastructure integrity and human safety; it can only place the system into safe mode and cannot modify constraints. Prices are enforced through verification status and network status rather than physical shutoff. Outputs are verifiable through metering, aggregated public reporting, published retail schedules, product specifications, independent attestation, audit sampling, and tamper-evident commitments. Only outputs that meet all applicable CTMP Verified requirements may be represented as CTMP Verified. Seizure or persistent misrepresentation with refusal of auditability triggers Exit status; the response is network separation, not coercion. Re-entry requires technical compliance, auditability, and public disclosure in the reporting record. Participation is voluntary. The constraints are structural, non-discretionary, and identical for everyone.