跳到主要內容
回到文件Action Proof · 有界委派
規範

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 是原子消耗的。

  • authority

    Set 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 固定攜帶為一。

  • budget

    Durable 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 · revocationVersion

    The 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.

  1. 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.
  2. 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.
  3. 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.
  4. 04Revocation is optional in the task runtime, and it is checked before the provider preflight rather than at the moment of sending.
  5. 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.
  6. 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.

有界委派 — Task Contract 規範 | SecureStamp Foundation