ax-audit

# AX audit ## Contract | Field | Bound contract | |---|---| | Trigger | Human asks for an agentic experience audit, an AX review, whether something is agent-native, a critique of an AI feature, or whether it earns user trust | | Authority | Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. | | Side effect | Chat output only: a read-only severity-tiered report with a ship-readiness verdict and an AX Relationship Summary | | Done | Delivered findings with locators (file:line for source, logical bounds for described behavior), an AX Relationship Summary, and a PASS/FAIL/INCOMPLETE verdict | ## Inputs - Target agent system or AI feature under audit: source path, repository, or described behavior. Required. - Scope boundary: which files, modules, or interaction surfaces are in scope. Required. - Specific concern or focus area the human wants prioritized. Optional. ## Procedure 1. Read the target source or described behavior within the stated scope. Do not mutate anything. Done when: the target is read within the scope boundary. 2. Evaluate the target against two audit axes, each with four rule families. Record every finding with a locator: `file:line` for source-backed targets, or logical bounds (described behavior, interaction surface, or module name) for behavior-only targets. Architecture axis (rules-arch): - Communication: approval gate present where the agent should act autonomously; completion signal missing or ambiguous; progre...