Phage Host-Range Reuse Map

Why It Matters

Mobile-element and phage work is represented in the Atlas, but it has not yet produced a named reusable product comparable to metal scores or ecotype labels. This opportunity asks what the first reusable phage/mobile product should be.

Review Brief

What changed: prophage-AMR and T4SS/CAZy work make the need for a reusable mobile-context product more concrete.

Why review matters: reviewers should decide whether the first product should be host range, defense context, mobile-element burden, or mechanism-partitioned transfer features.

Evidence to inspect:

• Mobile Elements, Phage, and Genome Plasticity for topic synthesis.
• Phage, mobile, and defense data for data substrate.
• prophage_amr_comobilization, prophage_ecology, ibd_phage_targeting, and snipe_defense_system for candidate outputs.

Questions for reviewers:

• Which product would have the most immediate consumers across AMR, host, and pangenome topics?
• Are current phage/mobile annotations strong enough for promotion, or only for screening?
• Should host-range and mobile-element burden be separate products?
• What validation would make a phage/mobile product reusable outside its source project?

Evidence Base

The relevant projects span prophage ecology, defense systems, phage targeting, and strain variation. Existing PhageFoundry and genome collections provide the data substrate, but the reusable abstraction is still underdefined.

Work Package

Inventory outputs from phage and mobile-element projects. Group them into candidate product types: host-range labels, defense-context scores, mobile-element burden, or phage-targeting compatibility. Identify which candidate has enough provenance and consumer demand to promote first.

Decision Use

The output should either create a new derived-product page or explain why phage/mobile outputs are not ready for promotion. This keeps the Atlas honest about reuse maturity.