From one public variant expression to a reviewable evidence package

Step-by-step agent flow

Call search_variant_evidence with GRCh38 and the public expression. Continue only if the result is resolved.

• Record normalized coordinates, alleles, gene, transcript and canonical key.
• Report the current automated classification and applied criteria.
• Group available evidence by source and preserve data versions.
• Use the canonical key for variant literature when requested.
• Inspect individual PMIDs only after they are returned by literature search.
• End with limitations and qualified professional review.

Identity checks with public examples

For a BRCA1 example, the verified public GRCh38 identity GRCh38:chr17:43124027:ACT:A resolves to BRCA1 ENST00000357654.9:c.68_69del. A separate non-BRCA example, ENST00000226413.5:c.317A>G, resolves to GNRHR. These examples show why a gene name or familiar short form must not replace exact allele and transcript verification.

• Preserve the transcript accession and version supplied by the user.
• If that transcript expression does not resolve, report the state instead of substituting a different transcript.
• Treat GRCh37 input as outside the current GRCh38 contract unless the user supplies a separately verified GRCh38 representation.
• Report structural variants and other unsupported variant types as unsupported.
• Do not freeze a classification label in an example because evidence and source versions can change.

Branch before you summarize

For an ambiguous result, show candidates and ask the user to choose. For not found, invalid, unsupported or temporarily unavailable states, report the state directly. Never substitute a likely variant or a model-memory classification.