Skip to content
Chapter 20 of 28
Illustrated overview of Make the agentic workflow visible. An accessible explanation follows below.
Enlarge / view original infographic The key ideas are also explained in the text below.

Make the agentic workflow visible

Connect the goal, proposed changes and review evidence through a plan-act-validate-merge loop.

Plan, act, validate, merge

The image condenses an agentic workflow into four stages. Planning clarifies the intended outcome. Acting produces branch changes. Validation gathers tests, security evidence and review. Merging accepts the result only when the required conditions are met.

Connect the artifacts

Keep the goal or issue linked to the branch and pull request. Attach relevant workflow results and review decisions. A reviewer should be able to understand what changed, why it changed and which evidence supports acceptance.

Prefer policy-driven acceptance

The image contrasts an unstructured change with a visible, validated and policy-driven system. Implement important boundaries using required checks, review rules and limited credentials.

A diagram is not itself enforcement. If an actor can bypass the pull request or required checks, the intended architecture has a gap. Test configured controls using a harmless example before depending on them for sensitive work.