Aglet

Triage an Agent Workflow With Missing Evidence

Missing evidence is a workflow boundary, not a conclusion about the recommendation. Triage should state the decision at risk, list the observations required to support it, and compare those requirements with the artifacts actually available. Record freshness, provenance, and inaccessible sources as separate gaps.

Establish what is happening

  1. Name the claim

    Write the recommendation, diagnosis, or comparison the agent is expected to support, then identify the exact facts that would make it credible. Separate observations from interpretations and assumptions. Mark claims that cannot be evaluated without a source artifact, timestamp, or comparison.

  2. Inventory available evidence

    List files, records, logs, queries, screenshots, test outputs, and human observations in scope, with source, time, revision, and completeness. Check whether each item directly supports a claim, merely provides context, or conflicts with another artifact. Preserve absent evidence explicitly.

  3. Bound the review gap

    Group unsupported claims by decision, source, time window, and evidence type. Record the smallest missing observation that would change the review outcome. Distinguish unavailable evidence from evidence that was gathered but omitted from the handoff.

What to carry forward

Return an evidence-gap brief naming the decision, claims, available artifacts, provenance, missing observations, and review consequence. Triage stops when a reviewer knows what can and cannot be evaluated. Keep the result unready when a material claim lacks a source or a stated uncertainty.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow