TruaceTracing the truth around AIWednesday, July 15, 2026
TRV-2026-0225Certified recordPeer-reviewed

Randomized, Double-Blind, Placebo-Controlled First-in-Human Trial of a First-in-Class AI-Designed Monoclonal Antibody (GB-0669) Against the Conserved SARS-CoV-2 Spike S2 Stem Helix

Background Antibodies against the SARS-CoV-2 spike receptor-binding domain provided effective COVID-19 treatment until resistant variants emerged. GB-0669 is a half-life-extended monoclonal antibody optimized using artificial intelligence. It targets the conserved spike S2 stem helix, a region subject to limited selective pressure from antibody responses induced by natural infection or vaccination. Methods Pre-clinical safety studies were conducted in cynomolgus monkeys. In the first-in-human trial, healthy adul…

Health · G Space — documented gain · certified 2026-07-15 · v1 · article view · machine-readable

Current reading — gain

AI-optimized monoclonal antibody GB-0669 was safe and well-tolerated in healthy adults with dose-proportional pharmacokinetics and a 54-day half-life and dose-dependent serum live virus neutralization.

What this doesn’t fix

Findings limited to small first-in-human study in healthy adults aged 18-55 with 51 participants, not yet tested for efficacy in immunocompromised patients.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0225, v1: “Randomized, Double-Blind, Placebo-Controlled First-in-Human Trial of a First-in-Class AI-Designed Monoclonal Antibody (GB-0669) Against the Conserved SARS-CoV-2 Spike S2 Stem Helix.” Truvace, 2026-07-15. /record/TRV-2026-0225 (accessed at citation time). sha256 3cb561397ac9c678

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv13cb561397ac9

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0225 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.