ansible · jself-sudoku · Jan 19, 2026 · Jan 20, 2026 · Jan 20, 2026 · Jan 20, 2026
diff --git a/downstream/archive/archived-modules/platform/con-gw-managing-access.adoc b/downstream/archive/archived-modules/platform/con-gw-managing-access.adoc
@@ -2,7 +2,7 @@
 
 [id="gw-managing-access"]
 
-= Managing access with role based access control
+= Configure and administer role based access control (RBAC)
 
 Role-based access control (RBAC) restricts user access based on their role within an organization. The roles in RBAC refer to the levels of access that users have to the network.
 

diff --git a/downstream/archive/archived-modules/platform/proc-controller-edit-credential.adoc b/downstream/archive/archived-modules/platform/proc-controller-edit-credential.adoc
@@ -2,7 +2,7 @@
 
 [id="controller-getting-started-edit-credential"]
 
-= Editing a credential
+= Edit a credential
 
 As part of the initial setup, you can leave the default *Demo Credential* as it is, and you can edit it later.
 

diff --git a/downstream/assemblies/aap-hardening/assembly-hardening-aap.adoc b/downstream/assemblies/aap-hardening/assembly-hardening-aap.adoc
@@ -3,7 +3,7 @@
 ifdef::context[:parent-context: {context}]
 
 [id="hardening-aap"]
-= Hardening {PlatformNameShort}
+= Harden the platform security posture
 
 :context: hardening-aap
 

diff --git a/downstream/assemblies/aap-hardening/assembly-managed-node-configuration.adoc b/downstream/assemblies/aap-hardening/assembly-managed-node-configuration.adoc
@@ -2,7 +2,7 @@
 
 [id="assembly-managed-node-configuration"]
 
-= Managed Node Configuration
+= Improve the security of nodes managed by {PlatformNameShort}
 
 [role="_abstract"]
 {PlatformNameShort} is an agentless technology that relies on making a remote connection to the devices it manages, called managed nodes, to run automation tasks. 

diff --git a/downstream/assemblies/aap-migration/assembly-migration-artifact.adoc b/downstream/assemblies/aap-migration/assembly-migration-artifact.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
 
 [id="migration-artifact"]
-= Migration artifact structure and verification
+= Contents of the migration artifact
 
 [role="_abstract"]
 The migration artifact packages all necessary data and configurations from your source environment. Verify its structure and contents to ensure a successful migration.

diff --git a/downstream/assemblies/aap-migration/assembly-source-containerized.adoc b/downstream/assemblies/aap-migration/assembly-source-containerized.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
 
 [id="source-containerized"]
-= Container-based {PlatformNameShort}
+= Prepare and export data from a container-based environment
 
 [role="_abstract"]
 Prepare and export data from your container-based {PlatformNameShort} deployment.

diff --git a/downstream/assemblies/aap-migration/assembly-source-environment.adoc b/downstream/assemblies/aap-migration/assembly-source-environment.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
 
 [id="source-environment"]
-= Source environment
+= Prepare and export data from the source environment
 
 [role="_abstract"]
 Prepare and export data from your existing {PlatformNameShort} deployment. The exported data forms a critical migration artifact, which you use to configure your new environment.

diff --git a/downstream/assemblies/aap-migration/assembly-source-rpm.adoc b/downstream/assemblies/aap-migration/assembly-source-rpm.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
 
 [id="source-rpm"]
-= RPM-based {PlatformNameShort}
+= Prepare and export data from an RPM-based environment
 
 [role="_abstract"]
 Prepare and export data from your RPM-based {PlatformNameShort} deployment.

diff --git a/downstream/assemblies/aap-migration/assembly-target-containerized.adoc b/downstream/assemblies/aap-migration/assembly-target-containerized.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
 
 [id="target-containerized"]
-= Container-based {PlatformNameShort}
+= Prepare the container-based target environment and import migration content
 
 [role="_abstract"]
 Prepare and assess your target container-based {PlatformNameShort} environment, and import and reconcile your migrated content.

diff --git a/downstream/assemblies/aap-migration/assembly-target-environment.adoc b/downstream/assemblies/aap-migration/assembly-target-environment.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
 
 [id="target-environment"]
-= Target environment
+= Prepare, configure, and validate the target environment 
 
 [role="_abstract"]
 Prepare, configure, and validate your target {PlatformNameShort} environment.

diff --git a/downstream/assemblies/aap-migration/assembly-target-managed-aap.adoc b/downstream/assemblies/aap-migration/assembly-target-managed-aap.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
 
 [id="target-managed-aap"]
-= Managed {PlatformNameShort}
+= Prepare to migrate to Managed {PlatformNameShort}
 
 [role="_abstract"]
 Prepare and migrate your source environment to a Managed {PlatformNameShort} deployment, and reconcile the target environment post-migration.

diff --git a/downstream/assemblies/aap-migration/assembly-target-ocp.adoc b/downstream/assemblies/aap-migration/assembly-target-ocp.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: ASSEMBLY
 
 [id="target-ocp"]
-= {OCPShort}
+= Prepare the {OCPShort} target environment and import migration content
 
 [role="_abstract"]
 Prepare and assess your target {OCPShort} environment, and import and reconcile your migrated content.

diff --git a/downstream/assemblies/analytics/assembly-automation-savings-planner.adoc b/downstream/assemblies/analytics/assembly-automation-savings-planner.adoc
@@ -6,7 +6,7 @@ ifdef::context[:parent-context: {context}]
 
 :context: assembly-automation-savings-planner-ctxt
 
-= About the {planner}
+= Plan, track, and analyze returns with {planner}
 
 [role="_abstract"]
 An automation savings plan gives you the ability to plan, track, and analyze the potential efficiency and cost savings of your automation initiatives. Use automation analytics to create an automation savings plan by defining a list of tasks needed to complete an automation job.

diff --git a/downstream/assemblies/analytics/assembly-evaluating-automation-return.adoc b/downstream/assemblies/analytics/assembly-evaluating-automation-return.adoc
@@ -7,7 +7,7 @@ ifdef::context[:parent-context: {context}]
 
 :context: assembly-evaluating-automation-return-ctxt
 
-= About Automation Calculator
+= Use automation calculator to determine automation savings
 
 [role="_abstract"]
 The automation calculator provides graphs, metrics and calculations that help you determine the total savings on your investment in automated processes.

diff --git a/downstream/assemblies/analytics/assembly-insights-reports.adoc b/downstream/assemblies/analytics/assembly-insights-reports.adoc
@@ -6,7 +6,7 @@ ifdef::context[:parent-context: {context}]
 
 :context: assembly-insights-reports-ctxt
 
-= Viewing your reports on {PlatformName}
+= Get a comprehensive visual overview of automation with reports
 
 [role="_abstract"]
 The reports feature on the {PlatformName} provides users with a visual overview of their automation efforts across different teams by using Ansible.

diff --git a/downstream/assemblies/analytics/assembly-using-job-explorer.adoc b/downstream/assemblies/analytics/assembly-using-job-explorer.adoc
@@ -6,7 +6,7 @@ ifdef::context[:parent-context: {context}]
 
 :context: assembly-using-job-explorer-ctxt
 
-= About the Job Explorer
+= View data about automation jobs across your organization
 
 [role="_abstract"]
 The *Job Explorer* provides a detailed view of jobs run on {ControllerName} clusters across your organizations. You can access the *Job Explorer* by selecting {MenuAAJobExplorer} from the navigation panel or using the drill-down view available across each of the application's charts.

diff --git a/...automation-dashboard/assembly-appendix-inventory-file-automation-dashboard.adoc b/...automation-dashboard/assembly-appendix-inventory-file-automation-dashboard.adoc
@@ -1,9 +1,9 @@
 :_mod-docs-content-type: ASSEMBLY
 
 [id="assembly-appendix-inventory-file-automation-dashboard"]
-= Appendix
+= Inventory file variables for {AutomationDashboardName}
 
 [role="_abstract"]
-The inventory variables required by the {AutomationDashboardName} installer are described in the following table: 
+The inventory variables required by the {AutomationDashboardName} installation program are described in the following table: 
 
 include::automation-dashboard/ref-automation-dashboard-inventory-variables.adoc[leveloffset=+1]
diff --git a/downstream/assemblies/automation-dashboard/assembly-view-key-metrics.adoc b/downstream/assemblies/automation-dashboard/assembly-view-key-metrics.adoc
@@ -6,7 +6,7 @@ ifdef::context[:parent-context: {context}]
 
 :context: assembly-view-key-metrics-ctxt
 
-= View key usage metrics with {AutomationDashboardName}
+= Install {AutomationDashboardName} to calculate savings (RHEL only)
 
 [role="_abstract"]
 

diff --git a/downstream/assemblies/builder/assembly-MCP-servers-and-EE.adoc b/downstream/assemblies/builder/assembly-MCP-servers-and-EE.adoc
@@ -10,7 +10,7 @@ An MCP eliminates the need for custom integrations by providing a universal "lan
 
 The MCP operates using a client-server architecture:
 
-[cols="a,a", options="header"]
+[cols="a,a,a", options="header"]
 |===
 | Component | Role | Description
 | MCP Host | The application environment | This is where the user interacts with the AI, such as an AI-powered IDE like VS Code or a chatbot interface.

diff --git a/downstream/assemblies/builder/assembly-populate-container-registry.adoc b/downstream/assemblies/builder/assembly-populate-container-registry.adoc
@@ -2,7 +2,7 @@
 
 [id="assembly-populate-container-registry"]
 
-= Populating your {PrivateHubName} container registry
+= Manage {ExecEnvShort}s in {PrivateHubName}
 
 [role="_abstract"]
 By default, {PrivateHubName} does not include {ExecEnvName}.

diff --git a/downstream/assemblies/builder/assembly-using-builder.adoc b/downstream/assemblies/builder/assembly-using-builder.adoc
@@ -2,7 +2,7 @@
 
 [id="assembly-using-builder"]
 
-= Using {Builder}
+= Build customized runtime environments with Ansible builder
 
 [role="_abstract"]
 {Builder} is a command line tool that automates the process of building {ExecEnvName} by using metadata defined in various Ansible Collections or created by the user.

diff --git a/downstream/assemblies/devtools/assembly-backstage-software-templates.adoc b/downstream/assemblies/devtools/assembly-backstage-software-templates.adoc
@@ -2,7 +2,7 @@ ifdef::context[:parent-context: {context}]
 :_mod-docs-content-type: ASSEMBLY
 [id="backstage-software-templates_{context}"]
 
-= Using custom actions and UI components in Backstage Software Templates
+= Use custom actions and UI components in Backstage Software Templates
 
 :context: self-service-rbac
 

diff --git a/downstream/assemblies/devtools/assembly-creating-playbook-project.adoc b/downstream/assemblies/devtools/assembly-creating-playbook-project.adoc
@@ -2,7 +2,7 @@ ifdef::context[:parent-context: {context}]
 :_mod-docs-content-type: ASSEMBLY
 [id="creating-playbook-project"]
 
-= Creating a playbook project
+= Auto-generate the structure and files for your automation project
 
 :context: creating-playbook-project
 [role="_abstract"]

diff --git a/downstream/assemblies/devtools/assembly-developer-workflow.adoc b/downstream/assemblies/devtools/assembly-developer-workflow.adoc
@@ -2,7 +2,7 @@ ifdef::context[:parent-context: {context}]
 :_mod-docs-content-type: ASSEMBLY
 [id="developer-workflow"]
 
-= Workflow for developing automation content
+= Development workflow 
 
 :context: developer-workflow
 

diff --git a/downstream/assemblies/devtools/assembly-devtools-create-roles-collection.adoc b/downstream/assemblies/devtools/assembly-devtools-create-roles-collection.adoc
@@ -9,7 +9,7 @@ ifdef::context[]
 [id="devtools-create-roles-collection_{context}"]
 endif::[]
 
-= Creating a collection for distributing roles
+= Understand collections for distributing roles
 
 :context: devtools-create-roles-collection
 

diff --git a/downstream/assemblies/devtools/assembly-devtools-develop-collections.adoc b/downstream/assemblies/devtools/assembly-devtools-develop-collections.adoc
@@ -8,7 +8,7 @@ endif::[]
 ifdef::context[]
 [id="devtools-develop-collections_{context}"]
 endif::[]
-= Developing collections
+= Package and distribute automation content with collections
 
 :context: devtools-develop-collections
 

diff --git a/downstream/assemblies/devtools/assembly-devtools-extension-set-language.adoc b/downstream/assemblies/devtools/assembly-devtools-extension-set-language.adoc
@@ -2,7 +2,7 @@ ifdef::context[:parent-context-of-assembly-devtools-install: {context}]
 :_mod-docs-content-type: ASSEMBLY
 [id="extension-set-language"]
 
-= Manually adding the Ansible language to YAML files
+= Set the lanaguge for the {VSCode} extension
 
 [role="_abstract"]
 

diff --git a/downstream/assemblies/devtools/assembly-devtools-install.adoc b/downstream/assemblies/devtools/assembly-devtools-install.adoc
@@ -2,7 +2,7 @@ ifdef::context[:parent-context-of-assembly-devtools-install: {context}]
 :_mod-docs-content-type: ASSEMBLY
 [id="installing-devtools"]
 
-= Installing {ToolsName}
+= Install {ToolsName}
 
 :context: installing-devtools
 [role="_abstract"]

diff --git a/downstream/assemblies/devtools/assembly-devtools-intro.adoc b/downstream/assemblies/devtools/assembly-devtools-intro.adoc
@@ -2,7 +2,7 @@ ifdef::context[:parent-context: {context}]
 :_mod-docs-content-type: ASSEMBLY
 [id="devtools-intro"]
 
-= {ToolsName}
+= Create, test, and deploy automation content with ansible-dev-tools
 
 :context: devtools-intro
 [role="_abstract"]

diff --git a/downstream/assemblies/devtools/assembly-mcp-vscode-ext-configure.adoc b/downstream/assemblies/devtools/assembly-mcp-vscode-ext-configure.adoc
@@ -0,0 +1,32 @@
+:_newdoc-version: 2.18.5
+:_template-generated: 2026-01-19
+:_mod-docs-content-type: ASSEMBLY
+
+ifdef::context[:parent-context-of-mcp-vscode-ext-enable: {context}]
+
+ifndef::context[]
+[id="mcp-vscode-ext-enable"]
+endif::[]
+ifdef::context[]
+[id="mcp-vscode-ext-enable_{context}"]
+endif::[]
+= Configuring the Ansible {VSCode} extension MCP server
+
+:context: mcp-vscode-ext-enable
+
+[role="_abstract"]
+As an automation developer, you can enable the Ansible MCP (Model context protocol) server to work with the Ansible {VSCode} extension. Doing so empowers {ToolsName} to give customized suggestions tuned specifically to your working environment.
+
+You can enable the MCP server through the {VSCode} command palette, or the *Settings* menu.
+
+== Prerequisites
+* {VSCode} is installed and running.
+* The GitHub Copilot extension is installed, running, and enabled in Agent Mode.
+* The Ansible {VSCode} extension is installed.
+
+include::devtools/proc-enable-mcp-command-palette.adoc[leveloffset=+1]
+
+include::devtools/proc-enable-mcp-settings.adoc[leveloffset=+1]
+
+include::devtools/proc-disable-mcp-server.adoc[leveloffset=+1]
+
diff --git a/downstream/assemblies/devtools/assembly-mcp-vscode-ext-create-ee.adoc b/downstream/assemblies/devtools/assembly-mcp-vscode-ext-create-ee.adoc
@@ -0,0 +1,33 @@
+:_newdoc-version: 2.18.5
+:_template-generated: 2026-01-19
+:_mod-docs-content-type: ASSEMBLY
+
+ifdef::context[:parent-context-of-mcp-vscode-ext-create-ee: {context}]
+
+ifndef::context[]
+[id="mcp-vscode-ext-create-ee"]
+endif::[]
+ifdef::context[]
+[id="mcp-vscode-ext-create-ee_{context}"]
+endif::[]
+= Create and validate an {ExecEnvShort} with the AI assistant
+
+:context: mcp-vscode-ext-create-ee
+
+[role="_abstract"]
+Use the AI assistant to generate and validate a definition file, and then build an {ExecEnvShort} with `ansible-builder`.
+
+== Prerequisites
+
+* The GitHub Copilot Extension installed and active.
+* Ansible {VSCode} extension is installed.
+* The Ansible MCP server is enabled. Ensure the setting `ansible.mcpServer.enabled` is set to `true`.
+* {ToolsName} is installed either through the AI assistant (`adt_check_env`) or manually.
+
+include::devtools/proc-create-ee-def-with-assistant.adoc[leveloffset=+1]
+
+include::devtools/proc-generate-ee-from-playbook.adoc[leveloffset=+1]
+
+include::devtools/proc-validate-ee-with-assistant.adoc[leveloffset=+1]
+
+include::devtools/proc-build-ee-with-assistant.adoc[leveloffset=+1]
diff --git a/downstream/assemblies/devtools/assembly-mcp-vscode-ext-manage.adoc b/downstream/assemblies/devtools/assembly-mcp-vscode-ext-manage.adoc
@@ -0,0 +1,30 @@
+:_newdoc-version: 2.18.5
+:_template-generated: 2026-01-19
+:_mod-docs-content-type: ASSEMBLY
+
+ifdef::context[:parent-context-of-mcp-vscode-ext-manage: {context}]
+
+ifndef::context[]
+[id="mcp-vscode-ext-manage"]
+endif::[]
+ifdef::context[]
+[id="mcp-vscode-ext-manage_{context}"]
+endif::[]
+= Manage your {ToolsName} environment with the AI assistant
+
+:context: mcp-vscode-ext-manage
+
+[role="_abstract"]
+Use the AI assistant to help you understand what is happening in your own environment without having to leave the {VSCode} editor.
+
+== Prerequisites
+
+* {VSCode} is open with the Ansible {VSCode} extension active.
+* The Ansible MCP server is enabled.
+* GitHub Copilot is active.
+
+include::devtools/proc-understand-env-with-assistant.adoc[leveloffset=+1]
+
+include::devtools/proc-understand-automation-with-assistant.adoc[leveloffset=+1]
+
+include::devtools/proc-list-available-mcp-tools.adoc[leveloffset=+1]
diff --git a/downstream/assemblies/devtools/assembly-mcp-vscode-ext-run.adoc b/downstream/assemblies/devtools/assembly-mcp-vscode-ext-run.adoc
@@ -0,0 +1,30 @@
+:_newdoc-version: 2.18.5
+:_template-generated: 2026-01-19
+:_mod-docs-content-type: ASSEMBLY
+
+ifdef::context[:parent-context-of-mcp-vscode-ext-run: {context}]
+
+ifndef::context[]
+[id="mcp-vscode-ext-run"]
+endif::[]
+ifdef::context[]
+[id="mcp-vscode-ext-run_{context}"]
+endif::[]
+= Running playbooks with `ansible-navigator` using the AI assistant
+
+:context: mcp-vscode-ext-run
+
+[role="_abstract"]
+Once you have built a suitable {ExecEnvShort}, prompt the AI assistant to generate the correct `ansible-navigator` command to execute your playbook in that particular environment.
+
+== Prerequisites
+
+* The GitHub Copilot Extension is installed and active.
+* Ansible {VSCode} extension is installed.
+* The Ansible MCP server is enabled.
+* {ToolsName} is installed through the AI assistant (`adt_check_env`) or manually.
+* An {ExecEnvShort} definition file is prepared and ready to use.
+
+include::devtools/proc-run-playbook-with-assistant.adoc[leveloffset=+1]
+
+