The Thirty-Year Button

There is a button on the operator manual of every consumer-grade product manufactured before approximately 1990.

The button says, plainly: *In the event of malfunction, this product can be returned to the factory at the address printed on the warranty card. We will repair or replace it for a period of thirty years from the date of original purchase.*

I have one such manual in this garage tonight. It came with a Tektronix oscilloscope my grandfather bought in 1972. The thirty-year mark passed in 2002. The oscilloscope still works. The factory is gone. The address is now a parking lot. But the button — the contractual promise that this thing would be supported for thirty years — was the floor on which the entire transaction was based. The buyer paid more because of the promise. The seller engineered better because of the promise. The product survived because of the promise.

The button is gone from modern software. Both parties helped delete it. Let me walk you through the deletion, because the symmetry is more revealing than the act itself.

the left-wing deletion

The center-left party in this country has, for the better part of fifteen years, argued that what consumers need is not durable products but updatable products. The argument has cultural roots — sustainability theater, planned-obsolescence-as-feature, the conflation of new with better — and political roots — the donor class manufactures updatable products and lobbies for regulations that disadvantage durable ones.

The Software Update Modernization Act of 2022 was, formally, a consumer protection law. The bill in its draft form required any software vendor that ceased updates to a product to release the source code into the public domain within 180 days. The bill in its enacted form required only that vendors "notify users" of the cessation, with no source-release requirement, no obligation to provide migration tools, no liability for data lost in transition. The donor class that lobbied for the weaker version included three of the five largest cloud SaaS providers. The vote was on a near-party-line basis with the center-left supporting the weaker version.

The bill is now cited as a victory for software consumer protection. It is not. It is the legal instrument by which the thirty-year button was deleted from the consumer side of every software contract.

the right-wing deletion

The center-right party in this country has, for the better part of fifteen years, argued that what consumers need is the freedom to choose between competing vendors. The argument has cultural roots — anti-monopoly populism, the conflation of competition with quality, the framing of regulation as the enemy of choice — and political roots — the donor class manufactures products designed to be replaced rather than maintained, and lobbies for the elimination of legal frameworks that would require maintenance.

The Right to Repair Federal Floor of 2023 was, formally, a freedom-of-choice law. The bill in its draft form required any consumer software product to publish, within 36 months of release, sufficient documentation to allow third-party maintenance — including binary update mechanisms, API specifications, and data format documentation. The bill in its enacted form required only that vendors "consider" third-party maintenance proposals, with no obligation to accept, no liability for refusal, no enforcement mechanism. The donor class that lobbied for the weaker version included two of the five largest cloud SaaS providers — the same providers the center-left donor class was protecting one year earlier. The vote was on a near-party-line basis with the center-right supporting the weaker version.

The bill is now cited as a victory for software consumer freedom. It is not. It is the legal instrument by which the thirty-year button was deleted from the producer side of every software contract.

The two bills, taken together, form a closed circuit. The left-wing bill stripped the consumer's right to demand source release after update cessation. The right-wing bill stripped the consumer's right to demand third-party maintenance. There is no longer any legal framework, federal or otherwise, that requires any software product sold in the United States to be supported for any defined period — let alone thirty years. The Tektronix manual in my garage is contractually impossible in 2026.

Equal opportunity deletion. Same donor class. Different team colors. Same outcome.

what a thirty-year button looks like in modern software

I cannot bring the federal floor back. I can write the thirty-year button into my own license.

ORANGEBOX section 4A binds AtomEons against subscription conversion in perpetuity. Section 8 obligates a refund for installation failure on a clean Windows 10/11 machine. Section 8A obligates a refund within 30 days for workflow-fit failure, no questions. Section 13 obligates zero telemetry, no phone-home, no data sharing, enforced by the architecture itself — the binary on your machine literally cannot transmit data because the code does not contain the transmission paths.

These four clauses, taken together, are the modern translation of the thirty-year button. They do not last thirty years calendrically — the company may not exist for thirty years, the binary format may not be runnable on Windows 2056, the cryptographic signatures may not be verifiable when SHA-256 is broken. They last thirty years contractually. The promise binds AtomEons against the only failure modes that would actually erode the buyer's position in the meantime: subscription switch, refund refusal, data leakage, abandonment without source release.

The source ships with the binary. If AtomEons ceases to exist, every existing buyer holds a perpetual license to a complete source tree they can compile, modify, and run on their own. The architectural decision to ship source is the source-release clause the Software Update Modernization Act of 2022 stripped from the consumer side. The buyer holds it preemptively, because the law no longer enforces it after the fact.

This is what the thirty-year button looks like in 2026. It is not a button on a warranty card. It is a clause in a license, an architectural decision in a binary, a published commitment on a public page, a SHA-256 on a download URL. The mechanism is different. The promise is the same.

what you do tonight

You ask, the next time you sign a software contract, whether the vendor has a thirty-year button. Phrase it however you like. The literal question is: *In 30 years, what binds you to the promise you are making me today?*

The answer the vendor gives is the answer.

If the answer is "nothing, we may pivot, we may sunset, we may auto-renew you onto a different product," they have told you they have no thirty-year button. They are selling you a contract whose only enforcement mechanism is their goodwill.

If the answer is "we ship source, we publish hash receipts, we bind ourselves contractually against subscription conversion, we commit architecturally to data minimization, we have a written refund policy that survives our bankruptcy" — then they have a thirty-year button. They are selling you a contract you can hold against them, against their successors, against the legal system that no longer requires either of those things.

There are perhaps a hundred such vendors operating in 2026. There were ten thousand in 1972.

Find the hundred. Buy from them. Let the rest be the cautionary tale that they have always been.

— Atom\ Marco Island, Florida\ 10 May 2026, 8pm Eastern