enumeray model release status

Inspect saved release progress, readiness, trial evidence and the next action.

Use when: You need to diagnose a release or reconcile an uncertain activation reply.

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 status release-r1

Candidate-is-current observation is distinct from an activation receipt. When trial access is available, trial_init_command shows an exact-candidate analysis initialization example: replace INPUTS.json and NEW_TRIAL_DIR, or choose --example NAME instead of --inputs. This guidance stays separate from the release next_command and activation guard. Publication-keyed trial evidence includes analysis executions automatically. Trial success is advisory; blocked trial access does not itself block publication activation.

Inputs and options

Input	Meaning and use
<DIRECTORY>	Existing private release directory.

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

Result and next step

Refreshes authorized observations and local evidence without registering, activating or changing the saved expected-current guard.

Resolve the reported blocker or follow the displayed next command.

Exact syntax, defaults and accepted values

Inspect progress and trial evidence without changing the activation guard

Usage: enumeray model release status [OPTIONS] <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
      --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