Renew a licence (execute proposal)
license_renewExecute a confirmed renewal proposal to mint a successor licence with renewed terms, link it to the previous licence, and mark that licence superseded.
Instructions
Execute a renew proposal: mint a successor licence carrying the renewed terms, linked to the previous licence, which is marked superseded. Requires the proposal_id, the confirm token bound to its hash (confirm-renew-...), and a live mandate covering the product and the renew operation class. Issuance is journalled before the new artefact is returned. Returns the new licence id, artefact, hash, payload, and receipt. A proposal executes exactly once.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"proposal_id": "<proposal_id>",
"confirm_token": "<confirm_token>",
"_tenant_id": "<_tenant_id>",
"_principal_id": "<_principal_id>"
},
"name": "license_renew"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| _tenant_id | Yes | Tenant the call acts for. The tenant must exist; an unknown tenant is refused with state LICENSE_UNKNOWN. Transport authentication is a deployment concern -- this parameter scopes the call, it does not authenticate it. | |
| proposal_id | Yes | Proposal id returned by the matching propose tool. The proposal must still be in proposed state and belong to the caller's tenant; anything else is refused and logged. | |
| _principal_id | Yes | Acting principal inside the tenant. Principal-gated tools refuse unknown principals and principals of the wrong class; executions (tier T2) additionally require a live, unexpired mandate covering the product and the operation class. | |
| confirm_token | Yes | Confirm token bound to the proposal hash, in the shape confirm-<verb>-<proposal_id>-<first 12 of the proposal hash>. A token bound to any other proposal or hash is refused and logged; the token is the human-confirmation step of the propose -> confirm flow and is single-use. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| payload | No | ||
| receipt | No | ||
| artefact | No | ||
| license_id | No | ||
| artefact_hash | No |