Journey flows

Journey flows

In short: Write your two or three most common user journeys as numbered steps, each step linking its page, and note any prerequisite or where a human takes over.

• Category: Agent Readiness · weight 10 of 100 within the category
• Agent Readiness is worth 30 in technical, 25 in generic and commerce, 20 in regulated (points of 100, by scoring profile)
• Audit ID A4 (as shown on reports) · rubric v2.1

What it checks

Whether multi-step user paths are written out as numbered flows.

Why it matters

Agents that help a user through a process — buying, applying, onboarding — need the steps in order, not a pile of pages to piece together.

When it applies

Applies when the file shows evidence of multi-step work: an agent-callable action (a state-changing API operation such as POST /orders, a declared MCP endpoint that isn’t a docs-search or read-only server, or WebMCP tools) or at least one journey flow. A single user-facing link, such as “Book an appointment”, is one step and doesn’t make it apply. Otherwise it’s Not applicable.

An audit that doesn't apply, or that we couldn't verify, is removed from your score and its weight shared among the Agent Readiness audits that do apply. It is never scored as a zero.

How it's scored

0.4 for one flow, 0.6 for two or more · + 0.2 when a flow links at least half its steps to a page or names an operation · + 0.2 when a flow states a prerequisite or a human handoff, in it or just before it. A flow is at least three ordered steps outside code (a numbered list, numbered headings or an arrow chain such as “Flow: Find → Extract → Use”), most of them with content (two or more words, or a link), introduced as a journey: a nearby line or heading with a word such as journey, flow, steps, onboarding, how to, how it works, get started, quickstart, process or workflow. A file that applies with no flow scores 0.2 if it links a quickstart page (a link titled just “Quickstart”, “Quick start”, “Getting started” or “Get started”, optionally with “guide” or “tutorial”), otherwise 0; that 0.2 is never added to a flow’s score.

How to fix

1. Pick the two or three journeys users most often need help with.
2. Write each as a numbered list of at least three steps under a heading or line that calls it a journey, flow or steps, and link the page for each step.
3. Note prerequisites, and where a human needs to take over (“Prerequisite: …”, “A person takes over when …”).
4. Until the flows are written, link your Quickstart or Getting started page with that title (“- [Quickstart](https://acme.com/quickstart.md)”): it earns 0.2 of the check, a written flow 0.4 or more.

Example

## Journeys

### Journey: open an account

1. [Check eligibility](https://acme.com/eligibility.md)
2. [Apply](https://acme.com/apply.md)
3. [Verify identity](https://acme.com/verify.md)

Prerequisite: a government ID. A human takes over at the identity check if the automatic step fails.

### Journey: close an account

1. [Check balances](https://acme.com/balances.md)
2. [Transfer funds out](https://acme.com/transfer.md)
3. [Request closure](https://acme.com/close.md)