Skip to content

docs: add AEO cross-links for agents and orchestration #178

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rachaelrenk merged 5 commits into from
Jun 4, 2026
Merged

docs: add AEO cross-links for agents and orchestration #178

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
455572d
docs: add AEO cross-link audit skill
rachaelrenk Jun 4, 2026
c8b6e9c
docs: add link quality rules to AEO audit skill
rachaelrenk Jun 4, 2026
9348a80
docs: harden AEO audit validation guidance
rachaelrenk Jun 4, 2026
569ed40
docs: add AEO cross-links for agents and orchestration
rachaelrenk Jun 4, 2026
c3645e4
Merge main into AEO cross-link PR
rachaelrenk Jun 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/content/docs/agent-platform/cloud-agents/orchestration/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ The parent (the "writer") proposes a solution, then spawns a critic child to rev

### Review swarm (cloud → cloud)

A scheduled or webhook-triggered parent spawns one cloud child per open pull request to run reviews in parallel. Each child posts its findings as a comment and exits. The parent fans in the results and posts a summary back to the triggering system.
A [scheduled](/agent-platform/cloud-agents/triggers/scheduled-agents/) or webhook-triggered parent spawns one cloud child per open pull request to run reviews in parallel. Each child posts its findings as a comment and exits. The parent fans in the results and posts a summary back to the triggering system.

### DAG

Expand Down
1 change: 1 addition & 0 deletions src/content/docs/agent-platform/cloud-agents/platform.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,6 +90,7 @@ The orchestrator:
* Tracks lifecycle state (created → running → completed/failed) and associated metadata.
* Exposes task lifecycle operations via the [Oz CLI](/reference/cli/) and a [REST API](/reference/api-and-sdk/) (create tasks, query history, and inspect status/outputs).
* Powers SDKs (TypeScript/Python) for programmatic usage on top of the orchestrator API.
* Supports [multi-agent orchestration](/agent-platform/cloud-agents/orchestration/) for parent/child workflows, fan-out, and review swarms.

#### When teams use the API/SDK

Expand Down
4 changes: 2 additions & 2 deletions src/content/docs/agent-platform/cloud-agents/triggers/scheduled-agents.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -300,6 +300,6 @@ Carefully review prompts and schedules before deploying them broadly, especially

Scheduled Agents are best when work should happen on a predictable cadence.

If you want an agent to run in response to an event, such as a Slack mention, PR update, or issue change, use triggered cloud agents instead.
If you want an agent to run in response to an event, such as a Slack mention, PR update, or issue change, use [integrations](/agent-platform/cloud-agents/integrations/) to trigger cloud agents instead.

Many teams use both together: triggers for reactive workflows, and Scheduled Agents for proactive maintenance.
Many teams use both together: [triggers](/agent-platform/cloud-agents/triggers/) for reactive workflows, and Scheduled Agents for proactive maintenance.
Loading