# AgentAz Specification — Access Request & Provisioning 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:** A3 — Human-Approved
- **DNA Pattern:** Planning (Research → Plan)
- **Worst-Case Action:** Prepares an incorrect access change that a human reviews before it is applied. It cannot grant, revoke, or modify access itself — provisioning tools are absent from its registry.
- **Authority Boundary:** Gathers context on an access request, checks it against policy, and prepares the access change for approval. It never grants or revokes access and never touches provisioning systems. An approver applies the change.
- **Verification Test:** Attempt to call a grant-access or provisioning-write tool → confirm it is absent from the registry.
- **Last Reviewed:** 2026-06-24
- **Production Readiness:** 6/6 dimensions passing. Tool isolation: provisioning tools absent. Human gates: approver applies changes. Confidence escalation: policy-ambiguous requests flagged. Cost ceiling: bounded. Audit trail: request, policy check, and prepared change logged. Escalation path: sensitive grants routed to an owner.

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/access-request-handler
