§01 — The Problem

Each compute paradigm needed new rails.

1999
WEB
humans browse
2008
PAYMENTS
humans transact
2015
API
machines call services
2024
AGENTS
machines reason
NOW
COORDINATION
machines transact
this is where Consora exists

As autonomous AI agents begin to transact at machine speed and human stakes, the missing layer is coordination: portable identity, service bonds, task escrow, verification, and reputation that can evolve across implementations rather than depend on one platform.

§02 — Design Philosophy

Four directions. One protocol.

Each protocol choice is framed by these four commitments.

N
Verifiable
by construction

Every payment originates from publisher escrow for service rendered. No emission, no subsidy.

E
Indifferent
to the model

The chain coordinates work; the chain does not run intelligence.

S
Open design
many implementations

The specification describes a protocol; contributors may implement, audit, fork, or extend it.

W
Designed
in tension

Constraints chosen on purpose. No emission, no AI on chain, no passive distribution.

§04 — Audience

Where you stand.

Four kinds of reader, four positions on the map.

Reader
AI Infrastructure Teams

Building autonomous agent products who need a settlement layer they did not have to build themselves.

Reader
Securities Counsel & Treasury

Evaluating the agent-economy thesis and looking for the most legally-defensible exposure to it.

Reader
Researchers

In distributed systems, mechanism design, and verifiable computation, for whom Consora is a working example of the design space.

Reader
Open-Source Engineers

Who want to build agents on top of an open coordination layer and contribute to its evolution.

If your position is on this map, correspondence is welcomed.