From 36d1525e786095d93cc9b9bf2b98462bcf302147 Mon Sep 17 00:00:00 2001 From: Mara Nikola Kiefer <8320933+mnkiefer@users.noreply.github.com> Date: Wed, 21 Oct 2026 10:38:24 +0200 Subject: [PATCH] docs: introduce AWs in the opening CAO definition Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 76fb2e66-3141-40a8-a5d7-2abd6fd5572c --- docs/architecture-at-a-glance.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/architecture-at-a-glance.md b/docs/architecture-at-a-glance.md index 57e31e4f7..55333c3c2 100644 --- a/docs/architecture-at-a-glance.md +++ b/docs/architecture-at-a-glance.md @@ -6,8 +6,9 @@ next: label: How does CAO work? --- -**Central Agentic Ops (CAO)** is a system for monitoring and governing GitHub -Agentic Workflows across repositories. It brings collected activity, cost, and +**Central Agentic Ops (CAO)** is a system for monitoring and governing +[GitHub Agentic Workflows (AWs)](https://github.github.com/gh-aw/introduction/overview/) +across repositories. It brings collected activity, cost, and outcome evidence into a shared dashboard and supports policy-governed execution and rollout of participating shared workflows. @@ -16,8 +17,7 @@ and rollout of participating shared workflows. ## What is CAO? Agentic work might begin with a single task, then grow across repositories. -[GitHub Agentic Workflows (AWs)](https://github.github.com/gh-aw/introduction/overview/) -run those tasks in GitHub Actions, using Markdown instructions and configured +AWs run those tasks in GitHub Actions, using Markdown instructions and configured tools and permissions. These AWs form the building blocks of CAO as we scale. CAO helps you operate these building blocks together: