Contribution

What Should this Page Contain?

---

Teams must document their contribution and explain why their effort is a contribution to fellow iGEMers. There is no single definition of what a contribution should be. We invite teams to be creative and generous in the knowledge, data or tools they may provide to the community.

A few examples of contributions are:

• Creating a new BioBrick part or significantly improving an existing one in the iGEM Registry.
• Developing software, tools, or resources that can considerably assist future iGEM teams.
• Sharing optimized protocols, experimental techniques, or methodologies.
• Any other contributions that provide a clear benefit to future iGEM teams.

Jett's Version: What we leave behind for the next team.

---

The section below is a separate, independently-written draft, produced by a team member outside the main documentation process. Kept here for reference and comparison; not yet fact-checked by team leadership — in particular, the Registry part codes below should be verified against actual reserved codes before being treated as final.

Five parts total — three submitted, two drafted — all under a reserved team prefix, plus four protocols and one dataset.

Parts overview

Part code	Type	Function	Status
BBa_SP2601	CDS	PETase ORF · K-12 codon-optimised	Submitted
BBa_SP2602	CDS	MHETase ORF · K-12 codon-optimised	Submitted
BBa_SP2603	Composite	Lpp–OmpA–PETase fusion (surface display)	Submitted
BBa_SP2604	Composite	Thermosensitive λ-cI857 kill switch	Drafted
BBa_SP2605	Composite	EL222 light-induced colicin cassette	Drafted

Protocols & data

• Lpp–OmpA cloning — Gibson-assembly protocol, primer sequences, troubleshooting log. See Experiments.
• PET-film hydrolysis assay — 24-well plate, mass-loss + HPLC monomer detection. See Experiments.
• Kill-switch escape assay — plate-based escape-rate measurement. See Safety and Security.
• Kinetic model — open-source Python, PET → MHET → TPA + EG, with notebook walkthrough. See Software.

For a future team

The single biggest open question flagged: long-term viability of the PETase strain under simulated launch vibration, which the team has not had access to a vibration platform to test. A future team with that access would be well positioned to extend this work into flight-relevant validation.

Continue to Jett's Version of Experiments → · Back to Jett's Version of Results