review-zoom-v3-gene-browser-inventory

Review zoom v3 gene browser: inventory PHR intervals and gene annotations

Metadata

Statusdone
Assignedagent-1024
Agent identity3577bc75d6ed4f1947509aa5c086c91ce7c997c7806dab6bf6affac647452647
Created2026-05-07T00:58:49.927268603+00:00
Started2026-05-07T01:01:39.664505521+00:00
Completed2026-05-07T01:12:58.591108197+00:00
Tagsbog-this-week, bog-deck, review-zoom, review-zoom-v3, eval-scheduled
Eval score0.94
└ blocking impact0.96
└ completeness0.95
└ coordination overhead0.94
└ correctness0.93
└ downstream usability0.96
└ efficiency0.91
└ intent fidelity0.97
└ style adherence0.95

Description

User feedback: slide 14a has no useful information; what is missing is annotations of genes over the regions of the PHRs discovered. We need focused, systematic genome-browser views across selected PHRs.

Goal: find canonical interval and gene annotation inputs needed to make genome-browser-style views for PHRs and their genes.

Requirements:

  • Search repo and HPRCv2 paths for canonical PHR intervals, projected homologous regions, gene annotation GFF/GTF/BED, gene family summaries, DUX4/D4Z4/OR4F/TAR1 annotations, and community assignments.
  • Use git history and prior gene-enrichment/provenance notes to distinguish canonical outputs from stale intermediates.
  • Build a target list of candidate browser-view loci: at minimum DUX4/D4Z4 C1 4q/10q, OR4F-rich subtelomeres, TAR1-rich arms, one acrocentric p-arm group, and 1-2 top gene-enrichment/community examples.
  • For each target, record coordinates, assembly/haplotype/arm, community, genes/repeats to display, source files, and why it belongs in the talk.
  • Recommend a minimal track schema: PHR intervals, genes, gene family labels, repeat/TAR1/D4Z4/OR4F markers, optional community/copy-number annotation.
  • Keep outputs under slides/v2-review-zoom/_revision_assets/v3/gene_browser_inventory/.

Validation:

  • README includes source paths and a target-locus table.
  • Coordinates are in a clearly named coordinate system/assembly.
  • It is clear what downstream renderer should draw.

Depends on

Required by

Log