Temporal Adds Standalone Nexus Operations

This is a meaningful shift from workflow orchestration toward reusable durable services: teams can expose capabilities once and let many applications or agents consume them. The catch is that the feature remains experimental, so production adoption should wait for API stabilization.

• –Reuses the same Nexus contracts, handlers, and workers as Workflow-driven operations, reducing duplicate integrations.
• –Operation IDs let disconnected clients start work, reconnect later, and retrieve results reliably.
• –At-least-once execution means handlers must be designed for idempotency.
• –Multi-step orchestration still belongs in Workflows; Standalone Nexus Operations fit discrete service calls.
• –Pre-release limitations include incomplete operator features and unsupported high-availability multi-region namespaces.