Use Retrieval as an Audit Surface

Lesson outcome

You will be able to pull the right notes into an audit and use them as evidence rather than relying on memory or model confidence.

Why this matters in an agency

Most audit failures are evidence failures. The reviewer critiques the output in the abstract because it never saw the canonical note, the policy, the brief, or the architecture doc that should govern the decision. Retrieval fixes that by pulling the real business context into the review.

Inputs, tools, and prerequisites

You need the output being reviewed, a retrieval surface into your vault, and a short list of note types that usually matter: offer docs, SOPs, project notes, buyer personas, pricing notes, and prior lessons.

Step-by-step walkthrough

Start by defining the claim or behavior you are trying to verify. Then retrieve the notes that should govern it. If you are auditing offer copy, retrieve the buyer persona, offer note, pricing logic, and any recent decision notes. If you are auditing code or systems work, retrieve the architecture note, deployment constraints, and relevant runbooks.

Ask Codex to compare the output against those sources explicitly. The question is not "is this good." The question is "where does this drift from the stored decision or documented rule." This produces a much stronger audit because the standard is visible.

If the relevant note cannot be found or is clearly weak, that is an audit finding too. The vault is part of the system. Weak notes create weak verification. Improve the note or mark it for follow-up rather than pretending the evidence base is adequate.

Failure modes and verification checks

The main failures are pulling irrelevant notes, trusting adjacent notes instead of canonical ones, and forgetting to update the source note when the decision changes. Verify by checking that each material claim in the output maps back to a note or source you can point at.

Implementation checklist

• Define the claim or behavior under review.
• Retrieve the canonical notes that govern it.
• Compare output to source notes explicitly.
• Flag weak or missing notes as part of the audit.
• Update the source note if the decision changes.

Immediate next action

Audit one live piece of copy or one live workflow using only the vault notes you can actually retrieve today.