Read-only demo
Mermaid-authored diagram

Procurement Copilot Workflow Diagram

This page now shows the workflow as one simple static diagram so it is easier to explain live: route the request, follow one of three paths, and end in a supported outcome.

Demo-safe summary only. This view does not expose prompts, raw evidence chunks, search scores, secrets, or internal exception details.
Simple architecture view
One diagram, three routes, four outcomes
Static SVG image

The diagram below is authored from a Mermaid source file and rendered as a static SVG so the page stays clean, readable, and reliable during demos.

Procurement workflow diagram showing User Chat Input to Orchestration Agent, then branching to Procurement Execution, Policy Q&A, or Unsupported, with Azure AI Search and deterministic guardrails supporting the procurement path.
Source maintained in docs/diagrams/workflow-diagram.mmd and shown here as a static image for clarity.
How to explain it quickly

Start with one chat request.

The orchestration stage picks the correct path.

Only the procurement path can create Approved or Rejected outcomes.

Policy questions stay advisory and unsupported requests are redirected.

What the audience should remember

Procurement execution

Intake → Compliance → Purchasing → Approved or Rejected

Policy advisory

Policy Q&A → PolicyAnswer with references only

Unsupported fallback

Unsupported → guidance back to a supported task

Guardrails

Hardware over $5,000, non-compliant vendors, and missing required fields block approval

Presenter notes
Azure AI Search provides policy evidence to the compliance stage.
Deterministic backend guardrails stay authoritative over approval decisions.
The page intentionally omits prompts, tool traces, raw retrieval payloads, and exception details.

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.