Conserved residues within the HIV-1 Vpu transmembrane-proximal hinge region modulate BST2 binding and antagonism
Bibliographic record
Abstract
BACKGROUND: BST2 inhibits HIV-1 release by tethering nascent virions to the surface of infected cells. HIV-1 Vpu overcomes this restriction by removing BST2 from viral budding sites via BST2 intracellular trapping and sequestration, surface downregulation and/or displacement mechanisms. Vpu is composed of a short luminal tail, a transmembrane domain (TMD) and a cytoplasmic hinge region that is followed by two helices. BST2 counteraction relies on the ability of Vpu to physically bind BST2 through TMD interactions and recruit the clathrin-dependent trafficking machinery via a canonical acidic di-leucine signalling motif within the helix-2 of Vpu. The highly conserved Vpu transmembrane-proximal hinge region encompasses residues that resemble an acidic leucine-based trafficking motif, whose functional roles are currently ill-defined. In this study, we investigated the contribution of these residues towards Vpu-mediated BST2 antagonism. RESULTS: We show that while these conserved residues have no intrinsic activity on the cellular distribution of Vpu in the absence of BST2, they regulate the ability of Vpu to bind to BST2 and, consequently, govern both BST2-dependent trafficking properties of the protein as well as its co-localization with BST2. Moreover, these residues, particularly a glutamic acid residue positioned immediately following the TMD, are a determinant not only for efficient targeting of BST2, but also binding and degradation of CD4, another host membrane protein targeted by Vpu. Mechanistically, our data are consistent with a role of these residues in the maintenance of the Vpu TMD conformational configuration such that interactions with membrane-associated host targets are favoured. CONCLUSIONS: Altogether, this work demonstrates an important regulatory role of the transmembrane-proximal Vpu hinge region residues towards enabling the protein to efficiently engage its target host proteins. Thus, this highly conserved, cytosolic Vpu hinge region may represent an attractive target for the development of anti-Vpu inhibitors.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".