Lost in Latent Space

Memo: Golden Gate / Type IIS assembly for multi-fragment cloning

Background

Classical restriction cloning hit a wall around three-fragment assemblies. Each fragment needed a unique pair of compatible restriction sites at its ends, the host plasmid had to be free of those sites, and every junction left a scar — the recognition sequence itself, deposited at the seam between fragments. For pathway-scale work (five, ten, twenty parts), the combinatorics of finding non-clashing site pairs collapsed.

Golden Gate, introduced by Engler, Kandzia, and Marillonnet in 2008, sidesteps both constraints by using Type IIS restriction enzymes — BsaI, BbsI, SapI, and the like — instead of the more familiar Type II enzymes (EcoRI, BamHI).

The mechanism

Type II enzymes (most of what you learned in undergrad) bind a palindromic recognition site and cut inside it. The cut is symmetric; the recognition sequence is preserved on both products.

Type IIS enzymes bind a non-palindromic site and cut outside it, at a defined offset. BsaI, for example, recognizes GGTCTC and cuts one base downstream, leaving a 4-nucleotide 5′ overhang:

5'... G G T C T C N | N N N N ... 3'
3'... C C A G A G N   N N N N | ... 5'

The four-base overhang is whatever you designed it to be. There’s no constraint that it match the recognition site, because the enzyme isn’t cutting inside its site at all.

Why this changes the design problem

Three consequences follow:

Tradeoffs

Open questions for our workflow

What’s next

Gibson assembly is the obvious comparison — overlap-based, sequence-agnostic, no scar concerns at all, but harder to multiplex cleanly. The right next read is the side-by-side benchmarks in Casini et al. (2015), which still hold up.