Source 1review2026MED
Toolkit/CCR5-locus knock-in CAR-T design
CCR5-locus knock-in CAR-T design
Taxonomy: Mechanism Branch / Architecture. Workflows sit above the mechanism and technique branches rather than replacing them.
Summary
Explicitly supported related components/tools include HIV-protective engineering features (CCR5-locus knock-in, C34-CXCR4). Supported as a genome-editing integration site for HIV-protective CAR-T designs.
Usefulness & Problems
Why this is useful
This design pattern uses targeted integration at the CCR5 locus in HIV CAR-T engineering. In the supplied evidence it is framed as an HIV-protective engineering feature.; targeted integration of HIV CAR designs; engineering HIV-protective CAR-T cells
Source:
This design pattern uses targeted integration at the CCR5 locus in HIV CAR-T engineering. In the supplied evidence it is framed as an HIV-protective engineering feature.
Source:
targeted integration of HIV CAR designs
Source:
engineering HIV-protective CAR-T cells
Problem solved
It addresses the need for a defined integration strategy in HIV-protective CAR-T designs.; provides a named genome-engineering strategy for HIV-protective CAR-T design
Source:
It addresses the need for a defined integration strategy in HIV-protective CAR-T designs.
Source:
provides a named genome-engineering strategy for HIV-protective CAR-T design
Problem links
provides a named genome-engineering strategy for HIV-protective CAR-T design
LiteratureIt addresses the need for a defined integration strategy in HIV-protective CAR-T designs.
Source:
It addresses the need for a defined integration strategy in HIV-protective CAR-T designs.
Taxonomy & Function
Primary hierarchy
Mechanism Branch
Architecture: A reusable architecture pattern for arranging parts into an engineered system.
Mechanisms
targeted genomic integrationTechniques
Computational DesignTarget processes
editingImplementation Constraints
cofactor dependency: cofactor requirement unknownencoding mode: genetically encodedimplementation constraint: context specific validationimplementation constraint: payload burdenoperating role: regulator
It requires genome-editing capability for CCR5-locus integration in addition to the CAR construct itself.; requires targeted genome editing at the CCR5 locus
The supplied evidence does not specify whether this strategy alone resolves antiviral efficacy, persistence, or manufacturing challenges.; the supplied payload does not provide exact construct details or direct review text on outcomes
Validation
Cell-freeBacteriaMammalianMouseHumanTherapeuticIndep. Replication
Supporting Sources
Ranked Claims
The review explicitly names gp350 and LMP1 as EBV CAR target leads, and names BRG01 as a gp350-targeted autologous CAR-T product in clinical development.
The review explicitly names HBsAg-related and PreS1-related HBV CAR strategies, including 4D06 and 4D08 as HBV-directed binder leads.
The review explicitly names VRC01, 3BNC117, and 10-1074 as HIV broadly neutralizing antibody-derived CAR binder leads.
Within the supplied evidence, the strongest explicitly supported antiviral CAR design leads are HIV Env/bNAb-based CARs, HBV HBsAg-directed CARs, and EBV gp350/LMP1-directed CARs.
The review explicitly names CCR5-locus knock-in and C34-CXCR4 as HIV-protective engineering features relevant to antiviral CAR-T design.
Approval Evidence
1 source1 linked approval claimfirst-pass slug ccr5-locus-knock-in-car-t-design
Explicitly supported related components/tools include HIV-protective engineering features (CCR5-locus knock-in, C34-CXCR4). Supported as a genome-editing integration site for HIV-protective CAR-T designs.
Source:
engineering feature summarysupports
The review explicitly names CCR5-locus knock-in and C34-CXCR4 as HIV-protective engineering features relevant to antiviral CAR-T design.
Source:
Comparisons
Source-stated alternatives
The payload also names C34-CXCR4 as another HIV-protective engineering feature.
Source:
The payload also names C34-CXCR4 as another HIV-protective engineering feature.
Source-backed strengths
explicitly identified as an HIV-protective engineering feature in the supplied evidence
Source:
explicitly identified as an HIV-protective engineering feature in the supplied evidence
Compared with C34-CXCR4 protective module
The payload also names C34-CXCR4 as another HIV-protective engineering feature.
Shared frame: source-stated alternative in extracted literature
Strengths here: explicitly identified as an HIV-protective engineering feature in the supplied evidence.
Relative tradeoffs: the supplied payload does not provide exact construct details or direct review text on outcomes.
Source:
The payload also names C34-CXCR4 as another HIV-protective engineering feature.
Ranked Citations
- 1.