Druantia system
traitmech:000234 · CLASS · PROPOSED
A phage defense system in which an organism possesses a Druantia locus encoding a conserved DruE-family core and subtype-specific partner proteins.
Trait evidence
-
DOI:10.1126/science.aar4120Druantia DruABCDE (type I) DruMFGE (type II) DruHE (III) pfam14236, pfam00270, pfam00271, pfam09369, COG1205, pfam00145, COG0270 Helicase, methylase 1,342 1,321 (2.6%)
-
DOI:10.1126/science.aar4120A Type I system cloned from E. coli UMEA 4076-1 into E. coli MG1655 rendered the engineered strain resistant against 4 of the 6 phages tested
-
DOI:10.64898/2026.05.12.724681There are several subtypes of Druantia that all share the DruE protein but differ in their associated genes
-
DOI:10.64898/2026.05.12.724681Druantia III is a late-acting defence where DruH is the likely infection sensor and DruE is a helicase-nuclease effector that engages ssDNA-containing replication intermediates
-
DOI:10.64898/2026.05.12.724681we identified 6,885 bacterial genomes encoding complete Druantia III systems, defined by the presence of both DruE and DruH
-
DOI:10.64898/2026.05.12.724681DruE is the only component shared across Druantia subtypes, suggesting that DNA processing by a DruE-like helicase-nuclease is the conserved core function of Druantia
-
DOI:10.1093/nar/gkab883the Druantia-like system lacks the type II requisite DruM and DruG proteins, instead encoding a hypothetical protein
Provenance
- Identifier source
- TraitMech local identifier
- Definition source
DOI:10.64898/2026.05.12.724681
Parent traits (1)
Children (4)
Synonyms (1)
- Druantia
kg-microbe context
Matched 1 kg-microbe node via parent_proxy.
METPO:1000188[-0.956, -1.962, -3.148, +1.274, …]
Nearest neighbors in embedding space
- upper quality 1.000
- genomics Kongming system 1.000
- genomics Kiwa system 1.000
- genomics Kamadhenu system 1.000
- genomics JukAB system 1.000
- genomics integrative conjugative element 1.000
- genomics Ig-like Schlafen system 1.000
- genomics Hypnos system 1.000
Canonical examples
-
Escherichia coli
NCBITaxon:562DOI:10.1126/science.aar4120
Discussions and Knowledge Gaps
Resolve Druantia subtype mechanisms separately from architecture-based possession classes.
Doron et al. separated Type I DruABCDE, Type II DruMFGE, and Type III DruHE architectures and validated one Type I locus, while Wu et al. define a Type III mechanism in which DruH likely senses infection and DruE engages ssDNA-containing intermediates. Druantia III system now captures the DruE/DruH Type III branch from the pinned Druantia_III DefenseFinder row, but the parent record remains at the DruE-core family level until separate review resolves Type I and Type II partner functions, Type IV partner functions represented by the pinned Druantia_IV HMM rows, exact phage triggers, native host breadth, and Zorya-coupled versus standalone outputs across Druantia loci. Druantia type IV system (traitmech:000577) now captures the DruE/F/L architecture described by Payne et al. (DOI:10.1093/nar/gkab883), without the type-II DruM/G components. This resolves the architectural child, not type-IV experimental defense or partner chemistry. The family definition no longer requires universal helicase-nuclease DNA processing. Wu et al.'s family-wide conservation claim is a hypothesis in a type-III preprint. The overgeneralized parent graph is removed; the characterized III branch remains at traitmech:000560. New proposal v454 replaces the unminted v111 family row without changing the local family identifier or historical TSV. Type I architecture is now represented by traitmech:000578 Druantia type I system: DruB/C/D/E with optional DruA. Doron's optional DUF4338 component and the Ralstonia study's mapping of that domain to DruA qualify the earlier five-gene shorthand. The five-profile PADLOC rule and three-match DefenseFinder threshold are detection criteria, not identical biological definitions. This resolves the type-I architecture lead, not its partner functions or native-host mechanism. Type II architecture is now represented by traitmech:000579 Druantia type II system, defined by DruM/F/G/E possession using DOI:10.1093/nar/gkab883. Hou et al. version 2 (DOI:10.65215/LTSpreprints.2026.06.18.000273, 2026-07-08 preprint) adds Pf-5 DruE biochemistry and a limited heterologous assay, not full-system or native-host phage-defense validation. The architectural lead is resolved; accessory roles and the transition from DNA unwinding to phage restriction remain open.
Evidence
-
https://raw.githubusercontent.com/mdmparis/defense-finder-models/afb0e5a8b466be53586b13266f5d38d98c3ac268/Liste_hmm_system.md| Druantia_IV__DruE4 | | Druantia_IV | Custom | 750 | | Druantia_IV__DruF4 | | Druantia_IV | Custom | 20 | | Druantia_IV__DruL | | Druantia_IV | Custom | 100 |
Curation history
-
·
MINTED_TRAITMECH_ID · codex
Minted Druantia system as a DOI-backed GENOMICS TraitRecord under the phage defense system parent after an ignored-and-hidden duplicate review found no exact live TraitMech, METPO, or prior proposal record; the replacement placeholder is reserved in proposals/metpo_traitmech_v111.
-
·
TRACK_NARROWER_RECORD · codex
Documented Druantia III as split out in the open Druantia subtype discussion after minting traitmech:000560 for the DefenseFinder-backed Druantia_III child; Type I, Type II, the pinned Druantia_IV HMM context, Zorya-coupled versus standalone activity, and finer Druantia activation mechanisms remain open.
-
·
SCOPE_DRUANTIA_FAMILY_AND_TYPE_IV · codex
Addressed #1635: removed a universal DNA-processing requirement and the overgeneralized family graph, retaining evidence with preprint/hypothesis qualifiers. Linked the new type-IV architecture child traitmech:000577. The existing III record retains its characterized mechanism; type-IV defense remains unresolved. Proposal v454 supersedes the v111 family row.
-
·
TRACK_DRUANTIA_TYPE_I_CLASS · codex
Linked traitmech:000578 using DOI:10.1126/science.aar4120 and DOI:10.3389/fmicb.2020.00961. Resolved the type-I architecture lead with optional DruA and distinct detector thresholds. Kept family identity, definition, hierarchy, evidence and example unchanged; type-I functions and the type-II lead remain open.
-
·
TRACK_NARROWER_RECORD · codex
Linked traitmech:000579 Druantia II possession using DOI:10.1093/nar/gkab883 and the July 8 version of DOI:10.65215/LTSpreprints.2026.06.18.000273. Resolved the architecture lead while preserving full-system mechanism uncertainty. Family identity, evidence and example are unchanged.
Recorded curation sessions
-
· codex
- CREATE — Add Druantia system trait
Minted traitmech:000234 for the Druantia phage-defense system after an ignored-and-hidden duplicate search found no exact live TraitMech, METPO, or prior proposal record for Druantia, the expected slug, the source DOI identifiers, or the reserved IDs. Curated DOI-backed Doron and Wu evidence, an Escherichia coli canonical example, a nonmechanistic causal graph for DruE-core DNA processing, and a same-PR METPO v111 proposal.
- CREATE — Add Druantia system trait
-
· claude-code
- EDIT — Track Druantia III split
Documented traitmech:000560 Druantia III system in the open Druantia subtype-mechanism discussion after minting the DefenseFinder-backed Druantia_III child, and cited the pinned Druantia_IV HMM rows for Type IV scope. Type I, Type II, exact phage triggers, native host breadth, Zorya-coupled versus standalone activity, and finer Druantia activation mechanisms remain open.
- EDIT — Track Druantia III split
-
· codex
- EDIT — Restrict Druantia family to shared architecture
Addressed #1635 by removing universal helicase-nuclease DNA processing from the Druantia family definition and removing its overgeneralized family graph. The characterized type-III child remains unchanged. Preserved existing evidence and canonical example, identified Wu et al. DOI:10.64898/2026.05.12.724681 as a preprint and the universal mechanism as a hypothesis, and added Payne et al. DOI:10.1093/nar/gkab883 architecture evidence. Linked type-IV traitmech:000577 without resolving its functional gaps. Proposal v454 replaces the unminted v111 family placeholder while retaining its TSV and stable traitmech:000234 identity.
- EDIT — Restrict Druantia family to shared architecture
-
· codex
- EDIT — Resolve Druantia type-I architecture lead
Replaced the open type-I architecture lead with a link to traitmech:000578 and explained optional DruA versus detector thresholds, citing DOI:10.1126/science.aar4120 and DOI:10.3389/fmicb.2020.00961. Type-I partner mechanisms and the type-II lead remain open. Guarded writer preserves the family definition, identity, hierarchy, evidence and canonical example; adds one curation-history event. No protected record or existing III/IV child was edited.
- EDIT — Resolve Druantia type-I architecture lead
-
· codex
- EDIT — Link the Druantia II architectural child
Updated only the existing family knowledge-gap tail and appended TRACK_NARROWER_RECORD through the validated writer. Linked traitmech:000579, resolved the type-II architectural discovery lead and retained full-system and native-host defense uncertainty. The July 8 version-2 preprint contributes isolated DruE evidence, not family-wide chemistry. Family identity, definition, hierarchy, evidence, canonical example, prior provenance and sibling records are unchanged.
- EDIT — Link the Druantia II architectural child