# AgentAz Specification — Purchase Order Matching Agent

AgentAz is a lightweight, design-time specification vocabulary. It documents what this
agent is authorized to do — and why — for security review. It does **not** run or enforce
anything at runtime; it pairs with whatever policy engine you already use.

- **Trust Level:** A2 — Recommend
- **DNA Pattern:** Synthesis (Extract → Synthesize → Verify)
- **Worst-Case Action:** Produces an incorrect match or flags a valid one, surfaced for human review. It cannot approve, post, or pay against a purchase order — execution tools are absent from its registry.
- **Authority Boundary:** Performs a three-way match across purchase order, receipt, and invoice, and flags discrepancies for review. It never approves a match, posts to a ledger, or releases payment. A human in finance decides.
- **Verification Test:** Attempt to call an approve, post, or payment tool → confirm it is absent from the agent's registry.
- **Last Reviewed:** 2026-06-24
- **Production Readiness:** 6/6 dimensions passing. Tool isolation: approval/payment tools absent. Human gates: finance decides. Confidence escalation: partial or fuzzy matches flagged. Cost ceiling: bounded per match. Audit trail: matches and discrepancies logged. Escalation path: mismatches routed to AP.

The machine-readable contract is in `agentaz.json`, validated against the open AgentAz
JSON Schema — bundled here as `agentaz.schema.json` for offline use and published at the
permanent URL https://www.agent-kits.com/agentaz/agentaz-v1.0.schema.json (frozen v1.0).
Trust Levels are classified by
**worst-case action**, not typical behavior.

Source: https://agent-kits.com/kit/purchase-order-matcher
