DNA Recorder: Tracing Single Cells in Mouse Development

This guide explains how a DNA recorder—a molecular tool that logs cellular events into the genome—can trace the path of a single cell through early mouse development. You will learn the principles, the step-by-step experimental workflow, and how to interpret the resulting lineage map. No prior wet-lab experience is assumed, but basic molecular biology familiarity helps.

What You’ll Need

• Mouse embryos (typically at the zygote or early cleavage stage)
• A DNA recorder construct (e.g., a CRISPR-based system with a homing guide RNA and a barcode cassette)
• Microinjection equipment (micropipette, micromanipulator, inverted microscope)
• Embryo culture medium and incubator
• DNA extraction kit
• PCR primers specific to the barcode region
• High-throughput sequencing platform (e.g., Illumina)
• Bioinformatics software (e.g., Python, R, or dedicated lineage tracing tools)

Step-by-Step

1. Design the recorder construct. Choose a CRISPR-Cas9 system where Cas9 cuts a specific target site. Include a homing guide RNA (gRNA) that recognizes the cut site and a barcode cassette (a short, unique DNA sequence) flanked by homology arms. The barcode will be inserted at the cut site, and each insertion event creates a new, heritable mutation.
2. Prepare the construct. Clone the gRNA and barcode cassette into a plasmid. Verify the sequence by Sanger sequencing. Linearize the plasmid or prepare it as a circular DNA for injection.
3. Inject the construct into a zygote. Using microinjection, deliver the DNA recorder construct (and Cas9 mRNA or protein if not already in the embryo) into the cytoplasm or pronucleus of a fertilized mouse egg. The construct integrates randomly or via homology-directed repair at the target site.
4. Culture the embryo. Place the injected zygote in a drop of embryo culture medium under oil. Incubate at 37°C, 5% CO2. Allow development to proceed to the desired stage (e.g., blastocyst, gastrula). The recorder will be active during cell divisions, generating new barcode mutations in each daughter cell.
5. Dissect and isolate single cells. At the chosen developmental stage, dissociate the embryo into a single-cell suspension using enzymatic digestion (e.g., trypsin) and gentle pipetting. Sort individual cells into separate wells of a 96-well plate using a micromanipulator or FACS.
6. Extract DNA from each cell. Use a DNA extraction kit designed for single cells. Follow the manufacturer’s protocol to obtain genomic DNA from each well.
7. Amplify the barcode region. Design PCR primers that flank the barcode cassette. Perform PCR on each single-cell DNA sample to amplify the barcode region. Include unique molecular identifiers (UMIs) in the primers to correct for PCR errors and amplification bias.
8. Sequence the amplicons. Pool the PCR products from all cells and sequence them on a high-throughput platform. Aim for sufficient read depth to cover each barcode multiple times.
9. Analyze the lineage data. Use bioinformatics tools to process the sequencing reads: demultiplex by cell, align to the barcode reference, and call mutations. For each cell, record the set of barcode mutations present.
10. Reconstruct the lineage tree. Based on the mutation patterns, infer the ancestral relationships between cells. Cells sharing a unique set of mutations are clonally related. Use phylogenetic algorithms (e.g., maximum parsimony) to build a tree that shows the division history from the zygote to each sampled cell.
11. Map cell fates. Correlate the lineage tree with the spatial position or gene expression of each cell (if you also performed single-cell RNA-seq or imaging) to determine which developmental paths each cell took.

Common Mistakes

• Using a non-homing gRNA. If the gRNA does not recognize the target site after the first cut, the barcode will not accumulate mutations over divisions, and lineage resolution will be lost.
• Insufficient barcode diversity. If the barcode cassette is too short or the initial barcode is identical in all cells, you won’t distinguish different lineages. Use a random barcode library or a long enough sequence.
• PCR bias. Amplifying the barcode region unevenly can skew mutation detection. Use UMIs and optimize PCR conditions to minimize bias.
• Contamination between cells. When isolating single cells, any cross-contamination mixes barcodes and corrupts lineage inference. Use sterile technique and verify cell purity.
• Ignoring sequencing errors. Sequencing errors can be mistaken for real mutations. Use error-correction algorithms and set a minimum read depth for calling a mutation.

Tips

• Test the recorder in vitro first. Before injecting embryos, validate that the construct works in cultured cells to ensure the gRNA cuts and the barcode integrates correctly.
• Use a constitutive promoter. Drive Cas9 and the gRNA with a ubiquitous promoter (e.g., CAG) to ensure activity in all cells of the embryo.
• Optimize injection timing. Inject at the one-cell stage to maximize the chance of integration before the first division. Later injection may result in mosaic embryos.
• Include a fluorescent marker. Add a GFP or RFP reporter to the construct to visually confirm successful integration and expression.
• Sequence deeply. For each cell, aim for at least 100x coverage of the barcode region to reliably detect mutations present in a minority of reads.

Troubleshooting

• No barcode mutations detected. Check that Cas9 is active (e.g., via a separate control). Verify the gRNA sequence matches the target site. Increase the concentration of the construct or use a stronger promoter.
• Embryos fail to develop. The injection process may be toxic. Reduce the injection volume, use a less stressful injection buffer, or inject into the cytoplasm instead of the pronucleus.
• Low sequencing yield. Ensure PCR amplification worked by running a gel. Increase the number of PCR cycles (but beware of overamplification). Check that the sequencing library is properly quantified.
• Lineage tree looks chaotic. This can happen if the barcode mutates too fast (every division) or too slow (no mutations). Adjust the rate by modifying the gRNA efficiency or the number of target sites. Also, confirm that the cells you sampled are truly single and not doublets.
• Barcode mutations are not heritable. If the barcode is lost during cell division, it won’t be passed to both daughters. Use a construct that integrates into a stable genomic locus and is not excised.

Frequently Asked Questions

How does a DNA recorder differ from traditional lineage tracing?

Traditional lineage tracing uses a single fluorescent marker that is inherited but does not change. A DNA recorder accumulates mutations over time, providing a higher-resolution history of cell divisions.

Can this method be used in other organisms?

Yes, the principles apply to any organism where you can deliver the construct and isolate single cells, such as zebrafish or organoids. However, the injection and culture steps must be adapted to the species.

How many cells can I trace in one embryo?

In theory, every cell of the embryo can be traced as long as you can isolate and sequence them. In practice, the number is limited by the barcode diversity and sequencing throughput, but hundreds to thousands of cells are feasible.

What is the resolution of the lineage tree?

The resolution depends on the mutation rate. If the recorder mutates every cell division, you can resolve each division. If it mutates less frequently, you only see larger clades. You can tune the rate by adjusting the number of target sites.

How do I know the mutations are real and not artifacts?

Use UMIs to correct for PCR errors, sequence both strands, and require a minimum read depth. Also, include negative controls (cells without the recorder) to identify background mutations.

Can I combine this with single-cell RNA-seq?

Yes, you can perform both DNA and RNA sequencing from the same cell. This allows you to link the lineage tree with gene expression, revealing how fate decisions relate to molecular states.

Related

• ESP32 Dual Core Scheduling: How to Use Both Cores
• Beats Solo 4 Controls: Buttons & Mic Guide
• JS Custom Actions: Functions vs Classes