Skip to content

Create an evidence-role legend for a public research brief

Create an evidence-role legend for a public research brief: A role legend explains each passage's contribution.

Guides

What should an evidence-role legend for a public research brief make inspectable?

Imagine a brief blending quotations, reported experiences, illustrations and interpretation without visible distinctions. A role legend explains each passage's contribution. It prevents an interpretation from appearing to be another independent source and preserves narrative examples without treating their presence as proof of a broader finding or an observed causal explanation absent from the public material about the actual task.

Artifact schema and decision check
Output columns: evidence_role; local_definition; example_passage; clause_boundary; source_basis; prohibited_inference; unresolved_classification.
Decision check: Check transitions for role leakage. A reported success does not prove the analyst's explanation.
01 / Guides

Identify the concrete review task

Define only roles used in the brief. Separate quotation, attributed report, inspected scene and interpretation. Explain why the distinction matters: a proposed mechanism has not necessarily been observed, and an illustrative account does not need to represent a typical experience to help readers understand the particular problem it is used to explain.

02 / Guides

Inspect admissible supporting material

Include one concrete passage per available role. Exclude invented incidents from observed evidence; hypothetical teaching examples need labels. Montage references can locate originals, but inaccessible context cannot be replaced by calling an automated summary a directly inspected quotation or visual observation simply because its wording is specific and its citation looks convincing in the draft.

03 / Guides

Assemble the decision artifact

Annotate where basis changes within paragraphs. One passage may blend an account and explanation. Repeated automated interpretations of a source remain interpretations, not independent confirmations that increase case counts, verify the event or establish a missing mechanism behind the reported outcome; preserve the source's own uncertainty and the analyst's separate contribution in the worksheet.

04 / Guides

Check the inference and action boundary

Check transitions for role leakage. A reported success does not prove the analyst's explanation. Narrow unsupported meaning instead of adding decorative disclaimers while leaving the same implication in headlines or summary statements readers see first, and do not treat an illustrative scene as a controlled demonstration just because it appears alongside factual prose.

05 / Guides

Deliver the bounded review state

Deliver definitions, annotated examples and unresolved classifications. The legend improves interpretation without assigning fabricated scores or automatic approval. Clear labels do not satisfy unmet counts, create independent cases or certify each product account as true; they make evidence basis and remaining judgment inspectable so a reviewer can decide what the brief legitimately supports for its stated use.

Keep the boundaries clear.

  • Clear labels do not satisfy unmet counts, create independent cases or certify each product account as true; they make evidence basis and remaining judgment inspectable so a reviewer can decide what the brief legitimately supports for its stated use.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage