enumeray model release review

Review a ready candidate against the current publication and save the activation guard.

Use when: You have reviewed candidate trial evidence and want to prepare activation, including after a competing publication update.

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

This is the only release command that refreshes a saved review guard. It does not activate. Trial evidence is included automatically from candidate analyses, including failed/cancelled trials; it never becomes an activation requirement. Another account’s compute grant cannot be substituted; a named delegation authorizes trial and activation under the original grant. The saved review pins that delegation.

Inputs and options

Input	Meaning and use
<DIRECTORY>	Existing registered, ready release directory.

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

Result and next step

Shows scientific identities/contracts, installation, execution location, disclosure and trial evidence. Saves the observed expected-current publication for explicit activation.

Complete scientific checks and explicitly run model release activate with this directory.

Exact syntax, defaults and accepted values

Review the comparison and explicitly refresh the expected-current guard

Usage: enumeray model release review [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