enumeray model release delegate

Authorize a named active model administrator to trial and activate this exact candidate.

Use when: The captured compute-grant holder wants to hand review or activation to another account or CI.

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 delegate release-r1 --user 11111111-1111-4111-8111-111111111111 --generation 2 --dry-run
enumeray model release delegate release-r1 --user 11111111-1111-4111-8111-111111111111 --generation 2

Requires me:read, models:read and models:manage plus ownership of the captured grant. Repeat the same recipient and generation after interruption to reuse the saved UUID. A fresh handoff needs a freshly observed generation. Neither participant may redelegate borrowed authority.

Inputs and options

Input	Meaning and use
<DIRECTORY>	Existing private release directory for the registered candidate.
--user <USER>	Active current model administrator account UUID. The recipient does not need a separate compute grant.
--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 handoff without saving or sending a mutation.

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

Result and next step

Saves the request and delegation UUID before sending. Returns the retained handoff, including any permanent revocation on replay.

Give the recipient the model and publication IDs; they adopt their own release directory with model release init --candidate and create a separate trial directory with analysis init --candidate.

Exact syntax, defaults and accepted values

Authorize a named model administrator under the captured compute grant

Usage: enumeray model release delegate [OPTIONS] --user <USER> --generation <GENERATION> <DIRECTORY>

Arguments:
  <DIRECTORY>  Existing private release operation directory created by model release init

Options:
      --api <API>                User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --user <USER>              Stable UUID of the model administrator receiving the candidate handoff
      --generation <GENERATION>  Observed model_generation from model release status; shared by model governance changes
      --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
      --dry-run                  Inspect the observed and proposed change without applying it
      --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