Sebuah mandat adalah artefak, bukan pengaturan.
Delegasi terbatas adalah kemampuan di dalam Execution Authorization, bukan kategori tersendiri. Sebuah Task Contract membingkai rantainya; ia tidak menggantikan satu pun bagiannya. Setiap langkah tetap menghasilkan Execution Grant sekali-pakai miliknya sendiri dan Action Receipt miliknya sendiri.
Rancangan
TaskContractV1
Kontraknya mengikat, dalam satu objek bertanda tangan: tenant, para aktor yang boleh bertindak di bawahnya, Guardian dan audience yang dituju, revisi, langkah-langkah, batasannya, anggaran dan satuannya, jendela keberlakuan, kebijakan dan manifes yang berlaku, serta penghitung pencabutan.
taskId · revisionIdentitas dan versi. Kontrak yang sudah disetujui tidak pernah diedit di tempat: setiap perubahan pada sebuah langkah menghasilkan revisi baru yang harus ditinjau ulang.
tenant · guardianId · audienceMilik siapa ia dan titik eksekusi tunggal mana yang boleh mengonsumsinya. Satu mandat dialamatkan ke satu Guardian.
actors[]Setiap aktor mengikat sebuah pengenal ke sebuah kunci dan thumbprint-nya. Sebuah langkah diklaim dengan membuktikan kepemilikan kunci itu terhadap tantangan yang baru, yang dikonsumsi secara atomik.
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[]Setiap langkah menyebut operasi kanoniknya, penyedianya, daftar sumber dayanya, digest parameter persisnya, dan membawa maxUses yang terkunci pada satu.
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 · expiresAtJendelanya. Sesudah itu tidak ada langkah baru yang dikirim; tidak ada masa tenggang dan tidak ada perpanjangan dari dalam tugasnya.
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.
Irisannya tetap berlaku
izin efektif = mandat ∩ grant ∩ kebijakan lokal bertanda tangan ∩ batasan adapter ∩ anggaran ∩ identitas ∩ keberlakuan dan pencabutan
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.
Mesin status
Sebuah tugas menempati tepat satu status, dan yang dicatat ledger adalah transisinya, bukan niatnya.
- draft
- approved
- running
- paused
- completed
- revoked
- expired
Pengecualian yang disengaja
- Tanpa subdelegasi. Satu mandat, satu Guardian, satu anggaran; sebuah tugas tidak bisa menyerahkan sebagian dirinya ke aktor lain maupun mendirikan titik eksekusi kedua.
- Tanpa efek terbuka. Langkah tanpa operasi kanonik dan tanpa digest parameter bukanlah sebuah langkah.
- Tanpa otorisasi permanen. Setiap mandat kedaluwarsa, dan kedaluwarsanya tidak bisa diperpanjang dari dalam tugas.
- Apa yang dibaca aktor — dokumen, keluaran tool, konten web, memori — adalah masukan, tidak pernah otoritas. Itu tidak bisa memperluas kontraknya.
- Adapter yang menentukan efek kanonik dan keadaan awal. Ringkasan sebuah agen, skema hanya-baca, atau tujuan yang diambil dari konten tidak diterima sebagai kebenaran.
Peran pembaca
Pembaca lokal bersifat menjelaskan. Dalam profil ini sebuah temuan tunggal, abstain, tidak-dievaluasi, atau pembacaan sebagian tidak memblokir, tidak mencabut, dan tidak memaksa persetujuan tambahan atas efek persis yang sudah disetujui dan diizinkan. Otoritas tidak pernah dinaikkan untuk mengompensasi sebuah peringatan, dan tidak pernah diturunkan karena tidak ada peringatan yang muncul. Identitas, tanda tangan, anggaran, prasyarat, dan pencabutan tetap gagal dalam posisi tertutup — ini bukan izin untuk menjalankan tanpa kontrol.
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.
Status
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.
Pertanyaan terbuka
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.