Update body-text links from operate/ to new-IA paths

Replace 283 body-text markdown links across 128 files that reference
/operate/ paths with their new information architecture equivalents.
This prepares for the operate/ section removal by ensuring all
cross-references already point to the correct destinations.

Mapping summary:
- /operate/reference/components/* → /reference/components/*
- /operate/reference/services/* → /reference/services/*
- /operate/reference/viam-server/ → /reference/viam-server/
- /operate/modules/write-a-*/ → /build-modules/write-a-*/
- /operate/modules/configure-modules/ → /hardware/configure-hardware/
- /operate/install/setup/ → /set-up-a-machine/overview/
- /operate/control/* → /build-apps/overview/ or /organization/access/
- /operate/hello-world/* → /try/
- /operate/reference/architecture/* → /hardware/multi-machine/overview/
- /operate/reference/services/frame-system/ → /motion-planning/frame-system/overview/

Also fixes 10 pre-existing "Component or service" UI label violations
(should be "Configuration block") in touched files.

Does not modify files within docs/operate/ (those are deleted separately).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: shannonbradshaw

docs/build-modules/dependencies.md

@@ -247,4 +247,4 @@ Then resolve it the same way as any other dependency.
 - [Write a Driver Module](/build-modules/write-a-driver-module/) -- full walkthrough including dependency handling in context.
 - [Write a Logic Module](/build-modules/write-a-logic-module/) -- build a module that coordinates multiple resources.
 - [Access platform APIs](/build-modules/platform-apis/) -- access fleet management, data, and ML training APIs from within a module.
-- For full examples, see the [Desk Safari tutorial](/operate/hello-world/tutorial-desk-safari/) or [complex module examples on GitHub](https://github.com/viamrobotics/viam-python-sdk/tree/main/examples/complex_module/src).
+- For full examples, see the [Desk Safari tutorial](/try/) or [complex module examples on GitHub](https://github.com/viamrobotics/viam-python-sdk/tree/main/examples/complex_module/src).

docs/build-modules/module-reference.md

@@ -300,7 +300,7 @@ func (c *component) someFunction(ctx context.Context, a int) {
 {{< /tabs >}}
 
 To see debug-level logs, run `viam-server` with the `-debug` flag or
-[configure debug logging](/operate/reference/viam-server/#logging) for your
+[configure debug logging](/reference/viam-server/#logging) for your
 machine or individual resource.
 
 ## Common gotchas
@@ -405,7 +405,7 @@ The full schema is available at `https://dl.viam.dev/module.schema.json`.
 
 ### Applications
 
-If your module provides a [Viam application](/operate/control/viam-applications/),
+If your module provides a [Viam application](/build-apps/overview/),
 define it in the `applications` array in `meta.json`.
 
 Each application object has the following properties:

docs/build-modules/write-a-cpp-module.md

@@ -22,9 +22,9 @@ If no [existing modules](/hardware/configure-hardware/) support your specific us
 Follow the instructions below to learn how to write a new module using your preferred language and its corresponding [Viam SDK](/reference/sdks/), and then deploy it to your machines.
 
 {{< alert title="Note: viam-micro-server modules" color="note" >}}
-[`viam-micro-server`](/operate/reference/viam-micro-server/) works differently from the RDK (and `viam-server`), so creating modular resources for it is different from the process described on this page.
+[`viam-micro-server`](/reference/viam-micro-server/) works differently from the RDK (and `viam-server`), so creating modular resources for it is different from the process described on this page.
 Refer to the [Micro-RDK Module Template on GitHub](https://github.com/viamrobotics/micro-rdk/tree/main/templates/module) for information on how to create custom resources for your `viam-micro-server` machine.
-You will need to [recompile and flash your ESP32 yourself](/operate/install/setup/) instead of using Viam's prebuilt binary and installer.
+You will need to [recompile and flash your ESP32 yourself](/set-up-a-machine/overview/) instead of using Viam's prebuilt binary and installer.
 {{< /alert >}}
 
 {{% alert title="Tip" color="tip" %}}
@@ -61,16 +61,16 @@ For example, the [sensor API](/reference/apis/components/sensor/) has a `GetRead
 If instead of just getting readings, you actually have an encoder and need to be able to reset the zero position, use the [encoder API](/reference/apis/components/encoder/) so you can define functionality behind the `GetPosition` and `ResetPosition` methods.
 
 In addition to the list of methods, another reason to choose one API over another is how certain APIs fit into the Viam ecosystem.
-For example, though you could technically implement a GPS as a sensor with just the `GetReadings` method, if you implement it as a movement sensor then you have access to methods like `GetCompassHeading` which allow you to use your GPS module with the [navigation service](/operate/reference/services/navigation/).
+For example, though you could technically implement a GPS as a sensor with just the `GetReadings` method, if you implement it as a movement sensor then you have access to methods like `GetCompassHeading` which allow you to use your GPS module with the [navigation service](/reference/services/navigation/).
 For this reason, it's generally best to choose the API that most closely matches your hardware or software.
 {{< /expand >}}
 
 {{% alert title=Note color="note" %}}
 If you want to write a module to add support to a new type of component or service that is relatively unique, consider using the generic API for your resource type to build your own API:
 
-- If you are working with a component that doesn't fit into any of the existing component APIs, you can use the [generic component](/operate/reference/components/generic/) to build your own component API.
-- If you are designing a service that doesn't fit into any of the existing service APIs, you can use the [generic service](/operate/reference/components/generic/) to build your own service API.
-- It is also possible to [define an entirely new API](/operate/reference/create-subtype/), but this is even more advanced than using `generic`.
+- If you are working with a component that doesn't fit into any of the existing component APIs, you can use the [generic component](/reference/components/generic/) to build your own component API.
+- If you are designing a service that doesn't fit into any of the existing service APIs, you can use the [generic service](/reference/components/generic/) to build your own service API.
+- It is also possible to [define an entirely new API](/build-modules/advanced-patterns/), but this is even more advanced than using `generic`.
 
 Most module use cases, however, benefit from implementing an existing API instead of `generic`.
 {{% /alert %}}
@@ -81,7 +81,7 @@ Each existing component or service API has a unique identifier in the form of a
 You will use this {{< glossary_tooltip term_id="api-namespace-triplet" text="API namespace triplet" >}} when creating your new model, to indicate which API it uses.
 
 The API namespace triplet is the same for all built-in and modular models that implement a given API.
-For example, every model of motor built into Viam, as well as every custom model of motor provided by a module, all use the same API namespace triplet `rdk:component:motor` to indicate that they implement the [motor API](/operate/reference/components/motor/#api).
+For example, every model of motor built into Viam, as well as every custom model of motor provided by a module, all use the same API namespace triplet `rdk:component:motor` to indicate that they implement the [motor API](/reference/components/motor/#api).
 
 The three pieces of the API namespace triplet are as follows:
 
@@ -168,7 +168,7 @@ Browse additional example modules by language:
 | ------ | ---------- | ----------- |
 | [berryimu](https://app.viam.com/module/viam-labs/berryimu) | [viam-labs/berry-imu](https://github.com/viam-labs/berry-imu) | Extends the built-in [movement sensor API](/reference/apis/components/movement-sensor/) to support using the BerryIMU v3 accelerometer, gyroscope and magnetometer using an I2C connection on ARM64 systems. |
 | [oak](https://app.viam.com/module/viam/oak) | [viam-modules/viam-camera-oak](https://github.com/viam-modules/viam-camera-oak) | Extends the built-in [camera API](/reference/apis/components/camera/) to support OAK cameras. |
-| [odrive](https://app.viam.com/module/viam/odrive) | [viamrobotics/odrive](https://github.com/viamrobotics/odrive) | Extends the built-in [motor API](/operate/reference/components/motor/#api) to support the ODrive motor. This module provides two models, one for a `canbus`-connected ODrive motor, and one for a `serial`-connected ODrive motor. |
+| [odrive](https://app.viam.com/module/viam/odrive) | [viamrobotics/odrive](https://github.com/viamrobotics/odrive) | Extends the built-in [motor API](/reference/components/motor/#api) to support the ODrive motor. This module provides two models, one for a `canbus`-connected ODrive motor, and one for a `serial`-connected ODrive motor. |
 | [yahboom](https://app.viam.com/module/rand/yahboom) | [viamlabs/yahboom](https://github.com/viam-labs/yahboom) | Extends the built-in [arm API](/reference/apis/components/arm/) and [gripper API](/reference/apis/components/gripper/) to support the Yahboom Dofbot robotic arm. |
 
 For more Python module examples:
@@ -199,7 +199,7 @@ For more Go module examples:
 | Module | Repository | Description |
 | ------ | ---------- | ----------- |
 | [csi-cam](https://app.viam.com/module/viam/csi-cam) | [viamrobotics/csi-camera](https://github.com/viamrobotics/csi-camera/) | Extends the built-in [camera API](/reference/apis/components/camera/) to support the Intel CSI camera. |
-<!-- | [module-example-cpp](https://app.viam.com/module/viam/module-example-cpp) | [viamrobotics/module-example-cpp](https://github.com/viamrobotics/module-example-cpp) | Extends the built-in [sensor API](/operate/reference/components/sensor/#api) to report wifi statistics. | -->
+<!-- | [module-example-cpp](https://app.viam.com/module/viam/module-example-cpp) | [viamrobotics/module-example-cpp](https://github.com/viamrobotics/module-example-cpp) | Extends the built-in [sensor API](/reference/components/sensor/#api) to report wifi statistics. | -->
 
 {{% /tab %}}
 {{% /tabs %}}
@@ -220,7 +220,7 @@ If your module references {{< glossary_tooltip term_id="pin-number" text="pin nu
 
 First, inspect the built-in class provided by the resource API that you are extending.
 
-For example, if you wanted to add support for a new [base component](/operate/reference/components/base/) to Viam (the component that represents the central physical platform of your machine, to which all other components are connected), you would start by looking at the built-in `Base` component class, which is defined in the [Viam Python SDK](https://github.com/viamrobotics/viam-python-sdk) in the following file:
+For example, if you wanted to add support for a new [base component](/reference/components/base/) to Viam (the component that represents the central physical platform of your machine, to which all other components are connected), you would start by looking at the built-in `Base` component class, which is defined in the [Viam Python SDK](https://github.com/viamrobotics/viam-python-sdk) in the following file:
 
 <!-- prettier-ignore -->
 | Resource Model File | Description |
@@ -435,7 +435,7 @@ For more information on the base component API methods used in this example, see
 
 First, inspect the built-in package provided by the resource API that you are extending.
 
-For example, if you wanted to add support for a new [base component](/operate/reference/components/base/) to Viam (the component that represents the central physical platform of your machine, to which all other components are connected), you would start by looking at the built-in `base` component package, which is defined in the [Viam Go SDK](https://github.com/viamrobotics/rdk/) in the following file:
+For example, if you wanted to add support for a new [base component](/reference/components/base/) to Viam (the component that represents the central physical platform of your machine, to which all other components are connected), you would start by looking at the built-in `base` component package, which is defined in the [Viam Go SDK](https://github.com/viamrobotics/rdk/) in the following file:
 
 <!-- prettier-ignore -->
 | Resource Model File | Description |
@@ -680,7 +680,7 @@ For more information on the base component API methods used in this example, see
 First, inspect the built-in class provided by the resource API that you are extending.
 In the C++ SDK, all built-in classes are abstract classes.
 
-For example, if you wanted to add support for a new [base component](/operate/reference/components/base/) to Viam (the component that represents the central physical platform of your machine, to which all other components are connected), you would start by looking at the built-in `Base` component class, which is defined in the [Viam C++ SDK](https://cpp.viam.dev/) in the following files:
+For example, if you wanted to add support for a new [base component](/reference/components/base/) to Viam (the component that represents the central physical platform of your machine, to which all other components are connected), you would start by looking at the built-in `Base` component class, which is defined in the [Viam C++ SDK](https://cpp.viam.dev/) in the following files:
 
 <!-- prettier-ignore -->
 | Resource Model File | Description |
@@ -1122,7 +1122,7 @@ Resource-level logs are recommended instead of global logs for modular resources
 Resource-level error logs appear in the **Error logs** section of each resource's configuration card in the app.
 
 {{% alert title="Note" color="note" %}}
-In order to see resource-level debug logs when using your modular resource, you'll either need to run `viam-server` with the `-debug` option or [configure your machine or individual resource to display debug logs](/operate/reference/viam-server/#logging).
+In order to see resource-level debug logs when using your modular resource, you'll either need to run `viam-server` with the `-debug` option or [configure your machine or individual resource to display debug logs](/reference/viam-server/#logging).
 {{% /alert %}}
 
 {{< expand "Click to see global logging" >}}
@@ -1638,7 +1638,7 @@ Add the module to your machine's config, then add the component or service it im
 
    {{<imgproc src="/how-tos/sensor-module-config.png" resize="600x" style="width: 300px" alt="Configuring a local component after the local module is configured" class="shadow" >}}
 
-1. Select the type of modular resource provided by your module, such as a [camera](/operate/reference/components/camera/), from the dropdown menu.
+1. Select the type of modular resource provided by your module, such as a [camera](/reference/components/camera/), from the dropdown menu.
 
 1. Enter a name for this instance of your modular resource.
    This name must be different from the module name.

docs/hardware/multi-machine/overview.md

@@ -94,4 +94,4 @@ If the client goes silent (network loss, crashed process), `viam-server` automat
 A rover will not keep driving, an arm will not keep moving, and a gripper will not keep closing when the commanding process vanishes.
 This applies equally to local and remote resources.
 
-For the lower-level details of how machines communicate, see [Machine-to-machine communication](/operate/reference/architecture/machine-to-machine-comms/).
+For the lower-level details of how machines communicate, see [Machine-to-machine communication](/hardware/multi-machine/overview/).

docs/monitor/overview.md

@@ -71,5 +71,5 @@ This section covers tools for monitoring, operating, and debugging machines that
 | Configure components and services              | [Configure hardware](/hardware/)        |
 | Capture and sync data from sensors             | [Manage data](/data/)                   |
 | Train and deploy ML models                     | [Train ML models](/train/)              |
-| Build a custom web or mobile app with the SDKs | [Build apps](/operate/control/web-app/) |
+| Build a custom web or mobile app with the SDKs | [Build apps](/build-apps/overview/) |
 | Manage fleet deployment and provisioning       | [Fleet deployment](/fleet/)             |

docs/monitor/teleop-workspaces.md

@@ -20,7 +20,7 @@ For an explanation of widget types and capabilities, see [Data dashboards overvi
 
 Your machine needs at least one camera, movement sensor, sensor, base, arm, board, gantry, gripper, motor, or servo.
 
-See [configure a machine](/operate/modules/configure-modules/) for more information.
+See [configure a machine](/hardware/configure-hardware/) for more information.
 
 {{% /expand%}}
 

docs/monitor/troubleshoot.md

@@ -158,10 +158,10 @@ If you are not seeing helpful logs, enable debug logging.
 ]
 ```
 
-For more on log configuration, see [Logging](/operate/reference/viam-server/#logging).
+For more on log configuration, see [Logging](/reference/viam-server/#logging).
 
 By default, `viam-server` deduplicates log messages that repeat within a one-minute window.
-To disable this, see [Disable log deduplication](/operate/reference/viam-server/).
+To disable this, see [Disable log deduplication](/reference/viam-server/).
 
 #### Access logs from the command line
 
@@ -220,7 +220,7 @@ This exposes endpoints for CPU profiling, memory allocation analysis, goroutine
 
 The `/debug/graph` endpoint renders an SVG visualization of the machine's resource dependency graph.
 
-For details, see [Debug Endpoints](/operate/reference/viam-server/debug-endpoints/).
+For details, see [Debug Endpoints](/reference/viam-server/).
 
 ## Diagnostics
 

docs/navigation/how-to/drive-a-base.md

@@ -35,7 +35,7 @@ service instead. See
   configuring...**, wait for the motor's status badge to read **Ready**
   before attempting Quick move.
 - An SDK client connected to your machine. See
-  [Create a web app](/operate/control/web-app/) or the language-specific
+  [Create a web app](/build-apps/overview/) or the language-specific
   quickstart.
 
 ## Direct motion commands

docs/reference/apis/_index.md

@@ -23,7 +23,7 @@ date: "2024-10-01"
 
 Every Viam {{< glossary_tooltip term_id="resource" text="resource" >}} exposes an [application programming interface (API)](https://en.wikipedia.org/wiki/API) described through [protocol buffers](https://developers.google.com/protocol-buffers).
 
-The API methods provided by the SDKs for each of these resource APIs wrap gRPC client requests to the machine when you execute your program, providing you a convenient interface for accessing information about and controlling the {{< glossary_tooltip term_id="resource" text="resources" >}} you have [configured](/operate/modules/configure-modules/) on your machine.
+The API methods provided by the SDKs for each of these resource APIs wrap gRPC client requests to the machine when you execute your program, providing you a convenient interface for accessing information about and controlling the {{< glossary_tooltip term_id="resource" text="resources" >}} you have [configured](/hardware/configure-hardware/) on your machine.
 
 ## Platform APIs
 

docs/reference/apis/billing-client.md

@@ -25,7 +25,7 @@ The billing API supports the following methods:
 To use the billing client API, you need to instantiate a `ViamClient` and then instantiate a `BillingClient`.
 
 You need an API key and API key ID with [Org owner permissions](/organization/rbac/#organization-settings-and-roles) to use the billing client API.
-To get an API key (and corresponding ID), use the [web UI](/operate/control/api-keys/#add-an-api-key)
+To get an API key (and corresponding ID), use the [web UI](/organization/access/#add-an-api-key)
 to the [Viam CLI](/cli/).
 
 {{< tabs >}}
@@ -128,7 +128,7 @@ const billingClient = viamClient.billingClient;
 {{% /tab %}}
 {{% tab name="From within a Module" %}}
 
-See [Use platform APIs from within a module](/operate/modules/advanced/platform-apis/).
+See [Use platform APIs from within a module](/build-modules/platform-apis/).
 
 {{% /tab %}}
 {{< /tabs >}}