A protocol is not an app. It is what apps speak.
Eternity is the contract layer between humans and intelligent systems. The same .ety file can be authored by a founder, audited by a regulator, compiled by Orin, executed by a swarm of agents, and replayed by a researcher — without changing a character.
Plain-language directives become typed intent.
Agents negotiate work through shared .ety contracts.
Robotics, finance, infra — actuated under invariants.
Why a protocol, not a product
Every prior wave of computing settled on a protocol once the use cases multiplied: HTTP for the web, SMTP for mail, IP for the network itself. Autonomous systems are at that same threshold. Eternity is the answer: one language for intent, one runtime for verification, one bus for orchestration.
Why .ety is readable by anyone
Web developers, operators, founders, and domain experts can all read the same intent file. There is no DSL to learn beyond a handful of keywords — intent, purpose, must always, must never, verify, end. The grammar is intentionally small so the protocol stays universal.
Where MCP fits
We ship Eternity as an MCP server so any AI client can connect to the protocol without integration code. See the MCP Hub for the tool surface.