Grant Is Not Mandate: The Gap Between Them Is Exposure Nobody Accepted
Summary
Superseded in place by a sharpened same-day version, which adds the argument below on prohibitions. A vocabulary split with a measurement inside it: a grant is the union of capabilities conferred at assignment, a mandate is what the holder is authorised and expected to do, and in practice the first is much larger than the second. The difference — excess authority — is blast radius measured from the other end, and it is unaccepted by construction, so it defaults to critical and escalates without anybody escalating it. The brief corrects a 17 July claim (to grant is to mandate — they coincide only in the rare case), gives a mandate its five required fields (issuer, subject, scope, interval, revocation path — a mandate with no interval is a grant wearing a mandate's name), separates enforcement (an execution broker, where grant and mandate coincide by construction) from instrumentation (a declared mandate, honest only when called that), and notes an instruction in a chat is not a mandate at all.
Key concepts
- Excess authority — grant minus mandate — the registry's countable product, drawn as D7
- The five fields — issuer, subject, scope, interval, revocation path — four already published here
- Enforcement vs instrumentation — the broker bounds the grant; a declared mandate measures it
- Agent cards as the partial home — scope-of-authority declared; the issuer signature and interval are the missing half
Key ideas
- A deny-list mandate widens SILENTLY every time the provider ships a feature — the world is open, so an allow-list is the only form that stays correct.
- Excess authority is only well defined against an allow-list: a difference taken against a deny-list is the whole open world minus three named items.
- Prohibitions still belong in the record as annotations — they carry intent an allow-list cannot express — but never as what a checker consults.
- An instruction in a chat has no issuer, no interval, no record and no revocation path — a different kind of object.
- Mandate compliance measured on a cooperative agent says nothing about an injected one.
On this site
Folded into the registry MVP pack as change-control entry C1 — the grant redefinition that makes excess authority the registry's countable product.