Chris M. Coode
Originator, Architect and Steward of the CTMP
Why I Built CTMP
The problem was never that humanity cannot build. It is that the way we build guarantees failure before the first shovel moves. Nine of ten megaprojects overrun. Large dams land at nearly double their estimates. The cause is not concrete or rock. It is the structure: a builder that owns nothing, buying every machine, every tonne, every kilowatt-hour and every dollar from markets that each add a queue, a margin, a contract and a failure mode. The modern megaproject is a procurement office wearing a hard hat.
So I removed the procurement. The CTMP manufactures its own boring machines, turbines, steel, concrete, cable, wafers and molecules, powers all of it with its own 300 gigawatt hydro core, and moves every internal good at cost. I rejected debt because lenders become leverage, leverage becomes capture, and capture becomes rent. I rejected internal profit because margins forbidden at the customer's meter will otherwise hide inside the body. I rejected a stock listing because a sixty-year asset should not perform for a ninety-day audience.
And I built The Wall because the one question no ministry, fund or consultancy can answer honestly is where the people of the world actually want this. So we ask them directly, at zero cost, with nothing collected and nothing sold, and we publish the answer live.
Every claim on this page is dated, versioned and published for audit rather than belief. That is the discipline. This is the record.
The Platform That Owns Its Own Supply Chain
Demonstrates that megaproject failure rates are artifacts of supply-chain separation, not laws of engineering. Derives a quantified avoided-procurement floor exceeding $115 billion per module on four input classes alone, and validates a 5 to 6 year build window against documented external lead times of 96 to 174 months.
The Documentation Program
Six families. Every document versioned, dated and status-labeled. Older figures must never be mistaken for current canon; the label tells you which is which.
Core Architecture
hydro core · waterways · turbines · TBM fleet · module structureIndustrial Verticals
steel · concrete · molecules · wafers · compute · HVDC · desalinationEconomics and Delivery
owner-cost energy · procurement comparisons · schedule compressionGovernance and Integrity
charter · no-debt structure · at-cost transfers · attestationPublic Mandate
the wall · country race · thresholds · selection processHistorical Development
earlier architectures · superseded design documentsHow the Architecture Evolved
Not a life story. A dated technical lineage, showing that the architecture did not appear after public attention arrived. Each stage links to the documents that established it.
CTP · Philippines
The initial integrated infrastructure concept: energy, water and transport treated as one system rather than three procurements. The founding question is asked here: what if the builder owned the chain?
Establishing documents →CTMP-UAE
Canal, energy and industrial-platform development. The marine corridor and the industrial body are joined into a single architecture for the first time.
Establishing documents →CTMP-GCC
Regional deployment architecture. The module concept generalizes: one design, many geographies, with deployment-dependent quantities separated from platform invariants.
Establishing documents →People's CTMP
The public mandate. The Wall, the Country Race, required counts at five percent of population, and the principle that deployment follows demonstrated demand rather than inferred demand.
Establishing documents →The Current Architecture
The 300 GW module. Seventeen verticals, integrated supply-chain ownership, the Stewardship Charter v3.2, at-cost internal transfers, zero debt, and the published five to six year build window. The 50 MW proof-of-concept is design-complete, with its first physical build as the next milestone.
50 MW PoC · Design complete · First build next Current canon →Whose Work This Is
CTMP was originated by Chris M. Coode. Its technical documentation has been developed through iterative research, modelling, engineering consultation and assisted analytical work under his direction. Canonical documents are issued through the CTMP documentation program with version numbers, publication dates, disclosure boundaries and dated errata.
Changes to canonical documents follow the Charter's change-control provisions: documented justification, multi-party approval, public notice, and tamper-evident logging of the change itself. Platform invariants are not subject to amendment.
The Record of Corrections
Every engineering drawing carries a revision table, and so does this record. A page that displays its own corrections, dated, is worth more than a page that appears never to have been wrong.
| Rev | Date | Document | Change |
|---|---|---|---|
| v1.0 → v1.1 | Jul 2026 | Technical Record (this page) | Clarified that the 50 MW proof-of-concept is design-complete; first physical build remains the next milestone. |
| v1.1 → v1.2 | Jul 2026 | The Platform That Owns Its Own Supply Chain | Disclosure boundary stated explicitly throughout: the $75B figure is the hydro-core capital basis used to derive owner-cost power economics, not total integrated platform capex. The $118B figure is a quantified avoided-procurement floor on four input classes only, not total avoided capex. |
| v3.1 → v3.2 | Dec 2025 | Stewardship Charter, Plain-Language Public Edition | Clarity, formatting, definitions and implementation detail refined. Platform invariants and constraint logic unchanged; invariants are not subject to amendment. |
Future corrections are appended here with a dated version number and a public change log, under the Charter's change-control provisions. The absence of an entry is itself a claim, and it is auditable.
Do Not Take This Page's Word for It
The Charter's verification architecture applies to the documentation itself. Four layers, none of which require trusting the author.
Unambiguous text
Every document states its version, date, disclosure boundary and status. Superseded figures are labeled superseded. What is claimed is written so that compliance can be checked against a clear standard.
Cryptographic fingerprints
Each published PDF carries a SHA-256 hash beside its download link. Any copy of the document, anywhere, can be verified against the canonical fingerprint.
sha256 · [affixed per document on publish]Independent archives
Canonical documents are deposited with independent archives that assign persistent identifiers and preserve every version. The record survives this website.
DOI registry · Internet Archive mirrorThe dated trail
The evolution timeline, the revision table and the archive series together form a lineage that cannot be backdated. The work is inspectable from its earliest stage to current canon.
Keep the Record Public
The CTMP technical record is published openly so that its architecture, assumptions and governing principles can be examined rather than merely believed. Contributions support technical publication, independent verification, research, diagrams, archival preservation, hosting and public access.
Contributions are received by Hutchison Lea ConneXions Inc. Anonymity applies to public display; payment processing requires standard identity handling.
See how support is used
- Technical research and independent verification
- Documentation, figures and vector plates
- Hosting, archival deposit and persistent identifiers
- Public communication of the record
- Legal and technical publication expenses
The Work Is Public. The Architecture Is Accountable. The Record Is Dated.
CTMP does not ask the world to accept an idea without examination. It publishes the architecture, identifies its assumptions, corrects its errors and preserves the record of how the system developed. There is a specific person behind CTMP. There is a dated body of technical work behind that person. You are standing in it.
Enter the Technical Library Country Updates Visit The Wall