- Rating
- 3
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
In this paper, the authors explore the all-atom generative approach for chameleon protein design. The AtomDiff-X is first developed for end-to-end all-atom protein design, and a fine-tuned model, AtomDiff-Chameleon, is introduced to generate alternative conformations for identical amino-acid sequences in different structual contexts. In addition, a large paired-structure dataset from AFDB is constructed and utilized for finetuning and evaluation. Experimental results demonstrate that the proposed AtomDiff-Chameleon outperforms ProteinGenerator in joint generation of the shared chameleon sequences. Case study on joint motif and chameleon design illustrate the potential of designing switchable protein variants.
Critical strengths
- Multistate protein design is a valuable problem to investigate, and the paper identifies the challenges of that.
- A large paired-structure dataset is constructed, including 3M distinct sequences and 11M structural pairs, which is benefit for sequence-structure relationships across alternative conformations.
- The AtomDiff-Chameleon, which is finetuned based on the proposed AtomDiff-X with the constructed dataset, is introduced. Experimental results demonstrate its effectiveness and performance advantage on de novo chameleon sequence design, and a case study illustrate its potential of designing switchable protein variant.
Critical weaknesses
- The authors acknowledge that the designs share local sequences while their surroundings differ. A shared segment can adopt different conformations in different structual environments without establishing that one complete protein sequence can access both conformations. The structual context and tertiary interactions outside the shared segment may be decisive. The paper should frame the contribution as a framework for generating alternative structures with shared sequence segments, rather than as a practical framework for multistate protein design. The paper should clearly and consistently distinguish alternative local conformations from conformational switching by one complete protein sequence to avoid misleading.
- Both training set and test set are constructed from AFDB. The train/validation/test splitting procedure should be described in detail. The paper should establish that the experimental results do not rely on close homologs, duplicated structural contexts or overlapping segments, since random splitting can produce overly optimistic estimates if related sequences, motifs, or structual contexts appear across training and test sets. It would be better to report sequence identity distributions between test and training set and explain how overlapping pairs and homologous sequences are handled.
- AtomDiff-Chameleon contains several key components, including Token DiT, Atom DiT, and cross-branch attention. The paper would benefit from a targeted component ablation study with the same paired structural supervision.
Questions for authors
- How are the paired structures split across training and testing? Are sequence clusters and homologous structural contexts kept separate?
- How much of the improvement is attributable to each key architectural designs? Could the authors isolate these effects with more controlled ablations?
4 comments
Responses 2/n
3. Sampling conditions, overlap with the training data, and sequence novelty
We thank the reviewer for raising concerns about close homologs, repeated structural contexts, and overlapping segments. In our sampling task, the model starts from noise and jointly generates the shared chameleon segment and its surrounding sequence and structural context in each of the two chains, A and B. We specify the length of each chain, the length of , its position in each chain, and the residue-to-residue correspondence between the two segments. For Table 3, we also provide local secondary-structure (SS) labels for in states A and B. These labels come from natural segments, and the model receives neither their amino-acid sequences nor their 3D coordinates or surrounding backbones. Below, we clarify what information each input provides and directly compare the generated sequences with the training sequences.
-
Length of the shared segment. The length specifies only how many residues must have the same sequence in the two chains. In addition to the 6–10-residue segments in Table 3, we tested lengths of 12, 24, 36, and 48 residues in Figure 5. All four exceed the longest shared segment in our curated natural chameleon pairs (11 residues). Successful designs are thus not restricted to shared-segment lengths observed in the natural paired data.
-
Position of the shared segment. We sample the start position of independently and uniformly from the eligible internal positions in each chain. We grouped the original 1,000 designs according to whether the midpoint of fell in the N-terminal, middle, or C-terminal third of each 96-residue chain. Each cell below reports the number of successful pairs divided by the number of pairs with that placement (Success rate). | Position of in chain A | Chain B: N-terminal third | Chain B: middle third | Chain B: C-terminal third | | :--- | ---: | ---: | ---: | | N-terminal third | 22/105 (21.0%) | 40/118 (33.9%) | 23/103 (22.3%) | | Middle third | 28/103 (27.2%) | 39/147 (26.5%) | 23/117 (19.7%) | | C-terminal third | 22/103 (21.4%) | 27/114 (23.7%) | 32/90 (35.6%) |
We observed successful designs in all nine placement combinations, including cases in which lay near the N-terminus of one chain and near the C-terminus of the other. Successful design is therefore not restricted to a particular position, nor does it require to occupy the same position in both chains.
-
Local SS conditions. The local H/E/C labels are the only sampling input taken directly from natural structures. Some of the natural pairs from which these labels were drawn also appear in the training index. We held the chain lengths, the length and positions of , the random seeds, and the initial noise fixed, removing only the SS labels on in both chains. | Position of in chain A | Chain B: N-terminal third | Chain B: middle third | Chain B: C-terminal third | | :--- | ---: | ---: | ---: | | N-terminal third | 22/105 (21.0%) | 40/118 (33.9%) | 23/103 (22.3%) | | Middle third | 28/103 (27.2%) | 39/147 (26.5%) | 23/117 (19.7%) | | C-terminal third | 22/103 (21.4%) | 27/114 (23.7%) | 32/90 (35.6%) |
Without SS labels, 293 pairs still had identical sequences across and passed independent refolding for both chains.
-
Similarity between generated and training sequences. We compared all 2,000 chains generated under the original SS-conditioned setting in Table 3 with the host sequences eligible for sampling during fine-tuning or earlier monomer pretraining. We also analyzed the 256 successful pairs separately. For each 96-residue generated chain, we compared its sequence with every contiguous 96-residue window in the training hosts and recorded the highest ungapped sequence identity over all 96 positions. | Comparison with training hosts | All designs (2,000 chains) | 256 successful pairs (512 chains) | | :--- | ---: | ---: | | Full 96-residue sequence occurs verbatim in a training host | 0/2,000 | 0/512 | | Median sequence identity to the closest 96-residue window | 27.08% | 26.04% | | Chains with ≥50% sequence identity to the closest 96-residue window | 11/2,000 | 1/512 |
These results support the novelty of the designs: none of the 2,000 generated chains was copied verbatim from a training host, and the median identity to the closest 96-residue training window was only 27.08% overall and 26.04% among chains from successful pairs.
In general, given the generative nature of our model, we did not conduct the conventional train/test analysis used for discriminative models. Based on our examination of the model inputs, we see no indication of data leakage or memorization.
Responses 3/n
4. Bridging the gap between chameleon pairs and fold-switching proteins
To further illustrate our vision for multistate protein design, we also fine-tune RFD4-proteina on our chameleon dataset using cross-branch communication. Using RFD4 as the base model, we can combine its protein–protein interface design capability with chameleon design to generate real fold-switch proteins. We extend paired chameleon design to two complexes, and , both designed de novo. The same full-length protein adopts different folds depending on whether it binds or . Therefore, the design objective is a full-length protein that switches folds depending on its binding partner.
To generate de novo fold-switching proteins, we sampled using the recommended RFD4 settings. We set the protein length of 32 for and 96 for and . We generated 64 pairs of protein complexes and predicted their structures using AlphaFold3(AF3). We set the in silico success criteria as follows:
- Both complexes have
ipTM>0.6andcomplex-RMSD<2, - The two conformations of differ (
cross-state RMSD>3).
| Success rate | Avg. complex RMSD (Å) | Avg. ipTM | Avg. cross-state RMSD of chain (Å) | Avg. SS difference in chain |
|---|---|---|---|---|
| 15.6%(10/64) | 0.60 | 0.91 | 9.38 | 86% |
Here we report our in-silico Success Rate, the metrics of complex formation, and the structural differences of within two binding contexts. Avg. metrics are calculated for all successful designs. These preliminary results strongly indicate that our chameleon-based approach can generalize to full-length multistate protein design. Together with open-source all-atom models like RFD4-proteina, we are now even closer to brigde the gap between chameleon pairs and fold-switching proteins. The visualization of our designed fold-swtich proteins are shown in link: 5 selected successful fold-switch designs
The reviewer appreciates the authors' thorough rebuttal and additional analyses. The responses has addressed most of the concerns. The reviewer therefore maintains the rating of 3 (Weak Acceptance).
Responses 1/n
We thank the reviewer for recognizing the importance and challenges of multistate protein design, the value of the Chameleon Dataset for studying how the same sequence can adopt different local structures, and AtomDiff-Chameleon’s performance in de novo chameleon design. We also appreciate the reviewer’s interest in the potential of our motif-conditioned designs. We address the reviewer’s concerns as follows:
1. Distinction between chameleon design and full-length multistate protein design.
We thank the reviewer for highlighting this distinction.
As discussed in both the Introduction and the Conclusion, we have made this distinction explicitly and explain why we take chameleon design as a starting point rather than as a demonstration of full-length conformational switching. Our approach is designed to circumvent the scarcity of multistate protein structure data. The abundance of natural chameleon sequences forms the starting point for our work. A foreseen pathway from the chameleon sequences to multistate protein design is conceived as follows:
We apologize that this vision was not clearly presented to the reviewer previously. We hope the additional experiments with RFD4-Proteina can convince the reviewer that this is a promising pathway worth taking (see response section 5).
2. Ablations of key architectural components
We thank the reviewer for this suggestion. We conducted four ablations of the components introduced for chameleon design: token-level cross-branch attention, atom-level consensus communication, and the shared-sequence consistency loss (shared-JS). We do not ablate Token DiT and Atom DiT due to the limited resources and they are mainly related to uncondition base model. We evaluated all variants using their 10k-step EMA weights on the original 1,000 paired cases, with identical secondary-structure conditions, random seeds, and initial noise for each case.
In this setting, atom-level consensus was the key communication pathway for achieving shared-sequence agreement. The full model outperformed the atom-only variant on Exact (53.2% vs. 34.1%), Success (14.3% vs. 8.1%), and SuccessSS80 (4.1% vs. 2.0%), indicating token-level context exchange complementing atom-level consensus. Cross-branch communication allows the branches to exchange information, whereas shared-JS explicitly rewards them for using that information to make consistent residue choices. All three parts contribute to the final performance.