AUTHORITY DOCSDocumentation for the layer beneath the doors — not a door itself.the core laws →
AUTHORITY · DOCUMENTATION

The authority canon. One rule, written down.

Every system in the ecosystem — ECHO, ECHO ID, MESH, STACK, LORE — rests on one rule system: power stays closer to the human than to the machine. This is its documentation, read in the order the stack is built.

This is not a sixth door. The five doors are what you use. This is the rule system underneath all of them — grant, verify, revoke, prove.

Built to try · tools and reference labs

Authority Tools

Explore all tools →

Reference labs use test units. PULSE, heartbeat, WebAuthn and QR lab interfaces are in English. Physical sensors, authenticators and QR timing still need field validation.

Experimental · offline phone link

PULSE QR lab

Use a phone and a second device to exchange signed PULSE messages by QR. Open the phone role on your phone and the executor role on the other device, then follow the setup steps.

Lab only: no real payments. A scan grants no authority and proves neither distance nor biological presence.

Physical-phone cameras and five-second timing still need field testing. Lab interface: English.

MONEY MUSK · HUMAN AUTHORITY SECURITY PROFILE

Bounded permission. Verifiable evidence.

Echo Atlas is Money Musk's existing architecture map. The Human Authority Model defines the governing semantics. This section adds implementation safeguards and their verification scope.

The TypeScript security profile 0.2 pins human root keys, binds each delegate to its exact key, checks the complete delegation chain, and rejects unsupported or malformed authority. An agent proposes an action; the service performing it must enforce the human's limits.

Keys and delegationTrusted root policies, signed parent bindings, shared ancestor limits and current revocation checks.
Authenticated evidenceSeparate signed decision, dispatch and outcome receipts. Verification requires independently trusted signer keys.
Local demonstrationsOne-use grants and complete metadata commitments for new history entries. A local hash does not authenticate a human or prove settlement.
Kernel owner boundaryKernel reads, grants, policies and decisions now require exact-action Echo key signatures, with durable replay checks and separate key-owned records. Callsigns do not establish ownership. This proves key control, not physical human presence.
Production integrationThe Kernel migration and deployment configuration require isolated rollout checks. Connecting payment executors to the delegated-authority verifier, durable reservations and provider reconciliation still require separate evidence.

These are tested reference safeguards. They are not an independent security audit or a claim that live payments, recovery or external outcomes have been verified. Older Rust/WASM examples use a separate profile and do not certify this implementation.

01
Philosophy

Foundation

02
What authority is

Formal Model

03
The blueprint

Specification

04
How it is enforced

Runtime

05
A shared language

Adoption

06
What actually happened

Proof

07
The human in command

Control surface

Inside the specification

Concepts that live in the protocol

These are not separate pages — they are load-bearing sections of the Authority Protocol, each demonstrated by the live verifier there.

Reference implementations and their scope

The reference implementation

The five-crate Rust toolkit includes a WebAssembly demonstration on the protocol page. It uses the legacy profile. Its test results and the TypeScript security profile 0.2 results have separate coverage; agreement on examples does not establish production security.

echo-authority-coreecho-border-controlecho-authority-testsecho-authority-wasmecho-authority-cli

Five systems. One authority model. Authority governs.