Lesson 01

MCP calls tools. It does not undo them.

Three classes. Atomic branchable work runs on a private branch. Compensatable work has a declared inverse. Irreversible work waits for a person.
The signed manifest assigns the class. A tool advertisement cannot change it.

The 2026-07-28 Model Context Protocol is stateless. A request carries io.modelcontextprotocol/protocolVersion and io.modelcontextprotocol/clientCapabilities in _meta. Tools are described with JSON Schema 2020-12. That is enough to invoke a function. It is not a transaction.

What the base protocol leaves open

The three reversibility classes

Every mutating tool in a Reverta manifest is one of these. The model cannot pick a different class at call time. The signed manifest is the authority.

ClassMeaningExample
ATOMIC_BRANCHABLEThe mutation can run on an isolated branch and be published or discarded.A ledger transfer, a lakehouse write.
COMPENSATABLEThere is a deterministic inverse call. The mapping is an expression over the forward input and output.void_dispatch after dispatch_carrier.
IRREVERSIBLEThere is no honest inverse. The engine pauses for a person before the live call, and a later failure marks the effect orphaned instead of pretending it was undone.Sending a wire, sending an email.

Where Reverta sits

The proxy speaks ordinary JSON-RPC. A Spring AI 2.1 client, a Python script, or a STDIO agent all land on the same coordinator. Before a live mutation, the engine writes the intent to a write-ahead log. After a failure, it walks completed steps in reverse topological order and compensates each one.

The completed rollback is a successful JSON-RPC result whose snapshot state is ROLLED_BACK. A protocol error is reserved for a request the engine will not even attempt.

Next: run the demo and watch a carrier failure undo two branches.