[codex] consolidate SDK entrypoint and canonical link usage

.codex/REDIRECTS_AND_DEPRECATIONS.md

@@ -4,6 +4,10 @@ Use this file whenever a docs route, page label, or public surface name changes.
 
 ## General rules
 
+### Canonical links first
+Always update docs content to link directly to the canonical destination route.
+Treat redirects and stubs as compatibility layers for legacy/external traffic, not as an internal linking strategy.
+
 ### Prefer stable routes
 If a misleading page can be corrected by:
 - changing the H1,
@@ -22,7 +26,7 @@ Change a route only if the current route is:
 ## When a route changes
 
 1. Add an entry to the ledger below.
-2. Update all internal links.
+2. Update all internal links to the new canonical route.
 3. Update `docs.json`.
 4. Add a redirect or a short deprecation stub if the platform supports it.
 5. Mention the route change in the task summary.
@@ -50,19 +54,19 @@ Example:
 
 | Status | Old route | New route | Reason | Notes |
 |---|---|---|---|---|
-| changed | `/sdk-reference/oracle-ai-sdk` | `/sdk-reference/oracle-adk` | ADK slug for Personal Agent ADK (`@ixo/assistant-sdk`) | Redirect configured in `docs.json` |
+| changed | `/sdk-reference/oracle-ai-sdk` | `/sdk-reference/oracle-adk` | ADK slug for Personal Agent ADK (`@ixo/assistant-sdk`) | Internal links use canonical route; compatibility redirect retained in `docs.json` |
 | accepted (stable route) | `/mcp/model-context-protocol` | keep existing route | H1 and body fixes are sufficient without slug migration | Prefer stable route first |
 | changed | `/articles/ixo-protocol` | `/protocols/ixo-protocol` | Protocol concept docs consolidated under canonical `protocols/` directory | Internal links and nav updated |
 | changed | `/articles/ixo-blockchain` | `/protocols/ixo-protocol` | Duplicate IXO Protocol concept page removed in favor of one canonical protocol page | Internal links and nav updated |
 | deprecated (stub) | `/api-docs/*` | canonical `api-reference/*` routes | Legacy API docs tree replaced with transitional stubs | Stubs point to closest canonical API or guide route by topic |
-| changed | `/spatial-web-stack/*` | `/ixo-stack/*` | Canonical stack route namespace normalized to IXO naming | Directory renamed, internal links updated, and explicit redirects added in `docs.json` |
-| changed | `/ixo-stack/sdks/oracle-agent-sdk`, `/spatial-web-stack/sdks/oracle-agent-sdk` | `/sdk-reference/oracles-client-sdk` | Old route represented the client-facing oracle interface, now mapped to the canonical Oracles Client SDK page | Redirects updated in `docs.json`; ADK remains canonical at `/sdk-reference/agentic-oracles-adk` for service-side scaffolding/deployment |
+| changed | `/spatial-web-stack/*` | `/ixo-stack/*` | Canonical stack route namespace normalized to IXO naming | Directory renamed, internal links updated to canonical routes, compatibility redirects retained in `docs.json` |
+| changed | `/ixo-stack/sdks/oracle-agent-sdk`, `/spatial-web-stack/sdks/oracle-agent-sdk` | `/sdk-reference/oracles-client-sdk` | Old route represented the client-facing oracle interface, now mapped to the canonical Oracles Client SDK page | Internal links use canonical route; ADK remains canonical at `/sdk-reference/agentic-oracles-adk` for service-side scaffolding/deployment |
 | changed | `/ixo-stack/sdks/ixo-matrix-sdk`, `/spatial-web-stack/sdks/ixo-matrix-sdk` | `/sdk-reference/matrix-client-sdk` | Legacy SDK stub replaced with direct redirect to Matrix Client SDK reference | Internal MDX links updated |
 | changed | `/ixo-stack/sdks/intro-sdks`, `/spatial-web-stack/sdks/intro-sdks` | `/sdk-reference/index` | Legacy IXO Stack SDK intro stub replaced with direct redirect to SDK reference index | Internal MDX links updated |
 | changed | `/ixo-stack/sdks/signx-sdk`, `/spatial-web-stack/sdks/signx-sdk` | `/sdk-reference/signx-sdk` | Legacy stub redirected to SignX SDK reference | Stubs retained as pointers |
 | changed | `/ixo-stack/sdks/jambo-wallet-sdk`, `/spatial-web-stack/sdks/jambo-wallet-sdk` | `/sdk-reference/jambo-wallet-sdk` | Legacy stub redirected to JAMBO PWA SDK reference | Stubs retained as pointers |
 | changed | `/ixo-stack/sdks/ixo-multiclient-sdk`, `/spatial-web-stack/sdks/ixo-multiclient-sdk` | `/sdk-reference/multiclient-sdk` | Legacy stub redirected to MultiClient SDK reference | Stubs retained as pointers |
-| changed | `/guides/dev/spatial-web-sdks` | `/guides/dev/ixo-stack-sdks` | Developer SDK hub slug aligned to IXO Stack naming | Redirect configured in `docs.json`; file renamed to `guides/dev/ixo-stack-sdks.mdx` |
+| changed | `/guides/dev/spatial-web-sdks` | `/guides/dev/ixo-stack-sdks` | Developer SDK hub slug aligned to IXO Stack naming | Internal links use canonical route; compatibility redirect retained in `docs.json` |
 | added | n/a | `/reference/networks-and-endpoints` | Establish canonical home for endpoint and network literals | New reference route |
 | added | n/a | `/reference/authentication-matrix` | Establish canonical home for auth headers and surface-level auth ownership | New reference route |
 | added | n/a | `/reference/product-and-sdk-map` | Establish canonical home for product-to-SDK naming and route mapping | New reference route |

guides/dev/ixo-domains.mdx

@@ -4,14 +4,14 @@
 ---
 
 <Tip>
   Entity Domains provide a standardized way to register and manage digital twins of real-world entities on the IXO blockchain, with built-in support for decentralized identity, verifiable credentials, and relationship management.
 </Tip>
 
 ## Overview
 
 <AccordionGroup>
   <Accordion title="Decentralized Identity Management" icon="fingerprint">
     Create and manage decentralized identifiers (DIDs) for entities, enabling sovereign control and cryptographic verification of identity claims.
   </Accordion>
 
   <Accordion title="Verifiable Ownership and Control" icon="key">
@@ -118,7 +118,7 @@
 
   2. **Submit Registration**
      - Sign domain creation transaction
      - Broadcast to blockchain
      - Wait for confirmation
      - Verify registration
 
@@ -137,7 +137,7 @@
 
   async function createEntityDomain(
     creator: string,
     entityType: string
   ) {
     const msg = {
       typeUrl: "/ixo.entity.v1beta1.MsgCreateEntity",
@@ -210,13 +210,13 @@
   <Accordion title="Add Service" icon="plus">
     ```typescript
     async function addDomainService(
       entityId: string,
       service: Service
     ) {
       const msg = {
         typeUrl: "/ixo.entity.v1beta1.MsgAddEntityService",
         value: {
           entityId,
           service
         }
       };
@@ -304,8 +304,8 @@
     Entity module API documentation
   </Card>
 
-  <Card title="SDK Guide" icon="code" href="/guides/dev/ixo-stack-sdks">
-    Client SDK implementation guide
+  <Card title="SDK and kit overview" icon="code" href="/sdk-reference/index">
+    Canonical SDK guide and routing map
   </Card>
 
   <Card title="Examples" icon="lightbulb" href="/guides/dev/examples">

guides/dev/ixo-stack-sdks.mdx

@@ -1,167 +1,63 @@
 ---
 title: 'IXO Stack SDKs'
 icon: 'code'
-description: 'Build advanced applications on the IXO Stack using the comprehensive suite of IXO development tools'
+description: 'Developer entry point to SDK workflows, with the canonical SDK and kit overview in the SDK reference'
 ---
 
-<Tip>
-The IXO Stack SDKs help you integrate the IXO Protocol, IXO Matrix, and related services from TypeScript. Deployable **gateway tools** extend IXO to offline and mobile channels (including USSD).
-</Tip>
+<Info>
+The canonical SDK and kit overview is now maintained at [IXO and Qi Developer Kits](/sdk-reference/index).  
+Use this page as a developer workflow entry point.
+</Info>
 
-## Available SDKs
+## Start here
 
 <CardGroup>
-
-<Card title="IXO MultiClient SDK" icon="network-wired" href="/sdk-reference/multiclient-sdk">
-  Connect with IXO and Cosmos networks for interchain operations
-</Card>
-
-<Card title="Matrix Client SDK" icon="database" href="/sdk-reference/matrix-client-sdk">
-  Build secure data rooms and encrypted communication channels
-</Card>
-
-<Card title="Agentic Oracles ADK" icon="sparkles" href="/sdk-reference/agentic-oracles-adk">
-  Build oracle and agent services with `@ixo/oracle-agent-sdk`
-</Card>
-
-<Card title="Personal Agent ADK" icon="brain" href="/sdk-reference/oracle-adk">
-  Integrate conversational AI with `@ixo/assistant-sdk`
-</Card>
-
-<Card title="JAMBO PWA SDK" icon="wallet" href="/sdk-reference/jambo-wallet-sdk">
-  Manage digital assets and credentials in JAMBO PWA experiences
-</Card>
-
-<Card title="SignX SDK" icon="signature" href="/sdk-reference/signx-sdk">
-  Enable secure mobile-to-web authentication and transaction signing
-</Card>
-
+  <Card title="SDK and kit overview (canonical)" icon="book" href="/sdk-reference/index">
+    Choose the right SDK or kit, including Oracles Client SDK, Agentic Oracles ADK, and JAMBO PWA SDK.
+  </Card>
+  <Card title="Developer workflows" icon="diagram-project" href="/guides/dev/workflows">
+    Follow end-to-end implementation patterns for entities, claims, evaluation, and integrations.
+  </Card>
+  <Card title="Identity and credentials" icon="id-card" href="/guides/dev/identity-and-credentials">
+    Understand DID, claim, and credential relationships used across SDK workflows.
+  </Card>
+  <Card title="API reference" icon="code" href="/api-reference/index">
+    Review service and infrastructure APIs used by SDK-based implementations.
+  </Card>
 </CardGroup>
 
-## Gateway tools
-
-Fork or deploy these tools to extend IXO services to additional channels and environments.
-
-<CardGroup>
-
-<Card title="IXO USSD gateway" icon="tower-cell" href="/articles/ixo-ussd">
-  Give any GSM mobile phone access to IXO services — no smartphone or data plan required
-</Card>
-
+## SDK quick links
+
+<CardGroup cols={2}>
+  <Card title="IXO MultiClient SDK" icon="network-wired" href="/sdk-reference/multiclient-sdk">
+    Interchain protocol interactions and entity workflows.
+  </Card>
+  <Card title="IXO Matrix Client SDK" icon="database" href="/sdk-reference/matrix-client-sdk">
+    Encrypted rooms, messaging, and shared state integrations.
+  </Card>
+  <Card title="Oracles Client SDK" icon="comments" href="/sdk-reference/oracles-client-sdk">
+    Frontend agent-client interfaces for deployed oracles.
+  </Card>
+  <Card title="Agentic Oracles ADK" icon="sparkles" href="/sdk-reference/agentic-oracles-adk">
+    Scaffold, implement, and deploy oracle services.
+  </Card>
+  <Card title="Personal Agent ADK" icon="brain" href="/sdk-reference/oracle-adk">
+    Personal conversational assistant integrations.
+  </Card>
+  <Card title="JAMBO PWA SDK" icon="wallet" href="/sdk-reference/jambo-wallet-sdk">
+    JAMBO PWA integrations with wallet-enabled workflows.
+  </Card>
+  <Card title="IXO SignX SDK" icon="signature" href="/sdk-reference/signx-sdk">
+    User authentication and transaction signing flows.
+  </Card>
+  <Card title="IXO USSD gateway" icon="tower-cell" href="/articles/ixo-ussd">
+    Extend IXO services to offline and feature-phone channels.
+  </Card>
 </CardGroup>
 
-## Installation
-
-```bash
-# Install core SDKs
-npm install @ixo/impactxclient-sdk @ixo/matrixclient-sdk
-npm install @ixo/assistant-sdk @ixo/jambo-wallet-sdk
-```
-
-## Basic Setup
-
-<CodeGroup>
-
-```typescript IXO MultiClient SDK
-import { createClient } from "@ixo/impactxclient-sdk";
-
-// Initialize client
-const chain = await createClient({
-  rpcEndpoint: RPC_ENDPOINT,
-  chainId: "ixo-5"
-});
-
-// Create digital twin
-const twin = await chain.entity.create({
-  type: "DigitalTwin",
-  controller: "did:ixo:org/123"
-});
-```
-
-```typescript IXO Matrix Client SDK
-import { createMatrixClient } from "@ixo/matrixclient-sdk";
-
-// Initialize Matrix client
-const matrix = await createMatrixClient({
-  baseUrl: MATRIX_ENDPOINT,
-  accessToken: USER_TOKEN
-});
-
-// Create secure data room
-const room = await matrix.createRoom({
-  name: "Secure Data Room",
-  encryption: true,
-  visibility: "private"
-});
-```
-
-```typescript Assistant
-import { createAssistant } from "@ixo/assistant-sdk";
-
-// Initialize assistant
-const assistant = await createAssistant({
-  type: "VerificationAgent",
-  capabilities: ["verification", "analytics"]
-});
-
-// Process verification request
-const result = await assistant.verify({
-  data: inputData,
-  context: verificationContext
-});
-```
-
-```typescript JAMBO PWA
-import { createWallet } from "@ixo/jambo-wallet-sdk";
-
-// Initialize wallet
-const wallet = await createWallet({
-  storageType: "secure",
-  network: "mainnet"
-});
-
-// Manage credentials
-const credential = await wallet.createCredential({
-  type: "VerifiableCredential",
-  issuer: "did:ixo:issuer/123"
-});
-```
-
-</CodeGroup>
-
-## End-to-end workflows
-
-For runnable patterns (client setup, entities, claims, evaluation) aligned with [Implementation examples](/guides/dev/examples), read [Developer workflows](/guides/dev/workflows). For DID, claim, and VC relationships, read [Identity and credentials](/guides/dev/identity-and-credentials).
-
-## Key Features
-
-### MultiClient SDK
-- Interchain transactions and queries
-- Digital twin management
-- Entity state management
-- Blockchain service management
-
-### Matrix Client SDK
-- End-to-end encrypted data rooms
-- Secure messaging and file storage
-- Access control management
-- Real-time data streaming
-
-### Personal Agent ADK
-- AI-powered agent services
-- Analytics processing
-- Evidence collection
-- Proof generation
-
-### JAMBO PWA SDK
-- Credential management
-- Digital asset operations
-- Secure key storage
-- Transaction signing
-
 ## Next steps
 
-- [Developer workflows](/guides/dev/workflows) — SDK patterns for domains, claims, and verification
-- [SDK reference](/sdk-reference) — full reference for each SDK
-- [API reference](/api-reference) — IXO service APIs
-- [Developer overview](/guides/dev/overview) — entry points and task-oriented guides
+- [IXO and Qi Developer Kits](/sdk-reference/index) — canonical SDK and kit overview
+- [Developer workflows](/guides/dev/workflows) — implementation patterns for domains, claims, and verification
+- [API reference](/api-reference/index) — IXO service APIs
+- [Developer overview](/guides/dev/overview) — task-oriented entry points

guides/dev/overview.mdx

@@ -1,20 +1,20 @@
 ---
 title: 'Developer Overview'
 icon: 'code'
 description: 'Build AI-operable workflows on IXO: SDKs, APIs, and paths from shared state to Qi cooperation and agents.'
 ---
 
 <Tip>
   **Build lens:** you are wiring **real-world workflows** where agents and services act on **verifiable** entities, claims, and evidence—not only on generic LLM context. This hub lists SDKs, APIs, and guides for that stack.
 </Tip>
 
 **IXO** anchors what is true on-chain and in linked services (domains, claims, credentials). **Qi** (the **Qi Intelligent Cooperating System**) is where people and agents **cooperate** on that truth—via Matrix, oracle and agent services, and automation. Most projects still implement **state first** (protocol, claims, indexing), then add **cooperation** (Matrix, Agentic Oracles, SDKs). Read [Introduction](/introduction), [What you can build](/guides/what-you-can-build), [Core concepts](/core-concepts), and [Qi: cooperation on verified workflows](/articles/qi-intelligent-cooperating-system) for the full model.
 
 ## Choose your starting point
 
 <CardGroup>
-  <Card title="SDKs and tools" icon="toolbox" href="/guides/dev/ixo-stack-sdks">
+  <Card title="SDKs and tools" icon="toolbox" href="/sdk-reference/index">
     Browse TypeScript SDKs and deployable gateway tools, including the IXO MultiClient SDK, IXO Matrix Client SDK, and IXO USSD gateway
   </Card>
   <Card title="API reference" icon="server" href="/api-reference">
     REST, RPC, GraphQL, and service API interfaces for IXO Protocol and application services
@@ -23,7 +23,7 @@
     Set up credentials, session keys, and authorization to connect to IXO services
   </Card>
   <Card title="Networks and endpoints" icon="network-wired" href="/reference/networks-and-endpoints">
     Mainnet and testnet connection details, chain IDs, and base URLs
   </Card>
   <Card title="Authentication matrix" icon="table" href="/reference/authentication-matrix">
     Which headers and credentials apply to each API surface
@@ -63,7 +63,7 @@
 
 <AccordionGroup>
   <Accordion title="IXO Protocol" icon="cube">
     The IXO Protocol is a Cosmos SDK blockchain for coordinating, financing, and verifying real-world impacts. Core modules cover entity management, claims, tokens, bonds, and smart accounts. [Read the protocol overview](/articles/ixo-protocol).
   </Accordion>
   <Accordion title="Domains and digital twins" icon="diagram-project">
     Domains are on-chain representations of real-world entities — organisations, projects, assets, and devices. Each domain has a Decentralized Identifier (DID), controllers, services, and a linked IXO Matrix data room. [Learn about digital twins](/guides/digital-twins).
@@ -72,12 +72,12 @@
     IXO Matrix is the encrypted data and communication layer. Applications use it for secure data rooms, evidence storage, and messaging linked to on-chain state. [Read the Matrix overview](/articles/ixo-matrix).
   </Accordion>
   <Accordion title="Agentic Oracles" icon="brain">
     Agentic Oracles are AI-powered services that process impact claims, validate evidence, and write verifiable attestations to the IXO Protocol. [Learn about Agentic Oracles](/articles/ixo-oracles).
   </Accordion>
 </AccordionGroup>
 
 ## Developer resources
 
 - [IXO open-source repositories](https://github.com/ixofoundation) — source code for SDKs, gateway tools, and reference implementations
 - [Developer community](https://ixofoundation.slack.com/archives/C04UERAUHQT) — questions, discussions, and support
 - [Product and SDK map](/reference/product-and-sdk-map) — canonical list of products, SDKs, and their package identifiers

guides/dev/workflows.mdx

@@ -7,7 +7,7 @@
 These workflows follow the same patterns as [Implementation examples](/guides/dev/examples). Method names and payloads can change between SDK releases—confirm types and exports in [`@ixo/impactxclient-sdk`](https://www.npmjs.com/package/@ixo/impactxclient-sdk) and the [ixo-multiclient-sdk repository](https://github.com/ixofoundation/ixo-multiclient-sdk) before shipping.
 
 <Info>
   There is **no single blessed CLI** for every IXO operation in this docs set. Prefer the SDK, Cosmos-compatible wallets, or deployment-specific CLIs your operator documents. For HTTP examples (for example Emerging Platform domains), see [Domain registration](/guides/domain-registration).
 </Info>
 
 ## Prerequisites
@@ -27,9 +27,9 @@
 });
 ```
 
 **Signing:** production flows attach a signer compatible with the chain (for example Keplr, Cosmostation, or a custodial signer). The examples below assume `client` can submit transactions for your account.
 
 **Errors:** RPC misconfiguration often surfaces as connection timeouts or JSON-RPC errors. Retry with a different node if the operator allows; confirm TLS and `chainId` match the network.
 
 ## 2. Register or manage a domain (digital twin)
 
@@ -124,14 +124,14 @@
 ## Error handling
 
 - **HTTP service calls:** use [Error handling](/api-reference/errors) for status codes; add retry/backoff for `429` and transient `5xx`.
 - **GraphQL (Blocksync):** partial errors may appear in a top-level `errors` array while `data` is non-null—always check both; unauthenticated introspection may be disabled on some deployments.
 - **DID resolution:** if resolution fails, confirm the DID is registered on the expected network and that you query the correct registry or indexer endpoint.
 
 ## Next steps
 
 <CardGroup cols={2}>
-  <Card title="IXO Stack SDKs" icon="toolbox" href="/guides/dev/ixo-stack-sdks">
-    All SDK entry points and gateway tools
+  <Card title="SDK and kit overview" icon="toolbox" href="/sdk-reference/index">
+    Canonical SDK and kit overview with route selection guidance
   </Card>
   <Card title="MultiClient SDK" icon="server" href="/sdk-reference/multiclient-sdk">
     Module-level features on-chain

platforms/Emerging/domain-registration.mdx

@@ -31,7 +31,7 @@
 ### Core Properties
 <AccordionGroup>
   <Accordion title="Digital Identifier (DID)">
     - Follows Interchain Identifier methodology
     - Self-sovereign and cryptographically secure
     - Globally unique and resolvable
     - Permanent and immutable
@@ -39,7 +39,7 @@
 
   <Accordion title="Entity Metadata">
     - Verification credentials
     - Relayer node assignment
     - Validity period
     - Operational status
     - Verification state
@@ -80,8 +80,8 @@
         "version": "1.0"
       },
       "credentials": [],
       "relayerNode": "did:ixo:entity:relayer123",
       "validFrom": "2024-01-01T00:00:00Z",
       "status": "active"
     }
     ```
@@ -90,7 +90,7 @@
   <Accordion title="Required Fields">
     - Protocol class reference
     - Entity type specification
     - Relayer node assignment
     - Validity period (optional)
     - Initial status
   </Accordion>
@@ -112,14 +112,14 @@
 
 ## Governance and DAO workflow
 
 **What “proposal to DAO” means here** — A domain change (new entity, protocol class, relayer, or material metadata) is packaged as a **proposal**: voters decide whether the network should treat that domain as verified and active for the intended program.
 
 1. **Draft** — Complete the entity document and evidence your template requires (controllers, relayer, protocol DID, optional credentials). Use [Digital identifiers](/platforms/Emerging/digital-identifiers) and [Data integrity](/platforms/Emerging/data-integrity) as guardrails.
 2. **Submit** — Send the proposal through the governance surface your deployment uses (for example on-chain gov module parameters, a **Studio**/**Portal** workflow, or operator-specific APIs—confirm with your program operator). The exact transaction or HTTP call is deployment-specific; align with [Emerging API](/platforms/Emerging/emerging-api) and [Networks and endpoints](/reference/networks-and-endpoints).
 3. **Vote** — Token holders, committee members, or allow-listed voters evaluate risk, relayer assignment, and protocol fit. Outcomes are typically **pass**, **fail**, or **abstain** with a quorum threshold.
 4. **Execute** — On approval, state transitions run (verification flags, registry pointers, service enablement). On rejection, the domain stays inactive or reverts to the previous version depending on module rules.
 
 For how DAOs fit the wider IXO story, see [DAOs](/articles/daos). For who typically drafts vs votes vs funds programs, see [Your role](/your-role).
 
 ## Who does what (roles)
 
@@ -135,7 +135,7 @@
   </Accordion>
 
   <Accordion title="Capital and outcome-linked funding" icon="hand-holding-dollar">
     - **Typical role:** Funder
     - **Doc entry:** [Your role — Funder](/your-role)
   </Accordion>
 
@@ -151,7 +151,7 @@
 
 - Controllers and keys match who will operate the entity on-chain.
 - Protocol / class DID is the one your template expects.
 - Relayer or service endpoints are reachable from your environment.
 - Evidence and metadata align with [Digital certification](/platforms/Emerging/digital-certification) where applicable.
 
 **After vote**
@@ -210,7 +210,7 @@
   <Card title="API Reference" icon="code" href="/platforms/Emerging/emerging-api">
     Domain registration endpoints
   </Card>
-  <Card title="SDK Guide" icon="box" href="/guides/dev/ixo-stack-sdks">
+  <Card title="SDK Guide" icon="box" href="/sdk-reference/index">
     Client libraries and tools
   </Card>
   <Card title="Example Projects" icon="lightbulb" href="/guides/dev/examples">

platforms/Emerging/energy-systems.mdx

@@ -6,7 +6,7 @@
 
 This page documents **Emerging Household Energy** solution modeling. It explains how the solution maps households, devices, and verification data using platform primitives. Use this guide when implementing household-energy workflows rather than generic platform capabilities.
 
 ## Why Cognitive Digital Twins (CDTs)?
 
 <CardGroup>
   <Card title="Real-Time Intelligence" icon="brain">
@@ -83,7 +83,7 @@
 
 <AccordionGroup>
   <Accordion title="Entity Configuration">
     - Unique identifiers (DIDs)
     - Controller assignments
     - Service endpoints
     - Resource links
@@ -131,14 +131,14 @@
 
 ### CDT System Integrations
 <CardGroup>
-  <Card title="IoT Connectivity" icon="wifi" href="/guides/dev/ixo-stack-sdks">
+  <Card title="IoT Connectivity" icon="wifi" href="/sdk-reference/index">
     Device data streaming and control
   </Card>
   <Card title="Registry Services" icon="grid" href="/platforms/Emerging/registry">
     Asset and claim registration
   </Card>
   <Card title="Payment Systems" icon="credit-card" href="/platforms/Emerging/digital-vouchers">
     Digital payments and tokenization
   </Card>
   <Card title="Impact Markets" icon="globe" href="/platforms/Emerging/digital-certification">
     Carbon credit trading & ITMO purchases
@@ -151,7 +151,7 @@
 2. [Create digital twins](/guides/digital-twins) for your devices and entities
 3. [Configure monitoring](/platforms/Emerging/household-monitoring) and verification rules
 4. [Implement dMRV](/platforms/Emerging/emerging-dmrv) for impact tracking
 5. [Enable payments](/platforms/Emerging/digital-vouchers) and tokenization
 
 ## Developer Resources
 
@@ -159,7 +159,7 @@
   <Card title="API Documentation" icon="code" href="/platforms/Emerging/emerging-api">
     Complete API reference
   </Card>
-  <Card title="SDKs" icon="box" href="/guides/dev/ixo-stack-sdks">
+  <Card title="SDKs" icon="box" href="/sdk-reference/index">
     Development tools and libraries
   </Card>
   <Card title="AI Companion" icon="sparkles" href="/guides/users/ai-companion">

platforms/Emerging/intro-emerging.mdx

@@ -47,7 +47,7 @@
     - Decentralised data storage
     - Verifiable credentials
     - Digital claims processing
     - Carbon credit tokenization
     - Digital payment processing
   </Accordion>
 
@@ -96,7 +96,7 @@
 
 ### Device Integration
 <CardGroup>
-  <Card title="Client SDK" icon="box" href="/guides/dev/ixo-stack-sdks">
+  <Card title="Client SDK" icon="box" href="/sdk-reference/index">
     Libraries for device connectivity and data streaming
   </Card>
   <Card title="Cognitive Digital Twins" icon="brain" href="/platforms/Emerging/energy-systems">

reference/product-and-sdk-map.mdx

@@ -37,7 +37,7 @@
   <Accordion title="Personal Agent ADK" icon="brain">
     - **Package identifier:** `@ixo/assistant-sdk`
     - **Primary docs route:** [oracle-adk](/sdk-reference/oracle-adk)
-    - **Notes:** Public docs name for `@ixo/assistant-sdk`; `/sdk-reference/oracle-ai-sdk` redirects here.
+    - **Notes:** Public docs name for `@ixo/assistant-sdk`; use this canonical route in all docs links.
   </Accordion>
 
   <Accordion title="IXO SignX SDK" icon="key">
@@ -87,7 +87,7 @@
   </Accordion>
 
   <Accordion title="IXO Blocksync" icon="compass">
     **Primary docs routes:** [IXO Blocksync](/articles/ixo-blocksync), [Blocksync GraphQL API](/api-reference/blocksync-graphql-api)
   </Accordion>
 
   <Accordion title="Agentic Oracles" icon="brain">