mandate 是一份产物,不是一个设置项。
有界委派是 Execution Authorization 之内的一种能力,不是另起一个类别。Task Contract 为这条链条定下框架;它不替换其中任何一环。每一步仍然产生自己那份一次性的 Execution Grant 和自己那份 Action Receipt。
设计
TaskContractV1
这份合约在单一的签名对象中绑定:tenant、可在其之下行事的行为者、它所指向的 Guardian 与 audience、修订号、步骤及其约束、预算及其单位、有效窗口、生效中的策略与 manifest,以及吊销计数器。
taskId · revision身份与版本。已批准的合约从不就地修改:任何一步的改动都会产生一个需要重新评审的新修订。
tenant · guardianId · audience它属于谁,以及哪一个执行点可以消费它。一份 mandate 只指向一个 Guardian。
actors[]每个行为者把一个标识符绑定到一把密钥及其 thumbprint。认领一个步骤,需要针对一个新鲜的 challenge 证明持有该密钥,而这个 challenge 是原子消费的。
authoritySet per operation by the protocol. The caller neither chooses it nor may degrade it within the same request, and an approved mandate must never lower a step's threshold. The Guardian must refuse, locally, any operation that is not eligible for delegation — even under a validly signed grant.
steps[]每一步点名自己的规范操作、提供方、资源清单、其确切参数的摘要,并把 maxUses 固定携带为一。
budgetDurable and atomic per tenant, task, revision and step. Committed means consumed plus anything reserved whose outcome is pending or uncertain, so one grant cannot reserve twice — and submitting the same task and revision with different content must not open a fresh budget.
issuedAt · expiresAt有效窗口。过了它就不再发出新的步骤;没有宽限期,也不能从任务内部续期。
policyVersion · revocationVersionThe signed local policy in force and the revocation counter. Revocation is checked as part of the send itself, not only before it; if storage or revocation is unavailable, no new effects go out.
交集依然适用
有效权限 = mandate ∩ grant ∩ 签名的本地策略 ∩ 适配器约束 ∩ 预算 ∩ 身份 ∩ 有效性与吊销
The cloud never widens the local ceiling. A mandate is one more term in the intersection, never a way around it, and the Guardian has to enforce all of them before a provider is contacted — for the task runtime, gap 03 below says where that stands today.
状态机
一个任务恰好处在一个状态中,而账本记录的是状态转移,不是意图。
- draft
- approved
- running
- paused
- completed
- revoked
- expired
有意的排除
- 没有再委派。一份 mandate、一个 Guardian、一份预算;一个任务无法把自己的一部分交给另一个行为者,也无法立起第二个执行点。
- 没有开放式效果。一个没有规范操作、没有参数摘要的东西,不算一个步骤。
- 没有长期有效的授权。每一份 mandate 都会过期,而且这个过期无法从任务内部续期。
- 行为者读到的东西——文档、工具输出、网页内容、记忆——是输入,绝不是 authority。它无法扩展这份合约。
- 规范效果与前置状态由适配器判定。智能体的摘要、只读的模式,或从内容里取来的目的地,都不会被当作事实接受。
读取器的角色
本地读取器是用来解释的。在这个配置档下,一条孤立的发现、一次弃权、一次未评估或一次部分读取,都不会阻断、不会吊销,也不会对一个已经批准且被允许的确切效果强加额外审批。绝不会为了弥补一条告警而抬高 authority,也绝不会因为没有出现告警就降低它。身份、签名、预算、前置条件与吊销仍然朝着关闭的一侧失败——这不是可以不带控制就执行的许可。
Known gaps in the local runtime
A local runtime for this profile exists and runs in simulation. A review on 2026-09-23 found these differences between the specification above and the code. They stay listed here until each one is closed with a regression test.
- 01Offline verification of a task bundle treats the expiry of a step's grant as a reason to reject, so a bundle stops verifying minutes after it was issued. A historical proof has to stay verifiable after the authorization it records has expired.
- 02The same verifier rejects correctly signed receipts whose status is failed, indeterminate, revoked or expired. An incomplete task has to be representable as incomplete, not as invalid.
- 03The task runtime does not yet apply the signed local policy, nor a local check that an operation is eligible for delegation. Until it does, the ceiling depends on whoever signs the grant.
- 04Revocation is optional in the task runtime, and it is checked before the provider preflight rather than at the moment of sending.
- 05The task ledger identifies a contract by its digest, so a different contract reusing the same task and revision would get its own budget. There is no transition yet from indeterminate to a reconciled result.
- 06A task bundle does not yet carry the human approval, the local policy applied or the durable claim, so on its own it does not prove separation of duties or the ceiling that bounded the task.
Planned next — not available today
Each item below is part of the current plan. None of it is available today, and each one will appear on the evidence page with its own level — design, simulated or real integration — when it closes.
- Approval bound to the mandate: a single-use challenge tied to the contract digest, the revision, the approver and an expiry. In an organization the requester and the approver are different people, and an open session on its own does not count as a fresh approval.
- A minimal console in securestamp.online to review a proposed task, approve or reject one exact revision, follow its budget and uncertain steps, request revocation and export the evidence.
- Two labels that are never merged. Restricted call: only the tools and arguments the mandate allows reach the server — which says nothing about the server's internal effect. Exact effect: a verified adapter binds operation, resources, parameters and preconditions to the observed result. A route that bypasses the Guardian is labelled not covered.
- The model is shown the approved snapshot of each tool's name, description and schema. A later change stops the affected task instead of reaching the model first.
- Later, and not in the first profile: an authority diff. A task that needs something outside its mandate asks for that exact change; the new revision inherits what was consumed and what is uncertain, and never resets the budget.
状态
Design, with a local runtime in simulation. The schema and its invariants exist and are covered by tests, and the known gaps above are open. No delegated mandate has been executed against a real provider, so this profile is labelled simulated. A result is never extrapolated from a mock or from a different connector, and a legacy connector tested with MFA or quorum does not credit multi-step delegation.
尚未定论的问题
Canonicalization, size and count limits, clock handling and the rejection of unknown fields are fixed in the local contract, and are to be published as versioned test vectors alongside the verifier. The verifier ships before the profile: nothing is emitted that cannot yet be verified independently — which is why the verifier gaps above are closed first.