# Fictional example: approval routing demo

This example is synthetic. “Northstar Logistics” is not a customer, and no outcome
below is a commercial claim.

## Evidence ledger

| Claim or constraint | Source and date | Status | Safe wording |
| --- | --- | --- | --- |
| Purchase requests pass through email | Synthetic discovery note, 29 Aug 2026 | buyer-stated | “You described email as the current intake path. Is that still correct?” |
| Finance must approve requests above a threshold | Synthetic policy excerpt, 29 Aug 2026 | observed | “The sample policy requires finance approval above its configured threshold.” |
| The workflow saves two hours per request | No source | unknown | Do not say this. Ask which steps consume time today. |
| An ERP integration is available | Product release note, 29 Aug 2026 | observed | “This demo environment includes the documented ERP connector.” |
| The buyer will adopt the workflow this quarter | No source | inferred | Do not say this. Ask what an internal evaluation would require. |

## One narrative

- Starting condition: a fictional requester emails a purchase request.
- Job: route the request to the correct approver and preserve the decision record.
- Product actions: create request, apply sample threshold, approve, inspect history.
- Observable end state: status, approver, timestamp, and decision are visible.
- Limitation: the example does not measure time saved or production adoption.

## Fallback

If the ERP connector is unavailable, show the saved request and approval history from
a rehearsed synthetic account. State that the live integration failed; do not present
the fallback screenshot as a live result.