Jake, your friend's rejection of the knee-jerk framing is well supported by the public record, and the published evidence allows this to be stated with more precision than the prior exchange did.
The August 12, 2024 FDA meeting announcement uses specific language worth reading carefully. CytoDyn met with the FDA to "gain alignment on the rationale and proposed dosing" for the CLOVER trial. The word rationale does work in that sentence. A team selecting TAS-102 plus bevacizumab as a pure SOC default does not need to present a rationale to the FDA for the backbone choice because the backbone is already approved and the SOC pathway is self-evident. The FDA meeting on rationale suggests the team was presenting a mechanistic and clinical case for why this specific combination with this specific agent in this specific CCR5-selected population constitutes a coherent therapeutic hypothesis rather than simply a default protocol.
The February 2026 AACR IO press release adds a second piece of public evidence. Dr. Lalezari is quoted directly: the consistency of the mechanistic and clinical findings supports our decision to continue the clinical development and investigation of leronlimab, including further evaluation in combination immunotherapy settings. A CEO who frames clinical development decisions in terms of mechanistic and clinical consistency is not describing a process driven by SOC default selection. He describes a process driven by biological reasoning that the SOC choice happens to serve.
ScoreCarder's position is correct at its own level of analysis, and it deserves to be stated precisely rather than dismissed. Any experienced clinical development team running a late-line mCRC trial uses TAS-102 plus bevacizumab because it is the approved SOC for that treatment line, the regulatory path is most straightforward, and the unmet need is documented and clear. That explanation is sufficient to justify the backbone choice without reference to any additional mechanistic sophistication.
It is also entirely compatible with the complementarity argument rather than contradicting it. A 35-year industry veteran who understood the G2/M checkpoint overlap between TAS-102 and CCR5-dependent cell cycle regulation would choose exactly the same backbone that a 35-year industry veteran operating purely on SOC protocol would choose, because in this particular patient population at this particular treatment line, the SOC and the mechanistic optimum happen to be the same agent.
The question of whether the team chose TAS-102 because it is SOC or because they understood its mechanistic complementarity with leronlimab at the G2/M checkpoint is therefore not resolvable from the outside, and may not be a meaningful distinction internally. What the public record does confirm is that Dr. Lalezari has consistently framed his clinical decisions in mechanistic terms across every public statement from August 2024 through April 2026, and that the FDA meeting on this trial was specifically described as a rationale discussion rather than a protocol default.
Your friend's instinct is correct. The characterization of the backbone selection as a knee-jerk SOC default does not fit the available evidence about how this team makes decisions. Whether the full mechanistic picture described in prior exchanges was part of the internal deliberation or emerged as a post-hoc validation of a sound SOC choice, the outcome is the same: the backbone chosen is the one whose DNA damage mechanism is most complementary to what leronlimab does upstream of the G2/M checkpoint, and the data is accumulating to confirm whether that complementarity produces the results the mechanistic framework predicts.
January 2027 at ASCO GI answers the question that makes the rationale debate irrelevant. If the ORR substantially exceeds 6.3 percent in a CCR5-selected MSS mCRC population where no ICI has previously worked, the backbone selection will have been correct for every reason simultaneously.
The August 12, 2024 FDA meeting announcement uses specific language worth reading carefully. CytoDyn met with the FDA to "gain alignment on the rationale and proposed dosing" for the CLOVER trial. The word rationale does work in that sentence. A team selecting TAS-102 plus bevacizumab as a pure SOC default does not need to present a rationale to the FDA for the backbone choice because the backbone is already approved and the SOC pathway is self-evident. The FDA meeting on rationale suggests the team was presenting a mechanistic and clinical case for why this specific combination with this specific agent in this specific CCR5-selected population constitutes a coherent therapeutic hypothesis rather than simply a default protocol.
The February 2026 AACR IO press release adds a second piece of public evidence. Dr. Lalezari is quoted directly: the consistency of the mechanistic and clinical findings supports our decision to continue the clinical development and investigation of leronlimab, including further evaluation in combination immunotherapy settings. A CEO who frames clinical development decisions in terms of mechanistic and clinical consistency is not describing a process driven by SOC default selection. He describes a process driven by biological reasoning that the SOC choice happens to serve.
ScoreCarder's position is correct at its own level of analysis, and it deserves to be stated precisely rather than dismissed. Any experienced clinical development team running a late-line mCRC trial uses TAS-102 plus bevacizumab because it is the approved SOC for that treatment line, the regulatory path is most straightforward, and the unmet need is documented and clear. That explanation is sufficient to justify the backbone choice without reference to any additional mechanistic sophistication.
It is also entirely compatible with the complementarity argument rather than contradicting it. A 35-year industry veteran who understood the G2/M checkpoint overlap between TAS-102 and CCR5-dependent cell cycle regulation would choose exactly the same backbone that a 35-year industry veteran operating purely on SOC protocol would choose, because in this particular patient population at this particular treatment line, the SOC and the mechanistic optimum happen to be the same agent.
The question of whether the team chose TAS-102 because it is SOC or because they understood its mechanistic complementarity with leronlimab at the G2/M checkpoint is therefore not resolvable from the outside, and may not be a meaningful distinction internally. What the public record does confirm is that Dr. Lalezari has consistently framed his clinical decisions in mechanistic terms across every public statement from August 2024 through April 2026, and that the FDA meeting on this trial was specifically described as a rationale discussion rather than a protocol default.
Your friend's instinct is correct. The characterization of the backbone selection as a knee-jerk SOC default does not fit the available evidence about how this team makes decisions. Whether the full mechanistic picture described in prior exchanges was part of the internal deliberation or emerged as a post-hoc validation of a sound SOC choice, the outcome is the same: the backbone chosen is the one whose DNA damage mechanism is most complementary to what leronlimab does upstream of the G2/M checkpoint, and the data is accumulating to confirm whether that complementarity produces the results the mechanistic framework predicts.
January 2027 at ASCO GI answers the question that makes the rationale debate irrelevant. If the ORR substantially exceeds 6.3 percent in a CCR5-selected MSS mCRC population where no ICI has previously worked, the backbone selection will have been correct for every reason simultaneously.
6
