<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. SPDX-License-Identifier: Apache-2.0 -->

Refactor NemoClaw Documentation

Refactor a bounded documentation section without changing product meaning. Improve findability while preserving every useful fact, one canonical owner per topic, and every supported published route.

Prerequisites

• Work from the NemoClaw repository root.
• Follow the shared Documentation Writing and Review contract before planning or editing.
• Read the full target pages, their navigation entries in docs/index.yml, their redirects in fern/docs.yml, and their inbound links before editing.

Choose the Deliverable

• Treat cross-section ownership, navigation hierarchy, and published URL changes as maintainer-owned decisions.
• For a request to plan, audit, or propose a structure, stop after the information architecture, ownership map, and URL migration plan.
• For a request to refactor, implement the plan, validate it, and report the completed migration.
• Keep the work bounded to the named docs section. Report adjacent debt instead of folding unrelated cleanup into the refactor.
• Allow a cross-section move when canonical ownership requires it, but identify the move explicitly in the plan and migration report.
• Surface a choice only when it changes topic ownership, public URLs, supported variants, or user workflow. Use established repository conventions for routine details.

Load the phase that applies

• For an audit or structure plan, use Structure and Ownership.
• Before changing published routes or moving content, use Migration. A plan that changes URLs must include its route and anchor mapping.
• For an implemented refactor, use Validation and Review. Repair findings and rerun affected checks before reporting completion.