Product capabilities and interface boundaries¶
Platform objects, UI actions, and API calls do not have a one-to-one relationship. Before development, determine which object an operation affects, whether it creates a new run instance, and which ID you need to save.
Model calls and model-service configuration¶
Genesis Model API lets external applications call models directly, including model discovery, chat, Responses, embeddings, and reranking.
Providers, Backends, Endpoints, and Routers in Product configure model services used internally by workflows, semantic models, or agents.
Creating a Provider or Backend in Product does not create a model-call endpoint that can replace the Genesis base URL.
Workflow definitions and workflow jobs¶
A workflow is a process object made of operators and connections. A workflow job is the run instance created each time the workflow is triggered.
Saving or deploying a workflow updates its definition; it does not mean that the workflow has run.
After starting a workflow, save the workflow job ID and query its status, results, and operator statuses.
Pausing a workflow commonly prevents new runs. Do not infer that existing workflow jobs have stopped.
Publishing a WorkItem API service and running an ordinary workflow are separate flows. A successful publication does not mean that the service has been called.
Import tasks and import runs¶
An import task persistently stores its source, destination, and run configuration. An import run is the run instance created each time that task is triggered. After submitting an import task, check the task status, import-run status, and import-task file results separately. Deleting a task record does not automatically roll back data already written to the destination.
Agent tasks and automation tasks¶
When an agent is called through A2A, a Task represents one agent execution and artifacts are the text, data, or files produced by that execution. An automation task is a long-lived named task with a trigger; every trigger produces a history record. For either type, a successful request submission alone does not establish that execution is complete.
User accounts and workspace members¶
A user account is a platform-level login identity. A workspace member is the relationship between that user account and the current workspace, with member status, roles, and tags. Inviting, removing, or changing a role applies to the workspace member; it does not create or delete the platform account.
Data publications and subscriptions¶
A data publication publishes selected data objects to a target workspace. A data subscription establishes access to that publication in another workspace. Deleting a data subscription does not delete source data. Before deleting a publication, check existing subscriptions and downstream dependencies.
Confirm before using an interface¶
Whether the page documents a public API, SDK method, or CLI command for the object.
Whether the operation changes a definition object or creates an asynchronous run.
Whether a successful response requires you to save an object ID, run ID, or request ID.
Which status or result interface to query next, and what result establishes business completion.
Whether deletion, cancellation, retry, or resubmission can leave external side effects.
Do not infer that an undocumented UI feature is a stable public interface from web requests, internal paths, or similarly named commands.