Part:BBa_K3365014
pBAD/araC upstream of RFP with inhibition unit containing target
To facilitate measurements, we use the RFP as a reporter protein, which can be exchange to other reporters according to the users’ needs. The RFP gene sequence (BBa_K3365052) is located directly downstream of BBa_K3365006 (Target sequence downstream of pBAD/araC) followed by BBa_B0015 (rrnBT1-T7TE). The transcription of the RFP gene is under the control of the inducible pBAD/araC promoter designed to carry PAM and target sequence downstream of pBAD. In our part, the “target” is the target sequence for PDCD1 CRISPR gene editing in one clinical trial, which can be identified and bound by the complex of dCas9 and corresponding sgRNA.
Usage and Biology
This part is used to expression of RFP protein regulated by the signal of arabinose and the on-target or not of dCas9. The pBAD is regulated by the AraC protein, which is both a positive and a negative regulator. The binding of dCas9 to any position within the region between the promotor and RBS might prevent transcription. Therefore, the uninduced transcriptional level of RFP is very low. In the presence of arabinose, transcription from the pBAD promoter is turned on and there will be a relatively strong fluorescence expression. In the presence of both arabinose and the complex of dCas9 and sgRNA, the complex might bind to the target sequence and the transcription is partially inhibited because of the block of RNAP. So, a relatively weak fluorescence expression of bacteria indicates a dCas9 with higher on-target rate that effectively inhibits the expression of reporter gene.
Results
The inducible pBAD/araC promoter (BBa_K3365013) is amplified with the primer F1/R1 to add restriction cutting sites, target sequence and part of the RBS sequence (BBa_K3365002). The RFP with double terminator is amplified with the primer F2/R2 to add restriction cutting sites and part of the RBS sequence (BBa_K3365002). The above PCR products are ligated through overlap PCR with the primer F1/R2 to get the fragment with suitable restriction sites and the product can be ligated into its backbone pUC57 by enzymic digestion and connection. The eletrophoretic profile of the overlap PCR (F1/R2) and colony PCR (M13 fwd/ M13 rev) product and the sequencing result reveal the successful construction of the fragment and the plasmid, named pIn-RTr.
F1: 5’-CGAGCTCTTATGACAACTTGACGGCTACATCATTCAC-3’
R1: 5’-TTCTTAAAGGCAGTTGTGTGACACGGAAGCGGATGGAGAAACAGTAGAGAGTTGCG-3’
F2: 5’-TTCCGTGTCACACAACTGCCTTTAAGAAGGAGATATACATATGGCGAGTAGCGAAGACG-3’
R2: 5’-GGAATTCCCGCCCTAGGTATAAACGCAGAAAG-3’
M13 fwd: 5’-GTAAAACGACGGCCAGT-3’
M13 rev: 5’-GTCATAGCTGTTTCCTG-3’
To verify the inhibition effect of pdCas9 on pIn-RTr, we set up six culturing system (as shown in the table below) and use microplate spectrophotometer to examine fluorescence intensity. L-arabinose is added to induced the expression of RFP.
The results are shown below, from which we could see 64.39 times of fluorescence/OD600 difference between transform group (without the expression of dCas9) and co-transform group (with the expression of dCas9), indicating our transcription inhibition system does work.
To know about the inhibition of the expression of RFP by dCas9 in a single cell as well as verify our mutant library, the obtained dCas9 mutant library and the wild-type dCas9 are transformed into MG1655 carrying pIN-RTr. Then, we analyze the red fluorescence by flow cytometry. The results are shown below. 77.12% cells have positive red fluorescence in the absence of dCas9, while the proportion of positive cells decreases to 0.08% in the presence of dCas9, showing a quite efficient inhibition of wild-type dCas9. And the positive rate rises to 78.37% when the cells are transformed into dCas9 mutant library, which means the lack of function in most of mutant dCas9 and the successful construction of our mutant library.
Sequence and Features
- 10COMPATIBLE WITH RFC[10]
- 12COMPATIBLE WITH RFC[12]
- 21INCOMPATIBLE WITH RFC[21]Illegal BamHI site found at 1913
Illegal XhoI site found at 1922 - 23COMPATIBLE WITH RFC[23]
- 25INCOMPATIBLE WITH RFC[25]Illegal AgeI site found at 979
Illegal AgeI site found at 1789
Illegal AgeI site found at 1901 - 1000INCOMPATIBLE WITH RFC[1000]Illegal SapI site found at 961
| None |