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.

01
Philosophy

Foundation

The Core Lawslaws
Twelve laws in four articles — the constitution the whole system answers to.
The Echo Constitutioncharter
Eleven articles of human sovereignty, in plain language.
Prior Art & Design Lineagelineage
What this protocol inherited, and from whom — SPKI, macaroons, UCAN and the rest — plus what prior art still does better than we do.
02
What authority is

Formal Model

The Human Authority Modelfoundational
Where authority comes from, how it moves, shrinks, expires — and what machines can never do with it.
03
The blueprint

Specification

The Authority Protocol · Draft 0.1spec
The normative spec: Authority Object, Invocation, deterministic Border Control, reason codes, attenuation.
The Authority Objectprimitive
The smallest unit of human authority — the grammar every grant is written in.
04
How it is enforced

Runtime

Border Controlenforcement
Deterministic enforcement. Intelligence detected, authority unknown — does the action fit the grant?
Authorize with Echoflagship
The honest replacement for 'Sign in with Google' — exactly what an app may do, and nothing it can smuggle.
05
A shared language

Adoption

The Human Authority StandardHAP-1
HAP-1 — the eight questions and the Universal Receipt. Like HTTPS, but for authority.
06
What actually happened

Proof

The Authority Graphledger
One history you hold: everything you delegated, and what happened — opaque heads only.
07
The human in command

Control surface

The Human Authority Centerdashboard
The human control surface: active grants, delegations, revoke, and your standing across the ecosystem.
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.

Invocation Objectthe exact action attempted, signed by the acting agentAttenuation & delegationa child grant can only ever narrow its parent — never widen itReason codesthe fixed vocabulary every DENY speaks inConformance vectorsthe hostile suite two implementations must both passInterop adaptersOAuth / MCP / OpenAI grants re-represented, never silently expandedBitcoin anchoringthe authority-log tip, notarized so even the operator can't rewrite it
Two implementations, one verdict

The reference implementation

The standard is real because a second, independent implementation agrees on every vector. A five-crate Rust toolkit — compiled to WebAssembly, it runs live in your browser on the protocol page.

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

Five systems. One authority model. Authority governs.

The Human Authority Model →The Authority Protocol →The Human Authority Center →The Core Laws →