enumeray model release revoke-delegation

Permanently revoke a candidate handoff.

Use when: The captured grant holder or current model owner needs to withdraw delegated trial and activation authority.

Role and prerequisites: Model owner or current co-admin. Install enumeray, configure the API and log in. Use an account or delegated token with the required permissions. Example IDs must be replaced with IDs from your service.

Example

enumeray model release revoke-delegation release-r1 33333333-3333-4333-8333-333333333333 --generation 3 --dry-run
enumeray model release revoke-delegation release-r1 33333333-3333-4333-8333-333333333333 --generation 3

Requires me:read, models:read and models:manage. Role removal or suspension of either participant invalidates handoffs permanently; restoring their account or role does not revive old trials.

Inputs and options

Input	Meaning and use
<DIRECTORY>	Existing private release directory; a model owner can adopt the candidate into their own directory.
<DELEGATION_ID>	Retained delegation UUID from the handoff receipt or delegation inventory.
--generation <GENERATION>	Observed resource generation from the relevant get, members, policy or limits response. This is an optimistic concurrency check, not a release number. Read again after a conflict; do not blindly increment it.
--dry-run	Inspect the proposed revocation without saving or sending a mutation.

Every command also accepts the profile, API, JSON and timeout options.

Result and next step

Checkpoints the exact mutation and retains the revocation reply. Published standard model execution is independent of the handoff.

Inspect release authority. Restoring delegated authority requires a fresh handoff.

Exact syntax, defaults and accepted values

Permanently revoke a retained candidate handoff

Usage: enumeray model release revoke-delegation [OPTIONS] --generation <GENERATION> <DIRECTORY> <DELEGATION_ID>

Arguments:
  <DIRECTORY>      Existing private release operation directory created by model release init
  <DELEGATION_ID>  Candidate handoff UUID retained in model release status

Options:
      --api <API>                User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --generation <GENERATION>  Observed model_generation from model release status; shared by model governance changes
      --dry-run                  Inspect the observed and proposed change without applying it
      --profile <PROFILE>        Named local user API/login profile; host/runner commands use explicit configuration [default: default]
      --config <CONFIG>          Private user profiles file; defaults to $XDG_CONFIG_HOME/enumeray/profiles.json or ~/.config/enumeray/profiles.json
      --json                     Emit user API results as JSON (NDJSON for following logs) and runtime errors on stderr; host/runner output follows its own protocol
      --timeout <TIMEOUT>        User API HTTP timeout in seconds; live logs use it for read inactivity. Does not limit execution time [default: 60]
  -h, --help                     Print help