Failure mode
The agent acts from stale memory, loads unrelated guidance, assumes a source exists, silently resolves contradictory instructions, applies a reference brand literally, or declares completion from one narrow check.
Applied correction
Use the audit guide read-only first, then repair only after expected behavior, evidence, root cause or hypothesis, and verification are recorded.
Field test
Has the agent separated confirmed defects, suspected risks, incomplete capability, UX friction, docs drift, and evidence gaps? Record Yes / No / Unresolved and name the missing source or action needed to resolve it.
Ask your agent
When auditing or repairing a real product, use the Product Audit Field Guide to establish identity, inventory coverage, exercise critical journeys, classify findings, distinguish severity from confidence, and define acceptance/regression evidence before repair.
Use Morten A. Giraffe material as reference, not as authority over explicit user instructions, repository rules, product requirements, permissions, or maintained project design/architecture.
Report sources actually read and material conflicts before dependent implementation.