Week 2 HW: DNA Design
Part 0: Set up in Kernel Get oriented in the software tool before you design anything.
- Log in to Kernel and join the HTBAA 2026 workspace.
TBD
- Create a repository for your project, and inside it a folder named for you and your project, e.g. lastname-project.
Awaiting Kernel Access but the provisional name for the repository is: Palmer-Project_ZP_Freeze
- Spend some time exploring: open an existing part and an existing construct and notice the difference. Check out the different tools and ask Kernel AI some questions!
TBD
Deliverable for this part: a one-sentence note in your write-up with the name of your repository and folder, so we can find your work.
I’m awaiting Kernel Access but the provisional name for the repository is: Palmer-Project_ZP_Freeze
(TBD - Kernel Access needs to be supplied)
Part 1: Define your expression target
Start from the project you proposed in Homework #1 and pin down exactly what your cells need to make. Answer in your write-up:
- What molecule are you expressing?
A protein from Lithobates sylvaticus / Rana sylvatica (Wood Frog): FR10
Source: https://www.ncbi.nlm.nih.gov/protein/AAC60284.1
Paper:
Cai Q, Storey KB. Upregulation of a novel gene by freezing exposure in the freeze-tolerant wood frog (Rana sylvatica). Gene. 1997 Oct 1;198(1-2):305-12. doi: 10.1016/s0378-1119(97)00332-6. PMID: 9370296.
- What is the sequence? Give the protein or RNA sequence, or the specific gene, you will encode, and say where it comes from (a database accession such as UniProt or NCBI, a known part, or de novo). Cite it.
mkvlalvvlv iaisgleagv vkrdaqdplq qitdifqgis ktlqekfana eipsqtqelg akiqahgeti sasiqkwiee mvalskekls
Source: https://www.ncbi.nlm.nih.gov/protein/AAC60284.1
- What host or chassis? The living system from HW1, for example E. coli, S. cerevisiae, CHO or another mammalian line, or a cell-free system. Your host drives almost every part choice that follows.
The living system employed would be E. Coli.
- Where does the product need to go? Cytoplasm, secreted, membrane, or a compartment? This decides whether you need a signal peptide or targeting sequence.
The product needs to go to the cytoplasm.
Part 2: Design your genetic parts Every construct is built from parts. Decide which parts your target needs, then create or import each one in Kernel with the correct part type. At minimum, choose the elements below for your host.
[TBD]
For each part you use, record in Kernel (and note in your write-up):
The part type and a short name.
[TBD]
Its sequence and where it came from (a Kernel part, a database, or designed).
[TBD]
One sentence of justification, why this part, for this host, for this product.
[TBD]
You do not need to hand-design a backbone from scratch; you may reuse an existing one and say what it provides.
[TBD]
Part 3: Assemble your construct
Now put the parts together into a single construct in Kernel.
[TBD]
Create a new construct in your folder and add your parts in the correct 5’→3’ order for your host (for a basic expression cassette: promoter → RBS or 5’ UTR/Kozak → CDS → terminator, plus any signal peptide or tag, in the vector backbone).
[TBD]
Check the assembled sequence: the reading frame is intact, the start and stop codons are where you expect, and there are no accidental internal stops.
[TBD]
Look at the construct map Kernel renders and confirm the parts sit in the order and orientation you intended.
[TBD]
Deliverable for this part: your assembled construct in Kernel, plus an exported schematic of it in your write-up, with a brief description of the design.
[TBD]
Part 4: Optimize and quality-check
Use Kernel’s design tools on your coding sequence and construct, and interpret the results rather than just running them.
[TBD]
Codon-optimize your CDS for your chosen host. Compare before and after: what changed, and why does codon usage matter for expression in this organism? Note any constraints you applied (e.g. avoiding certain restriction sites, GC content).
[TBD]
Search your sequence (BLAST / sequence search) against known sequences. Is your CDS what you think it is? Is it identical to a natural gene, or novel? What is the closest match?
[TBD]
Run the safety screen on your construct. Summarize what it checks for and what it reports. If it flags something, explain whether it is expected for your design and how you would respond.
[TBD]
Deliverable for this part: a short paragraph per tool covering what you ran, what it returned, and what you concluded. Screenshots welcome.
[TBD]
Part 5: From design to build A sequence in software is not yet DNA. Using this week’s readings, reason about how your construct would actually be made. Answer in your write-up:
[TBD]
How would you build it? Would you order it as synthetic DNA, assemble it from smaller fragments (e.g. Gibson assembly), or build it from a pool of oligos synthesized on a chip? Justify your choice given your construct’s length and complexity.
[TBD]
What does synthesis constrain? Synthesis has error rates and struggles with certain sequences. Does your design contain anything hard to synthesize? How would error correction or fragment-based assembly change your approach?
[TBD]
Prototype vs. scale. Mirroring HW1: the way you’d build one construct to test your idea may differ from how you’d produce DNA at the scale your product needs. Briefly describe both if they differ.
Ground this in at least two of the assigned readings and cite them.
[TBD]
Part 6: What don’t you know yet?
[TBD]
As in Homework #1, close by naming the edges of your design. Identify the 2–3 biggest unknowns or risks in your construct. For example: Will the promoter give the right expression level? Will the protein fold and be active in this host? Will it be secreted? Is codon optimization enough, or do you need to tune it empirically?
[TBD]
For each, state how you would find out: the measurement, experiment, or design variant you would try next. A good answer here shows you know which decisions are still bets.