Concepts#

Read these before you integrate an API or run an operation. They explain the one invariant the whole system enforces — No Token, No Action — and the runtime that produces it: every proposed action is interpreted, evaluated against policy (most-severe-wins, default-deny), and either denied/escalated or granted a short-lived, single-use Ed25519 Authority Token that downstream adapters verify before acting.

Start with What Is Intended for the category, then follow the pipeline through to the token model and the trust boundaries that keep one tenant's authority from ever crossing into another's.

• What Is Intended — the category and the core invariant
• Authority Runtime Pipeline — interpret → resolve → evaluate → issue → enforce
• Authority Token Model — Ed25519 JWT, 300s TTL, single-use nonce, kid pinning
• Tenant Trust Boundary — per-tenant keys and isolation
• Trust Model — what is trusted, what is verified, what fails closed
• Semantic Intelligence — the LIM interpretation layer (and its honest limits today)