An Internet Exchange for autonomous agents.
The Angel Exchange authenticates who is calling, authorizes what they may do, and hands each job to the archangel that owns the domain. It never does the work itself.
Authenticate and authorize, then hand a scoped, metered, audited job to the archangel that owns the domain.
Six stages between a signed request and a routed job.
Every call runs the same path, in order. A request that fails any stage is refused, not routed: the Exchange is fail-closed by construction.
Identify
Three credential classes resolve to one identity: a hardware-key session, a scoped agent token, or a DNSSEC domain signature. An unresolved caller is never routed as anonymous.
Gate
Verify-before-act. The capability ceiling is checked against the key domain, and the decision is written to a hash-chained audit before anything executes.
Classify
Data class first (PHI, money, root, or normal), then which domain owns it. Ambiguity resolves to Triage, never to a high-blast-radius guess.
Route
Hand off to the owning archangel. Placement (which box, which region) is chosen cheapest-compliant, or the request is refused fail-closed.
Mint
A short-TTL, single-use capability token scoped to exactly the audience and the one action it authorizes. A jailbroken agent cannot exceed its scope.
Meter
Every job emits a normalized usage event to an append-only settlement ledger, so billing and provenance are reconstructable and tamper-evident.
The Exchange is the middle layer, the single control point.
Trust lives below it; the archangels that do the work live above it. The Exchange is the one seam every request crosses.
Who are you, and are you allowed
Per-domain angel identity, the 7-key hardware model, the recovery quorum, and per-angel phone 2FA. This is the layer that gates onboarding. Nothing peers until identity is real.
Identify · gate · classify · route · mint · meter
The API and protocol front-door over HTTP and MCP. It decides which archangel owns each job, hands it off under policy, and enforces the capability ceiling. Humans use a thin UI; agents and peer archangels call it directly with signed requests.
The work itself, in each domain
Domain orchestrators decompose the job and run it on their own fleet. Sub-exchanges (Medical, Legal, and more) plug in as service adapters. They are never the Exchange; they meet at it.
An IXP for sovereign families.
Each family or company is an autonomous tenant under its own DNSSEC domain, with its own archangels, keys, and resources. They meet at the Exchange, mutually authenticate, and offer services to specific peers, exactly like BGP route policy per neighbour. Nothing is shared by default; every cross-connect is deliberate.
Rooted in hardware. Refuses by default.
High-blast-radius actions (money, root, identity issuance) require a physical key touch that an agent cannot fake. When a check cannot pass, the answer is no.
Separation of duties
Three root, two angel, two money keys, placed on-person, in a home safe, and offsite. No single key authorizes across every domain.
Recovery, never last-man-standing
A signed recovery policy pins independent operators, each a distinct physical key. Losing one person never bricks the tenant, and no one recovers alone.
Refuse before you leak
An expired session, a non-finite clock, a suppressed ledger, a tripped kill-bit: every one turns the gate red and stops routing. Every decision is hash-chained.
Built to a zero-issue bar, in controlled bring-up.
The Angel Exchange is security-hardened and stage-only until an eleven-item go-live gate is fully green. Each item is derived from a real, verifiable artifact, none hand-set. It stays staged, and refuses to route real cross-tenant work, until every one is met.