Terminology

Term	Meaning
Account / user	An individual with a stable UUID. Federated identities bind issuer and subject.
Owner / co-admin	Resource-specific administration. An account can administer one model or connector without administering another.
Model	A stable offering with metadata, administration and an independently controlled access policy.
Installed release	Files installed under an approved release directory. Installation is arranged outside Enumeray.
Publication	An immutable scientific definition and installation snapshot identified by one release ID; activation selects the current publication.
Provider binding	Internal key allocated by registration and reused for the same model/context with identical physical installation settings and scientific installation identities.
Execution disclosure	Execution location and scientific-data access information retained by publications and accepted runs.
Connector	A compute resource with an explicit owner and optional co-admins. Its host process coordinates over outbound HTTP and retains job ownership and transfer evidence in private durable state.
Execution context	Connector-approved driver, connection, identities, roots and operational capacity.
Compute grant	Permission for a publishing account, including a model owner or co-admin, to use a context, with admission limits. It does not create an OS account or install software.
Driver	Backend job lifecycle, currently foreground process or Slurm.
Connection	Transport to the compute runner, currently direct or SSH.
Wrapper	Model-owned translation between scientific inputs/results and the versioned wrapper protocol.
Run	Accepted scientific work pinned to the original publication, inputs, execution destination and installation snapshot.
Assignment	Connector-owned execution of an accepted run, tracked separately from the public run state.
Artifact	Verified file metadata referring to an exact stored object version, size and SHA-256.
Analysis directory	Private local workflow retaining reviewed inputs, execution identity, receipts, observation checkpoints and collected evidence. Reusing it continues the same operation.
Saved release	Private author/reviewer directory retaining one candidate, readiness observations, explicit review and activation recovery.
Candidate	An exact publication being validated or trialed before explicit activation as the current publication.
Current publication	The model owner’s selected offering for new standard runs; historical accepted work remains pinned to its original publication.
Collection	Immutable manifest of named file paths and exact artifact versions; current byte availability is a separate observation.
Prepared operation	Privately saved request and idempotency identity, reused after an uncertain reply.
Generation	Observed management version supplied with guarded changes. Connector configuration generation and ownership_generation are independent; contexts and grants have their own generations.
Provenance	Export of retained identities and evidence for interpreting an accepted run.

Use architecture and responsibilities to select the relevant workflow. The lifecycle reference distinguishes states, phases, cancellation and publication readiness.