AAV genome integrity defines how closely encapsidated genomes match the intended construct in length, structure, and junction correctness. When integrity drifts, expression becomes erratic, replicate variability increases, and cross‑batch conclusions break. The practical outcome is simple: without a common, evidence‑based integrity framework, teams can't compare vendors or lots with confidence, nor standardize internal methods and reports. This guide lays out the minimum metric set, fit‑for‑purpose assays, and a reporting template that turns integrity signals into decision‑ready outputs.

TL;DR

• A compact metric set—full‑length fraction, effective genome yield, breakpoint landscape, junction correctness, and contamination‑aware context—answers most comparability questions.
• Adopt a platform‑agnostic evidence stance and, where structure matters, run short‑ and long‑read workflows in parallel with defined controls and replicates.
• Express thresholds as project‑defined targets with failure triggers and confirmatory actions; avoid universal hard cutoffs.
• Standardize an integrity reporting template with metric cards, aligned coverage, breakpoint summaries, a junction table, an impurity profile, and an evidence appendix.
• Use uncertainty transparently: include replicate counts, %CV, and 95% confidence intervals; grade evidence when orthogonals concur.

Define Genome Integrity in AAV and Why "Success" Depends on It

Genome integrity is the extent to which the packaged genome matches the intended design end‑to‑end, including ITR continuity and correctness at critical junctions (promoter boundaries, splice sites, coding junctions, and polyA). In practice, integrity governs reproducibility. Lots with similar titers but different integrity profiles can behave differently in expression assays, leading to misleading vendor comparisons and unstable internal baselines.

What Counts as "Intact" in Practice

Operationally, "intact" means a molecule spans the construct from one ITR to the other with no truncations, large deletions, or rearrangements, and with correct sequence at predefined key junctions. Methods should classify molecules or reads using explicit rules (alignment identity, minimum span across ITR‑adjacent windows) and then validate with targeted checks at high‑value junctions. Because algorithms and protocols differ, evidence notes and parameter versions must accompany any "intact" count to keep results comparable across teams.

Downstream "Success" as Decision Outcomes

This guide ties AAV genome integrity to two primary outcomes: 1) lot‑to‑lot and vendor‑to‑vendor comparability for selection, and 2) internal method and report standardization so future runs align to the same dictionary. Troubleshooting remains optional: when metrics land in a warning zone, the framework prescribes confirmatory actions and next steps without turning the entire effort into a fault‑finding exercise.

Common Failure Modes That Distort Results

Truncations often concentrate near ITR‑adjacent regions; internal deletions remove critical elements; rearrangements (inversions, duplications) disrupt continuity; and incorrect junctions at promoters or splice sites degrade expression predictability. For a broader primer connecting integrity to outcomes and practical examples, see the overview on AAV sequencing principles and applications: AAV sequencing principles, applications, and therapeutic case studies.

Core AAV Genome Integrity Metrics and What Each One Really Tells You

A small, consistently defined metric set explains most "why did this result change" questions and enables cross‑batch comparability. The emphasis here is on definitions that independent reviewers can reproduce from evidence attachments.

Full‑Length Fraction and Effective Genome Yield

Full‑length fraction is the proportion of molecules that span the intended construct from ITR to ITR without structural breaks. Long‑read sequencing classifies reads into full‑length versus partial based on end‑to‑end alignment and identity thresholds, while digital PCR‑based designs can infer intactness with two distal targets and appropriate statistical modeling. Effective genome yield converts nominal genome titer into the absolute quantity of intact molecules (e.g., vg/mL × full‑length fraction). This adjustment often explains discrepancies when two lots have similar titers but diverge in experimental performance. For a neutral overview of analytical techniques mapping to AAV critical quality attributes, see: AAV vector characterization techniques and CQAs (review).

Truncation and Breakpoint Landscape

The breakpoint landscape highlights where truncations cluster along the genome. Enrichment near ITR‑adjacent windows is commonly observed due to hairpin structures and replication stress, and it often correlates with batch‑specific preparation effects. Reporting should include position bins, event frequencies normalized to coverage, and hotspot flags.

Rearrangement Signatures

Rearrangements—such as inversions and duplications—are most reliably detected by long‑read sequencing that preserves molecule‑level context. In practice, reports list event types, approximate positions, and estimated frequencies with uncertainty bounds. See the peer‑reviewed work on noncanonical configuration analysis: molecular configuration analysis with HiFi long‑reads.

Junction Correctness for Key Regions

Junction correctness focuses on areas where small sequence errors can have outsized impacts: ITR junctions, promoter boundaries, splice donors/acceptors, coding junctions, and polyA sites. A pragmatic approach blends long‑read continuity across these regions with short‑read depth for SNVs/indels at low variant allele fractions.

Contamination‑Aware Integrity Interpretation

Contamination‑aware interpretation distinguishes intended genomes from impurity classes such as host cell DNA, plasmid backbone fragments, and helper sequences. For a concise platform and workflow context, see: AAV sequencing technologies, platforms, workflows, and applications.

Measurement Strategies: Matching Assays to the Metric

Different integrity questions need different assays. A platform‑agnostic evidence stack prevents over‑calling and makes cross‑team comparisons possible. Where structural context is decision‑critical, running short‑ and long‑read in parallel is recommended.

Short‑Read Mapping for Coverage and Small Variants

Short‑read sequencing provides high‑depth coverage to detect small variants and to infer truncation‑prone windows from coverage drops. It also enables multi‑reference mapping to quantify impurity classes. See the review of sequencing-based methods: review of sequencing-based methods for AAV characterization.

Long‑Read Strategies for Structural Context

Long‑read sequencing resolves molecule‑level continuity, ITR integrity, rearrangements, and breakpoint positions. High‑fidelity protocols emphasize consensus accuracy and library strategies that preserve end‑to‑end spans.

Targeted Checks for Hard Regions

Hard regions include ITRs and specific regulatory junctions with high GC content or secondary structure. For dedicated checks on ITR analysis challenges, see: ITR sequencing workflow, analysis challenges, and trends.

Controls and Replicates That Prevent False Integrity Calls

Controls and replicates convert interesting plots into trusted decisions. Orthogonal confirmations (digital PCR, size‑based separations, AUC/MP/SEC‑MALS) should accompany NGS metrics. Reports should include replicate counts (n), %CV or %RSD, and 95% CIs alongside method notes.

Reporting Integrity Metrics So Sponsors Can Compare Batches and Vendors

A reporting template that standardizes definitions, thresholds, and evidence attachments turns integrity into a comparable attribute rather than an anecdote.

Minimum Report Package

• Metric cards with values, units, 95% CI, %CV, and replicate counts.
• An aligned coverage plot annotated with ITRs and other key features.
• A breakpoint summary with position bins and normalized frequencies.
• A junction correctness table for predefined regions with links to read evidence.
• An impurity profile with class taxonomy and interpretation notes.

A Metric Dictionary That Eliminates Ambiguity

A metric dictionary prevents silent drift in definitions. For each metric, specify counting rules, normalization, and how exceptions like ITR hairpins or GC bias are treated. Version each algorithm and parameter set so that numbers are reproducible.

How to Present Uncertainty Without Losing Trust

Trust increases when uncertainty is explicit. Report 95% confidence intervals, %CV across replicates, and evidence grades based on control agreement and the presence of orthogonal confirmations.

Batch‑to‑Batch Comparison Format

Comparison sheets work best as side‑by‑side tables using the metric dictionary's units and terms. For framing around suitability attributes, see: viral vector suitability attributes in AAV and lentivirus (context only).

Interpreting Integrity Signals: Turning Metrics Into Next‑Step Decisions

Integrity interpretation should map directly to next actions using project‑defined targets, failure triggers, and confirmatory steps.

Decision Matrix: Proceed vs Fix vs Confirm

• Proceed when all core metrics meet target bands with convergent evidence and stable %CV across replicates.
• Fix when a single root cause plausibly explains deviations and confirmation verifies improvement.
• Confirm when metrics sit near boundaries or evidence conflicts; add targeted assays before committing to selection or remediation.

Common Misreads and How to Avoid Them

Misreads often arise from mapping artifacts in palindromic ITRs, GC‑bias in coverage plots, or conflating partial genomes with rearrangements. For boundaries and secondary confirmation, see: AAV integration analysis: scope and considerations.

Practical Workflow: From Sample Intake to Deliverables

A stepwise, checkpointed workflow reduces rework and keeps integrity conclusions reproducible across runs and teams.

QC Checkpoints

Log sample receipt, document DNase/polishing policies, version library parameters, and maintain run‑level QC manifests. For cross‑vector analogy, see: lentiviral integration analysis methods and risks.

FAQ

What Does "AAV Genome Integrity" Mean in Sequencing Reports?

It means the proportion and structure of packaged genomes match the intended design end‑to‑end with correct key junctions.

How Do You Estimate Full‑Length Fraction Without Overcalling It?

Use long‑read continuity rules with defined identity thresholds and confirm with an orthogonal method while reporting 95% CI and replicates.

Why Do Apparent Truncations Cluster Near ITR‑Adjacent Regions?

ITR hairpins and GC‑rich structures drive breakpoint hotspots and can amplify mapping artifacts without long‑read confirmation.

How Can I Distinguish True Rearrangements From Mapping Artifacts?

Rely on molecule‑level long‑read evidence with supporting reads and confirm suspicious events with targeted assays.

What Minimum Deliverables Should an Integrity Report Include?

Metric cards with CI/%CV/n, aligned coverage, a breakpoint summary, a junction correctness table, an impurity profile, and a methods/evidence appendix.

Next steps

Teams can adapt the metric dictionary and reporting template in this guide to standardize vendor and batch comparability immediately; for neutral assistance aligning assays to metrics and packaging evidence for sponsors, CD Genomics can support projects for research use only (RUO).