enumeray model publication

Inspect one immutable publication candidate and its validation state.

Use when: You are waiting for connector validation or investigating a failed candidate.

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 publication scalar-double scalar-v1

Inspect caller-specific trial eligibility, state counts and latest successful trial references. Use run get/logs/artifacts/provenance to review execution evidence; scientific validation remains author-owned.

Inputs and options

Input	Meaning and use
<ID>	Managed model ID.
<PUBLICATION>	Immutable publication ID from model publications or model release status. Inspect status before activation or revocation.

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

Result and next step

Returns candidate status and retained context/installation evidence. Registration alone does not make it available to users.

Activate only a ready, authorized candidate; diagnose a failed installation through publication troubleshooting.

Exact syntax, defaults and accepted values

Inspect an exact publication, readiness and captured execution settings

Usage: enumeray model publication [OPTIONS] <ID> <PUBLICATION>

Arguments:
  <ID>           Stable model ID from model list/get or supplied by its author
  <PUBLICATION>  Immutable publication ID from model publications or model release status

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