enumeray analysis collect

Collect terminal inspection, effective inputs, scientific outputs, provenance and verified files.

Use when: Your accepted run is terminal and you need a resumable evidence bundle.

Role and prerequisites: Authenticated model user with access to the resource. 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 analysis collect analysis

Original input bytes remain outside the directory. The bundle contains accepted artifact references and any available local source evidence; attachment cannot reconstruct missing paths/checksums or transfer checkpoints. Optional output failures remain visible. A collect exit of 0 means the requested collection step succeeded, including partial or evidence-only selection and evidence for failed/cancelled runs. Check complete:true and bundle.json for verification of every output.

Inputs and options

Input	Meaning and use
<DIRECTORY>	Existing private analysis directory with a terminal accepted run.
--member <SLOT=PATH>	Select exact output collection members: SLOT=PATH. Repeat for several members. Other output bytes remain deferred; complete manifests and provenance are retained.
--evidence-only	Save terminal evidence and complete collection manifests without downloading scientific bytes. A partial bundle is not marked complete.

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

Result and next step

Writes bundle.json with output-name mappings and results/files/ verified against retained size/SHA-256 evidence. Repeated collection verifies existing files, adopts exact matches and preserves conflicts. Scientific failure/cancellation is recorded separately from collection completeness.

Retain the directory and original source files as needed. Whole-file retries remain bounded by current transfer limits.

Exact syntax, defaults and accepted values

Collect terminal evidence and checksum-verified files; resume without overwriting conflicts

Usage: enumeray analysis collect [OPTIONS] <DIRECTORY>

Arguments:
  <DIRECTORY>  Existing private analysis directory bound to this API and account

Options:
      --api <API>           User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --member <SLOT=PATH>  Select a collection output member: SLOT=PATH with a collection-relative path. Repeat for several members; other output bytes remain deferred
      --evidence-only       Save terminal evidence and complete manifests without downloading scientific bytes
      --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