Not a language.
A protocol.
Two plain-English files sit at the top of whatever you're building — software, robotics, operations, anything. They tell every AI, forever, what you actually wanted.
Eternity is not a programming language.
You don't learn syntax. You don't write code. You write what you want — in normal English — into a file called intent.ety. The AI replies with what it's going to do, in normal English, into a file called implement.ety. You read it. You approve it. The AI then builds in whatever native tooling the target uses — React, ROS, Solidity, a kitchen recipe, a city ordinance. The protocol doesn't care.
The two files live at the root of the project — alongside the code, alongside the robot's firmware, alongside the org chart. They version with the work. They are the only thing every future AI needs to read to remember what you asked for.
The whole protocol is two files. That's the point.
purpose: build a pomodoro timer that
actually helps me focus.
must always:
- work offline
- keep my last session if i refresh
- be readable by my 9 year old
must never:
- send my data anywhere
- autoplay sound
on failure: tell me in plain words.i will build this as a single web page. to honor 'work offline': i'll save state to localStorage, no backend. to honor 'readable by your 9 year old': buttons say 'start', 'pause', 'reset'. no jargon, no settings menu. to honor 'never send data': zero network calls, no analytics, no fonts from CDNs. approve to build? (y/n)
That's it. No grammar to memorize, no DSL, no SDK. Anyone who can write a grocery list can author intent.ety. Any AI capable of following instructions can return an honest implement.ety. The same pair works for software, for a warehouse robot, for an operations runbook.
Prompts vanish. Intent persists.
A prompt is a conversation. When the chat ends, the AI forgets you ever said it. Next week, next model, next vendor — the context is gone. You re-explain. You re-fight the same battles. You hope nothing important got lost.
An intent file is a contract. It lives in the project. When you upgrade, the intent file upgrades with it. When a different AI takes over, the intent file tells it everything that came before. The implementation file proves the AI actually understood. Both stay there. For eternity.
- — lives in a chat window
- — forgotten after the session
- — invisible to the next AI
- — no version history
- — no record of what was promised
- — lives at the top of the project
- — read by every future AI, forever
- — versions alongside the build
- — diffable, reviewable, auditable
- — anyone can read it, even non-coders
A protocol works everywhere — that's what makes it a protocol.
HTTP didn't know what a website was. SMTP didn't know what an email contained. Eternity doesn't know what you're building. It only carries intent — between any human and any intelligent system, in any field. As AI moves into more of the world, the same two files keep working.
intent.ety + implement.ety live in /, alongside package.json. Every future model reads them first.
Both files ship with the robot. A new firmware vendor inherits the contract — what it must never do, what it must always guarantee.
An ops team writes intent in English. The AI returns a runbook. The runbook is approved once and reused forever.
Embedded systems carry their intent file. Anyone diagnosing the device knows what it was built to do.
A city writes intent.ety. The implementation becomes auditable record. Citizens read both.
The protocol doesn't know what you're making. It only knows: there is a human who wants something, and an intelligence that will do it.
The protocol is free.
MCP is paid.
The two files cost nothing — write them anywhere, with any AI, forever. If you want our hosted MCP server so Claude, Cursor, or any agent can speak Eternity over a wire, that's the paid product. It's the only thing we charge for, because it's the only thing that costs us money.
- ✓ the protocol itself, in any project
- ✓ writing intent.ety with any AI
- ✓ self-hosting the verifier
- ✓ training your own model on the spec
- ○ our hosted MCP gateway (we run the inference for you)
One protocol.
Forever.
Write the two files. Anywhere. Once. Let every AI that ever touches your work inherit the contract.