🔐Authorization and Fixed Tools
Authorization is the proof that a workflow step may use a particular value or mutate a protected application object. A fixed Tool requirement is the discovery constraint that the skill expects a particular Tool; the two checks work together but neither replaces the other.
Proven values and grants
The workflow carries proven values through a worksheet and can issue a Task-bound grant for a protected vertex. The grant binds the intended recipient or state object to the Agent skill and is copied into the execution when the Task is dispatched. A Tool consumes the proof and checks the expected object, witness, or capability before mutating application state.
The stored Grant<T> material is copyable (T must be copy + store), so a recurring Task does not consume a remaining-use counter. The configured grant count is the number of protected-vertex entries in the Task-bound vector, not a quota or balance. Each execution copies the appropriate material into a one-use ProvenValue; that copied proof must still match the recipient UID, worksheet, vertex/Task context, and input commitment before the Tool mutates state.
Fixed Tool requirements
A fixed Tool entry records the Tool FQN and registry identity that a skill expects. Registration checks that the FQN is registered at transaction time, but application developers should also read back the selected DAG vertex, Tool ID, registry ID, immutable schema, authorization mode, witness, and business policy. This is how an application prevents a discovery match from being mistaken for proof of asset authorization.
Protecting a business asset
Keep the business object and its mutation capability in explicit application custody.
Bind the protected vertex to the expected Tool and skill requirements.
Create the Task with the authorization binding for the intended recipient or object.
Let execution carry the grant and worksheet to the Tool.
Have the Tool check its own state invariant before performing the mutation.
Verify the accepted output and resulting business state after settlement.
Authorization does not decide whether an off-chain response is trustworthy. Use Verifiers and Result Trust for that decision and Registered Keys and Signed Tool Communication for signed-message mechanics.
Next
Continue to Registered Keys and Signed Tool Communication for key-bound evidence.
Last updated

