mandate は成果物であって、設定項目ではありません。
限定委任は Execution Authorization の内側にある能力であり、独立したカテゴリではありません。Task Contract は鎖を枠づけるものであって、その部品を置き換えるものではありません。各ステップは引き続き、自身の単回使用の Execution Grant と自身の Action Receipt を生みます。
設計
TaskContractV1
この契約は 1 つの署名済みオブジェクトの中で次を結び付けます。tenant、その下で行為してよい行為者、宛先となる Guardian と audience、リビジョン、ステップ、その制約、予算とその単位、有効期間、適用中のポリシーと manifest、そして失効カウンタ。
taskId · revision同一性とバージョン。承認された契約をその場で編集することは決してありません。ステップを変えれば、あらためて見直すべき新しいリビジョンになります。
tenant · guardianId · audience誰のものか、そしてどの単一の実行点が消費してよいか。1 つの mandate は 1 つの Guardian に宛てられます。
actors[]各行為者は識別子を鍵とその thumbprint に結び付けます。ステップは、新しいチャレンジに対してその鍵の所持を証明することで請求され、それは原子的に消費されます。
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 を 1 に固定して持ちます。
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.
状態機械
タスクはちょうど 1 つの状態を占め、台帳が記録するのは意図ではなく遷移です。
- draft
- approved
- running
- paused
- completed
- revoked
- expired
意図的な除外
- 再委任なし。1 つの mandate、1 つの Guardian、1 つの予算。タスクが自身の一部を別の行為者に渡すことも、2 つ目の実行点を立てることもできません。
- 開いたままの効果なし。正規の操作とパラメータのダイジェストを欠くものはステップではありません。
- 恒久的な認可なし。すべての 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.