enumeray model release activate

Explicitly activate a saved reviewed candidate with its exact expected-current guard.

Use when: The candidate is ready, its comparison/disclosure has been reviewed and scientific checks are complete.

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

A changed current publication stops activation. Retrying an uncertain uncommitted request preserves its body; resume/status only observe. If activation already made this candidate current, the workflow reports that evidence without inventing a missing receipt or reactivating a historical publication.

Inputs and options

Input	Meaning and use
<DIRECTORY>	Existing release directory with a saved ready review.

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

Result and next step

Rechecks current authority and reviewed evidence, checkpoints the activation request and applies the existing guarded API operation. Accepted runs keep their original snapshots.

Inspect status and current availability. A conflict requires another explicit review before activation.

Exact syntax, defaults and accepted values

Explicitly activate using the saved review and expected-current guard

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