Mandates.

Today every protected action asks a person, and the ask is bound to the exact action. That is safe, and it caps a role at supervised work. A mandate is a grant of authority that stands: chase overdue invoices up to three times, under a stated amount, never issue a credit note, until the end of the quarter.

It is granted to a department, bound to a principal, and every exercise of it is a receipt. It can be revoked, and it expires. It is the power of attorney for a role, written down.

A finance director or a regulator does not need to see every approval. They need to see what authority was granted, by whom, with what limits, and what was done under it. A mandate gives them that on one card, and the receipts give them the rest.

No mandate will go live without a replay: Q runs last month's work under the proposed mandate and shows what it would have done. The card is approved against that record, not against a description.

Today there are no mandates. The approvals store knows two policies, required and advisory, and every protected action waits for a person. Nothing on this page is available, and the site says so rather than implying otherwise.

Mandates are the first thing to build, before the ledger across systems and qualification by replay, because the first operating role cannot run unattended without them. They will appear in the registry before they appear as a claim.