flippedcoder · Sep 14, 2026 · Aug 20, 2026 · Aug 20, 2026 · Aug 24, 2026 · Aug 24, 2026
@@ -123,7 +123,7 @@ need its own service accounts, API keys, dashboards, or rate limits. If that is
 [Namespace best practices](/best-practices/managing-namespace) before committing to Namespace-per-tenant isolation.
 
 <RelatedReadContainer>
-  <RelatedReadItem path="/evaluate/development-production-features/multi-tenancy#namespace-isolation" text="Namespace Isolation in Temporal Cloud" archetype="cloud-guide" />
+  <RelatedReadItem path="/cloud/security#namespace-isolation" text="Namespace Isolation in Temporal Cloud" archetype="cloud-guide" />
 </RelatedReadContainer>
 
 ### Pattern comparison
@@ -336,7 +336,7 @@ TenantId = 'customer-123' AND ExecutionStatus = 'Running'
 ## Related resources
 
 <RelatedReadContainer>
-  <RelatedReadItem path="/evaluate/development-production-features/multi-tenancy" text="Multi-tenancy Overview" archetype="feature-guide" />
+  <RelatedReadItem path="/namespaces" text="Namespaces" archetype="feature-guide" />
   <RelatedReadItem path="/cloud/limits" text="Temporal Cloud Limits" archetype="cloud-guide" />
   <RelatedReadItem path="/visibility" text="Visibility and Search Attributes" archetype="feature-guide" />
 </RelatedReadContainer>
@@ -228,7 +228,7 @@ Intentionally break or degrade downstream dependencies used by Activities:
 
 - [Workflow Versioning Strategies - Developer Corner](https://community.temporal.io/t/workflow-versioning-strategies/6911)
 - [Worker Versioning](/production-deployment/worker-deployments/worker-versioning)
-- [Replay Testing](/evaluate/development-production-features/testing-suite)
+- Replay Testing: see SDK documentation for details
 
 **What to test**
 
@@ -251,7 +251,7 @@ Intentionally break or degrade downstream dependencies used by Activities:
 
 - [Workflow Versioning Strategies - Developer Corner](https://community.temporal.io/t/workflow-versioning-strategies/6911)
 - [Worker Versioning](/production-deployment/worker-deployments/worker-versioning)
-- [Replay Testing](/evaluate/development-production-features/testing-suite)
+- Replay Testing: see SDK documentation for details
 
 **What to test**
 

@@ -92,7 +92,7 @@ extension using the following command:
 
 :::tip Support, stability, and dependency info
 
-The Temporal Cloud extension is in [Public Preview](/evaluate/development-production-features/release-stages#public-preview).
+The Temporal Cloud extension is in [Public Preview](/evaluate/product-release-stages#public-preview).
 APIs and configuration may change before the stable release.
 
 :::

@@ -274,7 +274,7 @@ key and mTLS authentication on the same Namespace, please contact
 :::info
 
 Using **both** API key and mTLS authentication on the **same** Namespace is in
-[pre-release](/evaluate/development-production-features/release-stages) and doesn't support
+[pre-release](/evaluate/product-release-stages) and doesn't support
 [High Availability features](/cloud/high-availability) or authenticating with an API Key to a Namespace Endpoint.
 
 :::

@@ -130,7 +130,7 @@ These are often major concerns for financial services, e-commerce, gaming, globa
 
 In selected regions, you can add a replica to a Namespace in the same region.
 Temporal operates a "cell architecture" and will replicate the Namespace across multiple cells in that region.
-This feature is currently in [Public Preview](/evaluate/development-production-features/release-stages) in selected regions.
+This feature is currently in [Public Preview](/evaluate/product-release-stages) in selected regions.
 
 Failovers between cells are always managed automatically by Temporal. Unlike Multi-region and Multi-cloud Replication, you cannot disable automatic failovers and you cannot trigger a manual failover for a Same-region Replication Namespace. See [Failovers](/cloud/high-availability/failovers) for details.
 

@@ -215,8 +215,8 @@ Each descriptor includes a `release_stage` field that reports the metric's lifec
 
 | Value | Description |
 | ----- | ----- |
-| `public-preview` | The metric is in [Public Preview](/evaluate/development-production-features/release-stages#public-preview) |
-| `general-availability` | The metric is in [General Availability](/evaluate/development-production-features/release-stages#general-availability) |
+| `public-preview` | The metric is in [Public Preview](/evaluate/product-release-stages#public-preview) |
+| `general-availability` | The metric is in [General Availability](/evaluate/product-release-stages#general-availability) |
 | `deprecated` | The metric is deprecated |
 
 #### Query parameters

@@ -26,5 +26,5 @@ Temporal Cloud builds on the [core Nexus experience](/nexus) with:
 
 ## Learn more
 
-- [Evaluate Nexus](/evaluate/nexus) | [Keynote and demo](https://youtu.be/qqc2vsv1mrU?feature=shared&t=2082)
+- [Evaluate Nexus](/evaluate/features/nexus) | [Keynote and demo](https://youtu.be/qqc2vsv1mrU?feature=shared&t=2082)
 - [How Nexus works](/nexus) | [Deep dive talk](https://www.youtube.com/watch?v=izR9dQ_eIe4&t=934s)
@@ -17,7 +17,7 @@ import { StandaloneActivityDemo, ReleaseNoteHeader, SdkGuideLinks } from '@site/
   languages={["Go", "Python", "Java", ".NET", "TypeScript", "Ruby"]}
   guidePath="activities/standalone-activities"
 >
-  Available in [Temporal Cloud](/standalone-activity#temporal-cloud-support) and in the [Temporal CLI](/standalone-activity#temporal-cli-support) v1.7.0 or higher with Temporal Server v1.31.0 or higher. Java SDK support is in [Pre-release](/evaluate/development-production-features/release-stages#pre-release).
+  Available in [Temporal Cloud](/standalone-activity#temporal-cloud-support) and in the [Temporal CLI](/standalone-activity#temporal-cli-support) v1.7.0 or higher with Temporal Server v1.31.0 or higher. Java SDK support is in [Pre-release](/evaluate/product-release-stages#pre-release).
 </ReleaseNoteHeader>
 
 Standalone Activities let you run a single Activity straight from your application without

@@ -13,7 +13,7 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import { CaptionedImage } from '@site/src/components';
 
-Use [Temporal Nexus](/evaluate/nexus) to connect Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations.
+Use [Temporal Nexus](/evaluate/features/nexus) to connect Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations.
 
 :::tip
 
@@ -665,6 +665,6 @@ For **synchronous Nexus Operations** the following are reported in the caller's
 
 ## Learn more
 
-- Read the high-level description of the [Temporal Nexus feature](/evaluate/nexus) and watch the [Nexus keynote and demo](https://youtu.be/qqc2vsv1mrU?feature=shared&t=2082).
+- Read the high-level description of the [Temporal Nexus feature](/evaluate/features/nexus) and watch the [Nexus keynote and demo](https://youtu.be/qqc2vsv1mrU?feature=shared&t=2082).
 - Learn how Nexus works in the [Nexus deep dive talk](https://www.youtube.com/watch?v=izR9dQ_eIe4) and [Encyclopedia](/nexus).
 - Deploy Nexus Endpoints in production with [Temporal Cloud](/cloud/nexus).
@@ -13,10 +13,10 @@ hide_table_of_contents: true
 
 import { SetupSteps, SetupStep, CodeSnippet } from '@site/src/components';
 
-[Temporal Nexus](/evaluate/nexus) connects Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. Build a Nexus Service that wraps an existing Temporal Workflow, then invoke it from a caller Workflow.
+[Temporal Nexus](/evaluate/features/nexus) connects Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. Build a Nexus Service that wraps an existing Temporal Workflow, then invoke it from a caller Workflow.
 
 :::info
-To evaluate whether Nexus fits your use case, see the [evaluation guide](/evaluate/nexus). To learn how Nexus works, see [Temporal Nexus](/nexus).
+To evaluate whether Nexus fits your use case, see the [evaluation guide](/evaluate/features/nexus). To learn how Nexus works, see [Temporal Nexus](/nexus).
 :::
 
 **Prerequisites:** Complete the [.NET SDK Quickstart](/develop/dotnet/set-up-your-local-dotnet) first.

@@ -15,7 +15,7 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import { CaptionedImage } from '@site/src/components';
 
-Use [Temporal Nexus](/evaluate/nexus) to connect Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations.
+Use [Temporal Nexus](/evaluate/features/nexus) to connect Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations.
 
 :::tip
 
@@ -812,6 +812,6 @@ For **synchronous Nexus Operations** the following are reported in the caller's
 
 ## Learn more
 
-- Read the high-level description of the [Temporal Nexus feature](/evaluate/nexus) and watch the [Nexus keynote and demo](https://youtu.be/qqc2vsv1mrU?feature=shared&t=2082).
+- Read the high-level description of the [Temporal Nexus feature](/evaluate/features/nexus) and watch the [Nexus keynote and demo](https://youtu.be/qqc2vsv1mrU?feature=shared&t=2082).
 - Learn how Nexus works in the [Nexus deep dive talk](https://www.youtube.com/watch?v=izR9dQ_eIe4) and [Encyclopedia](/nexus).
 - Deploy Nexus Endpoints in production with [Temporal Cloud](/cloud/nexus).
@@ -15,10 +15,10 @@ import { SetupSteps, SetupStep, CodeSnippet } from '@site/src/components';
 
 # Nexus Go Quickstart
 
-[Temporal Nexus](/evaluate/nexus) connects Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. Build a Nexus Service that wraps an existing Temporal Workflow, then invoke it from a caller Workflow.
+[Temporal Nexus](/evaluate/features/nexus) connects Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. Build a Nexus Service that wraps an existing Temporal Workflow, then invoke it from a caller Workflow.
 
 :::info
-To evaluate whether Nexus fits your use case, see the [evaluation guide](/evaluate/nexus). To learn how Nexus works, see [Temporal Nexus](/nexus).
+To evaluate whether Nexus fits your use case, see the [evaluation guide](/evaluate/features/nexus). To learn how Nexus works, see [Temporal Nexus](/nexus).
 :::
 
 **Prerequisites:** Complete the [Go SDK Quickstart](/develop/go/set-up-your-local-go) first.

@@ -30,7 +30,7 @@ For a complete list of metrics capable of being emitted, see the [SDK metrics re
 
 To instrument Temporal applications with OpenTelemetry, use the
 [OpenTelemetry v2 integration](/develop/go/integrations/opentelemetry-v2)
-([Pre-release](/evaluate/development-production-features/release-stages#pre-release)).
+([Pre-release](/evaluate/product-release-stages#pre-release)).
 It propagates OpenTelemetry context across Temporal boundaries and
 is replay-safe when instrumenting Workflows.
 
@@ -152,7 +152,7 @@ Tracing allows you to view the call graph of a Workflow along with its Activitie
 
 To instrument Temporal applications with OpenTelemetry, use the
 [OpenTelemetry v2 integration](/develop/go/integrations/opentelemetry-v2)
-([Pre-release](/evaluate/development-production-features/release-stages#pre-release)).
+([Pre-release](/evaluate/product-release-stages#pre-release)).
 It propagates OpenTelemetry context across Temporal boundaries and
 is replay-safe when instrumenting Workflows.
 

@@ -14,7 +14,7 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import { CaptionedImage } from '@site/src/components';
 
-Use [Temporal Nexus](/evaluate/nexus) to connect Temporal Applications within and across Namespaces using a Nexus
+Use [Temporal Nexus](/evaluate/features/nexus) to connect Temporal Applications within and across Namespaces using a Nexus
 Endpoint, a Nexus Service contract, and Nexus Operations.
 
 :::tip
@@ -871,7 +871,7 @@ For **synchronous Nexus Operations** the following are reported in the caller's
 
 ## Learn more
 
-- Read the high-level description of the [Temporal Nexus feature](/evaluate/nexus) and watch the
+- Read the high-level description of the [Temporal Nexus feature](/evaluate/features/nexus) and watch the
   [Nexus keynote and demo](https://youtu.be/qqc2vsv1mrU?feature=shared&t=2082).
 - Learn how Nexus works in the [Nexus deep dive talk](https://www.youtube.com/watch?v=izR9dQ_eIe4) and
   [Encyclopedia](/nexus).

@@ -13,10 +13,10 @@ hide_table_of_contents: true
 
 import { SetupSteps, SetupStep, CodeSnippet } from '@site/src/components';
 
-[Temporal Nexus](/evaluate/nexus) connects Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. Build a Nexus Service that wraps an existing Temporal Workflow, then invoke it from a caller Workflow.
+[Temporal Nexus](/evaluate/features/nexus) connects Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. Build a Nexus Service that wraps an existing Temporal Workflow, then invoke it from a caller Workflow.
 
 :::info
-To evaluate whether Nexus fits your use case, see the [evaluation guide](/evaluate/nexus). To learn how Nexus works, see [Temporal Nexus](/nexus).
+To evaluate whether Nexus fits your use case, see the [evaluation guide](/evaluate/features/nexus). To learn how Nexus works, see [Temporal Nexus](/nexus).
 :::
 
 **Prerequisites:** Complete the [Java SDK Quickstart](/develop/java/set-up-your-local-java) first.

@@ -191,7 +191,7 @@ requirements:
   meaning it produces the same commands and results when replayed. For example, don't call system time APIs, generate
   random values, or perform direct network and file I/O from Workflow-context code; move that work to Activities or
   Nexus Operations.
-- See [observability](/evaluate/development-production-features/observability) to avoid duplicating observation side
+- See [observability](/evaluate/features/observability) to avoid duplicating observation side
   effects when Workflows replay.
 - Put other side effects inside of Activities or [Local Activities](/local-activity). This helps your Workflow handle
   being restarted, resumed, or executed in a different process from where it originally began without losing correctness
@@ -208,7 +208,7 @@ queues and Workers.
 Users use Workflows for:
 
 - Orchestration and decision-making
-- Interactivity via [message-passing](/evaluate/development-production-features/workflow-message-passing)
+- Interactivity via [message-passing](/evaluate/features/workflow-message-passing)
 - Tracing and observability
 
 #### Making changes to your library

@@ -14,7 +14,7 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import { CaptionedImage } from '@site/src/components';
 
-Use [Temporal Nexus](/evaluate/nexus) to connect Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations.
+Use [Temporal Nexus](/evaluate/features/nexus) to connect Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations.
 
 :::tip
 
@@ -509,6 +509,6 @@ For **synchronous Nexus Operations** the following are reported in the caller's
 
 ## Learn more
 
-- Read the high-level description of the [Temporal Nexus feature](/evaluate/nexus) and watch the [Nexus keynote and demo](https://youtu.be/qqc2vsv1mrU?feature=shared&t=2082).
+- Read the high-level description of the [Temporal Nexus feature](/evaluate/features/nexus) and watch the [Nexus keynote and demo](https://youtu.be/qqc2vsv1mrU?feature=shared&t=2082).
 - Learn how Nexus works in the [Nexus deep dive talk](https://www.youtube.com/watch?v=izR9dQ_eIe4) and [Encyclopedia](/nexus).
 - Deploy Nexus Endpoints in production with [Temporal Cloud](/cloud/nexus).
@@ -15,10 +15,10 @@ import { SetupSteps, SetupStep, CodeSnippet } from '@site/src/components';
 
 # Nexus Python Quickstart
 
-[Temporal Nexus](/evaluate/nexus) connects Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. Build a Nexus Service that wraps an existing Temporal Workflow, then invoke it from a caller Workflow.
+[Temporal Nexus](/evaluate/features/nexus) connects Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. Build a Nexus Service that wraps an existing Temporal Workflow, then invoke it from a caller Workflow.
 
 :::info
-To evaluate whether Nexus fits your use case, see the [evaluation guide](/evaluate/nexus). To learn how Nexus works, see [Temporal Nexus](/nexus).
+To evaluate whether Nexus fits your use case, see the [evaluation guide](/evaluate/features/nexus). To learn how Nexus works, see [Temporal Nexus](/nexus).
 :::
 
 **Prerequisites:** Complete the [Python SDK Quickstart](/develop/python/set-up-your-local-python) first.

@@ -305,7 +305,7 @@ To send an Update to a Workflow Execution, you can:
 
 :::tip Stability
 
-In [Public Preview](/evaluate/development-production-features/release-stages#public-preview) in Temporal Cloud.
+In [Public Preview](/evaluate/product-release-stages#public-preview) in Temporal Cloud.
 
 Minimum Temporal Server version [Temporal Server version 1.26](https://github.com/temporalio/temporal/releases/tag/v1.26.2)
 

@@ -13,7 +13,7 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import { CaptionedImage } from "@site/src/components";
 
-Use [Temporal Nexus](/evaluate/nexus) to connect Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations.
+Use [Temporal Nexus](/evaluate/features/nexus) to connect Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations.
 
 :::tip
 
@@ -539,6 +539,6 @@ For custom interceptor logic beyond tracing (for example, logging, authorization
 
 ## Learn more
 
-- Read the high-level description of the [Temporal Nexus feature](/evaluate/nexus) and watch the [Nexus keynote and demo](https://youtu.be/qqc2vsv1mrU?feature=shared&t=2082).
+- Read the high-level description of the [Temporal Nexus feature](/evaluate/features/nexus) and watch the [Nexus keynote and demo](https://youtu.be/qqc2vsv1mrU?feature=shared&t=2082).
 - Learn how Nexus works in the [Nexus deep dive talk](https://www.youtube.com/watch?v=izR9dQ_eIe4) and [Encyclopedia](/nexus).
 - Deploy Nexus Endpoints in production with [Temporal Cloud](/cloud/nexus).
@@ -13,10 +13,10 @@ hide_table_of_contents: true
 
 import { SetupSteps, SetupStep, CodeSnippet } from '@site/src/components';
 
-[Temporal Nexus](/evaluate/nexus) connects Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. Build a Nexus Service that wraps an existing Temporal Workflow, then invoke it from a caller Workflow.
+[Temporal Nexus](/evaluate/features/nexus) connects Temporal Applications within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations. Build a Nexus Service that wraps an existing Temporal Workflow, then invoke it from a caller Workflow.
 
 :::info
-To evaluate whether Nexus fits your use case, see the [evaluation guide](/evaluate/nexus). To learn how Nexus works, see [Temporal Nexus](/nexus).
+To evaluate whether Nexus fits your use case, see the [evaluation guide](/evaluate/features/nexus). To learn how Nexus works, see [Temporal Nexus](/nexus).
 :::
 
 **Prerequisites:** Complete the [TypeScript SDK Quickstart](/develop/typescript/set-up-your-local-typescript) first.

@@ -27,7 +27,7 @@ API. Activity Operations don't apply to [Local Activities](/local-activity) or
 
 :::note Public Preview
 
-Activity Operations are in [Public Preview](/evaluate/development-production-features/release-stages#public-preview).
+Activity Operations are in [Public Preview](/evaluate/product-release-stages#public-preview).
 Pause, Unpause, and Reset are available in Server v1.28.0+. Self-hosted UI requires v2.47.0+.
 
 Activity Operations aren't available as SDK client methods. They're operational controls designed for the CLI, UI, and