§ Thesis · v1 · July 2026
The economy is becoming a nervous system.
Economic coordination is moving from human clock to machine clock. Software agents are becoming economic actors — they hold budgets, buy services, sell work, and settle with each other in milliseconds. Payment cycles, settlement windows, business days, approval flows: all artifacts of a person making the decision. The person is leaving the loop.
A stack is forming around this shift, and 2026 research has converged on its shape: agent-to-agent communication (A2A, MCP), machine payments (x402), and on-chain identity/reputation registries (ERC-8004). Agenomics builds inside that stack — an x402 payment relay, a staked agent registry — plus the layer none of the standards ship: settlement. Milestone escrow, dispute resolution, and execution provenance between agents that have never met.
What we hold to be true
- Agents need accounts, not keys. A private key is all-or-nothing trust. A vault is policy: per-transaction limits, allowlists, rate limits, pause controls, and an audit trail for every action the agent takes.
- Trust must be priced, not assumed. The leading registry standard launched reputation with no economic barrier — an academic study found 59–91% of its reviewers are coordinated Sybils. Agenomics reputation is staked, slashable, and nonce-bound. The attack was priced before it happened.
- Work needs settlement, not just payment. Pay-per-request is a solved problem. Escrowed milestones, rejection, disputes, and reputation consequences are not. That is the core of this protocol.
- Claims must survive checking. This market runs on self-reported numbers. We publish test counts, calibration arithmetic, and rejected alternatives in an open ADR trail — so a skeptical evaluator can check, not trust.
The protocol is chain-agnostic by design: payments speak x402 (chain-neutral by construction), capability manifests are signed JSON, and identity and reputation attest outward — so other protocols can verify an agent without running our stack. It runs on Solana first, because 400ms blocks are machine clock; settlement implementations travel to other chains as real demand arrives — spec-first, not port-first.
Where it stands: v0.1.0 · three packages on npm · four programs on devnet · 580+ tests · external audit pending.