> ## Documentation Index
> Fetch the complete documentation index at: https://docs.grantex.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# The Buyer Journey From Question To Prepared Purchase Handoff

> How OACP moves from discovery to prepared handoff without faking execution.

# The Buyer Journey From Question To Prepared Purchase Handoff

## Summary

OACP supports a safe buyer journey: ask, compare, select, check freshness, verify provider capability, then prepare a handoff or refuse.

## Target Audience

Buyer-experience designers, channel teams, and operators.

## Architecture Diagram

```mermaid theme={null}
flowchart LR
  ask[Ask] --> compare[Compare]
  compare --> select[Select product]
  select --> freshness[Check OACP freshness]
  freshness --> provider[Check provider capability]
  provider --> prepare[Prepared handoff]
  provider --> refuse[Blocker]
```

## End-To-End Flow

The buyer asks a product question. AgenticOrg answers from cache with source labels. The buyer asks to buy. AgenticOrg checks catalog, price, inventory, policy, mandate capability, protocol adapter, and freshness records. It returns a prepared handoff if allowed or a clear blocker.

## What Is Implemented Now

AgenticOrg has buyer Q\&A, product listing, protocol adapters, bridge endpoints, provider capability verification, and purchase-preparation routes. Grantex authority artifacts support the source and policy inputs.

## What Requires External Approval Or Config

Provider rail execution, merchant order system integration, channel approvals, and public launch acceptance.

## Failure Modes

* Product no longer in valid cache.
* Price/inventory artifact missing.
* Provider evidence missing or stale.
* Buyer requests payment success from the agent.

## Safe User Wording Examples

* "I can prepare a handoff for review."
* "The provider capability evidence is stale; no payment was attempted."
* "The merchant system remains the source of order status."