enumeray analysis attach

Recover an accepted run into a new private analysis directory.

Use when: The original directory was lost or this host has only a run ID or saved acceptance receipt.

Role and prerequisites: Authorized run reader; cancellation still requires the original submitter and runs:cancel authority. 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 attach 22222222-2222-4222-8222-222222222222 --directory recovered-analysis
enumeray analysis attach --receipt run-receipt.json --directory receipt-analysis

Attachment uses the selected API/account and grants no new access. Original local sources and access to today’s current publication are unnecessary. Unavailable local-only paths, fingerprints and upload checkpoints remain explicitly unavailable. Model-administrator inspection does not confer submitter cancellation. See recovery.

Inputs and options

Input	Meaning and use
[RUN_ID]	Accepted run UUID from authorized history or a retained receipt. Choose either this ID or --receipt.
--receipt <RECEIPT>	Existing private acceptance-receipt JSON file. Mutually exclusive with RUN_ID; the receipt is checked against authorized run evidence.
--directory <DIRECTORY>	New private analysis directory, or the same interrupted attachment destination. Its parent must exist.

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

Result and next step

Reads authorized run/provenance records and saves accepted inputs, the exact publication/contract, purpose and available evidence. No upload or submission occurs. Repeat the same command and directory after interruption; unrelated destinations and conflicting evidence are preserved.

Use analysis status/logs/wait/cancel/collect with the recovered directory. An attached directory cannot submit another execution.

Exact syntax, defaults and accepted values

Reconnect to an accepted run without preparing or submitting another execution

Usage: enumeray analysis attach [OPTIONS] --directory <DIRECTORY> [RUN_ID]

Arguments:
  [RUN_ID]  Accepted run UUID; provide either this ID or --receipt

Options:
      --api <API>              User API origin override; credentials never cross origins. Host/runner commands use explicit configuration
      --receipt <RECEIPT>      Original saved acceptance receipt; its identity is checked against the service
      --directory <DIRECTORY>  New private analysis directory, or the same interrupted attachment destination; parent must exist
      --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