Limits and manifests
Limits live in a policy outside the model. Each agent also carries a signed manifest that lists what it can do, and a delegated manifest can only narrow its parent.
On this page
There are two layers of limits. The policy states what any agent can do for an operation. A manifest states what one agent identity can do. An action must pass both.
Policy limits#
A policy names each operation and gives it a level, an optional maximum, an optional approval threshold, an optional currency and a retry rule. Two daily caps apply across operations: one per account and one for the whole team.
| Field | Effect |
|---|---|
level | One of Assist, Draft, Execute with Approval, Execute within Limits. Only the two Execute levels can run. |
max_amount_minor | An amount above it is blocked. |
approval_above_minor | An amount above it needs approval. |
approvers_required, approval_bands | How many approvers sign. See maker and checker. |
caps.team_per_day_minor, caps.per_customer_per_day_minor | Shared daily caps, enforced when an amount is reserved. |
egress.allow_hosts | The only hosts the egress gateway can reach. Without it nothing leaves. |
The schema is in the policy file reference. Any change to a level, limit, currency, retry rule or cap changes the policy hash, which every approval binds to.
Manifests#
Every agent has its own key and its own manifest. The manifest states which action kinds the agent runs, up to which amount, in which currency and to which destinations. Everything else is denied.
actions = {
"payout": {"max_amount_minor": 50000, "currency": "INR", "destinations": ["bank-a", "bank-b"]},
"report": {"destinations": ["partner-bank"]},
}- An action kind that is not listed is denied. An unknown key id is denied.
max_amount_minoris optional. When present, the action carries an amount at or below it.currencyis optional. When present, the action uses it.destinationsis an explicit list. When it has entries, the action names one. When it is empty, the action names none. There are no wildcards.
Delegation only narrows#
The bank's root key signs the root manifest. A child manifest is signed by its parent's subject key and carries the hash of the parent's signed manifest. A child is refused when it adds an action kind, raises or drops a cap, drops or changes a currency, or adds a destination. issue() raises ManifestError, and verify_chain() rejects the same widening in a hand built chain, even when the widened manifest carries a valid signature from its issuer.
from verdock.manifest import ManifestRegistry, issue, key_id
root = issue(root_seed, parent_agent_public_key, root_actions)
child = issue(parent_agent_seed, child_agent_public_key, narrower_actions, parent=root)
registry = ManifestRegistry(root_public_key)
registry.add(root); registry.add(child)
registry.check(key_id(child_agent_public_key), "payout", 9000, "INR", "bank-a")check returns {"allowed", "reason", "chain"}. The receipt records the full signed chain from the root to the acting agent in params.delegation. verify_log(lines, anchor, manifest_root=root_public_key) checks every signature, every link, every narrowing step and that the action fits every manifest on the chain. The reason strings are in failure reasons.