Skip to main content

The Audit Trail

Citation to source as a product feature: every answer carries a pointer to the exact place it came from, so the human verifies instead of hunts.

Hand-drawn line illustration in warm terracotta and cream: a loopy line-drawn hand holds up a single cream card joined by one continuous wobbly line back to the small stack of cream cards it came from, a one-line profile face watching.

What it is​

An audit trail, in the agent-product sense, is the discipline of making every output traceable: each extracted fact, each drafted claim, each triage decision points back to the source document, sentence, or record it came from. The founders building for regulated and high-stakes buyers treat it as table stakes; Alloovium, in YC's Summer 2026 batch, describes a system where "every answer cites its exact source sentence," paired with the policy that "nothing AI-drafted moves without a human sign-off."

Why it changes the economics of review​

Citation converts review from search to spot-check. Without it, the human verifying an AI output must re-find the evidence, which can cost nearly as much as doing the work; with it, verification is a click. The corpus quantifies the difference:

  • Carta Healthcare's abstraction product answers clinical registry questions "with justifications and direct citations, so human abstractors validate rather than hunt," per its story, which also reports abstractors previously spending "on average, one hour per case manually combing through clinical notes and documents" and quality holding at "98-99% Inter-rater Reliability (IRR) scores." (source)
  • Quillit measured citation quality directly and published the delta: "Before using Claude 3.5 Sonnet, our accuracy rating for citations was around 60-70%. After that, it was between 89-98%." Its stated stake: precision is "crucial for our clients' confidence in the insights they receive." (source)
  • Elation Health ships cited summaries of a patient's longitudinal chart inside the EHR, and reports "Reduced median time to first insight by 61% for chart review." (source)

The other trail: what the agent did​

Product citations answer "where did this claim come from." Operating an agent adds a second question: "what did the run actually do?" The platform's primitives leave that trail as a by-product when used properly: per-firing run records on Scheduled Deployments, versioned writes on Memory Stores, immutable config versions under Agent Once, Session Every Run, and persisted approval decisions at the Human Gate (details in the platform docs; verify against platform.claude.com/docs, beta surfaces drift). Together they answer the auditor's question: which config, which run, which sources, who approved.

Why it earns a concept page​

Because it is the feature that makes the Human Gate fast enough to keep. An approval step whose reviewer must hunt for evidence gets bypassed under deadline pressure; an approval step with citations attached stays cheap enough to survive contact with a busy Monday. Traceability is not compliance overhead on the product; it is what lets the product be trusted at speed. The same standard this wiki applies to published metrics (see Strength of Evidence) applies inside an agent product: a claim you can check beats a claim you must take on faith.

Further Reading​