📖 [Docs]: Agentic development has one canonical home

src/docs/Capabilities/agentic-development/design.md

@@ -325,6 +325,6 @@ Because Copilot code review reads the head branch, a pull request that changes `
 - [Agent Interaction](agent-interaction.md) — how agents and humans coordinate through platform artifacts.
 - [Advisory Agents](advisory-agents.md) — agents that produce advice rather than commits.
 - [Conformance](conformance.md) — the checklist a repository is measured against.
-- [Agentic Development](../../Ways-of-Working/Agentic-Development.md) — the way-of-working standard this framework implements.
+- [Agentic Development framework](index.md) — the framework this design delivers.
 - [Documentation Model](../../Ways-of-Working/Documentation-Model.md) — why spec and design are split.
 - [README-Driven Context](../../Ways-of-Working/Readme-Driven-Context.md) — why local repository context remains the front door.

src/docs/Capabilities/agentic-development/spec.md

@@ -22,7 +22,7 @@ This framework rests on the [Principles](../../Ways-of-Working/Principles/index.
 
 - **[Documentation lives close to the thing it documents](../../Ways-of-Working/Principles/Engineering-Practices.md#documentation-lives-close-to-the-thing-it-documents).** Organization-wide ways of working live in the organization `docs` repository; repository-specific nuance lives in the repository.
 - **[Everything as Code](../../Ways-of-Working/Principles/Engineering-Practices.md#everything-as-code).** Standards and memory are plain files in git. Changes are reviewed, diffed, and reverted like code.
-- **[Written once, referenced everywhere](../../Ways-of-Working/Agentic-Development.md#principles).** Agent instructions point to canonical docs and memory rather than duplicating them.
+- **[Written once, referenced everywhere](../../Ways-of-Working/Principles/Software-Design.md#dry-with-judgment).** Agent instructions point to canonical docs and memory rather than duplicating them.
 - **[AI-first development](../../Ways-of-Working/Principles/AI-First-Development.md).** Humans create durable context; agents consume that context and leave useful improvements behind.
 
 ## Scope
@@ -64,7 +64,7 @@ Applies to any organization that wants a shared project knowledge base and memor
 - **Stage resolution from work.** Agents MUST infer the current stage from the prompt and current artifacts. Explicit task language MAY shortcut to the matching stage, but the shortcut MUST resolve to the canonical documentation.
 - **One process source.** Skills, commands, named agents, and tool-specific instruction files MUST NOT redefine Workflow stages. A client convenience MAY link to a stage procedure and add only runtime mechanics.
 - **Segmentation before loading.** An agent MUST segment work by host, organization, repository, path, and task before loading project standards or memory. The repository router MUST supply the coordinates that make this possible by naming its host and organization. The instruction to segment belongs to the user-global bootstrap, which runs before any repository file is read; a per-repository file MUST NOT restate it.
-- **Client routes.** A runtime that cannot read `AGENTS.md` under its own filename MUST be given a route file — `.claude/CLAUDE.md`, `.github/copilot-instructions.md`, or the equivalent path for that runtime. A route file MUST contain only a pointer to `AGENTS.md` plus, at most, genuinely runtime-specific configuration that cannot be expressed as documentation. It MUST NOT restate standards, describe workflow behavior, or repeat the reading order. Duplication is a property of content rather than of filenames: a route holds nothing that can drift, so the number of route files is unconstrained while their contents are strictly limited. [Agentic Development](../../Ways-of-Working/Agentic-Development.md#which-agent-files-a-repository-carries) names the exact set an MSX repository carries; an adopting organization MAY carry a different set for the runtimes it uses.
+- **Client routes.** A runtime that cannot read `AGENTS.md` under its own filename MUST be given a route file — `.claude/CLAUDE.md`, `.github/copilot-instructions.md`, or the equivalent path for that runtime. A route file MUST contain only a pointer to `AGENTS.md` plus, at most, genuinely runtime-specific configuration that cannot be expressed as documentation. It MUST NOT restate standards, describe workflow behavior, or repeat the reading order. Duplication is a property of content rather than of filenames: a route holds nothing that can drift, so the number of route files is unconstrained while their contents are strictly limited. [Client behavior](design.md#client-behavior) names the exact set an MSX repository carries; an adopting organization MAY carry a different set for the runtimes it uses.
 - **Reading order and authority order are distinct.** An agent MUST read nearest context first, in the order the repository router defines. Precedence on conflict MUST run the opposite way: repository-local files MAY add nuance and narrow exceptions but MUST NOT override an organization or inherited ecosystem standard unless that standard permits a local exception, and memory MUST NOT override documentation.
 - **Deterministic context resolution.** Agents MUST resolve context in layers: system and client policy, user preferences, the repository router, the context-repository freshness gate, repository context, path-scoped repository rules, organization docs, any inherited ecosystem docs, organization memory, then current task context.
 - **Local-first availability.** The docs and memory repositories SHOULD be available locally in a predictable workspace so agents can read them without relying on search or web access.
@@ -123,6 +123,6 @@ This is the order in which context is **read**, nearest first. It is not the ord
 - [Agent Interaction](agent-interaction.md) — issues, labels, and pull requests as the coordination substrate.
 - [Advisory Agents](advisory-agents.md) — the pattern for automation that advises without deciding.
 - [Conformance](conformance.md) — how a repository is measured against this spec.
-- [Agentic Development](../../Ways-of-Working/Agentic-Development.md) — the existing way-of-working standard this framework operationalizes.
+- [Agentic Development](index.md) — the framework this specification defines.
 - [Documentation Model](../../Ways-of-Working/Documentation-Model.md) — how specs and designs are written and kept evergreen.
 - [Open Knowledge Format](../../Dictionary/index.md#open-knowledge-format) — the Markdown and frontmatter model used for knowledge pages.

src/docs/Coding-Standards/Natural-Language.md

@@ -208,5 +208,5 @@ Do not include secrets, private personal notes, or speculation.
 
 - [Documentation](Documentation.md) — where documentation lives and what it explains.
 - [Markdown](Markdown.md) — Markdown syntax and linted formatting rules.
-- [Agentic Development](../Ways-of-Working/Agentic-Development.md) — how agents consume the same docs as humans.
+- [Agentic Development](../Capabilities/agentic-development/index.md) — how agents consume the same docs as humans.
 - [README-Driven Context](../Ways-of-Working/Readme-Driven-Context.md) — why the README is the repository front door.

src/docs/Dictionary/index.md

@@ -15,7 +15,7 @@ The 2018 book by Nicole Forsgren, Jez Humble, and Gene Kim presenting the resear
 
 ### Agent
 
-An AI participant that reads the same documentation as a human and acts on the platform — opening issues, proposing pull requests, and reviewing changes. See [Agentic Development](../Ways-of-Working/Agentic-Development.md).
+An AI participant that reads the same documentation as a human and acts on the platform — opening issues, proposing pull requests, and reviewing changes. See [Agentic Development](../Capabilities/agentic-development/index.md).
 
 ### Anthropic API