The Reason Everything Is Public

On the new plain-words front door at peoplesctmp.org/technical-record-simplified.html, why every section of it exists, why the record will keep growing for months, and why there is exactly one place on Earth where any of it counts as real.

This week a new page went live on the CTMP site. It is called "CTMP in Plain Words," and it does something that technical projects almost never do: it explains itself to a stranger in five minutes, with no jargon, and then tells that stranger, in plain type, exactly which parts of the project exist and which parts are still drawings.

I want to walk through why that page exists, section by section. Not what it says. You can read what it says in less time than it takes to read this newsletter. I want to walk through why each section is public, because the publicness is not decoration. It is the design. And I want to tell you what is coming, because this page is the front door of a record that is about to grow considerably, and the growing is the point.

One more thing before we start, and it is the most important sentence in this piece, so I will say it early and again at the end. Everything I publish about this project, every article, every paper, every correction, has one source and will only ever have one source: the website. Every document there is tagged with its SHA-256 fingerprint and carries our digital signature. If you read a claim about CTMP anywhere else, including here, including in my own posts, the website is the original and everything else is a copy. There is one point of origin. That is not a branding choice. I will explain, near the end, why it is a survival choice.

Now, the walk.

Part one is a picture of two ways to build. Here is why it is public.

The page opens with the whole idea in one image. On the left, the usual way: a builder buys machines from one seller, steel from another, power from a third, money from a bank, and every one of those sellers adds a markup and a waiting line. On the right, the CTMP way: one platform that makes its own machines, its own steel, its own concrete, its own electricity, and borrows nothing. Nobody to wait for. No markup to pay. No interest running while you build.

Why does this live in public, in words a twelve-year-old can follow?

Because an idea that cannot be explained simply cannot be checked broadly. That is the progression that runs through this entire project, and it starts here. If the core mechanism of a plan can only be understood by specialists, then only specialists can catch its mistakes, and specialists are few, busy, and sometimes conflicted. But if the core mechanism fits in one picture, then every person who looks at that picture becomes a potential auditor of the logic. A farmer can ask: what happens when one of your own machines breaks? A shopkeeper can ask: who checks your prices if there is no market checking them? Those are excellent questions. They deserve to be askable by everyone, not just by people with engineering degrees.

The failure statistic quoted in that section, that roughly nine out of ten giant projects land late and far over budget, comes from the largest academic database of megaprojects ever assembled, more than sixteen thousand of them. That number is not mine. It is public research, cited on the page, and it describes the mountain of evidence this design is a response to. Publishing the response next to the evidence, in plain words, is what lets anyone on the planet weigh one against the other.

That is the first why. Plain language is not a simplification of the record. It is the part of the record that makes the rest of the record checkable by the species instead of by a committee.

Part two is six numbers with labels attached. Here is why the labels matter more than the numbers.

The second section is six cards. Three hundred gigawatts. Two and a half cents per kilowatt-hour, posted and fixed. Zero debt, permanently. Two billion cubic meters of fresh water per year, given to the host nation, not sold. Five to six years from first dig to switch-on. And fifty megawatts, the proof-of-concept.

Every card carries a label, and the labels are the honest machinery of the whole page. "Design value, on paper." "Fixed by the Charter." "Rule, written and permanent." "Design complete, first build next."

Why publish the labels? Most projects would not. Most projects would print the big numbers and let the reader assume they describe something that exists. The assumption does the selling.

We do the opposite, in public, for a reason that has a logical shape to it. A number without a label is a claim. A number with an honest label is a record. Claims persuade and then decay. Records accumulate and then compound. When the fifty-megawatt plant is one day built and metered, its card will change from "design value" to "measured," and that change will be dated, hashed, signed, and visible. Anyone will be able to watch a paper number become a physical number in the open. That transition, repeated across every figure the project has ever published, is the entire evidentiary strategy. But you can only watch a number cross the line from paper to metal if the paper version was published first, labeled as paper, where everyone could see it.

So the labels are not humility theater. They are the "before" photograph. A project that intends to be audited takes its "before" photograph in public, because an audit needs a starting point that nobody can quietly move later.

And this is where the SHA-256 tagging earns its keep for the first time. A fingerprint on the "before" photograph means that when the "after" arrives, no one, including me, can retouch the "before" to make the prediction look better than it was. The record does not trust its own author. That is a feature I insisted on.

Part three is The Wall. Here is why consent is measured in the open.

The third section explains the part where you come in. There is a public board. You open the site, you pick your country, and after validation your country's public count goes up by one, live, for everyone to see. No account. No name. No email. About ten seconds.

Why is this public? Because of what the board is actually for, which is answering one question that nobody else can answer: do the people of the world actually want this?

Think about how that question is usually answered for large infrastructure. It is answered in rooms. Ministries, consultancies, investor briefings. The people who will live next to the project, drink its water, and pay its posted price are surveyed, at best, and the survey is owned by whoever paid for it. The answer arrives pre-shaped by the room it was formed in.

The Wall inverts that. The question is asked in public, the answers accumulate in public, and nobody, including us, owns the result in any way that lets us shape it. The count is the count. When it goes up, everyone sees it go up. When abuse is removed, the correction is transparent. The board never claims to know who any individual voice belongs to, because it never asked.

And there is a second why buried in the design, the one I think about most. Every nation has its own finish line, set at five percent of its own population, and the rankings measure progress toward your own line, not raw totals. A country of ten million and a country of a billion climb the same mountain, each theirs. Why publish that rule? Because the alternative, ranking by raw count, would quietly tell most of the world that its voice is arithmetic noise. A public consent instrument that structurally favors the largest populations is not a consent instrument. It is a census with extra steps. The five percent rule is public because fairness that is not published is not fairness, it is policy, and policy can change in a room. Rules on the record cannot be changed in a room. That is the whole distinction this project is built on.

As I write this, the board holds tens of thousands of voices across more than a hundred countries. Every one of them was added in the open, under a rule everyone could read first.

Part four is two columns titled "what is real." Here is why the second column is the important one.

The fourth section is the one that surprises people. It is a plain table. On the left, what exists today: a fifty-megawatt proof-of-concept complete in design, the published technical record with every paper dated and versioned, The Wall live and running, and a public revision table where every correction is displayed, mistakes included. On the right, what is still on paper: the three-hundred-gigawatt module itself, because no full-scale construction has begun. The factories, tunnels, steel mills and water plants. The free water, which requires the power plant to exist first. And one number, a daily mortality figure that sets the project's moral pace, which is being withheld until its full methodology can be published and checked.

Why publish the right-hand column at all? No fundraising deck on Earth has a "still on paper" column. That is precisely why this page has one.

Here is the progression. A project that hides what is unbuilt has to spend the rest of its life defending the hiding. Every discovered gap becomes a scandal, every scandal becomes a reason to distrust the parts that were true. But a project that lists what is unbuilt, in its own voice, on its own page, before anyone asks, has converted its biggest vulnerability into its credential. Nobody can expose what you have already exposed. The right-hand column is not a confession. It is armor made of daylight.

The withheld mortality number is the sharpest example, and I want to be direct about it because it cost me something to withhold. There is a figure I believe in, about the daily human cost of energy poverty, and it used to appear in project materials. It no longer does. It is out of the record until its complete methodology, sources, overlap controls, and uncertainty ranges can be published and independently checked. Why? Because a record that contains one unverifiable number teaches readers to wonder about all the others. The discipline is indivisible. Either every number can be traced, or the tracing means nothing. Withholding a true-feeling number until it is a provable number is what "audit, not belief" costs in practice. The page says this openly, and it says it in the column where the project admits what it has not yet earned the right to claim.

Part five is a ladder of depth. Here is why every rung is open.

The fifth section offers the reader a choice of depth. An easy starting essay, twenty-five minutes, that explains the whole design as one long refusal to go shopping. The main technical paper, with the machines, the costs, the timelines, and every assumption stated. A white paper on what happens to climate policy when clean power is simply cheaper, metered, and verified at the point of delivery. And the full technical record, the formal registry where every document, every version, and every correction lives on one page, which is where serious reviewers are pointed.

Why publish the deep end next to the shallow end?

Because depth that is gated is authority, and depth that is open is evidence. Those are different substances. When a project keeps its technical core behind credentials, meetings, or data rooms, it is asking the public to trust that the people inside the room checked properly. When a project publishes its core where a graduate student in any country can download it at three in the morning and attack the arithmetic, it is asking for something else entirely. It is asking to be found wrong, as fast as possible, by anyone capable, so that what survives is worth building.

The ladder structure matters too, and it is deliberate. Most people will read the five-minute page and stop, and that is a complete experience: they now know what the project is, what is real, and what is on paper. Some will read the easy essay. A few will descend to the papers. A very few will open the registry and check hashes. Every rung is public, so the reader chooses their own depth, and, this is the part that matters, every reader at every depth is reading the same record. The plain-words page is not a separate simplified story that could drift away from the technical truth. It is the same truth at a different altitude, pointing down at its own sources. When a simplification and its source live one click apart, the simplification cannot quietly lie, because the correction is adjacent.

That adjacency is a publishing principle I intend to hold for everything that comes: no claim at the surface without its derivation one level down, all the way to the bottom.

Part six is a chronological archive. Here is why the order is the honesty.

The sixth section is the dispatch archive. Each time a country reaches first place on The Wall, a dated dispatch marks the moment. Twenty-eight of them so far, from Ukraine on the eighth of May to Morocco on the fifteenth of July, and the archive keeps them in the one order that cannot be argued with: chronological. Reading it top to bottom replays the entire race.

Why publish leadership history at all, and why in this rigid order?

Because momentum claims are the easiest place for a movement to start lying to itself. It is trivially easy to curate a highlights reel: lead with your biggest country, bury the quiet weeks, reorder the story so it always seems to be accelerating. The chronological rule makes that impossible. The archive shows the race exactly as it happened, including whatever the honest sequence happens to be. When Ukraine took the lead twice, the archive shows Ukraine twice, in the two places it actually happened. Nothing is promoted. Nothing is buried. The order is the order.

And there is one small design choice in that section that I consider a tell for everything else: the page never names the current leader. Leadership can change any hour, so it lives in exactly one place, the live board. Why? Because a static page claiming a live fact will eventually be wrong, and a record that permits itself to be even briefly, innocently wrong about a small live fact has started down a road. The rule is: every fact lives where it can be kept true. Live facts live on the live board. Dated facts live in dated dispatches. The plain-words page holds only the facts that do not move. This sounds fussy. It is fussy. Fussiness about where facts are allowed to live is most of what integrity turns out to be, mechanically.

Part seven is the questions people actually ask. Here is why the answers are printed in advance.

The seventh section is a short list of fair questions with direct answers. Who is behind this. Is this asking me for money. Why should I believe a project this big can work. What do I get out of adding my voice. Is my information safe. Where does the free water come from.

Why print them? Every project gets asked these questions. Most answer them privately, one conversation at a time, which means the answers can flex to fit the listener. Printing the answers removes the flex. When the answer to "is this asking me for money" is published as a flat "no" on a hashed, signed page, that no is now permanent in a way a spoken no can never be. The reader is not trusting my consistency. They are reading a commitment that would visibly break if it changed.

Look at what the printed answers actually say, because they follow the same discipline as everything else. The answer to "why should I believe this can work" begins: you should not simply believe it, and the project says so itself. It then points to public research on why giant projects fail, and to two historical ancestors of the approach: Henry Ford's River Rouge plant, which made its own steel and glass and proved integration slashes costs, and the Falcon 9 rocket, where the incumbent's own published cost model predicted a development cost roughly ten times what the vertically integrated builder actually spent. Ancestors, not proofs. The page is explicit that proof will come from meters and public reporting, and that the first physical build of the fifty-megawatt proof-of-concept is the next milestone. Even the water answer carries its catch, stated openly: the quarter-of-a-cent figure is the energy component only, the full delivered cost is larger, the mineral recovery that offsets it must be demonstrated at scale, and the power plant has to exist before any water flows.

An FAQ that argues against its own easy belief is rare. It is rare because it is expensive. It spends persuasion to buy verifiability, every time, on every question. That exchange rate is the project's entire communications policy, printed where everyone can hold me to it.

Part eight is about money, and it says: not yet. Here is why even that is public.

The final section addresses support. A voluntary contribution option, for hosting, research, diagrams and archiving, is being finished. It opens when it works properly end to end, and not one day before. Contributions will not be investments, will not buy access or influence of any kind, and the Charter forbids anything else.

Why publish a payment feature that does not exist yet, labeled "opening soon"?

For the same reason the numbers carry labels. Announcing it before it opens puts the rules on the record before the first dollar arrives. The constraints, no investment, no access, no influence, are now published prior commitments rather than policies improvised after money appeared. Money is where public projects most often begin to bend, quietly, one reasonable exception at a time. The defense is the same as everywhere else on this page: write the rule down in public first, hash it, sign it, and then let the money arrive into a structure it cannot renegotiate.

One point of origin: why the website is the only source there will ever be

Now the doctrine underneath all eight sections, the one I promised to return to.

Every article in this series, every dispatch, every paper, every plain-words explainer, has exactly one source: the website. Not this newsletter. Not my posts. Not any repost, screenshot, quotation, or summary, however accurate. The website is the record. Everything else, including the words you are reading right now, is commentary on the record, and commentary is not evidence.

Here is why that rule exists, and why it is enforced with mathematics rather than with my word.

Every document on the site is tagged with its SHA-256 fingerprint and carries our digital signature. If those terms are new to you, the idea is five sentences long. A SHA-256 fingerprint is a short string of characters computed from a document's exact contents. Change one letter of the document, one comma, one digit, and the fingerprint changes completely. So the fingerprint published beside a document is a promise: this text, exactly this text, character for character, is what was published. The digital signature adds the second half: it proves the document and its fingerprint came from us and not from someone pretending to be us. Together they mean any person on Earth, with free tools, can verify that what they are reading is what we published, unaltered, and genuinely ours.

Why does a public-benefit infrastructure project need cryptographic fingerprints on its essays? Three reasons, in ascending order of seriousness.

First, drift. Ideas mutate as they travel. A design value becomes "they built it." A target tariff becomes "they charge." A withheld number becomes a quoted one. None of this requires bad faith; it is what retelling does to precision. A single fingerprinted origin means every mutation can be settled in seconds by anyone: go to the source, check the text, done. The record does not argue with the telephone game. It simply outlives it.

Second, fabrication. A project that reaches millions of people will eventually be quoted as saying things it never said. Screenshots are trivial to forge. Entire fake pages are trivial to forge. The only durable defense is a rule the public can apply without trusting anyone: if it is not on the site, hash-tagged and signed, it is not ours. Full stop. That rule protects you from impostors, and, notice this, it also protects you from me. If I were ever tempted to tell one audience one thing and another audience another, the single point of origin makes it structurally impossible. There is one text. Everyone reads the same one.

Third, and most serious: time. This project measures itself in decades. The people who eventually audit it, engineers, journalists, historians, host-nation reviewers, will need to know exactly what was claimed, when, in what version, with what corrections. Social platforms are rented land; posts get edited, deleted, and buried by design. A dated, versioned, fingerprinted, signed archive on one domain is the difference between a paper trail and a rumor trail. When someone in 2040 asks "what did they actually say in 2026," the answer must not depend on anyone's memory, including mine. It will depend on a hash.

That is how important these articles are, and that is the weight the single origin carries. The claims in this record are the kind that must be exactly right or visibly corrected, and both exactness and visible correction require one canonical text that nobody, friend or enemy or author, can silently amend.

So here is the standing instruction, for this newsletter and everything after it: enjoy the commentary anywhere you find it, but cite only the source. peoplesctmp.org/technical-record-simplified.html.One domain. One record. One point of origin.

Why the record is about to grow, a lot

The plain-words page is a front door, and behind a front door you build a house. Over the coming months, the record will grow considerably, and I want to say in advance what kind of growth it will be, so that when you see it happening you recognize the pattern instead of wondering about it.

Every vertical I have published will be updated. The platform is designed as an integrated whole, seventeen verticals, from power and water through steel, concrete, green molecules, and beyond, and the documentation of each will be brought to the same standard the newest papers already meet: every figure classified as measured, externally sourced, calculated, modeled, or targeted; every assumption stated; every route-specific comparison matched honestly; every dependency named. Where an older document used a single number that should have been a labeled range, it will become a labeled range, and the change will appear in the revision table with a date on it.

New plain-language companions will follow, because the adjacency principle applies everywhere: no technical document without a version any person can understand, one click away, telling the same truth at a different altitude.

And corrections will continue to be published as first-class documents, not as quiet edits. The record already contains papers that were revised because review found real errors, an inconsistent capacity factor here, a double-counted megawatt-hour there, and each revision carries a change log stating plainly what was wrong and what replaced it. That will keep happening, and I want to be understated but completely clear about what it means when it does. A record that never corrects itself is not a record that never errs. It is a record that hides. The corrections are not the embarrassing part of this archive. They are the proof that the verification machinery is switched on and pointed at its own author first.

Why say all this before doing it? By now you know the answer, because it is the same answer as every section above: committing in public, in advance, is the only commitment that counts. This paragraph is itself now part of the record. In six months, hold it against what the site contains. That is the correct use of everything I publish.

The quiet part, said once

I will state the deeper meaning one time, plainly, and then put it down, because it is not the kind of thing that improves with repetition.

Before this project pours any concrete, it is building something else: a public record engineered so that its author cannot cheat. Fixed prices written into a charter. Unbuilt things labeled unbuilt. A consent board that asks for nothing and shows everything. An archive in an order that cannot be curated. Answers printed before they can flex. Rules for money published before money. One origin, fingerprinted and signed, so that every claim is permanently checkable by anyone, forever, against a text no one can quietly change.

If the machines never get built, that record will still have demonstrated something worth demonstrating: that a project can choose, from its first public day, to be auditable instead of believable, and to treat every person on the planet as qualified to check it. And if the machines do get built, they will stand on the only foundation that could ever hold something this large, which was never steel. It was the record.

The page is live. Five minutes, no jargon, and by the end you will know exactly what is real, what is on paper, and how to verify every word of it yourself.

The source, and the only source, is peoplesctmp.org/technical-record-simplified.html.

No account. No name. No email. Just your country.